Westside Steve
Hmmm. Can R Mix isolate remove and paste by itself say a vocal line from a stereo mix for processing alone?
Is it similar to the Sony plug called spectral something or other? I have SF pro but did not purchase the spectral thing when they offered it.

Thanks!

(And I do have Melodyne editor even though its a little hinky......)
WSS

You can achieve a certain amount of isolation of parts depending on the mix (really thick mix with lots of stuff in the freq range of isn't gonna work as well as a sparse mix where the other instruments are higher/lower than the thing you want to isolate). You may lose some of the overtones as well. So it's not perfect but nothing really is when trying to yank stuff out of a stereo mix.

Ok, Cakewalk. Last straw - I have been faithful for many years - I had cakewalk back before it could record audio tracks - but I hate to bring up an old mix (ok, this one I am working on is a whole 3 years old) and have to do handstands to get the plugins back if at all. I loved and used Vintage Channel on all sorts of tracks.
 
Reason doesn't master as well as you do, but they also don't take things out of their product after it has been added. You have been doing this for years - you should at least let us know what will be supported in the future and what you will yank out indiscriminately.
 
Sorry, I'm done. I upgraded for nothing.

RobbSadler
Ok, Cakewalk. Last straw - I have been faithful for many years - I had cakewalk back before it could record audio tracks - but I hate to bring up an old mix (ok, this one I am working on is a whole 3 years old) and have to do handstands to get the plugins back if at all. I loved and used Vintage Channel on all sorts of tracks.
 
Reason doesn't master as well as you do, but they also don't take things out of their product after it has been added. You have been doing this for years - you should at least let us know what will be supported in the future and what you will yank out indiscriminately.
 
Sorry, I'm done. I upgraded for nothing.

Cakewalk would like nothing better than include a 64-bit a version of the Vintage Channel. However, they don't own the rights to modify the code nor do they own the IP, and the original developer is literally nowhere to be found. Cakewalk, I, and several other people have tried to locate him, but to no avail.
 
If you do an "advanced" custom install from any version of Sonar that included the Vintage Channel, which you must have or you wouldn't have used it in your projects, you can use it in X3. If a previous version of Sonar remains on your hard drive that had the VC-64 installed, it will still be available. I still use it and it doesn't crash the system or anything. However, I am resigned to the fact that one day, some system or program change will make it unusable unless the original developer turns up and/or Cakewalk can get the rights to the code.
 
Cakewalk is very good about backward compatibility, especially given that some programs dropped any support whatsoever for DirectX or 32-bit plug-ins. BTW - what you said about Reason isn't true. Reason 7 no longer includes Dr. REX.

Beepster
They left it out because it is 32bit and I guess they were trying to cut down on conflicts.

Just to re-iterate, I believe they left it out primarily because it has no future. The Vintage Channel has become an end-of-life product through no fault of Cakewalk's, other than their not including a line in the licensing that said "If you disappear, the code becomes ours."

Everything you've purchased you can still install.
 
I don't see what the big deal is. I'm guessing that they pulled the old plug because it's 32 bit and it isn't scheduled to be upgraded.
 
I appreciate that you're upset that you can't just open a 3 year old project with a default install of the new version of Sonar. For some software manufacturers, backwards compatibility is a HUGE goal. It was for Microsoft for a long time.
 
But Cakewalk balances between super users and a huge population of light users. I believe a large part of the Sonar customer base is novice. People who have to learn to use an EQ. That sort of thing. For them, dragging in a plug that requires bit-bridge might be confusing.
 
Super users can install all their old plugs and toys. There's nothing to stop you.

You can use the old plugins if you so wish. You can also use the new ones. You can also use the old version of Sonar until your old project is complete. However expecting plugins to be supported forever is unreasonable (sorry) and if you check the specs before you buy you would see it isn't bundled with X3 (however no matter you can still use it).

In my view Cakewalk should be leaving out a lot more old plugins in X4 and go for 64 bit only, but still allow people to use their old plugins they have previously purchased should they wish.

(edited for typo)

I was one of the folks who tried to track down the VC creator, to no avail.  I spent several HOURS digging through all kinds of stuff on the web, and simply could not locate the individual.
 
I did get the impression, from some of the content out on the web, that there had been some sort of financial problems, and I speculate that he simply got disgusted with it all and chucked it and went off to be a rodeo clown, or some such other non-VC creating direction in his life.
 
FABULOUS plugin, but it will never be upgraded, unless the author someday reads our pleas and decides to help us out.  I would CHEERFULLY help him pay his mortgage, should he ever decide to update it to a 64-bit version - OR sell the rights to someone who would.
 
I believe Cakewalk did the right thing to decide to remove it - it cannot be supported, and it will likely at some point begin to have trouble in a 64-bit environment.
 
And, as far as old plugins and such go, other than content, the actual SIZE of an older release of Sonar, and the unique plugins it had that are no longer with us, is actually quite small, in today's storage bliss.  I have retained everything back to X1 - and actually still have a 32-bit XP computer with 8.5.3 on it, if I REALLY have to go back for some reason.
 
When installing a new release, I believe it is not wise to unilaterally uninstall a prior release, as one never knows if there are any show stopper bugs in the new install - sometimes for a few months.  On top of that, they DO indicate things that have been dropped, and when that happens, it cements my decision to retain the older release.
 
I used to LOVE a freeware synth recreation of the Minimoog and the ARP2600 (minimogueVA and ARP2600VA).  These were, sadly, never updated to 64-bit versions, and the finally began to once in a while cause problems in my 64-bit Sonars.  It was these two 32-bit synths beginning to have trouble that finally got me to move to using ONLY 64-bit 3rd-party plugins, and my systems have been incredibly stable ever since then.
 
BUT, I do still have them - they live on in an older computer that is running XP Pro in 32-bit, and they continue to work fine there.  
 
You might be able to run old 32-bit plugins in a 32-bit install of Sonar on a 64-bit platform, but I had experimented with that, using Native Instruments PRO-53, and it failed miserably, so I abandoned that quest.
 
The other thing I normally do is finish any project started on one release of Sonar ON that same release, even if I have also installed a newer Sonar version.  I just have never had trouble with that approach.  Yes, they go to lengths to maintain backward compatibility, (wow, 4 of the letter 'i' in that word), but I try to maintain a clean break with projects, and it just works well for me to do so.
 
But I have hung onto older releases, so that I could maintain access to plugins that were dropped, and am cheered by them being there for older projects, in case I need them.
 
My motto is: "Saving it for someday", and it has served me well.
 
Bob Bone
 

I hated to lose Vsampler! I made huge custom librarys with that thing that are just gone in a puff of smoke. I agree that if a developer stops developing the code should be surrendered to Cake so we all don't get left out in the cold. It was quite a long wait to get everything in to 64 bit for me but I finally made it. Some good plugs and librarys got left behind though.

I understand - I have lost many things over the years, as well, including stuff where I had accumulated large libraries.
 
I DO try to retain stuff, when I know it is going to go away - this is why I have kept 1 computer that runs 32-bit XP Pro, and 8.5.3, as there are things that run there and only there.
 
I don't know how the arrangements are between Cakewalk and the companies that they get software to bundle into Sonar are made.  It looks like there is no guarantee of any kind of 'forever' arrangement, such as if the developer quits developing a particular component.  That is likely some kind of dark and murky legal stuff.
 
The 32-bit to 64-bit change was a HUGE deal, and there was a lot of fallout in that shift.  I had a large number of freeware 32-bit synths and effects that I just cannot use any longer - hundreds of them, unless I work on a project that needs them in a 32-bit Sonar.  This could mean going back to an old XP Pro computer.
 
I made a deliberate choice to just walk away completely from using 32-bit 3rd-party stuff.  It hurt, sometimes a lot, but in the long run, I will benefit from it.  By running all 64-bit 3rd-party components, my X3e is the most stable release I have ever had - neck and neck with my 32-bit 8.5.3 version.
 
Bob Bone
 

I still use Vintage channel from time to time, the routing of effects is hard to achieve using other stand alone VST's. My Sonar setup is still 32 bit and it allows me to use all the old effects right back to 8.5. I even have Pro Audio 9 installed on the same system. Eventually it will be time to upgrade the main music computer to 64 bit but I rarely need the large track counts and high number of effects so it'll get done when I can't get my work done anymore.