[Cory Caplan]

I will be expecting my check from Adobe any day now.

[Cory Caplan]

Got it! This had been bugging me since installing Snow Leopard. I didn’t spend too much time on it, thinking it might be a SL thing, but I looked again this morning, and decided it wasn’t SL, because more people would be reporting it.

Ran the update, failed again.

I looked in the /Library/Logs/Adobe folder, and double-clicked the most recent log. It unzipped it in the ‘downloads’ folder. Opened the log. cmd-F ‘Error’ and searched through the errors.

Found quite a few of these “File already present at “/Applications/.AdobePatchFiles/{7B92D….”

Finder cmd-shift-G /Applications/.AdobePatchFiles/

Delete *all* folders in that patch folder.

Re ran adobe updater.

Rejoiced.

[Cory Caplan]

As I have a fully CCC backed-up Leopard install, I went ahead and upgraded to SL. The driver seems to work, albeit in 32-bit mode.

Off Topic for SL: although I’m sure there’s a lot of streamlined/removed legacy code, I think a lot of these people reporting ’20 GB freed up’ may not realize that Snow Leopard calculates space differently–

Before the update, I had about 89GB free on my ‘289 GB’ drive, (30.7%) and after the update (with Rosetta) I had ‘103GB’ available on my ‘319 GB’ drive (32.2%) So though it seems like I “got 14GB”, (89-103 GB Free) I only got 1.5% or 4.3 ‘Old GB’ or 4.8 ‘New GB. Sneaky, sneaky Apple. Aah, you can’t hide from inflation.

[Cory Caplan]

Just got this response (within 30 minutes on a Sunday AM at that…) from Firmtek support..
..I assume this is with respect to the fact that most of us will be running Snow Leopard in 32-bit mode anyway

https://hothardware.com/News/Apples-64Bit-Snow-Leopard-OS-Installs-32Bit-Kernel-By-Default/

__________________________

If you are using the 32-bit default mode of Snow Leopard, the existing 5.3.2 driver will work
with the SeriTek/2SE2-E. However, a restart may be required when changing hard disk
configurations.

FirmTek is currently testing a new Snow Leopard compatible driver and plans to post it in the
download section of FirmTek.com once it is validated. The final driver will probably be
available within two weeks.

Thank you,

Michael
FirmTek, LLC

[Cory Caplan]

Thanks for this. I was about an hour from going to the Apple store to pick up SL. Considering my startech eSata dock is my new beloved part of my workflow, this would have been a bad, bad thing. (Firmtek S2e2 here…)

[Cory Caplan]

PNG Fields (composite mode) was the answer, however, it took me a long time to figure it out.

I had to RE-EDIT them into the timeline after I had changed the alpha mode from black to straight. (which solved it) Just changing them in the bin didn’t.

Is this standard behavior for FCP– is there any way to change these attributes en masse after the clip has been edited in? I can right click on the clips in the timeline, then choose ‘Item Properties’ > ‘Format’ but I still have to change them one by one…

I’m just glad it was a few gfx, not a whole 30 minute show or something. The whammy of working in RT, but rendering bizarre would have killed me.

Hope this helps someone else.

[Cory Caplan]

Good call. But no love. These are prefab ‘slates’ from the client’s client’s client’s company. And that’s all that’s on the tape. Plus, the elements they want removed are from the original composite, generated by some 3D/motion graphics house, so we’d really have to go further up the chain… This was all about CYA for me.

Thanks everyone!

Cory

[Cory Caplan]

Thanks. It was so crazy, and they were so sure, there was this little voice of paranoia in the back of my head– and though I ‘grew up’ around a digibeta linear suite, I never actually worked it. I know there were lots of ‘tricks’ but this just seemed insane.

[Cory Caplan]

Thanks for the suggestions.

the PNG isn’t interlaced, and clearly isn’t the problem, as I can change the codec, and it works fine.

As for the recommendation to do it in Motion on AE, yeah, I had to move a lot of the project to AE, but I still need to do the name/web super and the disclaim in FCP because of the 80 or so different versions I have to generate. Luckily (?) I can do the workaround with animation codec or whatever, if I don’t find a fix.

This is clearly a Prores glitch..

[Cory Caplan]

I only have this problem if I render in Prores422. (No difference between HQ ON/OFF)

This must be a recent development or somebody surely would have noticed this, yes? Kind of a big deal..

If Avid DV50 can do it, surely Prores can?