• SONAR
  • Warez and mainstreaming (p.3)
2015/03/25 18:42:44
...wicked
Yeah, that's another legit thing that happens, you use a random (or not) VST and it goes belly up and then it doesn't work a few OS hops later. I think Phatmatik was like that for me once upon a time.
 
Seriously though, everyone on here bounces ALL their softsynths in every little project they do? I can certainly adopt that method going forward but sheesh what a giant nightmare if you've been making music with sequencers for...well crap I guess it's been about twenty years I've been using Cakewalk products? holy crap I'm old!
 
I'm surprised more people aren't currently in or have been in this situation though, hauling older projects now and again kicking, screaming, and crashing into the present. Okee, I'll spend some time in the archives trying to future proof things and get ready for another big DAW build. Can't wait to get access to all those dang Kontakt libraries..I'm sick of looking at the box with all the pretty pictures! :-)
2015/03/25 20:03:51
mixmkr
...wicked
 
I'm surprised more people aren't currently in or have been in this situation though, hauling older projects now and again kicking, screaming, and crashing into the present. 

I won't say I don't have older projects for sure.  Even a closet full of 1/2 master tapes as well.  But the multitrack tapes have long gone.  I just signed off on them.  The reason is I feel my music is getting better and better and stuff like Toontrack, Addictive Drums, Perfect Space, Pro Channel stuff...Z3ta2, etc, etc... and the other VSTi help things so much better than using old Oberheim drums or even old Roland keyboard drums...as good as they might have been back then.  I like to think my abilities are much better too, and not just chocking things up to better equipment, recording devices and instruments.  But having SPlat nowadays totally outweighs my Cool Edit Pro of years ago.  There's no comparison.  Therefore I listen to the "old" stuff to remember, but if anything I'll DEFINITELY re-record a song, should I want to keep it "current".  I've done that a couple times and the newer versions totally smoke my old ones.
BTW, I'm over 60, so I understand the "older" projects.  
Move forward Mr. Wicked.  Keep it fresh and look to the future.  Otherwise, the youngsters will pass us by.  Now as it is...., they have to "catch up"  HA!  :-D
2015/03/26 00:27:33
dubdisciple
I have a policy now that if a song is more than 3 years old it is either done, not getting done or i will simply start from scratch if i decide to remake.
2015/03/26 06:59:17
Bristol_Jonesey
dubdisciple
I have a policy now that if a song is more than 3 years old it is either done, not getting done or i will simply start from scratch if i decide to remake.


Case in point.
 
I intended to re-visit an old project last night.
 
I located several version so naturally I chose the newest one.
 
The project opens ok but sounded terrible, probably because a handful of plugins - notably some T-Racks modules  - weren't in the location expected by Sonar. This project as last saved at the back end of 2011 so I'm guessing it was an 8.5 project.
 
Guess I'll have to rebuild it now, as 8.5 is long gone from my system.
 
Edit: I do still have my old DAW kicking around somewhere - I might fire it up (if it still works) and see what I can see.
2015/03/26 09:22:18
Kylotan
...wicked
I'm surprised more people aren't currently in or have been in this situation though, hauling older projects now and again kicking, screaming, and crashing into the present.



You're still being a bit vague about what your actual problems are, though. :)
 
I have been using Sonar - and before it, Cakewalk Pro Audio, or whatever it was called - for something like 15 years, maybe longer if we go back to the MIDI only versions. And migrating projects is not something that ever really required much thought.
  1. Open project in new version of Sonar.
  2. Note every plugin that it reports as missing. Think about how important that plugin is, and decide either to:
    1. obtain and install that plugin, then go back to (1)
    2. or, replace it with a different plugin.
  3. Note any missing samples, libraries or patches that your plugins report. Decide whether to:
    1. relocate samples/libs/patches that have moved
    2. obtain and install missing samples/libs/patches
    3. replace missing samples/libs/patches
  4. Work with the project
There's not much more to it than that - either you have the data it needs, or you don't, and if you don't, you can either find it, or replace it.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account