johng

Been doing some more digging and will post it here lest anyone else comes by this thread. Really looks like there is an issue free-ing up and re-using memory on this desk, which is not great if you want to add/remove fixtures for different gigs and re-use the same showfile by editing it. I hope someone from Zero88 comes by and can shed some proper insight on to this. 1. I have roughly 20 fixtures (mix of movers/LED's), 10-15 position/colour/gobo palettes each and previously had 11 pages of subs each with about 20 subs set. 2. If I delete e.g. 6 complete pages of the subs I only free up a fraction of the memory - in my case only enough to make a few minor edits to the remaining subs before the desk says memory full. 3. Seems very similar issue to a thread in January 2011 "Jester ML Memory upgrade Started by Härterei, Jan 25 2011 09:00 AM" where Harterei found deleting chases didn't free up all the memory. On that thread Jon Hole reckoned he'd have to go and look more deeply at that issue, but i can't find any further responses. (Also in that thread there was discussion on ensuring you don't record all dmx in - I don't believe I'm doing that). John.

I'm modifying an existing show file to take account of some fixture changes to my rig. The memory on the desk was nearly full with the old showfile. I've deleted a bunch of subs from the old show file, then am adding the modified subs back in. The modified subs are not much different (the fixture count is roughly the same but there may be an extra step count in some chases), however I'm only half way through and the desk is now full. Does the jester have any known problems with e.g. memory becoming fragmented or are there any other steps I can take to work out what's going on. I'm actually building the show for this NYE (!) so if anyone is out there I'd appreciate any input. Can send show files if that would help. Thanks, John.

Can someone explain why color attributes are only triggered at 5% on submasters ? I find that with LED's because they're not very linear you have a visible brightness level as the submaster comes up with the wrong color (if a previous sub you used had a different colour) until the color attributes are triggered and the color change is then very noticeable. I'd like to change this behaviour - is that possible ? However I'm also thinking there must be a good reason for it being set like that which I'd like to understand as well ! Thanks, John. P.S have searched the forums and seen this behaviour mentioned before, but no explanation as to why or whether it can be changed.

Hi, I've been donated 4 Stairville MV250H moving heads. They are not dimmable but they have a shutter. Hitting Blackout on my jester24ML leaves the stairvilles still fully on/open. I'm not particularly experienced, but I'm guessing that that is because there's no dimmer channel on the fixture. What's the best way round this so Blackout closes the shutter ? (Note this will be the first fixture I've ever tried to edit...). Should I just set the default value for the shutter to closed in the fixture editor, save that and then load that in to the desk ? Or would that not work because Blackout just sets channels the desks knows as dimmer channels to zero, it doesn't set other values to their defaults ? Is there a smart way round this issue - essentially I want the darn things to go off when I hit blackout, and closing the shutter is the only way to do that ! Thanks for any help. Have searched the forum and while someone had a similar issue there was no detailed solution given. Regards, John G

Hi, I Recently got a jester24ML - so I am a novice... Loaded up the fixture files that match my robe clubscan 250's and am successfully using them. However... In the fixture library for that device the dimmer level that triggers e.g. strobe/reset has not been split out or limited - so you can take the dimmer level past 38% and accidentally trigger reset or strobing or program run etc. The details in the dimmer parameter list these different behaviours and the dmx values that trigger them but I haven't been able to work out the best (or any !) way of splitting these out logically, and in a way that works with the jester24ML. So, what I'm not clear on is: 1. Can i limit the dimmer value so that the dmx value of that parameter will never go above a certain value ? What is the best way of doing this ? That would enable me to have a dimmer channel that just takes the fixture from fully closed to fully open with no risk of accidentally hitting the reset value. 2. Can I create a separate virtual parameter that takes the dimmer channel e.g. to the strobe value ? And would I do this by adding a paramter or creating a sub-fixture ? 3. Am I on entirely the wrong path here, and I should for example be using some other desk functions for doing this, rather than monkeying about with the fixture library ? Thanks for any help or guidance, John.