Issues when Exporting to H.264

Hey guys, just ran into an issue for the first time with CS6. I'm trying to export to h264 and I get a file size estimate that reads 324mb, but the output turns out as GB's of data. Included is a screencap for reference. Input codec was DVCPRO HD. Thanks much in advance.

I too have been plagued by this H264 problem for the past 2 years it seems.
I have a suspicion that if we polled the users experiencing this effect that
it would result they all use custom or modified Display Profiles in the Display System Preferences.
My temporary (and somewhat silly workaround) has been to change my display profile to the
standard "Cinema HD Display" instead of my user-created "Cinema HD Display Calibrated" profile.
It does alter the gamma of my display to a unpleasing value, but after changing it, the H264 export
works beautifully. No gamma shift at all.
I have read all the suggestions on trying the quicktime "filter then colorsync" export and always got unsatisfactory results. My silly workaround always produces the best results. I just have to change the dang setting back after I export so my eye dont burn out of my skull.

Similar Messages

Audio sync issue when exporting to h.264

I've seen this issue reported many times, but can't find an answer, or whether it's simply another bug in Premiere CS5. The same issue happens on more than one computer (PC with Intel i7, 64 bit, GeForce GTX 470, and BlackMagic video card), the video is HDV using Sony Compact flash. Audio sync is fine throughout editing and exporting to standard DVD or h.264 blu-ray using Encore Dynamic link. But when I export directly from premiere to create a flash video or h.264 720p video, the audio moves ahead of the video by about 4 frames. This didn't happen with CS4. There is a similar issue if I export using MPEG2, though the audio error seems less consistent. Have wasted very many hours, and a fix or solution would be welcome! Many thanks.

Having the same issue here. Some kind of solution would make me so happy right now.
I've shot and edited a series of short interviews on a DSLR. So I've started with H.264 files and I'm attempting to export the final product to h.264 and the audio is very noticeably out of sync.
The only workaround I've come up with so far is as follows:
1. Export the audio only from the original sequence
2. Export the video only from the original sequence
3, Start a new sequence and drop in the files I just created.
When I export that sequence, for some reason, it syncs perfectly. Needless to say however, this is a huge inconvenience and time waster, especially when it comes to making further edits.

Hi there! So I am using Lightroom 3 on a pc and I have ran into an issue when exporting images. The DPI and image size (in inches) that I am selecting during the export process. For example I just exported a collection and set the dpi to 180 and the size

Hi there! So I am using Lightroom 3 on a pc and I have ran into an issue when exporting images. The DPI and image size (in inches) that I am selecting during the export process. For example I just exported a collection and set the dpi to 180 and the size to 7 inches on the long edge. My exported result is 457 dpi and sized at 3200x2134 pixels.. Any ideas on why this is happening and what I can do to correct it?

The DPI setting in a digital image has no meaning at all. You need to learn how to calculate what you need in your exported image. The only measurement in a digital image that has any meaning is the number of pixels in each direction. It doesn't matter what you set that DPI to (actually it's PPI or pixels per inch). The image will have the same number of pixels regardless of the setting. If you need an image that is 5 x 7" (for example) at 200 PPI then you would want an image that measured:
5 x 200 = 1000 pixels
7 x 200 = 1400 pixels
So you would need an image that is 1000 x 1400 pixels to have a 5 x 7" image at 200 PPI. The reason your exported image had such a high PPI setting is because you specified the number of inches you wanted the image to be. And there were enough pixels in the image that it calculated out to be that high PPI setting.
I apologize, I don't explain this very well. But you need to learn to do the math to determine how large you really want your exported images to be.

How do I get rid of memory issue when exporting in imovie

How do I get rid of memory issue when exporting in imovie?

Delete the content that is filling it up. Text messages, iMessages, SMS, emails, Safari Cache; essentially all data for all of the built in apps.

Alignement issue when exporting to PDF

Hello,
I'm having some alignment issues when exporting an InDesign file to PDF.
I have a couple of square pictures, touching eachother at the edges. These are aligned bang on in InDesign (the lines overlap), but when exporting to a PDF and viewing in there, it seems that some seem to jump up slightly.
Is this just a display issue or a setting issue when exporting to PDF?
Thanks
Benny

The detail is cropped too tight for me to tell how many photos are intersecting there. Is there a vertical intersection as well? If not, I think you're looking at a very slightly non-rectangular frame, if there is, then you might still be looking at a non-rectangular frame, or the frames are not perfectly aligned, which doesn't surprise me if you snapped to a guide -- I find that less than 100% reliable since CS6.
Presuming that you've zoomed in to show us the problem, that's probably a single pixel misalignment and you'd be very hard pressed to see it in printed output without a loupe.
You can check the bottom edge of the top photo, and the top edge of the bottom photo(s) for being out of horizontal by using the direct select tool to select the corner points and seeing if the y-coordinate is the same on both sides of the frame.
My printer tell me to always overlap frames, rather than butting them, for trapping, for what that's worth, but I don't always do what he says, and I've never had a problem.

OBIEE 11g - issue when export hierarchy to a csv

Hello,
I have an issue when I try to export to a csv file a report containing a Logical Dimension field, when I export just the first level of hierarchy is exported and not all the records. When I export to another format (such as excel) all the records are exported correctly. Do you know what can I do in order to have all the records exported to a csv?
Thanks!
Solange.

This is a bug see below.
Bug 13083479 : EXPORT DATA TO CSV FORMAT DOES NOT DOWNLOAD EXPANDED HIERARCHICAL COLUMNS
Proposed workaround : OBIEE 11.1.1.5: Pivot Table Report Export To Csv Does Not Include Hierarchical Data [ID 1382184.1]
Mark if answered.!
Thanks,
SVS

SSRS 2012 Conditional Formatting Color Issues When Exporting to Excel

Hi all,
We recently upgraded to SQL 2012 from SQL2008 R2. I'm having a strange issue with SSRS2012.
One of the report has conditional formattings on cell background colors. Everything works fine when render the report in browser or preview mode. However, the conditional formatting stop working when export the report to Excel (no issues if
export to pdf). All cells are high-lightened with pre-defined color although it should only high-lighten those cells that fulfil the condition.
Has someone encountered this issue before ? Thanks for any help.

Hi ZZ02,
I have test the scenario in my testing environment, however, everything goes well when exporting to Excel format. The issue might be related to the expression for the conditional background color. To make further analysis, please post the expression as well
as the report design structure.
Additionally, in SQL Server 2012 Reporting Services, the Excel rendering extension renders a report to the native format of Microsoft Excel 2007-2010, the format of which is ExcelOpenXML. By default, the previous version of the Excel rendering extension,
compatible with Microsoft Excel 2003, is disabled. At this time, I suggest that you enable the Excel 2003 rendering extension by modifying the RSReportServer.config file. After that, the Excel 2003 rendering format will be available on report manager (not
available in Report Designer). So, please export the report from report manager and check the result again.
For more information about enable the Excel 2003 rendering extension, please see:
http://social.msdn.microsoft.com/Forums/en/sqlreportingservices/thread/0713de27-dcc0-4e51-81ac-5272647d171f
Regards,
Mike Yin
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Mike Yin
TechNet Community Support

OBIEE 11g - issue when export to a csv file

Hello,
I have an issue when I try to export to a csv file a report having numeric feild, when I export and open the file in notepad the trailing zeros to the right of decimal points do not show up. When export to another formats (such as excel, pdf) the trailing zeros appears correctly. e..g, 100.00 appears as 100, 100.50 appears as 100.5.
Do you know what can be done in order to have trailing zeros to the right of decimal points to appear in a csv?
Thanks

This is a bug see below.
Bug 13083479 : EXPORT DATA TO CSV FORMAT DOES NOT DOWNLOAD EXPANDED HIERARCHICAL COLUMNS
Proposed workaround : OBIEE 11.1.1.5: Pivot Table Report Export To Csv Does Not Include Hierarchical Data [ID 1382184.1]
Mark if answered.!
Thanks,
SVS

Premiere pro CS6.0.3 keeps crashing when exporting to H.264

Good day everyone,
I am trying to export my timeline using some of the H.264 setting and it keeps crashing on me. Not all of the H.264 like the Apple and Android settings. Those work fine. But trying to export to H.264 Youtube (any presets), H.264 HD 1080I 29.97 and HD 1080P 29.97 it will process to around 80%-95% than crash. It gives me an error message than gives me three files that can help with finding the problem.
I have tried to export using Premiere and also AME. They both crash at the same point.
I have tried creating new projects, new sequences and such. No luck.
Currently I am using Premiere Pro CS6.03, Adobe Media Encoder CS 6.03 as well. Windows 7 64bit, Intel Core [email protected] with 8GB ram. My video card is a NVIDIA GeForce GTX 670. Any advice would be most helpful and appreciated.
Thanks

I solved what might be a similar problem last evening by lowering the speed of my i7-3055K (nominal 3.9GHz) to 4.2GHz from 4.5GHz.
My symptoms were similar: new PC build (10 days old); crashing or blue screens about 1 minute into a 3 minute Premiere export or AME render, Win7 Pro. The system had previously been very stable. At first I suspected an H264 codec problem or an iTunes/Quicktime incompatibility but when an AVI render using the NTSC DV Widescreen preset crashed it broadened my search for solutions. Mercury GPU render on/off did not fix the crash problem.
The render last evening was probably the first time that my new CPU was seriously stressed. Lowering the CPU speed was the quick solution. Overclocking sites/forums probably have tips on stress tests, memory tests, voltage tweaking, etc but as long as the system is stable I'll probably be satisified with the slower CPU solution.
The CPU cooling is the Intel stock fan. 32GB of Corsair memory is running at its rated PC1600. CPU and memory voltages are the defaults, i.e., no tweaking. Intel DZ77RE-75K motherboard. EVGA GTX680 FTW+ 4GB at its defaults, i.e., no overclocking/tweaking. 1000 watt power supply , which is probably overkill but it's what I had lying around (I have an almost identical setup (GTX460 rather than GTX680) which runs fine at 4.2GHz with a 700-watt PSU -- but I've never stressed that 2nd PC with an Premiere/AE/AME render).

Stops rendering to media until I restart the program - when exporting to H.264

When exporting to media, sequences in Premiere Pro CS6 sometime just stop rendering to media (with no error warning)...until I restart the program. Other times the same sequence will report an "error" for "unknown" causes. This generally happens on a 2 pass variable export rendering to H.264.... but almost never on a CBR renderings. It is almost always solved with restarting Premiere.
I'm not sure if this is related, but I just built a new system with a terabyte solid state drive and reinstalled CS6 when it seems that these errors began. The preview renderings are being saved to a partition on this drive, but the export renderings go to a different normal spinning Sata drive.
Any suggestions?

Others have reported the same thing, and I saw it happen once but can't tell what combination of factors is causing the encoder library to fault. Queuing the sequence into AME doesn't seem to help, nor does rendering with previews.
The 'workaround' is to export from Premiere in another, high-quality format (e.g. Cineform AVI) then use Media Encoder to convert to H.264. I can't make it crash in standalone mode, even with VBR2.

No audio when exporting to h.264 (mp3 - aac conversion fails)

Using QuickTime Player Pro 7.5.5 on OS X 10.5.6:
I have a video file (video format: On2 VP6, audio format: MPEG Layer 3 mono) that I am attempting to export for high-quality YouTube.
When I export to H.264 my only audio export option is AAC-LC. But the resulting mp4 file has a silent audio track. I've tried different settings on the audio (mono/stereo, different data rates) but that makes no difference.
Is there a way to successfully export the audio when using the H.264 format?

Thanks -- it's too bad QuickTime Pro doesn't properly handle this. I successfully used iTunes as a workaround as well (I exported the audio track to a standalone mov, opened in iTunes, exported as an MP3, then added back to the video in QuickTime Pro).

Report Title and Text Area issue when exported to pdf using Viewer

Hi there,
We are using OracleBI Discoverer Version 10.1.2.55.26
We have reports that displays Report title containing the following
- Report Title
- Runt Date and Time
- Page No
And text area which displays 'Last Page'
Following properties are set at the worksheet level using page setup
Report Title --> 'Print on every Page'
Text Area --> 'Print on last page'
The report when exported to PDF using Discoverer plus works fine and displays report title and text area as defeined.
But when we try to export the same report to pdf from Discoverer viewer, it displays
- Report title on first page only.
- text area on all pages
All our users accesses report using discoverer viewer so we cannot open discoverer plus to them.
Is there a solution which will enable us to export the report in pdf using discoverer viewer and displays the same output as discoverer plus.
Please let me know... If you have any questions then please feel free to ask.
Thanks in advance for your help...
Manish

but when opened on other os x machines some text is colored differently than it should be
Well, if typographic objects are colour managed, the colour appearance is dependent on the source ICC profile that describes the colourants in the typographic objects and the destination ICC profile that describes the colours the display is able to form and the RBC colourant combinations that will form those colours.
In general, typographic objects should have special treatment, since the expectation is not that typographic objects should be colour managed, but that typographic objects should simple be set to the maximum density of dark. On a display, that is R=0 G=0 B=0 and on a seperations device (a lithographic press) that is C=0 M=0 Y=0 K=100.
If for some reason typographic objects are colour managed, and if the ICC profiles for the displays are off by half a mile or more in relation to the actual state of the display system, then the colours will not be the same. On the other hand, if those displays are calibrated and characterized, then the colourants will be converted to form the same colours on the displays.
/hh

Crystal Reports Formatting issues when exporting to Word Editable document

Version: CR XI, I am editing a document exported from CR to Word Editable
When exporting to a Word Editable (.rtf) document the formatting changes. For example: lines that were drawn in the report do not come across, there is a tab in front of each line and a carriage return at the end of each line and spacing and justification formatting are not the same. Is there a way to export to Word Editable and keep the formatting integrity? This report was developed by a third party but I can edit it if needed.

Pages 5 is, as an early reviewer put it, "an unmitigated disaster." Not only does it lack some 100 feautres that are present in Pages 09 (4.3), it is also VERY buggy, A quick look through these discussions will reveal a painful litany of data corruption, files that cannot be opened, lost data, and other anomalies. Links do not export reliably to PDFs, and, as you've discovered, export to .docx format is unreliable. Sadly, the best advice is to trash Pages 5.1 and use Pages 4.3 or — yes, it's come to that — Word instead.

Quality Issues when exporting to itunes

I'm a new user to garageband and have been learning quite a lot about it and how to work with it.
My band recorded some songs tonight on garageband. I have a basic mixer hooked into the line in port of my macbook pro. When I tried to export it to itunes, the completed song, the quality from gb3 to itunes was horrible. In gb, it sounded really good, yet when it played back in itunes, it was of quite low quality. I'm curious if there are any preferences or advance options I missed when exporting from GB into itunes.
Thanks in advance.

Hey thanks for everyone's help. I played with the input volume, track volume and master track volume and the songs sound fine (well, still a bit overmodulated, but nothing I can do, it was recorded live).
The songs tend to sound better when I export them from itunes under WAV settings. The sound is tons better.
MacBook Pro G4 Mac OS X (10.4.6)

Audio Sync Issue When Exporting to Quicktime

Currently using Premiere Pro CS3 3.2 and Quicktime 7.5.5
When I export to a quicktime .mov, my audio is a few frames out of sync. I've tried downgrading to older versions of quicktime with no success. Everything is completely in sync inside Premiere. If I import my rendered out-of-sync .mov back into Premiere, it magically syncs up fine again. It's the weirdest thing.
Help!

Scott:
There is a workaround.
I never really found a solid cause/solution, but if you're noticing that you have a couple of white frames at the end of your Quicktime exports, then you're probably suffering the same problem I have. Tech people I have checked with have suggested that the problem may be related to the use of .mp3 sound files (as opposed to .wav) in the Premiere project, but after removing them and replacing them with .wav's the problem persisted.
I am not technical enough to figure out exactly what's causing the problem, but I think it must have something to do with the Adobe Media Encoder (at least how it works on my computer). From what I've read on the subject, the Media Encoder is Premiere's Achilles's Heel.
Changing versions of Quicktime did nothing. Others trying to solve this problem have tried exporting their files with every conceivable variation of options and settings in the Adobe Media Encoder with no positive result.
I'm not the only one with this issue, but searches of the Internet show it to be relatively rare, so it's probably some weird glitch somewhere deep in my system. It's not widely-reported enough for anyone to care about addressing this bug. Of the few people that I've found suffering from this anomaly, none have found a fix.
But the good news is that I have found a workaround that accomplishes getting a quicktime file out properly that does work for me. I avoid the Adobe Media Encoder completely.
Step 1: Go to File > Export > Movie, and under Settings > General choose QuickTime, under Video > Compressor choose H.264, then Uncompressed Audio. I have not experimented with other settings, but believe that most of them will do just fine.
If you examine the quicktime file you've just exported, you'll see it works just swell; i.e. no white frames at the end of the movie and the sound syncs up perfectly. Okay, sounds great---but there's no way to limit the data rate using this method, which means we're stuck with a ridiculously large file.
The solution is to load the Quicktime file that you've just exported into Quicktime Pro, and now export it using data rate compression / sound compression options to suit your tastes. Bingo!
The other workaround that I have heard from some is to export your movie (again, avoiding the Adobe Media Encoder, instead using File > Export > Movie) as an Uncompressed AVI, and then compress with QT pro as before. This method didn't work for me, something about not having the proper codec on my system to read the AVI file that was exported, which makes absolutely zero sense but I couldn't find the right codec anywhere, even after identifying it with some super-duper codec identification utility. Go figure!
So, you'll have to get QT Pro ($30 I think) to use this workaround, but it does work, and that's what counts. I have no idea if there's a QT Pro clone or similar program available out there. Compression/decompression and all that jazz is way beyond me and I'm just happy to be able to get my file finally out there in working condition.
The only other bit of information I might share with you is that I tried searching the Internet at great length to try and solve this issue, but on the rare occasion I did find someone suffering this problem they were as confounded and frustrated as I was, and no one had a real solution. I continued to search with different search terms and tripped over the clues to this solution when searching for "white frame problem" in relation to Premiere. I even believe that if you search the Abobe forums you may find some posts about it, so if you're inclined to learn more about it, I suggest concentrating your searches with terms that refer to the white frame problem/issue, instead of the terms I used for so long, such as "Premiere Audio Sync Quicktime" and the endless permutations thereof.
But I'll bet this workaround works for you. Let me know, and if you'd like me to try it on one of your exports on my computer I'd be happy to give it a go.
I have often wondered if upgrading to CS4 would solve this problem. Are you using CS3 like me? If I could be sure CS4 made this issue vanish I would jump on it, but there just isn't enough information out there to know for sure. I'm inclined to think not.
Please do let me know if this solution works for you, or if you dig up any new information.
Thanks!

Issues when Exporting to H.264

Similar Messages

Maybe you are looking for