MPEG 2 compression problem

Hi, I was wondering if someone could please give me some advice on MPEG encoding in Premiere Pro CS3. I'm using the standard MPEG 2 DVD when exporting my movie (which is made up of PNGs 1024 x 576), the problem is its just compressing my movie way too much.
Even when I shrink down a single PNG image to 720 by 405 they still don't look as bad as when converted to MPEG format. Even when I export it to MOV from Aftereffects its still not as compressed, but i need to keep the MPEG format for a DVD.
My movie is only 1 min 40 sec,roughly 50mb I've got 2 other things to go on the DVD which come to about 800mb all up, so I've still got 3.9gb unused which I'd rather use to maximise the resolution of my movie.
I could increase bit rate but apparently most DVD players can't handle higher than 9, surely there must be some way i can get better picture quality?

I'm using the standard MPEG 2 DVD
That would be an interlaced preset, which can wreck any progressive source.
made up of PNGs 1024 x 576
That is a square pixel aspect ratio proportion for widescreen. DVD can't handle that. It'll require 720 x 576 using a 1,4 pixel aspect ratio, so the export is doing come conversion here. Better if your source was also 720 x 576 with a 1,4 PAR.

Similar Messages

Losing smoothcam filter after mpeg compression

Hi, I used the smoothcam filter on a few clips within an 1hr 20 mins project. After rendering, these play fine in FCP7. However after mpeg compression (dvd 90 mins best qual) in Compressor 3.5.3 the effect is either lost or struggles causing unwanted artifacts.
I'm wondering how to solve this. The format is HDV Pal 1080i using this as the sequence preset in FCP7. My capture scratch disc is a Lacie 1tb hard drive via usb 2.0
On advice I trashed preferences (FCP and Compressor) but didn't seem to solve anything and now I also have a problem with dropped frames and red render lines keep popping back in the timeline should I make further edits.
The whole thing is driving me crazy. Does the HDV format have a problem with the smoothcam filter - do I need to transcode these sections?
Any help appreciated.

Yes that's right - I was sending direct to compressor. I exported a small section as you suggested and played it back with Quicktime and the problem remained.
A couple of points to note:
- As I clicked 'Export>Quicktime Movie' and the dialogue box appeared I noticed all the red render bars for all the smoothcam clips appeared again in the timeline. So it doesn't seem possible in this instance to commence an export without these render bars showing
- If I play the clips within FCP after rendering and without making further edits the smoothcam filter works well

Color Correction + DVD/MPEG Compression Produced Noise

I recently color corrected a 3-hour rock concert using FCP and a broadcast monitor. When played from the timeline the concert looks great however after outputting, MPEG compression and authoring a DVD there's video noise over the image. Almost snow like but different. I'd post a screengrab but I can't seem to take one in DVD Player. Any advice?

That's exactly right Jonathan, you need to add the 2:3 pulldown, and I can tell you all why. (I read the post from Max Average, but I'm not commenting that separately)
The DVD specification simply does not support video marked as 23.98 fps (which is how Apple wants to call it) or even 23.976 fps (which is what MPEG-2 calls it). This means that for NTSC DVDs you can only use MPEG-2 video files which are marked as 29.97 fps. This is true whether your encoder (like Compressor) is letting you be aware of it or not. There is no "native 23.98 frame rate" on a DVD and the right way of making the decoder believe it is 29.97 instead, is to use 2:3 pulldown. Any other method would just be wasting bandwidth/bitrate or picture quality, depending on which way you want to look at it.
The 2:3 pulldown process, as specified by MPEG-2, is a way for the encoder of describing to the decoder which of its already decoded fields it should be repeating (displaying once more) and when. These field repetitions are designed to increase the interlaced displayed frame rate from 23.976 to 29.97. This "new" frame rate must be explicitely written into the .m2v stream, to be accepted by a DVD authoring tool, e.g., DVD SP.
I am sure many of you may wonder why it is called "pulldown" when in fact the frame rate seems to be going "up" from 24 to 30, as I did myself back in the nineties;-)
The way to wrap ones head around that, is to think about what whould happen if you just mapped 24 FPS film frames onto the NTSC TV standard which has to display frames at nearly 30 fps on a TV. Of course the movie would run 25% FASTER on a TV than it did at the cinema/picture theatre. In that perspective, the solution had to be to SLOW DOWN (pulldown) the presentation speed on a TV. The engineers of that time (this was long before color TV was even invented)
were faced with a need for film (Hollywood movies) to be translated for TV broadcasts). Of course they could not change the 30 fps used for TV broadcasts (29.97 fps came much later when colors were added;-), so they had to come up with a scheme which made each film frame seem to last 25% longer on the TV screen, than it would have otherwise. "Pulling down" the display frequency from, the physical 30 fps to match the experienced 24 fps was accomplished by letting every other frame be displayed for 50% longer on the TV. On average that is of course 25% longer (slower) which was the goal.
I may be monitoring this thread for further comments.
BTW, BitVice 1.7 runs surprisingly well under Rosetta.
Roger Andersson / Innobits AB, Makers of BitVice MPEG-2 Encoder for Mac
http://www.innobits.com/
As per Apple Discussions Terms of Service:
"I may receive some form of compensation, financial or otherwise, from my recommendation or link."

File Compression Problem

Hello all,
I'm having a strange file compression problem with CS5 on our new Mac Pro. We purchased the Mac Pro to scan and process images, but the JPEGs and GIFs we create from this computer are much larger than they should be when closed (e.g. images that should be compressed to 6KB are reading as 60KB, and the file size is often smaller when opened than closed). Furthermore, anytime we use these image files in other programs (e.g. Filemaker Pro) the inflated file size will carry over. What's even more puzzling is that the same files that are reading as 60KB on our Mac Pro will read correctly as 6KB from a PC. Similarly, if we embed these images -- that were created on the Mac Pro -- into Filemaker from a PC, the image file size is correct. We cannot use the compressed files we create on our Mac Pro because the inflated file size will be passed on to whatever application we use on the Mac Pro (except for Photoshop).
We have been processing images for years on a PC and haven't had any troubles with this. We were thinking for a while that the problem was with the Mac operating system, but after many calls with expert Apple advisers it seems like Photoshop for Mac has to be the issue. We have already tried reformatting and re-indexing the hard drive, and at this point there is nothing else that can be done from Apple's end. The last expert I spoke with at Apple said that it sounds like the way Photoshop for Mac compresses files and how Mac reads file sizes is very different from the way Photoshop for PC compresses files and how Windows reads file sizes. If he was correct, and there is no work-around, we'll have no other choice and will have to return our Mac.
Has anyone else experienced this before? The experts at Apple were thoroughly confused by the problem and so are we.
Thanks,
Jenny

This has nothing to do with compression.
Macintosh saves more metadata, and more previews than Windows - that's one part.
Macintosh shows the size of the file on disk, including wasted space due to the disk block size - that's another part. (look at the byte count, not the size in K or MB).
When you upload the files to a server, or use them in most programs, that extra metadata is lost and the file sizes should be identical.
I can't believe that your advisors spent any time on such a trivial issue...

MPEG Streamclip problem

I use mpeg streamclip but when i try to convert avi to mp4 or whatever itunes is capable of having and it takes all this time to convert or watever and then when i finaly get it on itunes i replay the movie and it is black with no audio.
p.s. The movie plays fine before i try to convert it and i have tried several and no progress.
Pleeeez help me!

There could be several reasons for this.
You could be using the wrong settings.
The file could be corrupt (regardless of whether it plays OK or not)
Mpegstreamclip may not have the codecs at hand to decode the AVI.
AVI is a container not a compression type, it can contain any number of different video and audio compression types which may or may not be supported by mpegstreamclip. The problem primarily is that AVI is so old and outdated it should have been put out of its misery years ago. Indeed even M$ abandoned AVI over 10 years ago. In some cases AVI can contain compression types that can no longer be converted, although these are rare.
Use Quicktime to open the AVI files, use the quicktime inspector to see what compression is used and let us know.

Export Movie to MPEG-4 Problem

I am trying to export an .mov file to MPEG-4 with no compression in Quicktime. The movie plays with no problem in Quicktime. However, when I try to export the file (File|Export|Options), the "passthrough" choice is grayed out and "MPEG Improved" is the highest resolution I can output. The video was taken with an Aiptek Action HD, 720p at 30 fps. At the bottom of the Options page opposite "Compatibility" it says "Image data rate too high for MPEG-4 Video Simple Profile Level 1". "Show Movie Properties" indicates the video is format is H.264 at 4.00mbits/sec and the audio is AAC at 31.98kbits/sec. I tried Google but could not find any information. Any help would be appreciated. Thanks in advance for your help.

/System/Library/QuickTime
ApplePixletVideo.component
QuickTimeIIDCDigitizer.component
QuartzComposer.component
QuickTimeMPEG.component
QuickTime Updater.app
QuickTimeMPEG2.component
QuickTime3GPP.component
QuickTimeMPEG4.component
QuickTimeBMPUpdate.component
QuickTimeStreaming.component
QuickTimeComponents.component
QuickTimeUSBVDCDigitizer.component
QuickTimeFireWireDV.component
QuickTimeVR.component
QuickTimeH264.component
/Library/QuickTime
ACTLComponent.qtx
QTFbx.component
AXELplayer.qtx
Zoomify.component
AppleIntermediateCodec.component
ZyGoVideo.component
Microcosm Decode.component
on2vp3.component
I do not have a ~/Library/Quicktime

Any help appreciated - iTune compression problems

Hi there,
Just bought a second hand iPhone 3g yesterday that has to last me out 5 months before my contract is up and I can hopefully get a 5 if it's out (touchwood).
Transferred some music from iTunes to my iPhone and on the phone speakers it sounds fine, however when I put my headphones into the jack it's incredibly distorted and sounds like it's suffered far too much compression.
I'm guessing this is possibly a headphone jack related problem as opposed to a compression issue? Tried converting files to AAC but made no difference
Any help appreciated!
Thanks
Dan

FYI - the iPhone includes a single external speaker. The opposite grill that appears the same is a microphone.
If this were a compression or format issue, the same would occur when playing the music via the speaker. Using earbuds has no affect on the compression or format. More than likely this is a headphone jack related problem or there could be a problem with the earbuds being used.

JAI CCIT4 compression problem

I have experienced a problem when trying to write out a tiff image using the group4 compression method (CCIT4), the problem is that it inverts the colors of the ouput file, inverting the image before writing or going through the image and inverting manully is too slow. If anyone could please help?
Thanks, Wesley.

The Java Twain package has been updated since, the name has changed to Morena. Now Morena is available at http://www.gnome.sk together with a tutorial and many examples.
For illustration:
Using Morena, pictures from the scanner/camera are acquired in the same way as a file is opened from the disk:
image=Toolkit.getDefaultToolkit().createImage(TwainManager.getDefaultSource());
There are more than 100 methods available in the Morena to get and set scanner capabilities. Below is an example how to call some typical of them:
TwainSource twainSource= TwainManager.getDefaultSource();
twainSource.setVisible(false);     // hiding the Twain user interface and manage scanning directly from the Java
twainSource.setXResolution(100);     // setting DPI
twainSource.setYResolution(100);     // setting DPI
twainSource.setPixelType(TwainSource.TWPT_ RGB);     // setting color model
System.err.println("getPixelType=" + source.getPixelType()); //geting the actual color model
twainSource.setContrast(300);     // setting contrast
image=Toolkit.getDefaultToolkit().createImage(twainSource);
To analyze an acquired image is a straightforward method. The developer needs to create his own class with a Java ImageConsumer interface and to start produce data from the scanner/camera directly to the new class. E.g. if his class has name "myImageConsumer", it receives data by the following code:
TwainSource twainSource= TwainManager.getDefaultSource();
twainSource.startProduction(myImageConsumer);
Data are sent via ImageConsumer interface and can be parsed in the byte/int array.

[Solved] Compression Problem with 7z + Peazip

I like to compress a file with 7zip, which doesn't succeed.
It has a size of 4.4GB and after compression it got about 3,8GB.
If I choose split the file to 1DVD size, it will succeed with a *.7z.001, this is why I know the compressed size. But if I choose single volume, it will give me this error:
7-Zip [64] 9.20 Copyright (c) 1999-2010 Igor Pavlov 2010-11-18
p7zip Version 9.20 (locale=en_US.UTF-8,Utf16=on,HugeFiles=on,4 CPUs)
Scanning
Creating archive /home/xxx/xxx/file.7z
Compressing file.iso
System error:
E_FAIL
The command is:
/usr/lib/peazip/res/7z/7z a -t7z -m0=LZMA -mmt=on -mx5 -md=16m -mfb=32 -ms=2g -w '/home/xxx/xxx/file.7z' '/home/xxx/xxx/file.iso'
The code which will succeed with split file is:
/usr/lib/peazip/res/7z/7z a -t7z -m0=LZMA -mmt=on -mx5 -md=16m -mfb=32 -ms=2g -v4699324416 -w '/home/xxx/xxx/file.7z' '/home/xxx/xxx/file.iso'
Ark compressor also crashes when trying to compress this file, and so is fileroller. This is why I guess the problem lies in 7z, but I don't actually know for sure, because if I use peazip and try to compress the file to a single volume *.zip, it will also crash. But on the other hand I think zip compression is also done by 7z.
Compression ratio is not relevant, it will crash even of store.
It doesn't crash if I use compressor to create *.pea, which I don't want to use.
The compression will succeed with other files, but not with all. From 11 files I try to compress, it succeeded with 6, it didn't succeed with 5. All files are 4,4Gb before compression.
My file systen is ext4, I tried to copy the files to a different hdd also on ext4 and another one with ntfs, no change.
I am out of ideas what I should do, I only can guess the problem is with 7zip somewhere.
Last edited by alocacoc (2014-03-06 06:39:50)

OK, when I compress with peazip to *.7z, it will fill up the directory /tmp, which is 2GB, which is half of my RAM size I guess, till its full. But when I do a split file (to produce a *.7z.001 file with a split limit of 4,4GB (this will also produce one file only), it will not use /tmp.
So maybe the problem is that at *.7z time it wants to cache it to /tmp, and at the split file it will cache to the destenation directory.
This was guessable also the problem why ark and fileroller crashed before, since I kept the peazip error window open and it won't release its temp file in /tmp till its closed and the whole system reacted strangely in this time.
Maybe I have to wait for an update on Peazip or 7zip to see if the problem will be fixed.
Last edited by alocacoc (2013-11-24 22:38:51)

Spoken Podcast compression problem

For the podcast I host I've always edited the audio in Soundtrack Pro and then imported the AIFF audio file into iTunes to compress using the AAC Spoken Podcast preset. This worked great for years but ever since iTunes 9 was released the audio sounds garbled after compression. The other AAC presets still produce excellent sounding audio it's just the Spoken Podcast preset that seems to be broken. I submitted a bug report but wanted to know if anyone else has had this problem or if they know of a fix.

Thank you Arun,
There was no selective deletion on the cube.Roll up is included before the compress process in the chain.
Please find the info below from the table we can understand that DM is going fine.
The latest request in the cube is 1109217 and last compressed req is 1094040
Please find the table result for the cube
QUALOK ROLLUP_RSVD_DUAL ROLLUP COMPR_AGGR DMEXIST DMALL TMSTMP_ROLLUP
1.109.217 1.109.217 1.109.217 1.007.194 1.109.217 1.094.040 20.120.215
Could you please tell me from the above analysis what i can do ?
Thanks
Satya

MPEG Compression Artifacts (aka "Picture Quality Issues")

I can't stomach watching the Broncos / Browns game on NFL Network HD - the signal breaks up with small, rectangualar "compression artifacts" every 10 seconds, or every time there's a sudden movement (like the camera panning to follow the football).
This is what Comcast HD was like, and this is why I switched.
Verizon FIOS HD Picture Quality has gone down the tubes -- very much contrary to the claims of the advertising.

Glenn,
Well, I disagree, so I guess we will just have to agree to disagree.
There are going to be occasional glitches in anything, be it the TV or my car or my house or travel or elections or even my darling wife of 45 years...I have had FiOS TV for 3+ years, and over that time I have very rarely seen pixellation on any channels. I agree, tonight there is some on NFLNet, but I have had the new channels for several weeks now and this is the first time that I can remember anything more than one or two times in maybe 30 minutes. I don't see this as anything more than an unusual occurance that will probably happen again some time in the future, hopefully a long time in the future; I certainly don't see it as a trend, at least until I see it happening regularly.
Just curious, have you reported this to the FSC? I hope you and others have, otherwise Verizon may not even realize there is a problem.
Here is a link to a dslreports.com thread discussing this same issue: http://www.dslreports.com/forum/r21388668-HD-Thr-Nite-Football-on-NFLNET-HD-Pixelating
I guess TV is not just that important to me to worry about a little pixellation. I watch a lot of TV now as I am retired and have some health problems, but gee, it really is only TV.
Justin
Verizon FiOS TV, Internet, and phone
IMG 1.6.0, Build 06.89
Keller, TX
Message Edited by Justin on 11-06-2008 10:21 PM

DVCPRO HD Compression problem

Hello
I've got some great looking DVCPRO HD 720p 59.94 footage. I export it as is from FCP.
When I let DVD Studio Pro compress it to an SD DVD (NTSC 23.98 fps), it looks blocky and terrible.
I've seens some posts about this around, but can't seem to understand the solution...
Thanks
Alex

Well, can I burn a DVD to 59,94?
In compressor any setting I use looks terrible. I tried converting the DVCPRO HD footage to 10bit Uncompressed in case that was the problem (changing the size to 1280x720), but it didn't work either. I can up every single setting (including Frame Control) in compressor to best or highest bit rate, and my preview looks like bad jpeg compression...
Do you think the frame rate could be the issue?
Thanks
Alex

Lightroom - edit in PS TIFF compression problem

Hello everybody,
when I send my image to photoshop from lightroom via edit in function, after I save it (ctrl + s) in ps the output tiff file is always uncompressed regardless the compression setting in lightroom.
I noticed it because the sizes of the tiffs are rather huge. I checked the tiff properties in explorer and it says uncompressed indeed. Every other settings in lightroom edit in ps preferences seem to work. This behavior is the same with dngs and jpegs, just when lightroom is handing over the original to ps. It doesn't occur when lightroom renders its own copy and handing it over to ps afterwards.
A workaround is to use save as in ps but anyway..
Am I missing something, or is it a bug? Thanks for your answer.
Lightroom 3.6 64bit, Photoshop CS 5.1 64bit, Win 7. I also tried it with LR 4 beta and it's the same (due to incompatibility Open anyway option). Tiffs always come back uncompressed as well.

I totally agree. This is easy to replicate. I am running LR4 and PS5 on an IMac.
Open a 20MB dng file to PS5 from Lightroom and then save via Command S. Tif file size is 150MB and compression is at level 1.
Open a 20MB dng file directly to PS5 and then use Save As and choose ZIP compression. Tif file size is 36MB and compression is level 8.
This is a long standing problem! Is it fixed in PS6?

DV PAL Quicktimes compression problem

I am putting out DV PAL QuickTime’s, but noticing in QT pro you can tick a button in properties that makes the compression better and the pic looks less compressed. I want to know is there a way to export them out of Final Cut so that this setting is already ticked and we are getting the highest quality straight out of final cut rather then having to recompress and save it out of QT pro. Has anyone come across this problem before is this a final cut problem or is this just a monitoring problem in other programmes. There is a big difference in quality when you tick the button in QT pro.

Jen:
As Trevor saud, export your movie as Quicktime Movie with default settings and you'll get a full quality copy of your timeline, that can use as source for any further encoding, ie. MPEG2 to use in DVDSP.
There is a big difference in quality when you tick the button in QT pro.
I think you refer to the check button named High Quality you can access when opening the movie in QT > Window > Show Movie Properties > Video Track.
When you check that option you get a better playback quality, right?
If you mean that setting, it's only a playback setting, all your quality is inside of your QT movie, you are not recompressing it. The low quality playback default come from the time when computers had not enough power to playback the DV stream at full quality.

Playing MPEG video problem

I have this problem when I tried to play MPEG video.
I imported a 10 Mb MPEG video to director cast, it used
QuickTime to play.
But the video itself plays little slow at first (the sound
was playing smoothly). It's like the video was buffering while
playing itself at the same time. After a few seconds, the video
plays normally.
My video is 320 x 240 size, running on 24 fps.
My project is 640 x 480 size, tempo 30.
I've updated my QuickTime player to the latest version.
Yes, I did safe video preloading. I placed the video 5 frames
before it is needed to play.
I checked the following settings :
Video, Audio, Paused, DTS, Streaming.
and the Playback is set to Sync to Sound.
I tried opening the MPEG with windows media player, and it
plays smoothly.
But the same problem occured when I tried to play the video
on director stage and director Video: QuickTime preview.
I wonder what was wrong.
Please help.

quote:
Originally posted by:
Newsgroup User
Download a trial version of the MPEG Advance xtra and see if
it performs
any better.
http://xtras.tabuleiro.com
YES
that's it.
that xtra worked.
so there's no other way to play MPEG video without purchasing
any xtra?

MPEG 2 compression problem

Similar Messages

Maybe you are looking for