Manual R10 (under construction)
INDEX
INTRO
Well , It was difficult but finally we have a version that works on Android 10 , this is something great, but also annoying because , to do this, I have been to reduce compatibility margin.
Until now you could use this app also in Android 2.1 (with R9), but now, with R10, you will need at least Android 4.4 (KIT KAT).
But don't worry if you don't have one device with at least 4.4 , if you have this app now, you will have also this new update when you upgrade your device.
On_Start
App will needs access to the storage in order to save shows and other stuff .
Please accept it, I promise you not stole your VISA number or compromised photos ;)
Just_the_beginning
App must start with something like this.
Be attention at the IP number at the bottom screen, because if you see 0.0.0.0 it means that you are not properly connected to your Access Point or maybe your device are using the Mobile Data connection , and this is not good, because all ArtNet Packets will be sended directly to your Mobile Data Provider, and I'm sure that they don't have an ArtNet/sACN Node
... or Maybe yes (nobody know)
goto_MENU
Normal way to access to the Menu is touching the three dots icon image at the top of the main screen...(Left to the App icon) but this is not the only way... there are some devices where you can configure the way to show the Menu... for example, my xiaomi has an option in settings to configure the buttons shortcuts, and I'm actually using the three bars button as a menĂş button when I touch&hold it
Items on the Menu are self explanatories.
_SETTINGS
Buff, so many options here, but look, seems that they are separated with headers...
At this POINT : If you have problems with your Settings or you want to restore them, You only need to create (with your favourite File Manager) a file or directory named "flag_restore_settings" in App SHOWS directory
With "flag_restore_show" you will leave your workspace cleaned with a default show
These files or directories will be auto-deleted after next App start
_Settings.NET
This must be your first stop if you start the App from the very beginning
Be attention at the Art-net Broadcast / Unicast address because by default is : 2.255.255.255
In a normal ArtNet Network this will work without problems, because ArtNet uses this IP range, but if you are using your own Network (Maybe using your old internet provider router, or similar) you will need to change Broadcast/Unicast address to something in Range with your system.
You can always use the standard Broadcast address 255.255.255.255 or try to find your Node using the Self explanatory button on the Right.
AT THIS POINT:
- Is strongly recommended that you use Node IP address in front of the Global Broadcast Address, specially if you pretend to use more that one universe at once. Otherways stucked or delayed signal can appears depends of your Network configuration.
Select your favorite Node or CLick on GLOBAL BROADCAST to use 255.255.255.255 broadcast address
Special attention at the Universes Address when you select a Node from the NOde List because Addresses will change accordingly to the settings of your node. This point is important to check because there are cases where a single Universe node sends the same Address for all 4 outputs and , if you have all 4 outputs enableds... well, you will start the armageddon ;) ,... not really, but you will send different information to the node for the same Address
IF you are using sACN just leave the TextBox blank because this protocol uses Multicast address and you really don't need to know the IP server, but just in case that you want to directly connect with your node (UNICAST) you can write your node IP in the sACN TextBox
A, B, C, D Represents the outputs of the App, so we will have 4 available Outputs (at the moment)... it means 2048 DMX channels or 4 Universes.
By default, just the first Output is enabled and using ArtNet protocol at:
Net 0 Universe 0
It's a good practice Enable just the Outputs that we really needs, because the App will has less work to process and more speeder will be ( Also less battery Drain ) .
Here You can change the functionality (ArtNet/sACN) of the output and the Universe to use (from 0-0 to 127-255 for ArtNet3 , and from 1 to 63999 for sACN)
At this point, with ArtNet2 NODES, you will need to translate the address to ArtNet3,
examples:
- ArtNet2 0-0 > ArtNet3 0-0
- ArtNet2 0-1 > ArtNet3 0-1
- ArtNet2 0-2 > ArtNet3 0-2
- ArtNet2 0-15 > ArtNet3 0-15
- ArtNet2 1-0 > ArtNet3 0-16
- ArtNet2 1-1 > ArtNet3 0-17
- ArtNet2 15-15* > ArtNet3 0-255
*In Artnet2 numbers > 9 sometimes are represented in HEX ...so 15-15 must be F-F
This is because ArtNet 2 only support 255 Univers Addresses and ArtNet3 32767
_Settings.DISPLAY
In this section we can control the visual aspects of the App
All changes in this section will need to restart the App...
At this point (There are some devices where restart doesn't work,s or not always works, This is a know issue and I'm working on it... if your device doesn't restart... simple restart by yourself)
- Channels : The number of channels that can be showed in your screen, it will depends of your screen resolution and your desired faders size. (Not Scrollable). At this point... this is not the number of channels used by the App ... this is just the number of channels showed per page (app will calculate the number of page needed in order to show all 512 channels by Univers). Leave at 12 CH until you see exactly what it means.
- Subs/Cuelists/PlayBacks : Number of elements that you want to use [MIN 1 MAX 99 for each one]... but be prudent, and set it in concordance with your hardware (remember... more items, more work and less performance) (Scrollable)
- Presets : Number of Presets that you will use [MIN 0 / MAX 99] (Scrollable)
Screen Always ON : With this option screen will always be ON
Full Screen: This option hide the status bar on some devices in order to maximize the space that App needs
Light Theme: To change the Normal Dark Theme to a new Light Theme very useful in theaters as a complement of your head light during focus sessions in order to bring light to plots, notes, etc... and in exteriors for better contrast under the Sun
Tablet Mode: This option will start the App in Tablet mode
If you have a mobile device, you will need to change Fader Size and Text Size to 0.8 or similar ... try at yourself
Channel ZOOM : With this option the size of channels will expand when you touch them
Channels in % : By default App show you the levels on channels from 0 to 255,... with this option enabled you will have it in % from 0 to Full
Fader Size Multiplier : Multiplier Factor for the size of objects in this app [recommended from 0.8 to 1.5]... you can adjust this size as your needs with values like 1.348 or similar... try as your way
Text Size Multiplier : Same as Fader Size applied to TextSIze [recommended from 0.8 to 1.4]
_Settings.PERFORM
This Part is just to adjust the Outputs of the App, change only if you have issues like flickering or similar.
Continuous Broadcast : Disabled by default to save battery... you must activate it if you don't want to lose single packets due to inherent UDP transfer protocol associated to Artnet / sACN or because your node need it.
Limit dmx output : Set it only if you need to limit dmx packet size.
Certain dimmers run erratic if you don't limit dmx packet size. (This setting will be applied to all universes outputs)
Frames/sec : Change at your own... default and recommended is 40fps (same as DMX)
More fps = more accurate dmx response = better device needed
Less fps = less accurate dmx response = less powerful device needed
AT this POINT:
- If you are experienced issues with delays or stucks , first, be sure that you are not using the Global Broadcast Address (use in front of this the Node IP) and second, try to change Frames/sec to 30 or 25 Frames/sec
_Settings.OTHER
NumPAD RPN Mode : Check it to use Reverse Polish Notation
Uncheck it if you prefer to use Standard notation.
RPN: 2 CH 80 (LVL)
STD: CH 2 (LVL) 80 ENTER
When DMX-IN Enabled Univ D Controls Executors: On Check, App uses values captured via Output D (when DMX IN is enabled ) to control Executors following the next map (that you can always view clicking on View Map Button) :
DMX IN Ch [EXECUTOR]
1-99 [Subs 1-99]
101-199 [PB's 1-99] trigger >50%
201-299 [Cuelist 1-99 Fader]
301-399 [Cuelist 1-99 GO] trigger >50%
401-499 [Presets 1-99] trigger > 50%
501 [Grand Master]
502 [SUBS Master]
503 [Clear] trigger > 50%
504 [Release PB's] trigger > 50%
Accuracy control on faders : With this option, fader levels on SUBS/CUELIST/GRANDMASTER never will change directly from one value to another. They will change progressly following their natural movement
Enable MIDI IN: Activate the MIDI module that you can configure next on MENU > OPTIONS. Due to compatibility reasons , this part only will works with Android 6 and above.
An OTG adapter and one USB Midi controller will be required
At this point:
- The diversity in Android's ecosystem do that not all USB midi controllers works with all devices... it depends of the final implementation that Manufacturer do with the public libraries embedded in Android 6 and above.... for example, my Behringer BCF2000 doesn't work with my Samsung Tablet, but works perfectly with my Xiaomi Phone (both with the same Android 9). If your MIDI controller works with other Android MIDI programs that you can find in Google Play, also will works with Art-Net Controller. About Behringer BCF2000 you need to work with it in U1 mode (EDIT+STORE and move first encoder until U1 , then EXIT)
Enable Initial MACROS : Activates Initial macros that you can configure in MENU > OPTIONS. Every time that you start the application, the macro will starts to play the steps of the macro sequentially.
This Macro can be from 1 to unlimited numbers of steps and will be explained later in _OPTIONS
Auto START/STOP
If you enable for first time Schedule Start or Stop, system will ask you for OVERLAY PERMISSION. this permission is required in order to start the app at time no matter what are device doing at this moment
Schedule Start: Activate the Auto-Start Service at the time that you want . This will start the application. 24h format
Schedule Stop: Activate the Auto-Stop Service at the time that you want . This will shutdown the application. 24h format
Auto Start and Auto Stop are both independents , so you can just Start the application without auto Stop or you can Stop without previously auto start
Daily Repeat : to repeat Auto Start/Stop every day at the same time
Once you are configured Auto Start /Stop you will see a little icon in status bar remembering you that app is ready to start or stop or both
Also you will see a permanent notification in notification bar with automatization details
At this Point: IMPORTANT
Required Button: This button is just to remember you that some requirements are needed in order to Start the program from an Android Background process....
Extracted from the program:
"Device manufacturers don't like apps or services that drain battery running processes in background. Vendors like Samsung, Xiaomi, Huawei, Nokia, etc... modify their Android versions (MIUI, EMUI, ONE UI etc... ) with some sort of battery optimizer, memory cleaners or complementary permissions. Developers can't face all the possibilities and combinations because they scape of google rules and change in every model and every update... Anyway, if you want to use the scheduler part of this app you will need to grant that none internal process kills the scheduler service. To do it I leave here one link (100% applicable to the scheduler part of this app) where you can search the way to prevent this issue for your particular device... if you need more information googling "Don't kill my app" can give you some extra tricks
In Battery Optimizer you need to NOT ALLOW battery optimizer for Art-Net Controller
In Android App Setting you have a quick access to individual app settings where you can give permissions"
This is the Link (very impressive Alarm application that never fail me)
and also if you want Don't Kill my App
Finally I leave here 2 screen captures of my configuration in my Xiaomi (AutoStart is also required in some devices to re-enable the service because system clear all alarms after boot)
_FILES
Here you can manage your shows
Move OLD shows is just an option to import shows that you has stored in the hidden system part that was used by R09 and before. So you will only use it one time or probably never... but here it is
Shows are compatibles between all versions since r08 in both directions and all with work with each other, but you will reduce functions in the way that you trying to load shows created with a major number of version into an app with minor version number, of course. For example if you try to load a show created with R10 in R08, shapes generator will not work.
LOAD : It will Load the selected SHOW
Selected SHOW is the show that you can see in the TEXTBOX (White field)
SAVE : This will Save the selected SHOW , if it exist, it will be Overwritted , Change the name as you want in the TEXTBOX to Save a new one.
DELETE : This will delete the selected SHOW
SHARE : With this option you will share with other apps or devices the Selected SHOW.
At this point: Everytime you press Share Button, a compressed copy of your selected SHow will be created in App SHARES folder , you can then share or not the show, but the compressed copy will remain in this folder , for future actions or for your own access.
As in LOAD button, you can share your show with another versions of the App.
Compressed files created with Share has "*.SHOW.ZIP" extension and, as you suspect, is in fact a ZIP file with all the necessarily content for the show.
LOAD SHARE : This will open a minimalistic file explorer to search downloaded SHOWS thru your device folders.
This tool only will open files with extension "*.SHOW.ZIP".
at this point: remember that in R09 you saved your shares in
/sdcard/Art_net_Controller_SHOWS/
if you want to load some of your OLD shows that you shared before maybe this tool can help you to try to import one of this old shows.
When you click on one compatible file [*.show.zip] App will LOAD the SHOW into the program and will SAVE it at once.
If a show with same name exist in SHOWS folder, it will be overwritten.
New / Wipe All : This option will clean all the Workspace, clear all the memories and patched fixtures. It is the best option in order to start a new Show
you can make a New / Wipe All creating a file or directory called "flag_restore_show" in App SHOWS directory
This file or directory will be auto-deleted after next App start
_PATCH
A priori, You don't need to patch nothing if you only will play with conventional lights.
Program could work with or without patching, but if you want to take advantage to the use of shape generator, repatch or grouping tools, I recommend you to patch conventional lights as Dimmer fixture using the predefined library Dimmer_LX.D4
By Default, all 512 channels works as HTP Channels (Highest take precedence).
Only if you Patch one Fixture, you will work with some parameters as LTP (Last take precedence) and 16bits resolution on parameters that need it.
Create Libs : This button will create or recreate the libraries used by this program in FIXTURES app folder. It will take 240MB of your storage and about 2 minutes. Feel free to consult, modify or expand them as you need.
In fact libraries are based and compatible with Avolites D4 files so you can learn more about them in :
https://personalities.avolites.com/
Avolites has also a free Personality Builder v3.1 that you can use to create new libraries in an easy way (login required) in https://www.avolites.com/software/latest-version
Once you are created the Libraries press LIB in order to search one of them
Search your fixture using the TEXTBOX. you can start to write the manufacturer, then the fixture or whatever you want to reduce the search.
Then Click in your fixture.
If all needed information is ok, library will be loaded to the program
SELECT THE MODE : Under de LIB button you can select the fixture mode.
OUTPUT /Address / NUMBER OF FIXTURES/ ID and COLOR : Finally you only need to define the Output (a,b,c,d), the start address of your first fixture, the number of fixtures that you want to patch, the ID number (It will be the reference for this fixture and also the order that will be showed in fixture tool) and choice a color (if you want) for this fixture/s
All this information can be then changed in Edit Patch WIndow
PATCH IT : I don't remember what this button do... is very big so something important for sure
Once fixtures has been patched you will see them on "Patched Fixtures" SelectBox sorteds by patch order
from here you can UnPATCH iT one by one
Wipe PATCH : Clean all the patch . This is not the same as FILES>WIPE ALL, because this process (also Unpatch_iT ) take care of all cues, and presets and leave the information recorded but not related to Unpatched fixtures themself. Because of this, process can take some time and will depends of number of cues and presets recorded, and of course the performance of your device.
_patch.EDITPATCH
Inside the Edit Patch matrix we have all the fixture patched in the application, here we can change the ID, the name of the fixture, the color of this fixture and the address..., but more important thing is that we can do it with blocks of fixtures....
When you select a group of fixtures, not only you can Unpatch this group of fixtures, you can change their properties in block just changing the first one and then pressing the i-Change Selected Button. the rest of the selected buttons will change following the first one... name will be the same (and this is important, because groups for the same fixture will be automatically created).
Also the addresses will change following the offset of the fixtures and selected order.
The top Right button has double functionality , when you touch all selected fixture change to Unselected and Unselected to Selected. When hold down the button (Touch&hold) all fixtures going to be Unselected.
In the next video you can see how to patch and use Edit Patch.
_patch.RDM
RDM work only thru Art-Net Protocol (not sACN), taking advantage of ArtDMX packets.
Here you will see all RDM compatible fixtures connected to the system as long as your node can be able to work with RDM thru its dmx output..
Art-TOD data packet will be asked to the node at the beginning. You can always ask to node for another Art-TOD data packet using the top right button of the windows, if you see that received information is not correctly or you want to generate another Art-TOD data ... you need to FLUSH the information and renew it , in this case hold the top right button (touch¬hold) in order to send a FlushTOD packet to the node... as fast as possible node will send you the new Art-TOD data table
The selected button of every fixture has double functionality and works the same maner as in the EditPatch, but, by default is no only a selection button, is also the LOCATION fixture button, if you want just select the fixture without locate it, you need to change button's functionallity unselecting the top left second button to Only SEL
The other three buttons of top are just to sort the list (touch&hold) to reverse the list at this sort
At bottom you will see a little fader where you can change the time between packets just in case. (Due to COVID'19 i was not able to test it consciently in real enviroment , so I leave the option for future issues)
I'm gonna leave a video here from one of the first test that I do with the RDM section... At the moment you can change all the important information of the fixture... (see PARAMS and SENSORS where available), including PAN/TILT invert, restore to default, etc... , but there are a lot of work to do in this part of the program, libraries are prepared to support RDM direct patch, and there are fixtures that will send the parameters directly to the app, but this part is not completed yet. You can start to play with it as your own way
_OPTIONS
Here is the place where you can find quick actions that could be in settings but because their frequently access is much better that they have their own space
MODE : It Can be REC or PLAY .
Basically function is to avoid accidentally delete or record during playback.
This option will be reversed at default (REC) on every restart
On PLAY mode:
REC button will be disabled on PlayBack Buttons.
REC button will be switched to FLASH on Submasters.
And finally "Action" & "Execute Action" buttons will be disabled on Cuelists.
RECORD MODE : It can be STAGE or PROGRAMMER.
With programmer (DEFAULT) only channels with values (including zero values) on the programmer will be recorder in executors
With Stage ...what you see is what you get ... all parameters will be recorded.
PLAY PB's BY : Can be Channel or Fixture.
With Channel (Default) PB's change only parameters previously recorded,
for example :
If you only have Dimmer and blue recorded in a PB for a fixture with DimRGB.
if your Fixture was at full in RED, then it will change to magenta, because PB only add Blue (also dim, but is something that previously fixture has)
with FIxture , no matter that you has only Dimmer and Blue recorded in the PB... your fixture will change to Just Blue, because App bring to zero all the other parameters that has no DIM and BLUE
CLEAR TIME : Time for clean the programmer
PRESET TIME : Is the time that presets will use to insert themselves in the programmer
_options.INITIAL MACRO
Here you can establish an initial sequence that will run every time you start this program. ONLY IF "enable initial macros" is enabled in SETTINGS.
Initial Macro also will be executed on Schedule Start, but NO when you load a show from FILES or a SHOW has been loaded from a Share Intent
INITIAL MACROS will be SAVED BY SHOW
Options here are self explanatories but basically you can add a new line on the macro stack with NEW Button or delete them with DEL (Touch Del Button, and then Touch the ID number of the line that you want to delete).
In every line you can select the executor TYPE that you want to play (SUBS, PB's, CUELIST) or a special type named DO_NOTHING to do .... exactly! ...nothing , just wait x seconds.
Every line will be executed sequentially only if the previously one has been completed.
All times are in seconds.
The Command order for every executor will be following this rules:
For Cuelists :
- GO
- Fade in (Following Fade Time)
- Wait (Following Wait Time)
- Fade Out (Following Fade Time)*
- Release*
For Subs
- Fade in (Following Fade Time)
- Wait (Following Wait Time)
- Fade Out (Following Fade Time)*
For PB's
- Instant Execute
- Wait (Following Wait Time)
- Instant Release PB*
DO_NOTHING
- Wait Time
*Execute only if Keep is NOT Selected
PB's has no fade in/out because you can control fade in and release fade directly from PB itselfs.
At this point: You can TEST your INIT MACRO holding down the MENU (3 dots icon at top left) and also stop it following the same way.
If you need to execute a complete cuelist stack at the beginning you can create a macro with just one line with your desired Cuelist and mark keep button as selected . Then make the magic with AUTO GO in the cuelist itselfs
if you repeat a line with same values for example Cuelist -1 (if no release was executed in previously one [keep is marked] ) a GO will be invoked and next cue will be executed.
ONLY in MACRO, When a Release is invoked in a Cuelist [it means that Keep is NOT selected], Cuelist stack will be reset to the first CUE (normally CUE 0). This can be useful in order to repeat same cuelist stack in other steps.
Also think, that when you do a release, it will be executed with the internal cue fade out time, so if you want to repeat the same cuelist in the next macro step, you must insert between these two steps a DO_NOTHING step to leave time for the last release
_options.MIDI
This option only will works if you have a device with Android 6 or above.
Remember to CHECK "enable midi in" in Settings.
FIrst you need to select the MIDI port that you will use. (You must do this every time that you connect or disconnect your midi device or you restart the application)
Then you must Map your midi device to the App executors (You only need to do this the first time that you connect your MIDI device)
This MIDI MAP will remain independently to the shows or "wipes"
Here you have all Executors that can be mapped in the program, following the number of SUbs, PB's Cuelist and PRESETS that you have configured in SETTINGS.
For every EXECUTOR you have one or more triggers
SUBS > FADER - FLASH
PB's > BUTTON
CUELIST > FADER - GO
RELEASE - ACTION
PRESET > BUTTON
G.MASTER> FADER
S.MASTER> FADER
CLEAR > BUTTON
RELEASE PB > BUTTON
REC PB > BUTTON
To Map one button or fader, just move the fader or touch the button that you want to map in your midi controller , then look at the top left to see that this button or fader is catched by your device . If no response, be sure that you has your midi port selected or Enable midi IN is selected in Settings.
If you see the message sended by your midi device, you only need to assign to the executor that you want.
Use the button at the left of the textbox to do this.
To delete simply write 0 in the textbox or EXIT and ENTER to the midi MAP and with the three dots "..." in the top left, assign where you want to delete.
AT THIS POINT: By default, and just in case of NoteON/NoteOff , Note ON will be choiced.
If you really want to use NoteOff to trigger a button, you only need to write the decimal number that you see , between brackets in the top left.
You can, if you want, Map more than one executor with the same Midi control.
_DMX_TEST
This part is just a tool to quick view the main outputs of the app. Here also you can test in a quick way your channels at a predefined level.
First Select the Output port. (A,B,C,D)
Touch "+" button to start test on DMX Channel 1
Test always start at 80% in order to take care of the lamps, but can be changed easily moving the bottom fader.
Use Button "+" to increase channel
Button "-" to decrease channel
If you hold + or - buttons, the selected channel will increase o decrease automatically.
If you want to Jump to a concrete dmx channel, > Touch Ready > Write desired channel (or use + -) > finally Touch "..."
DMX Test send values directly to the Programmer and override their actual values
_FIRST_visual
The visual distribution of this app is pretty basic.
A main top row with a Menu, a multipurpose ICON, the Grand Master , the Clear Button, a row of presets and the tab section with the Programmer, Keyboard, Subs, Cuelist and Playbacks
in Tablet mode, also you will see the SUBS Master fader and only two tabs sections PROG and RUN
_PHILOSOPHY
This App works with 2 type of channels:
HTP and LTP channels
HTP (Highest Take Priority) is used by Dimmer Parameter or NON patched channels. These Channels will be processed by the main thread and the highest value will be sended to the output. Only exception is the programmer that take all the priority and no matter what value is more highest in this particular case.
LTP (Last Take Priority) is used for all fixture parameters that are not DIMMER. These Channels will be sended to the output in the way that they change their values without take care of their own levels
EXECUTORS follows the same philosophy: Last executor played is the executor that control the channel, Except if this executor is a Submaster with "LTP Instant fade" unselected (see below) or Channels involved are HTP channels which follows the HTP priority
MENU: Show the MENU (already Described) and ,when hold it, starts the initial MACRO TEST
ICON_APP : When Touch Starts the Fixture TOOL , when hold it Start the DMX-IN server
Control LEDS: Quick way to see what you are sending to the main output and from where
- Green (Programmer)
- Yellow (Submasters)
- Orange (Cuelists)
- Red (Playbacks)
Grand Master: It controls the Main output of all HTP channels of the app
SUBS Master: This control the level of all the enabled submasters of the app (only available in Tablet mode)
CLEAR: To clear the programmer. When Hold you will RELEASE (without time) all the PB's
This Button also will change to UNSEL when one or more fixtures has been selected.
Then First touch will Unselect all selected fixtures and second touch will Clear the programmer
_Programmer
Programmer (Prog) is the heart of the app, taking the philosophy from the major consoles of the market, it's the place where you can change or add values that later will be recorded as a cues or presets.
The values of the programmer take the highest priority over other values, even when you set values to zero .
You will notice that a value is in the programmer because level color is boldered and a little green bar appear in the app icon.
for example : In the top image channels 1,2 and 7 are in the programmer, notice that ch 2 has value zero, but is actually in the programmer so this value will be also recorded.
Touch the CLEAR Button to clear the Programmer.
Or if you need to clear just a particular channel, Touch the number of this channel and its value will be cleared.
To move around all 512 channels of the 4 universes that this app can control, you need to use the navigation bar in the first row of the programmer.
Select the Universe (second button) and then move around the pages of channels using the + or - button or selecting the desired page with the selector of the right.
You also can scroll upon channels values to move up and down from the pages
_Prog_MULTI_Select
The First Button labeled "Simple" is named the Multi- Select Button
This Button is a god way to select multiple channels at once
Touch and Hold to configure it
By default Multi-Select is configured BY COLOR, it means that all channels with same color will be changed at once changing only one of this channels (except fader with default color for obviously reasons*)
*This is not exactly, if you uncheck Exclude default color you can change all 2048 channels at once (Be careful with this , specially in conventional environments)
When you uncheck "Multi-Select by Fader color" you are using Multi-Select at the normal way, and you need to set Buttons Every and By
Every is the channels that you jump to the next fader (or if you prefer, number of channels that your fixture has... in dimmers channels only one, for example)
By is the number of times that you want to repeat this jump (or if you prefer, the number of fixture that you want to control)
For example, next image has multi-select in 3/4 so this takes control of 4 channels every 3 channels or "Jump 3 and repeat this 4 times"
Are you thinking that this is completely crazy?... ok I agree... but you must think that this tool was make before the fixture tool (R05) and this was the best way to control RGB panels or move around PARS bars and Harting / Socapex installations. And now, if you don't want to lose time patching some Chinese-impossible-to-know-PAR-LED , but you know how many channels it has, it can be a great tool to test/rec a huge quantity of them, or maybe to test/rec RGB panels
_Prog_Labels&Colors
You can add a label or change the color of every channel in the programmer, except if this channel is part of one Fixture that is already patched
You can change them individually or by groups
To do this, touch&hold the number of the channel that you want to change
Following with the last example, I'm gonna Label these 4 channels as a Chinese RED and I will change the fader color also.... because all these channels are now at the same level, I can use "Apply to all with same LEVEL" and all the channels will change at once
This way I can change color & labels easily with just a few touches Thanks to Multi-Select
Once Color has been changed in a channel option "Apply to all with same color" is enabled giving you the option to change easily the label or the color of this group.
Also then,if you want, you can change Multi-Select to their default configuration : "BY_COLOR"
_PRESETS
Also named Palettes or Preset Focus . Basically is a quick copy of the content of the programmer that you can fast call to load in the programmer.
You can see them in the main screen of the app or in the fixture tool and can be horizontal scrolled
The main goal of the presets is that when you record your cues based on the content of a preset, you only need to change the preset content in order to change the cue itselfs.
This is particular useful when you program with complex fixtures and you have a lot of cues recorded , because if something changes from your initial plans you only need to change a few presets in front of update every cue that you was recorded. Think in a case where your favourite guitarist change his position 2 meters back in the last minute because he is at the beginning of a collapse by panic scene ... well, if you was recorded your cues based on presets, you only will need to change your "mega solo big bang supernova" preset and all the cues involved will change at once
To record a preset , you only need to touch de desired preset... if there is something in the programmer or a shape fx is running the preset will be recorded.
You can record values from patched fixtures or just channels , also you can record shapes fx in your presets.
Zero values that has in the programmer also will be recorded , so if you don't want to record these values, you will need to clear them (touch channel number in the programmer or touch&hold x2 the label of the parameter in fixture tool)
To call a preset, just press the preset and all its content will be loaded in the programmer
Channels involved will change their color to the color of the preset and label also will change with a P(number of preset)*.
*See first image of this part
important
If you call a preset with just a Shape FX you will see the contourn of the channel with the color of this preset, but no the channel itself, this is because Shapes are not exactly in the programmer (note that you can not clear Shapes touching on channel label, and also you don't see boldered values and the green little bar under the app icon). You only can clear a shape using CLEAR button or Touch & Hold "CLEAR Sel" in fixture tool.
More about Shape will be explained later
If you Touch & Hold the preset you will go to the Preset properties where you can change some visual aspects of it, Update, merge or clean the preset.
In honor of all the time that some of us lost drawing some artistic interpretation of our presets, I leave opened here the possibility of using Emojis ;)
APPLY is just for save the visual feel of the preset, NOT for the content itself.
UPDATE Update the content of the preset with the content of the programmer. This will override the content of the preset with the new information.
MERGE This option will merge new information to the preset, or if information already exists, it will be upgraded to the new values
CLEAN Clean all the content of the preset leaving it without content. This option doesn't clean the links to the cues based on this preset so you can re-create the preset with all the links intact
At this point.
When you call a preset to the programmer, if some channel of this preset is part of a patched fixture , this fixture will be selected and Clear button will change to Unsel.
At this moment (r10.2) is not possible to call a preset just for one fixture that is part of this preset. When you call a preset it simply goes to the programmer without more.. so, if you need to clear one or more fixtures from the programmer after a preset call, you need to select the fixtures that you don't want in the fixture tool and pres "CLEAR SEL".
_EXECUTORS
This App has 3 types of executors that you can use to play your show. The way to play with them depends on the person.
_executor_SUBS
This type of executor has no fade in/out time. You must adjust this on the go.
For more accuracy control of them, you can change "Accuracy control on faders" in _SETTINGS
To record one of them, only set something in the programmer and touch the REC button at the right of every fader.
Fader will activate and raises to full ready to take the output control once you press CLEAR
To Update a Sub with new information just repeat the steps to record it
If you want to delete one of them, You need to CLEAR the programmer and then press REC. (An Alert will advise you before perform this action)
To LOAD the content of one SUB to the programmer , Touch & Hold REC button
By default all LTP parameters will be played instantaneous and only HTP (dimmer) parameters will follows the fader value
You can change this for every subs unselecting "LTP instant fade" in Sub parameters (see below)
If other Executors claim the control over one of this LTP parameters, the sub need to be reloaded (raise to zero and restart) in order to claim the control over this parameter (Remember the LTP philosophy over executors)
If you record some Shape FX in SUBS this Shape will increase its Size and Speed following the Sub level until its recorded state when fader raise to full.
You can Change the color and the label of every Submaster ... to do it, just touch and hold the number of the SUB that you want to change
Here you can Label your Submaster and also set a color (no emojis here ;)
If you need that your Sub plays LTP parameters following the fader value , UNCHECK "LTP Instant fade".
UNCHECK This option acts approx. as a MODE 2 in Avolites or TEMP_fader in Ma
WHen you raise a sub with UNCHECKED "LTP instant" to zero, LTP parameter's control will return to last Executor that had control previously
Finally if you change in OPTIONS the mode to PLAY, REC button will changes to FLASH and then you will be ready for ROCK'n'ROLL !!!