-
New MacBook Pro and Sony DSR 1800
With the new Firewire 800-only MBP, we are having difficulty getting it to function with our Sony DSR-1800. Using an 800-400 adapter and a 6-pin to 6-pin cable, the deck recognizes the signal and audio comes through fine, but the video freezes on the first frame while the timeline plays. Web and forum searches have turned up others with a similar problem, but no answers. Is this a hardware or software thing?
We’d PREFER not to have to go to an Firewire 400 Express Card, because we use an ESATA Express Card to connect our external drives.
Thanks,
Steven
-
6 Replies
-
Is the problem, after you captured the footage, while playing back the timeline footage on an external monitor freezes or FCP canvas video freezes?
Do you have the correct sequence settings?
-
While playing back already captured footage (an edited timeline)…plays smoothly on the canvas, but the deck freezes on the first frame of video (audio still works fine…just video chokes). That frozen frame is not just what’s indicated by the monitor…it’s what’s actually written to the tape.
Sequence settings are fine.
-
When you stop the playback does it frame on the monitor jump to the where the playhead is paused?
This really sounds like a mismatch of the sequence setting and video out settings.
-
Sometimes…sometimes during playback, if you hit the spacebar to stop and then restart playback, it will jump to THAT frame and freeze. BUT…it’s inconsistent. It NEVER plays video back, but it’s inconsistent about what frame it shows. Bizarre, I know…but it is not a sequence setting issue. To prove it out, opened the same project on an older MacBook Pro and connected via the FW400 port, and it worked perfectly. It’s something about using that FW800 slot on the new one…
-
What is your Ext Video out set as, that is where a mismatch can be, and that is something that give the problem that you are describing. Not saying this is a problem but it might be.
-
Ext video was fine, as well. The editor who was having this issue is now concerned that it may have been a corruption in the source media on the FCP side — not a FW issue after all. If I find out otherwise, I’ll post what we learn.
Thanks for taking the time to help troubleshoot this — we appreciate it.
Steven
Reply to this Discussion! Login or Sign Up