Annoying bug when exporting

I get a problem when i try to export using quick time conversion and then suddenly switch to another app like mail for example. When i go back to final cut express i cant come any further. the dialog box shows cancel or save, neither of which is effective, meaning i have to force quit the app losing any changes i have made. has anyone else experienced this??

It happens when you are setting up the export conditions. It occurred the first time when i was referencing a websites recommended compression settings as i could not remember them by heart. Try it for yourself.
When you click export, choose Quick time conversion
Then options and finally settings
then open a webpage or another app
Everything is fine until you go to click save - it just wont budge! and clicking cancel doesnt help either.
I regularly save my projects and i realised just now that i can do a restore after force quitting the app, but all the same its flippin annoying.
Thanks for your quick replies.

Similar Messages

Premiere CC 2014 "Match Source" bug when exporting multiple clips

Getting a strange bug when trying to batch export.
The source clips are 4K MP4s. When exporting individually I use the Match Source button in the export dialogue and it correctly matches to the 4K frame size when sending to queue in Media Encoder.
If I select multiple clips and batch export them, selecting "Match Source" they come out as NTSC DV 29fps 720 x 480. The only way to work around this is to manually enter the frame values in Media Encoder after queuing.
Anyone come across this? Anyone at Adobe aware?
System Specs:
Mid 2010 Mac Pro 2 x 2.9GHz 6 Core Xeon
32GB RAM
nVidia GTX 680
240GB SSD boot drive
2TB internal cache drive
Adobe Premiere 8.1.0 (81) Build
OS 10.8.5

Do you have a utility to check your computer temperatures?
You MAY have a hardware problem, since video editing puts a LOT of stress on all components... below is not exactly the same, but worth reading
BSOD shutdowns http://forums.adobe.com/thread/1427408?tstart=0
http://blogs.adobe.com/kevinmonahan/2014/01/13/computer-shuts-down-with-premiere-pro-or-af ter-effects/

Annoying bug when opening a folder as "CoverFlow"

CoverFlow is a very great feature when working with videos and photos without opening Aperture nor FinalCut.
But when I was organizing my photo files, I've discovered this annoying bug, where if you open a folder as CoverFlow, and then you delete some files from the list (bad pictures) the CoverFlow part won't update, so it will get out of sync with the list of files.
So after deleting any files, you must close and re-open the finder window to get it updated. Otherwise you will think you are deleting the right file, but it's a totally different file then the selected in the list.
I've tested on different ways, just to make sure, and it happens every time, easy to duplicate.
Please fix it!

Apple doesn’t routinely monitor the discussions.
Send Apple feedback. They won't answer, but at least will know there is a problem. If enough people send feedback, it may get the problem solved sooner.
Feedback

CS5: Bug when exporting directly from PPro with hardware MPE?

For the record, I'm using:
A GTX-480 (unsupported)
The hardware MPE-enabling hack (unsupported)
The latest version of the nVidia drivers (257.whatever)
I discovered an issue, of sorts, when exporting directly from Premiere CS5, versus using the "Queue" option to send to AME. I was exporting from an NTSC DV Standard sequence to a 320x240 H.264, in which I had enable cropping and trimmed a bit off the sides and top and bottom of the source; the Output tab was summarily set to "Scale to Fit". With hardware MPE enabled in the Project Settings, the export would be the proper final dimensions (320x240), but any area that was cropped off was instead padded with black. The actual video content was then squeezed and malformed into the area not occupied by the black bars.
I found that, if I disabled hardware MPE or sent the export through AME by use of the Queue button (instead of Export), then the export was performed properly--the video was cropped correctly and then the video stretched to the borders of the exported video, maintaining the desired aspect ratio.
As I mentioned at the outset, I'm breaking a couple rules and perhaps tempting fate with others, but before I go about rolling back my drivers and the like, has anyone noticed a similar issue?
ADDENDUM: By the way, the export doesn't need to come from a sequence. If I load up a source clip into the Source Monitor, and export from there using the process outlined above, I get the same issue. This would seem to indicate, to me, that this is due to some incompatibility with my card, its driver and hardware MPE...

Did he demo renders or exports?
About 11 minutes in, he [Dave] demos accelerated H.264 renders.
Harm Millaard wrote:
AFAIK MPE only works with renders, not with encoding.
Well, he did both, actually--but the quote above is a typo on my part. I meant to say "exports" or "encodes." The last couple minutes of the aforementioned demo video are dedicated to exporting a sequence directly from Premiere, and having the benefit of hardware MPE. That's where I'm getting the issue I've outlined above; with hardware MPE enabled, and using the "Export" versus AME "Queue" button/function, I get the strange black outline. With software MPE or through AME, all is well.

Strange bug when exporting a spreadsheet to a pdf

I am using Numbers 3.5 on a brand new Mac with Yosemite and I think that I have found a bug. When I export a spreadsheet into either a pdf or excel file it works fine if I save it to my default location (Documents). But if I change to a subfolder within Documents before I do the export I get an error message that says "The file name.pdf doesn't exist!" (Where name is the filename that I have specified for the export.) It's as if Numbers is trying to open an existing file instead of exporting to make a new one. Any ideas on this?
Thank you,
Paul H.

I will reply to my own question. I spent some time with an Apple tech support person and at first I stumped him. Eventually he got it to work and he thinks that the key was to get my computer to reindex my file structure. He did that by creating another folder inside Downloads, exported to it OK, and then was able to export to my previously existing subfolders. Thank you Apple!

Bug when exporting large images

I found this bug in Flash 8, so I just downloaded CS5.5 trial and I see the same problem.
When I increase the image export resolution to get a larger image, at one point the lower section of the image became white (the image has the appropriate size but the content is not rendered in the lower section). As bigger is the image, larger is the white fraction. The amount of useful pixels always stay around 10 or 13 megapixels. Here some examples:
Original image was 3375x6710 pixels in the left one and 2625x5219 en the right one. Any idea to solve this?? Can anyone reproduce this problem?

That article is regarding the size of the bitmaps you can put INSIDE the project, and the issue I'm experiencing is regarding the size of the output when you use the "Export image" function.
Actually I got the same problem even if I delete all bitmaps from the stage and try to export only the vector features (lines, text, etc...).
I can't see clearly how the limit explained in that article could be related to a limit of exported images.
As example, the following image shows the same issue, but this time of a project with only vector data, no bitmaps at all, you can see how the rendering is truncated.

Column with bug when exporting photos to html

When I select, say, 20 photos and choose file/ export to html document, the default number of
photos (Columns) per row is three. If I change it to five, the html document keeps a 33% column width
instead of changing it to 20%. This did not happen in an my older version. Is this a bug that could be corrected in the next update?
My actual version is iphoto- '08 7.1.4 (371)

Welcome to the Apple Discussions. Change the thumbnail size and that should get you to a narrower column. I find the build in HTML page builder to be clumsy to use with the thumbnail size always reverting back to the 240 size. Changing the thumbnail size will let you adjust the column width.
Have you tired the free iPhoto plugins, Flash Album Exporter or SimpleViewer which create flash based galleries and slideshows? They are a lot nicer than the build in web page builder in iPhoto. Or iWeb?
TIP: For insurance against the iPhoto database corruption that many users have experienced I recommend making a backup copy of the Library6.iPhoto (iPhoto.Library for iPhoto 5 and earlier) database file and keep it current. If problems crop up where iPhoto suddenly can't see any photos or thinks there are no photos in the library, replacing the working Library6.iPhoto file with the backup will often get the library back. By keeping it current I mean backup after each import and/or any serious editing or work on books, slideshows, calendars, cards, etc. That insures that if a problem pops up and you do need to replace the database file, you'll retain all those efforts. It doesn't take long to make the backup and it's good insurance.
I've created an Automator workflow application (requires Tiger or later), iPhoto dB File Backup, that will copy the selected Library6.iPhoto file from your iPhoto Library folder to the Pictures folder, replacing any previous version of it. It's compatible with iPhoto 6 and 7 libraries and Tiger and Leopard. Just put the application in the Dock and click on it whenever you want to backup the dB file. iPhoto does not have to be closed to run the application, just idle. You can download it at Toad's Cellar. Be sure to read the Read Me pdf file.
Note: There's now an Automator backup application for iPhoto 5 that will work with Tiger or Leopard.

Two annoying bugs when exiting guided acces via Touch ID

When exiting guided access on my iPad Air 2 (iOS 8.1.3) via Touch ID, I encounter the following strange behavior:
1. the disabled areas I defined in the guided access mode (the "greyed-out" areas where touch input is not accepted) remain as grey areas on the screen, even when entering other apps or the home screen after having left guided access mode via Touch ID. However, though still shown on the screen, said grey areas are not active any more, i.e. touch input is accepted though being greyed-out. In short, guided access mode is indeed disabled via Touch ID as expected, but the previously disabled areas remain visible on the screen, which is quite annoying when, e.g., watching movies etc. The left-overs disappear only when starting guided access mode again, and exiting it via triple-clicking the home button and entering the passcode (i.e. NOT via Touch ID)
2. When starting guided access mode again in the same app as before, the previously defined disabled areas are not restored. I.e. every time I start guided mode, I have to define for each app its disabled areas over and over again, which is very annoying in daily use. Again, this forgetfulness occurs only when having left guided access mode via Touch ID before; having left via triple-clicking the home button and entering the passcode saves the set disabled areas such that they are restored when re-entering guided access mode.
Therefore, exiting guided access via Touch ID as currently implemented in iOS 8.1.3 does not make any sense at all, since the greyed out areas left on the screen are quite annoying, as well as re-defining the disabled areas over and over again is not quite useful.
Does anybody also observe this annoying behavior?

Update to iOS 8.2 did not improve the situation - exiting guided access mode via Touch ID still causes both issues...

Bug when exporting table data

The exported columns name are still ordered as the table definition and the data are ordered as the table is diplayed in the explorer. If you change the order of the columns in the explorer and export the data in a csv file by example, the data are putted in a wrong column due to the labeling mismatch.
Table
+column a
+column b
Table data in the explorer
+column b
+column a
Data exported in the csv file
+Title column a
+data column b
+Title column b
+data column a

Sure enough - just tested this with Export > Insert and the column headings are in the displayed order but the data is in the db order. I will log a bug now.
-- Sharon

Non-functioning booksmarks when exporting with Acrobat X

Using InDesign CS5, I export my book documents to PDF Print and include bookmarks and hyperlinks. This has been working just fine using Acrobat Standard, and the person reading the document can navigate through the pages using either the document's Table of Contents or the Adobe bookmarks panel. I recently upgraded to Acrobat Pro X, and now this function no longer works properly. When you click on any Table of Contents bookmark, they all take you to the first page of the document. In addition, the bookmarks in the Adobe bookmark panel do not work at all. When I look at the bookmark properties, they all point to p0. It is possible to manually reset the properties of the Adobe panel bookmarks, but not the TOC, but this is time consuming and doesn't solve the problem. Besides removing Acrobat Pro X from my computer, has anyone found another solution for this problem?

I believe this is a known bug when exporting Books from CS5, and that it is not restricted to Acrobat X.
The only workaround I know is to combine the files into one document.

6300 - bug when exiting sms editor

I've got a Nokia 6300, firmware v5.00, on Orange UK.
I've found an annoying bug when replying to text messages. This is what happens:
- press 'reply'
- compose message and press 'send'
- press 'exit'
- rather than exiting, the phone goes to the 'reply as' screen, giving me the choice of replying as a text or an MMS.
- if I can press 'back', then the right soft key is now 'exit' and it works properly.
Any ideas how to fix this?

No, but there is a newer version of the 6300 firmware (v.5.5). Perhaps that would help.
Currently using 6300 & 6233 (backup)

Bug: Can't view photos in a slide when Exporting to PDF viewing files on XP

Hi,
I'm completely new to the discussion forum.
So hope this hasn't been covered, but the bug is there none the less.
When Exporting a Keynote 09 slide or slides that use some of the
new Layout themes(Kyoto style etc), nothing shows up when the
PDF is opened on Windows XP machines.
I have tried it on several machines at work and at schools,
and cant get photos or text to show up.
This never happened in 08, as i often have to use PDF to do presentations
at schools that dont have powerpoint no their pcs. PDF exporting
is really important in my daily work with keynote.
I really hope there is a fix or that Apple can release a fix
for this bug, as I would love to use the new layout themes
in presenting.
Strangely older themes have no problem opening and show all text and
photos as they should when exported using keynote 09 to pdf...
so i assume its an issue with the newer themes only ;(
wierd.. (cries)
Thanks in advance to anyone that can help me here. Apple!!! I luv you
but this issue is annoying the heck out of me.
D

Wow, thank you so much for quick replies!
Ok ill try and explain more.
1) I used to the Export feature (now I used SHARE > Export > choose PDF > save to desktop... view it.. its all good)
2) I then save the file onto a flash drive and put in a XP OS run PC
3) The slide background only shows up.. i.e. no content just the template itself
4) This only happens to the newer templates.
5) This happens when dragging a picture into the preset template picture boxes,
the picture just doesnt show up on the pc
6) havent checked file sizes, because i could do this process on keynote 08.. so i assumed its a BUG and not the fault of mine
7) Most importantly, i can do the same process and it works with the keynote 08
backgrounds and themes within 09.. but i cant get my PDFs on an XP to show when using the newer themes... just shows blank themes.. even for Kyoto theme, the tea pot picture isnt there.. its just the background
i am thinking of taking my mac into a mac store,
but im almost certain this is a bug.
to view the PDF on both my macbook and on XP i just double click
whats on the desktop and it usually shows.. but since buying 09,
as i said before, i can only get this to work for slides that use
the old 2008 keynote templates ;( ;(
i have not tried exporting using the print feature.. i will give that a shot today. but its so wierd that it shows up for some templates and not for others.
thanks again for your kind help. i really appreciate the time and effort
you are all putting in in helping.
D

Is there a bug or problem with increased noise when exporting pictures out of Lightroom 4?

Is there a bug or problem with increased noise when exporting pictures out of Lightroom 4?

As you are asking about it, looks like you do see a problem. So if googling does not provide a solution, you should describe the issue in detail so we can try to help out.

LR 3.6 exported images can't be read by other application (annoying BUG!)

Hi,
I am working with M.Objects which is a very neat and comfortable picture show application.
Images that are exported under LR 3.6 can't be imported there. M.Objects is a Windows application.
So I threw 3.6 into trash, and installed LR 3.5 again.
Now it works again properly!!
Please, remove this annoying bug!
Cheers, Hans

Hi, I am sorry for posting in the wrong user-forum!
But I try to explain my problem: I'm working with LR 3.6 on an iMac (OSX 10.6.8). My picture files are on an iOmega hard drive. After LR-work the images are exported to a FAT-formatted LaCie hard drive. My slide/picture show application only runs on a Windows 7 partition on my iMac. So I copy the images from the LaCie hard drive to the Windows pc.
With 3.5 everything worked really fine. But with 3.6 my show application M.Objects (http://www.mobjects.de/) says „can't read the files“. The Windows preview app. can open the image files.
But now I've found out that I can export the images to a Vosonic hard drive, and M.Objects can read and import my images. So my problem is solved. I don't know why on two different FAT hard drives files are stored in ways that on one hand it works but doesn't on the other hand.
Thank you,
Hans

Serious show-stopping bugs in Premiere Pro when exporting

OK, so first of all, I get that making a video editor is not an easy task. In fact, it's a nightmarish task. One I would never even attempt. However, Premiere Pro CS6 has been worked on since 1992 or so, by one of the biggest and wealthiest software companies in the world, with well paid experts on this very thing. It's supposed to be professional-grade, but bugs like this makes me wonder if it's some sort of a joke. It simply does not do what you tell it to when exporting. I come back to this problem (and similar ones) again and again. It's not me doing anything wrong. It's not me having misunderstood something. It's serious bugs in this software. There is no other explanation. Please look at these images:
To the left: the video file as it appears in Premiere Pro.
To the right: the video file as it appears once exported using the "Match Sequence Settings" option.
What you cannot see well in the images is that the quality is also significantly lower, and it stutters in an insane fashion.
It does NOT match the sequence settings. I repeat: it does NOT match.
I know some people on this board are eager to reply quickly, but I would rather have you think this over before. It gets very tiresome to have people shout out the first (incorrect) thought that pops up in their minds. Thank you for respecting that. Please only respond if you know what is going on for sure.

The "Match Sequence Settings" settings forces Pr to use rendered preview files as a source, instead of the actual source video. If no rendered preview files are present, it defaults the export settings to the same settings that are used in the sequence to generate the preview files. Check your sequence settings - you'll see what export settings Pr is using when MSS is selected. Most likely, it's not what you want or expect.
I've been told that the Match Sequence Settings check box is working as designed. I personally think it's confusing and misleading.
Jeff

Annoying bug when exporting

Similar Messages

Maybe you are looking for