par led

Hello !

In your device, your parameter of intensity would be DIMMER instead of MASTER DIMMER.
I've try to modify them directly on devices listing and it doesn't work better. But I've edit it on Personnality Editor, save as a new name and try again, and INTENSITY works.

TO patch your device, you have to specify your channel on Device listing, and next patch the DMX address on D-Patch colon on Patch window.

Hi,
Antoine is right, you need to set DIMMER as INTENSITY parameter in order to work.
attached the Device's personality modified.

++

That did the trick - I didn't though the Parameter value was of such importance name-wise (I took over the personality name of the manufacturer).

Thanks Antoine et Nico!

@Wilf,
cool, I've pushed your personality to dlight-tools:
github.com/dlight-tools/dlight-devices

@nomatter
thanx for sharing, I've pushed your personality to dlight-tools too.
by the way, I've set some HOME value for shutter (we want it open for HOME calls), and for PAN/TILT

To create a Dlink, Intensity has to have value > 0; So if I need to move machine on black I need to record cue with light, then to modify intensity and save again. Is there another way I don't know?

:Light will automatically do move on black.
-step 1, intensity = FF, DLink to set devices at some palette
-step 10, intensity = 0 (move to next asked palette as in step 11 a dlink is recorded)
-step 11, intensity = FF, DLink to set device to some other palette.

I know you're still working on MIDI. Are you also adding MIDI command to activate Palettes? It will be very useful for impro shows.

not yet, this and OSC calls will come in future

Imagine I have 2 equal device set with different DMX address. Is it possible to control them with same channel? I didn't succeed in it.

nope,
use GROUPs to work with several devices

Really great the possibility to save Palette in Dlink. In this way if I modify Palette I will see changes all over the sequence. Really useful for refocusing devices in a tour show. Awesome.

use the palette editor.
if you modify levels for a palette in the palette editor, every time the palette is call, it will use new levels

thanx for trying these Device's new feature.
++

That did the trick - I didn't though the Parameter value was of such importance name-wise (I took over the personality name of the manufacturer).

I think only this one is important. Other parameter can be named as you like !

the more you keep name that :Light recognize as parameter, the more :Light will be able to do proper merge between devices.

let's say that on tour, on the first date you work with ClayPaky, and the seconde date with Martin, you'll want to merge personality (in the device listing) for your sho.

and as for now I didn't finish the merge, :Light will only merge if it recognize parameter's word.

this is where it's important to keep parameter's name
++

@ Nico: I changed the personalities and made a few more - I'll make the rest too (the TOUR and ALL at least).

I changed the name of every personality to match the personality chosen on the device.
The one with AR2.Z has a seventh channel with 0-200 no function, 201-220 zoom reset, 221-255 no function. Please look into it to see if I made the right choice in naming (I do not know however where to find the function for it in DLight).

By the way, this par has a HSV personality - how can I implement that?

By the way, this par has a HSV personality - how can I implement that?

HSV ???
I thought it was only a computer thing and that only CMY or RGB exists...
DL can do HSV, but it's math derived from CMY.
can you post a link to the manufacturer doc?

++

This is a PDF of the manual. It reads very hard since it is a printout PDF so all the pages are mixed up.

www.rolight.nl/download/ROLIGHT156054.pdf

you're right....
but IMHO, it's something derived from RGB and in DL you cannot implement HSV mode...

for the ar2.z, you are right to choose CONTROL as attribute, but for the parameter you want to choose FUNCTION and create definitions like
no function 0 -> 200
reset 201 -> 220
no function 221 -> 255

after which personality to write for this device... I would write 3: TOUR, TR16 and FULL
but once again it depends how many universe you can get and how many device do you have...

++

Yes, the simple personalities were more of a rehearsal for me to see how I could manage devices and if I could make personalities. They could be used as a template though in some instances; I know of some venues with LED lighting as house lights, it's of course infinitely more easy to make a few devices then to patch them all as single channel. Maybe those personalities should just be called "Generic MRGB(W)" for instance (meaning Master Red Green Blue (White)).

Anyway, thanks again for your great input, now I know how to make personalities and the next time I run in to a new device I can make my own AND share it with everyone.

P.S. I edited my post on page 2 - it has a crash report (crash occuring because of faulty personality file) concerning 4.0.b39

@Wilf,
it's hard to rely on 'Generic' personality as for example DIMMER can be the first offset or the last offset or whatever...
the house light with LEDs is a great example and it would be nice if one can test DL in such situation. Two possibilities come to my mind: either all LEDs are wired together with 4 dimmers (for example) for all, either each LEDs have 4 dimmers and are wired on the second or the third universe.
in the first case, it's easy, you create a personality, load it, set a channel, patch it to the Dimmers the venue tell you they are...
in the second case, you'll create a personality, load it, set a channel and clone it (as you can get more than 100 units).
it would be nice to test DL in this kind of venue to see how it behave.
in DL you cannot patch (yet... I don't know if I'll work on that) several devices to 1 channel

P.S. I edited my post on page 2 - it has a crash report (crash occuring because of faulty personality file) concerning 4.0.b39

I don't see the crash report... can you post it here, please?

++

Using a personality as a generic personality of course only works if one knows the data matches and I know a few venues in The Netherlands that have such charts. For example: there is one venue here in Amersfoort which has RGB LED house lighting consisting of about 120 different consecutive channels. With the old DLight it was quite a task to patch it, with 4 it would consist of loading a generic RGB personality and cloning it 40 times. That's a great way to simplify and speed up patching. Great stuff!

Wilf wrote: 4.0.b39 crashes when I adjust color values when I try to test with the personality file without master dimmer (only 4 channels/dimmers).

Later on I tried it again and it crashed when trying to adjust the channel master. So what I think happened is this: I adjusted the personality file in the device window, deleting the master dimmer track to see if that made the fixture working (thinking the channel number was already a master, that it would be offset 0 (that is not on the list) as first DMX channel. When repatching, going back to main window and (with the track pad) dragging the channel open DLight crashed. As if it got conflicting data back from the fixture that did not match. Probably the real conflict is because of the now missing master and the interpretation of DLight of the master channel that is now also R from RGB, which is not possible of course. This is just speculation on my side trying to interpret the crash.

@wilf,
and can you provide the crash log?

I mailed you the crash logs on your gmail account (if you still use it).