Titan Simulator / Visualiser / Chauvet Products

[nrosten]

Hi All,

bit new to the modern world of lighting (but give me a Vmware server or anything windows and I can help there!)

Basically I have a new setup I work with at a local skating rink which comprises the following:-
Titan Mobile console paired with a 23" multitouch screen.
8 x Chauvet Intimidator Spot LED 350
4 x Chauvet QWash 560Z-LED
8 x DMF10 (not my choice but adds a bit of colour)
20 x Colorband Pix bars

Very impressed with the LED kit, its very bright and responsive and big step up from the boring fixed lights and martin streaky controller (ugh!)

As time onsite is limited programming wise due to the venue being open pretty much all day long I figured I would try my hand at the offline Titan simulator / Vis and try to setup some programs in my own time.

Main issue I have is it appears the main moving heads are not supported in the Vis. I understand pixel bars and such are not supported, less worried about these as they can be programmed while venue is open, and the DMF10's again not worried as they static moonflower effects with limited options.

I have requested the vis files via the normal route but was wondering if there is any way to hack via personality builder or similar a workable file to get some basic output in the visualiser?

I have the show file backup from site and when using the auto option as expected only populates the vis with 12 channells of generic Par Cans also onsite.

I admit to being a bit green on this front so forgive any stupid wording here, so far this titan mobile setup seems really user friendly and with the touchscreen makes it a joy to use.

Many Thanks
Neil

[niclights]

The good news is you have all the tools available that are used at factory and all those fixtures should simulate fine (with the exception of the multi-cell and amber/white bits). The bad news is it can sometimes be a bit fiddly and potentially could be a bit of a steep learning curve on top of a new console. Depends on how comfortable you are with computers.

Firstly, Personality Builder does provide an option to create .vis extension files when exporting .r20 (classic) personalities. There is also a separate application called VisWiz although personally I would probably not use this.

Visualiser files require a matching pair of .r20 and .vis file to work and the .r20 file must exist in the avolites/visualiser/personalities folder. This is very important as these are intentionally separate from those in the avolites/personalities folder. Both files must have the same device name and for the auto-update function to work this device name must be defined in the .d4 personality Classic Pearl Reference field which is found in each mode.

Even if an .r20 file already exists it will probably be easier to export a new version along with the .vis extension from the factory .d4 file. This way you can ensure you get a matching set.
When doing this one of the most important things to get right is the Classic wheel mapping. You will need to do this because it is not stored within the .d4 file and therefore will almost certainly be wrong when you first load the file into Personality Builder for editing.
Select Wheel Mapping bottom-right and then the Classic tab at the top. This will show the current wheel assignments for all the attributes. Where an attribute is not assigned or a wheel has more than one then it will be marked in red. It is important that all attributes are assigned and nothing overlaps (ie. no red). Drag-drop until this is true. For this application it is not particularly important where they go as long as they are not red. Then select each attribute and set its type in the options. Each attribute must have a unique type with the exception of 'uncategorised'. Personality Builder relies on the type definitions to understand what each attribute does.

Now expand the modes section in the tree on the left, select a mode (maybe just the one you are using for now) and enter a device name in the Classic Pearl Reference field. Choose 'Export .r20' from the files menu and say yes to the 'create Vis file' prompt. Save the .r20 file to C:\program files\avolites\visualiser\personalities. Save the .vis file to c:\program files\avolites\visualiser\extensions.

For testing I would start a new show, close/relaunch software and try patching with auto-update turned on in Vis. If it's successful then great. If not then the .vis extension file might need some tweaking. Here we are going beyond the bounds of the forum but open the file in a text editor and you should be able to make some sense of it with a basic level of programming skills.

If this sounds confusing it's because it is.

Finally a note about the multi-cell. While visualiser doesn't natively support it and there are no ways to automate the process, it is still possible to simulate these fixtures. You just have to do it manually. For example if you have a 9-cell fixture which is R1,G1,B1,R2,G2,B2 etc. then you can use nine generic RGB, 3 DMX fixtures in Vis. As long as the addresses match it will work just fine. I have done this in the past to pre-program many times and it works very well.

[nrosten]

Thanks Nic

I will give it a go - I am willing to learn / try anything - I used to be a oracle programmer in years gone by and now spent most of life installing / setting up windows / vmware servers so used to fiddling around to get things working.

I think its worth the effort getting them working to a fashion, i can then measure the venue / rig height and get the lights more or less in same possition, bit of effort but once done will save a load of time in messing around and testing things.

tempted to try the RGB as once setup some nice effects should be avail accross the 20 led bars, they round 3 sides of the skating ring pointing up illuminating a bright white wall.

Neil

[niclights]

When manually adding fixtures for multi-cell battens I find it very helpful to make use of the position offset fields to quickly arrange things neatly.

For example with vertical battens set a start x/y/z coordinate with y offset, add x*number of cells. Change to x+gap and reset y to the original start value. Repeat adding x*number of cells etc.
As long as all the cell addresses run consecutively and your positioning starts from the first fixture/cell then you have a tidy layout ready to go with minimal fuss. Normally I will experiment to find the correct offset values before doing it properly.

I would also suggest considering an abstract simulation rather than an absolute 3d version. The nature of the wireframe can sometimes make it quite confusing in 3d and personally I find it much more useful to use a front view and deliberately design a theatre that shows me everything I need in this elevation even if it is not technically correct in 3d space. This is particularly true of non-moving fixtures where really you just want to know whether it is on and in what colour (if applicable). Even when I am pre-programming moving elements I tend to switch between front/plan/side rather than use a perspective view.

[nrosten]

Had a good fiddle with the Qwash 560Z.
in the classic pearl wheel mapping I had White/Colour Macro/Control highlighted in red. Moved these into some blank spaces such as White > Colour/Wheel 2 and so on.. changed the classic pearl reference to CH_Q560ZA for advanced 15 dmx and CH_Q560ZB for the Basic 12 DMX.
when exporting it appears to save the R20/Vis in same folder so I moved them to folders as suggested.

Restarted / new show / Patched a couple of Qwash 560 in advanced 15bit mode - no luck nothing shows in Vis, even if you go in manually into vis I would assume I could see the Qwash in the list of moving heads ?

will play around and try the led 350 if i can find it

Thanks

[niclights]

Two thoughts. One, I did miss out the step of saving the edited .d4 file with the new classic pearl references which relates to auto-update. Two, one of the most common issues is where there are more than one .r20 file with the same device name.

Looking at the factory .d4 file it already has the same device names defined in classic pearl reference so theoretically you shouldn't need to do anything here if you're using these.

However, given that you have given them the same device name as the factory .r20 files there could be a conflict. Have a look and see if CHQ560ZA.R20 and CHQ560ZB.R20 exist. Technically I don't think they should be there but if they do rename the extension to .old and try again.

[nrosten]

WIll give it a go and let you know. Thanks!

[nrosten]

bah - checked all that and re-saved - got the 4 washes to appear in the vis when I open the venue show and they even auto populate when doing a new show and manually adding a bunch of them, only problem is i get no movement or beams in simulator run mode - everything else I add manually works fine bar this one I created - guessing its some setting I messed up.

[niclights]

This is all standard fayre in my experience but I reckon you're almost there now.

If it patches then we're just down to the finer points and it's time to get involved with the text editor.
First I would open the .r20 file and check all the attribute types are correct and unique.

Using the factory advanced version of QWash560Z as an example:

Code: Select all

;----------------------------------------------------------------------------
; DMX channel description
;
; Column by column description of each DMX channel
; 1. The channels bank number (1..20)
; 2. The upper faders in the bank (1) or the lower faders in the bank (61)
; 3. Channel type (L=LTP, H=HTP, I=Instant LTP, S=16-bit instant LTP,
;    s=16-bit Fadeable LTP
; 4. DMX offset (1..number of DMX channels)
; 5. The output level is proportionally reduced by this level (0..100%)
; 6. The curve number (applicable only to HTP channels), usually set to 1
; 7. Inverted (I) or Normal (N)
; 8. Attribute type (A=Colour Wheel 1, B=Cyan, C=Magenta, D=Yellow,
;         E=Pan, F=Tilt, G=Iris, H=Dimmer, I=Gobo1, J=Gobo2, K=Gobo1 Rotate,
;         L=Focus, M=Gobo2 Rotate, N=Colour Wheel 2, O=Shutter, P=Prism, Q=Zoom,
;         R=Effect Rotate, S=Frost, T=Red, U=Green, V=Blue, 0=uncategorised)
; 9. Checksum channel (Always 1)
;10. Attribute name, must be enclosed in quotes and upto 12 characters allowed
;11. The ON value of this channel (0..255)
;12. The Highlight level of this channel
;13. The Lowlight level of this channel
;
DMX
3    61   s    1   100   1N   E   1   "Pan"             128     0     0
0     0   L    2   100   1N   E   1   "Pan Low"         128     0     0
3     1   s    3   100   1N   F   1   "Tilt"            128     0     0
0     0   L    4   100   1N   F   1   "Tilt Low"        128     0     0
8     1   L    5   100   1N   0   1   "P/T Speed"         0     0     0
10    1   L    6   100   1N   T   1   "Red"             255   255     0
10   61   L    7   100   1N   U   1   "Green"           255   255     0
9    61   L    8   100   1N   V   1   "Blue"            255     0   229
4    61   L    9   100   1N   0   1   "White"             0     0     0
4     1   L   10   100   1N   0   1   "Amber"             0     0     0
9     1   L   11   100   1N   0   1   "Colour Macro"      5     0     0
1     1   H   12   100   1N   H   1   "Dimmer"          255     0     0
2    61   L   13   100   1N   O   1   "Shutter"           5     0     0
5     1   L   14   100   1N   Q   1   "Zoom"            127     0     0
11    1   L   15   100   1N   0   1   "Control"           0     0     0
END
;

The eighth column contains the attribute type letter. This is how it should look ie. Pan/Pan Low = E, Tilt/Tilt Low = F, RGB = TUV, Dimmer = H, Shutter = O, Zoom = Q and everything else 0 (zero - uncategorised). The uncategorised attributes would not simulate so this if fine.

Once this is fixed/confirmed correct then we can move onto the .vis file which is most likely where the error lies. It might be easiest if you post it wrapped in code tags here for dissection.

[nrosten]

one i have is a bit different ..

Code: Select all

DMX
3    61   s    1   100   1N   E   1   "Pan"             128     0     0
0     0   L    2   100   1N   E   1   "Pan Low"         128     0     0
3     1   s    3   100   1N   F   1   "Tilt"            128     0     0
0     0   L    4   100   1N   F   1   "Tilt Low"        128     0     0
8     1   L    5   100   1N   0   1   "P/T Speed"         0     0     0
10    1   L    6   100   1N   T   1   "Red"             255   255     0
10   61   L    7   100   1N   U   1   "Green"           255   255     0
9    61   L    8   100   1N   V   1   "Blue"            255     0   229
9     1   L    9   100   1N   0   1   "White"             0     0     0
4     1   I   10   100   1N   A   1   "Amber"             0     0     0
8    61   L   11   100   1N   0   1   "Colour Macro"      5     0     0
1     1   H   12   100   1N   H   1   "Dimmer"          255     0     0
2    61   L   13   100   1N   O   1   "Shutter"           5     0     0
5     1   L   14   100   1N   Q   1   "Zoom"            127     0     0
7     1   L   15   100   1N   0   1   "Control"           0     0     0
END

tried changing settings to yours and still no movement or beams.. was pretty close.

[nrosten]

vis file for same advanced unit

Code: Select all

// Chauvet - Q-Wash 560Z LED
// Avolites Visualiser Extension File
// Copyright © Avolites Ltd. 2012
//_________________________________________________________________________________
// File Name: CHQ560ZA.VIS
// Created by: Personality Builder - Version 2.2.11.5
// Date: 30/07/2012 20:25:01
// Exported From: Q-Wash 560Z LED
//_________________________________________________________________________________

Device CHQ560ZA

// Pan
ChanRef Pan
    Vismode Value
    UseBits 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
    DmxOffset 1 2
    Mapping 0 65535 -265.000000 265.000000
End

// Tilt
ChanRef Tilt
    Vismode Value
    UseBits 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
    DmxOffset 3 4
    Mapping 0 65535 -135.000000 135.000000
End

// Red
ChanRef Red
    Vismode Value
    UseBits 1 2 3 4 5 6 7 8
    DmxOffset 6
    Mapping 0 255 0 255
End

// Green
ChanRef Green
    Vismode Value
    UseBits 1 2 3 4 5 6 7 8
    DmxOffset 7
    Mapping 0 255 0 255
End

// Blue
ChanRef Blue
    Vismode Value
    UseBits 1 2 3 4 5 6 7 8
    DmxOffset 8
    Mapping 0 255 0 255
End

// White
ChanRef Color Wheel 1
    Vismode Value
    UseBits 1 2 3 4 5 6 7 8
    DmxOffset 9
    Mapping 0 255 White
End

// Amber
ChanRef Color Wheel 2
    Vismode Value
    UseBits 1 2 3 4 5 6 7 8
    DmxOffset 10
    Mapping 0 255 RGB240,100,0
End

// Colour Macro
ChanRef Color Wheel 3
    Vismode Value
    UseBits 1 2 3 4 5 6 7 8
    DmxOffset 11
    Mapping 0 10 White
    Mapping 11 30 Black
    Mapping 31 50 Black
    Mapping 51 70 Black
    Mapping 71 90 Black
    Mapping 91 110 Black
    Mapping 111 130 Black
    Mapping 131 150 Black
    Mapping 151 170 Black
    Mapping 171 200 Black
    Mapping 201 205 Black
    Mapping 206 210 Black
    Mapping 211 215 Black
    Mapping 216 220 Black
    Mapping 221 225 Black
    Mapping 226 230 Black
    Mapping 231 235 Black
    Mapping 236 240 Black
    Mapping 241 245 Black
    Mapping 246 250 Black
    Mapping 251 255 Black
End

// Dimmer
ChanRef Dimmer
    Vismode Value
    UseBits 1 2 3 4 5 6 7 8
    DmxOffset 12
    Mapping 0 255 0 255
End

// Shutter
ChanRef Dimmer
    Vismode Strobe
    UseBits 1 2 3 4 5 6 7 8
    DmxOffset 13
    Mapping 0 10 1 1
    Mapping 11 255 30 300
End

// Zoom
ChanRef Zoom
    Vismode Value
    UseBits 1 2 3 4 5 6 7 8
    DmxOffset 14
    Mapping 0 255 10 10
End

[nrosten]

think ime getting somewhere - just rebooted as vis.exe had crashed - new show and added 4 advanced and 4 12 channel
now got working Pan / Tilt

zoom does not work / dimmer does
colour is messed up - only seem to get amber / orange and no other colours so guessing I messed up the R4 file as no colours showing in titan part - let alone the vis ..

Getting there slowly.

[nrosten]

also got intimidator led 350 spot working more or less - working dimmer / pan / tilt / gobos to a fashion and colours apart from the colours do no tmatch the wheel at all - open looks like yellow, Red is green and so on ..but at least the fixture is visable.

[niclights]

OK. Two more things...

Firstly I notice that your device name doesn't quite match your classic pearl ref in your earlier post. The device name in your .vis file does not have the underscore. Double-check that the device name in the .r20 file, the .vis file and the classic pearl ref field of the .d4 mode all match.

Next try deleting the White, Amber and Colour Macro sections of the .vis file. You can also change the Zoom mapping so there is a range: In the Zoom section replace

Code: Select all

Mapping 0 255 10 10

with

Code: Select all

Mapping 0 255 8 32

With those steps complete I'm quietly hopeful!


For your reference all the vis fixture data is stored in theatres (including those embedded in showfiles). Existing fixtures in a theatre will update any changes if you close/reopen Vis.
To patch any newly created .d4 fixtures or any that have new modes or changes to mode names you must restart the software before they will be available.
To update any changes to a .d4 file that is already patched use Patch/[Update Personality]. Note that this will break if you change the mode name of a patched fixture. In this case you can use exchange fixture instead.

[nrosten]

Thanks Nic

will give this a try and update.

Neil