Thread: [Qtractor-devel] NoteOffs don't get sent on additional MIDI channels?
An Audio/MIDI multi-track sequencer
Brought to you by:
rncbc
Menu
▾
▴
qtractor-devel
|
From: Frank N. <bea...@we...> - 2015-10-04 09:59:51
|
Hi list,
not sure if this is intended behaviour or a bug, so I am asking this here first -
I created a small "song" with 2 MIDI tracks.
The first tracks plays out to "Master MIDI", the second is using an additional
MIDI bus ("Supernova") I have created via the "View->Buses" dialog.
Both tracks have a small MIDI clip, both play out fine. However, when I stop
playback via the <space bar> key, the notes played on the second track don't
get stopped.
I see from the "aseqdump" output that the respective messages do not get sent
when I stop playback.
Dumping output on "Master MIDI" bus:
[playback is running]
...
130:0 Note on 0, note 62, velocity 23
130:0 Note on 0, note 67, velocity 23
130:0 Note on 0, note 71, velocity 23
[pressing space bar here]
130:0 Control change 0, controller 120, value 0 (All Sound Off)
130:0 Control change 0, controller 123, value 0 (All Notes Off)
130:0 Control change 0, controller 121, value 0 (Reset All Controllers)
-> All sounds are off
Dumping output on "Supernova" bus:
[playback is running]
...
130:1 Note on 0, note 50, velocity 64
130:1 Note off 0, note 50, velocity 0
130:1 Note on 0, note 55, velocity 64
130:1 Note off 0, note 55, velocity 0
130:1 Note on 0, note 43, velocity 64
130:1 Note off 0, note 43, velocity 0
130:1 Note on 0, note 50, velocity 64
[pressing space bar here]
[no additional MIDI output here, but "stuck" notes are still being heard]
Only when I press the "Panic" button, I see the expected:
130:1 Control change 0, controller 120, value 0
130:1 Control change 0, controller 123, value 0
130:1 Control change 0, controller 121, value 0
Rui, this looks like a bug, right? Or can I somehow adjust that behaviour
"per bus"?
Thanks,
Frank
|
|
From: Ralf M. <ral...@al...> - 2015-10-04 10:39:34
|
Perhaps you should mention what version you're using ;). $ qtractor -v Regards, Ralf |
|
From: Frank N. <bea...@we...> - 2015-10-04 11:13:29
|
Hi, > Perhaps you should mention what version you're using ;). > > $ qtractor -v Right, sorry about that. Following Git pretty closely, this is 0.7.0.30. Greetings, Frank |
|
From: Rui N. C. <rn...@rn...> - 2015-10-04 11:17:27
|
hi Frank, On 10/04/2015 10:59 AM, Frank Neumann wrote: > > Dumping output on "Supernova" bus: > [playback is running] > ... > 130:1 Note on 0, note 50, velocity 64 > 130:1 Note off 0, note 50, velocity 0 > 130:1 Note on 0, note 55, velocity 64 > 130:1 Note off 0, note 55, velocity 0 > 130:1 Note on 0, note 43, velocity 64 > 130:1 Note off 0, note 43, velocity 0 > 130:1 Note on 0, note 50, velocity 64 > [pressing space bar here] > [no additional MIDI output here, but "stuck" notes are still being heard] > > Only when I press the "Panic" button, I see the expected: > 130:1 Control change 0, controller 120, value 0 > 130:1 Control change 0, controller 123, value 0 > 130:1 Control change 0, controller 121, value 0 > > Rui, this looks like a bug, right? Or can I somehow adjust that behaviour > "per bus"? > yes, you're probably right, the three CC's 120, 123 and 121 should have been qlwo sent to 2nd bus (Supernova; port 130:1) when playback stops, not only when you hit "panic"! i'll have to confirm this bbl. cheers -- rncbc aka. Rui Nuno Capela |
|
From: Rui N. C. <rn...@rn...> - 2015-10-04 11:19:28
|
On 10/04/2015 12:17 PM, Rui Nuno Capela wrote:
>> ...
>> Rui, this looks like a bug, right? Or can I somehow adjust that behaviour
>> "per bus"?
>>
>
> yes, you're probably right, the three CC's 120, 123 and 121 should have
> been qlwo sent to 2nd bus (Supernova; port 130:1) when playback stops,
^^^^
also
> not only when you hit "panic"!
>
--
rncbc aka. Rui Nuno Capela
|
|
From: Rui N. C. <rn...@rn...> - 2015-10-04 19:15:35
|
On 10/04/2015 12:19 PM, Rui Nuno Capela wrote: > > On 10/04/2015 12:17 PM, Rui Nuno Capela wrote: >>> ... >>> Rui, this looks like a bug, right? Or can I somehow adjust that behaviour >>> "per bus"? >>> >> >> yes, you're probably right, the three CC's 120, 123 and 121 should have >> been qlwo sent to 2nd bus (Supernova; port 130:1) when playback stops, > ^^^^ > also >> not only when you hit "panic"! >> hi Frank, i'm not seeing to reproduce this behavior: a) stopping playback does send CC#120 (all sound off) and CC#123 (all notes off) on all playing MIDI output buses from their respective MIDI track/channels. b) panic does the same as a), with an additional CC#121 (all controllers off) being sent as well. is there anything i'm missing? cheers -- rncbc aka. Rui Nuno Capela |
|
From: Rui N. C. <rn...@rn...> - 2015-10-06 10:11:45
|
On 2015-10-04 10:59, Frank Neumann wrote:
> Hi list,
>
> not sure if this is intended behaviour or a bug, so I am asking this
> here first -
>
> I created a small "song" with 2 MIDI tracks.
> The first tracks plays out to "Master MIDI", the second is using an
> additional
> MIDI bus ("Supernova") I have created via the "View->Buses" dialog.
>
> Both tracks have a small MIDI clip, both play out fine. However, when I
> stop
> playback via the <space bar> key, the notes played on the second track
> don't
> get stopped.
>
> I see from the "aseqdump" output that the respective messages do not
> get sent
> when I stop playback.
>
> Dumping output on "Master MIDI" bus:
> [playback is running]
> ...
> 130:0 Note on 0, note 62, velocity 23
> 130:0 Note on 0, note 67, velocity 23
> 130:0 Note on 0, note 71, velocity 23
> [pressing space bar here]
> 130:0 Control change 0, controller 120, value 0 (All Sound
> Off)
> 130:0 Control change 0, controller 123, value 0 (All Notes
> Off)
> 130:0 Control change 0, controller 121, value 0 (Reset
> All Controllers)
>
> -> All sounds are off
>
> Dumping output on "Supernova" bus:
> [playback is running]
> ...
> 130:1 Note on 0, note 50, velocity 64
> 130:1 Note off 0, note 50, velocity 0
> 130:1 Note on 0, note 55, velocity 64
> 130:1 Note off 0, note 55, velocity 0
> 130:1 Note on 0, note 43, velocity 64
> 130:1 Note off 0, note 43, velocity 0
> 130:1 Note on 0, note 50, velocity 64
> [pressing space bar here]
> [no additional MIDI output here, but "stuck" notes are still being
> heard]
>
> Only when I press the "Panic" button, I see the expected:
> 130:1 Control change 0, controller 120, value 0
> 130:1 Control change 0, controller 123, value 0
> 130:1 Control change 0, controller 121, value 0
>
> Rui, this looks like a bug, right? Or can I somehow adjust that
> behaviour
> "per bus"?
>
hi
it is/was a very old "bug/feature" indeed...
it dealt with not setting an MIDI track's instrument name
properly--leaving it at "(No instrument)" was the culprit ever since...
ever?
i even remember you asked something about this back in the days, some
8years+ ago, for which i replied that the all-shut-up messages were only
sent iif there was an instrument defined on the track/channel...
nevermind, it's hopefully fixed on git head (master) now aka.
qtractor-0.7.0.33+
http://sourceforge.net/p/qtractor/code/ci/ed2f56
http://github.com/rncbc/qtractor/commit/ed2f561
byee
--
rncbc aka. Rui Nuno Capela
|
|
From: Frank N. <bea...@we...> - 2015-10-06 21:26:14
|
Hi Rui, [..] > > Rui, this looks like a bug, right? Or can I somehow adjust that > > behaviour > > "per bus"? > > > it is/was a very old "bug/feature" indeed... > > it dealt with not setting an MIDI track's instrument name > properly--leaving it at "(No instrument)" was the culprit ever since... > ever? > > i even remember you asked something about this back in the days, some > 8years+ ago, for which i replied that the all-shut-up messages were only > sent iif there was an instrument defined on the track/channel... > > nevermind, it's hopefully fixed on git head (master) now aka. > qtractor-0.7.0.33+ > http://sourceforge.net/p/qtractor/code/ci/ed2f56 > http://github.com/rncbc/qtractor/commit/ed2f561 Great :-). Confirmed, looking good now. At least in my little example setup with 2 MIDI busses, no more stuck notes are heard upon playback stop. BLB++ ;-). Greetings, Frank |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X