Hi there,
after the usual but always needed grats for your continuing efforts on this great software i wanted to ask if it's me that i don't get something or is it something else inside the program that doesn't allow the Eurolite USB-DMX512-PRO Interface to be seen as an output?
As far as i tried nothing can be done. FreeStyler sees it but (along with my sorry to developers and users of FS) as far as I may say, the comparison is by far for the QLC+.
So if there is something that can be done either by me or by any of you i'd appreciate your answers.
Thanks in advance
EUROLITE USB-DMX512-PRO Interface, not playing-showing as output
-
Jano Svitok
Hi,
QLC+ doesn't support this device now. OLA in LInux supports it, so
1. it's possible to use OLA plugin with this card (Linux/OSX only, no Windows)
2. the code is available, and pretty simple, so creating plugin for this device should not be hard, may be even one of the existing may work. The downside is, that no of the current developers has the device, and development without the device is slow.
If you know C++, I may guide you through the process.
QLC+ doesn't support this device now. OLA in LInux supports it, so
1. it's possible to use OLA plugin with this card (Linux/OSX only, no Windows)
2. the code is available, and pretty simple, so creating plugin for this device should not be hard, may be even one of the existing may work. The downside is, that no of the current developers has the device, and development without the device is slow.
If you know C++, I may guide you through the process.
-
vag
Jano thanks for answering.
Unfortunately i don't know C++ (one of the many things i regret every day for not giving them some time), my only relation to programming is minimized to MSOffice... (Access and all these).
I don't know if i could follow your guideness but to just have a look of how a plugin is, just give me the info where i can find it in the source files (is it just the plugins folder?) and what info i should have from the device side, cause in the box there was nothing and i only downloaded the drivers from the site of eurolite.de
Thanks again
Unfortunately i don't know C++ (one of the many things i regret every day for not giving them some time), my only relation to programming is minimized to MSOffice... (Access and all these).
I don't know if i could follow your guideness but to just have a look of how a plugin is, just give me the info where i can find it in the source files (is it just the plugins folder?) and what info i should have from the device side, cause in the box there was nothing and i only downloaded the drivers from the site of eurolite.de
Thanks again
-
Jano Svitok
The plugin files are in plugins/usbdmx/src/ You'll have to either add required information to enttecdmxusbpro, or clone the related files and adjust that (depending on how different the devices are).
OLA sources are here: https://github.com/OpenLightingProject/ ... ins/usbdmx
Here is an old QLC thread about the device: https://sourceforge.net/apps/phpbb/qlc/ ... 62&start=0
Here is an article that warns people about this device, that gave me this idea:
It may be possible to download FT_Prog from FTDI site and set the IDs of the device to the those of enttec open or pro, whichever is more similar to the eurolite device. Beware! If you don't know what you are doing, you may brick your device (render unusable/unrepairable)!
OLA sources are here: https://github.com/OpenLightingProject/ ... ins/usbdmx
Here is an old QLC thread about the device: https://sourceforge.net/apps/phpbb/qlc/ ... 62&start=0
Here is an article that warns people about this device, that gave me this idea:
It may be possible to download FT_Prog from FTDI site and set the IDs of the device to the those of enttec open or pro, whichever is more similar to the eurolite device. Beware! If you don't know what you are doing, you may brick your device (render unusable/unrepairable)!
-
vag
Hi again everyone.
After all these months i see that this dongle isn't getting its place in QLC+...
I've checked inside the box and found that the chip is not ftdi but mcp2200 so i understand (not sure for that of course) that this is the pblm that all other usb-dmx plugins don't "see" it.
Anyone here that has found a way to make that work with QLC+...?
After all these months i see that this dongle isn't getting its place in QLC+...
I've checked inside the box and found that the chip is not ftdi but mcp2200 so i understand (not sure for that of course) that this is the pblm that all other usb-dmx plugins don't "see" it.
Anyone here that has found a way to make that work with QLC+...?
-
Matthew Marks
It seems this isn't a very popular device... unless you've got several to support it might be better to cut your losses and get something that's compatible. I don't see anything special about it to justify its price tag - it doesn't even seem to claim isolation. Search this forum for Anyma for a really cheap interface I can recommend.
-
vag
THX for your reply Matthew.
I know that the best to do would be to go for something else but the main pblm is that the setup is running in an occupied theater that hasn't got much money to spend and decisions through the open assembly are very difficult to make (it was my bad from the beginning that i didn't check compatibility)... so i'll stick to FreeStyler for now and hope that someone will find a way to make a plugin for QLC+...
I know that the best to do would be to go for something else but the main pblm is that the setup is running in an occupied theater that hasn't got much money to spend and decisions through the open assembly are very difficult to make (it was my bad from the beginning that i didn't check compatibility)... so i'll stick to FreeStyler for now and hope that someone will find a way to make a plugin for QLC+...
-
Karri Kaksonen
I got fooled by the name and the positive comments about this device at Thomann. I would like to port the plugin to QLC+ as soon as possible. We should be running with the device by May.
I already cloned the git repository to my laptop and currently setting up the environment.
Update: currently compiling qlcplus
Update: it compiled and installed without any problems on 64 bit Ubuntu 14.04
Could you suggest a good starting point for the Eurolite USB-DMX512-PRO plugin?
[ 250.449708] usb 3-3: USB disconnect, device number 6
[ 256.214038] usb 3-2: new full-speed USB device number 7 using xhci_hcd
[ 256.234882] usb 3-2: New USB device found, idVendor=04d8, idProduct=fa63
[ 256.234892] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 256.234897] usb 3-2: Product: Eurolite DMX512 Pro
[ 256.234901] usb 3-2: Manufacturer: Eurolite
[ 256.235818] cdc_acm 3-2:1.0: This device cannot do calls on its own. It is not a modem.
[ 256.235861] cdc_acm 3-2:1.0: ttyACM0: USB ACM device
I already cloned the git repository to my laptop and currently setting up the environment.
Update: currently compiling qlcplus
Update: it compiled and installed without any problems on 64 bit Ubuntu 14.04
Could you suggest a good starting point for the Eurolite USB-DMX512-PRO plugin?
[ 250.449708] usb 3-3: USB disconnect, device number 6
[ 256.214038] usb 3-2: new full-speed USB device number 7 using xhci_hcd
[ 256.234882] usb 3-2: New USB device found, idVendor=04d8, idProduct=fa63
[ 256.234892] usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 256.234897] usb 3-2: Product: Eurolite DMX512 Pro
[ 256.234901] usb 3-2: Manufacturer: Eurolite
[ 256.235818] cdc_acm 3-2:1.0: This device cannot do calls on its own. It is not a modem.
[ 256.235861] cdc_acm 3-2:1.0: ttyACM0: USB ACM device
-
Massimo Callegari
Hi have a look at the nanodmx code (which maps a ttyACM device as well)
https://github.com/mcallegari/qlcplus/b ... anodmx.cpp
Keep in mind that not being based on a FTDI chip, you'll have to understand how to make it work and also it will work only in Linux.
Ask Eurolite for specifications...even though I can already imagine the (non) answer
https://github.com/mcallegari/qlcplus/b ... anodmx.cpp
Keep in mind that not being based on a FTDI chip, you'll have to understand how to make it work and also it will work only in Linux.
Ask Eurolite for specifications...even though I can already imagine the (non) answer
-
Massimo Callegari
Update: apparently OLA supports it:
https://wiki.openlighting.org/index.php ... DMX512_PRO
https://wiki.openlighting.org/index.php ... DMX512_PRO
-
Karri Kaksonen
Thanks for the hints. I will give it a shot as qlcplus/plugins/dmxusb/src/eurolite.cpp
If it starts working we will try it out in the theatre for a while to see if it is stable enough.
In the OLA sources the Eurolite seems to support 518 byte bulk transfers of the entire universe.
Unfortunately this is the 1st time for me coding anything in DMX. But it looks like the required info is available.
If it starts working we will try it out in the theatre for a while to see if it is stable enough.
In the OLA sources the Eurolite seems to support 518 byte bulk transfers of the entire universe.
Unfortunately this is the 1st time for me coding anything in DMX. But it looks like the required info is available.
-
Massimo Callegari
Reading around, it seems it uses the same protocol of the Enttec Open adapter.
https://groups.google.com/forum/#!topic ... e2u_murblw
If that's true, it should be easy to make it work.
I could do it in a few hours
https://groups.google.com/forum/#!topic ... e2u_murblw
If that's true, it should be easy to make it work.
I could do it in a few hours
-
Karri Kaksonen
I got to the point that the plugin is identified and it pops up on the input page in QLC+. Unfortunately I have no lights at home so I have to wait until the next time I go to the theatre in order to borrow some lights home.
I started from NanoDMX and edited in the commands for writing out the universe.
I also added a rule to udev for read/write access and the vendor and product id's to the place where the plugin is registered.
I started from NanoDMX and edited in the commands for writing out the universe.
I also added a rule to udev for read/write access and the vendor and product id's to the place where the plugin is registered.
-
Karri Kaksonen
The plugin appears to be working good enough for me. I will clean it up a bit and make a git request for merging it. Probably tomorrow or during the week-end.
-
Massimo Callegari
Hi, sounds like good news !
How did you organize the source in the end ?
Did you sublass enttecopen or nanodmx ?
How did you organize the source in the end ?
Did you sublass enttecopen or nanodmx ?
-
Karri Kaksonen
I took the nanodmx route. Perhaps it could have been done better.
On my laptop the usb's don't have dots in the name so it was not recognized at all. Like 2-1 and not 2-1.0
The widget is from DMX USB class.
I was a litle scared to add a lot of device handling code to a working enttec plugin. It could have caused problems. To make an own class for Eurolite felt safer.
The only downside was that I lost sound for some reason. It could be because I used Qt5 on my Ubuntu 14.04 64bit laptop. I now realized that I should have used Qt4.
On my laptop the usb's don't have dots in the name so it was not recognized at all. Like 2-1 and not 2-1.0
The widget is from DMX USB class.
I was a litle scared to add a lot of device handling code to a working enttec plugin. It could have caused problems. To make an own class for Eurolite felt safer.
The only downside was that I lost sound for some reason. It could be because I used Qt5 on my Ubuntu 14.04 64bit laptop. I now realized that I should have used Qt4.
-
Massimo Callegari
The dot thing sounds weird to me as I've implemented the nanodmx support exactly on a ubuntu 14.04.
Also I don't think Qt5 is related to your audio issues. It should be using ALSA, exactly as QLC+ on Qt4 did.
Anyway, ehenever you're ready, please send a PR on GitHub.
Cheers
Also I don't think Qt5 is related to your audio issues. It should be using ALSA, exactly as QLC+ on Qt4 did.
Anyway, ehenever you're ready, please send a PR on GitHub.
Cheers
-
Karri Kaksonen
Done. I also reverted back to Qt4 and the sound came back (mp3 player control in shows). Now I am designing the lights and sounds for the play. So far no problems. Already on page 28/68.
We will be running from my laptop using the branch "eurolite" on rehersals and go with Raspberry Pi2 in May when lights are stable.
We will be running from my laptop using the branch "eurolite" on rehersals and go with Raspberry Pi2 in May when lights are stable.
-
McCavity
- Posts: 2
- Joined: Wed Apr 06, 2016 9:21 pm
- Real Name: Henning Halfpap
Hi, everyone,
sorry to dig this up after over a year, but I just took the "wrong turn", too, by buying an Eurolite USB-DMX512-PRO and intending to use it on Mac OS. But before I start telling you what this post is all about I'd like to say many thanks to all of you for the great effort that went and continues to go into QLC+. I am absolutely dashed by this applications and its possibilities and I'd also like to thank all of the people involved for the effort that went into integrating the Eurolite adapter, too. I'd also like to stress that although I would really love to have support for the interface in QLC+ on MacOS, I'll not be disappointed if it doesn't work out: eventually I plan to buy an Enttec for my Mac so this'll solve my problem for sure - the Eurolite will probably be connected to a RasPi running Linux so it'll become useful there.
When I got my Eurolite today I tried it on my Mac just for curiosity. I've read this thread before so I didn't expect anything to happen since the documentation clearly states that currently support for this device is Linux only. But I also saw the source code and I figured that, since there seems to be only one source, that the code for this device should also end up in the compiled binary for the Mac - and I wondered what would happen if I tried to connect the device anyway.
So I hooked the device up to my Mac, fired up QLC+ and cautiously peeked in the Input / Output section - and in the device list there was a USB-DMX Eurolite output-only device which hasn't been there before with the device disconnected. But, as expected, that was all the success I've had so far and I have not been able to produce any real output on the device. I cross checked with Freestyler on a windows machine: the device itself is okay and communicates with my fixtures.
I assume that the following happened: due to the source code a basic support for the device is already compiled into the Mac binary, too. But due to different ways of handling devices between Linux and MacOS (which is basically a dervivate of BSD Unix "under the hood") the device only gets recognized but is not actually usable. But I wonder: what's missing so the device becomes usable in MacOS, too? I don't know if my programming skills are enough to add the Mac support on my own (I have been programming C before, but not C++, and my programming experience is from almost two decades ago) but if someone else would be interested to give it a try, too, I'd like to help as much as I can - for example by debugging, providing logs, testing, ...
I do know how to use git so I can clone a repository and create a fork and I know I'll need XCode on my Mac - but is there a step-by-step tutorial that I could walk through to set up a development environment on my Mac and compile the binary from source for the first time? Once I can compile the basic starting point (the unchanged git clone) I can start making modifications from there on my own fork.
Maybe that helps to add another Icon (an apple-shaped one
) to the list of compatibilities some time soon
Best regards from Germany,
McCavity
sorry to dig this up after over a year, but I just took the "wrong turn", too, by buying an Eurolite USB-DMX512-PRO and intending to use it on Mac OS. But before I start telling you what this post is all about I'd like to say many thanks to all of you for the great effort that went and continues to go into QLC+. I am absolutely dashed by this applications and its possibilities and I'd also like to thank all of the people involved for the effort that went into integrating the Eurolite adapter, too. I'd also like to stress that although I would really love to have support for the interface in QLC+ on MacOS, I'll not be disappointed if it doesn't work out: eventually I plan to buy an Enttec for my Mac so this'll solve my problem for sure - the Eurolite will probably be connected to a RasPi running Linux so it'll become useful there.
When I got my Eurolite today I tried it on my Mac just for curiosity. I've read this thread before so I didn't expect anything to happen since the documentation clearly states that currently support for this device is Linux only. But I also saw the source code and I figured that, since there seems to be only one source, that the code for this device should also end up in the compiled binary for the Mac - and I wondered what would happen if I tried to connect the device anyway.
So I hooked the device up to my Mac, fired up QLC+ and cautiously peeked in the Input / Output section - and in the device list there was a USB-DMX Eurolite output-only device which hasn't been there before with the device disconnected. But, as expected, that was all the success I've had so far and I have not been able to produce any real output on the device. I cross checked with Freestyler on a windows machine: the device itself is okay and communicates with my fixtures.
I assume that the following happened: due to the source code a basic support for the device is already compiled into the Mac binary, too. But due to different ways of handling devices between Linux and MacOS (which is basically a dervivate of BSD Unix "under the hood") the device only gets recognized but is not actually usable. But I wonder: what's missing so the device becomes usable in MacOS, too? I don't know if my programming skills are enough to add the Mac support on my own (I have been programming C before, but not C++, and my programming experience is from almost two decades ago) but if someone else would be interested to give it a try, too, I'd like to help as much as I can - for example by debugging, providing logs, testing, ...
I do know how to use git so I can clone a repository and create a fork and I know I'll need XCode on my Mac - but is there a step-by-step tutorial that I could walk through to set up a development environment on my Mac and compile the binary from source for the first time? Once I can compile the basic starting point (the unchanged git clone) I can start making modifications from there on my own fork.
Maybe that helps to add another Icon (an apple-shaped one
) to the list of compatibilities some time soon Best regards from Germany,
McCavity