Olin Padilla
Forum Replies Created
-
Even without the playback component you can still view m2vs on a Mac using VLC (and probably some other 3rd party applications), but the playback tends to be choppy and could be misinterpreted as the wrong frame rate. Transcoding them is a different issue.
As far as I know, MPEG-2 encoding is limited to standard resolutions and frame rates. It sounds to me like it’s a playback issue.
-
When you say it looks like it’s 8-10fps are you judging it by the look of the playback or is it actually reading as 8-10fps? MPEG-2 encoding is usually only for very specific uses (like DVDs). Most Mac video players can’t even play m2v videos, let alone play them smoothly.
In short:
1) Is mpeg-2 really what you want?
2) Are your videos actually suffering from a frame rate problem or does it just sort of look like they are?
-
Here’s the sneaky way to do it:
Tell them to just download the free 30 day trial of CS5. By the time the 30 days are up, the project should be done and they will have already started at least one new CS5 project. In a pinch they will have to buy the full version, BUT not for your project. This way it’s not you that’s making them spend money, plus you won’t have to deal with the same problem next time you work with them.
-
Check you comp from a different view where you can see the depth. Your light is probably not where you think it is.
-
Right click on a cut point and select trim. Is that what you mean?
-
The short answer is no, 520p is not a standard resolution.
Then again, these days most video is for web, so really it could be any sized rectangle you can think of.
Realistically, your client/dev meant 960×540. It is not technically a standard, but is 1/2 the vertical and horizontal resolution of 1080p, and is becoming increasingly common in web video.
You should probably clarify with them.
-
[Chidi Onyejurwa] “Also, I’ve read that since the video will be converted to a flash video once on the site that converting it to flash myself would help keep some of the quality.”
This is arguable. As far as I know, Youtube will always re-encode your video regardless of what you upload. I would love to know a way around this.
Second, Youtube only uses flv compression for low resolution video. Anything larger (640×360 and up I believe), is encoded as mp4 files with h.264 video and AAC audio.
Can you post the specs on the exported (2 gig) video?
-
If sending from FCP to compressor is freezing, then try doing it in two steps.
Export your timeline from FCP using quicktime, the prores codec, and whatever frame size you shot in (there should be a preset).
Import the exported video into compressor, and now apply the Youtube preset.
Hopefully splitting it into two steps will not put as much strain on your processor, and it won’t hang.
Also, if you really did edit with the native h.264 footage, and your sequence settings are set to match the video (h.264), then your exports should be significantly smaller (and basically Youtube ready). Something doesn’t seem right.
-
Rafeael’s settings sound pretty solid.
Remember that you are doing two things here:
1) Transcoding the AVCHD media to a viewable/editable format.
2) Compressing for small file sizes and an easy send.
Since you already transcoded to prores (and I assume you are going to edit with that footage), you should use the .mov files created form the first transcode to compress to h.264.
I wouldn’t recommend Quicktime for the compression, since it doesn’t allow for easy batches. I would use Compressor or MPEG Streamclip.Also, don’t forget to convert the audio to the AAC codec. You will be amazed at how much space that will save.
-
No. No matter what, transcode the 7d footage before editing.
After doing your log and transfer with the HPX footage, right click on a clip and select ‘reveal in finder.’ It should link to a new standalone video clip (not the original P2 folders). The clips revealed in the finder are your DVCProHD videos, and are what you would potentially transcode using compressor, MPEG Streamclip, etc. I believe this is how it works, I haven’t edited P2 footage in a while.
Personally, I would try editing with the HPX footage as is, on a prores timeline. If that seems to cause problems, then you should transcode.
I don’t see any reason to waste half a day transcoding perfectly good DVCProHD footage to prores when it’s already in an editable state. No matter what, those HPX pixels are going to be converted to square. Why not save yourself the time (and the possibility of generation loss) and do it with the final export.
Either way you’re fine.