|
|
|
01-25-2018, 01:35 PM
|
#1
|
Human being with feelings
Join Date: Oct 2007
Location: Lincoln, UK
Posts: 7,942
|
v5.71pre15 - January 25 2018
v5.71pre15 - January 25 2018
+ MusicXML: fix manual quantizing after import [t=202244]
+ VST3: prevent multichannel plugins from running in mono on stereo tracks [p=1945285]
# MIDI: display either 14-bit or associated MSB lane in arrange view, not both
>
|
|
|
01-25-2018, 01:51 PM
|
#2
|
Human being with feelings
Join Date: Oct 2008
Location: Right Hear
Posts: 15,618
|
Oh so good thanks much off to get and test
for sure the xml thing is FIXED!
pretty soon we'll be able to provide some examples and
documentation about some notation issues but for the moment
WE ARE HAPPY CAMPERS
Last edited by hopi; 01-25-2018 at 02:03 PM.
|
|
|
01-25-2018, 11:41 PM
|
#3
|
Human being with feelings
Join Date: May 2017
Posts: 981
|
Hi,
The VST3 Channel bug still exists. I have attached 3 videos. First I show Ver 5.6 where you can see no bug with the IOSONO anymix Panner.
https://www.dropbox.com/s/kl2n1v3mi8...20Bug.mov?dl=0
Second I show IOSONO bug in pre 15. The moment I split a file the channel settings are wrong. This didnt happen in Ver 5.6. this is something that started happening since Ver 5.7.
https://www.dropbox.com/s/yhp9h1hsgc...20Bug.mov?dl=0
Third: With Exponential audio plugins when I insert the plugin in a 5.1 track where I only have 4 channels of data on channels 1 (Left), 2(Right), 5(Left surround), 6 (Right surround). In this scenario reaper is sending input to the plugin to 1 (Left), 2(Centre), 3(Right), 4(Lfe). This is not right. It should send inputs to the plugin correctly. The blue meters that you see in the plugin are the inputs. Ideally reaper should send data to left, right, Ls. and Rs channels of the R2 surround plugin.
https://www.dropbox.com/s/zsphobt0bk...%2015.mov?dl=0
|
|
|
01-26-2018, 12:49 AM
|
#4
|
Human being with feelings
Join Date: Dec 2007
Posts: 32
|
Regression
Regression: on stop/play, VST plug-ins are not reset anymore (don't receive a resume opcode?) so e.g. reverb tails continue to play. Used to work fine at least in v5.65.
|
|
|
01-26-2018, 09:45 AM
|
#5
|
Human being with feelings
Join Date: Jul 2009
Posts: 3,714
|
Quote:
Originally Posted by planetnine
+ MusicXML: fix manual quantizing after import [t=202244]>
|
Please note that there is at least one other MIDI import/export bug remaining:
MIDI either exporting or importing tempo maps incorrectly
(Confirmed, and with RPP.)
|
|
|
01-26-2018, 12:49 PM
|
#6
|
Human being with feelings
Join Date: Oct 2008
Location: Right Hear
Posts: 15,618
|
Ouch on the tempo map that JS reports... hope for a fast fix on that one
cuz it makes me nervous just tested with an xml export and import and it seemed to be OK
it can be touchy in where you import on the time line... i.e., if the exported file did not
start at zero and you import it to some place in time that is not correct, you do get a messed
tempo map... of course
Last edited by hopi; 01-26-2018 at 12:57 PM.
|
|
|
01-26-2018, 01:18 PM
|
#7
|
Human being with feelings
Join Date: Oct 2017
Location: Black Forest
Posts: 5,067
|
@Schwa & Justin:
I know this is not really on topic, but I'm just working on a show/hide tracks script and there is no way to update the arrange window, so that the scroll bar
automtically updates its length according the track count. Would it be possible to provide a function in the API?
|
|
|
01-26-2018, 02:39 PM
|
#8
|
Administrator
Join Date: Mar 2007
Location: NY
Posts: 15,821
|
Quote:
Originally Posted by lalelu
Regression: on stop/play, VST plug-ins are not reset anymore (don't receive a resume opcode?) so e.g. reverb tails continue to play. Used to work fine at least in v5.65.
|
This behavior should be controlled by this preference. It's possible that the behavior in a previous build was not correct, or that I am misunderstanding the bug report!
|
|
|
01-26-2018, 02:55 PM
|
#9
|
Human being with feelings
Join Date: Oct 2011
Posts: 2,924
|
Quote:
VST plug-ins are not reset anymore
|
It's an old behaviour. Arturia VST have this kind of issue...
|
|
|
01-26-2018, 03:57 PM
|
#10
|
Human being with feelings
Join Date: Oct 2008
Location: Right Hear
Posts: 15,618
|
Quote:
Originally Posted by _Stevie_
@Schwa & Justin:
I know this is not really on topic, but I'm just working on a show/hide tracks script and there is no way to update the arrange window, so that the scroll bar
automtically updates its length according the track count. Would it be possible to provide a function in the API?
|
db clk the horizontal scroll bar to get that
|
|
|
01-26-2018, 04:03 PM
|
#11
|
Human being with feelings
Join Date: Oct 2017
Location: Black Forest
Posts: 5,067
|
That won't work, I need a command to implement it in my script:
|
|
|
01-26-2018, 09:32 PM
|
#12
|
Human being with feelings
Join Date: Oct 2008
Location: Right Hear
Posts: 15,618
|
hold on brb
never mind then... was having strangeness with the Inline Ed. but then it went away
|
|
|
01-27-2018, 02:11 AM
|
#13
|
Human being with feelings
Join Date: Dec 2007
Posts: 32
|
Quote:
Originally Posted by schwa
This behavior should be controlled by this preference. It's possible that the behavior in a previous build was not correct, or that I am misunderstanding the bug report!
|
I'm afraid you misunderstood
It's not about flushing/silencing FX after stopping, but after *restarting* playback.
So what I expect is:
Stop playback => reverb tail continues
Restart playback => Reverb is flushed (resume()d) and tail stops.
Not only is this not the default behavior anymore, I don't see any option the could re-enable it.
|
|
|
01-27-2018, 02:30 AM
|
#14
|
Human being with feelings
Join Date: Dec 2012
Posts: 13,334
|
I'm very sorry for posting inproper content in Pre-release forum, Devs, but I suppose this thing is really important.
In Preferences/Audio/Recording there is a setting to start new files at x Megabytes.
So why it also affects glueing items like in this thread?
https://forum.cockos.com/showthread.php?t=202023
If it so, wouldn't be better to call it properly, so everyone will know what this option is intended for?
Thanks for the attention.
|
|
|
01-27-2018, 03:51 AM
|
#15
|
Banned
Join Date: Feb 2014
Location: Moscow, Russia
Posts: 554
|
Quote:
Originally Posted by lalelu
I'm afraid you misunderstood
It's not about flushing/silencing FX after stopping, but after *restarting* playback.
|
I know what are you talking about.
I have similar issue, when, let's say, there's a huge reverb on the track.
1. Start playback.
2. Bypass reverb fx via checkbox in the plugin's GUI.
3. Stop playback.
4. Disable bypass for reverb plugin.
Enjoy sudden huge reverb tail in silence.
This option is enabled:
|
|
|
01-27-2018, 06:50 AM
|
#16
|
Human being with feelings
Join Date: May 2017
Posts: 981
|
Rewire is also not working in Pre15 -icc18.
Rewire transport is working but there is no audio when used as a slave.
I reinstalled Version 5.6 and it works on that. Can you pls fix this too ?
|
|
|
01-27-2018, 11:35 AM
|
#17
|
Administrator
Join Date: Mar 2007
Location: NY
Posts: 15,821
|
Quote:
Originally Posted by lalelu
I'm afraid you misunderstood
It's not about flushing/silencing FX after stopping, but after *restarting* playback.
So what I expect is:
Stop playback => reverb tail continues
Restart playback => Reverb is flushed (resume()d) and tail stops.
Not only is this not the default behavior anymore, I don't see any option the could re-enable it.
|
Hm, the apparent issue here is inconsistency in how plugins handle a couple of vst3 messages. Specifically:
Code:
/** Informs the Plug-in about the processing state.
This will be called before any process calls start with true and after with false.
Note that setProcessing (false) may be called after setProcessing (true) without any process calls.
In this call the Plug-in should do only light operation (no memory allocation or big setup reconfiguration),
this could be used to reset some buffers (like Delay line or Reverb). */
virtual tresult PLUGIN_API setProcessing (TBool state) = 0;
Some things in the VST3 spec are ambiguous but this seems pretty clear, the plugin is supposed to clear buffers on this call. REAPER always sends setProcessing(false)/setProcessing(true) on playback start or unbypassing the plugin, but apparently not all plugins clear buffers in this case.
Prior to this prerelease cycle, REAPER would send plugins a hard reset (setActive) on playback start, but this can cause plugins to do a lot of unnecessary recalculation. I do think that plugins that don't clear buffers in 5.71pre are not doing the right thing, but we might have to add a per-plugin compatibility setting for this, or something.
|
|
|
01-27-2018, 12:46 PM
|
#18
|
Human being with feelings
Join Date: Oct 2007
Location: home is where the heart is
Posts: 12,109
|
Quote:
Originally Posted by schwa
Prior to this prerelease cycle, REAPER would send plugins a hard reset (setActive) on playback start, but this can cause plugins to do a lot of unnecessary recalculation.
|
Is this change only for VST3 plugins or VST2 also ?
If so, sounds like it could fix issues with some plugins on playback start (will test if it's for VST2 also).
https://forum.cockos.com/showthread.php?t=140690
(see also post #4 for more examples)
https://forum.cockos.com/showthread.php?t=156637
(not a VEP user myself)
edit:
'flush' then is maybe used wrongly in these threads and should maybe rather be 'hard reset'.
edit2:
After a bit of testing, yes, seems to apply to VST2 also.
This testcase now works correctly with current pre (no more wrong / warbled sound when starting playback right before or while audio is present.)
edit3:
Seeing this change may cause trouble on other ends (following posts), I do hope it will survive in a way (option per plugin ?) and will not get completely reverted.
Last edited by nofish; 01-27-2018 at 03:57 PM.
|
|
|
01-27-2018, 01:58 PM
|
#19
|
Human being with feelings
Join Date: Dec 2007
Posts: 32
|
Quote:
Originally Posted by schwa
Hm, the apparent issue here is inconsistency in how plugins handle a couple of vst3 messages. <snip>
|
It affects VST2 plugins equally. Tested U-He (VST2 and VST3), Valhalla (VST2), my own plugins (VST2), none of them behave properly anymore with 5.71.
In the case of VST2, plug-ins usually are reset in resume() call (triggered by effMainsChanged opcode). This one doesn't seem to be sent anymore on start of playback. I'm not aware of any alternative event triggered by a host's playback my plug-ins could listen to and clear their buffers.
|
|
|
01-27-2018, 02:22 PM
|
#20
|
Human being with feelings
Join Date: Apr 2012
Location: Christchurch, New Zealand
Posts: 482
|
Yeah, I posted some similar problems with this new plugin-related behaviour in this thread, along with my workarounds. In particular, the current inconsistency of transport change "triggers", which is generally the most reliable way to prepare for playback, is far from ideal.
|
|
|
01-27-2018, 04:27 PM
|
#21
|
Human being with feelings
Join Date: Jan 2016
Location: Los Angeles, CA
Posts: 3,127
|
Solo behaviour
Hi all, I've tried to figure this out but I'm hoping one of you can clarify the new Solo behaviours.
Scenario:
DRUMBUS
==KICK (Send to 3+4 INSTBUS)
==SNARE
...
INSTBUS (Receive on 3+4, sidechain compression of entire bus)
==BASS
==PAD
...
Currently there's no way to hear the Sidechain Compression on the BASS alone. Previously if you solo'd the BASS track it would process the Send to it's parent, and only in the case of Alt-Solo would you hear just the BASS alone unaffected.
Any help?
|
|
|
01-28-2018, 02:57 AM
|
#22
|
Human being with feelings
Join Date: Nov 2008
Location: London, UK
Posts: 2,583
|
Quote:
Originally Posted by schwa
[...] we might have to add a per-plugin compatibility setting for this, or something.
|
Yes, please. Those recent changes have definitely been a regression in my experience.
|
|
|
01-28-2018, 03:14 AM
|
#23
|
Human being with feelings
Join Date: Aug 2007
Location: Luxembourg/Spain
Posts: 1,922
|
Is it this resetting of plugins that can cause yellow flash on transport changes?
If so would it be possible to "disconnect" all audio processing from the audio callback, then do the reset, prime the audio buffers and then reconnect the audio processing.
Would love to get rid of these "performance issues" at some point. Most of them unnoticeable just by ear, but they do show up in form of yellow flash, RT CPU peaks, Longest RT block, etc.
__________________
Reaper for Linux Documentation (WIP). Software: Archlinux/KDE, Fabfilter FX, Komplete 8, Nebula, Schwa/Stillwell, T-racks Max/Amplitube/SVX, etc. Gear: i7-2600k/4700HQ/16GB, RME Multiface/Babyface, Behringer X32, Genelec 8040, etc. :)
|
|
|
01-28-2018, 06:58 AM
|
#24
|
Administrator
Join Date: Mar 2007
Location: NY
Posts: 15,821
|
For the next build, we will:
- Hard reset VST2 plugins on playback start, reverting to pre-5.71 behavior
- Soft reset VST3 plugins for whitelisted developers who are known to conform to the spec in this regard (in brief testing, at least Voxengo and Celemony do)
- Hard reset all other VST3 plugins, but add a per-plugin compatibility setting for users to add plugins to the whitelist.
|
|
|
01-28-2018, 07:01 AM
|
#25
|
Human being with feelings
Join Date: Nov 2008
Location: London, UK
Posts: 2,583
|
>For the next build, we will[...]
<3
|
|
|
01-28-2018, 11:26 AM
|
#26
|
Human being with feelings
Join Date: Oct 2007
Location: home is where the heart is
Posts: 12,109
|
Quote:
Originally Posted by schwa
For the next build, we will:
- Hard reset VST2 plugins on playback start, reverting to pre-5.71 behavior
- Soft reset VST3 plugins for whitelisted developers who are known to conform to the spec in this regard (in brief testing, at least Voxengo and Celemony do)
- Hard reset all other VST3 plugins, but add a per-plugin compatibility setting for users to add plugins to the whitelist.
|
Please (re-)consider a per-plugin compatibility setting to not hard reset VST2 plugins also (post #18). (Ok, it sounds like the decision is set in stone already, it will be my last post about it.)
|
|
|
01-28-2018, 02:13 PM
|
#27
|
Human being with feelings
Join Date: Jun 2012
Posts: 126
|
I don't know what's up with the latest builds but Reaper freezes after coming back from sleep mode in Windows 10.
Last edited by Doc Shay; 01-28-2018 at 02:19 PM.
|
|
|
01-29-2018, 06:56 AM
|
#28
|
Administrator
Join Date: Mar 2007
Location: NY
Posts: 15,821
|
Quote:
Originally Posted by svijayrathinam
IOSONO bug in pre 15. The moment I split a file the channel settings are wrong
|
The general problem is that upmix settings for this plugin are not retained when used as media item FX. If you save the project and reopen it, the output configuration resets to stereo.
This is caused by a code change in 5.71pre10. The change is generally a bugfix, but unfortunately it triggers an existing bug in this particular plugin. Specifically, REAPER notifies the plugin of the I/O configuration, but the plugin stops responding to the nofication after the initial call.
I have communicated with the plugin developer about the problem, but I see the release version of the plugin has not been updated since 2012 so it may not be in active development. If they are unable to fix the problem, we may be able to work around it with special-case code on the host side.
|
|
|
01-29-2018, 09:45 AM
|
#29
|
Human being with feelings
Join Date: May 2017
Posts: 981
|
Is it possible to put the old code like how it used to be for this plugin please ?
|
|
|
01-29-2018, 05:14 PM
|
#30
|
Human being with feelings
Join Date: Nov 2008
Location: London, UK
Posts: 2,583
|
Quote:
Originally Posted by schwa
If they are unable to fix the problem, we may be able to work around it with special-case code on the host side.
|
*swoon*
This is why COCKOS is the best. Avid et al would tell the customer it's tough luck (if they even bothered to respond).
|
|
|
01-29-2018, 09:25 PM
|
#31
|
Human being with feelings
Join Date: May 2017
Posts: 981
|
Quote:
Originally Posted by daxliniere
*swoon*
This is why COCKOS is the best. Avid et al would tell the customer it's tough luck (if they even bothered to respond).
|
Reaper is definitely the best DAW and amazing support ! That bug is still not fixed though..Fingers crossed
|
|
|
Thread Tools |
|
Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -7. The time now is 01:13 AM.
|