-
Choppy YouTube Export
I just finished a project in FCP and when it’s exported it looks completely fine; when I upload it to YouTube, however, it gets slightly choppy and I can’t figure out what’s wrong. Here’s the video link: https://www.youtube.com/watch?v=OPn5pOt12qI
The footage and sequence properties are as follows:
Frame size = 720×486
Vid rate = 29.97
Compressor = Uncompressed 10-bit 4:2:2
Data Rate = 28.9MB/sec
Pixel Aspect = NTSC-CCIR 601
Field Dominance = Lower (even)The export settings are as follows:
Compression type = H.264
Frame rate = Current fps
Key Frames = Auto (frame reordering checked)
Data rate = Auto
Compressor quality = Best
Size = Tried a few different ones (current, NTSC 720×486 4:3 and 16:9)
De-interlace source vid checked and prepare for internet streaming checked @ fast startAnyone have any suggestions for better settings? This footage came from an old SD cam we were shooting on — hence the crappy 720×486 — but it just doesn’t feel as smooth on YouTube as it should. Given, some of the shots are pretty shaky, but it bugs me when I see it play smoother from the file on my desktop.
Thanks for the suggestions in advance!
Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
7 Replies
-
[Devon Hennig] “The export settings are as follows:
Compression type = H.264
Frame rate = Current fps
Key Frames = Auto (frame reordering checked)
Data rate = Auto
Compressor quality = Best
Size = Tried a few different ones (current, NTSC 720×486 4:3 and 16:9)
De-interlace source vid checked and prepare for internet streaming checked @ fast start”You shouldn’t let “Data rate: AUTO”. That makes a kind of huge uncompressed file.
Limit the data rate. Try 2.000 Kbps.Your size/pixels is also wrong.
You need to select “Square Pixels” and set a size keeping the 4×3 or 16×9 proportions (if your NTSC source is anamorphic).
rafael -
Played smooth for me, didn’t see choppyness here.
Chris Tompkins
Video Atlanta LLC -
Thanks for the tip on the data rate; I tried 2kbps and the file came out really small (8mb) but the image was extremely pixely/blurry. I’ll try some other rates. For interest’s sake, how large do you think a 2.5 minute video file like this should be?
Regarding the size/pixel issue: do I just need to change the sequence setting in the browser from NTSC-CCIR 601 to square pixels? The footage isn’t anamorphic, so in terms of the size in the export options, should I select NTSC 4:3? Or go with the current option? Thanks again, much appreciated.
-
I think he meant 2000kbs.
Regardless, don’t change your sequence settings.
Edit/finish in the highest settings.
Export “Current Settings”THEN, Compress that file in Compressor or Episode or Squeeze or whatever you use for a compression program.
Chris Tompkins
Video Atlanta LLC -
[Devon Hennig] “Thanks for the tip on the data rate; I tried 2kbps and the file came out really small (8mb) but the image was extremely pixely/blurry. I’ll try some other rates. For interest’s sake, how large do you think a 2.5 minute video file like this should be?”
Increase the data-rate as much as you can allow your self, but always keep it limited.[Devon Hennig] “Regarding the size/pixel issue: do I just need to change the sequence setting in the browser from NTSC-CCIR 601 to square pixels? The footage isn’t anamorphic, so in terms of the size in the export options, should I select NTSC 4:3? Or go with the current option? Thanks again, much appreciated”
No.
A 720×486 Square pixels picture is not 16×9 neither 4×3.
If your original picture is anamorphic (16×90, you need to export to a new size which keeps the sides proportions (H x W = 16 x 9) so you must stick with values like;
– 160 x 90
– 320 x 180
– 480 x 270..
If your original source was 4 x3, the H x W relation must always be 4 x3, so you must stick to values like:
– 240 x 180
– 320 x 240
– 400 x 300..
rafael -
Sorry it took so long for me to get back to this thread, but here’s another update.
I just edited a roller derby video and the same kind choppiness is happening (https://www.youtube.com/watch?v=24-Cf_ndcoI). Again, this isn’t a buffering problem (it still happens after the video has completely loaded); it’s a slight jittery choppiness that happens at random points throughout my videos, and never really in the exact same places. In addition, the clarity seems pretty pixelly compared to other 360p videos online. The vids aren’t as choppy and unclear in 720p, obviously, but one of my questions is why doesn’t my 360p quality seem as clear and smooth as other 360p YouTube videos (I.E,. any music video, College Humour video, etc? I know they’ve got better equipment, but I’m shooting with a Sony EX1, which isn’t a terrible cam). Something tells me that I’m not color correcting correctly either – could this be part of the problem? I’m self taught, so I’m not sure what’s “acceptable” for color levels… I just sort of go until it looks good — any info on this would be great. Sorry for being so irritatingly amateur…
Here’s the media info stats for the Roller Derby video I posted above in case anyone’s curious (info collected by MediaInfo program):
General
Complete name: /Users/TVZ/Desktop/Projects/Roller Derby/Exporting/Audio Correct/Roller Derby Final.mov
Format: MPEG-4
Format profile: QuickTime
Codec ID: qt
File size: 137 MiB
Duration: 2mn 22s
Overall bit rate: 8 047 Kbps
Encoded date: UTC 2011-04-20 20:28:36
Tagged date: UTC 2011-04-20 20:28:38
Writing library: Apple QuickTimeVideo
ID: 2
Format: AVC
Format/Info: Advanced Video Codec
Format profile: Main@L3.2
Format settings, CABAC: No
Format settings, ReFrames: 2 frames
Codec ID: avc1
Codec ID/Info: Advanced Video Coding
Duration: 2mn 22s
Bit rate mode: Variable
Bit rate: 7 911 Kbps
Width: 1 248 pixels
Original width: 1 280 pixels
Height: 702 pixels
Original height: 720 pixels
Display aspect ratio: 16:9
Frame rate mode: Constant
Frame rate: 59.940 fps
Color space: YUV
Chroma subsampling: 4:2:0
Bit depth: 8 bits
Scan type: Progressive
Bits/(Pixel*Frame): 0.151
Stream size: 134 MiB (98%)
Language: English
Encoded date: UTC 2011-04-20 20:28:31
Tagged date: UTC 2011-04-20 20:28:38
Color primaries: BT.709-5, BT.1361, IEC 61966-2-4, SMPTE RP177
Transfer characteristics: BT.709-5, BT.1361
Matrix coefficients: BT.709-5, BT.1361, IEC 61966-2-4 709, SMPTE RP177Audio
ID: 1
Format: AAC
Format/Info: Advanced Audio Codec
Format profile: LC
Codec ID: 40
Duration: 2mn 22s
Bit rate mode: Constant
Bit rate]: 128 Kbps
Channel(s): 2 channels
Channel positions: Front: L R
Sampling rate: 48.0 KHz
Compression mode: Lossy
Stream size: 2.16 MiB (2%)
Language: English
Encoded date: UTC 2011-04-20 20:28:31
Tagged date: UTC 2011-04-20 20:28:38Some contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
Color correcting will have nothing to do with playback choppiness.
Your vid looks fine. It’s a compressed file for web.
Want it cleaner and smoother? Up the data rate when compressing for web.In 720 mode it looks clean.
It looks like you shot 720p_60
Did you compress to a 30FPS file? Youtube prefers that I believe.
Also: Height: 702 pixels
This doesn’t make sense. You should compress using the same size as the original 720 file if you want an 720pHD option on the u-tube version.Chris Tompkins
Video Atlanta LLC
Reply to this Discussion! Login or Sign Up