Lightroom 5 doesn't export with a maximum long edge as instructed

What is going on with Lightroom 5? I upgraded from 4 and now it doesn't export with a maximum long edge of 2166 pixels even though that is what it is being told to do.

Hi Jim,
It fails to shorten to the maximum long edge requested, leaving longer-edged files in the exported folder.
Never had this problem with Lightroom4. Just upgraded to 5. My operating system is Windows Pro 8.
Thank you for your time.
Gary
Gary Lloyd McCullough
www.GaryLloydMcCullough.com
(904) 687-9690 text and voice

Similar Messages

Lightroom 4 resizing on export feature - using the "long edge" resize option - doesn't seem to work

In previous versions of Lightroom (prior to 4), when I used the resize feature while exporting, I often used the "long edge" value to resize.
Previously, when I selected 2500 as the "long edge" value, I would receive exported JPGs in a size of something like 2500x1650 or so for landscape shots and 1650x2500 for portrait shots.
With LR 4 (not sure if this started with the RCs or 4.0), using the same settings, I'm getting landscape shots that are 3700x2500 and portrait shots that are 1650x2500. This is acting more like I said I wanted a dimensional resize of _____ X 2500 instead of long edge of 2500.
I tried playing around with some of these settings, but nothing seems to give me the old behavior of 2500 on the long edge, even though that's what I've set it for.
Anyone else seen this type of issue?
I'm currently running LR 4 RC2, but also noticed this on RC1, but not sure of 4.0. I'm a Mac user, running the current version of Lion (10.7.3) on a 2010 Mac Pro.
Thanks,
Mark

With RC2 on Windows 7 (64 Bit) I get 2500x1667 for landscape and 1667x2500 for portrait, as expected. Seems to be an issue in the Mac version only.
A workaround might be to use "dimensions" instead and leave one of the fields empty (LR inserts "0" there, but one cannot enter "0" manually). I think this is equivalent to "long edge", but I am not 100% sure (edit: ok, I think I am nearly sure that it is).

Audio doesn't export with the video.

I am using Premiere CS4 to edit a group of clips together (a couple of them with audio.) I can hear the sound when I play them on the premiere file but not once it is exported.
My audio settings are: AAC, mono, 48khz, high, and the export audio checkbox turned on. I also tried with AAC version 1 and 2 but got the same results.
The video codec I'm using is H.264, if that matters at all, but I tried quicktime too and it didn't work either.
Any ideas what might be the problem or what am I missing?

I thought I recalled reading something when CS4 was first released that indicated that its codecs process files differently than in the past and therefore it would be more critical in CS4 to keep all of your presets and sources matching more closely. That in combination with Bill's comments got me thinking that there was probably something to it. It prompted me to run some quick :30 tests on new projects with the same issues.
I used both 48 & 44.1 project presets, 44.1 .mp3 and .wav source files, and 48 & 44.1 export presets. I also threw a video track on there for comparison sake. I expected the mixed source/presets to fail and the uniform source/presets to succeed. Wrong. End result was that everything exported as one would hope, error free and all without pre-rendering the timeline.
So, go figure. I guess I can only assume that there was some kind of hiccup/corruption in my original project file that prevented the audio from exporting like it should. I am never comfortable with that answer though. I need everything to make sense if I am going to sleep at night.
-gcs01

I am using Lightroom 5.7, 64 bit with Windows 7 Professional. For no apparent reason, I now get an error message when I export a photo, say a raw image to a JPG. However, the exported image seems to be OK. But now I notice that my LR directory of folders

I am using Lightroom 5.7, 64 bit with Windows 7 Professional. For no apparent reason, I now get an error message when I export a photo, say a raw image to a JPG. However, the exported image seems to be OK. But now I notice that my LR directory of folders in Library view does not show images correctly: If there is a folder with sub-folder(s), the folder will indicate 0 images, but the sub-folders show the proper number of images. What happened and is there a fix? I tried uninstalling Lightroom and re-installing, but problem persists.
Here is a screen shot of the error message:
Message was edited by: Joseph Costanza, Jr.

See here for a solution.

[JS][CS4]PDF Export With RegExp Doesn't Include First Zero-Please Help

This is a script we put together with the help of Jongware, Shonkyin and Kaysan a while back...
Here's the link to the original thread:
http://forums.adobe.com/thread/481958?tstart=0
( function() {
if(app.documents.length != 0){
var myFolder = app.activeDocument.filePath;
if(myFolder != null){
var myPageName, myFilePath, myFile;
var myDocument = app.activeDocument;
     //var myBaseName = myDocumentName + "_" ;
          //1. Update modified links, find and alert operator of missing links.
          var linksLog = updateLinks(myDocument, "");
     if (linksLog != "") {
          alert("Missing Links\n" + linksLog + "\nPlease resolve and try again.");
          return;
     function updateLinks(doc, log) {
          var myLinks = doc.links;
          for (var j = myLinks.length - 1; j >= 0; j--) {
               switch (myLinks[j].status) {
                    case LinkStatus.normal :; case LinkStatus.linkEmbedded : break; // nothing to do
                    case LinkStatus.linkOutOfDate : myLinks[j].update(); break; // update
                    case LinkStatus.linkMissing :
                         log = log + "Link '" + myLinks[j].name + "' is missing\n";
                    break
               } // end switch
          } // end for
          return log
     } // end updateLinks
var my_suffix = decodeURI(app.activeDocument.name).replace(/^(\d+).*/, '$1');
//my_suffix = Number(my_suffix);
if (typeof (my_suffix) != 'number')
my_suffix = Number(my_suffix);
for(var myCounter = 0; myCounter < myDocument.pages.length; myCounter++){
    if (myDocument.pages.item(myCounter).appliedSection.name != ""){
        myDocument.pages.item(myCounter).appliedSection.name = "";
myPageName = myDocument.pages.item(myCounter).name;
app.pdfExportPreferences.pageRange = myPageName;
myFilePath = myFolder + "/" + "MyTest_" + (my_suffix + myCounter) + ".pdf";
myFile = new File(myFilePath);
app.scriptPreferences.userInteractionLevel = UserInteractionLevels.neverInteract;
myDocument.exportFile(ExportFormat.pdfType, myFile, false, "[Press Quality]");
app.scriptPreferences.userInteractionLevel = UserInteractionLevels.interactWithAll;
    else{
        alert("No documents are open. Please open a document and try again.");
        exit();
alert("Finished exporting");
The problem is, I never considered pages 0 through 99. The script works perfect for 138-140 TEST 10_WORKER.indd. It creates PDFs named:
MyTest_138.pdf
MyTest_139.pd
MyTest_140.pdf
If the document name is 098-100 TEST 10_WORKER.indd, It creates PDFs named:
MyTest_98.pdf - should be MyTest_098.pdf
MyTest_99.pdf - should be MyTest_099.pdf
MyTest_100.pdf - This is perferct
And of course, the double 0s, 008-010 TEST 10_WORKER.indd
MyTest_8.pdf - should be MyTest_008.pdf
MyTest_9.pdf - should be MyTest_009.pdf
MyTest_10.pdf - should be MyTest_010.pdf
Why doesn't it use the first 0(s) in the name? 0 is a digit and every RegEx tester I've checked it with includes the zero.
Any assistance with getting this script to use the leading zero if there is one would be greatly appreciated.
Also, if there is a way to export each PDF from a multipage document which doesn't start with a number, it would be extremely helpful.
Thanks in advance
Danny

The zeros aren't there because they never were there. Your loop starts at 0 and that could be a page number. To pad your page numbers to three-digit numbers, replace this line:
myFilePath = myFolder + "/" + "MyTest_" + (my_suffix + myCounter) + ".pdf";
with this one:
myFilePath = myFolder + "/" + "MyTest_" + (my_suffix + pad(myCounter)) + ".pdf";
and add the following function somewhere at the end of your script:
function pad (n) {
    return ("00000"+n).slice(-3);
Peter

I have lightroom 4 and it doesn't work with d4s raw images? what can I do?

i have lightroom 4 and it doesn't work with d4s raw images? what can I do?

That model begin to be supported only in the very latest version of Lightroom, version 5.4. You will either need to upgrade Lightroom, or else use the latest version of the free Adobe DNG converter (version 8.4) to create digital negative copies of your raw images. Then you can import those DNG files into the Lightroom that you have now. The choice is yours.

How do Lightroom users manage sharing photos with family?

I'm just looking for some best practices about how to handle the workflow of sharing photos. Obviously the Lightroom user doesn't want family members to start messing around with the photos outside of Lightroom, and if the photos are not JPGs family members might not be able to view them anyway. One solution I can think of is to shoot all photos in JPG and in Camera Raw at the same time and save the JPGs to a folder available to everyone and only import the Camera Raw ones into Lightroom.

acresofgreen wrote:
... One solution I can think of is to shoot all photos in JPG and in Camera Raw at the same time and save the JPGs to a folder available to everyone and only import the Camera Raw ones into Lightroom. ....
This is a possible solution, but by doing this, family members will not be able to see changes you applied to the photos from within LR.
Another option would be to export your LR inventory (or parts of it) regularely to a specific folder, where others can access the JPEGs/TIFFs.
In LR 3, this can be somewhat automated by using the Publish Services to harddisk, where only changed photos are exported again a second or successive time.
A different approach could also be LRViewer, which lets you view images in a LR catalog from the previews without accessing the originals and without being able to change anything on them.
Beat Gossweiler
Switzerland

Lightroom 2.3 stops responding with keyword reorg (win 64bit - Vista)

I am trying to re-organise my keywords - making them more heirarchical, and renaming some to keep things tidy. In doing this I'm constantly getting LR2.3 stop responding.
Some background info:
Now I have a fair few images in my current catalog - 40,000 (approx), which is stored on a dedicated WD raptor drive - which is the fastest drive I have. My CR2 raw files are split between my local disk (images being worked on), and a NAS device (older images). The Catalog is 1.3MB in size.
I would consider the quantity of images in my catalog and my setup to be something resembling that of a standard professional configuration, and I would have hoped that by version 2.3, the Lightroom code would have been better optimised to deal with the handling of large quantity metadata updates. I can only presume that Adobe have a lot more functional design and code optimisation on their to-do list for future revisions of LR - at least I'm desperately hoping so! The problem appears to be this:
In my keyword heirarchy, if I rename a top level keyword to something new, then it has to amend all image records in the database (catalog) - most of the 40,000 in my case, and I appreciate that this takes time to do. What LR doesn't do whilst these updates are taking place, is give any user feedback - it simply seems to stop functioning until it's ready to hand back user control to the operating system. The thing is, as you haven't got a clue what's going on, you just assume that the application has crashed - and for all I know it may have as all I see if I try to interact with lightroom during the hang is my task bar reporting that the application is "(not responding)". Looking at the Resource Monitor in Vista there seems to be a large network load during the time of the hanging - now I can't understand this as LR should simply be updating the records in the catalog which is on a local drive, and not having a need to access my raw files, many of which are on a network drive. If this is the cause of the slow down then it shows that there is a desperate need for revision of the functionality of Metadata updates within LR.
I'm just hoping that Adobe take stock and for future revisions of LR, concentrate on performance issues, and amending of functionality or code structure to better tune the handling of data, rather than just adding more tools and functionality to the release which slows the app even further. I'm just hoping that LR will fulfil my needs at a professional level at some point in the near future as this app is core to the running of my business - and at the moment it's having an impact on my ability to do exactly that!
Anyone else with performance issues like this?
Thanks, Paul A

This has nothing to do with network access. I have been running the Winessentials Process Monitor app to try to figure out what's going on and I firmly believe this to be an issue with the Lightroom code. Once LR stops responding, the Lightroom process seems to go into an endless loop consuming memory on each iteration (I.e. a memory leak). Process Explorer shows every file handle and (as the directory of images I am displaying holds locally stored images only) none of the file handles are for network based files - all local files. This is what it's using in a nutshell:
The catalog file (2 handles on this)
The Catalog journal file
the thubnail cache (2 handles on this)
a whole load of internet explorer data files inc: history.ie5\index.dat; cookies\index.dat; Content.ie5\index.dat (no idea why it requires IE data access)
a couple of truetype fonts
a few temporary files in the user temp folder
loads of windows device files
access to the C:\Program FilesCommon Files\Adobe\Adobe Version Cue CS4\Client\4.0.1 directory (even though I don't have version cue installed to my knowledge! - certainly no service running for this)
Private Bytes is now sitting at 1.9GB (RAM being used by LR) and its continually on the up.
During the hang, LR is trying to spawn a new thread and Process Explorer is reporting this as "Thread Lightroom.exe (6008): 6040" then moments later <Error Opening Thread>, then it loops, each time more memory is taken up.
Since updating this message the memory usage by LR is now at 2GB!
This has completely stopped responding now!
**UPDATE** After an hour of being non-responsive, LR burst back to life. I just amended one of the keyword tag options again (this tag matches against 21,000 images), removing the 'export with keywords' option, clicked OK and it's stopped responding again!
Paul A

Lightroom Drop of quality exporting to jpeg

Good Evening,
I'm facing an issue with Lightroom 5.6. When I develop a photo and I export it to jpeg the result is far from the original Raw.
There is a loss of quality, particularly in term of noise reduction and sharpening. It seems that Lightroom doesn't take into consideration the changes made in these parameter.
I always export with all the metadata and sRGB Jpeg 80%, but I also tried 100% or Tiff and the result is always the same. When I export photos whitout changes in noise reduction and/or sharpening everything is ok.
I have many photos to be exported jpeg in order to share them with my family but if I touch the noise or the sharpening I'm lost.
Do you have any idea why is it happening?
I don't know if it is related, but it sometimes happens also when I open a photo fullscreen in the Library module. In order to show it properly I have to switch to fullscreen in the Develop module.
Thank you
Alessandro

Thank you both for your replies.
I'm sorry I think I don't understand what you are trying to explain to me.
When I work in Develop I make my changes and from time to time I switch to fullscreen to better check the results of my changes because the loupe view is too small (I use a laptop).
Sometimes it happens that if I go to Library and I watch the same picture fullscreen it is full of noise and/or pixels. It seems it happens after I work for more than one hour or so, in fact when I start working on Lightroom there are not differences in watching pictures fullscreen in Library or Develop modules.
Regarding the Jpeg Export issue, the “bad result” is visible in Lightroom or any photo viewer.
I have several jpeg pictures where the noise/sharpening issue is more visible because I used very high noise reduction values, but they are family pictures with children and I prefer not to put them in a public forum
Please follow the links below to see two samples related to difference in sharpening
https://www.dropbox.com/s/wc50noae6f8na0j/Compare%20Raw%20vs%20Jpeg.jpg
https://www.dropbox.com/s/onvvidl0hyligox/Raw%20vs%20Jpeg.jpg
The “select” is the Raw and the “candidate” is the Jpeg.
I guess it better to download them to appreciate the difference in sharpening.
Details:
Windows 8.1
Nikon d7000
First image:
ISO 100
Sharpening 150, Noise Reduction untouched
Export file settings: Jpeg, quality 80, Color sRGB, Limit file size unchecked.
Image sizing: Resize to fit unchecked
Output sharpening unchecked
Second image:
ISO 1600
Sharpening 60, Noise Reduction Luminance 41
Export file settings: Jpeg, quality 80, Color sRGB, Limit file size unchecked.
Image sizing: Resize to fit unchecked
Output sharpening unchecked

Error message ''Disk Full' when trying to export with CS6, works fine in 5.5

I get an error message when I try to export media in Premiere CS6 that I don't have in CS5.5
I use export media for a AVCHD 60fps sequence with a few photoshop images on top of the main track. In the export settings I choose ''match sequence settings'' which gives me a .mpeg I- frame, 1920 x 1080 P, 60fps, quality 50, and a I tick the ''use maximum render quality'' check box at the bottom.
It used to work fine but now I get a message: Disk Full where there is 1.5 TB free on the disk?
I have the exact same sequence made in Premiere Pro CS 5.5 and it exports fine.
It started to act weird after I used the queue for the first time and it went to the CS6 encoder.
Since I used that once and it gave me that message for the first time, even when I try to do the same thing directly in Premiere CS6 , I always get the same error message.
Question 2, is there a place to change the settings from 50 to 100 for the quality of this export profile?
By the way I can export with other profiles without problems but this setting is the only one that I've seen that lets me keep my 60 frames per second in the export
process. (Example: I can export this sequence in the H.264, 1920 x 1080, 30fps, high quality preset, using the maximum render quality in CS6)

Hi Guys,
Thanks for the input but if you read my message correctly and until the end I already can export to other settings and I want an answer to this problem. There's no logical explanation to why this suddenly wouldn't work with the same sequence that it used to do fine with and that CS 5.5 handles fine.
As I said earlier this is the only setting that lets me export my sequence with the 60 fps, that I know of, for further and easier manipulation. As my main camera provides me with these 60 fps I'd really like to be able to have them left in that transition phase and, no, I'm not gonna give up until I know, really, what's going on and solve that problem. If this is a bug it needs to be fixed, if not I want to know what's happening.
Also there's no answer to my question 2: Question 2, is there a place to change the settings from 50 to 100 for the quality of this export profile?
So for you experts out there the question is still hanging.

I want to cut and paste iCal entries on iPad. Have seen a number of questions raised but no definitive answer - is it possible or not? (I use Bento but that doesn't sync with ICal now so can use that solution)

I want to cut and paste iCal entries on iPad. Have seen a number of questions raised but no definitive answer - is it possible or not?
(I use Bento but that doesn't sync with ICal now so can use that solution)
Hope to hear helpful news soon....
C

No, the camera connection kit only supports the copying of photos and videos to the Photos app, it doesn't support copying content off the iPad. For your second camera instead of the SD reader part of the kit, does the iPad to camera cable not work with it for direct transfer to the iPad ?
For Lightroom and Nikon software again no - you can only install apps that are available in the iTunes app store on your computer and the App Store app on the iPad, 'normal' PC and Mac (OS X) software are not compatible with the iPad (iOS). There are some apps that perform fairly basic editing functions that are available in the store, but nothing as sophisticated as, for example, Lightroom.

Media Encoder CS6 doesn't export any of the common formats like .MOV, .AVI, .AIFF .WAV, etc.

When I queue exports from Premiere CS6, Media Encoder totally ignores any custom export settings, and chooses some completely different system defined default settings, which I did not choose in Premiere. In previous versions Premiere would always pass the encoding settings to the Media Encoder.
Update: When I tried to import the custom settings into Adobe Media Encoder, I got an error message: "Preset could not be imported. No exporter found for this preset." Then I've realized, that AEM doesn't even have a QuickTime export format!!! Actually it offers only 4 export formats: H.264 (MP4), FLV, F4V, and MP3. Then, when I queue an export with Premiere with one of those 4 formats, then AEM would accept it. Anything else - it just wouldn't work!!! So wait - am I missing something, or I literally cannot queue any other common format exports with AEM??? I need to work with MOV, AVI, AIFF, WAV etc. files, which all aren't accepted by the Media Encoder... Or am I missing something???
This is ridiculous. I am becoming quite fed up with Premiere CS6 bundle - in 20 minutes I have found already 4 diferent features, that worked in previous versions, and work no more in CS6
I don't know how it worked in CS5.5 - anybody?

I have found the solution in another thread!!! It's here: http://forums.adobe.com/message/4503096
1. Open this file:
On MAC: /Applications/Adobe Media Encoder CS6/Adobe Media Encoder CS6.app/Contents/Resources/txt/AddExporterList.txt
On PC: C:\Program Files\Adobe\Adobe Media Encoder CS6\txt\AddExporterList.txt
2. Back it up to some other location.
3. Then delete everything from it and paste this:
# MediaCore Plugins
# AME Plugins
AudioWriter
WinMediaWriter
# AME Plugin Formats
MPEG4
H.264 Blu-ray
4. Save it, and relaunch Media Encoder - voila! It worked for me and many others.

Media Encoder CS4 doesn't work with Premiere (pic related)

Oh hai!
I just got Adobe Master Collection CS4 and my Media Encoder doesn't work with Premiere CS4. When I try to export the file, Encoder starts normally. Then I click "Start queue" and Encoder starts loading. Loading takes almost five minutes, which is a long time, because my project is very simple. After that nothing happens, just a warning sign appears. When I click it open, some kind of log file open and it says:
Encoding failed
Could not read from the source. Please check if it has moved or been deleted.
And I didn't deleted anything. So what does that mean? Why that "Source Name's" path is different than my project files path? Can this problem relate that somehow?
I have also another problem with Premiere CS4, maybe there's a link between these two problems. I can't get Premiere projects linked to open in Premiere CS4. When I right-click the project icon, and click “Open with…”, I can't find Premiere from the list. When I click "Browse", I can find Premiere.exe from my computer, but if i doubel-clicked it, nothing happens. It won't appear to the list or anywhere else. Or have I missed something? So now the project files are linked to open in After Effects. Of course I can open projects from Premiere, but how do I get them open straight from file?
I have long experience using Adobe Premiere and this is the first time I got this kind of problems. I have also downloaded new updates for Premiere and Encoder, this didn't help. Does that matter, that I didn't installed Premiere in C-drive? However it's in my computers internal drive, I have divided my hard drive for five parts, one part contains all of my softwares. My scratch disks are in different hard drive (external), does that matter? I tried different location, but that didn't help.
Please help, I can't do any video editing, because of this problem. And sorry for my english, ask if you didn't understand something. =)

Hello, this is terrible problem, which i found in CS 6 softwares ...
solution i found only working, is uninstall and reinstall full package.. but it is not all,
you need to do BRAND NEW admin account in windows, and install it there.
that means, i could not export after repair from encoder in my original account never more (!!)   .. this is really terrible way how to repair this issue, because :
1.by reinstalling of software, client WASTE HIS TIME
2.by necessity to begin work in another windows profile you again WASTE YOUR TIME because of learning and migrating all other profile modifications, which i see really unaccpetable. Adobe means, this solution of repair is ok, and they did not do till today any steps of creating some "clever" solution.
I ask everybody, who will meet this issue in future, guys, please, complain about this situation, give "BUG Report" to them, and write "feature request" to them , in the way of creating some repair tool, which check actual "broken" connections between encoder and premiere, which refuses to "take material" from it and encode, and REPAIR it automatically..
   I am not IT, but ..does it seems so hard to create this ? Adobe IT developers should know their systems, and should create such utility tool really easy.
History of this problem and detailed description, HOW i did "repair" this. With wasting of app 2,5 days of my working time :
1. after repairing "error 5" problem , i solved it by reinstalling the suite from the new admin user profile (profile B) .
I continued my work on my normal working windows profile . (profile A)
Every cooperation (AE+Pr, export media via "queue" to Encoder) was working fine . . .
2. suddenly it stop working (without knowing any possible reason - i did not do installations )
and showed in error export log file :
"Could not read from the source. Please check if it has moved or been deleted."
3.repair via procedure(procedure "a"):
i did this procedure on the profile B (profile from last time installation of repairing problem error 5)
I did these steps :
a-uninstall master coll suite
b-i used Adobe cleaner tool (remove ALL)
c-removed raw directories in locations
•C:\Program Files\Adobe
•C:\Program Files(x86)\Adobe
•C:\Program Files\Common Files\Adobe
•C:\Program Files(x86)\Common Files\Adobe
•C:\ProgramData\Adobe
d-removed these links from registry file
•HKEY_LOCAL_MACHINE\SOFTWARE\Adobe
•HKEY_CURRENT_USER\Software\Adobe
•HKEY_LOCAL_MACH INE\SOFTWARE\Wow6432Node\Adobe
•HKEY_CURRENT_USER \Software\Wow6432Node\Adobe
e-restarted the PC
f- newly installed the Master Coll CS6
g-update the software
result of repair of "3" : problem still exists
4.Ok i find out after coordination with support, it should have been created ANOTHER NEW admin account.
4a:so i did the same procedure (uninstalling) in profile B
4b: and then i created brand new admin profile (profile C)for INSTALLATION of software
4c: restarted the pc (and did not updated it yet)
result :
==exporting of any sequence/raw/AE link video material from premiere via "queue" (Encoder) (profile C) : export WORKS
==exporting of any sequence/raw/AE link video material from premiere via "queue" (Encoder) (profile B) : export WORKS
==exporting of any sequence/raw/AE link video material from premiere via "queue" (Encoder) (profile A) : export DOES NOT WORK ! ! !
(in profile A, is possible to export some raw video material in encoder which is imported to it via "drag and drop)
problem i see:, i have my basic profile A, which i am interested to work, because of all my directory modifications are in there..
this issue should be some "broken" connections between encoder and premiere, which refuses to "take material" from it and encode.
what i expect :
to get from Adobe some repair tool, which automatically checks these connections and repair if necessary, without necessity of founding the new profile and reinstallation of whole software.. this is madness !
what i do NOT expect from Adobe:
to get from Adobe advice of kind : you have to reinstall full software in new admin profile. sorry , we do not know the solution, because we do not know, how do behave our software.

Movie in Keynote doesn't export properly for QuickTime

Hello all. I really hope someone can help with this. I've used the discussions before with great success so THANK YOU all for sharing your expertise.
I've got a keynote presentation that for the most part exports perfectly on QuickTime. The only part that doesn't export right are the 2 videos I've got on the presentation. I set the timing with the inspectors for it to start automatically and even added a song to play along with the presentation. But when I export it, there is about an extra minute and 15 seconds added to the whole video and I've got the presentation timed perfectly with keynote and the song. I've got iWork '09 and QT 10.0. Not pro just player.
I've played with the custom settings to no avail. Any way to get the videos to export exactly to their lengths?
Cheers

I don't know if this is the answer you're looking for but I'll share my experience. Like you, I have three videos in my presentation. Once I exported it as a QT movie, the delays that I built in with the Inspector to allow the movie to play before the next slide transition, played AFTER the video ran. I went back and just put in a 1.5 second delay in and the videos run fine. I'm guessing that QT sees the video and allows it to play and THEN looks at the Delay setting.
Now if someone can just tell me how to get the audio soundtrack to shut down during my three videos but play during the rest of the presentation...

Clips exported with Media Encoder from AE are choppy (CS6)

Hi!
I'm using Media Encoder (6.0.3.1) to export clips from AE (11.0.4.2) so that I can work with them in PPro (6.0.5).
In Media Encoder I go to add AE composition and I've tried the YouTube HD 1080p 25 and the Broadcast HD 1080p 25 presets (the latter creates a much bigger file but I don't think the file size is the issue - for example, the biggest clip of approx. 1 mintute is 276MB).
The curious thing is that most of the clips that are exported are fine, i.e. they play back fine - the problem is that some of the clips go slow or choppy towards the end of the clip. So the last couple of seconds will be choppy. It basically looks like the frame rate isn't quite right.
Once exported from Media Encoder, I import them into PPro to do some more work - the problem with the clips is apparent when I play the original file in VLC (for example) or in PPro. So it seems like the problem occurs during the export from AE. When I export the video containing the AE clips from PPro the problem is obviously still there (wishful thinking on my part). I use AE just for keying and making some basic titles, nothing massively complex.
I had some problems with RAM preview in AE before, in other words, it wasn't playing the clips back in realtime and the exported clips with the problem look exactly like that (i.e. looks like the frame rate isn't right). I deactivated Enable Disk Cache in AE (Multiprocessing was already deactivated) and now I can play back clips ok in AE using RAM preview - even the ones that go choppy towards the end when they are exported with Media Encoder play back fine in AE.
Could Media Encoder be going back to some previous render files saved somewhere on my system and could that cause some of the exported clips to go choppy?
I'm new to Adobe so I'm just guessing here and I don't want to go about and delete stuff that might not have anything to do with this problem. As I've adopted the computer I'm working on from my predecessor and it's had several users since, the system is a bit of a mess and there are files all over the place. Empting the Disk Cache doesn't actually delete anything for example.
I'm really stuck here because I can't finish the projects I started working on with AE.... I would appreciate someone's input!
Many thanks in advance!
My system specs:
Intel Core i7-3930K, 3.20GHz, 16GB RAM, 64-bit operating system, GeForce GTX 680, Windows 7, Creative Suite CS6
Before using Media Encoder to export clips from AE I was just relying on Dynamic Link between AE and PPro by the way and that made all of the clips choppy for the whole duration (this was before I solved the RAM preview problem and I haven't checked if a working RAM preview would make a difference to dynamic link). So Media Encoder nearly solved the problem. I posted this original problem on creativecow (http://forums.creativecow.net/thread/2/1045810) but no one has gotten back to me about the new issue unfortunately.

Thanks for your reply!
I tried using Quicktime with PNG and it created a big file (1.18GB for a 1 minute long clip) that doesn't play back nicely in PPro unfortunately. But I then tried rendering the clip using a lossy format, H.264, in AE and it's playing back ok in PPro! I will just do that for the rest of the clips and hope that this is finally resolved. Many thanks for the tip!
Out of curisoty, do you know what might be causing the problem when I use Media Encoder?

Lightroom 5 doesn't export with a maximum long edge as instructed

Similar Messages

Maybe you are looking for