Knowing File Size Prior to Exporting

With the advent of youtube etc which limits file size to 100mb is there a way to calculate the file size prior to export?
Even better is there any way, maybe a plug in that you can aim for a specific file size, say 99.9mb and the codec would meet that target size keeping the VDO at the best quality possible within those parameters???
Thanks,

Sounds like an interesting project for one of the shareware companies.......anyone??

Similar Messages

  • Export to jpeg:  Show jpeg file size prior to export

    Photoshop save to jpeg dialog box shows the jpeg file size associated with each jpeg compression level (1 - 12).  Lightroom export dialog box does not show jpeg file size.  Showing the expected jpeg file size is useful when needing to limit file size while maximizing jpeg quality.  For example, some email applications limit attachment file size; some photo hosting sites (e.g., Zenfolio) limit file size to 12mb.  If I export a cr2 file at 100 quality, it may result in a file size of 14mb.  However, I cannot determine this until after I export.  Then I may try 90 quality and find that the resulting file size is only 8mb.  So, I try 95 quality, and get a 12.5mb file.  This iterative process is a waste of time.  I need to se the file size resulting from each jpeg quality setting in the export dialog box.

    I have tried trashing the plist file. The files look fine through the media manager when copied to the other profile. They look like they are suppose to. The small videos also look fine when played on that computer. Unfortunately our other mac pro computer doesn't have final cut so i can't open and play proress files and my laptop, due to the extreme resolution can't be played on my laptop with final cut studio installed. Tomorrow i'm going to install the proress decoder on the one mac pro to check the files and make sure the self contained is checked but i'm almost positive on that. Other than nuking the profile i don't know what else to do. This is really weird.

  • Question about file size when using "Export for Web"

    Hi!
    I created a .mov file and worked to get a great balance between file size and quality so that I could deliver it via the web and make it easier for end users to see the video on a slower connection.
    My question: When I use "Export for Web," my .mov file is converted into a very large .m4v file--more than double the size of the original file. I know that this export option is to optimize the file for a wide variety of users/internet speeds. Am I correct in guessing that the end size is not an issue? I would post the .mov file instead, but I really like the option of embedding into a html page along with the "click to play" option.
    Bottom line--is it better to post the smaller .mov file that i originally started with or to go ahead and link to the bigger .m4v file that was created with the "Export for Web" option?

    "Export for Web" is a feature of QuickTime Pro and it makes 4 files and the html page code for easy copy/paste Web page editing.
    The very first file is called a "reference movie" and it links to the other 3 files (56kbps, 900kbps and 1.5Mbps). It, and the page code, "read" the connection speed of the viewing hardware and "serve up" the correct file based on that connection speed.
    In nearly all cases the "Desktop" version would still be smaller in file size than the original source. The times the file would "increase" in file size would be when an already compressed was used as the source file. You can find out more about your source file by opening it in QuickTime Player and viewing the Movie Inspector window information.
    There are dozens of other html "tricks" that could be used if your source file is already compressed but you want a different display size:
    Page code to show "aspect" or scale="tofit". This code allows values "outside" of those found in the actual QuickTime file be used for the Web page display. A 320X240 QuickTime .mov file looks pretty good at double size (640X480) but the file size would still be that of the source file.
    "Poster Movie" is another html trick that loads the Web based file directly in the QuickTime Player application (bypassing Web page layout restrictions). These files are also known as "Presentation Movies".
    Another method is the QuickTime Media Link file (.qtl). These are simple text based files that are used as a "direct link". These use simple XML (Extensible Markup Language) and are easily created in any text editing application. The simple syntax has amazing control over a simple QuickTime .mov file. You can launch (and quit) the QuickTime Player, display at other dimensions and even embed "links" inside the display.
    Some of my files as examples:
    http://homepage.mac.com/kkirkster/Lemon_Trees/ a "Poster Movie" style.
    http://homepage.mac.com/kkirkster/.Public/RedneckTexasChristmas.qtl
    A QuickTime Media Link file. A tiny file should download to the viewing machine, launch QuickTime Player, present the movie and it even includes a "link" to my Web page.
    Edit: It appears you must now double click the .qtl download to launch QuickTime.

  • Output file size increases as export occurs?

    Hello,
    I'm currently exporting a lengthy project in Adobe Media Encoder.  The settings are fairly straightforward I think, h.264 codec, 1280x720 @ 23.976 fps (i'm downgrading a bit from the native 1920x1080 files) ultimately leading to a .mov file.
    I've exported many times but never bothered to look at the output file template that is created where I told the compressor to save the export WHILE it is being exported.  So I don't know if when i click on the file and it says zero bytes after a half hour of encoding, if that means something is wrong of it just won't show the file size until export is complete?

    Hi,
    The file size cannot be determined unless the file is exported completely.  So please check the size of the file once encoding completes.
    Regards,
    Vinay

  • Get file size value for export to .txt

    I have created a script to export metadata using the XMP Script Library.  I am able to get all the properties I need except one: image file size (not dimensions, but the size of the file itself in MB).  File size is not included in any XMP namespaces and it isn't in any TIFF tags as far as I can tell.
    Getting the file name is very straightforward: exportFile.write (thumb.name), but I can't find any method to get the file size.
    Any ideas would be a big help.
    Thanks in advance,
    Greg Reser

    var sels = app.document.selections;
    alert(sels[0].spec.length);
    This will get you the file size in bytes, then you can divide to get Mbytes.

  • Lightroom Keeping Original File Size on JPEG Export

    In Photoshop Light room, when I make edits to some JPEG files in a library and leave some unedited, I want to then export the JPEG files, keeping their original file sizes. The default quality setting is 60%, but this reduces the file sizes.
    How do I keep the original file sizes?
    Thx.
    Tony.

    > The default quality setting is 60%, but this reduces the file sizes. How do I keep the original file sizes?
    All of the Export Presets can be edited and the new settings made to be default. Alternatively you can set up your own, new, presets to your own specification.

  • File size in pdf export

    Hi community,
    I have a question about reduction of file size when exporting to interactive pdf.
    I am working with an InDesign (CS6, Win) document with about 70 pages and about 100 links included.
    The links consist of Illustrator files with up to 15 layers, which I am using to show some step-by-step instructions.
    Because of the layered architecture of the included Illustrator files, the exported pdf becomes quite big (>50MB).
    I wonder if InDesign has a way of flattening the figures in the exported pdf, in order to show only visible layers?
    When I browse through the exported pdf, I see deeper layers being rendered, which finally are covered with an opaque layer.
    Of course I could use Illustrator to flatten each figure and link to separate files, showing the final view of the figure.
    Or I could export every view of the figure as png and link to that.
    However, with both these methods I lose the advantage of linking to one file and choosing the visible layers for the figure - thereby making it not easier for maintenance, besides creating a lot of work for saving the separate figures.
    When exporting from InDesign, I already unchecked the "Create Acrobat Layers", however this does not solve my issue.
    I also unsuccessfully tried to reduce the pdf file size using the "Save As Optimized pdf" feature of Adobe Acrobat Pro.
    Any ideas?
    Thanks in advance!
    Chris

    There has been some progress with the topic:
    As Dave Blatner pointed out, adding transparency to a figure and exporting to pdf using the PDF/X-1a preset will remove all hidden information from the Illustrator vector graphic included.
    However, this preset does not support interactivity:
    InDesign produces a warning, stating that all interactivity will be lost and one should use PDF 1.5 or higher to support interactivity.
    Unfortunately, these PDF versions do not support "Transparency Flattener" anymore - putting me back to start.
    But maybe I can form my question a bit more specific now:
    How can I drop all information on an exported pdf page that is not visible (while still having interactivity)?
    Any hints are gratefully acknowledged.
    Chris

  • Errors when using "Limit file size to" when exporting images

    When I try to use the "limit file size to" option in Export, I often get at least one image that doesn't export, and I get a dialogie box like the image attached here:
    As I am exporting in batches, it geats really messy and risky too!I have tried various file size options but that doesn't seem to be a factor.
    Any ideas on solving this, or is it an unfixed Lr bug?!
    thanks in advance

    I can't reproduce it here, so you could try trashing the preferences file http://members.lightroomqueen.com/index.php?/Knowledgebase/Article/View/1148/198/how-do-i- delete-the-lightroom-preferences-file
    If that doesn't do the trick, post it on the Official Feature Request/Bug Report Forum

  • File size issue with exporting PDF

    We write a newsletter for our daughter's gym and are trying to export a Pages '08 document into a PDF small enough for e-mail. When we export with Best settings the file size is 3.2MB, with Better the file is 4.1MB and with Good the file size is 3.8MB. Why would the lowest quality setting (Good) result in a larger file size than Best?

    Welcome to Apple Discussions
    That does seem odd the "good" export would be bigger. One thing that causes Pages documents to be so big is the graphics. If you pre-process the images to close to the actual size you'll use it will reduce the size of your Pages document. I prefer using GraphicConverter but you could use any image editor such as Photoshop Elements.
    Also, if you do any image manipulation in Pages, it will greatly increase the file size because Pages keeps all of the images in the document package.
    You can also try the "Reduce File Size" filter in ColorSync in the Print dialog. Click "Copies & Pages" > ColorSync & then Reduce File Size under Filters, Then click the PDF button in the lower left of the Print dialog. I don't find that the Compress PDF choice in the PDF menu saves much, if any.

  • File size limit on export doesn't.

    I have an export option for a photo forum I post to, where the size limit is 200kb. I have set 200kb, 600x600 JPG as the export limits, and I routinely get files much bigger, memory-wise, than that, up to 260kb.
    I can set the export dimension limit to 500x500, and still get files over 200kb. Today, after a file went to 260kb at 600x600, I set the dimension limit to 500x500, and the exported file size did not change: at 500x500, it was still a 260kb file. If I go through and tweak compression by hand, on every photo, or set a file size limit of 150kb, I can get under 200kb per file.
    I've tried files where I set the limit from 200, to 190, to 180, to 170, and see no change in the exported file (still well over 200 in size), and then when I set it to 160 it jumps down to 150-160 in size. If the file was only 210kb on export with the 200kb limit, setting it to 180kb will generally get the file under 200kb.
    Really, the file size limit does not do what it purports to do. It can clearly get the file below that size if I direct it by hand every time: I haven't specified anything that would artificially bulk the file up, like a quality setting that would be incompatible with the file size limit. It's free to compress the file as needed to meet the limit.
    What I want it to do is meet the limit I set for it. I shouldn't have to dance around. I have this export setting for the express purpose of quickly producing under-200kb files, and I sort of expect Lightroom to manage it.

    I've had this problem too, but it isn't the only one when creating small jpeg files from LR.
    There is something seriously amiss in the export module. I also create a lot of 600 pixel wide/high files and not only are the file sizes far too high, but the quality is poor. I have two workarounds for this, both of which add a little time to the job, but make a big difference.
    First is to export my files as full size jpegs (which I do anyway,) LR does a good job with these. Then get another programme to batch process these to give me the small sRGB files I also need!
    Second is to use LR's web module and create a basic html site for a batch of images in a folder in a temp directory at the precise size I want. This has the advantage that I can add a watermark. Then just rename and move the folder containing the images from the web folder that has been created to where I want them, followed by deleting the rest of the web folder.
    Working at low quality (38%) from the Export module gave me a file size for one image of 455KB. So then I told it to export at a max of 200KB, and it came out at 565KB.  Using the web module with quality set at 70 gave a higher quality result and a file size of 105KB!
    The problem seems to be worse on images where I've done quite a bit of work using local adjustments - rather as if they are actually performing these on the small jpeg and re-saving each time. Certainly something going very wrong - just like it was in LR2.x and I think it must be a logical error as presumably the web module uses the same library to create jpegs.

  • Why do my photo file size increases upon export?!?!

    This is driving me nuts. I have Aperture 1.5.2 referencing an iPhoto library. When I look at the metadata toolset I can see each photo's file size. I have all my photos already resized to fit in an 800x800px box. When I export through Aperture using "export version jpeg original" I get an increased file size. When I export using the master version I don't. I went through and added iptc caption data that only seems to export with the version not the master. I can't believe a line of txt adds so noticeably to the file size. If I need to export my photos with the iptc caption data and want to retain my original file sizes how should I go about it?
    Thanks,
    Michael

    chuck,
    it all depends on 2 factors. a - your original file (pixel dimensions, format, compression level, color and bit depth) and the exported file (pixel dimensions, format, compression level, color and bit depth).
    just as an example - if you take a quite strongly compressed jpg (lets say at 5) and export it to be a less compressed jpg (10 to 12), the file size in kb will be larger, while maintaining the same amount of pixels. what has changed is the way the information are stored within the jpg +(to say it very simplified and without going into details about compression and possible loss of data etc)+.
    if you'd take a high-res 16-bit tif and export it (again at exact same pixel dimensions) as jpg, you'd get a much smaller file, still the same pixels (at least the amount of pixels, however perhaps "lower quality" pixels, depending on compression level, original image, noise, tonality etc etc).
    long (technical) story short: there is no real "one answer fits all" because it heavily depends on your original image. as a rule of thumb however, print files should be in 300 dpi and images for the web in 72.
    in terms of color and bit depth it now depends who you're sending the files to. if you send them to your client, use 8 bit sRGB. if you send it to a graphic designer, i'd send him 16-bit tif files in adobe rgb. all of this makes no sense if your original image was a heavily compressed 8 bit sRGB jpg of course.

  • Difference in file size between EM Export and Export using cmd.....

    Hi ,
    I use the following command in a command prompt to export a schema....
    C:\oracle\product\10.2.0\database10g\BIN\exp.exe system/*****@local FILE=C:\FILES.DMP ROWS=Y OWNER=USER_DB LOG=C:\TEST.LOG
    which produces a file around 900KB.
    When i exported on the same database , the same dataschema , both the data and the db objects ... using the EM the file produced was around 4000KB.....
    Why is this difference.....????
    I noticed in the log file of the exported file using EM some additional info... such as :
    'estimated USER_DB.TABLE_NAME 64KB'
    Can this info justify the difference in file size between the two methods..????
    Note: I use OraDb 10g v.2
    thanks a lot
    Simon

    The export done from EM is from Data Pump export.
    The manual export you did is original export.
    Try do a manual data pump export using expdp and compare the size.

  • Is there a file size limit when exporting PDF to Word using AcrobatXI?

    We have a 500 page document, mostly text, to scan and convert.

    I doubt there is a hard limit, but you may hit problems with particularly big files.
    But I am concerned about the word "scan" here. Are these files not even PDF files yet? If so, no solution for going paper -> Word is likely to be improved by sticking "PDF" in the middle to get paper -> PDF -> Word. Involving PDF in the middle of any conversion process is more likely to be a mistake than not.

  • Premiere Pro CS4: Exporting to High Quality SWF with Low File Size

    Adobe Program: Premeire Pro CS4 (to build slide show video)
    Adobe Program: Adobe Media Encoder (to export project into flash file)
    Project Details: A 20 minute slide show with still images and audio.
    Project Source: HDV 720p, 29.97 fps
    Objective: Export slide show into a flash file so it can be watched online. The file must be small enough for most people to be able to stream the video but good quality (like videos found at Hulu.com).
    Problem: I'm struggling to find an export setting that will let me maintain both good quality and a small file size.
    The export setting that allows the best quality is:
    Format: FLV / F4V
    Preset: F4V - HD 720p
    File Size: 800MB
    Troubleshooting History: I have tried the following Presets:
    F4V - Same as Source
    F4V - 1080p Source, Half Size
    F4V - 720p Source, Half Size
    F4V - 720p Source, Half Size, VBR 2pass
    F4V - Web Large, Widescreen Source
    While the file size is much reduced with these Presets, I lose too much video quality.
    Inquiry: Does anyone have advice for meeting my listed objective?

    I understand that if you want a smaller file you must sacrifice quality and if you want better quality you must expect a larger file size. I am looking for a solution in between the two extremes (again, I draw on the example of Hulu.com). Mainly, I am looking to reduce the file mentioned above from 800MB to about half that.
    Does anyone know a way to manipulate the export settings to make that possible and still maintain as high a picture quality as possible?

  • Exported media file size issues Sometimes one size, Sometimes another without making any changes in FCPX?

    Hi there
    I'm having some strange issues with files sizes from
    Share>Export Media
    I'm not changing anything about the video (just moving an audio track forwards and backwards ever so slightly to try and get it to the correct timing), nor am I changing anything about the way I export the video.
    I am always using the EXACT same settings
    Sometimes finder states my video is 1.15GB, sometimes its states its 3.8GB
    But then when I close Finder down and then go back into Finder again to find the file it states its gone from 1.15GB to 3.8GB
    I'm not sure if this is a error with my system or Final Cut Pro X?
    By the way I'm running 10.0.5
    Thanks

    Bob,
    Well, the issue has gone to press and I have upgraded to Snow Leopard and CS5. Initial tests show that the problem still exists, and that it is  related to the XML tags. The problem occurs both with legacy (CS4) documents and documents created from scratch in CS5. As I mentioned before, it only seems to happen when overrides are applied to paragraph styles.
    Here is a sidebar as exported from InDesign. Overrides were applied to the two headlines to modify color, point size and baseline shift:
    The file with XML tags, packaged and opened in InCopy CS5:
    The same file with XML tags removed, packaged and opened in InCopy:
    OK. Now is when things start to get really interesting.
    I thought perhaps that exporting the InDesign file as an IDML document, then reopening it, might perhaps fix the problem. But, no. In fact, when I reopened the IDML file in InDesign, the font styles were broken in _exactly_ the same places as they were in InCopy. Apparently, whatever problem InCopy is having with the XML tags is being duplicated by the IDML export. (Do these processes share the same file format?)
    For example, here is a title page from the magazine as a screen grab in InDesign. Overrides were applied to the top headline on a line-by-line basis:
    The same file, exported as an IDML file and reopened in InDesign:
    As with InCopy, when the XML tags are removed, the IDML file reopens in InDesign just fine. Unfortunately, removing the XML tags is not a option. We need them to repurpose the content after it goes to press.
    This is a real bug, and for us it's a serious one. I'm surprised it hasn't come up before. Is there any way to draw this to Adobe's attention? I'd be more than happy to share any of these files if that would help.
    Steve

Maybe you are looking for