Backwards Compatibility vs Progression

[whyterabbyt]

So you're saying that these long abandoned projects are worth more to you then the progress of new features, technological advancements and innovation? Fair enough.

A year isnt 'long'. Its less time than most developers' release cycle.

[Guenon]

Its less time than most developers' release cycle.

Yes, and this can also be the case on the client side . As in, some productions I've been involved in have had 2-4 year spans, for example. Not to mention if doing sequels. The need to revisit "old" projects is very real.

I can imagine the production meeting. "Sorry guys, don't want to live in the past, can't do anything with this old shit nowadays."

"???"

[whyterabbyt]

Its less time than most developers' release cycle.

Yes, not to mention also on the client side . As in, some productions I've been involved in have had 2-4 year spans, for example.
"???"

Indeed. Begs the question as to the OP's familiarity with professional and/or large-scale projects.

[fmr]

I find it much more beneficial to stay up to date with the present and push forward into the future, rather then being hangup on the past. This goes for most things in life.

Considering that you were asking about going back to projects that were "a year" old or more, reading this is just funny ... Hung up on the past, eh?

Between the lines, I get the feeling you aren't genuinely in the position to offer these life lessons with authenticity.

I may be wrong, but I have the feeling that the OP is still too young, and still fascinated by technology, to the point of forgeting what exactly it is for. Technology isn't a goal in itself, it's just a "tool". Also, it alone will not guarantee you to "stay up to date with the present and push forward into the future" (geesh, this looks like an Apple slogan ).

Music is the goal here, and music is always in the past, in the present and in the future, depending how you look at it. Music is not a "chewing-gum" that you chew and throw away (some may be, but then it's worhtless). Music, if taken serious, aims to live forever (admitedly, most of it will not, but that isn't a reason to not have that ambition). So, you are always in the same point: revisiting the past to live the present and project the future, all at the same time.

BTW: One of the challenges faced today in several places is how to preserve electronic works done 20 or 30 years ago, with means and media that no longer exists, or is not working anymore. This is something to think about.

BTW: Do you consider a piano "a thing of the past" that should also be trashed? Or any of the acoustic instruments, for that matter?

[Guenon]

Indeed. Begs the question as to the OP's familiarity with professional and/or large-scale projects.

Yeah. I think it's also fair to say, in the other end of the spectrum, in my own experience/opinion, it also pays off to first take your time to learn the tools you have.

The OP is talking about projects from a year ago containing "learning errors" and the like, so it's obvious he's talking from a beginner's point of view, yes. So my subjective advice there is, if you keep chasing the next big thing while still just starting out, and switch into fresh new technologies all the time, not taking the time to get familiar with the stuff you have at any given point -- always getting new plugins, always getting new tech, having the feeling of missing out on something big and new instead of learning what you have -- after a couple of years of doing that chase act, you are at a disadvantage when compared to someone who took the same time to master a given fixed toolset.

[shidostrife]

When I open my old projects, it would usually be for total rework. Remix, remaster, continuing an unfinished song, etc.
I don't care if a plugin or two doesn't load because it's no longer available with the latest version of the DAW. I'll replace it with the new version or other alternatives, and tweak from scratch. As long as all the audio/MIDI are there, I'm good.

[gas pump]

I don't care if a plugin or two doesn't load because it's no longer available with the latest version of the DAW. I'll replace it with the new version or other alternatives, and tweak from scratch. As long as all the audio/MIDI are there, I'm good.

Exactly, I don't mind loading up an older version of the DAW program and bouncing out stems if they were that critically important. But I've usually exceeded the skill and experience level by then and just continue on with new and improved projects without looking back.

It would be a great asset and marketing angle for companies to refresh their old plug-in lines also. But most importantly it would put modern features in the hands of their customers who would look to the stock arsenal over 3rd party developers. Which will bring in new customers and making upgrades more appealing.

I think there are a lot of people that shy away from DAWs that have a massive library of demos and decade old devices as their offerings.

[jancivil]

So you're saying that these long abandoned projects are worth more to you then the progress of new features, technological advancements and innovation?

I'm not, not at all. Abandoned means abandoned, I have abandoned some good music I composed because, well I don't feel like I won't have new ideas, and redoing them was too much trouble.
If I were to decide something is not abandoned after all, the new tech is not an issue, that's an unnecessary dichotomy. I'm not in love with an old Kontakt 1 patch to where I would worry, you know.

As the old adage goes, songs are never finished they are eventually abandoned.

I know that one but it's 'mixes are never finished, only abandoned'. And the truth in that means there is a point where you cut your losses.
I definitely have compositions that are finished, I'm good, no worries.

For perspective, I have things out there from before there was a modern DAW and I do not have the master tapes. And the guy inserted into the process before it was a product f**ked the mix completely up. You can't put toothpaste back into the tube.