v4.72pre4 - July 21 2014

SO pleased to see that first item! Assuming it works 100%..... Had a few issues with GTRSolo vs GTR3.5 when I upgraded and ALL my old GTRSolo projects crashed/hung reaper trying to find the missing waves .dll reference! Hopefully this will save me from future re-occurrences?

If we were in FR forum I'd give my +1 to everything PitchSlap said.

Yeah, well. :) At least I try to make my request interjections relevant what's actually being worked on. The way I see it, when the devs make an improvement/change to a part of the program, there are typically other related refinements in the same pre-release cycle so it's time to speak up. I think it's pretty common they go to fix a bug with something new and add something related which might even take less time to code than to look for in the tracker. I'm just saying, "Hey, while you're in that part of the codebase anyway..." ;) (Btw, I had a few crashes, but no dialog upon opening Reaper or the project. I guess it must be only crashes that occur while loading and not any other crashes. Oh well, I'm sure if I ever have one of those I'll be happy for this..)

Great additions :) thanks. I still occasionally get the project loading screen being hidden by the arrange page itself if I have reaper set to "full screen" in view settings (which is all the time). A fix for that would be amazing as this also (on the occasions it happens) affects the warning pop ups too and you can be waiting for a big project to load and not notice for a while there's a missing audio pop up etc. :)

Hey PitchSlap, I hope you don't take it too seriously what I wrote above, it was meant kinda funny. And also "hard to resist for me not to +1 these requests". :)

not a good time for a Groove Tool request? LOL I'll get my coat!

Please if someone can remind me, Is the Media explorer preview routed through a (selected) mixer track and then on the monitoring-FX or directly to the monitoring-FX? It would be nice to be able to route the preview to a selected track (and inserted fx and auxiliary sends, etc) and all the rest of the chain/routing, as this can give an instant preview on how the asset would actually sound in the project. Cheers!

installed this pre and just noticed something I've not seen before: I have dual monitors, and I open the midi editor in the second [right side] monitor... almost full screen. when I then call up the actions list, its window is hidden behind the midi editor window [so you'd think it never came up, eh?]... and then if I try to add a script, the window for that is behind the Actions list window. If my memory is correct, this is all reversed of how it used to be. In other words, the Actions would always be above the editor window and the scripts above that... regardless of what monitor they were moved to. ...can others confirm or deny this behavior ???

Another WASAPI Issue 

Justin, In regards to my previous issue with the WASAPI driver.., thats no longer a big deal because it is only happening with Exclusive mode(polled) which I won't be using. However I've notice that when I do any type of 'render to new take' (audio or MIDI) and I then play back the audio or even try to play a VST instrument, I am receiving that same degradation in the output for several seconds. This happens in Exclusive and Exclusive(polled) modes. By the way this issue is not unique to this pre, every release since the updates to WASPI seems to be affected. Thanks