Big file export issue

Hello,
We have developed a pair of import/export plug-ins in order to support a in-house format. For several reasons, which are not explained here, we had to develop import-export plugins instead of a single format plug-in. Our in house file format is designed for aerial and satellite images and supports very large files which can be above 100.000*100.000 pixels in size.
The import plug-in works fine with large images but, unfortunately, we cannot export these images because the export plug-in is grayed out in the drop down list when a large image is loaded. We have tried with several versions of Photoshop up to CS 6 but the problem remains. We haven't found any attributes in the export plug-in in order to indicate that it supports large images.
Has anyone got an idea ?
Thanks,
Bruno

Heh, we also seem to run into the same issue with our Geographic Imager plugin, when exporting georeferenced files that exceed in either height or width the 30000 pixel limit (yeah, a common case for aerial or satellite data). PS indeed disables the menu and I'm unaware about any workaround for it (I'd also love to know if there is one). What's more important though, is that Photoshop doesn't actually disable the export plugin in this case - you can still run it through scripts or actions. And this is why for us specifically this is not really a big deal, because we do provide access to all our functinality including Export via our own panel.
Here http://forums.adobe.com/thread/745904 Chris mentioned a PIPL property that was supposed to exist that limits the exported file size, but I think the overall conclusion was that it didn't make it to the release, so unless he or Tom enlighten us here about another magic property, there may be no better soultion to it.
ivar

Similar Messages

File export issue

Hello. I'm having an issue with the file I export from FCP 6.0. Every time I play it on Quicktime it suddenly hangs the program and it crashes.
I'm working on a Macbook (2.0 Ghz. 2 gigs of ram) with an external hard disk drive (via USB 2.0). The footage was captured with a Canon 5D, and it's on H264 format. It has a resolution of 1920 x 1080, with a vid rate of 23.98 frames per second.
Obviously the machine has some difficulty dealing with this kind of footage, but it gets the job done mostly, except for the TITLES that I create. When I export the file and it reaches the area of the titles Quicktime hangs and I have to force quit.
The setting of the sequence is the same of the footage (1920 x 1080. Vid rate: 23.98 fps. Compressor: H.264)
What could be causing this problem? Thanks in advance for your answers.

I also thought that it was due to the use of USB and not Firewire, but I have worked with USB hard disk drives several times editing DV / HDV footage (even though it's not the adequate way)and it hasn't caused problems. Now, the thing is that this clips are more demanding, and I guess it could be a problem now.
I didn't know that FCP doesn't edit H.264 properly. I'll convert the material to another format (like the one you suggested) and see if it works.
Thanks for your answer.

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

Export color vs. print to file color issue with 2.3RC

Hi,
I'm having problems with exporting photos for web-site usage.
In short: colors get extremely washed out and plain when using "export to disk" (requesting sRGB color profile, in jpg-format). But, when "printing to file" using sRGB profile and rendering intent perceptual colors are reasonably close to what I see in LR. Yes, I know, sRGB is limited, but...
Why there is such a difference when both methods are using sRGB for generated jpg? Is it the fact that rendering intent can not be selected for "export to disk"?
As I can not control pixel dimensions in Print mode is not an option for my use (and I can not control sharpening with plug-in, but the color issue is there to begin with without any export plugin intervention).
In contrast, LR 1.4 export to disk gives reasonable colors, the color issue has appeared with 2.x series.
Running Windows XP SP3, LR 2.3RC, display calibrated with Color Vision SPyder 2.
Please help, this is driving me nuts :(

I think, that your examples shows the same problem as my observations.
It seems that your display has even smaller gamut than sRGB (on my notebook DELL D620 this is also the case) so after you calibrated it, both lightroom and color managed firefox shows more saturated colors than windows explorer showing exported image (as far as I know, export from library module works correctly, but win explorer is not doing conversion to your monitor profile, that's why image is undersaturated). This is correct. It is really hard to calibrate such a low quality display, which can often be found on cheap notebooks - I have my own experience with it. Blue shades are really weak so heavy corrections have to be done in the profile (generated with spyder in your case), which can result in purple skies (why? Read this: http://www.brucelindbloom.com/index.html?WorkingSpaceInfo.html).
Problem is with image printed to file. This should look same as file exported from library module given that you use sRGB both as a destination space in export from library and as a printer profile while printing to file. In your case LR printed your image using values corresponding to your monitor profile (even if sRGB was selected) which resulted in oversaturated image (because your display has smaller gamut than sRGB). In my case images printed to file are undersaturated (because my monitor has gamut wider than sRGB). But I'm sure this is a bug! Your monitor profile should not affect printing to file in any case if sRGB is selected as printer profile!
Summary: purle sky in LR and in color managed FF is ok, but purple sky in image printed to file is not ok. :-)
And my hint: do not try to calibrate this display... :-)
You can try to make some measurements of your UNCALIBRATED NB display using this freeware: http://www.homecinema-fr.com/colorimetre/index_en.php You will probably see a very uneven color temperature across grayscale and much smaller gamut than sRGB.
Let us know your findings.

Aspect ratio issues in iDVD with mov files exported from FCE

Please help. I believe this is an iDVD bug. I have found some relevant discussion of it on online forums - but have not found a solution that works for me. I am looking for a workaround.
http://discussions.apple.com/thread.jspa?threadID=1356500&tstart=31
PROBLEM STATEMENT:
My 4:3 movies, exported from FCE in QT-with-conversion formats (any 4:3 format) - appear in iDVD with gray side-pillars (as expected for 4:3) AND with a black line (letter-boxing) at top and bottom - as would be for 16:9. It appears the aspect ratio is also distorted i.e. 16:9. (The iDVD project is set to 4:3.)
1- A 4:3 mov file exported from FCE using Quicktime Movie format (no conversion) does not have the problem, but I cannot de-interlace the video using this export mode.
2) A 4:3 mov file exported using QT-with-conversion mode (any 4:3 format) DOES have the problem. I need to use this mode in order to get de-interlace.
(Exception: 640x480 VGA mode does not have the black lines, and it displays correctly in dvd player on my computer screen - but on the TV screen, it crops content from the top and bottom of the movie, so this is not an option.)
3) In Finder, if you click on mov file exported QT-only (no conversion), it opens in the FCE viewer. If you click on mov file exported in any other 4:3 mode, it opens in Quicktime viewer (i.e. there is absolutely something different in the header/ID of these files.)
4) All mov files, regardless of export mode, show correctly in Quicktime viewer - no black line, no distortion. The problem does not occur outside of iDvd.
5) I tried passing the QT-with-conversion mov files through an Inverse-Anamorphicizer (per suggestion on forum - this apparently fixed the problem for some people) but the resulting output mov (i.e. the inverted product) still had the same problem.
I am, so far, left with this trade-off: Give up the de-interlacing, or live with the letter-boxing/ distortion. Neither is acceptable.
I am looking for a workaround:
1) A way to export de-interlaced 4:3 mov from FCE that shows in correct ratio in iDVD
2) A way to "convert" / re-head mov file after exported so that it displays corrrectly (inverse-anamorphicize) so that iDVD reads it correctly
3) Can the mov be de-interlaced after the fact (so I could use QT export without conversion)?
4) Something besides iDVD to put this together - that doesn't have this problem? (I like and want to use the iDVD menu/theme.)
5) Other?????
I also notice that all the QT-with-conversion mov files are 1/3 to 1/2 the size of the QT-only mov file, which is valuable and preferable to me. (I don't see any quality difference in the display...)

In the Preview window > top frame > middle button
do you have correct for pixel aspect ratio checked or not?
!http://i533.photobucket.com/albums/ee340/gogiangigo/Picture1-4.png!

Big File issue

Hi Group,
When we are trying to process the big file (around 40MB) ,the source file adapter not picking up the file,we are using AAE,can any body suggest if we required any addition tuning.
Regards,
Rajiv

Hi Rajiv,
As said above by Michal 40 MB is not a big file but if yo need to tune your server you can set the below parameters in PI Server.
u2022     UME Parameters : May be we need to look into the pool size and poolmax wait parameters - UME recommended parameters (like: poolmaxsize=50, poolmaxwait=60000)
u2022     Tuning Parameters: May be we need to look/define the Message Size Limit u201Clike: EO_MSG_SIZE_LIMIT = 0000100u201D under tuning category
u2022     ICM Parameters: May be we need to consider ICM parameters (ex: icm/conn_timeout = 900000. icm/HTTP/max_request_size_KB = 2097152)
Thanks and Regards,
Naveen.

Export issue:saw.dll instead of cvs file in Chrome

Hi Experts,
We have a problem while exporting data from BIEE Dashboard in Chrome. Instead of a CVS file, we got a saw.dll file exported. When we opend the saw.dll with text editor, the data was shown in text, however, we want to use it in Excel.
Please advise if you have any idea.
BIEE Version:11.1.1.5.0

Hi MuRam,
Thanks for quick response. But this option doesn't work in my situation.
I added two answers in the Dashboard. One was a short version which was displayed with a few columns. The other included more columns just for exporting. So it only show a static view of some notes. The export link was added in the long version. With the option export to excel, only these static notes would be downloaded.

Why jpeg file exported from Aperture with 300 dpi's it opens with 72 dpi's on PS ( image size)? I've tried several combinations and all give different results. And I am confused on what is the best workflow for me.

Ok.
My workflow is
RAW > Aperture Library > export jpeg high resolution 300 dpi's > one file on PS > edit > Save us jpeg. The I realised that files from PS were being save in a smaller size from the ones exported form Aperture. That is when I went o see <image size> on PS and files were with 72.
Since ten I've trying different things
1. Aperture > export as PSD > open on PS > edit > Save us jpeg = small file (around 15 MB)
2. Aperture > export as jpeg high resolution 300 dpi's > open on PS > CHANGE dpi's to 300 on <image size> edit > Save us jpeg = big file (Huge, actually)
What am I doing wrong? Would someone give me guidance and tell me what is the best workflow, considering I edit photos to deliver to my clients and I shall give them 300 dpi's.
Thank you

This is a known Aperture issue: Problem with Aperture 3.6 preset exports. | Apple Support Communities
Benjamin

CS6 PSD Could not export the clipboard because it is too big to export

I have been getting the error "Could not export the clipboard because it is too big to export" since upgrading to CS6. The same files at the same bit depth on the same computer do not cause this error in CS5.
In fact, I can open a file in CS5, copy it, and paste it into CS6 with no trouble. If I then copy again within CS6 and leave the program, I am given the error. (As a note, I have not run these programs simultaneously, except to run this test.)
This error appears regardless of whether Photoshop CS6 is running alone, or with several apps.
The Raw files are from a Canon 5D mark ii and tend to be 20-25MB in size,
I am running a Mac Pro 2.8GHz Quad Core Intel with 24GB of RAM. I have set the preferences to allocate 70% of this RAM, which should be sufficient. Changing the allocation to 90% or 100% has no effect, nor does adjusting the tiles configuration. My scratch disks have 130GB and 500GB free.
How do I correct this problem?

Hi, FYI, To duplicate a layer on top of itself, use Command+A, Command+J (jump the layer) if you need part of it, make a selection instead of a Command+A, this will also avoid the clipboard, and use Photoshop's scratch disk instead.
(I don't know why you run into that issue in CS6 and not in CS5, so I try to give you useful workarounds)
I'm not talking about bigger tiles, but of unlimited clipboard size that you find here for CS5: http://www.adobe.com/support/downloads/detail.jsp?ftpID=4965
But are not listed here for CS6: http://helpx.adobe.com/photoshop/kb/plug-ins-photoshop-cs61.html#id_68969?PID=3350462
Maybe did you install it in CS5, but forgot all about it?

Photoshop CC slow in performance on big files

Hello there!
I've been using PS CS4 since release and upgraded to CS6 Master Collection last year.
Since my OS broke down some weeks ago (RAM broke), i gave Photoshop CC a try. At the same time I moved in new rooms and couldnt get my hands on the DVD of my CS6 resting somewhere at home...
So I tried CC.
Right now im using it with some big files. Filesize is between 2GB and 7,5 GB max. (all PSB)
Photoshop seem to run fast in the very beginning, but since a few days it's so unbelievable slow that I can't work properly.
I wonder if it is caused by the growing files or some other issue with my machine.
The files contain a large amount of layers and Masks, nearly 280 layers in the biggest file. (mostly with masks)
The images are 50 x 70 cm big @ 300dpi.
When I try to make some brush-strokes on a layer-mask in the biggest file it takes 5-20 seconds for the brush to draw... I couldnt figure out why.
And its not so much pretending on the brush-size as you may expect... even very small brushes (2-10 px) show this issue from time to time.
Also switching on and off masks (gradient maps, selective color or leves) takes ages to be displayed, sometimes more than 3 or 4 seconds.
The same with panning around in the picture, zooming in and out or moving layers.
It's nearly impossible to work on these files in time.
I've never seen this on CS6.
Now I wonder if there's something wrong with PS or the OS. But: I've never been working with files this big before.
In march I worked on some 5GB files with 150-200 layers in CS6, but it worked like a charm.
SystemSpecs:
I7 3930k (3,8 GHz)
Asus P9X79 Deluxe
64GB DDR3 1600Mhz Kingston HyperX
GTX 570
2x Corsair Force GT3 SSD
Wacom Intous 5 m Touch (I have some issues with the touch from time to time)
WIN 7 Ultimate 64
all systemupdates
newest drivers
PS CC
System and PS are running on the first SSD, scratch is on the second. Both are set to be used by PS.
RAM is allocated by 79% to PS, cache is set to 5 or 6, protocol-objects are set to 70. I also tried different cache-sizes from 128k to 1024k, but it didn't help a lot.
When I open the largest file, PS takes 20-23 GB of RAM.
Any suggestions?
best,
moslye

Is it just slow drawing, or is actual computation (image size, rotate, GBlur, etc.) also slow?
If the slowdown is drawing, then the most likely culprit would be the video card driver. Update your driver from the GPU maker's website.
If the computation slows down, then something is interfering with Photoshop. We've seen some third party plugins, and some antivirus software cause slowdowns over time.

File- Export not working after upgrade from 11i to R12

Hi,
File -> Export not working after upgrade from 11i to R12.1.3 in few systems. Can you please let me know what could be the issue.
If export record count more than 200 it is working fine in all the systems and if change the profile option "Export MIME type” value to ‘text/tab-separated-values’ from application/excel also it is wokring.
Thanks and Regards,
Jagadeesha

Enabled the FRD. Below are few last lines. Can you please let me know what i can in this log file contents.
In Argument 1 - Type: String Value: global.frd_debug
Executing GET_ITEM_PROPERTY/FIELD_CHARACTERISTIC Built-in:
In Argument 0 - Type: Integer Value: 196613
In Argument 1 - Type: Number Value: 54
Out Argument 0 - Type: String Value: 12
Executing COPY Built-in:
In Argument 0 - Type: String Value: Entering app_menu.set_prop.
In Argument 1 - Type: String Value: global.frd_debug
Executing FIND_MENU_ITEM Built-in:
In Argument 0 - Type: String Value: FILE.EXPORT
Out Argument 0 - Type: Integer Value: 19
Executing GET_MENU_ITEM_PROPERTY Built-in:
In Argument 0 - Type: Integer Value: 19
In Argument 1 - Type: Number Value: 79
Out Argument 0 - Type: String Value: TRUE
Executing COPY Built-in:
In Argument 0 - Type: String Value: Completed app_menu.set_prop.
In Argument 1 - Type: String Value: global.frd_debug
Executing COPY Built-in:
In Argument 0 - Type: String Value: Completed app_synch.menu_toolbar_sync. Event is WHEN-NEW-ITEM-INSTANCE.
In Argument 1 - Type: String Value: global.frd_debug
Executing NAME_IN Built-in:
In Argument 0 - Type: String Value: GLOBAL.APP_CUSTOM_MODE
Out Argument 0 - Type: String Value: NORMAL
Executing NAME_IN Built-in:
In Argument 0 - Type: String Value: GLOBAL.APP_CUSTOM_MODE
Out Argument 0 - Type: String Value: NORMAL
Executing COPY Built-in:
In Argument 0 - Type: String Value: NULL
In Argument 1 - Type: String Value: GLOBAL.OUT
Executing USER_EXIT Built-in:
In Argument 0 - Type: String Value: FND GETPROFILE NAME="UPK_RECORDING_ENABLED" FIELD="GLOBAL.OUT" N
FNDCPVCM, 11, Built-In, Entry, 316509814, USER_EXIT
FNDCPVCM, 11, Built-In, Exit, 316509814, USER_EXIT
Executing NAME_IN Built-in:
In Argument 0 - Type: String Value: GLOBAL.OUT
Out Argument 0 - Type: String Value: N
Executing NAME_IN Built-in:
In Argument 0 - Type: String Value: system.current_form
Out Argument 0 - Type: String Value: FNDCPVCM
Executing NAME_IN Built-in:
In Argument 0 - Type: String Value: system.current_block
Out Argument 0 - Type: String Value: MASTER
Executing NAME_IN Built-in:
In Argument 0 - Type: String Value: system.current_form
Out Argument 0 - Type: String Value: FNDCPVCM
Executing NAME_IN Built-in:
In Argument 0 - Type: String Value: system.current_block
Out Argument 0 - Type: String Value: MASTER
Executing GET_APPLICATION_PROPERTY Built-in:
In Argument 0 - Type: Number Value: 75
Out Argument 0 - Type: String Value: IHR40P
Executing COPY Built-in:
In Argument 0 - Type: String Value: Completed call_all_libraries. Event is WHEN-NEW-ITEM-INSTANCE.
In Argument 1 - Type: String Value: global.frd_debug
Executing COPY Built-in:
In Argument 0 - Type: String Value: Completed app_standard.event. Event is WHEN-NEW-ITEM-INSTANCE.
In Argument 1 - Type: String Value: global.frd_debug
FNDCPVCM, 10, Prog Unit, Exit, 316509814, /FNDCPVCM-3/P45_30_DEC_201223_28_33
FNDCPVCM, 9, Trigger, Exit, 316509814, WHEN-NEW-ITEM-INSTANCE
FNDCPVCM, 8, Prog Unit, Exit, 316509814, /DMU-4/P8_30_DEC_201223_23_12
# 15 - FNDCPVCM:MASTER.USER_CONCURRENT_QUEUE_NAME.1359399301498413820
WINDOW FNDCPVCM PROGRESS_INDICATOR RESIZE 4198 1500 3
# 16 - FNDCPVCM:MASTER.USER_CONCURRENT_QUEUE_NAME.1359399301512613925
WINDOW FNDCPVCM PROGRESS_INDICATOR RESIZE 4198 1500 3

Format changing when IDCS3 file exported to PDF

I am using Acrobat 8 version 8.1.2, and InDesign version 5.0.2.
I am noticing a very specific problem when exporting some files to PDF from InDesign.
We often have a format where we have a numbered list of right-aligned number, followed by some text, a leader line, and then another number at the end of the line. This is set up with a left indent and a first line left indent (rather than using the numbered list options, we are required to do it this way where I work), and then the necessary tabs later in the lines.
I am finding since we switched to IDCS3, that when I export to PDF, lines containing this format change in the PDF. The text that appears after the number in the front of the line is pushed over on top of the leader line, leaving a huge white space. On rarer occasions, it will move things in lines that have no indents, but contain tabs that aren't being used.
I have been able to get the files to export correctly by removing the left indent and first-line left indent and using tabs instead (or by removing unused tabs). But we have hundreds of files set up in this manner so going in and changing how they are all set up is problematic to say the least. Many of these are also multi-line and not using the indents means we have to manually tab lines over.
Is this a known issue? Does anyone know why this might happen and how I can prevent it?
I tried posting in the Acrobat forums and it was suggested since it's an export issue that I might get more help from the InDesign folks.

Given that the file is being exported to PDF and not going via a driver route, there really is no reason why changing the default printer should make a difference whatsoever in this particular case. Changing default drivers in Microsoft Office applications, yes, but for this situation, no. And since Acrobat doesn't change formatting, the issue sounds like some problem associated with InDesign. Please report this problem directly to Adobe Tech Support and be prepared to send them sample files. Thanks!
- Dov

I've doubled my RAM but still can't save big files in photoshop...

I have just upgraded my Ram from the shipped 4GB to 8GB but I still can't save big images in photoshop. It seems to have made no difference to the speed of general tasks and saving and I can't save big files in photoshop at all. I already moved massive amounts of files off my computer and onto my external hard drive, so there is much less in my computer now, and twice the RAM but it is making no noticeable difference. When I click memory, under 'about my mac' it shows that the RAM is installed and now has twice the memory. Could this be something to do with photoshop? I'm running CS6.

Also, I just calculated 220 cm into inches and this is roughly 86.5 inches. Over 7 feet in length.
WIth an image that large, you may want to consider down sampling to a lower DPI to help with being able to work on and process images of this size much easier and it will be easier for your Print house to process, as well.
You might want to consider working with these rather large images at 225 DPI instead of 300 if resolution at close distances is still a concern.
Or what you good try is working with the images at 300 DPI, but then save them/export them as a Jpeg image at the highest image quality setting.
I do a lot of project where I use a high resolution jpeg image to save on image proceesing overhead.
The final printed images still come out pretty clear, clean and crisp without having to process those large files at a print house or having to deal with using that full resolution image in a page layout or illustration program.

PS CS3, Camera Raw 4.6 Update and Nikon D810 NEF File Reading Issue

Currently Have Photoshop CS3 & Adobe Bridge CS3 2.1.1.9.
According to Adobe, Camera Raw 4.6 supports Nikon D810 NEF files. I have downloaded Camera Raw 4.6 Update. When
I try to open Nikon D810 NEF files, I get Photoshop CS3 error that says
"cannot complete request your because it is not the right kind of
document. These NEF files wont open in Adobe Bridge at all. What am I doing wrong?

Hey,
Before I purchased, let me get your thoughts on another option that just occurred to me which involves:
1)Editing my D810 NEF files in LR 5.6, which I have, then exporting/saving the edited files as JPEGs.
2) Doing any additional editing, as necessary (i.e. that might require layering or selections..etc) , with the JPEGs with Bridge or PS CS3.
This method wont involve any additional software purchase now.. right? Am I missing anything. here? Since my final output to my customers are JPEGs any way, wont this work? Will I be at any disadvantage. Am I missing anything. here?
From: ssprengel <[email protected]>
To: charles cash <[email protected]>
Sent: Monday, October 6, 2014 9:49 AM
Subject: PS CS3, Camera Raw 4.6 Update and Nikon D810 NEF File Reading Issue
PS CS3, Camera Raw 4.6 Update and Nikon D810 NEF File Reading Issue created by ssprengel in Adobe Camera Raw - View the full discussion
You can buy it from here:
http://creative.adobe.com/plans
Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at https://forums.adobe.com/message/6795004#6795004
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page:
To unsubscribe from this thread, please visit the message page at . In the Actions box on the right, click the Stop Email Notifications link.
Start a new discussion in Adobe Camera Raw by email or at Adobe Community
For more information about maintaining your forum email notifications please go to http://forums.adobe.com/thread/416458?tstart=0.

OMF Export issue in Premiere CS6

Hello,
I am trying to export a feature length OMF file for my sound mixer. I have the tracks I want on and selected. I then do File - Export - OMF. I do encapsulated audio, with 60 frame handles. I then start the export. I encodes through the files then it starts "generating metadata" and making its "First Pass Parsing Tracks", but it will immediatly jump to about 1/3 of the way through and just sit there. I have left it for about 3 hours and it still sits there. I have tried saving to various folders/hard drives and still no luck. I have seen people having problems with the omf working with other programs, but I haven't seen many people with this problem. Deadline is fast approaching and I desperately need to get this out to my sound mixer. Any help is GREATLY appreciated.
Tony

Hi Anthony,
I'm using Premier Pro 6 from the creative cloud, and am also doing a feature length doc. I'm having issues exporting an OMF and it originally came from FCP 7. I'm wondering if you've had any other reflections on the issues mentioned above and if you can offer any more insight? I'm pretty sure I don't have any filter applied anywhere as I had only exported it from FCP 7 when I was in the logging phase.
Someone else mentioned using Audition. Send the whole sequence to Audition and export an OMF from there. Have you tried to send your feature length doc sequence to Audition and has it been succesfull?
Any feedback would be greatly appreciated.
Thanks
Ryan

Big file export issue

Similar Messages

Maybe you are looking for