Davidmk
-
Posts
332 -
Joined
-
Last visited
-
Days Won
26
Posts posted by Davidmk
-
-
The error ocurred during start up. Had to power cycle to get the desk up. Requested files will be in the mail shortly.
-
Had a problem when I started up my desk yesterday. Debug file attached.Switched off & back on, saved the debug file and the desk behaved for the rest of the evening. Startup show file & screenshots available if required.
-
In order of priority (to me)...
High - Faders screen able to display any playback page, not just the one selected on the main desk. I use a wing (obviously not on the same page as the main desk) plus a midi keypad to fire playbacks on yet another page - very annoying being unable to see these without changing pages on the main desk (I always forget to change back for one thing). If view+page up/down or view+cursor left/right (or up/down) aren't doing anything then they might be ways to select the page (sorry FLX-S users) but I expect you'll think of something.
Medium - Midi notes/cues. As it stands this operates on the currently viewed playback. Would it be possible to add an option in setup to select a particular playback instead. "Currently viewed" is just too vague for my purposes.
Low - I've had the occasional problem when I have inadvertently hit channels/playback, page up or page down. Might be nice to have a way to lock these (press and hold for a number of seconds maybe).
-
Hi Tristan.
If you are still looking, I sent my number by PM.
-
(This is all assuming I have the right manual of course 🙂)
-
It probably comes up as strobe under beam parameters. Try setting it to 255 or 100%. Refer to the fixture manual to see why.
-
No expert on this fixture but have a look at what value ch7 is set to. A common trap (with non-LEDs) is that the shutter has to be set to something non-zero for any light to come out. Some LED fixtures seem to emulate this behaviour. You will also need one or more of the RGBW channels to be non-zero but I suspect you've thought of that.
-
Old Frog user. I used a key fob remote and receiver, set up a cue for each fixture then used the key fob to step through them when focusing. It was a three button fob so I used one as "shift" to get four options... reset to 1st spot cue, reset to 1st wash cue, next cue and previous cue. Saved a lot of walking along the catwalks. Not necessary now, with the remote app.
-
I'm guessing Edward"s reply will reference the fact that other desks can only have 6 remote switches.
-
That is useful to know. Thanks. Not quite as useful as a direct button on the console but great if your soldering proves to be unreliable mid show.
-
Suggestion for a lower tech alternative to that described in "FLX Remote Button Box - PCB Layout By jw-lighting, July 3, 2015"
-
Worked out the cue editing problem. My cues don't have any intensity information (this is delberate), they do have colour parameter information so it makes no sense to edit the cue fade, it does make sense to edit the colour fade. When I selected the colour fade time I could edit it, no problem. Now my colours fade in but they mix with the colours already there rather than replacing them.
Suggestions welcome but I'm going to look at what I tagged when I recorded the cue and also whether it is doing HTP or LTP. I'll keep you posted on that.
I had another, vaguely related, problem with colours in my gig this evening - I have a number of playbacks set up for colour mixing. After taking the Red playback to zero I found the actual level remained high. I had a similar problem with blue a bit later. Viewing the cue on screen with "source" selected showed it was the relevant colour playback even though the fader was at zero. Manually releasing the playback solved the issue (but did cause a sudden colour change on stage). Not sure what I did that led up to it and once I'd released the playback it all worked normally and didn't happen again.
So, lots for me to work out before my next gig. 🙂
-
Thanks Edward
My main purpose for using midi notes is to change colours on my LED fixtures when busking. Ideally each change would cross fade with whatever is there already and, when released, cross fade back to the (unreleased) original state. It is these two aspects that I am experimenting with at the moment.
I have something similar going on with UDK's for moving head positions although they do seem to snap off rather than fade (which is good enough for positions for the time being - I can look at that again later).
I'm fairly new to FLX and Zero OS so I'm probably doing it all wrong but...
- Note velocity seems to make no difference at all. It's not what I really want anyway, just saying.
- Playback fade times don't seem to make any difference either.
- Cue fade times might be the answer but I can't seem to edit times on existing cues making experimentation rather a drag.
-
Thought I had already uploaded this but coming back to the forum I saw no trace of my reply so trying again.
Attached notes describe what I am trying to achieve myself, how far I've got and how I've done it. If it works for you then perhaps we could collaborate on the rest. Of course it would be if the Zero 88 people take an interest, perhaps to correct what I've put or to fill in the gaps maybe even to help with the rest of it.
-
Hi
I'm trying to get Midi Notes working and I've got as far as being able to trigger the play backs I want. I'll get my desk out, check how I get that working and get back to you. Give me an hour or two.
-
Little thing I noticed on the DMX display on my FLX
I'm probably the only person on the planet who has fixtures patched on U2 but not on U1. After upgrading to 7.9.5 and loading my saved show file I went off to play with remote switches and Midi notes. As I was working from home, with no physical rig to see if things were working, I switched to the DMX output screen. Imagine my dissapointment to find that not only was it displaying U1, there was no button to switch to U2. (I did read the release notes, I was expecting to see U2 and only U2.)
You'll be pleased to hear that, by patching a single dimmer channel on U1, the U2 button appeared and I could see my outputs so anyone else affected should be able to use thatvwork-round.
-
15 hours ago, Edward- Z88 said:
Hi David,
On FLX you can still do this if you wish, but also apply a fade time using Programmer Time.
Correct, FLX will allow you to output a single cue from each playback at a time. If however there were 2 cues in a playback you wanted to output at the same time, you could make a copy of this playback, to allow the original to output one of the cues and the copy to output the other.
Programmer Time is commonly used for busking, and in conjunction will speed faders for effect rates there are many different ways to configure the console to busk. There’s more information on Programmer Time here...
http://support.zero88.com/1011402011
All cues have the ability to trigger macros. Therefore to trigger macros via MIDI, you could program a blank cue with a macro trigger, that can then be triggered via MIDI / close-contact triggers.
Hope this helps, let me know if you have any queries.
Edward
Aha!! Macros in cues - that's the thing I'd seen in the manual but forgot, of course they can!! Thanks for the reminder. Can't wait for my desk to arrive now.
-
Thanks Edward. I'll give this some thought while I wait for my FLX to be delivered. The Congo Jnr I have to endure on a regular basis has 40 PB faders and I try to avoid paging but I can select movers & trigger palettes on the screen with a mouse which is a bit clunky and doesn't provide a fade time. I'm guessing the FLX won't let me execute more than one cue from the master PB at the same time (why would it after all) but with Load and Go commands I should get part way to what I want. There's also master fade time and selecting groups/palettes from the screen to explore. I'm confident I'll find a way to busk that will suit me - especially with the promised midi notes in the next OS version. Never been dissapointed by Zero 88 yet 😊.
The wing is a possibility but the additional expense is probably too much.
Just a thought... If you could trigger macros with Midi you'd get more flexibility. I'm sure you've thought of that yourselves but maybe one day???
-
You never forget your first love and, discounting flirting with resistance dimmers and a later dalliance with Strand Mini 2's, that would make mine a Sirius (then, later, a Bullfrog until my main venue replaced it). With that in mind I'm pleased to say that I have just ordered my very own FLX.
Now, until/unless a button wing becomes available, I'm hoping to use a Midi controller instead but, despite searching the website, support FAQS and everything Google has returned elsewhere, I can't find any detailed information about what you can trigger with Midi show control and what Midi commands you'd use to do it. I get that a controller with Midi DIN output or a good quality USB to Midi link is needed but the little other information I've found is sparse and contradictory. I know there are UDK's and I have plans for them as well as for the remote input socket and I will be using a touch screen and probably a tablet as well but there's no substitute in my mind for physical controls when you want a colour change or a can-can in a hurry. (Mostly I light bands and have to busk.)
Is there anything out there already? Could something be put together and published? (I'm pretty sure I'm not the only one looking for it.). Ideally a full description so I can see the possibilities rather than suggestions for the specific examples above.
FLX Startup issue
in FLX
Posted
Files sent
The start up was in progress then the screens in the snap shots came up and start up halted.