MAJOR EDL Export BUG in 8.2!

I just upgraded to version 8.2 and now there is a major bug when exporting EDLs with audio clips!   EDLs (cmx3600 format) should only export Timecode In/Out for Source & Record.   The latest 8.2 version is now incorrectly outputting SAMPLE FORMAT for EDLS for any audio clips!  This is a major bug and potentially show-stopping.
What 8.2 is exporting:
What it used to (and should continue to) export before 8.2:

with my PP 8.2.0 (65) Build, I get the same error with edl WAV audio clips until I 'link' video clip with audio clip below on the timeline
I believe after linking the video clip to the audio clip (below on the timeline), then exporting the edl, the timecode format displays properly
However, my edl export ability still needs work, because I would think my video timecode needs to match my audio timecode (for linked clips) so I am still working on importing the edl into Speedgrade and 'hearing' the audio
I was getting the same error audio text file as AjentJJ30, until I 'linked' video with audio,
so far my edl text file appears as below
TITLE: edl with wav link
FCM: DROP FRAME
001  AX       V     C        00:00:00:00 00:00:24:23 00:00:00:00 00:00:24:23
* FROM CLIP NAME: bmpcc_1_2015-02-05_0951_C0005_[000000-002420].mxf
002  AX       AA    C        01:03:06:05 01:03:30:28 00:00:00:00 00:00:24:23
* FROM CLIP NAME: full shoot
003  AX       V     C        00:00:24:23 00:00:41:22 00:00:24:23 00:00:41:22
* FROM CLIP NAME: bmpcc_1_2015-02-05_0955_C0001_[000000-004258].mxf
004  AX       AA    C        01:06:32:22 01:06:49:21 00:00:24:23 00:00:41:22
* FROM CLIP NAME: full shoot
005  AX       V     C        00:00:41:22 00:01:00:10 00:00:41:22 00:01:00:12
* FROM CLIP NAME: bmpcc_1_2015-02-05_0958_C0003_[000000-004444].mxf
006  AX       AA    C        01:09:17:29 01:09:36:17 00:00:41:22 00:01:00:12
* FROM CLIP NAME: full shoot
EDIT: as you can see my WAV file does not show the proper clip name, as well as not displaying the .wav file extension.
I chase after the edl displaying proper WAV data, but could not achieve any solid results. My dng video clips from the bmpcc have wav files, normally they do not import into Speedgrade with the dng sequence, so using the video clips to test the edl process isn't very helpful.
I can not get results to support having the WAV edl data working when importing into SpeedGrade.
Sorry to think otherwise.

Similar Messages

  • Indesign CS6 epub export bug

    I am using Indesign CS6 to export a book to epub. Having problems with automatic numbers and bullets as well as spacing issues; however, I've made some adjustments and am getting a pretty decent epub. Here's the issue: When I convert my epub to Mobi using Calibre, I get double bullets and double numbers in my lists. I used this same process to create a Mobi file a few months ago in Indesign 5.5 with no problem. So I took one of my CS6 files, exported it to IDML, opened it in CS5.5 and exported to ePub. I then took that epub and converted it to Mobi using Calibre. No double bullets or numbers. So the issue is coming from Indesign CS6.
    Anyone else had this issue. Any other ideas on how to get a clean Mobi file from CS6?

    Thanks a million.
    Re: Indesign CS6 epub export bug
    created by Steve Werner in InDesign - View the full discussion
    lotuscott,
    You should get the 8.0.1 update for InDesign CS6. It fixes several EPUB bugs including the "space before" problem and the "epub-ruby" (which is I believed intended for Japanese language.
    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 http://forums.adobe.com/message/4773256#4773256
    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: http://forums.adobe.com/message/4773256#4773256
    To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4773256#4773256. In the Actions box on the right, click the Stop Email Notifications link.
    Start a new discussion in InDesign by email or at Adobe Community
    For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

  • MAJOR Cover Art bugs in iTunes 7.x.x

    Here are some interesting observations in discovering MAJOR Cover Art bugs in iTunes 7.x.x
    1. Importing CDs
    If you import a CD, you must wait for complete import to finish in hopes that all songs will populate successfully with cover art. Even here, success is random.
    If you request cover art during the import, there are mixed results.
    iTunes should be smart enough to detect if any album exists with partial cover art in the library database, then those tracks with missing cover art will be automatically detected and updated.
    2. Missing Cover Art
    This occurs on 2 levels:
    a. iTunes Store may just not have cover art for some (older) albums
    b. iTunes Store does find the cover art, but it is not applied to *all tracks* on the album
    The workarounds bring mixed results.
    I have resorted to the "Get Info" approach and pasted cover art to random album tracks where cover art was only partly applied by iTunes.
    In other cases, I scanned in the CD cover and applied it to albums where iTunes found no cover art. I assumed this would be a one-time fix as I expected some minimal tweaking would be involved in managing cover art.
    No such luck! Here is why iTunes cover art represents a MAJOR bug in version 7.x.x
    Day 1: I spend many hours tweaking and fine-tuning the cover art, assuming iTunes will "save" all my work. I browse different albums/tracks and everything looks great!
    Day 2: Looks like iTunes only "saved" some of this effort. Sure enough, certain complete albums and random tracks from other albums now show NO cover art! How frustrating!
    * * * Here is what is MORE DISTURBING about this Cover Art bug! * * *
    I resort to thinking about more workarounds, and here are the results:
    Hmmmm. Looks like if I paste in the Cover Art twice on certain album tracks, the Cover Art is now applied to that track. Meaning, if you do a "Get Info" on a track, you will see two pastes in the Cover Art tab, yes, you add the cover art twice, one cover next to the other so as to force that album track to get the cover art to attach. On the surface, this seemed to work, and all album tracks now seem populated with Cover Art and the effort appears "saved" when I revisit the album on Day 2.
    But all is not what it appears. The trick of adding missing cover art twice, in the hopes that an album and/or certain random album tracks might adopting the cover art you are trying to assign will produce the following:
    IT ACTUALLY AFFECTS THE AUDIO TRACK!!!!
    Multiple attempts to add/fix cover art will ADD TO TRACK DURATION, such that when you play a track, the lead-in portion of the lyrics (say first 10 secs or so) will REPEAT in as many times as you tried to add the cover art!!!!
    Thinking this might be a corrupt library database, I even deleted the database, started over, and while adding missing cover art, was able to reproduce the lyrics repeating on those tracks where the cover art was added (pasted) twice. You can HEAR and see the increased track duration in iTunes 7.x.x
    MAJOR Cover Art bug!!! So you are not alone. And besides all the wasted hours trying to fix this, I say wait for iTunes 8.x
    Please post and let me know if you have had the same experience with this cover art bug and similar workarounds.
    C'mon Apple! PLEASE FIX THIS. What gives?
    HP Media Center PC   Windows XP Pro  
    HP Media Center PC   Windows XP Pro  
    HP Media Center PC   Windows XP Pro  
    HP Media Center PC   Windows XP Pro  

    You can tell iTunes to "Clear Downloaded Artwork" to get rid of the wrong image.
    Getting iTunes to select the correct image, especially for compilations can be quite frustrating. I've been slowly cleaning up some old artwork from when iTunes could not pull artwork from the iTunes Store for music from other sources. I've learned to check the album in question by using the iTunes Store link in iTunes - I figure if it goes right the the album I'm all set - Wrong! Today I'm doing battle with a bunch of "20th Century Masters - The Millennium Collection" albums. I can go through the album song by song and every one goes right to the correct album - but when I "Get Album Artwork" it still may not find the album or will pull in volume 2 instead of volume 1, etc. I've tried making sure my albums names are exact matches to the iTunes store with the same bad results.
    It really seems like iTunes uses a different search method for artwork than for the iTunes Store link. At least Google has an image search...

  • EDL Exporting and Importing 101 - Questions

    We are testing Premiere's EDL exporting and importing capabilities for the first time, and are having issues. We set up a very simple test project with only 13 clips and a timeline with only 10 edits. This is what it looks like:
    http://img819.imageshack.us/img819/760/j00s.jpg
    We then exported an EDL, started a new Premiere project, and imported the EDL that we had created. It looks like this:
    http://imageshack.us/scaled/landing/32/6hd9.jpg
    In the bin, Premiere has now turned our 13 clips into 41. There are a lot of duplicates, some of them appear to be audio files, even though they're still listed as .mxf, and the start and end times are all over the place. Our two questions are: Why is it making all of these clips? And how do you link the media? We started linking some media manually, but because the start and end times are scrambled, the edits appear completely wrong in the sequence that we've created.

    There are a variety of options offered when exporting an EDL.
    These options need to be considered in conjunction with how the Sequence (audio/video layers) are set up. (managed for the edl export)
    Source footage management is vital in any EDL workflow and even more so when digital clip based ( as opposed to tape based linear assets).  ie. Digital clips have "unusual" filenames and are buried deep in folder structures. Filenames can be duplicated in a card to cards system. (mxf would be an exception)
    The EDL is usually used between systems.
    In your case  you are testing on the same system and assumeably the source footage resides there as well.  This is a case for managing the "source" so as the links work.
    Example. When I take footage to a Resolve Suite out of house.  I set up all the source footage on an transfer drive in the same manner ( filenames, folder names etc) as the original local drive .

  • Major font substitution bug in Illustrator CS5

    Hi all,
    This took me a good long time to track down, and since I didn't find any information here and Adobe technical support was no help, I figured I'd post the result. Happy new year.
    Here was the problem. Working in CS5, intermittently we would get font reflow issues. In addition, when going to edit the type boxes with font reflow, we would get the message, "This text was created in a different version of Illustrator. Editing the text may cause some changes to your text layout. Basic formatting will not be affected. Do you want to continue?" Please note it says "different version" rather than "previous version". These files originated and stayed in Ilustrator CS5! If we hit OK, the type would snap back to the original state!!! Worse, if the type was copied and pasted, or anything in character or paragraph styles was edited, it would snap back without ANY warning. Now you see it... now you don't. Major problem in any print environment.
    So here is what I found, and this is a CS5 exclusive. If you are working on a file and have a font set open which includes a font from one foundry, and then opened another document and activated a font set with an identical font from a different foundry (the original font closing), the kerning for the original document (in the background now) would be set to zero (rather than auto) and the font would reflow. If you didn't notice the reflow, and saved the file, well it would create the condition as described above. Of course it isn't ideal to have the font foundry change like that, but bottom line usually you could get away with it... maybe with one or two characters moving slightly. In the new CS5 world, Illustrator decides you really don't need ANY kerning pair information and then helpfully tells you it was a "different" version of Illustrator that caused this. Heh.
    What a mess. Bottom line, make sure your font management application is set to throw warnings when conflicting fonts are opened, and most importantly, leave the original font open! Do not allow the new font to be opened until the conflict is resolved.
    If your font management application does not have this option (Universal Type Server 1 did not), you better upgrade or forget about using Illustrator CS5 in a heavy production environment.
    Adobe, this was a major change and a major headache. You have some explaining to do...

    Confirmed this is being generated entirely in CS5. I opened the font Sabon. I created a text box. I pasted in some generic type I had just made in text edit. I changed the font to Sabon and the paragraph to justify. I saved and closed the document and closed Illustrator. I closed Sabon and opened Sabon from another foundry. I opened Illustrator and opened the document. All looked good. I duplicated the text box over and outlined the type. I went into the font manager and closed Sabon. I opened the original Sabon. DING! Type reflow. I saved as a second document. I copied the outlined type and closed the document. I opened the original document (note the original font is open). No problems. I paste the outlined type (type outlined with the wrong version of the font active) and it lands exactly in place. I open the second document. The type that reflowed now gives me the stupid message about another version of Illustrator screwing it up. I hit OK and the type reflows back to the way it is supposed to be.
    This proves that the kerning changes weren't due to differences between the fonts. This proves that Illustrator CS5 has a MAJOR type engine bug that could easily spell disaster in production.

  • Keyword exporting bug also impacts catalogs imported from PSE 6

    Hi,
    I haven't seen any mention of it, but the keyword exporting bug reported for catalogs imported from LR 1.x also impacts catalogs imported from Photoshop Elements 6. i.e. all Keywords imported from my PSE 6 catalog have "Include in export", "Export Containing Keywords", and "Export Synonyms" properties set to false.
    I've reported the bug, but as it seems the same as described in KB 405074 (and more importantly, its fix works for formerly PSE catalogs as well!), I'm sure it will be fixed in the next update.
    http://kb.adobe.com/selfservice/viewContent.do?externalId=kb405074&sliceId=2
    Thanks,
    Matt

    Hi Brian,
    When I installed the trial for LR2 I was asked whether I wanted to upgrade my existing PSE6 catalog.
    Screenshot of this can be found here: http://dawsons.id.au/temp/pse6-to-lr2-catalog.png
    That's it. I haven't imported any keywords via any other method.
    Thanks,
    Matt
    PS I'm impressed with the level of Lightroom team involvement in these forums. I've been a PSE user for at least 5 years and have never received feedback from that team re posts/support calls/feature request/bug reports. I've been a LR user for about two weeks and I've already had Tom and yourself reply to my posts. You've got to be happy with that!

  • Mono export bug

    strange export bug I experienced this weekend, I think its a metadata issue.
    Before the export I had to relink all the material because we had moved all the material from one SAN to another. Exported the show using Premiere, not AME, to Prores. The timeline have two mono audio tracks, each panned left and right. I then used AME to convert the new Prores file to export a MXF version and a h264 version.
    All the files came out with only audio in the left channel! But when I check on a different machine the Prores came out with sound in both channels, but the MXF and h264 did not. I then removed all the "Media Cache" and "Media Cache Files", located in the Library/Application Support/Adobe/Common/ folder.
    I then reimported the files, and now the Prores came up with audio in both channels but the MXF and h264 was still "corrupted".
    Have someone experienced the same? Why would the Prores file, with audio in both channels, produce a single mono track MXF/h264 file? Do people regularly delete the "Media Cache" and "Media Cache Files"? PEBCAK?
    Both machines where the new mac pro, 10.9.5, with similar specs, 3,5Ghz 32GB ram dual AMD FirePro D500, with Adobe Premiere 8.2
    Any thoughts is appreciated

    The Prores was exported with these settings:
    Audio Codec: AAC
    Sample Rate: 48KHz
    Channels: Stereo
    Audio Track Layout: 2 Mono Tracks
    Channel Layout: Mono
    The MXF was exported with these settings:
    Audio Codec: Uncompressed
    Sample Rate: 48KHz
    Channels: 2 Channel
    No multichannel

  • CR6.4 RC1 - XMP export bug, anybody else has it?

    I think I found a bug, and although I also found a workaround, here it is.
    My environment: Windows 7, Photoshop CS5, Camera Raw 6.4 RC1, all of them 64-bits.
    Steps to reproduce the bug:
    1. Open several raw files at once in Camera Raw (in my case, Olympus E-PL2 ORF files, but it probably doesn`t matter). For this bug, take images that are likely to have different white balance settings. Also make sure that those are original files, never modified by Camera Raw (or anything else) and that they have no XMP sidecars yet.
    2. Wait until thumbnails are generated (may not be relevant...). Don't click on any of them, just let them be created.
    3. Click on "Select All". Again, don't change the displayed image, just select them all.
    4. In Basic/White Balance, select Auto. All thumbnails are properly updated
    5. Export settings to XMP (from the menu on the right-most toolbar, i.e. still "Basic" if you haven`t changed it)
    6. Keep Camera Raw open, and have a look at the XMP files.
    The BUG : they all contain the same white balance settings (crs:WhiteBalance, crs:Temperature and crs:Tint) which happen to be the computed settings for the first image (the only one displayed so far). All other settings seems to be fine though (i.e. they are from their respective image).
    However, if you go back in Camera Raw and then click on some other images, not all of them. You can see that their WB settings are different and properly computed (as far as "Auto" can properly compute them). Export to XMP again. WB settings are then right, but only for the images that you clicked on. Those that were never displayed full size still have the wrong WB settings (from the first image).
    Obviously, the workaround is to click on each of them. Still that's a bit awkward, especially in my "quite-automated" workflow, where I'm not yet to the point to look at each image individually. Can't tell if this bug exist too on any other version of CR, and my E-PL2 raw files can only be opened in CR 6.4 anyway (unless I change some tags to fool CR).
    Can anybody can reproduce that bug on similar or different environment? And could Adobe fix it, if it is a bug?

    btw, don't know why I wrote RC1... I just meant Release Candidate!

  • Color Shift Happening When Exporting - Bug in Acrobat Export?

    Hi, we are using InDesign CS3 and trying to output a file to send to a printer. We are desiring to have all colors converted to the printer's CMYK color space upon exporting (they sent us their ICC profile).
    But we are getting a bizarre bug that I cannot figure out. It seems like it's actually a software bug, not an issue with settings. I'll try to describe the issue here:
    Upon using 'Convert to Destination (Preserver Numbers or Not)' in the PDF export dialog in InDesign (using PDF/X-4 setting), using the 'Document CMYK' profile, there is a shift in color for 1 particular element. We have a grayscale image of a bunch of dots (black dots on solid white background) that is placed in a frame in InDesign. This image is 'colorized' in InDesign by setting an image color and a frame color (the image color appears as the 'foreground' and the frame color is the 'background'). We've been doing this all the way back to the Quark days (many years). But if the 'background/frame' color is a combination of C+M+Y (with no black), the Magenta and Yellow values are shifted to the Yellow and Black channels (for example - 52c, 5m, 10y, 0k becomes 52c, 0m, 5y, 10k).
    I have never run into this before, and we've run this job with the same element many times now over the last couple years. But I have always used 'No Color Conversion' in my PDFs in the past. So it has something to do with the 'conversion'.
    So far I've tried:
    - Creating new document with just the single element, also created from scratch. So it's not an error in the file.
    - Starting with different profiles (to make sure the profile wasn't corrupt).
    - Choosing 'Preserve Numbers' or not when outputting PDF.
    - All sorts of color combinations. It also appears that if there is black in the color, this value gets shifted to the magenta channel, then the magenta & yellow bump down.
    - Checked the grayscale image to make sure it was flat, and using pure black & white colors. It is.
    I've also tried printing to Distiller (we have Acrobat 8 Pro), but the settings are a lot different here so I'm not sure if I set it up properly. I made a duplicate of the default PDFX3 2002 profile, then edited the color settings to 'Convert Everything to CMYK' and set our printer's profile as the CMYK Color Space. But images are converted to 'DeviceCMYK' and not the profile I put.
    - ANYBODY have any ideas or even know where I would start???
    THANKS. This job needs to go out, but I'm also trying to get a solid workflow down for the future.

    Looks like the issue in the CM thread.
    I'm trying to replicate the issue but haven't done it yet. Still grasping at straws
    1. Did the ID doc ever undergo Convert to Profile?
    2. In Swatch Panel do "Add unnamed colors". Make sure the grayscale is colored with swatches, not colors created in the Color Picker
    3. Do the color values in the swatches have crazy decimal values? Is the color mode of the swatches CMYK?
    4. What format are the grayscale links - TIFF or PSD?
    5. Make certain they are links, not embedded (I'm sure they are links though)
    6. The colorization - are there tints applied to the object colors, or are they 100%?

  • Lightroom 5.3 Export Bug

    During and after exporting a batch of photos, Lightroom will apply changes to the group of photos being exported, even if they are not selected and another photo (not being exported) is selected.  I haven't seen a discussion on this, but I do know that 5.0 had major selection issues.  This problem has caused me more than 3 hours of pain tonight!!
    Steps to repro:
    1) Select several photos to export
    2) Start exporting
    3) Select another photo in the catalog not being exported
    4) Make changes (such as set the rating or paste settings from previous or look at keywords)
         Expected result: only the photo selected is changes
         Actual result: the group of photos being exported changes and not the photo selected!!
    This continues to happen even after the export completes.  Setting the rating or pasting settings from previous or setting keywords affects all of the previously exported images and not the image selected.  The only way to get around this is to quit Lightroom and restart it.

    I tried a new catalog with 10 pictures.  I exported 1 and I do not see the problem.  Will let you know when I find out more.
    Here's the system info:
    Lightroom version: 5.3 [938183]
    Operating system: Windows 7 Business Edition
    Version: 6.1 [7601]
    Application architecture: x64
    System architecture: x64
    Logical processor count: 8
    Processor speed: 3.1 GHz
    Built-in memory: 18422.9 MB
    Real memory available to Lightroom: 18422.9 MB
    Real memory used by Lightroom: 2094.1 MB (11.3%)
    Virtual memory used by Lightroom: 2086.6 MB
    Memory cache size: 1899.0 MB
    Maximum thread count used by Camera Raw: 4
    System DPI setting: 96 DPI
    Desktop composition enabled: Yes
    Displays: 1) 2560x1440, 2) 1200x1600
    Application folder: C:\Program Files\Adobe\Adobe Photoshop Lightroom 5.3
    Library Path: C:\Users\Noah Wardrip\Pictures\20140101 5D Scratch\20140101 5D Scratch\20140101 5D Scratch.lrcat
    Settings Folder: C:\Users\Noah Wardrip\AppData\Roaming\Adobe\Lightroom
    Installed Plugins:
    1) Behance
    2) Canon Tether Plugin
    3) Facebook
    4) Flickr
    5) HDR Efex Pro
    6) HDR Efex Pro 2
    7) Leica Tether Plugin
    8) Nikon Tether Plugin
    9) SmugMug
    Config.lua flags: None
    Adapter #1: Vendor : 1002
        Device : 6898
        Subsystem : b001002
        Revision : 0
        Video Memory : 1002
    AudioDeviceIOBlockSize: 1024
    AudioDeviceName: Speakers (Realtek High Definition Audio)
    AudioDeviceNumberOfChannels: 2
    AudioDeviceSampleRate: 44100
    Build: Uninitialized
    CardID: 26776
    Direct2DEnabled: false
    GPUDevice: D3D
    MaxTexture2DSize: 8192
    OGLEnabled: true
    Renderer: ATI Radeon HD 5800 Series
    ShaderModel: 11.1
    Vendor: AMD
    VendorID: 4098
    Version: 1002:6898:b001002:0000

  • MAJOR iTunes 7 Bug (messes your tracks up!)

    OK I think I've found a really major bug here. I've been trying to manually paste in artwork, while the track is playing and then iTunes then overwrites the track repeating the 1st 7 seconds of the song twice!!!!!
    I've just tested it on Whatshername by Green Day, and copied the file out to another location for I would have an original copy.
    Original track details;
    File size 6172kb
    Runtime 3:39
    iTunes altered version;
    File size 6367kb
    Runtime 3:46
    I can then repeat this for any other track I try and paste artwork into.
    HELP!!!!

    Okay, we've investigated this issue further. Here's the situation:
    We can clear artwork for MULTIPLE items when it is our OWN artwork that we manually imported. But when it's Apple's artwork that iTunes 7 automatically downloaded, it doesn't let you clear the artwork for multiple items all at once... you actually have to clear the artwork one song at a time.
    This is a real pain, since iTunes doesn't always download the proper artwork!

  • Web gallery export bug: Crop ratio change doesn't update correctly

    I've just submitted this as a bug to the Aperture feedback site, but then realized that maybe I should have asked around to find out if it was just me or if it's an actual bug.
    Try this: Export a web gallery to your site. Now change the cropped aspect ratio of one or more images in the gallery. Now export the gallery again and when Aperture asks if you want to Update or Replace the existing gallery, select Update. (This option is supposed to save time by only sending the changed files to the site.) The image that was cropped differently will still show up in the Index and Detail view with the old ratio, but the new dimensions will be stretched to fit the old ratio.
    I've done this repeatedly and it's completely reproducible. The only way to get the gallery to display correctly is to select Replace when exporting the gallery. Obviously, if your gallery is larger than a handful of images this will take a while and it defeats the purpose of the Update option.
    Does anyone find this same issue or am I the only one?

    Yeah, that makes sense.
    I'm thinking now that if I create a new version in the web gallery and crop it just for the web export the app will probably re-send that image out to the web site because it treats the new version as a different image. Since the new version really doesn't take up any meaningful hard drive space this wouldn't be a deal-breaker, but I would have to remember to NOT delete that version or change the crop ratio before uploading the gallery again.

  • JSFL - PNG export bug in CS5.5, works in CS4 - 8000px limit

    We have a series of JSL scripts that export our ad banners in both SWG and GIF format. The GIFs are compiled by exporting each of the 3 frames of the SWF as PNG images then a .jsx script runs in Photoshop and compiles them into a GIF.
    This all worked fine in Flash CS4. Running the script on FLAs in FLash CS5.5 produces this error at the PNG export stage:
    The bitmap is too large. The largest bitmap that can be created is 8000x8000 pixels.
    The line of code that triggers this error is:
    fl.getDocumentDOM().exportPNG((pngPath+resName+".png"), true, false);
    The path variables are fine and produce a valid path (see below). As you know the first boolean states whether to 'use current PNG export settings' (true) or to show the settings dialog on export (false). The second Boolean states whether to export only the current frame (true) or all frames in the SWF (false).
    If I change the 'use current PNG export settings' to false and show the export dialog and OK the default values the export runs fine (which is how I know there is no issue with the export path).
    Showing the dialog box on each export is not acceptable because we have over 10,000 of these banners to export over the next couple of months.
    I'd like to know:
    [1] Is this an actual bug?
    [2] Can anyone suggest a workaround?

    To reproduce this behaviour create an FLA in CS4, make 3 keyframes, draw a filled rectangle (or whatever) on each frame then save it somewhere (ie C:\test.fla)
    Then create a Flash JavaScript file, paste the following code into it and save it in the same location as the FLA. (ie C:\script.jsfl)
    exportPath = fl.scriptURI.substr(0,fl.scriptURI.lastIndexOf("/"))+"/";
    fl.getDocumentDOM().exportPNG(exportPath+"Frame.png", TRUE, FALSE);
    The first line of code here just gets the location of the jsfl file and removes the filename to give an export path.
    The second line export each frame to the same location as the FLA and JSFL files.
    This should run fine in CS4 and you will see the following in your save location:
    test.fla
    script.jsl
    Frame0001.png
    Frame0002.png
    Frame0003.png
    If you change the first boolean in the export command to FALSE and run the script again you should see the PNG export settings dialog box and when you OK it you will get the same export result.
    Now open the FLA and JSFL files in CS5.5 and run the JSFL. With the boolean set to TRUE you should get an error (the 8000px error), however if you set it to FALSE so that you get the settings dialog when you OK it the export will run fine.
    Change it back to TRUE and you will get an error again.

  • CSV export bug in one report

    Hey guys and Apex-friends!
    I have a problem with the export of one of my reports.
    The Column BF is always empty when exported to Excel. In fact, the header is created but the results are not shown.
    If I drop the Page item P480_BIOTOPBAUMFLAECHE the data is exported as it should be but false of course. I just did that for testing purposes of course.
    On my page the results are displayed correctly. I guess that the computation is not carried out. Is there a way to fix that bug?
    Here is my report query!
    select
    :P480_BIOTOPBAUMFLAECHE as flaeche,
    count(b.lng_baumart) * 10000 / :P480_BIOTOPBAUMFLAECHE AS bf,
    LNG_BAUMART,
    p.STR_LRT_MAIN
    from
    VT_TBL_BIOTOPBAUM b,
    VT_PUNKTDATEN_JOIN p
    where
    (p.CNT_GEBIET = :P480_CNT_GEBIET)
    and (b.LNG_INV_PT_ID = p.INV_PT_ID_SUB)
    and (p.str_lrt_main = :P480_STR_LRT)
    and (b.int_bezug = -1)
    and (p.int_status_sub = 3)
    group by
    p.STR_LRT_MAIN,
    lng_baumartIf you have an idea or hint, please let me know!
    Thanks a lot!
    Sebastian

    Hi,
    I do not know does this help, but try
    select
    :P480_BIOTOPBAUMFLAECHE as flaeche,
    count(b.lng_baumart) * 10000 / TO_NUMBER(:P480_BIOTOPBAUMFLAECHE) AS bf,
    LNG_BAUMART,
    p.STR_LRT_MAIN
    from
    VT_TBL_BIOTOPBAUM b,
    VT_PUNKTDATEN_JOIN p
    where
    (p.CNT_GEBIET = :P480_CNT_GEBIET)
    and (b.LNG_INV_PT_ID = p.INV_PT_ID_SUB)
    and (p.str_lrt_main = :P480_STR_LRT)
    and (b.int_bezug = -1)
    and (p.int_status_sub = 3)
    group by
    p.STR_LRT_MAIN,
    lng_baumart

  • Arguable, Excel Export Bug

    When using a substitution string to define a region’s no data found message, if one attempts to use a substitution string as no data found message, it will work fine during normal display. However, when taking the CSV output of an empty report (enter the questionable nature of this being a bug) the substitution string is not evaluated.
    Is this working as intended or can this be fixed by the APEX team?
    I know it is a nit-picky type thing as what usefulness would an empty report provide and why would anyone attempt to export it, but as the corporate wheel turns I am asked investigate every little thing.

    It took me a second to figure out what exactly the we did in our application, but here is a test page for you to work with:
    http://apex.oracle.com/pls/otn/f?p=33318:1:
    It would seem that in our application (which is pretty huge and spans multiple applications) we have an idea of a master list page. On this list page there is only one report and there is an export to CSV icon on a tool bar that we output above the page's content. This icon is only active on master list pages since they by definition and requirement only have 1 large report on the page. The icon has a link that is forged based on inspecting how the #CSV_LINK# replacement works in region templates.
    The test page posted above uses such knowledge to make a #CSV_LINK# in the report template. And I am sure at this point you are saying to yourself "this is obviously in this guys hands and not our problem."
    I am not guessing the reason it could not be reproduced is that the CSV_LINK is not output when the report query returns no data found.
    Example of the HTML in the region template being used:
    <a href="f?p=&APP_ID.:&APP_PAGE_ID.:&SESSION.:FLOW_EXCEL_OUTPUT_#REGION_ID#_en-us">Custom Export Link</a>

Maybe you are looking for