Sandboxing for Audio

Reading this post by Eesm/Georgi I could not help but wince:
(I was also a fan of FXPANSION TREMOR)

I am half way down the same path,
my main studio Mac is approaching its EOL
& when I hear its fans roaring, I save often!

My old laptop had already became dysfunctional
and I held out & waited for an M2 laptop.
So I have suffered through the transition once already.
And as Georgi laments, some software does not come with us.

Before my last trip away I carefully transferred all my work in progress music,
mostly ableton LIVE sessions. But when I went to boot them up, elements did not work.
Turns out VST2 is not compatible with my M2 laptop & never will be.
So that stymied any plans to work on those tunes.
But it also made me realise, if I didn’t still have my old Mac system
which does still open the sessions, I would be royally screwed!

All of this makes me wonder, is sandboxing a solution?

Last year I was given/rescued some redundant pro audio gear
a Power PC, with PCI audio cards and ProTools interface
Thus far I have not had the free time or will to boot it up
but audio software from that generation began to spring to mind
eg Hyperprism or Turbosynth…

It’s such a strange quandry.
I have drum machines that are 30+ years old and still work perfectly.
But old apps? gone. Unless someone sandboxes them.

The day will come, likely within the next year, when my studio Mac needs an upgrade.
So when I buy a M2 desktop Mac, I will be very careful to keep my older studio Mac functional.
Because there is bound to be a bit of music or an idea that is otherwise no longer accessible.

So be warned:
when moving to a Silicon M1 or M2 Apple computer,
tracks in your old music sessions which use VST2 plugins will not be available to you.
Freeze/print them! Or suffer regretsy!



The other lesson is this:

Never leave an audio session dependent on plugins.





Leave a Reply

Your email address will not be published. Required fields are marked *