File Resolution Export Problem

I'm having problems with the resolution option when I export my images as jpegs in Lightroom.
In the export dialog box, I enter the file resolution as 240ppi, but once the file is exported and I open it in Photoshop or Bridge, the resolution is 72ppi not 240ppi. Any ideas what could be causing this?

Screen display ignores the PPI setting. Set PPI in LR to 1 on a test image. That image will display exactly the same as the same image set to 300ppi. PPI/DPI are printing issues, not screen display issues. Screen display is controlled by pixel dimensions only. Try it you will see.

Similar Messages

File Size & Export Problems

Hi, my name's Jorge and I have a couple of questions.
First, is I make machinima movies and my latest movie is 21:48 long. In order for it to be uploaded to a certain website, it needs to be under 200 MB's. I'd like the visual quality to at least be decent.
What is the best way to export my movie from FCE and have it under 200 MB's?
I'm pretty sure this can be done, because a while ago, someone else made a movie that was also 21 minutes long and the file size for her movie was only 131 MB's, and I can't seem to make mine less than 319.2 MB's.
This brings me to a problem I'm having. I've signed to be an official director at Machinima.com and they require the movies to be in wmv format. It also says that the movie files would be smaller sizes, so I figured that would help my file size problem.
So I tested it out, trying to export my movie from FCE at the wmv specs they required, but it only exports 30 seconds of the movie. (?) Why is this happening and what can I do to fix this?
Since I have signed on with Machinima.com, I need to be able to export my movies in this wmv format.
Any help would be SO GREATLY appreciated.
Jorge

So I tested it out, trying to export my movie from FCE at the wmv specs they required, but it only exports 30 seconds of the movie. (?) Why is this happening and what can I do to fix this?
The trial version of flip4mac only allows up to 30 seconds per export. You'll need to purchase one of the flip4mac plugins if you want to export a complete video.
http://www.telestream.net/flip4mac-wmv/overview.htm
-DH

Good evening. When I try to rename a master file or export a master file, it only allows 9 spaces for my new name, even though Aperature 3 allows many more spaces than that for version names. This creates a lot of problems and headaches for me.

Good evening. When I try to rename a master file or export a master file, Aperature 3 only recognizes the first 9 spaces for raw .NEF files, even though it easily uses twice that many spaces for version names. I have a system in place that works really well for me, wherein by changing the file name I can recognize what's important to me just by glancing at the file name, no matter what system it is in, I do not have to open or mouse over anything to know what the file is. My files also arrange themselves in order no matter what file system they are in. Can someone please tell me if there is a setting, or something I am doing wrong, that prevents me from using a longer Master file name. I can't be the only person who would like to have his Master File names correspond to the name that appears in the Aperature library, and would like to use at least 16 spaces (numbers, letters, etc.)
Thanks,
Photo Al

Hi Frank,
As you suggested, I am attaching several screen shots. In the first one you can see how I set up my preset. I used "Custom Name" and "Counter" with a dot between the two drag ins, followed by "D90". I also have a dot to seperate the 8 digits in the Custom Name and make it easier to read.
I then click "OK" which takes us to the second screen shot. Here you can see that in the Example File Name everything looks perfect, and you can see I have clicked on "Apply to Master Files".
In the third screen shot you can see that the version in my library did in fact change correctly. With the "mouse over" pop up screen you can see, however, that the Master File name was changed to "1933.1017.NEF". It failed to carry the "12D90" and if I go to where my masters are stored that is exactly what the name was changed to.
In the fourth screen shot I attempt to export the master. You can see how my "Version Name" is set up.
And finally on the 5th screen shot you see in the File Name Example the name "1933.1017.NEF" once again, which when I export the master is exactly how the name will appear. Since I will export more than one file at a time , a (1) and a (2) etc., will appear at the end of the names because all the files are being given the same "1933.1017.NEF" name.
I hope this reply does a better job of clarifying my problem. I am anxious to see if this is something I simply misunderstood, or if I am simply doing something wrong.
Thanks,
Photo Al

Exporting files from lightroom: problem with filename

Hi!
I am a sports-photographer and i use lightroom since version 1.0. i really like it to edit my pictures and it is very easy to use for importing my files and setting the meta-datas.
but i have one problem, that forces me to open up each file i export once again to rename it, what costs a lot of time:
when i export my files, i can choose a preset to give it a name, which works well. but i would need it like this: "my preferences"001 (f.e. oliver-climbing-01oct09001) and raising in numbers.
lightroom ALWAYS makes a "-" between my presets and the numbers.
does anyone know if there is a possibilty to export the file and give it a name without this "-" in fornt of the number?
glad to find a solution here!
cu or read u
oliver

hello!
thanx for the fast answer!
u are right, but this is not my problem:
i want lightroom to count my exported pictures starting with 001, then 002, then 003 at the end and so on
but if i use the sequency-number or anything else, it does not generate a new name like 001, then 002,
but it does make 001 and then 001-2 and 001-2...
u can see that in the screenshot i made down here...

Exporting All Audio Files - Having Some Problems. . .

Hi,
Im trying to export all my audio and audio intrument files as audio files so that i can pass them over to someone for a remix. Im having a couple of problems:
1. Automation does not bounce with the tracks
2. The tracks that run though busses does not bounce
3. Some of the exported files appear as clipping when we look at the waveform. The levels in logic appear as normal but the waveform is full, both when we view the region on the arrange and in the sample editor.
Has anyone got any advice on exporting all tracks as audio files or any advice on what this problem could be?
Thanks, Ben

benjamingordon wrote:
Whats PDC. Might seem like a silly question but im a bit lost.
Plug-in Delay Compensation. It's in the audio preferences, General tab.
If i want to have automation, then i have to bounce each track individually?
Yes. As John stated, the export feature bounces the file at Unity gain, and ignores automation. Generally speaking, this is the preferred method for handing off files to a mix engineer. But there are times when the automation is part of the sound you want. In these instances, you'll need to bounce those files, not export them. But certainly automation isn't part of every track?
I would suggest soloing each Aux track, or audio/innstrument track that needs to be bounced WITH automation, and then bounce offline. Bouncing offline will speed up the process of having to do these tracks one at a time.
When you're done with the bounced tracks, delete them from your arrange page (but DON'T hit SAVE). Then, use the function "Export ALL tracks as audio files", and all your remaining tracks will export at one time.

Lightroom 5.3 file export problems

Just upgraded to lightroom 5.3 and can no longer export photos. any clues?

A RAW file is a RAW file.
DNG is also a RAW format
Lightroom will not alter RAW fomat files on export, as in develop edits.
(it will record those edits in metadata if asked so another application capable of interpreting Lightroom edits can read and apply those edits - like ACR.)
DNG exports can be altered to various flavours of DNG but that does not include develop edits.
A colourspace can also be added as appropriate.
The other formats are derivative files and develop edits are baked in on export.
Tony Jay

Leica Monochrom and Lightroom export problems

I am using the latest version of LR on a 2011 Mac Book Pro. I am running into problems when I export Leica Monochrom DNG files that are shot AT AND ABOVE ISO 6400. Lightroom is brightening the files on export a lot so that the final exported file does not look anything like what my edit looked like. This only happens with full resolution exports. Other Leica MM users have experienced the same issue. I have photos and screen shots to prove this. What is the problem?

What I was hoping for was an original raw image with all the OP’s adjustments intact so I could demonstrate what was happening at various zoom levels and with different settings, but that seems overly difficult to come by so I’ll give my analysis of what is happening and what to do about it:
The brightening has to do with the micro-noise-grain that has been excessively sharpened making the image a mixture of mostly white and mostly black dots immediately adjacent to each other rather than continuous tone of a low-ISO image. This is not an error with LR or with the camera, and will happen with any such image from any camera. The “brightening” is merely the visibility of the white granules at 1:1 zoom. When a zoom level less than 100% is used, LR or Windows Photo Viewer or Mac Preview must determine how to combine multiple pixels together to represent one output pixel in the reduced-sized image. Different viewers use different methods to combine adjacent pixels into one. Some use Average, some use Median, some use the value of a single pixel position to represent the entire reduced-size combination pixel—this is called nearest neighbor and is the fastest but least accurate. LR is known to use a fast but inaccurate resampling algorithm which is why there is a warning on the Detail panel to use 1:1 zoom to judge sharpening and noise adjustments.
The problem here is that this lightening and darkening depending on zoom level is messing with toning adjustments, so how to tone and adjust such images, is to temporarily turn off Detail sharpening and turn up noise-reduction then adjust toning in Fit view. Then zoom in to 1:1 and adjust the noise-reduction up or down to remove most of the obvious grain, and turn up sharpen masking so all you’re sharpening is edges. Maybe even turn off the Detail slider (set to zero) to keep from enhancing micro-noise texture.
If you do want grain for artistic effect then do that after you’ve removed the ISO noise. The difference with high-ISO noise and added noise-grain is the high-ISO noise is single-pixel in size and will not be resampled accurately while the noise-granules created by the Effects panel can be control both in size and intensity so as not to respond negatively to resampling nearly as much.
If you are exporting images to nearly full resolution then dial back the export sharpening quite a bit. If you are resizing quite a bit smaller than any micro texture will have been averaged out by the resizing and adding more sharpening during Export sharpening will help things look crisp, again.

Hi Expert , crystal report export problem. system not responding

Hi,
crystal report export problem. system not responding.
Thanks
Rajkumar Gupta

Dear Raj,
Please try this
          Try
            Dim oSubReport As CrystalDecisions.CrystalReports.Engine.SubreportObject
            Dim rptSubReportDoc As CrystalDecisions.CrystalReports.Engine.ReportDocument
            Dim rptView As New CrystalDecisions.Windows.Forms.CrystalReportViewer
            Dim rptPath As String = System.Windows.Forms.Application.StartupPath & "\" & rptName
            Dim rptDoc As New CrystalDecisions.CrystalReports.Engine.ReportDocument
            rptDoc.Load(rptPath)
            rptView.ShowExportButton = True
            rptView.ReportSource = rptDoc
            For Each oMainReportTable As CrystalDecisions.CrystalReports.Engine.Table In rptDoc.Database.Tables
                oMainReportTable.Location = System.Windows.Forms.Application.StartupPath & "\" & SourceXML
            Next
            For Each rptSection As CrystalDecisions.CrystalReports.Engine.Section In rptDoc.ReportDefinition.Sections
                For Each rptObject As CrystalDecisions.CrystalReports.Engine.ReportObject In rptSection.ReportObjects
                    If rptObject.Kind = CrystalDecisions.Shared.ReportObjectKind.SubreportObject Then
                        oSubReport = rptObject
                        rptSubReportDoc = oSubReport.OpenSubreport(oSubReport.SubreportName)
                        For Each oSubTable As CrystalDecisions.CrystalReports.Engine.Table In rptSubReportDoc.Database.Tables
                            oSubTable.Location = System.Windows.Forms.Application.StartupPath & "\" & SourceXML
                        Next
                    End If
                Next
            Next
            'Setting Paper
            Dim rawKind As Integer = 0
            Dim printSet As New System.Drawing.Printing.PrinterSettings
            For i As Integer = 0 To printSet.PaperSizes.Count - 1
                If printSet.PaperSizes.Item(i).PaperName.ToUpper = PaperName.ToUpper Then
                    rawKind = CInt(printSet.PaperSizes.Item(i).RawKind)
                    Exit For
                End If
            Next
            Dim MyTest As New SaveFileDialog
            rptDoc.PrintOptions.PaperSize = CType(rawKind, CrystalDecisions.Shared.PaperSize)
            rptDoc.ExportToStream(ExportFormatType.Excel)
            'rptDoc.SaveAs("C:\TBKING.xls", True)
            '''How to export the report
            Try
                Dim CrExportOptions As ExportOptions
                Dim CrDiskFileDestinationOptions As New _
                DiskFileDestinationOptions()
                Dim rename As String
                rename = rptName.Replace(".rpt", "")
                Dim CrFormatTypeOptions As New ExcelFormatOptions
                CrDiskFileDestinationOptions.DiskFileName = _
                                            "c:\Report\" & rename & "_Export_File.xls"
                CrExportOptions = rptDoc.ExportOptions
                With CrExportOptions
                    .ExportDestinationType = ExportDestinationType.DiskFile
                    .ExportFormatType = ExportFormatType.Excel
                    .DestinationOptions = CrDiskFileDestinationOptions
                    .FormatOptions = CrFormatTypeOptions
                End With
                rptDoc.Export()
            Catch ex As Exception
                MsgBox(ex.ToString)
            End Try
            '' end by kevin shah
            rptView.Show()
            rptView.ShowExportButton = True
            Dim oFrm As New System.Windows.Forms.Form
            rptView.DisplayGroupTree = True
            rptView.Dock = System.Windows.Forms.DockStyle.Fill
            rptView.Location = New System.Drawing.Point(0, 0)
            oFrm.AutoScaleBaseSize = New System.Drawing.Size(5, 13)
            oFrm.Controls.Add(rptView)
            oFrm.Name = "Report Viewer"
            oFrm.Text = "Report Viewer11"
            oFrm.ResumeLayout(True)
            oFrm.WindowState = System.Windows.Forms.FormWindowState.Maximized
            oFrm.TopMost = True
            oFrm.ShowDialog()
        Catch ex As Exception
            objMain.objApplication.MessageBox(ex.Message)
        End Try
By pressing this button XLS file be generated on C:\report\
Hope this will resolved the issue
Thanks
Kevin

Export problem "A serious error has occured", or hang, upon export to Encore.

Hello,
I am using adobe Premiere CS3 3.2
I am trying to export my project to a DVD. I've been told that the best way to do this with minimizing quality loss is to export to Encore.
My project has some filters that affect system memory and have locked up the computer numerous times before, like Looks Suite and Noise Remover (on some clips)
when I choose export to Encore, then choose settings, I get the error "A Serious Error has occured...." Then I trried lowering the settings, and I got the window that says "Rendering", at least, but nothing appeared in that window after I left it overnight.
So I have some questions:
- What's the best thing I can do to export my movie onto a DVD with minimum loss of quality?
- Should I export as a video file first? Which is the best quality? Then can I export to Encore?
- Does it help to pre-render my entire project in Premiere first, THEN export to Encore?
I'd appreciate some advice.
Thanks!
EDIT: I just tried to export as a Quicktime Uncompressed video with the regular method (Export-> Movie).. and it gave me the error "Could not compile movie..." then the message "adobe premiere pro is running very low on system memory"
So I am assuming this is a memory issue? Then what should I do??
Also, I want to ask- If I put my entire project with all its files onto an external hard drive, then move them to another computer with adobe premiere pro installed which also has the same filters installed, would I be able to export this way?

I am quite sure it is a memory problem... the computer exported other videos in the past just fine, but its never been used for making a film with a lot of filters and such that run down the memory, and so it gives me the memory errors.
I am not sure what is "Memtest86+"... I would like to try such a program, but in fact this is not my computer... I am using a Workstation at a University and now I have limited time to complete my project (I must figure out a solution by the end of the day on Monday)
Maybe AVI is the best for some... but I have done comparisons beforehand which found .mov to be the best... and I was even told that uncompressed quicktime doesn't lose quality at all (though in fact it seems to just a bit). So if you not completely sure which will be better, I will go with .mov.
So I will try a few things- like exporting only the "special" clips which used a lot of filters on individually as .mov, then reimporting them into the project, then trying to export the whole thing into encore... If that does not work, I will try to export fragments as.mov (because if I try to export too much at one time, it has the memory error->crash).. then create a new project, import the .mov files, and export to Encore.
I only have limited time to solve this problem.. do you all think I am taking the right steps?
Also one key question I have is about the audio.. do you recommend that I export all of the audio into one wav file, and then put that into the new project? Or should I just export the quicktime files, with their audio, into the project and keep it like that?
I appreciate the help, again

I just got a new Mac Mini, and now when I try to import photos into Lightroom, iPhoto try to load them first, then Lightroom can't find the files. Big problem. What to do?

I just got a new Mac Mini, and now when I try to import photos into Lightroom, iPhoto ties to load them first, then Lightroom can't find the files. Big problem. What to do?

Simple:
File -> Export to get your photos out of the iPhoto Library. In the Export dialogue you can set the kind to Original and you'll get back exactly what you put in.
Apps like iPhoto2Disk or PhotoShare will help you export to a Folder tree matching your Events.
Once exported, you can then trash the iPhoto Library - just drag it from the Pictures Folder to the trash and empty it.
After that, if you're entirely neurotic about it, just put the iPhoto app in the trash and empty it.
Regards
TD

Export Problem in LR 3.5

Hi folks,
I have been working with LR 2.7 for a while now and was happy with it.
PC - Win XP - LR3.5
Photo's stored on external hard disk (K:)
The RAW captures of a Nikon 3100 I recently won were not being recognized/imported by LR 2.7 and I installed the 3.5 version to see if it was any better. I would have to buy it anyway by the time I switch to Win7. In 3.5 the Raw files were imported, the settings of 2.7 were nicely taken over but now and I cannot export the files I have worked on to the K: drive of the external hard drive as I used to do with 2.7.
I get the message 'The folder could not be found' though it is set in the Export Window and I am looking at it in Win Explorer.
The original RAW captures are on the D: drive but that was always the case with 2.7 as well... I am doing it exactly as I used to with 2.7.
I tried with a photo from an older folder of my usual camera and everything works fine there.
The problem seems to be only with the Nikon files. Now I start wondering if there is something with raw format of this Nikon camera that is putting LR in a twist...
Anybody any ideas to help me out?
Thanks and grts
Nil

@ web-weaver:
Of course they go to a different folder and they also get different
titels/names once processed in LR. The originals are always RAW (NEF) and I
export them as jpg or tiff files depending on what more I will do to them.
@ ssprengel:
I get the message when I have renamed the file in the export window, set
the folder it has to go to and hit export.
In the 2.7 version I got it already when I tried to import.
As I said, this only happens with the Nikon (NEF) RAW files. With the
Olympus (ORF) RAW files I have no problem at all and had no problem in LR
2.7 either.
I cannot see anything wrong in the Export panel nor in Preferences.
Plug in is Metadata Wrangler and has been updated to the latest version >
no joy...
I tried import/export with jpg files and no problem there.
Yesss! Got it! What I had overlooked was a question mark next to the folder
in Library (sooo small). A rightclick and telling LR where it was solved
the problem. Strange, though, as it has never done this before... the main
folder and the path are still the same as the ones that work perfectly with
Olympus exports... just a different subfolder named Nikon and another named
Test... Also strange that if I started off with jpg, it was no problem
either...
Anyway, thanks a lot for shaking my senses for me
Nil
2011/12/10 web-weaver <[email protected]>
Re: Export Problem in LR 3.5 created by web-weaver<http://forums.adobe.com/people/web-weaver>in
Photoshop Lightroom - View the full discussion<http://forums.adobe.com/message/4075999#4075999>

BUG?? UTF-8 non-Latin database chars in IR csv export file not export right

Hello,
i have this issue: my database character set is UTF-8 (AL32UTF8) and contains data in a table used in IR that are Greek (non-Latin). While i can see them displayed correctly in IR and also via select / in Object Browser in SQL Workshop when i try to Download as csv the produced csv does not have the Greek characters exported correctly, while the Latin ones are ok.
This problem is the same if i try IE or Firefox. Also the export in HTML works successfully and i see the Greek characters there correctly!
Is there any issue with UTF-8 and non-Latin characters in export to csv from IRs ? Can someone confirm this, or has a similar export problem with UTF-8 DB and non-Latin characters ?
How could i solve this issue ?
TIA

Hello Joel,
thanks for taking the time to answer to my Issue. Well this does not work for my case as the source of data (Database character set) is UTF-8. The Data inside the database that are shown in the IR on the Screen is UTF-8 and this is done correctly. You can see this in my example. The actual Data in the Database are from multiple languages, English, Greek, German, Bulgarian etc that's why i selected the UTF-8 character set when implementing the Database and this requirement was for all character data. Also the suggested character set from Oracle is Unicode when you create a Database and you have to support data from multiple languages.
What is the requirement, is that what i see in the IR (i mean in Display) i need to export in CSV file correctly and this is what i expect from the Download as CSV feature to achieve. I understand that you had in mind Excel when implementing this feature but a CSV is just an easy way to export the Data - a Comma Separated Values file, not necessarily to open them directly in Excel. Also i want to add here that in Excel you can import the Data in UTF-8 encoding when importing from CSV, which is fine for my customer. Also Excel 2008 and later understands a UTF-8 CSV file if you have placed the UTF-8 BOM character at the start of the file (well, it drops you to the wizzard, but it's almost the same as importing).
Since the feature you describe and if i understood correctly is creating always an ANSI encoded file in every case, even when the Database character set is UTF-8, it is impossible to export correctly if i have data that are neither in Latin, not in the other 128 country specific characters i choose in Globalization attributes and these data is that i see in Display and need to export to CSV. I believe that this feature in case the Database character set is UTF-8 should create a CSV file that is UTF-8 encoded and export correctly what i see i the screen and i suspect that others would also expect this behaviour. Or at least you can allow/implement(?) this behaviour when Automatic CSV encoding is set to No. But i stongly believe - and especially from the eyes of a user - to have different things in screen and in the depicted CSV file is a bug, not a feature.
I would like to have comments on this from other people here too.
Dionyssis

QuickTime Player export problem

When I save in QuickTime Player (10.0) as Movie everything works fine, but when I select another format, I get an "Export Progress" window, but after that finishes there is no file.
The problem seems similar as reported in this 1 year old thread:
http://discussions.info.apple.com/message.jspa?messageID=10326043
which doesn't have a solution.
Any idea what is going on?

...no problem Michael.But the question exist.Because is not accetable that a professional sw like FCP has these type of problems....if you making an application like Compressor I not understand why the export module inside program itself has these(very evidents....) problems. Question: Final Cut Studio
stand alone has COMPRESSOR inside???
This is like rallenty problems. Everyone tell me :" use rallenty in motion..is very good " Rallenty in Motion has the same identical problems (es : strobing...) that are in FCP (IDENTICAL !!). I use this SW and partially all applications of FCS 2 until 3 months but I have find problems like "banding" that people that use FCP from many many time have never see...is possible this??
It's a great suite but these things are inaccetable...this is my opinion.
silvio bonomi

Help! Exporting problem in Adobe Premiere & Media Encoder

Hi guys,
I have a problem for which I did not find any solution on the web. I am not a very experienced Premiere Pro user. Maybe you can help me!
I made a project using Adobe Premiere Pro.
It has only one Sequence, but I have multiple clips which I want to export in that sequence as separate videos (see video 1, video 2, video 3 in the image)
The problem is that when I open Adobe Media Encoder, I open the sequence and I export all the different clips, exported videos do not keep all the Effects that I've applied to the video (contrast and brightness adjustments, other different image adjustments / effects etc).
So, I can automatically export all the videos with Media Encoder, but with no color corrections or other adjustments. When I play the Sequence in premiere it all looks good. When I export all the videos using Media Encoder, they do not have any effects applied.
If I export the sequence directly in premiere as a long video, it keeps the effects, but I get only one single video, and I need all of them exported separately.
The only way it works is making different sequence manually and exporting each one at a time. But I have 200 of them. So it will take a lifetime
I assume there is a smarter way to do it.
Did it happen to you? Is it something that I don't do right?
What should I do to keep all the Effects that I apply when exporting from Media Encoder?
Is there another method which I could use to correctly export all the 200 videos in that sequence besides doing it manually?
Thank you!

Did you happen to select clips from the Project panel in Premiere Pro and queue to AME? Can you export a timeline correctly (select a timeline > File menu > Export > Media > Click "Queue")? Effects are applied only on clips in timeline and not on media clips under the Project panel.

Export problems- it's renaming my MOVs to strange things and they're huge!

Hey guys,
strange fcp export problem. I have a 10 minute anim compressed fcp project, 1920x1080, 30fps on a top-of-the-range macbook pro with external terabyte HD. I did a test export a couple of days ago, because our deadline is really soon, and that all worked fine - a 10 minute quicktime, 100% anim codec, was 26GB. That was fine. I did another test clip, just a spinning bitmap for 10 mins, from AfterEffects with similar, succesful, results and file sizes.
Now, however, when I export, it comes out as 60GB, and FCP changes the filename to something which is the first half of the filename I chose, and a strange number for the second half which is different each time I try it. Something like "filena#CF342.mov", for example. This file seems to have video in it OK, but it's 3 times the size, and the data rate is much higher, too high to play back.
The only changes I've made since my successful test are replacing many of the low res previews with hi res versions, and adding 1 minute to the end. And I changed my QMaster setup, not sure if that's anything to do with it.
Anyone got any ideas? I'm getting pretty worried.....
thanks in advance....

Thanks for the quick reply! No, don't think that's the problem. The new render doesn't have an alpha channel - it's Animation 100% Millions (not Millions+), and I don't think that would add more than 25% to the file size anyway. It also wouldn't account for the strange renaming of filenames. And the increase in length is only 10%. The file size has tripled!
The final delivery format was going to be animation, 1920x280, because it's going to projected on a 30m wide cinema screen and live TV tomorrow night but our playback solution (while it handles the test files ok) can't handle the data rate of these strange new files: it's 800mb/s, which is pretty ridiculous.
The renaming of the files suggests (to me at least) some kind of bug/error, but it doesn't report any kinda error in either fcp or quicktime.
Plan B is to recompress the strange big file using h264 which gives an ok quality and is 10% of the size. Reason I'd like to do it animation is I need to do several versions with different gamma, so I need to do further processing on the rendered file after it's dumped from FCP.
Any thoughts? I'd like to get to the bottom of this.
one thought - I didn't tick "recompress all files" and some of the source DOES have alpha - would it be taking the alpha channel even though I didn't ask for it?

File Resolution Export Problem

Similar Messages

Maybe you are looking for