[Jay Cordova]

I was hoping there would be a solution after reading this whole thread, but it appears not!

I may be having the same or a related problem.

I export DVCPRO-HD clips from Final Cut V6 into AE CS3. Things look OK on the computer monitor in CS3, but when exported from AFX the gamma is dark (as seen in QT as well as when re-imported into AFX).

Never had this kind of problem with digibeta footage or with any footage is SD for that matter.

I’m particularly perplexed that these things exported (rendered) from AFX have a darker gamma when imported back into AFX. I’ll post if I figure anything out.

Using AFX legacy gamma looked once like it made the round trip (FCP, AE, back to FCP) perfectly, but I can’t remember all of the other settings in place at that time and haven’t duplicated it again.

J. Cordova
Springboard Creative/Atlanta

[Jay Cordova]

This is a response to the entire thread here.

All of these issues drive me nuts, too, and it’s not just this camera. Plenty have only USB with no way to get usable video out without great hassle, and significant time for conversion/transcoding.

I’ve figured only one way to save the actual raw data in a way that will enable log and transfer with FCP later:

With your camera mounted as a drive on your desktop via USB, go into OS-X Disk Utility and create a disk image of the disk/device. In this way, you can basically archive your raw data directly to a drive, with the file structure needed for FCP log and transfer at your convenience.

This may help when your camera is full and you don’t have time for hours of log and transfer conversion. Mainly, it saves a helluva lot of space and time, if all you need to do immediately is save everything for later editing.

Archiving the disk image to a fast external drive (faster than USB 2.0) may speed up log and transfer process, too.

Please let me know if there’s an easier way to save the raw, compressed data for later use with FCP or general archiving.

J. Cordova
Springboard Creative/Atlanta

[Jay Cordova]

Thanks a ton. I don’t like it, but I’ll accept it and eliminate much more time and frustration. Crashing in manually and archiving works fine anyway. I’ll bump the addition of the firewire board up on the priority list.

Why in the world would they design a machine that doesn’t record via RS-422, and with no insert edit capability whatsoever (if I understand you correctly)?? That seems totally nuts to me.

In any event, thank you oh so very much — I’ll stop spinning my wheels.

J. Cordova
Springboard Creative/Atlanta

[Jay Cordova]

Well, go figure. Switching pins 2 and 8 does indeed work. Thanks a ton.

I didn’t mention that not only could I not control the digibeta A500, but I had no machine control with the Panasonic HD-1200A either.

With the pinouts switched, I have control over all of the machines now (BetaSP 1800, Digi M2000, Digi A500 & Panasonic HD-1200).

I do not understand, and I’m an engineer type. At this point, though, I don’t need to. It works.

Thanks again.

So those of you with the same problem (or similar with other decks not mentioned here) might consider this “solution”, even though your engineering brain says “no”.

J. Cordova
Springboard Creative/Atlanta

[Jay Cordova]

Thanks. So you have this crossover engaged, and are you still able to control other machines, or are you strictly hooked up RS-422 to the A-500?

J. Cordova
Springboard Creative/Atlanta

[Jay Cordova]

Well, darned if I don’t have exactly the same problem. Just got a Decklink Studio, can connect to everything else EXCEPT the DVW-A500.

I hesitate to cross over the wiring for sure but am at my wits end. Gotta be something with the protocol in the Studio card, because the former Decklink card that just came out worked fine controlling all machines.

I haven’t contacted Decklink support. I can’t believe this crossover worked either, and the Blackmagic folks suggested this solution to deal with the A500? Hmmmmm.

Anyone else with the same problem – Decklink Studio won’t work with DVW-A500?

J. Cordova
Springboard Creative/Atlanta

[Jay Cordova]

I’m not sure, but multiprocessor is currently activated, and the problem is there regardless of the multiprocessor setting in preferences.

[Jay Cordova]

I’ve got what I think is a memory related problem with RAM Preview. Machine is 2 x 3 GHz Intel; 9GB of memory. AE CS3 memory settings are the default: Max Memory Usage 120% = 3.0GB, and Max Ram Cache Size 60% = 1.8GB. No apps running other that AE CS3.

I can’t preview over about 30 seconds at 720×486, if I’m lucky. Go figure. Further, if I shift the work area to a totally unrendered area, it won’t get rid of previously rendered frames in order to render frames in the new work area.

And it’s 30 seconds max with a test comp using only straight video and audio (no filters at all).

If I “purge all”, I only regain the ability to RAM preview less than 30 seconds of the timeline.

Other notes are that the green rendered frame indicators on the timeline are not correct sometimes. I can get a preview of a work area only half covered with green “rendered” indicators.

Does anyone have any idea what might be wrong here??

Jay Cordova
Springboard Creative/Atlanta

[Jay Cordova]

Sorenson does a pretty nice job making flash movies.

J. Cordova
Springboard Creative/Atlanta