Replies – Forums – Michael Kammes – Page 33

Forum Replies Created

Page 33 of 42

← 1 … 32 33 34 … 42 →

Michael Kammes
January 6, 2011 at 1:41 am in reply to: Audio Export out of Sync

Sounds like drift because of a pull-up / pull down issue. I’m assuming Avid did a frame rate conversion on the audio to match the video sequence settings, which is why it played out in sync, but not during export. However, the audio export should have followed your timeline settings…so something else may be amiss.

Try bypassing Avid…Open both your exported video in QT as well as your raw sound mix from your sound person. Match up the common in points. Do those TRT match?

Did you give the sound person a countdown and visual 2 pop & tail pop, and did the sound person give you a tail pops and head pops to test sync?

What is odd is that film/video recorded at 23.98 and audio recorded at 29.97 are still in sync – 1 second is 1 second.

Maybe the sounds guys were working in true 24 or 30…not 29.97? Maybe they did a conversion? Maybe you did a conversion when importing the audio? I’d have them verify their timeline settings and frame rate they are exporting things at.

~Michael

.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.com
Michael Kammes
January 5, 2011 at 5:34 pm in reply to: HD 1080P : Feedback on RAM with the KONA

Dear Lord!

I think you may need to start from the beginning, this is unraveling by the post.

H.264 is NOT a good codec to edit with, and it’s no wonder you’re stuttering. H.264 looks good, and is lightweight in terms of file size and data rate but is horrible for editing and for use with NLEs. In fact, the fastest machines out there for both Avid and FCP do not guarantee 100% h.264 HD playback. Best bet is to transcode to a more easily editable codec.

I recommend you start from the beginning and state:

What Gear You have (CPU, RAM, RAID, software)
What file types you are dealing with (h.264, etc)
What problems you are experiencing and WHEN (capture, playback, etc).

I, too, sometimes jump the gun and inquire with pointed questions on issues, when sometimes explaining the issue in context can help immensely.

~Michael

.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.com
Michael Kammes
January 5, 2011 at 4:20 pm in reply to: HD 1080P : Feedback on RAM with the KONA

A few additional notes:

CS5 – and upgrade from CS4 – has a 64bit version of Premiere, if you decide to go with a 64bit OS.

Also, you have not mentioned what codec you are working with. If it’s uncompressed, you’re screwed – Ultra 160 SCSI or a single SATA drive won’t handle it, so you best be capturing into a compressed codec.

~Michael

.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.com
Michael Kammes
January 5, 2011 at 12:17 am in reply to: is EXPRESS CARD PORT SUPPORTED ?

Of course. Thank God I’m not always that “brief”.

Thanks Zane.

~Michael

.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.com
Michael Kammes
January 4, 2011 at 11:51 pm in reply to: is EXPRESS CARD PORT SUPPORTED ?

Do you mean on a MacBook Pro?

A MacBook Pro has a slot for an ExpressCard/34. Each card has it’s own drivers, obviously.

~Michael

.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.com
Michael Kammes
January 4, 2011 at 10:47 pm in reply to: create virtual set

Does the client need to interact with the background?

Lightwave is used quite a bit, and TriCaster uses them for reflections, “3D” environments where a filmed subject can be in back and also in front of the background, etc.

Generically, After Effects, Photoshop, FCP and Avid are used. Hell, if there is no interaction needed, then ANYTHING can be used to create your 2D background – it’s a flat image / video.

Some pointers:

If using a graphic program, keep in mind round pixels vs square pixels. If you don’t, you image will become stretched.

Match lighting on the background graphic as well as subject on green screen. It helps sell the illusion.

As always, do not skimp on lighting (and someone who knows how to light) A bad key is the best way to sell a bad effect. Also, don;t be afraid to transcode your footage of the subject into a more roust codec for better keying. Try Primatte or Ultimatte as video plugins for keyying.

Good Luck!

~Michael

.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.com
Michael Kammes
January 4, 2011 at 6:35 pm in reply to: HD 1080P : Feedback on RAM with the KONA

first rule: verify the software is compatible with your OS. The manufacturer may not support it.

If the manufacturer supports it – great! However, the app may only be 32bit, which doesn’t buy you much – other than the original 4GB can be used almost fully by the 32bit app (if written correctly) while the OS can use whatever RAM is available after the 4GB.

Windows 7 64bit runs 32bit apps fine.

I think you may be over thinking this. Virtually every video editing product and hardware explicitly layout what OSes, RAM and hardware make the software run as smoothly as possible. Attempting to reverse engineer this, too often, ends in disaster.

I don’t know what your main app is…(Combustion?)

Combustion was last qualified (in 2008) for XP SP2 (32bit) Se PDF on this page:
https://usa.autodesk.com/adsk/servlet/pc/index?siteID=123112&id=5562397

~Michael

.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.com
Michael Kammes
January 4, 2011 at 5:41 pm in reply to: HD 1080P : Feedback on RAM with the KONA

I think the real issue here is OS and Application address space.

Let’s use Windows as an example, as Mac OS is slightly different.

Most OSes are 32bit, which only allows for 4GB of RAM (roughly) to be used by the OS as well as an application. (I am using XP here as an example)

If the OS is 64bit, then you have a ton more space to play with, usually only limited by what the motherboard (and the OS itself) limits. A good rule of thumb is that most OSes today – if they are 64bit, SAY 64bit. if they don’t, they are most likely 32.

In addition, if the application is only 32bit – even if you have it on a 64bit OS – the app can only access 4GB (again, roughly) of the available memory.

~Michael

.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.com
Michael Kammes
January 4, 2011 at 5:32 pm in reply to: What is the difference between 2:1 and 2:1s resolutions?

2:1s is an older Meredien based resolution.

2:1s has 1 field per frame.
352 x 243 (NTSC) and 352 x 288 (PAL)

2:1s was once a great format for multimedia content creation (CD-ROMs, etc.)

2:1 has 2 fields per frame.
720 x 486 (NTSC) and 720 x 576 (PAL)

2:1 was often a good balance of quality and drive space “back in the day”.

~Michael

.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.com
Michael Kammes
January 3, 2011 at 9:50 pm in reply to: Error Exporting AAF

Is any of the media within the sequence linked via AMA…or was it imported (and thus, transcoded to Avid MXF)?

You can also try exporting a small section with the timeline mixed down, and make sure your MC version is at 5.0.3.x. (AMA has had a lot of work done to it between 5.0.x and the current release.l

~Michael

.: michael kammes mpse
.: senior applications editor . post workflow consultant
.: audio specialist . act fcp . acsr
.: michaelkammes.com

Page 33 of 42

← 1 … 32 33 34 … 42 →