v5.34 - February 24 2017

[playtimer]

v 5.34 final is on Landoleet

v5.34 - February 24 2017
+ API: GetTrackInfo/GetTrackState functions include TCP/MCP visibility flags
+ Envelopes: prevent possible crash when clearing FX parameter envelope while envelope list is open [t=188055]
+ FX: adjust parameter aliases when removing ReaEQ/ReaXcomp/etc bands
+ FX: fix bug where offline plugins could have their first/second parameter automation converted to bypass/wet automation
+ FX: preserve parameter aliases when offlining plugins [p=1803096]
+ Heal splits: fix potential crash when healing take automation [t=187901]
+ macOS: improve drawing CPU use on Retina displays
+ macOS: improve 10.11+ mouse event filtering
+ macOS: remove UI-update options, always use most optimal update mode
+ MIDI editor: fix pasting or duplicating events when the media item has a start offset [t=187507]
+ MIDI editor: fix quantize behavior when grid is a full measure or greater
+ ReaScript: prevent potential crash from Lua scripts that create excessive recursive tables [t=187415]
+ ReaScript: update GetFocusedFX() to include take number [t=187292]
+ Render: add $samplerate wildcard
+ Smooth seek: improve anticipative FX behavior and performance when seeking
+ Snap: improve behavior when adjusting a cut point and only one item is selected
+ Undo: add undo point when extending time selection via shift+click [t=187261]
+ Web control: fix bug using GET/TRACK/x/B_PARM etc
+ Video: improve YUY2/YV12 filtering

[_TIP_]

Hi, after about 3 months away from Reaper and music in general, i downloaded the latest version of reaper (v5.34). After playing a little bit with the new features, i tried to load a multi-timbral vsti (WusikStation8) and started to load sounds and send them to different audio outputs (sound1-main out, sound 2 - ST.out2, sound3 - ST. out3, etc...) my preferred way working with multi-timbral instruments is with (Allow feedback in routing) setting in project settings enabled so I'm able to send midi and receive audio in one track and not using 2 tracks, one to send midi and the other to recieve audio... That way worked fine and the audio came out as it should but as soon as i added an fx to the track, the audio of the track muted for no particular reason, even if you disable or toggle the fx offline the audio is still muted, as soon as you delete the fx the audio comes back. In the beginning i thought, it could be a Wusikstation8 bug but i also tried TX16Wx and Falcon and i'm getting the same results... Please devs take a look when you get a chance, i have so many projects that are not loading correctly because of that bug.

[schwa]

Does the way you are setting up these projects work in older versions of REAPER? You can download previous versions here: http://www.reaper.fm/download-old.php

[_TIP_]

Originally Posted by schwa

Does the way you are setting up these projects work in older versions of REAPER? You can download previous versions here: http://www.reaper.fm/download-old.php

Thanks for your quick reply Schwa! Yes, this setup, other than the known issue with the delay compensation, is working just fine in older versions with all of my projects. I'll try to go back maybe 3 months, install older versions and find out when did this broke. I'll report back to you ASAP, thanks again for your amazing work Reaper team!!!

[Dali]

Originally Posted by _TIP_

Thanks for your quick reply Schwa! Yes, this setup, other than the known issue with the delay compensation, is working just fine in older versions with all of my projects. I'll try to go back maybe 3 months, install older versions and find out when did this broke. I'll report back to you ASAP, thanks again for your amazing work Reaper team!!!

Remember you can always install a Portable install version to do testings....

Dali

[EvilDragon]

Originally Posted by _TIP_

other than the known issue with the delay compensation

It's not a "known issue". It's impossible to have feedback routing and PDC at the same time. Cause and effect, basically.

[_TIP_]

Originally Posted by EvilDragon

It's not a "known issue". It's impossible to have feedback routing and PDC at the same time. Cause and effect, basically.

I understand, i still hope though to see a device like Ableton's External Instrument in the future which is not only let you assign audio and midi in one track but it also takes care of the pdc, having 2 tracks, 1 sending midi and another one receiving audio is literally killing my workflow especially when automation is involved...

Originally Posted by Dali

Remember you can always install a Portable install version to do testings....

Thanks Dali, instead i used a Virtual Machine...

Originally Posted by schwa

Does the way you are setting up these projects work in older versions of REAPER? You can download previous versions here: http://www.reaper.fm/download-old.php

So, after a lot of digging i realized that nothing was wrong with the new versions of Reaper, i end up finding that the problem was in my Reaper preferences, i had the setting (Allow live fx multiprocessing on) enabled in the buffering tab... I don't know if that make sense and if is normal to brake the (Allow feedback in routing setting) in the project tab when is on but i'm happy i was able to find what was causing the problem. Thanks again and i'm sorry if i reported a false bug...

[EvilDragon]

Originally Posted by _TIP_

I understand, i still hope though to see a device like Ableton's External Instrument in the future which is not only let you assign audio and midi in one track but it also takes care of the pdc, having 2 tracks, 1 sending midi and another one receiving audio is literally killing my workflow especially when automation is involved...

You do know about ReaInsert, right?

[_TIP_]

Originally Posted by EvilDragon

You do know about ReaInsert, right?

ReaInsert has nothing to do with multi-timbral Vsti's, ReaInsert is for routing hardware effect units in Reaper. I wish ReaInsert would have that functionality!!!

[EvilDragon]

You mentioned Ableton's External Instrument - that's for using external hardware, which is exactly what ReaInsert is...

[TheWhistler]

Originally Posted by _TIP_

I understand, i still hope though to see a device like Ableton's External Instrument in the future which is not only let you assign audio and midi in one track but it also takes care of the pdc, having 2 tracks, 1 sending midi and another one receiving audio is literally killing my workflow especially when automation is involved...

I use the setting as you described. 1 track for midi and for audio.
I allow feedback. Is there additional pdc introduced with this setup?

[EvilDragon]

Only in case you actually route tracks in a feedback way, I think.

[TheWhistler]

Works for me here with 5.33
I mean, no actual feedback routing but midi to same track audio out by vsti.

Would any additional pdc result in a higher latency, because this is not the case with me?

[_TIP_]

Originally Posted by EvilDragon

You mentioned Ableton's External Instrument - that's for using external hardware, which is exactly what ReaInsert is...

Ableton's External Instrument is not only for using external hardware but also for routing multi-timbral Vsti's and Rewire devices.

[amagalma]

Originally Posted by Justin

Got it, extending this API for 5.34pre1, it will include the take number as the high 16 bits of fxnum.

Did this get added finally?