Floh Peters
Forum Replies Created
-
Brian,
what software version do you use? Exporting ColorFX into self contained files works fine for me in V13.0.3 and 13.0.4 (although I am not sure what you mean by “choke” effect).
-
It seems like the analog input but is only partially solved. While the clips you capture are okay, you get a somewhat non-standard video out during capture. Seems like adding support for the Kona LHi opened a can of worms of problems…
-
There are several components influencing your setup. When you output video via FireWire, the video you see in your record viewer has to be converted into DV codec and sent out via FireWire, which takes CPU cycles. The decoding of the video streams/layers also needs CPU performance (from your source codec into uncompressed format), and the compositing of your layers together into your final result takes CPU performance as well. So it is quite likely that your CPU is capable of decoding the 3 layers, compositing them together and displaying the result on the computer screen, but not powerful enough to re-encode the result back into DV codec to send it out to FireWire.
One thing you could do is to open “Activity Monitor” from your Applications->Utilities folder and to monitor the CPU usage. Most likely on playback of the timeline without sending it out via FireWire your CPU is already maxed out. Then your only chance is either to use codecs for your source material that are less CPU hungry, to buy a faster Computer or to render your material from time to time. -
[ralph conradt] “WHen I import the self contained QT movs that I exported from Edit Suite I think the quality sucks.”
You mean you export your clips from Media 100, and reimport it again into Media 100, and the quality is bad? What do you mean by bad quality? Missing fields? Not enough or too much contrast? Compression artifacts? Pixelation? Usually when you do a self-contained export and reimport the same clip back into Media 100 the quality should be equal to your original clip…
-
John,
you should upgrade to the Kona 6.03 driver for your board. I think V13.0.4 only works with the latest Kona driver version.
-
DVD players do have a different kind of error correction when playing back disks than DVD-ROM drives when reading data. One way of copy protection is to damage some sectors of a disc, which makes it actually difficult to copy them while there is no problem with playback. Not sure if this is the case here or if the disk is simply damaged, but it sounds like threre is something problematic with this copy. Is it possible to get another copy of the original disc? Another option would be to acquire the material into Media 100 e.g. from a DVD plaer via Composite or Component input…
-
QuickTime 7.6.2 is currently not recommended with V13.0.2 (and 13.0.3 as far as I know), since you can experience audio problems with it. Maybe 13.0.4, expected for today, will fix that (13.0.4 will fix Composite inputs on the Kona LHe broken with 13.0.3, with the introduction of support for the Kona LHi).
-
It also could be that the disc is copy protected. Then Handbrake and MPEG Streamclip are not much of a help. Otherwise they should be able to convert the content of the TS folder into a usable file format.
-
This was a joke, right? If yes, it was really funny. While FCP has some nice features (some of them I would love to see in Media100), it definitely is not a syst that “just works”. There are many more places in FCP where you can mess with your settings, and some (like the input selection) are not even within the app. Media100s hardware integration is much more robust, and the preference and project setting management is definitely superior. Plus, it is actually built for peoffesional workflows.
-
[Robert L. Kopf] “If there’s some way to use the Sheervideo codec while doing this, and the resulting digitized footage is usable in say, Final Cut Pro or DVD Studio Pro, then I would do that instead of using the Media 100 codec. “
That does not work. Everything that goes into Media 100 i (with the old P6000 hardware) gets compressed into Media 100 i codec on the hardware immediately. With the newer systems you have a wide range of codecs to chose from, since the incoming video is passed from the capture card to the CPU as an uncompreesed data stream. Still, as far as I know SheerVideo is still not supported in the newer Media 100 versions, and also not (again, as far as I know) in FCP or other editing systems.
[Robert L. Kopf] ” If there’s no way to do this, then what hardware should I use with the Sheervideo stuff, to replace the Media 100 as a capture device?”
Unfortunately the SheerVideo site, although very detailed on other topics, seems not to mention at all if there is a Editing system that supports this codec natively (meaning with a decent amount of realtime capabilities). Why have you decided that you want to use this codec? If you want to edit it later, I think e.g. ProRes would be a better choice, since it is much more optimized for realtime performance in Media 100 and FCP. And at least there is a free decoder for ProRes footage both for Windows and OSX, so if you need to send over files in this codec others can open it with the decoder.