3.0.15_b3

@Noel
issues should be he same with _b4 so i'll fix them next week.
Midi script is hardcoded in DL.... as it's a xplatform software, I cannot afford too much of using applescript.

I think (with some work as nothing is done yet) that I can add binding to other language (like python or so) but they need to be xplatform.
If you want to start learning a language, go ahead
this one seems pretty nice kivy.org/#home (it's python based and python is a fashion language these days)
it would be cool to have plugins for DL....

++

I wouldn't mind writing in Python
For my job (telecom engineer), I have developed a script (yes, in Python) that can control thousands of routers worldwide.

This script also uses a very simple form of "plugins" : CSV-files.

These files can easily be created and maintained with a simple textprocessor ( and with a spreadsheet, of course).
The point is that (almost) anyone can create and maintain these files.
There is now a whole library of these files for different purposes/networks.
As these are simple and small files, it is very easy to share them with other people.

DL is already using this idea too: it is possible to import a curve in the patch-window.
Perhaps this idea can be extended to other modules as well : patches, midi, ...?
And in the future: fixture personality files :whistle:

For the midi setup, I am thinking of saving the setup as XML, then edit that file, then import it again.

Best regards,
Noël

IMHO python plugin would be great to have more elaborated GUI for example controlling fixture:
- for Pan/Tilt
- Shape
-etc....

DL is already using this idea too: it is possible to import a curve in the patch-window.
Perhaps this idea can be extended to other modules as well : patches, midi, ...?

why not, we have to define the format of the CSV file.
but I think that xml files (as DL do) is better.

And in the future: fixture personality files

GUI for fixture personnality is already done. it's not yet public as I first would like to improve the 3.0 series to have a robust branch, and aslo I've to model the code to accept several 'mode' for personnality (eg mode 6 channels, 11 channels, 18 channels).
Files will be encrypted thus we can control parameters in DL and not with text editors to avoid mistakes.

For the midi setup, I am thinking of saving the setup as XML, then edit that file, then import it again.

it's a solution.
a python plugin can also allow to create Midi Bindings.

++

sl1200mk2 écrit: IMHO python plugin would be great to have more elaborated GUI for example controlling fixture:
- for Pan/Tilt
- Shape
-etc....

DL is already using this idea too: it is possible to import a curve in the patch-window.
Perhaps this idea can be extended to other modules as well : patches, midi, ...?

why not, we have to define the format of the CSV file.
but I think that xml files (as DL do) is better.

But XML is difficult to read for most people, let alone write in it.
Still, XML exported files can be exchanged between users.

And in the future: fixture personality files

GUI for fixture personnality is already done. it's not yet public as I first would like to improve the 3.0 series to have a robust branch, and aslo I've to model the code to accept several 'mode' for personnality (eg mode 6 channels, 11 channels, 18 channels).
Files will be encrypted thus we can control parameters in DL and not with text editors to avoid mistakes.

Why not, for a fixture that has multiple modes, create separate personality files?
That way, the structure of the files can be kept simple.

For the midi setup, I am thinking of saving the setup as XML, then edit that file, then import it again.

it's a solution.
a python plugin can also allow to create Midi Bindings.

Once I am done with creating the file, I will publish it on the forum, with some explanation on what it does, so others can use it as well.
For the BCF/BCR configurations (that will take a while, I'm afraid), I will publish the sysex-files.

For the patches, I used a 'new show', and exported the patch.
When I now want to put the patch back to '1:1' , but keep the rest of the show, I can simply import that file.
I'm thinking of creating a '1:0' (empty) file as well [idea shamelessly stolen from an ETC manual...]

++

Best regards,
Noël

For the patches, I used a 'new show', and exported the patch.
When I now want to put the patch back to '1:1' , but keep the rest of the show, I can simply import that file.
I'm thinking of creating a '1:0' (empty) file as well [idea shamelessly stolen from an ETC manual...]

there's a 1:0 function for all DMX universes in the patch window that you can export in xml...
++

Ah !... I had not explored the little broom yet. Great, and it even works per universe. Good job !

Best regards,
Noël

For the midi setup, I am thinking of saving the setup as XML, then edit that file, then import it again.

it's a solution.
a python plugin can also allow to create Midi Bindings.

++

Editing the exported Midi-setup in a texteditor works like a charm
It took me only a few minutes to export the setup that was created by the script, change the Submasters and Flash from Midi-channels 5 and 6 to 15 and 16, and import it again in DL. Perfect !

When I have a bit more time, I will add ROOM 2 (CC 0-127 in Midi-Channels 5-, so I can test all that too.
For ROOM 3 and 4, I am working on getting a second BCR2000

Best regards,
Noël

cool,
glad it works.

++

@ Nico,

In the Midi-window, how do I connect a CC to a circuit higher than 512 ?
e.g. Midi Ch.#5, CC 0 <> circuit 513

Merci !
Noël

PS. Someday, I want to build something like this ...

@Noel,

In the Midi-window, how do I connect a CC to a circuit higher than 512 ?
e.g. Midi Ch.#5, CC 0 <> circuit 513

I think it's something I've forget to do...
but as the b5 cooking was almost done, I keep this for the next one.

ps: nice machine, you can even trap the PC inside

++

@ Nico

No hurry. I'm not going to use more than 1 ROOM soon. But someday...

Yes, the idea (so far) is to get 3 BCF2000 (24 SIMULATIONS presets), and 2 BCR2000 (2 ROOMS each), but put an LCD in the middle, and the Mac Mini behind it (with a wireless keyboard and mouse)

Right now, I have the BCF2000 *and* BCR2000 working together. 'Shopping' for more...
Very nice to move a fader on the BCR, and see the LEDs move on the BCR

Best regards,
Noël

@ Nico,

In the Patch-window, the 'little broom' can be used to set the patches to 1:1 or 1:0. (Thanks for that !)
I think that, instead of 'universe 0, universe 1, ...', this should read 'Room 1, Room 2, ...'.
Also, when the patch is saved (as XML), it writes it as 'universes', while these are actually 'rooms'.
Not a big deal, but it adds to the confusion between 'universe' and 'room'.

Best regards,
Noël

@Noel,

In the Patch-window, the 'little broom' can be used to set the patches to 1:1 or 1:0. (Thanks for that !)
I think that, instead of 'universe 0, universe 1, ...', this should read 'Room 1, Room 2, ...'.

This was exactly the point were I've decided to separate ROOM and dmx universe because it was unclear and too confusing.
so in the Patch window, it's not the Channel that you clear but the Dimmer part.
thus if you have a channel that's patched against dimmer form universes 0 and 1, I think it's nice to be able to unpatch all dimmer from the first universe and keep the second universe' patch.

if you read ROOM in the 'little broom', you won't be able to do that.
and keep in mind that DL output over 4 universes regardless the ROOM number.

Also, when the patch is saved (as XML), it writes it as 'universes', while these are actually 'rooms'.
Not a big deal, but it adds to the confusion between 'universe' and 'room'.

you're right, I'll see if I can change that (eg if there's not too much people in the code that refer to 'universe' word)

++

sl1200mk2 écrit: @Noel,
so in the Patch window, it's not the Channel that you clear but the Dimmer part.
++

You're absolutly right. I got confused :ohmy:

Thanks for clearing that up

Best regards,
Noël

@Noel
with the b6, you can easily select the ROOM of a channel in the Midi patch window.
I've also change universe to ROOM in the patch.xml

would you mind trying if it goes well?
++