still having hanging note issue with Tyrell N6.
Also noticed the midi option to keep select or last note drawn length to draw new note option is broken : new note length is always 1/16 + a couple of tics length.
Also noticed the midi option to keep select or last note drawn length to draw new note option is broken : new note length is always 1/16 + a couple of tics length.
Nope, works just fine over here.
Also what are you doing with Tyrell to make it hang? I can't make it hang notes over here, even in a loop.
Also what are you doing with Tyrell to make it hang? I can't make it hang notes over here, even in a loop.
Tyrell hangs when i'm in loop mode and adjust some parameters : volume or filter envelope decay, release, Filter cut off, X mod osc1 depth...
This only happens in Reaper, tested in Bitwig, live, Logic, Studio one.
I tried 5.90 RC2 this evening and within 30 mn, I got 3 hanging notes.
I had to hit F10 of stop Reaper to stop tyrell Playing.
3 hanging notes within 30 minutes is not a consistent case for reproduction of the issue unfortunately... Try to find a sure-fire way to trigger hanging notes and only then it can be looked at more closely...
3 hanging notes within 30 minutes is not a consistent case for reproduction of the issue unfortunately... Try to find a sure-fire way to trigger hanging notes and only then it can be looked at more closely...
If notes hang after looping for 30 minutes every time then it is consistent.
Do you have authority over what issues get fixed?
@dupont, can you isolate the behavior to a specific condition that can be replicated? To ED's point, it's difficult to validate your finding without very explicit directions on how to reproduce the bug.
Good update, everything works fine. prompt, how to disable the option for plugins "Hard Reset on Playback start" by default? On several VSTi, in particular Omnisphere and Kontakt, with this option enabled, if you press fast stop/start, ingested notes, so I would disable it by default.
v5.90rc2 - May 15 2018
[*]+ Performance: make automatic worker scheduling slightly more aggressive
May I ask what the background of this is? It is related to the thread behaviour settings in buffer prefs I guess?
Does it affect the Automatic setting?
Also noticed the midi option to keep select or last note drawn length to draw new note option is broken : new note length is always 1/16 + a couple of tics length.
3 hanging notes within 30 minutes is not a consistent case for reproduction of the issue unfortunately... Try to find a sure-fire way to trigger hanging notes and only then it can be looked at more closely...
I tried to reproduced the bug, it happens but at random and never when I tweak the same plugin parameters, arghhh.
just move edit cursor to different position while a note is playing and it will sustain until you force a note off.
I don't have a lot of synths installed right now but some others do the same thing
- PG-8X, OBXD, ReaSynth, Audio Damage Basic, AIR Xpand2, Kontakt 5
Some that reset on transport position change/note off at stop
- Addictive Keys, IK Syntronik
simple solution would be to always send note off at transport stop.
edit - portable install of 5.78 is different with ReaSynth, it's stopping when I move cursor so maybe problem is in my preferences because I've had this problem with some plugins forever
__________________
REAPER Video Tutorials, Tips & Tricks and more at The REAPER Blog
Last edited by EpicSounds; 05-16-2018 at 02:38 PM.
Reason: further testing
So that might actually be an issue in the plugin, not within Reaper.
Isn't that somewhat an excuse for insufficient programing? "Somebody else's fault, not mine?" Shouldn't a program like Reaper be smart enough to to check for plugin errors like hanging notes, and self correct? Surely something can be done so that DAW is smarter than plugins, and doesn't go crazy if plugin does a mistake. Couldn't a DAW "grab hold" of a plugin, and stay solid no matter what nonsense plugin is spitting out?
edit - portable install of 5.78 is different with ReaSynth, it's stopping when I move cursor so maybe problem is in my preferences because I've had this problem with some plugins forever
Yeah doesn't happen over here. Not with ReaSynth, nor with Tyrell or PG-8X.
Audio->MIDI Devices->Reset by: [x] All-notes-off [x] Pitch/sustain Reset on: [ ] Play [x] Stop/stopped seek
Audio->Playback->[ ] Flush FX when looping
Plugins->VST->[ ] Don't flush synthesizer plugins on stop/reset
Plugins->VST->[ ] Don't send note-offs or pitch reset messages on stop/reset
Isn't that somewhat an excuse for insufficient programing? "Somebody else's fault, not mine?" Shouldn't a program like Reaper be smart enough to to check for plugin errors like hanging notes, and self correct? Surely something can be done so that DAW is smarter than plugins, and doesn't go crazy if plugin does a mistake. Couldn't a DAW "grab hold" of a plugin, and stay solid no matter what nonsense plugin is spitting out?
How would DAW know what is "nonsense" and what is correct output from a plugin? In any case, a plugin wouldn't create hung notes unless it's a MIDI processing plugin - VSTi usually don't output MIDI (and if they do, you're not hearing that unless you route that MIDI coming from the plugin out to another plugin).
In any case, this more and more looks to me like a preferences issue than anything else. I literally don't recall when I got hung notes in Reaper... could be years ago. And I have quite a number of VSTi...
On some VSTi if you change the position of the cursor during playback, a desynchronization occurs, which is restored through time. In version 5.80 everything works fine.
Edit: Returned the option "Hard reset on playback start", set the settings as advised EvilDragon, problems with the desynchronization disappeared.
Edit 2: But with the option "Hard reset on playback start" enabled, if you quickly press STOP/START, Omnisphere swallows notes
Isn't that somewhat an excuse for insufficient programing? "Somebody else's fault, not mine?" Shouldn't a program like Reaper be smart enough to to check for plugin errors like hanging notes, and self correct?
From what I know, Reaper does this, but it has no chance if the plugin won't 'listen'. It's like in real life; if you talk to somebody and he's reluctant to listen to you, you can't do anything.
Quote:
Originally Posted by EvilDragon
In any case, this more and more looks to me like a preferences issue than anything else.
IIRC there somewhere was another discussion where a similar problem with some VSTi occurred and Justin wrote that he couldn't do anything more than to built in a 'hard reset' option for such cases, but if the plugin doesn't react to even this, there's no other way to tell it to do what it should.
Hi I found a bug regarding quantisation that I don't remember seeing in previous versions...
Here's a way to reproduce it:
- Select grid display as 1/8 Triplets
- Draw some notes in the MIDI Editor
- Select some of them, hit Quantize, select 1/8 Triplets
- It works as expected and notes align to the 1/8 Triplets gridline.
- Hit ok and close the Quantize window.
- Open the Quantize window again, and now it remembers that the last chosen setting is 1/8 triplets, BUT in reality it it quantising to 1/8 straight, even though the menu is showing 1/8 Triplets.
Here's a video example of what's happening:
Thanks for your help!
-t
__________________
MacOS 10.15.7
Mac Pro 6-Core - 64GB ram
Motu M4
Hi I found a bug regarding quantisation that I don't remember seeing in previous versions...
Here's a way to reproduce it:
- Select grid display as 1/8 Triplets
- Draw some notes in the MIDI Editor
- Select some of them, hit Quantize, select 1/8 Triplets
- It works as expected and notes align to the 1/8 Triplets gridline.
- Hit ok and close the Quantize window.
- Open the Quantize window again, and now it remembers that the last chosen setting is 1/8 triplets, BUT in reality it it quantising to 1/8 straight, even though the menu is showing 1/8 Triplets.
Here's a video example of what's happening:
Thanks for your help!
-t
I'm on v5.81pre10 and I can reproduce that.
[MOAN] Apart from that bug, there could be more actions and features for quantisation. Quantization presets? Quantise strength via MIDI/Mousewheel/OSC? Quantize note positions to 1/12, 1/24 etc (currently only straight values exist) [/MOAN]
[MOAN] Apart from that bug, there could be more actions and features for quantisation. Quantization presets? Quantise strength via MIDI/Mousewheel/OSC? Quantize note positions to 1/12, 1/24 etc (currently only straight values exist) [/MOAN]
Thank you Stroudy,
So maybe I just didn't notice it before, I'm working on a piece that has a lot of triplets and that's why I came across this behaviour.
I also don't understand why sometimes, upon closing and reopening the Quantize window, Reaper remembers the last quantization values used (as I think it should) and sometimes it forgets (it happens in my video as well, when it reverts back to 1/8 straight).
Devs, if it doesn't concern this prerelease thread I'll post it in the Bug reports section, no problem.
Thanks again
-t
__________________
MacOS 10.15.7
Mac Pro 6-Core - 64GB ram
Motu M4
From what I know, Reaper does this, but it has no chance if the plugin won't 'listen'. It's like in real life; if you talk to somebody and he's reluctant to listen to you, you can't do anything.
That quote made my day
@sonicowl
There are so many gazillion ways of f**ing up communication on the plugin-side. Like deprecated standards, that aren't used anymore. Or that are badly implemented due bugs, lack of knowledge on the programmer's side or just plain human faults.
This is an endless stream of possible variations of problems and there's no way, that the Reaper-Devs would be able to catch them good enough without testing all plugins under all circumstances all the time with every new version of Reaper.
They probably could do it. With thousands of testers, who test all(!) plugins, which costs a lot of money and would make Reaper as expensive as a multibillion-dollar-yacht.
Each license, of course.
It's much faster(and cheaper) to complain and bugreport to the plugin-developer, that they should get their plugin right, because after all, they want it to be used, right...
Isn't that somewhat an excuse for insufficient programing? "Somebody else's fault, not mine?" Shouldn't a program like Reaper be smart enough to to check for plugin errors like hanging notes, and self correct? Surely something can be done so that DAW is smarter than plugins, and doesn't go crazy if plugin does a mistake. Couldn't a DAW "grab hold" of a plugin, and stay solid no matter what nonsense plugin is spitting out?
I agree with that. If that's a plugin issue, so why this plugin is working fine inside every other DAWs !