Applet for figuring bitrate based on target file size?

Occasionally when I'm exporting quicktimes for emailing to people with known restrictions on incoming file sizes, I'd love to be able to specify the target file size as opposed to the bitrate.
Does anyone know of any applets that can generate a rough estimate of what you should set the bitrate to in order to achieve a target file size given the length of the clip?
Sounds like a widget in the making to me...

And a widget:
http://www.apple.com/downloads/dashboard/calculate_convert/videospace.html

Similar Messages

Target file size and Bitrates help

I am trying to make my 2minute 40 second video become a file size of no larger than 100MB. Right now it's 470MB and that was after I converted it with MPEG Streamclip to a smaller version that I could upload. Is there an easy way to calculate the maximum bitrate to make your existing video the right size? I noticed some bitrate calculators but none of them are for web video's and I don't see any that have a target file size. Short of taking an encoding class for this project I could use some suggestions.

Export from fcp with current settings and bring that into compressor. Use one of the apple: otherworkflows: web: quicktime 7 compatible.. When you apply them they'll give you an estimate (just an estimate) of the file size in the summary window. It's a good place to start. If you're going to be resizing, I'd strongly recommend that you turn on frame controls in the frame controls panel and set the resizing filter to best.
Once you've found your ideal settings, you can save this customized preset and apply it to other files.

"target" file size for streaming?

Newbie question #2 (Many thanks in advance!)
I understand that the answer is relative to the uncompressed file size, but I'm trying to figure out a target file size (how small) for a 250 Mb file (a 30-second movie) to stream on the web. Should I be aiming for 25 Mb? 100 Mb? 8 Mb? Just looking for a ballpark, if that's possible.
If this question misses a critical point, feel free to let me know!
Thanks, e

If your going to use h.264 try 400 or 600 kbits/sec for the video (2passes, B-Frames). To tests, copy about 30 seconds of the video into a new Quicktime. If it look good to you then compress the original video. You can go as low as 300 kbit/sec. It all depends on the content of the video as to what bit rate you should use.
As for the audio use AAC at no higher than 128 kbps. You can go lower and use mono. There again it depends on what the audio is.
I just compressed a 320x240 at:
300...1MB
400...1.3MB
600...2.1MB

Target File Size Too Large?

Hello,
We have an interface, that takes a Source File-> Transforms it in the Staging Area ->and outputs a Target File.
The problem is the target file is way too large than what it is supposed to be.
We do have the 'Truncate Option' turned ON, so its not duplicate records..
We think its the Physical and Logical Lengths that are defined for the Target files.
We think the logical length is way too large causing substantial 'spaces' between the data columns thereby increasing the file size.
We initially had the Logical Length for the data columns as 12 and we got the following error:
Arithmetic Overflow error converting numeric to data type numeric.
When we increased the Logical Length from 12 to 20 the interface executed fine without errors. But now the target file size is just way too large 1:5
Any suggestions to prevent these additional spaces in the target columns??
Appreciate your inputs!
Thanks

Since 'File-system' does not have a property 'column length', ODI will automatically set a standard 'column length' according to the datatype of the column. In your case, as both your source and target is File, check the max length of each column in your source ( Ex: if your file is huge then open the file in excel and verify the lengths) and set the same 'Logical length' for your target file datastore.
drop the temporary tables (set the 'delete temp objects' option to 'true' in the KMs) and re-run the Interface. hope this helps.
Thanks,
Parasuram.

Processing Multiple Files for more than 100 Receive Location - File Size - 25 MB each file, file type DML

Hi Everybody
Please suggest.
For one of our BizTalk interface, we have around 120 receive locations. We are just moving (*.dml) files from the source to destination without doing any processing.
We receive lots of files in different receive locations and in few cases the file size will be around 25 MB and so while moving these large files, the CPU usage is varying between 10% to 90+% and the time consuming for this single huge file is around
10 to 20 minutes. This solution was already in place and was designed by the previous vendor for moving the files to their clients. Each client has 2 receive locations and they have around 60 clients. Is there any best solution for implementing
this with in BizTalk or outside BizTalk? Please suggest.
I am also looking for how to control the number of files which gets picked from the BizTalk receive location. For example, If we have say 1000 files in receive location and we want to pick at a time only 50 files only (batch of 50) then is it possible?
because currently it is picking all the files available in source location, and one of the process is dropping thousands of files in to the source location, so we want to control the number of files getting picked (or even if we can control to pick the
number of KBs). Please guide us on how we can control the number of files.

Hi Rajeev,
25 MB per file, 1000 files. Certainly you got to revisit the reason for choosing BizTalk.
“the time consuming for this single huge file is around 10 to 20 minutes”
- This is a problem.
You could consider other file transfer options like XCopy or RobotCopy etc if you want to transfer to another local/shared drive. Or you can consider using SSIS
which does comes with many adapters to send to destination system depending on their destination transfer protocol.
But in your case, you have some of the advantages that you get with BizTalk. For your scenario, you have more source systems (more Receive locations), with BizTalk
it’s always easier to manage these configurations, you can easily enable and disable them when a need arise. You can easily configure tracking; configure host instances based on load etc. So you can consider following design for your requirement. This design
would suit you well since you’re not processing the message and just pass it through from source to destination:
Use a custom pipeline component in the Receive Locations which receives the large file.
Stores the received file into disk and creates a small XML metadata message that contains the information about where the large file is stored.
The small XML message is then published into the
message box db
instead of the large file. Let the metadata file also contain the same context properties as the received file.
In the send port, use another custom pipeline component that process the metadata xml file, retrieve the location of the disk where the file is stored, access the file and send it to destination.
Read the following article on this design..
http://www.codeproject.com/Articles/180333/Transfer-Large-Files-using-BizTalk-Send-Side
This way you don’t need to publish the whole message into message box DB which would considerably reduce the processing time and utilises host instance to process
more files. This way you can still get the advantages of BizTalk and still process large files.
And regarding your question of restricting the Receive location to handles the number of files from receives location. No it’s not possible.
Regards,
M.R.Ashwin Prabhu
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Is there a way to export at a target file size?

I need to export at <10Mb. For now I've been exporting at descending quality levels until I get each picture to come in just under 10Mb, but this is very time consuming.
Is there any way to do this straight out of Aperture? I see LR5 now has an option for target megapixel size, but I don't have LR.

Not that I know of. It's trial➞retry until you get what you want, and it will change for each Image even if the Image's are from the same camera. But "<10 MB" should be a pretty easy target to hit.
In general, with JPG compression, lowering the resolution loses the smallest details, lowering the quality loses the slightest tonal changes. If your images have a lot of detail, lower the quality before you lower the resolution. If your images have broad areas of nearly-matched tones, lower the resolution before you lower the quality. Whatever you do, you should inspect every exported file before using it further.
Screenshot showing some of the results of my trying to get exported files to not exceed required storage specifications:
Would have liked to have the functionality you're seeking added to a future version of Aperture. Maybe we'll get it in PhotOSX.
—Kirby.

Compressing project to target file size (10MB)

I have a short (around 1 min) project. I want to export it as an MPEG-4 that is under 10MB. I've tried two options in Compressor: 40kbps and 800kbps. These resulted in a 900kb file and a 13MB file, respectively. Obviously, the first one had very low quality. How can I tell Final Cut (or Compressor) to give me the best quality video file under 10MB?
If these programs aren't capable of that, can anyone recommend an alternative solution?

How can I tell Final Cut (or Compressor) to give me the best quality video file under 10MB?
Compressor - or any other software compression suite on the market, for that matter - is not 'intelligent enough' to crunch your file to fit a specific file limit. You've gotta go further along the path you've cleared - via trial and error - to get things just right.
Have you tried dialing down the bitrate on the 800kbps preset? Just to stave off any confusion, I mean:
Import your file
Select the 800Kbps MPEG-4 preset
Drop the video bitrate by, say, 100 in the Inspector window
Submit and see what you get (in terms of quality and file size)

JSX Save PNG for web, quality parameter not changing file size

Hi
I have a script that uses this snippet of code to save png files for web. But, no matter what number I change the quality, the resulting file size and image fidelity remains the same.
I was wondering if I can save pngs for web at smaller byte size with JSX and how to modify the output settings.
docName = sourceDoc.name;
NamesaveRef = new File( outputFolder + "/" + docName );
var NewfileRef = new File( NamesaveRef )
var options = new ExportOptionsSaveForWeb();
options.format = SaveDocumentType.PNG;
options.transparency = true;
options.blur = 0.0 ;
options.includeProfile = false ;
options.interlaced = false ;
options.optimized = true ;
options.quality = 3 ;//THIS NUMBER DOES NOT CHANGE QUALITY IF CHANGED FROM 0.1 TO 100
options.PNG8 = false ;
sourceDoc.exportDocument(File( NamesaveRef), ExportType.SAVEFORWEB, options);
app.activeDocument.close(SaveOptions.DONOTSAVECHANGES);
Thanks for your help.
Aubrey

PNG does not have a quality setting. The quality property is used when exporting jpeg. That is why changing that property has no effect with PNG files.
Photoshop now supports PNG compression but as far as I can tell you have to use Action Manager to save. I don't see a compression option when using saveForWeb.

How can I use variable for a package filename and target file inODIFileMove

I want to use a variable for paths so that when I migrate from Dev to QA to Prod I don't have to do a lot of editing.
Specifically, I want a variable to be the first part of the path for the filename (\\sundev1\fnd1-hypd1) and join this with the rest (\update\log\*.log or specific filename) using several different objects like the ODIFileMove, ODI OS Command, OS Command, etc.
Thank you!

Hi,
you could set up a database table holding processing parameters (i.e. Column1 - ParamName, Column2 - ParamValue).
One row could then be ParamName = FilePath, ParamValue = \\<server>\folder\
So, the refreshing query (attached to a logical schema) would be something like SELECT ParamValue FROM <your table> WHERE ParamName ='FilePath'
Then, create a variable which can refresh from the database and in the package, drop the variable onto the flow and set it's type to 'Refresh Variable' in the properties.
Hope this helps.
geeo

Best way to create a background image for all resolutions without drastically increasing file size.

I see a lot of great background images with complex designs that resize with different screen resolutions. I can create the designs, but I don't know how to create a complex image for large screen resolutions without making it a large file, or it loosing quality with it stretches to the larger size. Is there a code that resizes images when stretched, or do I just have to live with a slower load speed with complex background images?

The background doesn't resize, it shrinks:
http://johnpatrickgiven.com/jquery/background-resize/
Basically make a 1920x1080 or higher resolution file and use that script. There will always be a maximum but based on your response that is not your monitor. Photoshop and other tools do a pretty good job compressing jpeg files and most internet connections are fast enough to make it seamless.

Target file size changes

Hi experts,
In my scenario the file that gets created in the target dir has shown the following pattern.
Expected size: 250MB
first the file got created with 4MB size then it went to 0MB n then raised again to 4MB n then again went to 2MB and after few more changes like this, the final size created was 120MB.
This has happened 2-3 times in the past few weeks and it can not be replicated in the QA/DEV as its very random but a big pain when it happens.
Plz tell me, what could have caused it?
what are all the possibilites that need to be considered?
THANKS n REGARDS
VJ

first the file got created with 4MB size then it went to 0MB n then raised again to 4MB n then again went to
2MB and after few more changes like this, the final size created was 120MB.
Insufficient disk space can be one of the reasons.....was any other program using the space when the above file was being written?
Regards,
Abhishek.

Card reader for sd dose it have a file size limit in hd

it will not download hd files into adobe elements

If you really expect an answer ( I noted 51 previous reads), you need to work on your translation.
1) Computer model and OS.
2) SD card size (GB), and type (ie SD, SDHC). All at FAT formatted. Unless you re-formatted NTFS.
3) Size of the file your attempting to transfer? FAT32 does not support files over 4GB.
I am a volunteer. I am not an HP employee.
To say THANK YOU, press the "thumbs up symbol" to render a KUDO. Please click Accept as Solution, if your problem is solved. You can render both Solution and KUDO.
The Law of Effect states that positive reinforcement increases the probability of a behavior being repeated. (B.F.Skinner). You toss me KUDO and/or Solution, and I perform better.
(2) HP DV7t i7 3160QM 2.3Ghz 8GB
HP m9200t E8400,Win7 Pro 32 bit. 4GB RAM, ASUS 550Ti 2GB, Rosewill 630W. 1T HD SATA 3Gb/s
Custom Asus P8P67, I7-2600k, 16GB RAM, WIN7 Pro 64bit, EVGA GTX660 2GB, 750W OCZ, 1T HD SATA 6Gb/s
Custom Asus P8Z77, I7-3770k, 16GB RAM, WIN7 Pro 64bit, EVGA GTX670 2GB, 750W OCZ, 1T HD SATA 6Gb/s
Both Customs use Rosewill Blackhawk case.
Printer -- HP OfficeJet Pro 8600 Plus

Export file size for youtube

Hi
After reading some of the comments regardind new users I am a little hesitant to pose my question . This is my first post.
Nothing ventured, nothing gained, so here goes.
I have a Panasonic X900 video camera which produces excellent shots at full HD1080i .(PAL AVCHD))
The file coming from the camera is a .M2TS which I gather is a mpeg variation. A typical shot of 3 minutes is over 300meg.
I usually create a sequence from the clip and then edit the clip.
So far so good when I am exporting for use on a DVD.
I have been asked to video someone doing a dance sequence and to place this on YouTube.
(Original file size 300meg)Trying numerous settings, the smallest I can get my output file is using H.264 with a YouTube SD 360 wide screen Preset and this gives me 28meg.
I see numerous .MP4 videos on YouTube of 10 minutes or so and they are still only around 50meg and have reasonable full screen quality.
I have tried importing one of those and creating a sequence from it but they are normally NTSC and 29fps .
On the above basis, if I filmed a 9 minute clip and exported it as H.264 etc it would still be approx 70meg.
I have tried reducing the target bitrate and it certainlyreduces file size but poor quality.
If this is the best that can be achieved, then so be it.
Any suggestions on how to get a reasonable quality result while keeping the file size reasonable would be appreciated.
Regards
Brian

After reading some of the comments regardind new users I am a little hesitant to pose my question . This is my first post.
We wont bite.
Well constructed full questions with detail and hardware / software info will usually get a good response. Screen and frame grabs are helpful.
"Attitude" can sometimes get a bit of a kicking.
Welcome to Forum.

Show file size in Cell Extras? (Either Compact or Expanded, or anywhere in Grid for multiple images simultaneously)

I've searched and seen several suggestions saying to change Metadata to Exif & IPTC to see the file size, but that's for only one image at a time. Under Cell Extras (both Compact and Expanded) I see options for Megapixeps, Cropped Dimensions, File Name, Extention, and a bunch of other options, but no file size. I suspect this is because file size isn't a metadata field and simply a file attribute (that may be incorrect, but regardless...) is there really no way to have file size visible in the thumbnail cells in Grid view in the Library? I'm trying to reduce redundancy and viewing file size of multiple images at a glance based on my Library Filter criteria would be a huge help. Thanks to anyone who can help sort me out!

Sure. I have a catalog with 22,000 images indiscriminately imported from hundreds of folders and multiple drives from this year alone (partially lost a RAID array to a corrupt index and recovered a dump of the files so I'm terribly disorganized juggling emergency redundancy backups wherever I had 50 gigs here, 100 gigs there, and working to clean up and organize my photos one year at a time ), including raw, jpg, websized jpg, png, tiff and psd (flattened and with layers/adjustments) and am now trying to identify my keepers and delete unnecessary files. I have 22 terabytes of personal files and photography spread chaotically and while I now have proper discipline when saving variants, I didn't always and want to remove unneeded, rejected, and duplicate images. I don't expect to be caught up for months or longer depending on my free time and sanity. Unfortunately, it's not as simple as keep the raw delete the rest. Sometimes I have multiple PSD documents with different version names and edits, sometimes with multiple layers, and I have to use a variety of information to identify which one is indeed the correct one to keep...or open them all/both.
Often, file size can be an indicator for me and aids in making the decision more quickly. For instance between 2 psd files with the same Megapixles I'm often able to identify the flattened version vs the layers intact version by file size if it wasn't properly noted in the filename, which unfortunately due to a combination of bad or evolving practices and being tired or rushed happens more often than I'd like to admit. One I just came across that brought me here searching was 3 similarly named and appearing PSD files of a panorama, all with the same MP/dimensions. One was flattened, one was the original stitch, and one was flattened with a few masks, adjustments, and an extra layer, and being the one I'd want to keep. Filesize helped me quickly identify which was which. Also sometimes dimensions are misleading, like when a panorama is first created and uncropped, its dimensions are larger, but a tighter cropped image with multiple layers and a larger file size indicates to me that it is newer and more finished, even though smaller dimensions typically indicates a crop and may not be a 'master' copy. Additionally, 2 images with different names but the exact same file size are very likely duplicates (at least in my workflow) but 2 similarly looking images with the same dimensions could be retouched/not, sharpened/not, have noise reduction/not, and I'd have to view them in detail to determine if they were in fact identical. For my purposes (since these are my personal fine art images & I have the raw files incase I occasionally mess up) I'm often willing to trade an educated guess for my time. Seeing identical file sizes on 2 apparently similar images is good enough for me to delete one.
I can select them individually and check...it's not a horrific problem. But it would save me time so I was hoping I had simply missed how to view that. My reasoning is 'why not' have the option available with all the others? Me personally, I don't care about megapixels when I already have the dimensions, that's just redundant and honestly much less helpful than LxW. File size would be an additional tool I would use, though. There are other examples but the main thing is that I do spend time checking filesize, and specifically when comparing multiple images, so having it displayed in the cell would be a time saver for me.

What is the recommended maximum file size for a VI ?

1.) I am involved in documenting a project that includes LabView developed controls for a built from scratch test instrument. The LabView I am wading through involves multiple VIs, many of which are large files that are difficult to decipher. I would like the programmer to consider reducing the VI file sizes by breaking the large VIs up into sets of smaller VIs. What would be a target file size to shoot for?
2.) Is it possible to avoid the use of global variables in LabView projects made up of multiple sub-VIs?
Lost in Code

Probably better guidelines that dictates 'size' of a vi are:
typically no more than 1 video screen in size
is it legible
and is it's function and operation clear.
I have seen examples of '1 vi does it all' that were many screens wide and tall, totally a flustercuck, and nearly 1 MB in size.
Globals and local variables (except for LV2 style) are typcially shunned for they can create a host of problems (race conditions, indeterminant data).
Use connector pane to wire controls and indicators to. Then use wires between vi's to transfer data. I tend to use clusters to hold shared data.
~~~~~~~~~~~~~~~~~~~~~~~~~~
"It’s the questions that drive us.”
~~~~~~~~~~~~~~~~~~~~~~~~~~

Applet for figuring bitrate based on target file size?

Similar Messages

Maybe you are looking for