Floh Peters
Forum Replies Created
-
[Maxwell Federman] “As I recall the limitation preventing me from running Producer on my G4 PowerBook was the need of an Intel processor…”
Producer does also work on PPC/G4 systems, but you won´t have much fun with all codecs except maybe DV. The problem is that the codec handling takes some CPU power, so the Intel laptops with DualCore CPUs have a big advantage over PPC systems.
And if you are considering one of the newest MacBooks you should be aware that the MacBooks (13″) do not have a FireWire port. So if you want to transfer footage via FireWire or if you want to view your video signal on a video screen you need a MacBook Pro or one of the older MacBooks with FireWire.
-
[Paul Crowe] “I was going to do this by loading the M100 V13 over the top of my V12 and then just installing the FCStudio 2 suite on the same drive. Obviously, I’ll need to make sure the AJA drivers/etc are on the same drive as well (they’re currently on the FCP side). Is it this simple as this or am I missing something? “
It is that simple. Only make sure that you have the 6.01 Aja drivers, and if you have a Kona 3, do NOT upgrade the board firmware. Plus, make sure that you only upgrade to QuickTime 7.5 and not to 7.5.5 (see the QT 7.5.5 thread below
[Paul Crowe] “So once I get all the adobe stuff, FCP, M100 etc, etc all on the same drive I guess I can just uninstall everything on the second drive and use it for storage – does this sound like a plan? “
If you don´t need the drive for storage, you could keep it as a second boot drive in case you have an emergency. I would set up the V13 partition and make sure that everything is fine there. Then I would use Carbon Copy Cloner to clone the startup drive to the second drive in case that some update or a HD failure messes around with your boot drive.
-
You can use a Firewire to Video converter with producer to view your video, or a DV camera to convert the FireWire signal fir monitoring. I think there were some compatible converters posted in a thread some weeks ago. Maybe you should do a search for it.
-
Yes, I know this problem, but since it is a displaying problem only I guess its priority is not too high.
-
[CJ MacPherson] “That was it Floh!!! Preferences – Video Output – HDe “Analog” to composite. When I first set up the preferences, I completely missed the “HDe” selection. That’s what 3 hours of sleep will do to you…your mind just isn’t working. I checked what you both suggested, and thank you both. I still feel stupid for not catching that…..”
No problem. Sometimes these little things get overlooked easily, especially when having not enough sleep, and when working on a new system.
-
Are you sure that you installed Media 100 Suite and not Producer? And did you install the Aja Kona 5.1 drivers? Plus, you need to set up your Media 100 system to use the Kona hardware, under Preferences->Video Output, select HDe and set “Analog” to Composite.
-
XML is basically only a set of rules describing the formatting of a document. The content of the document is not specified by the XML format. Media 100 does support the Apple FinalCut “flavor” of XML, but this does not have any relation to the XML format that is used to move Media 100 files to AE. They use the same “language”, but the content is completely different.
Plus, you still need to bring your media files over independently of the XML; the XML only acts as a sort of EDL, only with much more details and with a reference to the media files.
I think when you moved your files to the PC you lost your type/creator info, which is what is causing your problems now. When packing them into a .sit archive you preserve those info, and you should be able to open the timeline with the media files in V13 (or V12). -
[Ted Joyce] “What is involved in referting back to the earlier drivers? I’ve had the Kona for 3 wks and of course updated the drivers as they suggested which are supposed to improve performance and reliability of the Kona3.”
You can use the latest drivers, but you have to use the earlier firmware. If you did not run the firmware update application after installing the 6.01 drivers everything is fine. If you did run the firmware updater you need to run it again, and use the “revert to 32bit firmware” button to downgrade the firmware again. You still can (and should) use the 6.01 driver with the earlier firmware.
-
Media 100 does work natively with ProRes and other codecs, and it supports import from EX1 material (although it does not support the EX1/LongGop MPEG codec natively). Stability is very good, at least for our workflows, and it is much more reliable than FCP (at least if you run into a problem it is reproducible, unlike FCP problems which seem to float around and never tend to appear twice during the same task).
-
Bobby,
you should get in touch with techsupport about that. 720p 59.94 is not a format we are working with, so I cannot say if it does work in reality. It should work in theory without a slow import of the media files; the Media 100 app does need to do a (very very quick) media update, and it does need to create separate audio files from the original clips in case the audio is combined into the video files, but both steps are extremely quick even on very large and complex timelines. Maybe you really did discover a bug in the support of 720p 59.94 media timelines.
Maybe you could try it out with a relatively simple timeline from FCP to verify that it is really a bug…