Compressor output ac3 file too small?

I'm making an ac3 for a short 14 minute film from a large 800 meg 5.1 surround , however when compressor finishes the file is only 50 MB,
Is that ok? Just How do 800 MB become 50MB?
I check the audio and seems fine, but is this right?

Yeah but the 800 MB file is just audio .wav file!!! No video there to take so much space!!
Everything seems fine both channel mappings and length, its just too spooky to see such a huge file turn into a 50 MB clip.

Similar Messages

  • Has anyone solved the problem of 'oop,file too small' when uploading iMovie project to Vimeo.

    Vimeo says ' oops, file too small' when I try to upload an iMovie project. My file is definitely big enough. Any clues, please?

    It's OK, I've cracked it with the help of my son.

  • IPhoto file too small for publication

    I am writing a series of gardening articles for a national publication and was told the size of the photo (from my iPhoto library) I e-mailed is too small. Will changing the size from "large" to "actual" do the trick? Or do I need to send it through Dropbox or another application? Many thanks, Lynn

    Hi Larry,
    Thank you for your reply. I apologize for not adding more details. The photo I originally sent as a "large" file was 414 KB. When I switch to "actual" it is 2.3MB which I am assuming will work for the publication. I am only sending one photo at a time – one for each article. Thank you again. I expect the photo editor will let me know tomorrow if they have what they need. Fingers crossed.
    By the way, in addition to iPhoto I also have Lightroom but have not had a chance to learn the basics of using it. As of now my entire library is in iPhoto and Picasa.
    Thank you again for your time,
    Lynn

  • Backup file too small?

    I did a complete new backup onto a 1Tb TC I had previously used for backup (but deleted the old bakcup file). I have 214 GB on my HD, and TM said it was backing up about 214 GB, but it stopped at about 175 GB and said it was done! No further incremental backups add much of anything. I can't identify any particularly large folders or files that it missed, but I can't compare everything. a 35 GB difference is pretty big. Any thoughts about whether I should worry that the HD is not completely backed up, or how to remedy this?
    I did have previous problems with a "read only" TC, and then "backup file too large..." (the latter which I solved by trashing the TM .plist preferences file right before I did this big backup.)
    Macolyte

    Olaf is right it must be compressed backup:
    To check if the backup file is compressed or not
    RESTORE HEADERONLY FROM DISK = 'Path to backup file';
    Looks for column labelled "Compressed". 1 = compressed, 0 = not compressed.
    If you are skeptical about backup file you can verfiy whether a SQL database backup can be read and restored:
    RESTORE VERIFYONLY FROM DISK = 'Path to backup file'
    If the backup is valid, the SQL Server Database Engine returns:
    The backup set on file 1 is valid

  • Using field-symbols giving dump " the output area is too small.  "

    Hi All,
    Good Afternoon.
    I  am creating a report using field-symbols. The purpose is :
    "This development involves extracting all the fields and the entire data, of any SAP table, and download it as a ‘;’ seperator file."
    For this I wrote following code:
    *& Report  ZTOOL
    REPORT  ztool1.
    Tables***************************************
    DATA : i_tab TYPE TABLE OF dfies WITH HEADER LINE.
    Variables***************************************
    DATA dref TYPE REF TO data.
    FIELD-SYMBOLS <ft> TYPE ANY TABLE." with header line.
    FIELD-SYMBOLS <fs> TYPE ANY .
    DATA: w_heading(5000),
         w_line(5000).
    CONSTANTS  sep TYPE c VALUE ';'.
    Selection Screen*********************************
    SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME.
    PARAMETERS : p_tab LIKE dfies-tabname OBLIGATORY.
    PARAMETERS : p_file(100) TYPE c .
    PARAMETERS : p_lfile(100) TYPE c .
    SELECTION-SCREEN END OF BLOCK b1.
    START-OF-SELECTION.
      CALL FUNCTION 'GET_FIELDTAB'
       EXPORTING
         langu                     = sy-langu
      ONLY                      = ' '
         tabname                   = p_tab
      WITHTEXT                  = 'X'
    IMPORTING
      HEADER                    =
      RC                        =
        TABLES
          fieldtab                  = i_tab
    EXCEPTIONS
       internal_error            = 1
       no_texts_found            = 2
       table_has_no_fields       = 3
       table_not_activ           = 4
       OTHERS                    = 5
      IF sy-subrc <> 0.
        MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
                WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
      ENDIF.
         SELECT * FROM (p_tab) INTO <fs> .       
         endselect.
         CREATE DATA dref TYPE STANDARD TABLE OF (p_tab).
           ENDSELECT.
          assign dref to <fs> casting.
         ASSIGN dref->* TO <ft>.
         SELECT & FROM (p_tab) INTO table <ft>.
         OPEN DATASET p_lfile FOR INPUT IN TEXT MODE ENCODING DEFAULT.
    LOOP AT i_tab.
      IF sy-index = 1.
        w_heading = i_tab-fieldname.
      ELSE.
      CONCATENATE w_heading i_tab-fieldname INTO w_heading SEPARATED BY sep.
      ENDIF.
    ENDLOOP.
    TRANSFER w_heading TO p_lfile.
    LOOP AT <ft> into <ft>.
    clear w_line.
      LOOP AT i_tab.
             ASSIGN COMPONENT i_tab-fieldname OF STRUCTURE <ft> TO <fs>.
             IF sy-index = 1.
                  w_line = <fs> .
             ELSE.
                  CONCATENATE w_line <fs> into w_line SEPARATED BY sep.
             ENDIF.
      ENDLOOP.
      TRANSFER w_line TO p_file.
    ENDLOOP.
    The program is executed well till the statement :
    SELECT * FROM (p_tab) INTO <fs> .       
         endselect.
    But here it gives the following dump : 
    "Error analysis
        In an Open SQL select, the output area used t
        records must be at least as wide as the datab
        records are being read.
        In this particular case, the database table i
        but the output area is only 2 bytes wide."
    Can you please help me solve this problem.
    Thanks in advance.

    Hi Abhii,
    Both are having the same number of fields.
    The only problem is with the data and time (in my scenario). Here, actual length of date is 8 and maximum length is 10. and for time the actual length is 6 and maximum length is 8.
    So, my work area it is taking only the actual length but not the maximum length because of this it is going to dump.
    Can i have any thing which also considers the maximum length of any field at a domain level so that by work area bytes should match according to the db table byte length.
    Thanks
    rohith

  • RAW to Jpeg - file too small

    Hello,
    I have a 10.2 megapixel camera and I'm importing 16MB RAW/NEF files into Lightroom 3. But when I export them as Jpegs (Quality: 100, AdobeRGB1998, NO "limit file size," NO "resize to fit," Resolution: 300) the files shrink to 5MB AT BEST. That is with no cropping in Lightroom. What do I do to export larger Jpegs? I'm concerned about printing an 11x14 print with a 5MB file.
    Thank you!

    First you need to Crop to an 11x14 aspect ratio so that you can decide what to cut out. Your camera's file is likely 2:3 or 3:4 aspect ratio.
    Next you need to let Lightroom resize on export.
    Good settings for JPEG for print at a lab are:
    Long Edge: 14 Inches
    Resolution: 300 PPI
    Quality 84
    sRGB or Adobe (Depending upon your lab)
    Sharpening appropriate to your image content and paper media.
    Megabytes has very little to do with image size printability. It is your pixel dimensions of your file that are the largest determiner.

  • RAW to JPG file conversions too small?

    Hello,
    I recently upgraded to CS3 from CS so I'm now using Bridge/ACR to convert my RAW files to .JPGs. What is puzzling me is, if I open one or more RAW files in Bridge, make some adjustments (usually WB, exposure, etc.), then use the Save Image option within Bridge to save the image(s) as .JPGs, I am getting very small file sizes (I'm using the Max Quality setting in Bridge, which is 10). For example, a RAW file goes from 6.5MB to 1.2MB. However, if I open the RAW file in Photoshop instead of Bridge/ACR, make adjustments, then save as a maximum quality .jpg, the file goes from 6.5MB to 4.5MB. My concern is that when using the batch/save option within Bridge I'm losing quality somewhere?
    Any ideas?
    Thanks,
    FTP

    Hi Omke,
    Thank you for sharing your workflow--very generous and quite interesting.
    Yesterday, I barged into an Adobe Forums thread similar to mine and I discovered the reason for the file size difference, it's the 10 setting you get when you select Maximum Quality from the Bridge Save Image dialogue box. Bridge, like PS, actually goes to a 12 quality setting, but you have to type in the 12 manually (a curious requirement) rather than selecting the Max Quality option, which always goes to 10. Once I manually typed in 12, my Bridge-converted (RAW to .jpg) files became precisely the same size as when I convert them using PS.
    Here's a link to the thread:
    charles badland, "raw to jpeg,jpeg file too small" #36, 30 Sep 2008 1:47 pm
    Thanks again for your help and suggestions,
    --FTP

  • Low audio level in encoded ac3 file

    When I export from FCS 2 using Compressor, audio ac3 file has a low audio level. I was trying change settings in compressor but no result. Therefore I export audio from FCP as quick time movie - AIFF audio file. Then audio level is the same as in FCS. But file is so big. It takes so much space on my DVD when authoring with DVD Studio Pro. I make DVD - PAL. Anybody with the same problem?

    I'm glad you mentioned the preset, Silal. I kept meaning to bring that up, but forgot.
    Set Preprocessing to None. That will keep high level short duration sounds, like drums, etc., from overtaking your dialog, and crushing it.
    The way DIALNORM is intended to work, you set it to the average level of your dialog from your editing app. If you're working in FCP, then that might be something like -12. That setting will cause the player to attenuate the level so dialog is attenuated by 19dB (-31 minus -12 = 19dB of attenuation by the player).
    That, in turn, allows the ridiculously loud music and nat sounds in the film soundtrack to sound "more natural", as they blast your ear drums into bits. "More natural" means "much louder than dialog, just like they are in real life".
    Bah, humbug! Let me hear what the talent is saying. I don't care if I can hear every nuance of that rock ballad, I just want to be able to follow the story, the plot.
    Hey, I'm an old dude, you whippersnappers.
    But back to the point, by setting DIALNORM to -31, the player works out the math like this:
    -31 minus -31 = 0dB of attenuation
    So, your level should be exactly what it was before the compression/conversion. Why it isn't is a mystery, still.

  • OK, I have a .mov and .ac3 file output by Compressor.  How do I make a DVD from these?

    I'd like to use Toast 8 but I don't know where to drag the files...Toast help is no help at all...

    First off, you should have compressor turn your .mov into an mpeg-2 file with an .ac3 file. Once you've done this, you simply select the Video button in Toast (I'm on Toast 10, but I think 8 was the same). Next select your Menu style from Toast and type in your DVD name. Finally drag your mpeg-2 file over into the Toast window. It will then ask you "do you have audio for this file?". Drag the .ac3 file over and have it burn the DVD. If you've done everything correctly it shouldn't re-encode your video, but simply add the menu to your already encoded files.
    As an alternative, you could have Toast do the encoding as well. If you choose this route, you simply drag your original .mov video file over to the Video window. At this point there are some choices you need to make about how Toast will do the encoding. This way takes longer as Toast has to encode both your video and the menu you created.

  • Compressor on Intel Macs create byte reversed AC3 files

    A co-vendor's MUXing application is unable to recognize my .ac3 file created by Compressor. I have a file inspection application from Manzanita Systems that also fails to recognize the .ac3 file.
    I found this on the web:
    - - - - - - - - - - - QUOTE - - - - - - - - - - -
    another user had a problem with an AC3 recently as well. In that case the file was created with a wrong (well, it's not actually wrong but it's unusual for Intel PCs) byte order which makes it impossible for ProEx to handle the file. DVD Studio Pro sees it just fine.
    If you've got a hex viewer you could find out by yourself. The first two bytes of an AC3 must be 0B 77. If they are shown the other way around then the byte order has to be changed.
    - - - - - - - - - - - QUOTE - - - - - - - - - - -
    I looked at my .ac3 file with a hex editor and it starts with 77 0B.
    Then I looked at an .ac3 file that I created with Compressor on a G5 in back in October '06. It began with 0B 77. It was also recognized by Manzanita's MPEG-ID application.
    I can't find anything on Apple's website regarding this issue. No Knowledge Base article; no update; nothing.
    Whiskey Tango Foxtrot?
    Anyone using the latest version of Compressor on an Intel based Mac to create AC3 files having problems sending them out to people who are NOT using DVD Studio Pro to handle the files further?
    THIS NEEDS TO BE FIXED NOW.
    AND...
    see this thread:
    http://discussions.apple.com/thread.jspa?messageID=3394982&#3394982
    MacBook Pro   Mac OS X (10.4)   + stuff
    PBG4   Mac OS X (10.4)  

    I'm afraid you're right.
    I just created a brand new DVDSP test project. The three new files created with Compressor work. The same files that didn't work in the project where they were PPC created AC3 files.
    I was lost in many possibilities, since I had also notice that if I go in DVD SP 4 Preferences, in "Simulator" (I'm french and I don't know its real name in english...) then in "output of player" (same for my french translation) in "Audio" and that I select "numerical output - sp/dif" I have no sound played. If I select "Integrated output" then I can hear back my ac3 created with Intel Compressor.
    On this same computer, with my other project, AC3 PPC created or recently created on my Mac Pro with my old A.Pack software (from DVDStudio pro 2 or 3, I think), are read without difference between these two outputs.
    Finally, Do you suggest me to re-encode all my files ? or should I use A.pack instead of Compressor - maybe Apple Developpers will correct it one day ?
    I'm also upset because, I has a .DTS from a trailer that was accepted and perfectly integrated in my previous DVDSP version, and that I can't use anymore !

  • Problem with ffmpeg: "lame: output buffer too small"

    Seems stream 0 codec frame rate differs from container frame rate: 1000.00 (1000/1) -> 15.00 (15/1)
    Input #0, flv, from 'cEoVBVBCkGI.flv':
    Duration: 00:09:31.06, start: 0.000000, bitrate: 305 kb/s
    Stream #0.0: Video: flv, yuv420p, 320x240, 241 kb/s, 15 tbr, 1k tbn, 1k tbc
    Stream #0.1: Audio: mp3, 22050 Hz, mono, s16, 64 kb/s
    File 'pluxus.mp3' already exists. Overwrite ? [y/N] y
    Output #0, mp3, to 'pluxus.mp3':
    Stream #0.0: Audio: libmp3lame, 22050 Hz, mono, s16, 64 kb/s
    Stream mapping:
    Stream #0.1 -> #0.0
    Press [q] to stop encoding
    [mp3 @ 0x814b270]mdb:255, lastbuf:0 skipping granule 0
    [mp3 @ 0x814b270]mdb:255, lastbuf:196 skipping granule 0
    [libmp3lame @ 0x814c760]lame: output buffer too small (buffer index: 9404, free bytes: 388)
    Audio encoding failed
    [n00b@asrock Music]$
    Any ideas?

    Hi to all!
    I've uploaded lame-3.97-1 package to AUR. You will have to delete gstreamer0.10-ugly-plugins because it needs lame-3.98.2.
    http://aur.archlinux.org/packages.php?ID=366

  • [solved] dvdrip creates too small files

    hi,
    The output .avi files have not the selected bitrate / size.
    The Setteings in dvdrip are:
    Bitrate: 3422
    BPP: 0.581
    Target-Size: 1100MB
    the dvdrip.info file contains the right informations:
    [Video]
    Video format: PAL
    FPS: 25.000
    Size: 640 x 368
    Video bitrate (kbps): 3422
    Video codec: xvid4
    2-pass-encoded: yes
    Fast resizing: no
    Deinterlacer filter:
    Antialiasing filter: no Antialiasing
    but the file is only ~740MB with 2230 kbps.
    Last edited by SiD (2007-04-18 16:50:56)

    Ah, ok.
    Is there any option to keep aspect ratio?
    handbrake --help shows no such Option.
    Keeps handbrake the aspect ratio by default?
    I mean, when I use the --width option will handbrake keep the aspect ratio and calculate the correct height?
    EDIT:
    I found the answer in the HandBrake forums:
    http://handbrake.m0k.org/forum/viewtopi … 369b7ec4f4
    You get it by default in the CLI. Only turns off if you specify both width and height.
    EDIT:
    handbrake stops with ''Segmentation fault''. I opened another thread for it.
    http://bbs.archlinux.org/viewtopic.php?id=32061
    Problem is solved.
    I like HandBrake. It's fast with, IMHO, good quality.
    Thanks for the tip!  
    EDIT:
    No ideas about the dvdrip problem?
    I removed dvdrip and all the configs, reinstalled it, reinstalled transcode and xvidcore; but the target files still doesn't match the selected target size.
    A week ago it has worked.
    So maybe I'll restore my last System Backup (from April, 12) and report the results here.
    EDIT:
    Seems to be related to the settings / config of the used video codec and the input file(s).
    I have 2 movies on the DVD. The first one is encoded with correct target size (1100MB).
    I tried it with dvdrip/transcode and also with HandBrake using xvid and ffmpeg/lavc.
    The second is not encoded with selected target size. Using Handbrake with lavc as encoder, I noticed this message from lavc after the first pass:
    Using all of requested bitrate is not necessary for this video with these parameters
    I found this in the ffmpeg-devel list
    Another thing: I just now changed the phrase:
    "Using all of requested bitrate is not possible"
    ...to...
    "Using all of requested bitrate is not necessary"
    The former implies lavc is deficient in not doing what the user wants,
    which isn't the case.
    With B-frames, the PSNR is about the same, but note that the bitrate is
    much lower. lavc printed a notice about that: "Using all of requested
    bitrate is not necessary for this video with these parameters." The
    reason, here, is that lavc uses higher quantizers to encode B-frames,
    and, hence, a lower bitrate. With this clip, 7000 kbits/sec is so high
    that lavc can't reallocate the saved bitrate by lowering the quantizers
    of enough non B-frames--once all the I- and P-frames have a quantizer of
    2, the minimum allowed, the rest of the bitrate cannot be used.
    So I guess it's not a problem of dvdrip, but depends on the settings of lavc.
    Since the file xvid creates is smaller than target size too, I guess it's a similar thing, but don't know...
    I use the default settings, since I don't know anything about these PSNR, B, I and P frames.
    However, I'll set the topic to solved; cause it's not a problem of dvdrip.
    Last edited by SiD (2007-04-18 16:50:19)

  • I/O Error ioe: Output buffer too small

    I am currently running an FTP process from within the database using a Java stored procedure attempting to send about 199 rows. I am receiving the error message i/o error ioe: Output buffer too small.
    If I reduce the number of rows to below 83, I can successfully complete, however, any number over 83, and the technical problem occurs.
    Is there an Oracle Parameter in the init.ora file that I can modify to increase the amount of data sent... (BTW.. 82 Rows is approximately 8K of data)
    Thanks,
    wn

    I am currently running an FTP process from within the database using a Java stored procedure attempting to send about 199 rows. I am receiving the error message i/o error ioe: Output buffer too small.
    If I reduce the number of rows to below 83, I can successfully complete, however, any number over 83, and the technical problem occurs.
    Is there an Oracle Parameter in the init.ora file that I can modify to increase the amount of data sent... (BTW.. 82 Rows is approximately 8K of data)
    Thanks,
    wn

  • Compressor 3 produces silent ac3 files.

    I'm exporting files from FCP 5.1.4 to Compressor 3.0.3, using their preset for DVD Best Quality 120 minutes. Compressor run without any problems, produces an m2v file and an ac3 file. The problem is the ac3 file, although 171MB and the correct length, is completely silent. I've played it back using QT, VLC, imported it into DVDSP and even burned it to a disc.
    Help!

    Here's where we are now... I've uninstalled Compressor 3, installed Compressor 2. No luck. I installed a.Pack and that didn't seem to work either. Then I re-installed Compressor 3 as well as ffmpegX. (That will convert aiff files to ac3.) Since re-installing Compressor 3, it appears I can successfully convert aiff files to ac3 now using both ffmpegX and Compressor 3. They don't play back in anything other than DSP, but since that's where I need them, I'm not too concerned. So the problem is half solved but it still involves an extra step of exporting and aiff file from FCS and then converting it to an ac3 file in Compressor or ffmpegX. I still end up with a silent file however when I export directly from FCP to Compressor. (Even when I try to play it in DSP.)
    Of course now Batch Monitor is messed up and doesn't display anything while I'm converting from aiff to ac3. Any suggestions there?
    Thanks to all of you who've offered help!

  • Compressor presets making m2v file too big

    I am on fresh install of tiger fcp suite, all up to date. I use DVD best quality 120 min preset and it spits out a 5 gig m2v. I try to set my own custom setting with exact bitrate to maximize quality and use up disc space, never exceeding safe levels. and it creates file smuch bigger than compressor 1.2.1 did with same settings.

    I've just completed my third attempt to encode a 1h57min video using the following settings, based on the DVD Best Quality 4:3 factory presets.
    - Avg Bit Rate: 4.6 | Max Bitrate 7.5
    Result: M2V file too large (> 5gb!)
    - Avg Bit Rate 4.6 | Max Bitrate 7.0
    Result: M2V slightly smaller, but still too large (> 4.8gb!)
    - Avg Bit Rate 4.0 | Max Bitrate 7.0
    Result: M2V file still too large, at 4.72gb!
    *Again, these file sizes are the M2V files BY THEMSELVES!*
    BTW, I used a trusted bitrate calculator to get the 4.6 avg bitrate reading for a 120min video. I've also used that bitrate without issue in Compressor 1.
    The source is an 8-bit Uncompressed video timeline from FCP 5.0.2. There are no cuts in the timeline, as it was digitized directly from the source and placed on the timeline to be encoded with chapter markers in place. The only image transformation within Compressor set to occur is the cropping of the bottom 2 video fields to comform the 486 lines to 480.
    This has wasted THREE days of my time. And in all cases, the estimated file sizes reported by Compressor 2 has been grossly inaccurate.
    How am I supposed to work around this without churning out video that looks like utter crud???
    I've already had to drop my Avg and Max Bitrates from 5.0mbps to 4.0mpbs, even though Apple's preset for 120 minutes Best Quality lists 5.0mpbs with a max bitrate 7.5mbps. If the Apple presets aren't even working at this, clearly there is something wrong here.

Maybe you are looking for