Go Back   Cockos Incorporated Forums > REAPER Forums > REAPER Bug Reports

Reply
 
Thread Tools Display Modes
Old 11-28-2012, 02:45 PM   #1
Banned
Human being with feelings
 
Banned's Avatar
 
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
Default All-notes-off MIDI command sent regardless of preference (FIXED)

REAPER sends 'all-note-off' commands to external MIDI devices on stop, even when the setting in Preferences > Audio > MIDI Devices [sic!] for "On stop/play: Send all-notes-off" is disabled. See this video (2.1mb QuickTime .mov) illustrating the problem.

Bug Report here, please vote if you can reproduce and care to have it fixed.
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ

Last edited by Banned; 11-28-2012 at 02:55 PM.
Banned is offline   Reply With Quote
Old 11-28-2012, 02:57 PM   #2
EvilDragon
Human being with feelings
 
EvilDragon's Avatar
 
Join Date: Jun 2009
Location: Croatia
Posts: 24,798
Default

Confirmed.
EvilDragon is offline   Reply With Quote
Old 12-29-2012, 02:01 AM   #3
danfuerth
Human being with feelings
 
Join Date: Mar 2012
Posts: 1,824
Default

confirmed 100% with the Midiox logs.
danfuerth is offline   Reply With Quote
Old 12-29-2012, 04:48 AM   #4
gofer
-blänk-
 
gofer's Avatar
 
Join Date: Jun 2008
Posts: 11,359
Default transfer from tracker IID4501

Quote:
Originally Posted by Banned
<3 MIDI love bump! <3

(Seriously, am I the only one? Please vote if you can reproduce.)
Quote:
Originally Posted by EvilDragon
I can't believe I'm the only one who voted as reproducible.
Quote:
Originally Posted by danfuerth
reproduced here

Windows 8 x64

Confirmed 100% with Midiox

Really weird.
andsomechar
gofer is offline   Reply With Quote
Old 04-08-2013, 07:50 PM   #5
Justin
Administrator
 
Justin's Avatar
 
Join Date: Jan 2005
Location: NYC
Posts: 15,737
Default

Just to confirm, it only sends it when a track has its output routed to the hardware? Because these get sent at the track level, and not the hardware level (i.e. if you put a midi logger on a track, you'll see it gets the all notes off messages as well).

I'll add an option for this -- in the mean time, if the "run FX when stopped" option is off (in prefs/audio), and not set to flush fx on stop, it should prevent these from being sent.

Same should probably go for the pitch resets that get sent to the track as well, eh?

Last edited by Justin; 04-08-2013 at 07:59 PM.
Justin is offline   Reply With Quote
Old 04-09-2013, 01:09 AM   #6
EvilDragon
Human being with feelings
 
EvilDragon's Avatar
 
Join Date: Jun 2009
Location: Croatia
Posts: 24,798
Default

Same should go for any kind of reset IMHO, Justin. Why a separate option for this when you could just make the regular MIDI reset checkboxes be valid for hardware outputs?
EvilDragon is offline   Reply With Quote
Old 04-17-2013, 06:31 AM   #7
Banned
Human being with feelings
 
Banned's Avatar
 
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
Default

Quote:
Originally Posted by Justin View Post
Just to confirm, it only sends it when a track has its output routed to the hardware? Because these get sent at the track level, and not the hardware level (i.e. if you put a midi logger on a track, you'll see it gets the all notes off messages as well).

I'll add an option for this -- in the mean time, if the "run FX when stopped" option is off (in prefs/audio), and not set to flush fx on stop, it should prevent these from being sent.

Same should probably go for the pitch resets that get sent to the track as well, eh?
(And from bug report thread: )
Quote:
Originally Posted by Justin
I posted in the discussion thread, but in short these are actually sent at the track level. Need to sort out the best way to handle sending all notes off and pitch resets on stop; removing it at the track level could greatly affect the way plug-ins behave etc, so it will take some care to fix (whether this should be an option or not is TBD).
(Sorry for the late response...)

Indeed, they happen at the track level; REAPER also sends such note-off commands when a track does not have a MIDI Hardware Output set up in its I/O settings. But that is not clear from the context, while the all note-off setting seems to be dysfunctional: it is always enabled, making the preference either broken or redundant.

I think I agree with ED that we wouldn't necessarily need any additional preference for this one to distinguish between internal and external MIDI routings (if I understand him correctly - I'm not aware of any "regular MIDI reset checkboxes" other than these ones and the one in Media > MIDI: "Send all-notes-off when un-record-arming a track").

Perhaps what's confusing me most here, is the placement of these options in Preferences > Audio > MIDI Devices. Of course the "Audio" bit there is already a clue that the menu structure does not always accurately reflect the appropriate context for the individual settings, but I would still assume that "MIDI Devices >MIDI hardware settings" context actually means that the preference works for external MIDI output.

So, I would suggest moving all preferences which are related to MIDI out of the Audio section, into a dedicated section for Preferences > MIDI, and move all preferences which are not exclusive to external MIDI devices to a general subsection.

(For a slightly related example: I would *love* to see an option to reconfigure the mute / solo functions on tracks containing MIDI to use MIDI note-off commands instead of abruptly cutting off audio.)

As to pitch and CC# resets: these also work at the track level, but disabling them works as expected (unlike disabling note-offs).

However, they're useless to me. I typically do not want any pitch bend resets on stop - if I want resets at all, I want them on *start* (and/or perhaps on loading a new project). When pressing stop, MIDI instruments are typically still playing the release stages of envelopes on the notes that have been stopped (i.e. have received note-off commands), and resetting any pitch bend (or CC#) that was applied before is simply not musically useful to me at all - in my book, although not technically a bug, that is quite a severe design flaw. And much the same goes for CC#s. But that also adds insult to injury by sending 'standard' CC#s for volume (coarse only - no option for 14 bit mode), pan (coarse only - same), reverb send level (why this one only?), and hold pedal, without any way to configure them (e.g. set up which CC#s to reset, and which 'default' values to reset to). They really just get in my way, and tell me "REAPER doesn't 'get' MIDI".

Outright silly, imho, is resetting these CC#s and pitch bend during *pause*. I seriously can't even imagine any workflow where this would be useful (I'd like to hear of such a use case, if any).

Indeed, we should really sort out the best way to handle sending events like all notes-off, pitch bend, and CC# events on start/pause/stop. Imho these issues should better be discussed with related issues like event chasing (and perhaps not only for MIDI, but also including automation), than under the header of external MIDI hardware I/O settings. Indeed, changing anything could greatly affect the way plug-ins behave, but that is also exactly what I want to achieve. Imho, these options currently are simply an unusable mess, for plug-ins just as well as for external MIDI. So I'd love to discuss any possible improvements.
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ

Last edited by Banned; 04-19-2013 at 10:13 AM.
Banned is offline   Reply With Quote
Old 10-01-2013, 04:31 AM   #8
EvilDragon
Human being with feelings
 
EvilDragon's Avatar
 
Join Date: Jun 2009
Location: Croatia
Posts: 24,798
Default

Bump for importance. Devs, let's discuss this and fix this annoying issue.
EvilDragon is offline   Reply With Quote
Old 10-03-2013, 05:58 PM   #9
Studio Tan
Human being with feelings
 
Studio Tan's Avatar
 
Join Date: Aug 2013
Posts: 215
Default

I am having a problem with this also.

And it sends off message when I loop within the project.

I thought an easy fix would just be to loop from, say, measure 2...but alas, same problem.
Studio Tan is offline   Reply With Quote
Old 01-02-2014, 10:32 AM   #10
dr.squ
Human being with feelings
 
Join Date: Dec 2013
Location: Switzerland
Posts: 13
Default

Quote:
Originally Posted by Studio Tan View Post
I am having a problem with this also.

And it sends off message when I loop within the project.

I thought an easy fix would just be to loop from, say, measure 2...but alas, same problem.
At me same !

I changed from old Logic to Reaper. The only anyoing is the "All-Notes-Off" in loop mode. It needs a checkbox like the checkboxes in preferences for start/stop.

Please build in a checkbox for disable "All-Notes-Off" in loop mode.
Usually it's enough to push panic (F3) manually.
dr.squ is offline   Reply With Quote
Old 01-03-2014, 06:03 AM   #11
dr.squ
Human being with feelings
 
Join Date: Dec 2013
Location: Switzerland
Posts: 13
Default

If Tracks are in Solo-Mode, than its doesn't sends "All-Notes-Off" ...
dr.squ is offline   Reply With Quote
Old 07-12-2014, 04:43 AM   #12
jazznfunk
Human being with feelings
 
Join Date: Aug 2012
Location: Riga Latvia
Posts: 194
Default

Not confirmed on solo mode.

I use Reaper in live setup. Loops, backs and click is multichanneled out of my RME, also seperate outs from VSTi, played live by me. Very handy and nice!

I start track from region manager, at the end of this track i have !1016 defined marker (stop) to do not play next song in timeline w/out my command. Then i select next desired track in region manager, hit 'space' and so on, You got the idea. So far so good.

We often play some tails at the ends of songs, and there this "send all notes off" problem hits in.

But most interesting is this: When i hold fingers on MIDI keys (notes from MIDI key is being sending) when cursor passes !1016 'stop' marker, playback stops, and VSTi keeps sounding as desired. BUT. When this last chord is on sustain with no palms on MIDI keys, VSTi stops at !1016 'stop' marker. And it is "send all notes off" sign. Because VSTi i use (Alicias Keys) plays some release key noises, soundboard resonanses, as usual at situation that kind.

Yes, in reaper settings all "send notes off" is disabled.
jazznfunk is offline   Reply With Quote
Old 08-16-2014, 07:20 AM   #13
FlavioB
Human being with feelings
 
Join Date: May 2014
Posts: 31
Default Another victim...

... of this annoying bug. Please fix it asap!
I'm trying to play from my MIDI external keyboard through Reaper which is simply playing a drum loop: no way to have this thing sorted out, each time the loop begins from start, my notes get cut-off!!!

Thanks,
F.
FlavioB is offline   Reply With Quote
Old 01-25-2015, 05:08 AM   #14
mezzo
Human being with feelings
 
Join Date: Sep 2014
Posts: 28
Default

Yes,when I imported midi loop from Stylus (and many other),move cursor to start
item and play,sound does not begin from start of loop.And in "loop mode" cut
play every time at the starts of loop (((.
This is not in any other DAW (((.
mezzo is offline   Reply With Quote
Old 06-14-2015, 03:38 AM   #15
ivansc
Human being with feelings
 
Join Date: Aug 2007
Location: Near Cambridge UK and Near Questembert, France
Posts: 22,754
Default

Bump to remind the devs this needs fixing.
ivansc is offline   Reply With Quote
Old 10-28-2015, 02:56 AM   #16
Bollani73
Human being with feelings
 
Join Date: Mar 2015
Posts: 2
Default Another Victim!!!

Please fix it!!!
Bollani73 is offline   Reply With Quote
Old 10-28-2015, 03:11 AM   #17
EvilDragon
Human being with feelings
 
EvilDragon's Avatar
 
Join Date: Jun 2009
Location: Croatia
Posts: 24,798
Default

Quote:
Originally Posted by Justin View Post
I'll add an option for this
2 years later... still no option?


May I suggest a matrix of checkboxes here?


Code:
                   Start  Pause  Stop  Loop
All-Notes-Off                      x
Reset Pitch Bend     x
Reset CC             x
Seems like this would take care of everything. We don't need those stinking resets when looping (or pause)!

Last edited by EvilDragon; 10-28-2015 at 03:32 AM.
EvilDragon is offline   Reply With Quote
Old 10-28-2015, 11:57 AM   #18
EvilDragon
Human being with feelings
 
EvilDragon's Avatar
 
Join Date: Jun 2009
Location: Croatia
Posts: 24,798
Default

v5.05pre13 deals with this, can you fucking believe it?!
EvilDragon is offline   Reply With Quote
Old 10-28-2015, 06:54 PM   #19
ivansc
Human being with feelings
 
Join Date: Aug 2007
Location: Near Cambridge UK and Near Questembert, France
Posts: 22,754
Default

A small, cautiously reserved frightfully British "yay"...

Pending trying it out.
ivansc is offline   Reply With Quote
Old 01-18-2016, 02:52 PM   #20
TauTau
Human being with feelings
 
Join Date: Feb 2011
Posts: 130
Default

is there a fix yet? I still have that "B0 7B 00" message after some hand drawn notes in the raw view, and it confuses my device...
TauTau is offline   Reply With Quote
Old 10-17-2016, 03:23 AM   #21
Guod3
Human being with feelings
 
Guod3's Avatar
 
Join Date: Jan 2008
Posts: 506
Default

Looping kills held notes each time the playback head hits the start of the loop.
This is on external hardware midi synth.
Has this been fixed?
If so, how do I change this setting?
If not, why not? :-(
Thx
Guod3 is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 11:43 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.