Jon Hole

Hi Sam, The profile looks good, these are the only changes needed: Channel 1 - change 'special' to 'dimmer' Channel 5/6/7 (RGB) - change the default to '255' Because of how RGB colour mixing works, Red, Green and Blue have to be at full to get light output from the unit - I think this might be your problem. Hope this helps, let me know if it works! Best regards, Jon

Hi Sam, If you post up the fixture you have created, we can take a look at it and let you know what's wrong. This will be more productive than just making one for you, as you'll know how to do it for next time then! Regards, Jon

Hi Ray, You should have received an email from Martin with Screen Shots taking you step by step through this process. Going through this, is there a particular point that doesn't work as you expected? What bit isn't working? Regards, Jon

Hi Piero, We're aware of this and working on it. For now, if you send me your user file, I will create a special version of our main library for you, which you can load onto your console, which solves the problem. Best regards, (for reference purposes, this is issue ZOS-5466)

Hi Derek, On the Solution, Macros will only record button presses, so although you can record 'page up' and 'page down' on the submasters, you obviously would have to be on the right page to start with. If you ensured you started at page 1, all your macros could change to the page you wanted, and then put the page back again... I know that's not ideal, but a possible work around. The 30 submasters are there for use on DMX In. Macros on the Solution can only record front panel button presses, so in theory there's no way to get to the other submaster flash buttons from a Macro. However, are you using all 48 channels? If you have a spare one, you could patch it to another universe, and then run a short DMX cable from the DMX Out of that universe to the DMX In, and then use that fader and flash button to be one of the other submasters. Hope that makes sense? Best regards,

Hi, We think the cause of this problem is the same as http://zero88.com/forum/topic/6627-console-freezes/ It seems to be usually caused by 'dodgy' keyboards or mice, but not always. We're pretty sure we've fixed this in our latest software which we are currently testing. So, first try unplugging any mice or keyboards you have plugged in, and see if the problem continues. If it does, there are probably three options for you: - I can send you some beta software to see if this solves your problem. It's easy to backdate if it doesn't. - We can backdate your console to 7.6 until we fix the issue - You can stay on 7.7 for now, and wait until we do a public release Let me know, Best regards, Jon

Hi Ray, I've emailed Martin for me info, I'll let you know when I get more info. Thanks, Jon

Hi Norm, I've forwarded the installdebug.dat file to our software team who will have a look at it and let us know what's up. Hopefully we'll have an answer for you by the end of the day. Thanks, Jon

Hi Mal421, After selecting all the palettes you are using, just reselect the memory you wish to record using the up and down arrows. Best regards,

Hi Agedo, You can download 7.6.0 from this link: http://cooperdownloads.com/share/ZerOS%20Software/ Best regards, Jon

Hi Agedo, Thank you for sending Franck the debug files, sorry for the problem you have experienced. Our software team have found a possible issue, and have added some code to try and fix this and give us more feedback to what is happening in the background. Would you be interested in trying this beta software to see if it fixes the problem you are experiencing or gives us a better idea of what is going wrong? Best regards, Jon

Hi Ray, I've been in contact with Martin at Dram Solutions who tells me he's answered this by email. Please let me know if you haven't received this email, and I will ask Martin to send it again. Best regards, Jon

Hi Mike, Yep - the Jester range can do all of that, and you have the option of the ML section or not :-) Regards,

Hi keredyelesob, Sorry for my delay in replying. Yes - the app is being developed further. We've got an early beta version, but there are still several issues we need to iron out, so I don't have a due date at the moment I'm afraid. However, your feedback is REALLY helpful, so please keep giving it to us! Thanks Jon

Hi GoPowers, Which version of software are you running? The latest is 7.7. Best regards,

Topic duplicated here: http://zero88.com/forum/topic/6620-zeros-update-on-old-frog-2/

Topic duplicated here: http://zero88.com/forum/topic/6618-sharpy-wash-330-profile/

Hi, Did you do the update via USB or CD? Did you download the correct version of software (there is one download for USB, and there is another download for CD). There is no reason that updating the software and then backdating the software should cause any issues, as the update process actually removes ALL the software (both operating and application) from the desk and starts afresh, so backdating the software should work exactly as it used to. Did you definitely backdate the ZerOS software AND the Co Processors? Try backdating the software again, and going through each of the options in turn on the 'Update Screen'. Best regards,

Hi, The best thing to do is to look at the release notes. I've included the release notes for 7.4, 7.6 and 7.7 here for you. The release notes from 7.4 include all the release notes from previous releases. Hope this helps. ZerOS 7-7-0 Release Notes.pdf ZerOS_Release_Notes_7_6.pdf ZerOS_ReleaseNotes_7_4.pdf

Hi Carwyn, The Leap Frog 48 & 96 offers a simple command line used for intensity control, but not full syntax. You'd need a true syntax console, such as the ORB Series, to do this I'm afraid. Regards,

Issue duplicated here: http://zero88.com/forum/topic/6612-android-remote-on-samsung-galaxy-s4/

Issue duplicated here: http://zero88.com/forum/topic/6610-missing-fixtures/

Hi fensch, and all, It appears that LG might have started using a different touch controller, which is why this isn't working. We are working on updating our Linux Kernel at the moment, which will in turn increase our support for Touch Screens. However, this isn't something that's only going to take a week or two, it's a big job that will need a lot of testing afterwards. Best regards,

Hi Mike, So you would be happy if the Colour Picker controlled the whole bar, and then for individual LED components you would have to use the wheels? Regards,

We've defined this for ORB Series, but we're still discussing how we can implement this on Solution. Would you be happy if the colour picker only affected the whole bar? If not, how could you select just one of the LED components to control?