Thanks for the responses - much appreciated. Sorry for the delay coming back. To answer a couple of your questions..
- I was using 7.9.4 (Which I think is latest version)
- Re. outputs, I was getting no data received on the dimmers until I set an output to universe 1, however I hadn't patched anything at this time so maybe the output wasn't initialised? It was slightly confusing behavior though
Could you elaborate a little on where you find this is an issue? In the Fixture Schedule, using arrow keys you can see what cell is highlighted by the blue cell.
I am used to working in command line, so patching with the keyboard as far as possible. I found the workflow on FLX which seemed best for me was:
- Open to the patch window (after creating all the fixtures I want)
- Tap on the address column, this might cause a window to open but I clear that
- Type the channel I want to patch, press enter - the patch detail window for that channel appears
- Add the DMX address etc
- Press enter
- Confirm over-patching if necessary
- This returns me to the normal patch view, I now have to press clear, as if I type a second channel number without pressing clear I will edit two channels (however the window doesn't tell me this so i can make lots of mistakes!)
Could you elaborate a little on this? When doing this you will simply need to move the faders to the level the playbacks are currently at (shown in the MFF window), and the faders will then re-gain control of the playbacks. We call this level-matching.
It seemed to me that when I changed between the two the output would jump to the current fader positions in a non-nice way (level matching is what I would expect to happen), I would need to get back to the desk to check I wasn't imagining things
I'm not sure I understand what you mean here, could you expand a little? There is a new version of the iOS apps coming soon which greatly improves connectivity, and provides support for Apple Watch.
When you press a key, the button is rendered as down (highlighted) and when you remove your finger it should re-render to the normal state. What I found happening regularly (maybe due to bad wifi?) was that my release of the button was missed, so the button would remain pressed. If I wanted to use that button again I would need to press it so it logged a key-up before I could use it again
The thought behind the Remote is that any time you try to connect to the console from any device you will require the password. You can disable the password in SETUP -> Remote, if you wish, which in most cases still provides sufficient security as the wireless network password is required to connect your device in the first place.
This is just annoying though - once I know the password then I should be able to save it so I can quickly re-connect to the desk. I see no benefit to forcing it to be typed every time.
Pressing SETUP will take you out of Setup, as long as you aren't in a separate window within the console Setup. The HOME key is purely used to Home fixtures or program defaults and max levels, rather than being used to access a "Home screen".
So this is where I think the physical button layout is confusing - to me, the buttons surrounding the screen appear to be buttons that change the view - which some of them do (and their light lights up to reflect the view, hence the weirdness when the lights go out) - I would expect the home button to be near the programming keys. Obviously these buttons are now rather set in stone and I'm sure I would get used to them in time!
Do you remember whether any front panel buttons were lit, or did it just seem that the buttons were unresponsive? If this happens again, please let me know.
Has been fine since - all the buttons were off, although the 8 segment button for fader pages did its cycle on power up so was connected to something
There are a few other comments I have since using the desk a bit more..
- It would be great to have a list of used fixtures/favorite fixtures when adding new ones - I found it very boring to have to search for a fixture every time I wanted to add one. Ideally the "show" fixtures and maybe bookmarked fixtures would be in a list
- Similarly, it would be great to be able to search all fixtures (from all manufacturers) in the middle column when you haven't specified a manufacturer - that way if you know the model name you can miss a step of having to find the manufacturer first
- I found update annoying. In my mind update should only put the captured (red) channels into the target, however it seems to take the console output. This meant that in my use (an exhibition whit a playback for each area) I had to take other areas to blackout in order to record or update a specific playback
- I found it a little confusing when selecting a colour palette for a unit that wasn't in that palette (as there was no error to see when it wasn't a relevant palette) - maybe this is just me
- I found entering real time confusing in that I am used to being about to type 220000 and a console automatically formatting it to 22:00:00 - Jon Hole kindly pointed me in the right direction of adding decimal points to format appropriately
- I'm not a massive fan of the long command line - I found it hard to tell what I had just typed, and I feel at the least the "enter" command (or assumed enter after commands such as @@) should insert a more obvious block than just a comma.
- I also would like a way of sneaking/releasing a single channel out of the programmer in both live and also in blind, I couldn't see how to remove a channel from a cue..
- Also, in blind or in live, is there a way to see the colour/other information for a channel. I usually worked in the Strand 520-esq channel view (using shift-view)
Hope these thoughts are useful! I've finished on that job now but will try and find an excuse to use an FLX again soon