Segmentation fault opening a qlcplus qxw file with Peperoni USBDMX21 and novation launchpad

Archive of the non-categorized posts related to the QLC+ technical support.
Please do not create new threads here, instead, use the categories above !
Post Reply
tolmino

Hi, after last git update i have some problem to open a qlcplus qxw file with Peperoni USBDMX21 and novation launchpad setted as input

i have a segmentation fault

the only way is to remove in qxw file the line with peperoni input on universe 1 (or input on universe2 with launchpad)
and after qlcplus is restarted, i can open that file.....

but there is another issue: if i insert input on peperoni now, the launchpad don't work:
in input/output panel i can see a joystick image if a click on a button and same thing on universe1 if i send a dmx input, but in virtual console the launchpad don't move!

the only way to have all working is that:
i open qlcplus
i open the qxw file without peperoni input
i go in virtual console and switch to operate mode
now i click on a launchpad button (that works)
i switch in design mode
now i can go in input/output panel and set peperoni input on universe1
i return in virtual console and reswitch to operate mode

and now work button of launchpad and dmx input together.

i attach qxw files

thanks
Attachments
TOUR_2014_con_Midi_no_peperoni_input.qxw
(55.19 KiB) Downloaded 43 times
TOUR_2014_con_Midi_e_peperoni_input.qxw
(106.52 KiB) Downloaded 40 times
Massimo Callegari

Tolmino, since your usage case is getting more complicated, you'll understand more information is required to understand what you're doing.
Especially for users who will find your posts in the future that might recognize themselves in your case.
I guess nobody will open the debug logs to understand what you're trying to do.

So, PLEASE, indicate your input/output mapping like this:
- Universe 1
- input: device
- output: device
- Universe 2
- input: device
- output: device
- etc...

Also, please indicate what each device is meant to control.
For example I don't understand why you use the Peperoni input (DMX) when your input device is a Launchpad (MIDI)

Thanks
tolmino

Hi Massimo, you are right.
I explane

Universe 1 i have peperoni input and peperoni output
Universe 2 i have launchpad in input and peperoni output.

Universe output 1 is controlling dimmers and different RGB leds
Universe output 2 is controlling different moving heads.

I use peperoni input with a DMX controller that has 24 sliders and each one has own flash button... And that is useful for control dimmer channel of moving heads, for bus speed control, etc....
And i use launchpad`s buttons for pre selected color combinations on different moving heads and led machines.

I can add another annotation: all become instable using feedback on launchpad

For now thanks
Massimo Callegari

Much clearer now, thanks.
I haven't done extensive tests on the Peperoni input (lack of time and devices) but I have a question.
If you don't connect the Launchpad, everything works fine for hours or not ?
tolmino

the problem isn't to have a working situation for hours, the problem is to open the qxw file without segmentation fault.
because after the crazy game explained before, it works for hours!

if i remove one between launchpad input or peperoni input in qxw file, qlcplus can open it without segmentation fault.

the simplest thing is to remove peperoni input, because if i remove launchpad, is too hard to reinsert it: often, when i add feedback option, qlcplus is freezing.

i hope that is useful.
thanks... Tolmino
tolmino

I know that this post is for segmentation foult, but after test of input and outputs together that we have done that evening, i can say more about ....

yes, inputs after that crazy game are working for hours, but peperoni output stop after 20 or 30 seconds that we are using launchpad and sliders in input...

and when it stop emitting signal in monitor windows there aren't no movements.
thanks...
tolmino

there is a way to debug for help you?
Post Reply