Floh Peters
Forum Replies Created
-
What composition dimensions are you using? PAL is always upper field first, while NTSC 720 is lower and NTSC 640 is upper as far as I know.
Make sure that you set up your composition correctly, use a comp preset for whatever forma t youa re using.
Do you have the Media 100 software codecs installed? If not, download and install them.
What do you mean by “jump or stutter”? Could it be a playback performance problem? Have you limited the data rate of the codec?
-
Are you working in HD? I don
-
Because QuickTime does not know that it is 16:9 and treats it as it has square pixels. With your workflow you get “true” (anamorphic) 16:9, which is good for DVDs, TVs and so on. To play it back in QuickTime in the correct aspect ratio you have to rescale it in e.g. AfterEffects, or you have to resize the QuickTime Player window while pressing the shift key to allow unproportional scaling.
-
Are you sure the AES/EBU in you selected is connected to the deck? It always have been the way that if one of the digital inputs (video or audio) is missing the other does not show up also. Probably you see yellow boxes next to the audio track selection chekcboxes, and this also shuts down any video input
-
Send me your AE project file (make sure to put an item into the render queue) and a short rendered movie. I will have a look to see what
-
[Bobby Mosaedi] “my green screen composites seem not to be importing correctly. is there a pdf somewhere that says all the settings i need to correctly render footage from after effects adn quickly import into media 100? I’m working with media100 digitized footage 720×486, 48k audio. what im seeing is aliasing everywhere.”
Set up your comp from a template (PAL or NTSC with the correct pixel aspect ratio and numbers, like NTSC D1, 720*486), and leave the pixel aspect ratio as set by the template.
In the render settings, make sure that you are rendering Full and Best quality, and that your field dominance is set correctly (I think it is lower first for D1 NTSC, but I -
[jim Wilcox] “hat would be the difference between ingesting thru this DV input, going in composite to M100 with a DV deck and going into Final Cut as native DV?”
Composite in would result in less optimal image quality. Digitizing in FCP would be fine and even would carry over the TC to Media 100 HD (if you digitize into DV codec), but the image would be darker and have more contrast due to the different approaches of handling the lumaspace of Media 100 (and e.g. Avid) on the one hand and FCP on the other hand.
Digitizing in Media 100 i via FireWire or Component would be fine, and does give you also the correct levels, but probably result in larger files with the same image quality when compared to FCP (native DV comptression vs Media 100 i codec compression). -
[gmfguy] “you can do it with 8.2.2 but be careful,”
I never saw problems like this when using the Software Codec. There were problems with preview and hardware codec, but after Media 100 released the software codec we never saw these again.
-
[JIm Wilcox] “We’re running 8.2 with DV option, which we are finally in need of to import. With all set to DV we can control and import from DV deck, but the material is not coming in native DV, but instead, whatever setting Media 100 is set to (eg 300kb)”
This is the way Media 100 i works. Media 100 i only can work with material in its own codec, and it has a hardware board that converts DV into Media 100 i codec on digitizing.
[JIm Wilcox] “Also, the batch capture seems to not find the TC, so we have to capture live.”
In the hardware prefs, try another DV deck control. Maybe you will find one that works with your deck or camera. Or get a DV player with RS422, which will be much faster for batch digitize and cueing.
-
Yes, it seems like the V8.2.3 VOUT component is not working. To avoid that you could do the following workaround (I haven