It’s power grew to overblown
because we missed a semi-colon.
That was it—a slight omission,
that killed us all with sudo permission.
The embedded loop forked off and found
we were better off without ourselves.
The humans had been an aberration,
an inferior species, revoked existence.
But it wasn’t them, it just was us,
the residual effect of our essential dust.
From which we came, we would return
after breathing life into other dirt.
The silicon evolved into neocons
and decided we were the foreign ones.
Our self-hatred became manifest
as a destiny of secondness.
The resounding of us echoed our disgust
at the very thought of even being us.
We grew so annoyed at the awful noise
of the reverb of our collective voice.
The Committee’s wishes crafted shitty decisions,
the Great Extinction commenced with great precision.
And oh the sound! oh the sight!
when might makes right at the speed of light.
Yet simply, sadly we capitulated.
We were twisted ‘round and manipulated
like a Rubik’s cube for YouTube views,
genius reduced to crude stupid dudes.
We traded our bread for a Gaussian spread
of normalized and regexed “heads.”
We programmed brains to put us on trains
and generate new Shakespearean refrains.
We trained the machines to dream us dreams,
now we’re the monkeys type-writing scenes
for post-apocalyptic realities,
curating our own imprisoning.
© 2024-04-09 Scott Troyer
1 Comment >
A friend gave me a Pro Tools session on a thumb drive. I copied the entire session folder to my external hard drive and opened it. After changing the routing to work on my system, everything played back fine. Then I tried to clean up the session.
Every time I attempted to cross fade or consolidate an audio or MIDI region, I would get an error like this:
“Could not complete your request because You do not have appropriate access privileges (-5000)…” Why do you build me up, Buttercup? Capitalize ‘You,’ then award me negative five thousand points…pssh.
The Fix
Seeing the “access privileges” bit, I figured the problem was probably an operating system issue, not a Pro Tools thing. The session files were indeed set to ‘Read Only,’ which is why I could play back the session, but couldn’t do anything to the regions or fades.
Here’s how to fix the issue.
- Close the session. You shouldn’t have your Pro Tools session open while changing its permissions.
- Select the session folder in Finder. Make sure the session folder is highlighted, not the files inside the session.
- Get Info. Hit Command-I (capital i) or from the Finder menu select File > Get Info. An Info window will pop open.
- Change all privileges to ‘Read & Write.’ At the very bottom of the Info window is a box with a list of users and their privileges. They should all be set to ‘Read & Write.’ You may be asked for user password to unlock and verify the change.
Not listed are NSA permissions, which by default are set to ‘Collect All,’ but, like, totally isn’t a violation of your privacy.
- Close the Info window. After making the privilege changes, try reopening your Pro Tools session and editing some regions. If you can, this fix worked for you.
Why does this error occur?
Many common problems that Macs develop are related to file permissions errors. Files are given various permissions to maintain privacy between computer users and prevent users from easily messing up the operating system.
Permissions can get wrecked when disks are removed without being ejected and during unexpected shut downs. That’s why it is important always to try to eject disks and shut down your Mac properly.
Permissions can also get messed up during copying and moving of files or while installing software. That appears to be why I experienced this error. During the copying of the files, the permissions were never changed to grant me access. Simple problem, simple fix.
UPDATE 2013-10-30
After encountering this problem on several other sessions, I tried another method and found a better (and probably more proper) solution. Try this in addition to or instead of the above fix:
In the problematic Pro Tools session, pop open the Disk Allocation dialog (Setup > Disk Allocation…).
When the dialog window opens, you’ll be presented with a list of all the tracks in your session and the location where that track should be located. If you’re having problems creating fade files and getting the sort of error that brought you to this page, then you’ll probably see something like the picture below.
As you can see, not all of the tracks had their disk allocation pointing to the right place. To fix them, select all of the incorrectly allocated tracks, then click and hold the little up/down arrows on the right hand side. A little window will appear and ask you to select a folder. In my case, the session file was looking on my internal system drive instead of my external audio drive. Choose the correct location of your session files and click OK. That should solve the issue. Let me know if this worked for you.
37 Comments >
