- Welcome to da-Share Forum.
Recent posts
#21
Feature Discussion / Background During Stage Pause
Last post by stevem - July 25, 2026, 10:10:34 AMI'm looking for help configuring cues in MultiPlay V3. I can't seem to get this to work.
I'm using MP 3.x to project video behind musical performers on stage. One video cue per song. When a video ends I want it to smoothly and automatically transition into a static image cue and wait indefinitely for the next GO command. When the next GO command is issued I want the static image to smoothly transition into the start of the next video cue and begin playing the next video, and so on and so on.
No matter what I've tried though I always get a distracting black background flash (default window bg color) during the transition between the static image and video cues. I've even tried placing the static image as the default window background in hopes that it would supersede the solid color bg but it won't redraw properly between cue changes.
I suppose I could always fade to black between songs, but I really want to be able to fade in and out of an image. Thanks!
I'm using MP 3.x to project video behind musical performers on stage. One video cue per song. When a video ends I want it to smoothly and automatically transition into a static image cue and wait indefinitely for the next GO command. When the next GO command is issued I want the static image to smoothly transition into the start of the next video cue and begin playing the next video, and so on and so on.
No matter what I've tried though I always get a distracting black background flash (default window bg color) during the transition between the static image and video cues. I've even tried placing the static image as the default window background in hopes that it would supersede the solid color bg but it won't redraw properly between cue changes.
I suppose I could always fade to black between songs, but I really want to be able to fade in and out of an image. Thanks!
#22
Bug Reports / Re: MIDI Device issues
Last post by David - July 23, 2026, 08:28:14 AMThe current logic for keyboard, MIDI and OSC triggers is to find the first match, then stop looking.
It could possibly be changed to check for the first match in Shortcuts. If found, execute and go no further as I think allowing something to trigger a shortcut and one or more cues would be undesirable.
If no match in Shortcuts found, check for all matches in Adlib and main cue lists and trigger each one it finds.
The trigger error checking would also need changing to allow for duplicates within the cue lists and list them as warnings instead.
It could possibly be changed to check for the first match in Shortcuts. If found, execute and go no further as I think allowing something to trigger a shortcut and one or more cues would be undesirable.
If no match in Shortcuts found, check for all matches in Adlib and main cue lists and trigger each one it finds.
The trigger error checking would also need changing to allow for duplicates within the cue lists and list them as warnings instead.
#23
Bug Reports / Re: MIDI Device issues
Last post by coreystup - July 23, 2026, 04:30:25 AMIn thinking about it more, why should a conflict/duplicate exist? Shouldn't it be possible for a single MIDI message to start multiple cues if needed? Especially in the case of "Any" being used.
For instance, you'd want to cue a lighting action for any NOTE ON 60, regardless of the velocity, but then you'd want another cue to be 1:1 based on the specific velocity. All from a single trigger.
The whole architecture of MultiPlay allows for multiple cues to be running, so this isn't a unique case. I get that maybe keyboard triggers should be 1:1 with a specific cue, but the "Any" case to me lends itself to be allowed to trigger both the generic (data 2 - Any) case and the specific case.
Thoughts?
For instance, you'd want to cue a lighting action for any NOTE ON 60, regardless of the velocity, but then you'd want another cue to be 1:1 based on the specific velocity. All from a single trigger.
The whole architecture of MultiPlay allows for multiple cues to be running, so this isn't a unique case. I get that maybe keyboard triggers should be 1:1 with a specific cue, but the "Any" case to me lends itself to be allowed to trigger both the generic (data 2 - Any) case and the specific case.
Thoughts?
#24
Bug Reports / Re: MIDI Device issues
Last post by coreystup - July 21, 2026, 06:32:39 PMQuote from: David on July 21, 2026, 02:10:58 PMOK, I think I see what's going on with your test example. Having MIDI triggers with the same command, channel and note number will cause a conflict when one of them is using the Any value. You should see that a red cross icon appears next to each cue to warn of the duplicate MIDI triggers. In your example the value of Any in cue one is a match for the zero value in cue two as Any can include zero.I see the conflict X now. And I guess a conflict would make sense vs relying on cue order or some other sequencing to resolve it. I assumed the first cue in the list would win, but seeing there is a visible conflict helps indicate why nothing dispatched instead of the "first to match".
Thanks for explaining!
#25
Bug Reports / Re: MIDI Device issues
Last post by David - July 21, 2026, 02:10:58 PMOK, I think I see what's going on with your test example. Having MIDI triggers with the same command, channel and note number will cause a conflict when one of them is using the Any value. You should see that a red cross icon appears next to each cue to warn of the duplicate MIDI triggers. In your example the value of Any in cue one is a match for the zero value in cue two as Any can include zero.
#26
Bug Reports / Re: MIDI Device issues
Last post by coreystup - July 21, 2026, 10:31:35 AMOn #3, I actually double checked and here's how to reproduce the bug. I DID have a second audio cue with an Midi trigger set as I was using it in testing. Here's how I have my setup.
Cue 1: NOTE ON, Data 1 - 60, Data 2 - 127
Cue 2: NOTE ON, Data 1 - 60, Data 2 - 0.
(in this order on the cue sheet)
Send a 60/127 and Cue 1 plays as expected.
Change Cue 1 to Data 2 - Any.
Send a 60/127 and no cues play.
Remove the MIDI trigger on cue 2, leaving Cue 1 set to Data 2- Any.
Send a 60/127 and cue 1 plays as it should.
Cue 1: NOTE ON, Data 1 - 60, Data 2 - 127
Cue 2: NOTE ON, Data 1 - 60, Data 2 - 0.
(in this order on the cue sheet)
Send a 60/127 and Cue 1 plays as expected.
Change Cue 1 to Data 2 - Any.
Send a 60/127 and no cues play.
Remove the MIDI trigger on cue 2, leaving Cue 1 set to Data 2- Any.
Send a 60/127 and cue 1 plays as it should.
#27
Bug Reports / Re: MIDI Device issues
Last post by coreystup - July 21, 2026, 10:21:55 AMQuote from: David on July 20, 2026, 07:16:02 PM1 - I've just tested with 2 different MIDI devices (one virtual via Loopbe and one USB) and found that selecting one or the other in Production Properties changed which one controlled MultiPlay as soon as I exited Production Properties. Not sure why it's not working for you.Thanks for checking! I did just test again and as you said it appears to be working. It may have been that I disconnected the interface or reset it while Multiplay was running, and this actually caused the other issue.
Quote from: David on July 20, 2026, 07:16:02 PM2 - I can confirm that MultiPlay will not resume a USB MIDI connection that gets disconnected and reconnected while running. There can also be a crash if you try and refresh the MIDI device list, re-select that device and exit Production Properties. I'll have to see what's possible to fix those issues.Excellent, glad you were able to duplicate it. Theres also no indicator that the MIDI input connection has been lost. I dunno if thats worth a status bar indicator or some other clue that an input is no longer connected.
Quote from: David on July 20, 2026, 07:16:02 PM3 - Setting the Data 2 value to Any seems to work for me. Maybe someone else can check too?Testing again, I have only a single audio cue that has a MIDI Trigger on it (no other cues have MIDI Triggers). I set to NOTE ON, data 1 - 60, data 2 - 127. Cue triggers. Set it to NOTE ON Data 1 - 60, data 2 - Any. Cue does not trigger, and no other cue does either (as expected as no other triggers are set). Same MIDI message sent both times from same source.
Quote from: DavidThe match found first will be the only one processed for that received MIDI command. The triggers are searched for in the Shortcuts list first, then the Adlib list, then the main cue list. As soon as a match is found the search stops.Makes sense, but this doesn't appear to affect me. I have nothing in the Shortcuts list, notthing in the Adlib list. My main cue list is short and only has the 1 audio cue in it that has the trigger set.
#28
Bug Reports / Re: MIDI Device issues
Last post by David - July 21, 2026, 06:40:43 AMWith regard to using the Any value option for Data 2, there will be an issue if another assigned trigger is also using the same MIDI command with a specific Data 2 value.
The match found first will be the only one processed for that received MIDI command. The triggers are searched for in the Shortcuts list first, then the Adlib list, then the main cue list. As soon as a match is found the search stops.
The match found first will be the only one processed for that received MIDI command. The triggers are searched for in the Shortcuts list first, then the Adlib list, then the main cue list. As soon as a match is found the search stops.
#29
Bug Reports / Re: MIDI Device issues
Last post by David - July 20, 2026, 07:16:02 PM1 - I've just tested with 2 different MIDI devices (one virtual via Loopbe and one USB) and found that selecting one or the other in Production Properties changed which one controlled MultiPlay as soon as I exited Production Properties. Not sure why it's not working for you.
2 - I can confirm that MultiPlay will not resume a USB MIDI connection that gets disconnected and reconnected while running. There can also be a crash if you try and refresh the MIDI device list, re-select that device and exit Production Properties. I'll have to see what's possible to fix those issues.
3 - Setting the Data 2 value to Any seems to work for me. Maybe someone else can check too?
2 - I can confirm that MultiPlay will not resume a USB MIDI connection that gets disconnected and reconnected while running. There can also be a crash if you try and refresh the MIDI device list, re-select that device and exit Production Properties. I'll have to see what's possible to fix those issues.
3 - Setting the Data 2 value to Any seems to work for me. Maybe someone else can check too?
#30
Bug Reports / MIDI Device issues
Last post by coreystup - July 20, 2026, 06:48:14 PMTesting on 3.0.244.0.
1 - If the MIDI device in Production Properties->Midi->Control is changed, the new device doesn't appear to be used unless you restart MultiPlay.
2 - If the MIDI device selected above disappears while MultiPlay is running, but then returns, MIDI Control triggers will no longer function. I have a USB based MIDI interface and if its disconnected and then reconnected, you have to restart MultiPlay.
3 - The "Any" value for Midi Trigger - Data 2 doesn't appear to work. Test case, send a Note On, Data 1 - 60, Data 2 - 127. Set Data 2 to "127" and it triggers fine. Set Data 2 to "Any" and no trigger.
Thanks for a great tool!
1 - If the MIDI device in Production Properties->Midi->Control is changed, the new device doesn't appear to be used unless you restart MultiPlay.
2 - If the MIDI device selected above disappears while MultiPlay is running, but then returns, MIDI Control triggers will no longer function. I have a USB based MIDI interface and if its disconnected and then reconnected, you have to restart MultiPlay.
3 - The "Any" value for Midi Trigger - Data 2 doesn't appear to work. Test case, send a Note On, Data 1 - 60, Data 2 - 127. Set Data 2 to "127" and it triggers fine. Set Data 2 to "Any" and no trigger.
Thanks for a great tool!