Francois Stark
Forum Replies Created
-
Have you tried sending smaller files over? Just to check if the encoding on the Unix system is fine. The problem could also be encoding QT files over 2GB on Unix – i know windows used to have a problem with that.
Do the large QT files play back fine in the unix system?
-
Yesterday I captured 90 minutes from DVD NTSC (component) to NTSC DV codec with the Kona LS, and I was surprised by how easy it was. No delay at the end of capture. Captured to a Lacie D2 1TB FW800 drive. Played it out again straight afterwards after trimming in FCP. Flawless.
Our Cinewave system exhibits bad delays at the end of “capture now” over about 5 minutes. Short captures are fine, but you can forget capturing now of anything over 20 minutes.
Definitely a driver issue, and card-specific variations exist on using Capture Now.
Regards
Francois -
The best part is that you will be able to upgrade from FCP 3 to 5 for the same price we have to pay for FCP 4 to 5 upgrades.
-
[Pixel Monkey] “Version 2.0.2 in the Media Composer’s world would be… what about 1985 or ’86?
We tolerate it and move on. Is it smooth and slick yet? No, but it gets the job done.”
Well, well. Fortunately, by today, there are many non-avid alternatives out there that is stable will get the job done properly for much less. In 1986 there was not.
I agree with Grinner – somebody needs a whack on the head…
-
Thanks, but that is how I am running now – using a ADVC100 converter. Problem: It does not play uncompressed codec.
First Prize would be a decklink card but the G5 has too few PCI slots.
Second Prize would be a AJA Io, but the driver does not allow general quicktime to play out through the Io, like decklink does.There’s my problem…
Regards
Francois -
I would suggest a Decklink extreme card. This card can capture from SDI or Component to DV or MJPEG compressed, as well as uncompressed formats, and has a feature in the driver which will alow you to play out the quicktime player (an thus any quicktime app such as Pro Tools) to composite, component or SDI. When you move to a G5, the card will still work, but you will likely run out of PCI slots, since the G5 only has three.
We are using old DC-30 cards in two G4 based pro tools systems. They work with a custom driver written by 5 squared (italian company? – writing from memory here) and can do everything mentioned above except SDI or component in/out or uncompressd. They work extremely well with their own off-line half-res movies, which are very space efficient, but don’t look very clean. They also capture to DV and play it out very well.
Most of our workflow is to edit in DV res on our FCP suites, render the final timeline completely, and export as a self contained DV file for video, together with the OMFI for audio. This gets sent over the Pro Tools suite, which uses the DC30 card to mix to the video without having to capture it first.
The DC30 card will not work in a G5 at all, since it is 5V PCI and the G5 has 3.3V PCI slots – physically incompatible. Don’t even try it. You WILL mess up the G5.
The edit FCP systems still plays out the video to Beta SP (since the DC30 does not have component out), and the pro tools suite lays down the audio to the same tape when they’re finished.
Regards
Francois -
I disagree.
It must be a system-specific hardware problem, since there are so many users out there running FCP 4.5 on many versions of hardware and operating systems without getting your problem.
FCP 4.5 is triggering some hardware problem on your system that 4.1 is not triggering.
Have you tried a different DV deck?
Regards
Francois -
Walter
One of the big issues regarding this process is the fact that upon reconnecting the clips after the media manager process, many clips with speed effects applied will reconnect wrong.
This seems to have little to do with the media manager process, which seems to work right, but more to do with the reconnecting afterwards, since I have found many cases where the same problem occurs when reconnecting exactly the same media clips which have been moved to different media drives. Also happens after redigitising.
This is one of the main reasons why I am getting a shared storage solution for our FCP suites – this will stop me from ever reconnecting on FCP again.
On the other hand, maybe this problem’s been adressed in FCP 5?
Regards
Francois -
You say you tried different RAM configs. I hod lots of RMA-related problems on a G4 before. Have you tried with the base ram that came with the system alone?
I found that running with 512MB was often the most stable.
Kernel crashes are most likely caused by RAM, motherboard or CPU problems, especially if there are many other users out there with the same software/hardware combos without problems.
Regards
Francois -
Hi Joe
The physical output is not the problem. We want to be able to use a video device with the Pro Tools that does not need recapturing from the edit suite, in this case FCP.
So the ideal workflow is>: FCP finishes the edit -> export reference QT movie ( in DV or SD uncompressed) and then send that to the pro tools suite through gigE. The pro tools suite can use that at the moment with DV codecs only, and it works fine. I want a solution that will work with uncompressed files.
Regards
Francois