Floh Peters
Forum Replies Created
-
[Gregg Michaels] “So, is the problem the fact that M100 can’t deal with the 1440×1080 resolution versus the 1920×1080 res? Or is it a decoding issue?”
As far as I know it is an issue with the decoding of XDCam (Long GOP MPEG2) codec files. Unfortunately these are not as easy to implement as “regular” frame-based codecs. The decoding of non full-raster codecs is not a problem, since e.g. various flavors of DVCProHD are not full raster and have to be scaled to fill the image.
Apple is doing some rewriting of QuickTime these days, starting with the OSX 10.6 “QuickTime X Player”, which actually takes advantage (or disadvantage) of the new underlying infrastructure. Unfortunately in 10.6 this is not as finished as needed for an editing application, which can be easily seen by the many features that QuickTime Player X lost in comparison with QuickTime 7.
-
[Gregg Michaels] “The AJA hardware is capable of this, why not support it?”
Actually the Aja cards don´t do much in terms of decoding – only the scaling from anamorphic material can be offloaded to the card (still, this is nothing which Media 100 really can take advantage of, as far as I know, due to the fact that it works in full aspect timelines all the time).
But I also would love to see native XDCam support!!!
-
[Marcus Warren] “I am getting frustrated by the long render times in Media 100 and I am looking for a solution”
What kind of render times do you see? There are some things that e.g. can be sped up by having enough RAM and fast harddrives. Other parts could be faster by having something like an MXO2 with the MPEG4 encoding board (if your MPEG4 encodes are too slow). Other parts can only be made quicker with newer CPUs and/or more processors.
-
[Michael Slowe] “From what you say am I right in assuming that the file is correctly in the 16:9 aspect but just that it won’t play at that in a computer? How is the broadcaster going to get it on air in the correct aspect? I don’t really want to play it but I was just checking. “
The file is not in 16:9 aspect. It simply takes the “raw” 720*576 resolution (which can be both 4:3 and 16:9) and throws it on the screen. You can (e.g. in QuickTime Player Pro) tell the computer to display it “stretched”, which compenstes for the fact that Video pixels are not square (as computer pixels) but rectangular (either in a Pixel aspect ratio suitable for PAL 4:3, which is ~1.09, or for PAL 16:9, which is either 1.42 or 1.46 depending on what version of software you use). It is always the same number of pixels, but only displayed differently.
Since you have QuickTime Player 10.0 I think you are running OSX 10.6.x. On the 10.6 install disc there is an installer for the QuickTime Player 7 which has much more functionality than the QuickTime Player 10. You should install it alongside the new one to be able to do this kind of stuff.
[Michael Slowe] “How is the broadcaster going to get it on air in the correct aspect?”
The broadcaster needs to know if the file is 4:3 or 16:9; you need to tell him. On the broadcast signal there is a flag giving a hint to the receivers if the incoming (720*576 pixel) signal is 4:3 or 16:9. This has to be set by the broadcaster correctly, and therefore he must know if your file is 4:3 or 16:9
-
Hi Michael,
both SD 16:9 and SD 4:3 have the same pixel count, 720*576. So your file definitely contains all necessary Pixels. If you have the QuickTime Pro Player, you can manually set the file to show as 16:9 in QuickTime player by pressing Command-J and then setting the Video track Visual Settings to 1024*576. If you then save the file it will open up again in the “right” (correctly displayed on a computer screen) aspect ratio.
-
This message usually shows up if your codec does not support files larger than 2GB and your file is going to be bigger, or if your drive is not HFS+ (MacOSX filesystem) formatted. Are you trying to export e.g. to an USB drive that is formatted for Windows? Or is the drive you want to export to simply full? ProRes does support files larger than 2GB, so this is not the issue here.
-
On what format is he shooting? This whole 720p thing is pretty messed up. We recently had to deliver something in 720p50 on DVCProHD (source was 1080i), which was easily done with the Kona3 cross conversion. But the 720p50 is actually named 720p25 in the DVCProHD deck setting, and while it writes progressive images it “names” them like interlaced frames in its timecode.
-
Have you uninstalled the Aja drivers?
-
You mean that the computer does not start up at all? Or does the Media 100 application not start?
If the computer does not start up, you either have a software/hardware conflict (like the board conflicting with some other hardware in your system, or the board drive being incompatible with your hardware or a component of your system). If Media 100 does not start up, what does happen? Do you get the splashscreen or not? Spinning beachball?
If the computer does not start up at all, go to the BlackMagic website and look if there is a driver that is recommended for your system (OSX variant and PPC platform).
-
Seems to work for me. One thing you could try is to downgrade to the older version of the AE importer if you have a backup of it. It should read exports from Suite V1.7 still fine.