Forum Replies Created
-
Simon Hustings
August 3, 2010 at 12:44 pm in reply to: Audio and video not in sync after compressionCheck your audio sample rates too. I’ve seen issues in the past when encoding to one of the mpeg 4 flavours. If the audio bit rate is too low, the audio can drift. Double check the framerate of the mpeg4 too. Mismatching frame rates and audio rates can cause issues.
All the best,
Simon
“Is it me or do I spend half my life watching little grey bars turn into little blue bars??”
-
Hey Nate,
How is the audio out of sync? Does it drift over time or is it out of sync from the beginning of the clip? Why do you want to reduce the file size before compression? Pro Res is pretty hefty compared to HDV so it would be a big file anyway!
All the best,
Simon
“Is it me or do I spend half my life watching little grey bars turn into little blue bars??”
-
No worries Spike! Happy Cutting!
“Is it me or do I spend half my life watching little grey bars turn into little blue bars??”
-
Hi Nathan,
With the limited information provided in your post, the only thing that comes to mind is that the HD you are saving to is not formatted for Mac (OS journaled). If the HD is set to FAT 32, your file size limit is 4GB. Assuming that the video format of your project is PAL/NTSC or HDV, if your video duration is longer than about 20 mins, you will get an error when saving your file as anything longer than 20 mins will be more than 4GB.
All the best,
Simon
“Is it me or do I spend half my life watching little grey bars turn into little blue bars??”
-
All four look different?!
OK well first off, Motion does except vector based images as long as they are pdf. If you have the artwork as .ai, save as pdf and you can scale without quality loss to your hearts content.I’m racking my brain as to what the issue could be with the colour shift that you are experiencing. With the new colour profiles, are you still seeing a noticeable shift in hues or is it more a difference in the gamma levels?
Using the standard RGB Adobe 1998 profile has never caused me issues. I’m wondering whether it is a display issue more than a literal colour shift issue of the pixels. If you can open the images in Motion and PS and using the colour picker, compare the RGB colour values to that of the originals it might help shed some light on the issue. Can you upload an example of the varying images and their colour issues to the pasture so we can see what you are seeing?
All the best,
Simon
“Is it me or do I spend half my life watching little grey bars turn into little blue bars??”
-
Hi Spike,
FCS does utilise the cores better than it ever has done in the past but there is only so far you can go with a 32bit app. Could FCS use the cores better? Yes it could. Will it happen with this version? I doubt it. When FCS becomes 64 bit is when we’ll really see the difference.
You’ll find the biggest speed bump when encoding your final videos.. Compressor does a great job of making the most of a multicore system. And if you’re working HD vision then those extra cores will help when rendering effects in FCP.
Motion focuses more on the graphics card you have installed than the processors and the AGPs on the Pro are better than those in the iMac. FCP can only use up to 4GB of system RAM but that doesn’t stop you from putting more RAM in your Mac for other apps and processes!!My advice would be to go for a MacPro. It doesn’t have to be the high end model though. The main thing that always pushes me towards the Pros than the iMacs is that the Pros are much easier to upgrade as you go. Extra RAM, graphics cards, HDs, capture cards etc. The iMac gives you very little choice for upgrading. Plus if you’re cutting HD vision you may want to consider ESATA ext HDs. The iMac doesn’t have an ESATA connection.
Don’t forget the other apps out there that are 64bit, like CS5. I used to use Adobe Media Encoder CS4 to create flvs and it was painfully slow. With CS5 and it’s 64bit architecture, the same encoding process flies! I haven’t upgraded my mac but the new app uses my resources in a much more effective, 64bit kinda way. I’m looking forward to FCS 64bit and I don’t think I’m the only one!
All the best,
Simon
“Is it me or do I spend half my life watching little grey bars turn into little blue bars??”
-
Hi Kurt,
Make sure that you’re artwork is RGB and not CMYK. I’ve had similar problems in the past, and by changing the Image mode in Photoshop from CMYK to RGB did the trick for me.
All the best,
Simon
“Is it me or do I spend half my life watching little grey bars turn into little blue bars??”
-
I’m not aware of any plugins and I don’t know what format you are currently shooting and what your deliverables have to be but, if for example, you shot HiDef and delivered Standard Def then you would have a canvas/frame size that is twice as big as you actually need. If you laid the HD footage on to an SD timeline, you could do some basic motion effects (dolly, pan etc) in post without losing overall quality.
The other option would be to shoot your MC battle against bluescreen, key him (or in this case, I guess “him” would be “them”) out and then have fun with comping instead!
All the best,
Simon
“Is it me or do I spend half my life watching little grey bars turn into little blue bars??”
-
Yes apologies, open not gang. I don’t know where my brain was when I wrote that!!
“Is it me or do I spend half my life watching little grey bars turn into little blue bars??”
-
I’m not to sure of a specific plugin for FCP but I know Motion can handle it.
You can use the Audio behaviour in Motion which analyses the audio in a project. Then you can set a variety of different parameters to match the modulation of your audio. In your case you’d probably want to focus on oscillating the opacity of your video element to create a blinking effect.All the best,
Simon
“Is it me or do I spend half my life watching little grey bars turn into little blue bars??”