Now it's brilliant. Broken backward compatibility. Projects using these effects are not compatible in earlier 6.x version due to this slight/big change.
It is forwards compatibility, not backwards, and forwards compatibility is not nearly as important.
Yes, you're right, I unintentionally used wrong term (backwards vs forwards compatibility), sorry.
It was not about compatibility with myself, but about compatibility with partners using maybe older versions.
But if you see it as unimportant, then I won't argue, OK.
Yes, you're right, I unintentionally used wrong term (backwards vs forwards compatibility), sorry.
It was not about compatibility with myself, but about compatibility with partners using maybe older versions.
But if you see it as unimportant, then I won't argue, OK.
We try to maintain both backwards compatibility with old projects and, when possible, forward compatibility with old REAPER versions. But almost every new version adds some feature that won't work as expected if you load the project in an older version of REAPER. In a perfect world we'd always be able to predict how things will change in the future!
It was not about compatibility with myself, but about compatibility with partners using maybe older versions.
But if you see it as unimportant, then I won't argue, OK.
Well if you'd create a project in version with automation items and after that will try to open it in one of the previous versions, then it won't work. Same here. Verstehen?
Thanks for the update - as always!
I'm currently stuck on 6.09 because 6.10 introduced a bug when copying ARA edits (Melodyne 4) - SOME ARA edits don't get copied (results in vanilla untuned audio), some are copied properly, without an obvious logic nor reproducability.
From the changelog I can't find out if that's been adressed, nor can't I find the thread again which lead me to going back to 6.09 (which solved my issues immediately).
So, if anyone's better informed than me: How's the state with ARA/Melodyne 4?
Thanks!
We try to maintain both backwards compatibility with old projects and, when possible, forward compatibility with old REAPER versions. But almost every new version adds some feature that won't work as expected if you load the project in an older version of REAPER. In a perfect world we'd always be able to predict how things will change in the future!
Sure, but I was talking about maybe only just clicking MONO button on master track and resaving, then sending back to a partner, and viola - he wouldn't be able to open it properly (note that he would send me the project first from the older version). It's not like those error messages about new functions that are not understand by older app (tokens or what etc.), that wouldn't be problem if you are not make use of them (those new additions). So simple open older, check and listen, set track mono and save invalidates it. That was my point.
Thanks for the update - as always!
I'm currently stuck on 6.09 because 6.10 introduced a bug when copying ARA edits (Melodyne 4) - SOME ARA edits don't get copied (results in vanilla untuned audio), some are copied properly, without an obvious logic nor reproducability.
From the changelog I can't find out if that's been adressed, nor can't I find the thread again which lead me to going back to 6.09 (which solved my issues immediately).
So, if anyone's better informed than me: How's the state with ARA/Melodyne 4?
Thanks!
There are no ARA changes in this version. I don't recall seeing a reproducible bug report on this subject, so if you're able to find one or create one, please post it (ideally in its own thread), thanks!
Well if you'd create a project in version with automation items and after that will try to open it in one of the previous versions, then it won't work. Same here. Verstehen?
Read my answer to schwa ^^^^^.
1) It was about the simplest editing...
2) It was not about adding feature or function, but renaming stuff
(VCA Leads vs VCA Master JSFX).
Interesting.
Tried to workaround it (in pre 6.12b versions) by using Project Bay and Replacing instances by older VCA Master JSFX, but then the parameters are reset to defaults, even the effect code is the same.
It looked at the first sight like a way, but it's no go in the end :-(
As I just installed v6.12 and then few minutes later v6.12b to test them, I found interesting discrepancy in the ever returning graphic bug with the white places under labels in some Rea plugins (EQ, XComp, Delay and Pitch) and Project Settings.
These are both installed on the same computer runing at the same time side by side (Windows 7 Pro 32-bit), screenshots here:
And please: Option for showing FX Browser's "Filter" edit line and "Clear filter" button at the bottom of the Window - as it always was before.
That new position (on top) totally broke my workflow (not only mine, there are also others requesting it here too).
And please: Option for showing FX Browser's "Filter" edit line and "Clear filter" button at the bottom of the Window - as it always was before.
That new position (on top) totally broke my workflow (not only mine, there are also others requesting it here too).
So, please, +1000 for adding the option. Thanks.
Options are always good, but–in yet another example of how you can never please everyone–I find the new position on top to be a significant improvement.
Options are always good, but–in yet another example of how you can never please everyone–I find the new position on top to be a significant improvement.
You're right Quasar, but I've never said opposite. I was for option
It was below for a "decade", then sudden change with no option - just not the Reaper's way.
I am aware that for different workflow or just simple different positioning of FX Browser window/docker matters if you need it (filter/search box and button) above or below.
And mainly - OK and Cancel buttons should foolow the change in position then!
You're right Quasar, but I've never said opposite. I was for option
It was below for a "decade", then sudden change with no option - just not the Reaper's way.
I am aware that for different workflow or just simple different positioning of FX Browser window/docker matters if you need it (filter/search box and button) above or below.
And mainly - OK and Cancel buttons should foolow the change in position then!
I actually use this filter more than I'd like because I've never been especially happy with the FX Browser sorting options. I wish we had full folder directory control (a la Track Templates). I've made some of my own folders, which helps, but I've never been able to make good sense of Reaper's FX preset organization and so keep them hidden, and often find that the quick filter search is just easier than anything else.
I do appreciate your point about not suddenly jolting you out of a workflow action that has become automatic and reflexive over time. Changes accompanied by choice (as with the add and remove FX bin button location a while back, which was cool) are always best for workflow-effecting UI stuff. The change should not be mandatory if at all possible.
I just downloaded Version 6.12c, opened a track, and the Input drop-down is missing; Reaper recognizes my Presonus baord through the ASIO driver, and all of its channels, but I can't find a way of assigning a channel to a track. This sounds like a fubar bug. What did I miss, and how do I revert to a previous version?
Last edited by willhobbs01; 06-17-2020 at 05:53 PM.
I just downloaded Version 6.12c, opened a track, and the Input drop-down is missing; Reaper recognizes my Presonus baord through the ASIO driver, and all of its channels, but I can't find a way of assigning a channel to a track. This sounds like a fubar bug. What did I miss, and how do I revert to a previous version?
arm the track. Reaper 6 default layout has input box hidden on disarmed tracks.
__________________
REAPER Video Tutorials, Tips & Tricks and more at The REAPER Blog
arm the track. Reaper 6 default layout has input box hidden on disarmed tracks.
Thanks. I've been using earlier versions of 6.x without having to do this, but right-clicking above the new track brought down a menu that included arming, and when I selected that, the channel assignment drop-down menu appeared. Thanks.
It's not special to this version but a tiring recurrence: If you introduce a new modulation parameter, as in Reasamplomatic for example, and this new parameter is in the middle of the parameter list, all modulation parameter links created on previous versions are broken.
For some reason its not possible to create a black overlay with video processor in v 6.12. I just tested it, because someone wrote about problems in the Video subforum. I have no idea why it doesn't work anymore.
Older projects load and show up correctly. The oscilloscope with black background gets transparent in use with the famous black overlay code.
But it is some how impossible to do it with a fresh new project in version 6.12. Could someone please check it?
Edit: Transparency seems to be gone. Even if I use the chroma key presets with green or blue it only shows black but not transparency. If you have an image below and put the oscilloscope over it, you can't get it to shine thru.