kgallen

Here you go Jonny. 4, 6, 8 channel modes. Regards, Kevin Stairville_QPAR5x8RGBW.ift

I don't see the point cues in the (draft) manual, but Jon says it here: http://zero88.com/forum/topic/7148-missing-features/#entry27904

Hi Rob, Sounds good. Think you've done what you can. Looks like a new 'use case' for the software to consider. You're too good at this - you should be answering Forum posts now! Sorry, over to Jon! Regards, Kevin Sure you know, but you can have 99 'point' cues, i.e. 9.01 to 9.99 between cue 9 and 10.

Hi Rob, Just a thought as you're online now... Is cue 9 configured to jump to cue 200 next or are you at cue 9 and then go-load 200 (as in hold go and type 200)? Not saying there should be a difference, but since the desk 'looks ahead' for MOD maybe the issue? Kevin Just looked in the manual: In cue 9 go to the right column Cue Setup and set Next to 200, then see if you still have the problem. I'd interpret that as a bug if you do as the desk now has the information to look ahead to cue 200 for MOD.

Hi Andy, Welcome to the world of Frog, you'll love it! You will need a CR2032 battery (very common, get on the High Street). Place the desk on a table with the rear (the connector panel) facing you. Remove only 1 screw per side, it's the lowest screw in the curved rear metal silver side. The bottom panel will want to drop down, so support it. It's best to get some help as you will want to support the front panel whilst you access the PCB battery holder. You need to try to flick out the old coin cell - might need gentle help with a knife or small flat screw driver. Click in the new cell. Reassemble the desk, ensuring the bottom plate metal fingers are correctly located in the front of the desk, lifting the back into place and replacing the screws. Power up the desk and set the time/date. Make sure you're running software 10.12 (http://zero88.com/support/index.php?/de/Knowledgebase/List/Index/256/software). If you want to test all of the buttons, holding F1 down as you power the desk will get you into a test mode. Flash buttons 1-14 select faders to test and Step button tests the LEDs. Common fixtures are stored in flash, not battery-backed RAM, that's why they're still there. Anything else - just ask on the Forum! Good luck. Kevin I believe this indicates your desk was the 13th LeapFrog built in week 46 of 2002. I'd PM Keith with the serial number and ask him for the master lock code for that desk.

I should have asked about the hire. Are they providing the package, in which case the hiring company should sort this for you and provide a working setup. If you're adding the keyboard and or monitor then as above!

Yes, sorry Rob that was a bit of a distraction. Can only suggest the obvious for the monitor problem: to try different USB ports for both keyboard and monitor USB, keyboard brands and to recalibrate the monitor touch via Setup on the desk. Also to check for software 7.8.5. I have my monitor USB in a rear socket next to the DVI port. It's a Logitech keyboard and the recommended touchscreen (ProLight T1731). The keyboard is via a 4-port Belkin hub with the mouse into the second rear socket. After that, I'm as stuck as you.... Kevin

Proves you have the code to unlock it! It's a bit like the Yale/mortice door lock situation - whoops I've left my keys in the house and just shut the (Yale) front door! I think on balance, personally I'd keep the code-to-lock situation, particularly if I was hiring the desk.

Jonny, Can you link the manual here? Please always do this so we can be sure to build the correct profile. Please also indicate which modes you want prioritised - some fixtures are extremely complicated and building all modes can be very time consuming. It's a bit hectic for me this week, but I'll try and get around to building the profile in the next couple of days unless someone else beats me to it. Thanks, Kevin

For Blueroom user Biskit (http://www.blue-room.org.uk/index.php?showuser=6082) from this thread: http://www.blue-room.org.uk/index.php?showtopic=66445 Note: Contains 16-bit colour channels on one variant. Manual: http://www.spotlight.it/file.asp?file=/files/prodotto/manuale/Manuali/FOGL-UE-FNLED150-RGBW_IE_low.pdf spotlight_fresneled150rgbw.ift

We had our Tech/LX plot over the weekend, using the FLX, and first Dress last night. 7.8.5 software. Most was good with the FLX regards programming - worked very well. Much less stressful than with the Fat Frog now I've a fair few LED fixtures and needed to be using Tracking. Some usability comments (Tracking-Advanced with SmartTag): - Overall very good! - Groups from the touchscreen were a God-send. - Shift-Record great for blocking cues. - Record <num> Name <type> great for a one-pass record/name. - Update <num> worked a treat. - UDK4 with some strobes on, nice! However, I'm not sure it always released all channels as I expected when the button was released - but couldn't reproduce what I thought I saw, will keep an eye on this. - Auto-palettes on LEDs, great! Some more display niggles however: - The green and yellow bars do get in a muddle when you're programming i.e when there are no cues after the one currently being worked on and both bars are at the bottom of the cue list screen. - There's a "half line" problem where there is a vertical line misalignment and this causes the previous two cue lines to get obscured - needs some up/down arrows to get that sorted and the list redrawn. - When doing a Shift-Record, the just-programmed cue become current - fine. However, when just doing Record, the previous cue stays current and it needs a Go to get to the same place as Shift-Record would. This might be as intended but it's inconsistent. Also the yellow next bar jumps back up to the first cue (because there are no more following, so the first cue is "next"). This is a pain during programming when you want to update fade times in the just-recorded cue - need to do an up-up operation (because cue 0 appears) to get back to the last one just programmed so you can spreadsheet edit the timing parameters. Playing back the cue stack at Dress, the current/next cue are centred on the cue list and this works fine as does on-the-hoof spreadsheet edit of fade times. Button feel is nice. Double-click seems a bit variable on the master Go. When programming, needed to do a very positive/separated Go-Go to move forward. But during the Dress I did a bit of a half-baked press on one cue and skipped a cue and had to go back in the cue list. I had some AND issues, where I'd type 56 AND 57 but the following action only applied to 57 for some reason. This was when I'd got a number of selects in the programmer - selected a couple of groups via the touchscreen, then needed to add 56 AND 57. Often 56 didn't get the @ or the touchscreen palette selection. This happened a few times. As commented in another thread, one USB on the front is awkward when you want a desk light and want to save to USB stick. I have a small Belkin 4-port USB hub for keyboard and mouse in a rear port, and plugging the USB stick in there wasn't always detected. Also have touchscreen USB in the other rear desk port. Mouse pickup on the screen is a bit slow - have to wiggle the mouse a bit to get the desk to respond to it. Not too much of an issue as didn't need the mouse during programming. External keyboard no issues and worked well for cue naming. Only got bit by the ENTER-starts-to-edit-the-cue-number once! Nice to be able to record a part cue (73.5 in my case) before subsequent cues (e.g. 74) has been programmed. (Couldn't do this on FatFrog and it was a bit of a pain [needed to program a junk following cue first before being able to insert the part cue], as I come prepared with a lighting cue synopsis with numbered cue list and draft marked-up script but sometimes the director wants to add an extra cue or two during Tech).

Hi Jon, Excellent thanks for the detail and quick reply (and the function!)! Slightly confused (yes it's a common state!), if the programmer is non-empty then wouldn't it be selecting fixtures, so "Clear Fixture" would "clear everything within the programmer" too? ETA: Just tried this on PhantomOS 7.8.5; "Clear Fixture" on a UDK just clears fixtures selected in the programmer (I had "2 AND 9" in the programmer). It didn't affect the channel I'd grabbed with a channel fader. SHIFT+Clear on the other hand does release the grab and leaves the programmer selection alone :-)

(Sorry for the dumb question - missed it in the manual maybe, and thought it was asked in another forum issue but cant find it! ..and also prepared to be told I've misunderstood FLX channel release philosophy even now!) I'm looking for a function a bit like the channel grab on Fat Frog (http://zero88.com/support/index.php?/Knowledgebase/Article/GetAttachment/56/554 Section 9. Grab Mode for Brightness Channels (Frog Ref No 5574) ) If I'm playing back a stack and want to get hold of the intensity of a fixture (say it got knocked), how would I do this on FLX 7.8.5? Thanks, Kevin (Yes, pre-show panicking!)

Whilst we're here, also in Setup on the Defaults pane, with an external keyboard you can set a split fade time (say 3.0/5.0) for "Intensity Delay" "Cue". This can't be done without an external keyboard as there is no physical or soft-key for "/". Maybe e.g. THRU could act as a "/" key?

Thanks Jon, Ah, of course, makes sense! With the fixtures I had patched, the grey-boxes make sense in the sixes! 49 50 51 52 53 54 55 60 61 62 63 \_____________/ \___/ \______/ I like the attention to detail, nice one! Kevin

On 7.8.5 When I did a Reset All, I just get a full blue screen on the external monitor until I flick to palettes then back to programming, only then the split channels/playback window is drawn (black background). Then when I allocate some dimmers or fixtures, I get grey boxes around random channel numbers (different each time I do Reset All) - just the odd channel number here or there! If I page up then page down (ch/pb page up/down desk button), this gets sorted out, and the grey box draws around the 24 channels for that page (in sixes for the generics). Also with a variety of fixtures patched, the grey boxes draw in groups that I don't understand. They aren't in sixes and they aren't in fixture type groups. I get some grey boxes around pairs and threes and I'm not sure what the significance is! This is before I've set much up, other than a Reset All and patch some dimmers/fixtures. Also in Fixture Edit setup, if you select a fixture name but don't have an external keyboard attached you can get in a mess with the names disappearing if you aren't careful with Clear. You can only get any sort of name in with the numeric keys. There is no way to "Escape" out and leave the name unchanged that I can find. So no on-screen keyboard to help out here. With an external keyboard, no issues, can type a name. (Covered in part here too: http://zero88.com/forum/topic/7240-show-keyboard-when-naming-fixtures/#entry28291) Tech this week, show next - hoping I know enough about the desk! Panic! Kevin

Hi Rejean, The one main thing you didn't do was allocate wheels for each parameter. Under the "3 Wheel Group" tab, you need to allocate each parameter to a wheel. So e.g for Colour, right click and "Add Wheel Group", then allocate each of your colour parameters to a wheel. For this fixture you need more than one colour group for example, as there are 5 colour parameters over 3 wheels. On the desk, multiple presses of Colour give successive pages of colour parameters. Same for beamshape. Also you separated the fine/coarse pan and tilt to two separate channels. Might be preferable to you. In my fixture, I made pan one 16 bit channel. Same for tilt. You'll have to see how you go with these. Other than that, other than setting the defaults (I'm used to how Zero88 usually want them), you're about there. Good luck! Kevin

Jan 2016 CPC now do the SIBA HRC 10A fuses: FF02367 49p ea but MOQ=10.

Hi, Give this one a go. Load this and your own into the Fixture Editor to see what is different. Note: On FatFrog you won't get the channel details for ch12 on the displays. Regards, Kevin Yiscor_12LED_RGBW_Mover.ift

Hi Rejean, Can you attach your fixture file here so we can take a look? In what way doesn't it work? Kevin

Isn't that the point of 36 channel mode that you have individual control of all elements in the fixture? If you press the desk Colour button don't you cycle through the RGB for each element? Hopefully the fixture definition has an overall master dimmer. If you select the fixture and press Home, do all elements come on RGB? Kevin

Hi James, There is quite a bit of work in these, but you really ought to build the full feature fixture as a minimum. Generally the other modes are then a stripped down version. Good luck, Kevin

GROUP 1 AND 2 ENTER = Group 1 and fixture 2. GROUP 1 AND GROUP 2 ENTER = Group 1 AND Group2. This syntax extends ad-nauseum: GROUP 1 AND 3 EXCEPT 5 THRU 7 ENTER = Group 1 fixtures plus fixture 3 but not fixtures 5, 6 or 7 (which would only be relevant if they were in Group 1!) etc etc

Hi Jon. False alarm. Seems I have to press the middle button of the encoder wheel ("Scroll") to get the colour palettes for the scroller. Must have done this before but don't recall it! I have LEDs and scroller a patched. The palettes for the LEDs are always shown by default even if I only select the scroller. I.e. To get the scroller palettes I have to press the encoder button even if the scroller is the only thing selected. Anyway, works the same on 7.8.4 and 7.8.5, so thanks for the code image to check. Previous comment on possible display bug still apply. Kevin

I know this was covered in a topic, but blowed if I can find it. [ETA: See the bottom of this post: http://zero88.com/forum/topic/7172-more-questions-issues/#entry28049] 1 AND 2 AND 3 ENTER is fine, ch 1,2,3 are selected. 1 AND GROUP 1 ENTER starts to edit the cue number field. Grrr. GROUP 1 AND 1 ENTER is fine. GROUP 1 AND GROUP 2 ENTER starts to edit to cue number field. Grrr. (1) Please sort out a better way of triggering cue number edit, as it getting mixed up with syntax termination is naff and really annoying! But I sympathise as there doesn't seem to be an easy answer with ENTER being used to trigger field edit... (2) How to select multiple groups with syntax (with touch screen is ok). We know selection order is significant for effects... Thanks.