Black frames in QT after converting from HDV to ProRes 422

I've been making a movie, shot in HDV 25p. In the timeline, everything plays fine, but when converted to ProRes422 via 'export to Quicktime Movie', I get black (dropped?) frames every now and then, on an irregular basis. Can be every 40 frames or every 90, but they're all over the movie. Worse still: the last 10 seconds of the movie are 'lost' in the QT-version, it comes to a freeze frame while the sound runs on.
When I make the QT movie with a different setting (HDV-25p instead of ProRes422), the end is allright, but I still keep getting the black frames. Of course these black frames are visible in the movie, it looks like the movement stutters.
Also tried QT with AIC codec, but to no avail.
I never experienced this before, although I used this workflow several times.
I need to make a Bluray disk via Toast. Any suggestions of how to get rid of the black frames?

Concertpix wrote:
...Now render before exporting to QT, I suppose?
You don't really have to. Exporting is kinda the same as rendering. Only thing is that if you do not render before export, FCP does not 'remember' this rendering.
If you think you'll needs parts of the render files later, you might render first.
Others in this forum do deliberately throw away the renders before they export, in order to avoid artifacts. Personally I prefer to see rendered footage before I export. I can see what I am sending to the export-application then. Haven't have any trouble so far.
So. It's up to you.
Rienk

Similar Messages

  • Why is the image brighter after converting H264 to Apple Prores 422 in Compressor ?

    Hello -
    Very strange situation, keep reading please!
    I am using Compressor to convert H264 1080p footage from a D600, to Apple Prores 422HQ for editing. Normal.
    I am using the default Quicktime Settings named "Apple Prores 422 (HQ)".
    The converted file is a bit brighter than the original... Why is this even possible! I find this a bit problematic because I'm loosing some details in the whites, at a way too early stage for signal alterationt!
    So I tried different other stuff that you will find interesting:
    • changing gamma correction in the codec settings had no effect
    • I can see the change happening already in the Preview window
    • and this is the best one : if I apply a resize, to anything, like 1919 X 1079, or 1280 X 720... then the color change does not occur, even when exported! If I apply a resize to the same size, then the output is brighter again.
    I am proof checking in Quicktime 7 of course, with "FCP compatibility" enabled and disabled.
    I know this is a hot topic and there are many unsolved aberrations like this around this topic, but maybe there is something I don't get ?
    Thanks

    Apple are so thoughful for making us loose the discussion we clicked on after we log in..
    Alex CVideo > I am so happy that you wrote about this
    Yes: this is the exact problem. Very nice screencap, this is exaclty it (even if I said it 2 times now).
    I have a little secret for you:
    I read in another discussion saying that he had this problem too.
    The only time I ever did in the entire Internet.
    here it is :
    this guy re-installed her entire system
    mac os + final cut systems
    and this time it worked.
    Right now I prefer to convert to 1079p than risk this entire operation even it it worked 100% lol
    At least not right now
    but maybe you will be boosted up enough to give it a try
    Good luck to all of us  and thanks again to Apple for these great moments we spend together talking about their wonderful mysteries

  • Capturing HDV Into ProRes 422 (LT) Via FireWire

    I read this fine tutorial on Moviola on the technique of Capturing HDV Into ProRes Via FireWire.
    http://moviola.com/hdv_prores
    Since you can choose ProRes 422 (LT) as an option in the Log and Transfer window, I was wondering if there is a way to capture HDV to ProRes 422 (LT) via firewire like in the above mentioned article.
    I tried creating a custom capture setting in the AV Settings, but ProRes 422 (LT) was not available as an option, only ProRes 422 and ProRes 422 (HQ). And those settings cannot be edited or duplicated (grayed out).
    I don’t know why ProRes 422 (LT) is available in the Log and Transfer window but not in the AV Settings window. Maybe it will become available in an update.
    In the meantime, does anyone know a way to get around this? Maybe modifying an FCP file somewhere?
    Thanks,
    ======
    Richard

    HDV is recorded to tape inside of the camera as digital information. Component coming out of the camera is analog. The camera is performing the first conversion D/A, from HDV (digital) to component out (analog).
    Component going into the ioHD is analog. The ioHD then converts via its hardware to Prores (any flavor), which is digital. The ioHD has to convert the analog from the component outs of my camera to digital for use in FCP. FCP only uses digital video.
    You said "The IOHD internally converts to ProRes.." converts to ProRes is the second A/D conversion.
    So the path is D/A/D. I count that as two conversions, camera D/A as one the ioHD A/D as two.
    I don't want to unnecessarily convert from digital to analog to digital which is why I don't use the ioHD to convert from HDV to Prores (any flavor).
    Unfortunately I don't have any digital outs for this camera, neither HDMI or HD SDI.
    I believe capturing and converting HDV to ProRes via firewire in FCP doesn't have this D/A/D conversion which is why I'd like to be able to capture HDV to ProRes LT via firewire in FCP and stay digital all the way, with no analog conversions.
    I use the ioHD for all of my analog to digital conversions. It's a great box from a great company.
    Thanks,
    =====
    Richard

  • Unable to install iTunes after converting from Windows Vista to Windows 7.  Am told installation was successful, then "iTunes was not installed correctly", followed by "Error 7 (Windows error 193).

    Unable to install iTunes after converting from Windows Vista to Windows 7.  Am told installation was successful, then "iTunes was not installed correctly", followed by "Error 7 (Windows error 193).  I have my iPod plugged into my computer via USB port.  What am I doing wrong?

    i have the only account on my laptop so have checked and am the account administrator
    i run windows 7 home premium
    I have the same problem and
    have followed the link uninstalling in the correct order,
    then restarted as per instructions,
    went to Apple to download itunes,
    hit download now,
    Visit the iTunes download page. Click Download Now to download the iTunes installer. When prompted, click Save (instead of Run).
    did not get a save instead of run prompt
    Right click on iTunesSetup or iTunes64Setup (the installer you downloaded in step 3).
    If you have Windows Vista, Windows 7, and Windows 8: Choose "Run as administrator."
    i can only click run as administrator from right clicking the shortcut on my desktop screen
    If iTunes fails to install or repair, it might be necessary to remove components left from a previous installation of iTunes and then reinstall.
    sick of doing this
    at least 7 or 8 times i have re installed itunes to no avail
    troubleshooting no better
    please help. pulling my hair out at this stage
    it was working fine until 2 days ago when i opened itunes it offered to update to 12.1
    not working since i clicked yes
    also i have gone to restore previous point and ffs there are no restore points before my multiple reinstalls
    really dont want to have to restore factory settings

  • When using Adobe Export PDF - I cannot save a document after converting from PDF.  Why not?

    When using Adobe Export PDF - I cannot save a document after converting from PDF.  Why not?

    What happens when you click the Save/Download button after the file conversion is complete?

  • HDV to ProRes 422?

    I've got a 90 minute movie to cut.  2/3'rds of the original material was shot with a Sony HDV camera 60i.  The other third is XDCam (HQ), also 60i.
    I'm trying to figure out a protocol.
    The film is aimed at some kind of theatrical distribution, festivals for sure, possibly a network airing.  (It's an engaging subject, and very nicely shot, despite the older format).
    Anybody done this?  And might you have some recommendations?
    Do I 'optimize' on my import?  I notice FCPX optimizes the HDV to ProRes 422 (not HQ), but at 60i.  Is there a way to set a different optimization?
    Should I bother with a proxy when the original was only HDV (now being optimized to ProRes on import)?  The system I have at hand here seems to be fairly robust.
    Or.  Should I edit the HDV original?  And then just output in whatever codec seems appropriate (when I've done some more research)?
    Any suggestions would be most appreciated.
    Ben

    Thank you guys, very helpful.
    And Tom, this is all footage that was captured in FCP7, mostly a long while back, except for the XDCam.  So the HDV was captured from the Sony camera, and the XDCam was the EX3, so straight from the cards (using FCP's capture transfer setup).
    Now I'm playing at switching the whole project over to FCPX.  Mainly because FCPX looks so intriguing.  And.  I had to do an emergency colour grading of an IMAX movie last week, for a test screenig ... working on their HD proxy cut.  I was going to do it in Colour, but I haven't used Colour in six months, and it's a daunting creature to get back into after long breaks.  I've been toying with FCPX for a couple of weeks, just a few minutes here and there, and tried the colour grading setup.  Wow.  In ten minutes I was up to speed.  We did an XML of their film (being cut in FCP7).  An hour later it was in FCPX.  And a few hours later I had a really really nice grade.  It blew me away.  Yesterday we did the 'real' grade in a relatively high-end studio.  Very good people.  Brand new hardware - with lots of nifty buttons and tools.  But I swear the end result doesn't look any different than what we got from FCPX.  In fact.  I'm toying with the idea of actually pulling the 4K into FCPX, and outputting it with MY original grade - just to make a comparison.  Now wouldn't that be intriguing.  And horrible, ultimately, for studios with such a huge capital outlay.  Then again.  It ain't the equipment.  The colourist was a total pleasure to work with, knew his stuff.
    Thank you very much for your help guys.
    Actually, there is still a question in my head.  I'm used to working in 24p.  This film is for theatres, festivals, even a network airing perhaps.  Is a 30 fps master going to work in those venues?  I seem to remember that the new digital projectors don't care what the frame rate is.  Have I got that wrong?  And does it matter whether my master is interlaced or progressive?  I hate the interlaced look - but I'm not sure what this footage is going to look like de-interlaced.
    And.  I'm going to do a lot of colour correcting on this show, and some modes special effects (possibly do those in Motion), but in a 'realist' sort of way; no green screen.  Just trying to make the whole look more cinematic.  But I'm not attached to the 24 fps thing.  Though 30 fps this stuff was SHOT like a film, it already looks cinematic.  But I'd love to somehow ameliorate the inevitable 'video' look of the medium.

  • Capturing in the HDV-Apple ProRes 422 Preset

    I am trying to capture some HDV footage in Final Cut 7 using the HDV-Apple ProRes 422 preset. However, when I go to log and capture after changing the audio/visual settings, the program immediately asks me to enter a file name and then jumps right into a capture now rather than bringing up the usual log and capture screen.
    Has anyone else run into this problem, and if so, have any solutions to fixing it? This is the first time I have used this capture preset, so there may be a step or setting I am accidently skipping.
    Thanks in advance.

    If you are capturing HDV as ProRes, this is normal. This is the only case that this happens like this. Only with a capture card can you get the normal Log and Capture window. Converting one format to another via firewire...typically requires a card. This is a special case.
    http://library.creativecow.net/articles/poisson_chris/hdv-prores.php
    Shane

  • Media encoder inserts black frame at beginning, when converting my MOV file to H264 for YouTube 720pHD

    I'm using Adobe Media Encoder to convert my MOV file to H264, and selecting "YouTube 720pHD" (for Instagram) as I was instructed by someone at Adobe over the phone. But it inserts a black frame at the beginning or end. When I open the converted file on my desktop, the black frame is the first frame. After I upload to Instagram, the black frame is at the end. How can I get rid of the black frame?! Please help!

    Welcome to the furum, Forrest.
    Hmmm. I don't recall hearing of that problem. There may not be many users who can offer a solution.
    This workaround should work, however: Open the exported movie in QuickTime Player and remove the first frame. (I think it's only the first frame that is black, not the first second. Remove all the black, whatever it is.) Save the movie. That may cause QT Player to save it into a new movie. Use the modified movie for your Web site. QuickTime Pro is required — $30 from Apple.
    Note that you've posted in the iMovie 6 forum, not the iMovie HD forum for iMovie 5. There are fewer current iMovie 5 users here. Most were iM5 users, however, so someone might remember this problem.
    Karl

  • Receiving a message in my word document after converting from a PDF to word. Please advise

    After converting and dowloading that converted file from a  Adobe PDF file to a word document I then open the word document to see a message stateing
    "To view the full contents of this document, you need a later version of the PDF viewer. You can upgrade to the latest version of Adobe Reader from www.adobe.com/products/acrobat/readstep2.html
    For further support, go to www.adobe.com/support/products/acrreader.html"
    Please proivde advise on how to sucessfully convert the Adobe PDF file to a word document.

    Hi Buster,
    The error message you were receiving occurs when you try to convert a dynamic PDF file created with Adobe LiveCycle Designer.  This file is usually already a fillable form.  Unfortunately there is no workaround available for converting documents like this within the ExportPDF service.
    I'm sorry for the inconvenience.
    Please let me know if you have any questions or if I can be of further assistance.
    -David

  • Unnecessary text behind listbox after converting from a web-page

    When I make convertation from htm-page containing listbox to pdf, there also appear text on the back of Listbox object. The strings are equal to Listbox values. If I create listbox manually, these strings not appear. How to fix this bug?

    OK, I see now what you mean. It's been a while since I've web-captured an HTML form and I've never noticed that before. I don't think there's anything you can do to prevent it from happening though. You can change the color of the text so it's not visible, or remove it through redaction or other editing tools.

  • How to transfer XDCAM from EX1 using ProRes 422

    Ok, I'm starting to think a little above my pay-grade here, but:
    My understanding is that I can directly import XDCAM files shot on a Sony EX1 by placing the SxS card in my MBP express card slot and using Sony's transfer application. However, I want to transcode to ProRes 422 because the timeline will contain P2 footage from an HVX200.
    Does the ProRes 422 step require the EX1 camera itself to be connected via firewire, or can I transcode using just the cards? If I transfer using the native codec but edit in a ProRes 422 timeline, can I edit both the P2 and XDCAM footage just as well as if they had been transcoded on transfer?
    Any advice welcome. Tnx!

    There is no direct file based XDCAM EX to ProRes ingest method in FCP. You can import the footage directly into FCP using Sony's XDCAM Transfer app or through FCP's own Log and Transfer interface when using Sony's PDZK-LT1 FCP Log and Transfer plugin. Either way, its just a rewrap of the native media into an FCP friendly Quicktime wrapper.
    If you want to transcode to ProRes for edit then you need to either transcode the imported clips using FCP's Media Manager > Recompress option (or some other post capture transcode method/software eg Compressor, MPEG Streamclip etc) or capture the media directly as ProRes using the camera's baseband output together with a suitable I/O device attached to your Mac.
    Can you edit the XDCAM footage directly in a ProRes timeline? Absolutely ... obviously it will not be as render free / fluid as if you were editing in a native timeline, but depending on the power of you Mac it should offer no real issue. I know many who always edit with their camera native media such as XDCAM HD/EX and HDV directly in a ProRes timeline as a matter of course.
    Hope it helps
    Andy

  • Apple ProRes HQ files (converted from HDV) will not play in Premiere Pro

    I was working on a project in premier pro and finished a draft on 12/24 with no issues.  I took these file directy from their coverted state as .mov files into the PP project and edited on the timeline with no issues.  Shut down on 12/24.  Opened project today, none of the files from the HDV converted format will play correctly OR export correctly.  They are all Black video and still contain the right audio. 
    As a side note here, this is the same for trying to play the file in Quicktime AND in Apple's Final Cut Pro 7. 
    The only files affected are those that were uploaded and coverted to Apple ProRes HQ from the HDV format. 
    Again, this was working and functioning fine un Tuesday, now they appear black in the timeline and viewers. 
    Only change made to ANYTHING on my iMac is: Updated iTunes on Tuesday after I had closed the project from Premiere Pro.
    Please help!!!
    Thankyou,
    Clede

    Only change made to ANYTHING on my iMac is: Updated iTunes on Tuesday after I had closed the project from Premiere Pro.
    Sounds like a clue.
    Apple / Mac  updates have a history of creating issues and plenty of evidence supports that statement.
    My guess its a QT version issue.

  • After converting from fla to html 5    "413" warnings!

    Hi
    We have a fla file for a homepage, where we build in Flash 4 and then convert to Flash 5.  After we convert with Wallaby we was a little confused about so many warnings.  Here the start of the big logfile:
    <?xml version="1.0" encoding="utf-8"?>
    <conversion_log input_name="main_flash5.fla" output_name="main_flash5.html" date="Tue May 31 12:53:10 GMT+0200 2011" >
      <status label="reading fla file..."/>
      <warning label="Unsupported feature: Compiled Clip Not Supported" context="CompiledClipItem not supported: Form" code="18"/>
      <warning label="substituted missing font: Swis721 BT with Arial Narrow" code="23"/>
      <warning label="substituted missing font: Walkway Black with Arial Narrow" code="23"/>
      <warning label="substituted missing font: Cheboygan with Arial Narrow" code="23"/>
      <warning label="substituted missing font: AG ForeignerULB-Plain with Arial Narrow" code="23"/>
      <warning label="substituted missing font: GeoSlab703 Lt BT with Arial Narrow" code="23"/>
      <warning label="substituted missing font: DINMittelschrift with Arial Narrow" code="23"/>
      <warning label="substituted missing font: standard 07_55 with Arial Narrow" code="23"/>
      <warning label="Unsupported feature: Compiled Clip Not Supported" context="CompiledClipInstance not supported" code="18"/>
      <warning label="substituted missing font: English111 Adagio BT with Arial Narrow" code="23"/>
      <warning label="substituted missing font: standard 07_56 with Arial Narrow" code="23"/>
      <warning label="substituted missing font: kroeger 0853 with Arial Narrow" code="23"/>
      <warning label="substituted missing font: standard 07_58 with Arial Narrow" code="23"/>
      <status label="converting fla to HTML5..."/>
      <warning label="Unsupported feature: Tween attribute is not supported" context="Layer: bg_1_1/FrameSet[1]: frames[3,14]/Classic Tween/Tween attribute color transform: ColorMatrix" code="35"/>
      <warning label="Unsupported feature: Unsupported Filter encountered" context="Layer: bg_1_1/FrameSet[1]: frames[3,14]/Group[0]: instance of bg_1/HTML Filter export not supported" code="32"/>
      <warning label="Unsupported feature: Tween attribute is not supported" context="Layer: Layer 35_1/FrameSet[1]: frames[2,10]/Classic Tween/Tween attribute color transform: ColorMatrix" code="35"/>
      <warning label="Unsupported feature: Dynamic Masks are not supported" context="Symbol: preloader_main/TimeLine[0]: preloader_main/Layer[0]: Layer 2/Mask contains multiple framesets: FrameSet[0]: frames[0,98]" code="31"/>
      <warning label="Unsupported feature: Sound Not Supported" context="Symbol: preloader_main/TimeLine[0]: preloader_main/Layer[4]: Layer 16/FrameSet[0]: frames[0,99]/Audio not supported: Beep" code="15"/>
      <warning label="Unsupported feature: Tween attribute is not supported" context="Layer: footer_section_1/FrameSet[1]: frames[42,51]/Classic Tween/Tween attribute color transform: ColorMatrix" code="35"/>
      <warning label="Unsupported feature: Dynamic Masks are not supported" context="Symbol: eq1_my_eq/TimeLine[0]: eq1_my_eq/Layer[0]: Layer 1/Mask contains multiple framesets: FrameSet[0]: frames[0,37]" code="31"/>
      <warning label="Unsupported feature: Tween attribute is not supported" context="Layer: sq1_1/FrameSet[0]: frames[0,7]/Classic Tween/Tween attribute color transform: ColorMatrix" code="35"/>
      <warning label="Unsupported feature: Unsupported Filter encountered" context="Layer: sq1_1/FrameSet[0]: frames[0,7]/Group[0]: instance of sq1_my_eq/HTML Filter export not supported" code="32"/>
      <warning label="Unsupported feature: Tween attribute is not supported" context="Layer: sq1_1/FrameSet[1]: frames[2,9]/Classic Tween/Tween attribute color transform: ColorMatrix" code="35"/>
      <warning label="Unsupported feature: Unsupported Filter encountered" context="Layer: sq1_1/FrameSet[1]: frames[2,9]/Group[0]: instance of sq1_my_eq/HTML Filter export not supported" code="32"/>
      <warning label="Unsupported feature: Tween attribute is not supported" context="Layer: sq1_1/FrameSet[1]: frames[4,11]/Classic Tween/Tween attribute color transform: ColorMatrix" code="35"/>
      <warning label="Unsupported feature: Unsupported Filter encountered" context="Layer: sq1_1/FrameSet[1]: frames[4,11]/Group[0]: instance of sq1_my_eq/HTML Filter export not supported" code="32"/>
      <warning label="Unsupported feature: Tween attribute is not supported" context="Layer: sq1_1/FrameSet[1]: frames[6,13]/Classic Tween/Tween attribute color transform: ColorMatrix" code="35"/>
      <warning label="Unsupported feature: Unsupported Filter encountered" context="Layer: sq1_1/FrameSet[1]: frames[6,13]/Group[0]: instance of sq1_my_eq/HTML Filter export not supported" code="32"/>
      <warning label="Unsupported feature: Tween attribute is not supported" context="Layer: sq1_1/FrameSet[1]: frames[8,15]/Classic Tween/Tween attribute color transform: ColorMatrix" code="35"/>
      <warning label="Unsupported feature: Unsupported Filter encountered" context="Layer: sq1_1/FrameSet[1]: frames[8,15]/Group[0]: instance of sq1_my_eq/HTML Filter export not supported" code="32"/>
      <warning label="Unsupported feature: Tween attribute is not supported" context="Layer: sq1_1/FrameSet[1]: frames[10,17]/Classic Tween/Tween attribute color transform: ColorMatrix" code="35"/>
      <warning label="Unsupported feature: Unsupported Filter encountered" context="Layer: sq1_1/FrameSet[1]: frames[10,17]/Group[0]: instance of sq1_my_eq/HTML Filter export not supported" code="32"/>
      <warning label="Unsupported feature: Tween attribute is not supported" context="Layer: sq1_1/FrameSet[1]: frames[12,19]/Classic Tween/Tween attribute color transform: ColorMatrix" code="35"/>
      <warning label="Unsupported feature: Unsupported Filter encountered" context="Layer: sq1_1/FrameSet[1]: frames[12,19]/Group[0]: instance of sq1_my_eq/HTML Filter export not supported" code="32"/>
      <warning label="Unsupported feature: Dynamic Masks are not supported" context="Symbol: eq1_my_eq/TimeLine[0]: eq1_my_eq/Layer[0]: Layer 1/Mask contains multiple framesets: FrameSet[0]: frames[0,37]" code="31"/>
      <warning label="Unsupported feature: Tween attribute is not supported" context="Layer: sq1_1/FrameSet[0]: frames[0,7]/Classic Tween/Tween attribute color transform: ColorMatrix" code="35"/>
      <warning label="Unsupported feature: Unsupported Filter encountered" context="Layer: sq1_1/FrameSet[0]: frames[0,7]/Group[0]: instance of sq1_my_eq/HTML Filter export not supported" code="32"/>
      <warning label="Unsupported feature: Tween attribute is not supported" context="Layer: sq1_1/FrameSet[1]: frames[2,9]/Classic Tween/Tween attribute color transform: ColorMatrix" code="35"/>
      <warning label="Unsupported feature: Unsupported Filter encountered" context="Layer: sq1_1/FrameSet[1]: frames[2,9]/Group[0]: instance of sq1_my_eq/HTML Filter export not supported" code="32"/>
      <warning label="Unsupported feature: Tween attribute is not supported" context="Layer: sq1_1/FrameSet[1]: frames[4,11]/Classic Tween/Tween attribute color transform: ColorMatrix" code="35"/>
      <warning label="Unsupported feature: Unsupported Filter encountered" context="Layer: sq1_1/FrameSet[1]: frames[4,11]/Group[0]: instance of sq1_my_eq/HTML Filter export not supported" code="32"/>
      <warning label="Unsupported feature: Tween attribute is not supported" context="Layer: sq1_1/FrameSet[1]: frames[6,13]/Classic Tween/Tween attribute color transform: ColorMatrix" code="35"/>
      <warning label="Unsupported feature: Unsupported Filter encountered" context="Layer: sq1_1/FrameSet[1]: frames[6,13]/Group[0]: instance of sq1_my_eq/HTML Filter export not supported" code="32"/>
      <warning label="Unsupported feature: Tween attribute is not supported" context="Layer: sq1_1/FrameSet[1]: frames[8,15]/Classic Tween/Tween attribute color transform: ColorMatrix" code="35"/>
      <warning label="Unsupported feature: Unsupported Filter encountered" context="Layer: sq1_1/FrameSet[1]: frames[8,15]/Group[0]: instance of sq1_my_eq/HTML Filter export not supported" code="32"/>
      <warning label="Unsupported feature: Tween attribute is not supported" context="Layer: sq1_1/FrameSet[1]: frames[10,17]/Classic Tween/Tween attribute color transform: ColorMatrix" code="35"/>
      <warning label="Unsupported feature: Unsupported Filter encountered" context="Layer: sq1_1/FrameSet[1]: frames[10,17]/Group[0]: instance of sq1_my_eq/HTML Filter export not supported" code="32"/>
      <warning label="Unsupported feature: Tween attribute is not supported" context="Layer: sq1_1/FrameSet[1]: frames[12,19]/Classic Tween/Tween attribute color transform: ColorMatrix" code="35"/>
      <warning label="Unsupported feature: Unsupported Filter encountered" context="Layer: sq1_1/FrameSet[1]: frames[12,19]/Group[0]: instance of sq1_my_eq/HTML Filter export not supported" code="32"/>
      <warning label="Unsupported feature: Dynamic Masks are not supported" context="Symbol: eq1_my_eq/TimeLine[0]: eq1_my_eq/Layer[0]: Layer 1/Mask contains multiple framesets: FrameSet[0]: frames[0,37]" code="31"/>
      <warning label="Unsupported feature: Tween attribute is not supported" context="Layer: sq1_1/FrameSet[0]: frames[0,7]/Classic Tween/Tween attribute color transform: ColorMatrix" code="35"/>
      <warning label="Unsupported feature: Unsupported Filter encountered" context="Layer: sq1_1/FrameSet[0]: frames[0,7]/Group[0]: instance of sq1_my_eq/HTML Filter export not supported" code="32"/>
      <warning label="Unsupported feature: Tween attribute is not supported" context="Layer: sq1_1/FrameSet[1]: frames[2,9]/Classic Tween/Tween attribute color transform: ColorMatrix" code="35"/>
      <warning label="Unsupported feature: Unsupported Filter encountered" context="Layer: sq1_1/FrameSet[1]: frames[2,9]/Group[0]: instance of sq1_my_eq/HTML Filter export not supported" code="32"/>
    I think, there are so many problems that we start to build the webpage from the beginning in html 5.  Regards Marlise

    It looks like you have a variety of issues here:
    1) Missing fonts. Just like with anything else, you need to have the fonts you use in a file available on the machine where you are trying to utilize that file. I'm guessing the FLA was created on a different machine than where you ran Wallaby. Wallaby is just trying to make you aware that it is changing the fonts since it couldn't access the original font on the system where it was run.
    2) Complaints about filters. At this time CSS3 doesn't support filters so these will be dropped in the FLA to HTML5 conversion. Starting with HTML5 will not help you here. You'd have to create your content in a different way in HTML5, change the content in Flash to not have filters, or just ignore the warnings in Wallaby and accept the visual differences. However, sometimes the visual differences w/o filters are too dramatic.
    3) Complaints about compiled clips. Likely because of the use of components within the FLA. Wallaby doesn't support actionscript at this time and compiled clips use actionscript. Depending on what components you are using, trying to recreate similar content in HTML5 from scratch may be difficult.
    4) Complaints about tween color transforms. These are effectively filters and fall in the same bucket as #2 above.
    5) Complaints about dynamic masks. This first release of Wallaby only works with static non-moving content in masks.
    6) Complaints about audio. This first release of Wallaby doesn't support sound.
    We are actively working on a new release of Wallaby and will continue to add more features to make the transition from FLA to HTML5 easier.

  • How to fix black screen on iPad after restoring from 4.2.1 to 4.3.3

    recently i just restore my ipad from 4.2.1 to 4.3.3, suddenly it's just hang up on black screen (DFU mode i guess).
    I've tried pressing home and off button for 10 sec and bla..bla....but doesn't work at all...
    Googling to find another way such as use TU and others third party software..but still not bloody working at all...
    After few troubleshoot done, thing goes worse and worse...
    now my iTunes didn't detect my iPad at all.
    Can anyone help me?PLEASEEEEE!!!!!!

    Try reset iPad
    Hold down the Sleep/Wake button and the Home button at the same time for at least ten seconds, until the Apple logo appears
    Note: Data will not be affected.

  • Poor jpeg quality after converting from pdf.

    I am trying to make a book video out of a collection of pdf files in Premiere Elements 11. Apparently Premiere does not take pdfs so I converted the pdfs to jpegs via Photoshop CS5. When I try to run the video the quality of the images is horrible - very pixalated and some of the text is unreadable. Even though Photoshop psd files are said to be useable I get the same results. Rendering did nothing. Help?

    ksreid
    What are the pixel dimensions of your jpegs?
    For now, I will assume 1920 x 1080 pixels.
    In Premiere Elements 11 Expert workspace, go to File Menu/New/Project and Change Settings.
    In the Change Settings area, change the project preset to:
    NTSC
    DSLR
    1080p
    DSLR [email protected]
    After OK'ing the above, you will see the New Project dialog displaying your project preset.
    Make sure that there is a check mark next to the option "Force Selected Project Setting on This Project" in the New Project dialog, and
    then OK out of there.
    Back in the Premiere Elements 11 Expert workspace, use Add Media/Files and Folders/ to get your source files
    into Project Assets from where you drag the source files to the Timeline. Render the Timeline content and
    determine if the quality of that content playback in the Edit area monitor is improved in comparison to your prior projects.
    You might also explore applying fx Effects/Blur & Sharpen/Sharpen (just a little) to the Timeline content.
    What is your intended export for your Timeline content?
    Please review and consider and then let us know the outcome.
    Thank you.
    ATR

Maybe you are looking for