Skip to main content

Red Giant Plugins and Open Directory Accounts

This is pretty specific, but it's also pretty annoying and I'm sure I can't be the only one this applies to.


We have images with all the preinstalled software and settings that we roll out to our edit machines as needed for upgrades and what have you. These images once rolled out still need to have certain software serialized as each seat needs a unique serials. Also of note here is that our editors log in with network accounts to an open directory server.

I haven't really tested this extensively but I've seen this issue across OS X 10.8-10.9 and in the Trapcode Suite, Effects Suite, Color Suite... my non thorough conclusion is any plugin that uses Red Giant's serialization method will be affected on any OS X machine logging in with a network account.


Entering a serial while logged in with an Open Directory account doesn't really work, even though there's no real indication anything is wrong, aside from the red X still making your editor feel they are somehow undeserving of a full license. Was it something they said?

I've got no real caption for this. It's pretty straightforward stuff.


Log into a local admin account on the machine and serialize there. It will do the trick and remove the watermark.

Judging by Red Giant's FAQ, the issue stems from the fact that /Library/System belongs to root/wheel. They give you some troubleshooting steps to change permissions on that but I don't really feel like messing with system permissions if I can avoid it and it takes longer than using a local account for one time registration.


I don't even remember when I discovered this, it's been so long it's second nature by now. I do recall being puzzled when I first encountered it though, particularly since we haven't had any problems serializing any of the other multitude of plugins we use through Admin OD accounts.


Popular posts from this blog

AJA Monitoring In Premiere Isn't Fun *UPDATED 4/14/15*

CC 2014.1 screws up playback with AJA devices in a really irritating way. It's stuff like this that really makes we wish Adobe offered some sort of stable release of CC for post houses rather than constantly pushing out updates that fix some things while causing others to break.

We had a RED Dragon project coming in that was going to be extremely After Effects heavy and quickly discovered this fun fact, which required an update to Adobe CC 2014.1 to fix.

CinemaDNG and Premiere's Difficulty in Importing It

While visiting a friend I noticed an empty Premiere project open with an importing dialog box that didn't seem to be moving. When I asked him if his machine was frozen he revealed that no, it wasn't, he had simply dropped a folder containing a feature film's worth of Cinema DNG footage into Premiere and it was taking a while to import. A while in this case meant having run for about 5 hours and having a progress bar that was only barely visible.

I tried to explain his machine or Premiere would probably crash before it could finish, and that even if the import did finish he would not like or want the results. Another friend who works in video/tech was present and surprisingly agreed that although it may take a while, dragging and dropping the whole shebang into the project pane should be just fine. I did my best to resit the urge to facepalm.

He's a shooter rather than editor by trade, and the problem here is a weird one, so I don't fault him for not knowing any bet…

Standards Conversion with the Blackmagic Teranex and Hypderdeck Studio *UPDATED*

Blackmagic has a product called the Hyperdeck Studio which is essentially a tape deck that uses 2.5" SSD's instead of tapes. It even supports deck control via RS-422. They also make the Teranex, a hardware conversion box. So it should be simple to use these two products together for standards conversions right? Load your master(s) onto an SSD, pop it in, patch through the Teranex to an edit station with capture, and batch import your neatly converted media.

Well there are some weird quicks, but with a little help from FFmpeg and an AJA capture interface it all works out.