QLC+ and REAPER via MIDI... issue

[mungle]

Hello massimo and users!
I have a big issue with QLC+ and REAPER when I try to trigger some cue points vai MIDI. I made a cheaser with all my scenes and insert it in a "solo" window, inside Virtual Console. When I press play in reaper it send some notes to qlc+. One of these notes is linked with the "NEXT SCENE" button and when it is trigged the scene start. Sometimes everything works fine, sometimes all the dmx value are set to "255" missing up everything... I made a video where I show my issue. I'm sorry, it is in italian only.

Hope someone have a solution for me! THX!

https://www.youtube.com/watch?v=_t9ALuQ6j9A

[mcallegari]

Hi, it's probably better if you can share the workspace.

I'm not sure I've seen it right in the video, but apparently you've placed too many things into solo frames (thus the sudden stop of a chaser/cue list)
A solo frame with a single widget into it doesn't make much sense.
And I'm not sure, but it seems you placed 2 cue lists into 2 solo frames and those 2 solo frames into another solo frame ! It's just not correct.

You need to use solo frames when you need "exclusive" widgets (so activating one stops the others)
I think it is not your case. You can probably put everything into normal frames.

[mungle]

Thank you Massimo, maybe you are right... in the next days I will try to use a normal frame but in the meantime I found the problem I think and it happens when I exit from the operate mode and enter again... here a video: http://youtu.be/Z7Q2OPIFJqU

Thank you again!

[plugz]

Hey,

I don't see any problem happening in your video, it looks like everything works. Can you point out what the issue is exactly ?

And more importantly, as Massimo asked: Can you share your workspace file here ? We can't help much without it.

[mungle]

If you watch the video you can see that in the first try all the DMX values play correctly (with fade-in etc...), when I exit and enter again from operate mode the DMX values became 255 255 255 when the MIDI note play the Scene cheaser sequence.

Anyway massimo is right when he say that I could insert the sequences inside normal frames and avoid to insert the other 2 chasers sequences inside a SOLO frames... but I don't think it came from this the issue I had (even if I didn't try yet)

Attached you will find the QLC+ file but not the reaper one as it is a non admitted file...

Thank you for your support!

[mcallegari]

Hi, I did a quick test of your workspace.
When controlled manually, the channels behaviour seems to be always correct.
I can go to the next cue even if the current cue is fading in. The Cue list doesn't stop, and channels don't go to 255, as expected.

I confirm that you definitely don't need all those solo frames, as you correctly created Cue lists acting on different fixtures, so they won't conflict within each other.

I can only suppose the wrong behaviour has something to do with the MIDI input but unfortunately at the moment I don't have my nanoKONTROL at home (I borrowed it to a friend)
Otherwise it has something to do with the QLC+ version you're using and in the meantime we fixed something (I am always using the latest code from GIT)
From your project I see it has been created with QLC+ 4.8.5. Is that the version you're using right now ? Can you try with QLC+ 4.9.1 ?

[mungle]

Hello Massimo and plugz,
Thank you for your support. I just downloaded the 4.9.1 version and the problem still there so I decided to delete the solo frame and copy the sequence inside a normal frame. After a test trying to replicate the error everything worked fine and no error appears. After this I decided to add a solo frame again and copy the same sequence inside deleting the normal frame and after a test the error disappear... I can't answer more... I think there was a code error in the file when I built the virtual console...

[mungle]

[UPDATED]
The issue still there also with normal frame....

[mcallegari]

OK.
I'm starting to suspect this is a MIDI-related issue.
Can you actually reproduce the issue without using Reaper ? (so pushing the buttons manually)
In this way we can split the problem in 2 halves, if manually it works (just like I tried)

What kind of MIDI messages are you sending from Reaper ? Notes/CC/PC ?

[mungle]

Hello Massimo and everyone! Sorry for this delay.

You can find the reaper file here http://www.filedropper.com/testmidi and the qlc+ file attached to this post.

Here the workflow to replicate the issue:

1- Open QLC+ and Reaper files.
2- If you are mac user open "MIDI audio configuration" inside "Utility", press "cmd+2" and enable "Driver IAC"
3- Go to QLC+ Input/Output and select MIDI 1: Driver IAC
4- Everything should work. To test set QLC to "Operate Mode" pressing the top-right green play button.
5- Press play on Reaper. If the "Check Connessione" button will blink everything should work.
6- Open the "Fixture Monitor" (Heart beat icon) to see the dmx values
7- Every scene should play properly
8- Stop Reaper and switch to Design Mode inside QLC allowing the stop of the current functions.
9- Switch back to Operate Mode in QLC+
10- Press Stop and Back arrow (W for shortcuts) inside Reaper then press play
11- Inside QLC+ verify the "Check Connessione" button and open the "Fixture Monitor" to see the DMX values
12- When "Sfondo" start everything still works
13- When "Scene" start, all the scene lights became 255

This only happen in this case with MIDI even if I use normal Frame instead Solo Frame. If I play the scene manually everything works properly.

Thank you!