This content has been marked as final. Show 40 replies
What kind of source media? What sequence settings?
The source media is an mpeg1 file, 25fps, 320x240 (1.0), Average Data Rate: 147 KB / second. (originally captured from 16mm B&W film at 24fps).
Sequence settings are as follows (if this is what you are referring to):
Editing Mode: DV NTSC
frame size: 720x480 4:3
pixel Aspect Ratio: D1/DV NTSC (0.9091)
fields: Lower Field First
Display Format: 30fpd drop frame timecode
Sample Rate: 48000Hz
Display Format: Audio Samples
Preview File Format: NTSC DV
Codec: DV NTSC
Mezimum Bit Depth: unchecked. Maximum Render Quality: unchecked.
My own view is that source file is just not suitable for editing in Premiere. A consumer application may be the better choice here.
I can't believe that a professional tool like premiere can't handle this file. The timeline preview shows everything perfectly.
Here's some breaking news though: I just exported the 1 minute video to quicktime and the resulting video is perfect! I used the default export settings. However, the resulting file is about 250Mb as a quicktime file verses 12Mb as mpeg1 file. My ultimate goal is to put this video file on the web, so I guess I want the smallest file possible which looks to be mpeg1. (tell me if there's another format that is better for web streaming).
Here are some of my quicktime export settings.
video codec: DV/DVCPRO-NTSC
Frame Rate: 29.97
Field Types: Lower First
Aspect: D1DV NTSC (0.9091)
I'm hoping someone can point out some other setting I can try for a smooth mpeg1 export. Thanks again in advance.
--also, I wanted to make a correction. I can export to avi successfully (also approx 250mb), but mpeg1 and wmv have the mysterious jitter.
Your footage is 25 frames per second then your project should be set to 25 fps not 29.97. That's where your flickers coming from. You went from PAL to NTSC.
I just tried exporting mpeg1 at 25fps (both in PAL and NTSC (forced)). This did not fix the issue.
If the original PAR is 1 and you render out .91 it'll look funny in quicktime because quicktime doesn't take into account for it like window media player does.
H264 is better for streaming you just have to set the bit rate manually 3,000k/s should be good for your 4:3 project
Just tried the H264. It too had the stutter problem. But the file size was smaller (25Mb, vs 250Mb for avi and quicktime)
MPEG1 doesn't support interlaced video, so your source file is progressive.
Create a new sequence with the exact parameters that match your source file.
Export to same.
ok. I painstakingly re-did the whole project last night with the exact same settings as the original source video and I still get stuttering with mpeg1. Now I'm becoming hell-bent on resolving this issue. Anyone have any ideas? Please keep them coming. We must find a resolution!
Can you post a screenshot of your sequence settings dialog?
(I tried posting a screenshot of the sequence settings pop-up window, but it was not big enough to see clearly on dotphoto, so I'll transcribe everything - if you know where I can post a decent sized picture for free, let me know). As well, the avi export played back perfectly with the same settings. mpeg1 and wmv are the problematic ones. Thanks for your help!
Editing Mode: Desktop
frame size: 320x240 4:3
pixel Aspect Ratio: Square Pixels (1.0)
fields: No fields (Progressive Scan)
Display Format: 25fps timecode
Sample Rate: 48000Hz
Display Format: Audio Samples
Preview File Format: I-Frame Only MPEG
Codec: MPEG I-frame
Maximum Bit Depth: unchecked. Maximum Render Quality: unchecked.
Your sequence settings look great. I don't see any problems there at all.
Would you mind documenting your MPEG1 export settings in the same amount of detail? I'm particularly interested in the info under the Video tab.
Here are some relevant tab info. (Let me know if you want other tabs): I'm wondering if CS4 is buggy.
MPEG1 (I also tried VCD)
video codec: MainConcept MPEG Video
TV Standard: NTSC
Frame Width: 352
Frame Height: 240
Frame Rate: 25
Field Order: None (Progressive)
Pixel Aspect Ratio: 1.0000 -Square Pixels
Bitrate Encoding: CBR
Bitrate [Mbps]: 1.15 (also tried 3 - didn't help)
M Frames: 3
N Frames: 15
Closed GOP every: 0
Automatic GOP Placement: unchecked
Macroblock Quantization: 6
VBV Buffer Size [2Kbytes]: 112
Noise Control: Sensitivity checked
Force VBV Delay: Computed by the Encoder
Write Sequence End Code: Yes checked
Ignore Frame Interval: 0
Reaction Parameter: 0
Initial Average Activity: 0
Minimum Frame Percentage: 25
Pad Frame Percentage: 0
Is there a reason you want to use MPG1 for the web? I think you will find other codecs much more effecient/bw intensive. Such as flash. Try on the of the flash presets and see hwat happens
> (tell me if there's another format that is better for web streaming).
Curt is correct. Flash is by far the best choice for web video.
BTW - I don't see anything wrong with your export settings, either. So without seeing the source video and the exported video, I can't give you any advice on what to do other than to switch to Flash.
I just tried the .flv format, and it still had the stuttering. For web streaming, you are right. But the thing I like about Mpeg1 is that it plays on a lot of players and the size is reasonably small, and the audio and video are in one file. Anyway, this problem is interesting. The timeline, and some exports show everything fine. If I make a new project, and take a good export (avi file) as an input file, and export that as an Mpeg1, it works fine (except the resulting video is slightly more blury and less contrast).
>But the thing I like about Mpeg1 is that it plays on a lot of players and the size is reasonably small, and the audio and video are in one file.
Flash players are installed in like 98% of the computers in the world. I don't think MPEG1 players have quite that wide of a distribution. ;)
MPG1 file for equivalent visual quality of full motion video is going to be larger than flv, or wmv, or h.264.
Any last ditch thoughts on what else I can try? I agree I'll go with a flash output file, but even this has some stutter in it. Is there another tool I can use to convert my "good" avi or quicktime file to a flash file (other than Premiere?) (Premiere makes the output file a bit blury and darker)
Without seeing the stutter, I don't know how to advise you. Your description fits inverted field order or incorrect pulldown, but since your source is MPEG1, neither of those apply. So something else is going on.
I haven't exported to mpeg-1 in years. Too big for the internet but still a decent codec for local playback like PowerPoint. I think my grandmother still uses it....but seriously, have you tried playing the flash or wmv files on a different computer?
I just tried copying the mpeg1 and flash files on a separate computer, and it still shows the stuttering. Sometimes the stuttering is more pronounced like the whole screen quickly goes to a different frame, and then back again several times. And I now understand that mpeg1 is old school -just shows I'm not uptodate. So, I'll forget about Mpeg1, but let's focus on f4v, and mpeg2. I assume mpeg2 is still the standard for dvds. Anyway, let's keep the ideas coming. I'm going to try doing this export on a different computer, even though I don't think that should change the result. You know what? It's 10:42PM on a Friday night and I'm still working on this problem when everyone else is out having fun! This has got to pay off big sometime...
the studdering is a local problem there. its not some overall bug with AME. So, could be your hw or config, but more likely your source; is my guess.
So, can you post a short example of this source clip of yours so we can try it. That will eliminate your machine or not.
> TV Standard: NTSC
Frame Width: 352
Frame Height: 240
Frame Rate: 25
Why TV Standard NTSC with Frame Rate 25 fps
As desperate as you are, try exporting with fields. Also go back to square one and run Gspot on your source footage.
ok guys. I put my project up on my ftp site, for those of you bold enough to witness what I am dealing with (hopefully with better results). Just go to:
ftp://will.etowns.net/ using internet explorer or any ftp client, and download the zip file "Angel_Trailer5"(66Mb), or the folder. They are the same thing. This is the whole project. The Premiere project is called "Angel_Trailer5.prproj", and the original source video is "Angel.mpg". My goal is export to an f4v file (or mpeg1) without stuttering. If you export it, you will notice stuttering within the first 30 seconds, but if you export to quicktime or avi, there is no stuttering. Let me know how it goes. I'll try leaving my ftp server on for a few days. email me if you have any issues with downloading the files. (email@example.com).
Thanks a lot for taking the time to look into this.
...also I ran Gspot, and everything is ok with my source file, in terms of having the right codecs. Also tried exporting with fields (upper and lower). No luck. I tried re-doing the entire project on a separate computer, and I got the same results. I'd be very curious to see if someone downloads this project from my ftp site and discovers why this is happening.
Just curious to see if anyone is looking into my export problem?
I downloaded the .zip, though I only have 2.0 so what I find may or may not be helpful.
It would be interesting to see what your results are, even if it's Premiere 2.0
I did some tests using your project and some old mpeg1 sources that I have, and my conclusions follow. I posted this same info in another topic:
I think that mpeg1 source exported to mpeg1 output is broken in Pr CS4. Almost all Quicktime exports are broken.
On Windows, I've seen issues with the latest MainConcept codecs in other applications besides Premiere, and odd results using Apple codecs in the same programs.
So I can't tell you for sure if the mpeg1 issue is MainConcept's problem, or a problem with Adobe's implementation of it. It's likely a combination of both, and I suspect the same is true for the Quicktime stuff. As far as I'm concerned, QT 7.5.5 is rubbish.
I didn't test .avi source to mpeg1 output, so maybe exporting as an .avi file that works for you and then importing it back into your project for export as .flv will do the job.
Jeff, thanks for the info. I buy your explanation, considering all the testing I have done. I hope Premiere CS4 fixes their export issue. BTW, the quicktime export works fine for me for this project. I'll figure a way to convert the avi to flash file. (Pr CS4 can do this, but the end result looks a bit blurry to me for some reason. I'll look for another tool)
Thanks for everyone for looking into this. I appreciate it a lot. Feel free to add any comments to this thread in case someone else experiences the same issue.
I have been having issues related to revisiting a CS3 project with CS4. Some of the cross dissolves refuse to work, even when deleting and replacing them. It's as if they weren't there. This particular project had 3000 pixel wide PSD's panned and scanned. They are all shaking badly on the timeline and in the exported master. The project is a standard def widescreen with a mixture of P2 media (scaled-panned etc.), standard def video and PSD's.
I had to overlay the original avi master exported from the previous CS3 project in places in this new version of the video to cover up the jitter problem in areas of the CS4 project.
Exported Successfully after much frustration.
Breakthrough News!! I gave up on using premiere to export to flash or mpeg1 from an mpeg1 source. Because Pr CS4 did manage to somehow produced a good avi export, I looked for another tool to convert the avi to flash. I tried "AVSVideoConverter", and it did not do a good job. But I tried another tool called "video-to-flash-converter-pro", and it worked much better!! So my conclusion is this. Try different tools - they might make a difference. I wish all tools worked good, but this is not reality. Especially with Pr CS4
Charles, when you say "exported successfully", are you referring to using your exported portions of the CS3 project directly in the CS4, and exporting the whole thing in CS4? This tell me CS4 is still messed up. I'm hoping this will get fixed in an update soon, but who knows. Adobe needs a reason to sell us CS5, right?
The successful export was based on a time consuming troubleshooting work-around.
This was a corporate video that was played at a fairly large meeting. Several months later other departments of the company wanted to use the same video, but with some shot changes that are relevant to their departments. In the meantime, we upgraded to CS4 and had to open the CS3 project with CS4 (We uninstalled CS3).
I narrowed down the jitter problem to a graduating Gaussian blur added to a PSD on Video layer 1 that had an image above it on Video layer 2 with a transparent background. Gaussian blur and fast blur cause unacceptable image shake when the timeline is rendered and the shaking exists in the exported AVI. Fortunately, I was able to overlay segments of the original CS3 exported avi over the shaking areas in the new CS4 project because those areas were not changed.
The overlay presented yet another minor problem. The aspect ratio of a widescreen NTSC video exported from CS3 is about 8 pixels wider than that exported from CS4. So I had to stretch the old CS3 overlayed avi segments to a place on the timeline where the aspect ratio change was not detectable.
*It is possible that one of the editors stretched the width of the CS3 avi. One person in the forum did confirm though that CS3 exported avi's with a slightly wider aspect ratio than CS4.
We had a few other weird problems with this converted from CS3, CS4 project:
1.) Certain still image transitions failed to work. They would appear normal until rendered. The exported avi would be missing the transitions.
I found a workaround... For whatever reason hitting the "reset" icon in the Effects Control pallet (keyframe added) fixed the missing transition problem.
2.) Some timelapse, scaled down P2 1080i footage on the timeline exported with an odd unintended effect. The sky with clouds would hold a few frames, then jump ahead. Kind of a stop-start effect that was not in the original footage.
Didn't find a work-around.
3.) A still image at the end of the video shook violently in the export.
I fixed that by being able to overlay the original CS3 avi over this area.