Errors on version 3.2.2?

69 views
Skip to first unread message

Waschfeld, Maik

unread,
Nov 25, 2016, 7:34:06 PM11/25/16
to ql...@googlegroups.com

Hi QLab-Team,

 

With QLab v.3.2.2:

-          it still warns „Disarm cues require a license.“ on a ProBundle-licensed machine.

-          Opening a project on another machine with different attached hardware, I get “Invalid MIDI destination.”-errors on every MIDI-File cue, even when I’m readdressing another MIDI-Out to that MIDI File Patch 1 (RME HDSPe to IAC-Bus)  in the Workspace Settings.

When I just select the MIDI Destination in the Settings-Tab of the cue, the error disappears. But I have to do that on every MIDI-File cue.

Can anybody confirm?

 

 

Regards…

 

…Maik Waschfeld

 

 

Chris Ashworth

unread,
Nov 25, 2016, 7:43:04 PM11/25/16
to Waschfeld, Maik, ql...@googlegroups.com
Hi Maik,

Hi QLab-Team,

 

With QLab v.3.2.2:

-          it still warns „Disarm cues require a license.“ on a ProBundle-licensed machine.


-          
Opening a project on another machine with different attached hardware, I get “Invalid MIDI destination.”-errors on every MIDI-File cue, even when I’m readdressing another MIDI-Out to that MIDI File Patch 1 (RME HDSPe to IAC-Bus)  in the Workspace Settings.

When I just select the MIDI Destination in the Settings-Tab of the cue, the error disappears. But I have to do that on every MIDI-File cue.

Can anybody confirm?

If you change the patch in setting, save, close, and re-open the file, are the cues still broken?

-C

Maik Waschfeld

unread,
Nov 25, 2016, 10:42:37 PM11/25/16
to ql...@googlegroups.com
Hi Chris,

Thank you for the quick response!

The „Disarm cues require a license.“-problem was solved with the QLab-3.2.3-b2-version.

The MIDI-file-problem was solved with your save and re-open-cure.

Happy again!!!


With kindest regards…
…Maik Waschfeld


Chris Ashworth

unread,
Nov 26, 2016, 11:43:42 AM11/26/16
to Maik Waschfeld, ql...@googlegroups.com
Hi Maik,


Hi Chris,

Thank you for the quick response!

The „Disarm cues require a license.“-problem was solved with the QLab-3.2.3-b2-version.


Great - glad that one was fixed.


The MIDI-file-problem was solved with your save and re-open-cure.


Cool — I’ll add your description of the original problem to the issue list to investigate if (for example) assigning the new patch is failing to notify the cues of the change.

Best,
C

Chris Ashworth

unread,
Nov 27, 2016, 7:05:16 PM11/27/16
to Waschfeld, Maik, ql...@googlegroups.com
Hi again Maik,

Just a follow-up on this: 

I’ve had a chance to review the code tonight and did find a bug in the MIDI File cue (the MIDI cue was working correctly. 

This will be fixed in the next release; thanks for the catch!

-C

Maik Waschfeld

unread,
Nov 28, 2016, 4:28:19 AM11/28/16
to ql...@googlegroups.com
HI Chris,

I’ve had a chance to review the code tonight and did find a bug in the MIDI File cue (the MIDI cue was working correctly. 

This will be fixed in the next release; thanks for the catch!

Thanks very much for the fix and the notification!
Reply all
Reply to author
Forward
0 new messages