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

Similar Messages

  • DV/DVCPRO NTSC Compression not working

    When I export a sequence to QT movie using DV/DVCPRO NTSC compression (either directly to a QT movie or using QT conversion) I get what looks like a solarized effect (maybe 6 colors total) and the colors are all off - mostly browns and dark tans with hard lines between them, grainy.
    If I export with no compression, it looks fine.
    It also looks fine in FCP itself during edit and playback, etc.
    If I take this project and clips to another machine, it exports into DV/DVCPRO NTSC with no problem.
    This just started happening. It was working fine for months with the same settings.
    I've tried archive and reinstall the OS system as well as trashing and reinstalling FCP. No change. Using OS 10.4.11, FCP 5.1.4.
    I don't know what else to do other than wipe the drive completely. All suggestions appreciated.
    Thanks
    Paul

    Hi Paul
    in your first post you said that exporting without compression was fine, now you say that it also has issues and that exporting on another machine is ok.
    1. Given that you want to go back to tape, export at your sequence settings to maintain quality; actually selecting the same settings as the sequence settings should see no difference in quality. If you are outputting the finished product back to the same tape that the footage originated from there is no need to change codec, you are better to leave it the same.
    2. The fact that the export is seeing problems on one machine and not another suggests that something is wrong on machine one. Trash the prefs for FCP, run some system maintainence on it as well, eg. Disk Utility.
    Tony

  • 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...

  • HD for web compression problem

    I'm trying to compress some HD footage shot on an HVX200 for the web and am having a problem with jagged edges. I'm somewhat new to HD, but this problem resembles interlacing artifacts from my previous DV days. Straight lines aren't straight, they're jagged and the edges around people with white shirts on dark backgrounds have a similar jagged/digital characteristic. Here's how my project is set up.
    Shot on HVX200 at 24pn. Edited in FCP and my sequence settings are 960X720 HD (16:9) frame size. Pixel Aspect Ratio of HD (960X720) and QuickTime Video Settings set to Compressor: DVCPRO HD 720p60 at 100% quality.
    When I save a self-contained quicktime movie like this and view it on my monitor, no jagged edges. It looks exactly as I'd like it to look after its compressed. However, when I pull it into compressor and try to encode it with h.264, it comes out with the jagged edges. I have the following settings in my Compressor summary:
    Format: QT
    Width: 480
    Height: 360
    Pixel Aspect Ratio: Square
    Field Output: Same as source
    Frame Controls On (Retiming: Fast, Resize filter: linear filter, deinterlace filter: best)
    I've tried what feels like all of the various combinations of sequence and compressor settings. Obviously, I've not tried them all. How would I render this out for high quality web display?

    Compressing as mp4 instead, I was able to get this to work tweaking some of the settings in there. Only problem now is an enormous file size that I have to work to get down, but whatever my issue was, seems to have been corrected.

  • 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

  • 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.

  • 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.

  • DVCPRO HD footage problems with Quicktime 10 and MacBook Pro

    I am trying to open DVCPRO HD footage in Quicktime 10 on my computer and just get black screen with no video. Cannot get these files to play yet can get other ones to play, just not the DVCPRO HD footage shot with Panasonic P2 cards. I can play the same files in Quicktime 10 on other computers with Snow Lion and on my tower with Lion. These will just not work on  my MacBook Pro 10.7.5 Everything is up to date. Can anybody trouble shoot this for me? HELP!

    I have the same model as you with the same upgrades (8GB RAM, high-res screen) and began to experience similar problems around the same time as you. And like you, I managed to work around the problem with gfxCardStatus for awhile. It was less than ideal though, since my email client, for example, uses the discrete graphics card. After a week or two, the problem got worse and my computer became virtually unusable. The screen would start to flicker at the log-in prompt, forcing me to reboot again. I could only make it to my desktop 1 time out of 10, if that. The Apple Hardware Test (both regular and extended) revealed no problems. I removed some software that I had installed the day before the problem started on the off chance that was the cause, but still it continued. I also tried to boot with a Linux LiveCD to verify that it was, in fact, a hardware issue and not software related, but never managed.
    Finally, I brought the machine into my local Apple reseller (there are no Apple Stores where I live) for repairs. It was easy enough to demonstrate the issue, and they ended up replacing the motherboard, since that's the only way to replace the discrete graphics card. The turnaround time was about a week. All covered under the standard warranty (I don't have AppleCare). I've had my computer back for a couple of days now, and it's been running smoothly. No problems with the screen, and I feel confident enough to remove gfxCardStatus.
    I hope you've managed to solve your problem by now. Even if your computer passes the Genius Bar hardware diagnostic tool, surely you should be able to demonstrate the issue to the technician and they'll see something is clearly wrong.

  • Video Compression Problems

    Does anyone have any idea of some compression settings I could use for a video on my website? The current file I have on there now takes way too long to load, so I want to compress it somehow, but it also still has to be able to play on an ipod and I also would like to preserve the quality as much as possible. Also it still has to have auto play capabilities. Any suggestions?

    I would say it's a QuickTime problem. Not an iWeb one. You would have the same questions with a webpage of your own.
    Better ask in a QT forum.
    http://discussions.apple.com/category.jspa?categoryID=122

  • Cube Compression problems

    Hi
    We are having problems on our BW system when trying to compress requests.
    At the moment we're compressing a single request at a time, but more often than not end up using secondary logs, and when those are all used up, the job is cancelled, in which case a database rollback happens. During rollback, the system is unavailable for the 2-3 hours, so batch jobs are put on hold.
    This is not ideal.
    Is there a way to cancel a compress job, so that a database rollback doesn't happen?
    Also, should we be reasonably expecting a compress of 13 million records to complete in an acceptable amount of time, or is this unreasonable.
    Basis have already given us the maximum amount of logs, so we can't ask for more. We will also look at breaking the requests up into smaller pieces.
    Regards,
    Andrew

    Hi Andrew,
    We had similar issues in the past with regard to Compression, following activities to mention;
    1. In the past Compression was mainly handled via a process chain on daily basis, this has caused many issues, so we split compression jobs into parallel runs however this did not resolve our issues, Then,
    2.  We executed Compression only on Weekends, in order for this to happen created a condition in process chain, PSA deletions to happen on 2-3 weeks time frame ( best practice )
    3. 10 Million records can be easily compress, but will dump out if its more than that and Basis have to roll back which is time consuming, extending memory is another solution but its system Dependant.
    4. Have to minimize business impact not to schedule compression jobs during working hours as there is a direct impact to reporting process.
    Hope this helps
    WIDYL

  • Cube Compression Problem

    In the middle of a cube compression that was running in the background, the job short dumped.
    I know why the job short dumped.  It was due an invalid SQL statement, presumably because I tried to compress too many requests.
    Problem is that the requests that I asked to be compressed in the cube are marked as "compressed".    How do I "uncheck" those requests that I know are not compressed?

    Wardell,
    Requests get compressed one by one when you compress requests - hence if you are compressing 10 requests then it starts from request 1. If the job ends halfway then the requests that have been compressed till then stay compressed. It does not mean that the request has an incorrect compression status. If the request was getting compressed / scheduled for compression - you will get a clock icon against the request.
    Also to double check - you refresh the screen and go to the collapse tab and see if the release button is not greyed out.
    And go back to RSA1 and refresh tree and then go back to the manage tab and see the status.

Maybe you are looking for