This might be the solution.
An unexpected authorization error 14051 occurred.
ID: ePAY : 14051 / Dngl : 1595
I got this error a few days ago. Itâ€™s a new one for me. What caused this? Good question. I have no idea. Pro Tools wouldnâ€™t really start after this.
As usual the Avid forums weren’t very helpful. Which led to this tweet…
For the record, at the time the error occurred I was running OS 10.8.4 and Pro Tools 9.0.6 on a Mac Book Pro with an iLok 2.
I had to force quit Pro Tools. Then I unplugged my iLok 2 and plugged it into a different USB jack. Presto. Working again. Not sure what caused it, nor if switching USB jacks was actually the fix, but I did get it working again after doing so. Hope this helps somebody.
I confirmed again that switching which USB jack the iLok 2 was plugged into made the difference. I would think that this is a problem with that particular USB jack, but all other USB devices work just fine plugged in there. Hmm…
5 Comments >
Where does Bourne end and Snowden begin? Where’s the line between truth and fiction? What’s the difference between copyright infringement and fair use parody for the sake of satire?
After thinking about the scandalous NSA manhunt for Edward Snowden, I realized there are a lot of similarities between the news right now and the Bourne trilogy movies. I tweeted this a couple of days ago.
The next day I thought it might be fun to photoshop Snowden’s face onto a Bourne movie poster. The Bourne Ultimatum promotional image seemed like the best for trying to match up with the photos I could find of our dear whistleblower. (Shout out to the original artists of The Bourne Ultimatum image! See update below.)
The gun in Matt Damon’s hand didn’t really fit the Snowden plot line, so I replaced it with my own hand holding a USB drive (actually an iLok 2). It was a fun little project that only took a few
The day after I posted the image to Twitter, Andy Greenberg, a tech reporter for Forbes, saw it and asked if he could use it for an article he was working on. I was a bit surprised. Here’s the great article he wrote: Take a Break From the Snowden Drama For a Reminder of What He’s Revealed So Far
I wish Forbes wouldn’t have cropped the image, because I think the USB stick really makes the image. But oh well. It’s entertaining to see something I made get spread around a little. And hopefully the image gets people thinking about why nearly everyone considers the fictional Bourne identity a hero, but so many view the very real Snowden otherwise.
Let me know if you see the image out there in the wild. 😉
Update 2013-06-26 11:44am: As you can see in the comments section below, a guy named Jasin Boland, who appears to be the photographer of the original image, has contacted me. I’ve emailed him with some questions. Whether he is the sole owner of the copyright or not is still unclear. Perhaps it belongs to Universal Pictures or other digital artists have claims on it as well? Regardless of original ownership, my manipulations of the image for the sake of satire are considered “fair use” under copyright law. Furthermore, I claim no ownership or copyright of my manipulated image and have received no compensation for its usage anywhere.
Update 2013-06-26 12:35pm: I contacted Andy Greenberg at Forbes about the situation. This is his reply:
7 Comments >
…I checked with our editorial lawyer, who says that it’s “quintessential parody use. There is no actionable claim for infringement.”
She says she’s even planning to use it as an example in a law school class she’s teaching next semester.
or… How to release a new version of your product/service and bring an entire industry to a screeching halt.
Shown: original iLok on top, iLok 2 on bottom
PACE has changed how their customers interface with their infamous iLok. The iLok is a DRM dongle, that many software manufacturers use to manage licensing. Formerly, all licenses were managed (mostly just fine) through the ilok.com website, which is now an insufferable â€œsupportâ€ site. The new, prematurely launched system PACE requires users to install the iLok License Manager application on their computer.
Ok, no big deal, right?
I recently purchased several plugins to use in my audio production. Iâ€™d love to use these great new plugins, but I canâ€™t because the PACE application is horrible.
In order to use the plugins, I need an iLok 2, which has to have the licenses on it, which must be loaded onto the iLok only by using the iLok License Manager, which wonâ€™t even allow me to sign in. This is the error I get.
The session you were using is no longer valid. Press OK to establish a new session.
Pressing OK makes the error go away, but it comes right back when I click â€œSign In.â€ The iLok support site doesnâ€™t list this problem as a issue I can submit a support ticket for. So thatâ€™s it. I canâ€™t sign in.
Maybe it is just as well. Even if I could sign in, the advice on the the â€œstreetâ€ is donâ€™t try to sync your licenses, â€™cause you might lose them.
PACE has acknowledged there are issues, but has been otherwise silent.
If this were a football game, PACE fumbled at kickoff, bungled the whole first half, refuse to answer any questions at half time, and amazingly the fumbled ball is still loose in the second half.
I think this screen grab from the iLok.com website says perfectly what many digital audio workers are thinking.
A funny thing happened with some of the content on this page. I can’t tell the story just yet, but I bet it’s going to be a good laugh when it’s all over. Interweb lulz.
As promised…a funny story. After poking around my site stats and hits, I discovered someone was hot linking me.
If youâ€™re not familiar with hot linking, itâ€™s like stealing cable TV from a neighbor, except it hurts the neighbor instead of the cable company. I had a bandwidth leech!
Anyway, a very popular, well-respected pro audio plug-in development company (who will remain unnamed, because it ended well) was using an image from my site on their support page. It was the photograph I took of two iLoks, which is featured at the top of this very blog post.
I knew I could do something funny with the hot link and maybe get a free plug-in out of it. So I created this new image to replace the one they were linking to on my server.
The names of people and plug-ins are blurred out to protect both the guilty and the innocent.
This meant that the above image would now show up on their site. Zing!
I had formatted it to look nearly identical to their artist endorsements in hopes that it might ride under the radar, remaining visible on their support page for as long as possible. For a short while this unofficial endorsement was live on their site.
Long story short…I uploaded the image and went to bed.
Surprisingly, less than 12 hours later I received an email from one of the companyâ€™s developers. He basically said, â€œwell played,â€ thanked me for not goatse-ing them (If you donâ€™t know what that is, donâ€™t Google it.), and let me pick out a free plug-in. Woohoo!
Moral of the story: Hot linking costs everyone something.
Side note: The very same iLok 2 thatâ€™s in the picture featured in this debacle must have a desire to make me famous/infamous. It is the very same iLok I photographed to use in the satirical movie poster THE SNOWDEN ULTIMATUM, which was featured in Forbes and lots of other places. Thereâ€™s something strange about that iLok.
19 Comments >
Here is how I fix this Pro Tools error.
Really? A typo in the error? Grrrrr…
Ever get this error? Canâ€™t open your session, right? Not only is it a major workflow stopper, but the double punctuation typo at the end is annoying as well.
Luckily, the solution is quite simple.
This is the quick fix that works for me and my particular setup of hardware/software. Your mileage may vary.
- Quit Pro Tools
- Restart Pro Tools
- Open the session that wouldnâ€™t open before
- Get back to work
The IT mantra â€œHave you tried turning if off and on again?â€ waves the problem away like a magic wand, but why is this problem happening in the first place?
The last time this error occurred for me, I noticed that it was after I had ejected my audio hard drive, removed my iLok, and left Pro Tools open, but put my machine to sleep before Pro Tools could issue the panic message: â€œHey! Whereâ€™s your iLok, buddy?! Thatâ€™s it! Weâ€™re shutting this whole thing down.â€ Then when I went to reopen the last session I was working on, boom, the error in question occured.
Iâ€™m guessing that between the time I ejected everything and the time I plugged it all back in and tried to fire it up again, Pro Tools had switched its default sample rate from whatever my Mbox 2 Pro says it was to whatever my MacBook Pro thinks it should be. Then when I try to open a session with a particular sample rate that doesnâ€™t jive with what the current rate is, Pro Tools freaks out because it thought it knew what was right, but doesnâ€™t even know anymore, man.
Disclaimer: I donâ€™t actually know how or why the error is occurring. These are just my slightly educated stabs in the dark. If you know anything more about this error, why it happens, and, most importantly, why thereâ€™s a typo in it, please leave your thoughts in the comments section below.
No Comments >