H264 problems

I'm not able to export an H264 movie to another H264 movie in QuickTime Pro. Is this a QT issue?

Not compared to 16 bit 48k.Since I don't use Apple Lossless, I ran a number of tests using Apple 720p trailers as the H.264 source files. In all cases the Apple Lossless audio came out on the order of 650 Kbps. As David indicates and others have inferred, while as you indicate Apple Lossless may be compact compared to uncompressed audio, it is roughly 4 times the typlical AAC 48.0 KHz sampled file which is typically compressed at 160 Kbps (Apple trailers/iTunes normally use 128 Kbps at 44.1 KHz).

Similar Messages

  • H264 problems and out of synch/choppy

    I can code/compress the same timeline in Divx, MP4, and just about any other fromat and have no problems at all.
    When I go to code and compress in H264, the video and audio are out of sych, and the picture is choppy. I tried different FPS, key frame rates, bit rates and no go, interlace, progressive and it just doesn't matter
    But.....When I reduce the picture size to a very small size upon coding/compression, it is in synch, the h264. Like below 360x240
    What is going on? Thank you for your time
    David

    Have you run Apple hardware test and memory (Memtest) test to make sure that your RAM is not defective? http://discussions.apple.com/thread.jspa?threadID=1674664&tstart=0
    I would also copy a short video that is causing you problems and try to run it on a different machine just to see where the problem is.

  • H264 problems in Director 11.5

    Has anyone had any problems using H264 video in Director 11.5?  I am using H264 quicktimes exported out of Apple Final Cut Pro.  I've created a test project with 3 Adobe Photoshop graphics and an H264 video.  Sometimes I can import the video, sometimes Director crashes.  Even on those occasions I've been able to import the video, many times once I save the project I will not be able to re-open it.  I get a "Director has exerienced a fatal error and will close" error.
    Things seem to be much more stable with quicktimes encoded in Sorenson 3 or encoded with MP4.  I've even re-encoded the H264 video through Premiere Pro CS4 thinking it might be something out of FCP but still have the same problem.
    I have confirmed I have the most up-to-date version of Quicktime (7.6.5) and have re-installed Director 11.5.
    Any one else experiencing this?
    Mike M
    Director 11.5
    Windows Vista Ultimate

    I am having the same problems. I bought the new version of Director because of the advertised integration with H264, but when I play a cast member from the cast or on the stage I receive a fatal error.
    Vista Ultimate
    Director 11.5
    mikem75 wrote:
    Has anyone had any problems using H264 video in Director 11.5?  I am using H264 quicktimes exported out of Apple Final Cut Pro.  I've created a test project with 3 Adobe Photoshop graphics and an H264 video.  Sometimes I can import the video, sometimes Director crashes.  Even on those occasions I've been able to import the video, many times once I save the project I will not be able to re-open it.  I get a "Director has exerienced a fatal error and will close" error.
    Things seem to be much more stable with quicktimes encoded in Sorenson 3 or encoded with MP4.  I've even re-encoded the H264 video through Premiere Pro CS4 thinking it might be something out of FCP but still have the same problem.
    I have confirmed I have the most up-to-date version of Quicktime (7.6.5) and have re-installed Director 11.5.
    Any one else experiencing this?
    Mike M
    Director 11.5
    Windows Vista Ultimate

  • Quicktime h.264 still all washed out...

    I know there are countless threads about gamma / unsaturated color issues when exporting to using h.264... in fact I think I have read all of them, which are all at least a year + old... this is still a problem: (Obviously top is good)
    So does anyone have a REAL answer for this bug. Someone did post a supposed workaround, dealing with color profile... but this does not work.
    BTW... it plays fine embedded in Firefox.
    24" iMac Mac OS X (10.4.9) Core 2 duo - 2.33 - 2gb ram

    I too have been plagued by this H264 problem for the past 2 years it seems.
    I have a suspicion that if we polled the users experiencing this effect that
    it would result they all use custom or modified Display Profiles in the Display System Preferences.
    My temporary (and somewhat silly workaround) has been to change my display profile to the
    standard "Cinema HD Display" instead of my user-created "Cinema HD Display Calibrated" profile.
    It does alter the gamma of my display to a unpleasing value, but after changing it, the H264 export
    works beautifully. No gamma shift at all.
    I have read all the suggestions on trying the quicktime "filter then colorsync" export and always got unsatisfactory results. My silly workaround always produces the best results. I just have to change the dang setting back after I export so my eye dont burn out of my skull.

  • Issues when Exporting to H.264

    Hey guys, just ran into an issue for the first time with CS6. I'm trying to export to h264 and I get a file size estimate that reads 324mb, but the output turns out as GB's of data. Included is a screencap for reference. Input codec was DVCPRO HD.  Thanks much in advance.

    I too have been plagued by this H264 problem for the past 2 years it seems.
    I have a suspicion that if we polled the users experiencing this effect that
    it would result they all use custom or modified Display Profiles in the Display System Preferences.
    My temporary (and somewhat silly workaround) has been to change my display profile to the
    standard "Cinema HD Display" instead of my user-created "Cinema HD Display Calibrated" profile.
    It does alter the gamma of my display to a unpleasing value, but after changing it, the H264 export
    works beautifully. No gamma shift at all.
    I have read all the suggestions on trying the quicktime "filter then colorsync" export and always got unsatisfactory results. My silly workaround always produces the best results. I just have to change the dang setting back after I export so my eye dont burn out of my skull.

  • H.264 gamma and/or color off

    Anything I export as h.264 using QTPro looks washed out and the colors are off. Is there any way to tweak the export settings to correct this?

    I have been spending the better part of 2 days trying to figure this out. So far I have learned that Quicktime is displaying a gamma shift in the rendered video and that the actual file is okay, it is quicktime that is messing it up. This also goes for anything that uses quicktime, like safari, itunes, and similar players that use the Core Video hardware acceleration. Computers or Players that don't use hardware acceleration will show the same file correctly when played. But of course this is still an issue for anyone viewing your video on another computer with hardware acceleration enabled. To them your video will look faded.
    It happens far worse on windows machines where the gamma is set to 2.2 (my mac was set to 2.2 until I found this nasty H.264 bug in quicktime rendering.) In the 2.2 gamma environment the shift in brightness is very pronounced. In the 1.8 mac gamma environment, it is less pronounced but still problematic enough that many of the studios that I know won't use Quicktime or the H.264 codec until this bug is corrected.
    This problem is documented all over the web and it has caused major headaches for a lot of people for somewhere around 3 years. So far Apple hasn't done anything to fix it (or can't fix it) even though it is a persistent problem, especially for people who calibrate their monitors or people on PC's.
    It's really frustrating and after hours of scouring the net for an acceptable solution, I still haven't found anything that doesn't involve simply not using quicktime or h.264. Here is one (partial) solution I found:
    +This tip from Mitch Gates:+
    +As you may have noticed, the current implementation of the H.264 compressor for Quicktime has the nasty side-effect of raising the gamma or black levels of the resulting movie file. In order to fix this you must have Quicktime Pro (otherwise the fix will not hold since you can't save the updated .mov). Here are the steps?+
    +Open the QT+
    +Go to "Window/Show Movie Properties"+
    +Select "Video Track", then click the "Visual Settings" tab+
    +At the bottom left, change the transparency to "Blend" then move the slider to 100+
    +Change the transparency to "Straight Alpha"+
    +Close the Movie Properties window, then play or scrub the QT. Your black levels should now look correct+
    +Save over old .mov+
    This is for PC's. On the mac you change the transparency to "composition."
    The problem with this solution however is that doing this disables the settings that allow fast playback (playing the movie before it is completely downloaded.) Another issue with this solution is that, while it fixes the look of the video in Quicktime, VLC player still exhibits the 'washed out' look on the same file. Finally, this "solution" isn't actually a solution at all.
    An interesting thing about this is that the video file itself is not really washed out as far as I can tell. There are a few things that point to this. One, exporting the h.264 file and changing the codec to "Animation" or "None" corrects the gamma shift and returns the colors to where they should be, but this increases file size dramatically. Second, I noticed that when I select the h.264 file and choose "get info" the preview thumbnail shows the poster frame with correct colors. Third, when I put the h.264 file online Safari shows it all washed out but FireFox shows it correctly. Strange...
    At this point I think the only viable solution is to do this:
    +MacInTouch Reader+
    +I too have been plagued by this H264 problem for the past 2 years it seems.+
    +I have a suspicion that if we polled the users experiencing this effect that it would result they all use custom or modified Display Profiles in the Display System Preferences.+
    +My temporary (and somewhat silly workaround) has been to change my display profile to the standard "Cinema HD Display" instead of my user-created "Cinema HD Display Calibrated" profile.+
    +It does alter the gamma of my display to a unpleasing value, but after changing it, the H264 export works beautifully. No gamma shift at all.+
    +I have read all the suggestions on trying the quicktime "filter then colorsync" export and always got unsatisfactory results. My silly workaround always produces the best results. I just have to change the dang setting back after I export so my eye don't burn out of my skull.+
    So it all comes down to a gamma shift on the part of Quicktime's render of H.264. You would think that after so many years of this issue going on Apple would have fixed it since they have documented that they know of the problem. A little baffling.
    If you want to research this further, as I will continue to, just type "h.264 gamma" into google and you will find a ton of fellow frustrated users trying to figure this out. Most just switch to Sorenson 3 it seems or "un-calibrate" their displays when doing the render export. None of this is perfect unfortunately and I find myself using "Animation" even though the file size is insanely huge. It is better that having upset clients telling me that the video is washed out.

  • How to Export 320x240 .mov for Web, but darker and more saturated?

    Hi, I am trying to improve my Web .mov movies.
    My goal in this thread is to learn a good way to simply set a darker black and bump the saturation.
    I don't understand what I am doing wrong because the movies on apple.com always have a good black point and great saturation and my workflow of exporting leaves my movies looking light and washed out from my original.
    I recall I have also tried Compressor with similar results.
    My monitors are hardware profiled to 2.2/6500.
    From FCP 6.05:
    File> Export> Using Quicktime Conversion
    Settings:
    H.264
    Frame rate: 10
    Key Frames Every 24 frames
    Frame Reordering checked
    Quality: High
    Best Quality MultiPass
    Restrict to 500 kbits/sec
    Filters:
    ColorSync (I am experimenting setting Source and Destination profiles to sRGB because my Sony SD footage and .tif files are not associated with my custom monitor profiles) — otherwise I have not messed around with any filters.
    Size:
    320x240 QVGA
    Sound:
    I am only switching to Mono
    If anyone has any tips using FCP I would love to hear them...

    Real friggin crazy...
    http://discussions.apple.com/thread.jspa?threadID=1358418&start=0&tstart=0
    Thank you 11th_door for posting this (it moved me forward):
    11th_door
    Posts: 28
    Registered: Jan 11, 2006
    Re: h.264 gamma and/or color off
    Posted: Mar 14, 2008 4:11 PM in response to: Dave Mauriello
    I have been spending the better part of 2 days trying to figure this out. So far I have learned that Quicktime is displaying a gamma shift in the rendered video and that the actual file is okay, it is quicktime that is messing it up. This also goes for anything that uses quicktime, like safari, itunes, and similar players that use the Core Video hardware acceleration. Computers or Players that don't use hardware acceleration will show the same file correctly when played. But of course this is still an issue for anyone viewing your video on another computer with hardware acceleration enabled. To them your video will look faded.
    It happens far worse on windows machines where the gamma is set to 2.2 (my mac was set to 2.2 until I found this nasty H.264 bug in quicktime rendering.) In the 2.2 gamma environment the shift in brightness is very pronounced. In the 1.8 mac gamma environment, it is less pronounced but still problematic enough that many of the studios that I know won't use Quicktime or the H.264 codec until this bug is corrected.
    This problem is documented all over the web and it has caused major headaches for a lot of people for somewhere around 3 years. So far Apple hasn't done anything to fix it (or can't fix it) even though it is a persistent problem, especially for people who calibrate their monitors or people on PC's.
    It's really frustrating and after hours of scouring the net for an acceptable solution, I still haven't found anything that doesn't involve simply not using quicktime or h.264. Here is one (partial) solution I found:
    This tip from Mitch Gates:
    As you may have noticed, the current implementation of the H.264 compressor for Quicktime has the nasty side-effect of raising the gamma or black levels of the resulting movie file. In order to fix this you must have Quicktime Pro (otherwise the fix will not hold since you can't save the updated .mov). Here are the steps?
    Open the QT
    Go to "Window/Show Movie Properties"
    Select "Video Track", then click the "Visual Settings" tab
    At the bottom left, change the transparency to "Blend" then move the slider to 100
    Change the transparency to "Straight Alpha"
    Close the Movie Properties window, then play or scrub the QT. Your black levels should now look correct
    Save over old .mov
    This is for PC's. On the mac you change the transparency to "composition."
    The problem with this solution however is that doing this disables the settings that allow fast playback (playing the movie before it is completely downloaded.) Another issue with this solution is that, while it fixes the look of the video in Quicktime, VLC player still exhibits the 'washed out' look on the same file. Finally, this "solution" isn't actually a solution at all.
    An interesting thing about this is that the video file itself is not really washed out as far as I can tell. There are a few things that point to this. One, exporting the h.264 file and changing the codec to "Animation" or "None" corrects the gamma shift and returns the colors to where they should be, but this increases file size dramatically. Second, I noticed that when I select the h.264 file and choose "get info" the preview thumbnail shows the poster frame with correct colors. Third, when I put the h.264 file online Safari shows it all washed out but FireFox shows it correctly. Strange...
    At this point I think the only viable solution is to do this:
    MacInTouch Reader
    I too have been plagued by this H264 problem for the past 2 years it seems.
    I have a suspicion that if we polled the users experiencing this effect that it would result they all use custom or modified Display Profiles in the Display System Preferences.
    My temporary (and somewhat silly workaround) has been to change my display profile to the standard "Cinema HD Display" instead of my user-created "Cinema HD Display Calibrated" profile.
    It does alter the gamma of my display to a unpleasing value, but after changing it, the H264 export works beautifully. No gamma shift at all.
    I have read all the suggestions on trying the quicktime "filter then colorsync" export and always got unsatisfactory results. My silly workaround always produces the best results. I just have to change the dang setting back after I export so my eye don't burn out of my skull.
    So it all comes down to a gamma shift on the part of Quicktime's render of H.264. You would think that after so many years of this issue going on Apple would have fixed it since they have documented that they know of the problem. A little baffling.
    If you want to research this further, as I will continue to, just type "h.264 gamma" into google and you will find a ton of fellow frustrated users trying to figure this out. Most just switch to Sorenson 3 it seems or "un-calibrate" their displays when doing the render export. None of this is perfect unfortunately and I find myself using "Animation" even though the file size is insanely huge. It is better that having upset clients telling me that the video is washed out.

  • Problem exporting Premiere Pro CS5.5 projects with still photos and h264 video

    I'm a longtime Final Cut Pro user and evaluating Premiere Pro for my workplace before making the switch. I have been running into several problems when I try to export raw h264 video from a Canon 5D combined with still images on a Macbook Pro. Either I receive an error in Premiere Pro saying, "Error compiling movie. Unknown error." or Adobe Media Encoder appears to continue exporting (the time elapsed bar continues to move) even though the time remaining stays frozen once it hits a photo it doesn't like. It's not always the same photo.
    I've spent several days trying to troubleshoot the issue, including batch resizing all photos to 1920 wide (to match the video settings), and it hasn't work. The sequence is currently set to render in ProRes 422. I've also tried HDV 1080p30 and MPEG-4. I cannot find any consistency with the errors. Occasionally an export will work, but every couple still photos will look like green static. I've also tried batch converting the photos in Photoshop to PNG and GIF without any luck. I'd include my default export settings but I've pretty much tried it all. I'm just trying to figure out what's causing the error since the message is very vague.
    Couple other notes:
    There's plenty hard drive space available for export
    I can export the DSLR video (h264, 1080p30) without still photos no problem
    I can edit the same still photos and video in Final Cut with no problem
    I have the same problem with auto-save on and off
    I tried re-installing production premium, deleting the preference files and cleaning the media cache - no luck. I also tried exporting under a different user account and it wouldn't work.
    This is driving absolutely crazy. I'm affraid to use PP on deadline because I don't see any issues until it's time to export. Any ideas would be greatly appreciated. Thanks!
    - McKenna

    Thanks Todd. Your questions were actually very helpful. I'm using a Macbook Pro with an Intel Core i7 processor and NVIDIA GeForce GT 330M graphics card. I'm running OS 10.6.8 and have the latest updates installed.
    When I disabled the GPU acceleration, I was able to render and export without a problem. The problem only occured when using the GPU acceleration and mixing h264 with still photos. It also affected both rendered previews and the final export. I'm assuming its a support issue with the graphics cards, but it would be great if you had any other ideas. I appreciate your help.

  • H264 Export Problems

    I'm trying to export a slideshow from ProShow Producer to my Apple TV. When I export from Producer using the standard "Export for Device - Apple TV" then the audio (music & sounds) don't synch correctly with the slides. Depending on the length of the show, the audio ends early.
    With experimentation, I discovered that the sync problem does not exist if I export using h264. Using the documented Apple settings, I'm using the Create Output -> Create Video feature in producer. I have the video export settings at H.264 with 1280 x 720 @ 24 frames a second at Normal Quality. I have the latest updates for both ProShow and AppleTV.
    When I copy the resulting file to iTunes I receive the message "<FILENAME> was not copied to the Apple TV <APPLETVNAME> because it cannot be played on this Apple TV." When I use a "Quality" on the h264 at "70" the file size of the output is 415MB.
    Now here's the kicker, when I change the "Quality" setting to "50", the file will transfer to the Apple TV. But the problem here is that the quality is so poor it won't work for my application. Apple TV will also accept a high quality version as long as it's short (like 20 seconds).
    Given this information, the transfer problem appears to be a file size issue. I've done searches on the forum and some folks say it won't take files larger than 2GB, but these files are 1/4 that size. If you have any suggestions, I'd really appreciate it!

    >What version of Premiere Pro? I.e., have you installed the recent updates?
    5.0.3
    >What operating system?
    OSX 10.6.6
    >What kind(s) of source footage?
    Canon 7D HDSLR MPEG Movie. 1920X1080 Pixel Depth 32 Pixel Aspect Ratio 1.0. Still images Jpeg Files. Image Size 2808x1872. Pixel Depth 24 Pixel Aspect Ratio 1.0
    >What is the exact text of the error message?
    Error Compiling Video Unknown Error
    >Has this ever worked before?
    It sometimes works when exporting to the default Quicktime format and preset but with nothing else.
    >What other software are you running?
    At the time of export only Bridge and nothing else. As far as what other software is on the computer, I have the standard stuff on a Mac with iLife 11, Quicktime, iTunes, etc. I have Logic Studio Installed, Toast, ElGato Video Capture, Plural Eyes for Premiere and Microsoft Office for Mac.
    >Do you have any third-party effects or codecs installed?
    Not that I am aware of
    >Tell us about your computer hardware.
    Mac Pro 2xQuad-Core (8 core) Intel Xeon
    2.4Ghz
    16GB RAM
    NVIDIA Quadro 4000 for Mac Graphics Card
    OS on 600GB WD Raptor Drive 10,000 rpm
    VIdeo and Audio Assets on three WD 1TB Hard Drives 7200 rpm set at RAID 5

  • H264 encoding settings - problems with FLV/F4V conversions and playback... HELP!!!

    I do a lot of LIVE ENCODING and have been struggling with FMLE. I own the Adobe Creative Suite of applications and am pretty familiar with working with compatible/required formats, etc.
    We have been primarily using VP6/mp3 for encoding. Most of our work is SD. We also always seem to have trouble when trying to encode the FLV file to another format, audio always seem to be out of sync, but sometimes it works...
    Do you know why that would be regarding the FLV audio falling off sync when encoding to another format, such as MOV? Also, when we try to play back the FLV, the audio sounds garbled up and only plays well in Adobe Media Player.
    I keep hearing H264 encoding will provide better video, but I just can't get that to work. Also, why is it that my entire CS4 suite of applications can't read or playback the F4V file- that's unacceptable from Adobe, just a big huge pain the butt... I've had to buy several cheapie applications to try and read F4V files and try to convert it, except that converting F4Vs seems to be a hit-or-miss.
    What should I be using to playback and convert F4Vs? I also heard changing the extension to MP4 works, but I haven't seen that work, not even once. The cheap video conversion apps I have that read F4Vs are: FFMPEGX and Wondershare (Youtube). Sometimes they open F4V, but not most of the time... 
    I am using a super fast new Macbook Pro i7, 8GB ram (not the thunderbolt/usb3), CPU always runs smoothly and effectively.
    Also, I always use the Canopus ADVC-110 as my transcoder. I do both video via Firewire IN or Composite IN, then Firewire OUT into the Mac encoder. FMLE sees it ok, but I wonder if this device might be my problem.
    VP6 settings are as follows:
    VP6 video / MP3 audio
    300 to 500k video
    30 fps
    640x480 in/out
    44100hz audio
    56k audio
    We want to start using H264 encoding settings, but in my experience trying it out, the output file is ALWAYS PROBLEMATIC. Also, when testing a live stream, the audio seems to fall off sync with the video.
    I am looking for your recommendations on the H264 settings I should try. Most of my events are simple meetings with 1 to 5 speakers, mostly talking heads. We rarely encode high motion video, but I would also like to be able to adjust H264 settings for both talking heads and medium to high motion without (any) frame drops.
    I have tried streaming to multiple/different Flash Media Servers, archived only to file, and H264 results seem always bad.
    Any recommendations from professionals in the live streaming arena are much appreciated. I thank you for your time in advance.
    Thank you!
    Hugo

    Hello Hugo
    Sorry to know that you are facing these kind of issues, let me try to reply and understand issues one by one.
    >>We have been primarily using VP6/mp3 for encoding. Most of our work is  SD. We also always seem to have trouble when trying to encode the FLV  file to another format, audio always seem to be out of sync, but  sometimes it works...
    -- Which application you are using to convert FLV to other format?
    -- Is these any Audio - Video sync issue when you play FLV file in Adobe Media Player? if NO, it means FLV file created properly.
    >> Do you know why that would be regarding the FLV audio falling off sync  when encoding to another format, such as MOV? Also, when we try to play  back the FLV, the audio sounds garbled up and only plays well in Adobe  Media Player.
    -- Which application you are using to convert FLV to MOV? if FLV playabck fine and without a/v sync issue, it should convert MOV with a/v sync.
    -- It depend on audio codec selection by Media player or correct audio codec not installed for media player. Install appropriate audio codec to play in other media player if you dont want to play in Adobe Media Player.
    >> I keep hearing H264 encoding will provide better video, but I just can't  get that to work. Also, why is it that my entire CS4 suite of  applications can't read or playback the F4V file- that's unacceptable  from Adobe, just a big huge pain the butt... I've had to buy several  cheapie applications to try and read F4V files and try to convert it,  except that converting F4Vs seems to be a hit-or-miss.
    >> What should I be using to playback and convert F4Vs? I also heard  changing the extension to MP4 works, but I haven't seen that work, not  even once. The cheap video conversion apps I have that read F4Vs are:  FFMPEGX and Wondershare (Youtube). Sometimes they open F4V, but not most  of the time...
    -- Adobe Flash Media Server version 3.5 and later and Adobe Flash Media  Live Encoder 3 can record content in MPEG-4 (F4V) format using an  industry-standard recording technology known as "fragments" or "moof  atoms." Some MPEG-4 compatible tools and players do not support moof  atoms.
    The F4V Post Processor tool aggregates the information from all  the moof atoms into a single moov atom and outputs a new file." You can download the tool from above location: http://www.adobe.com/products/flashmediaserver/tool_downloads/
    Thanks

  • Problems importing HD H264

    Hi...
    Im making HD-DVD, just 8 min long, a loop...without menus, just the track... 720p ntsc... when im try to import the 8 minutes long asset previously compress in Compressor (i try with several diferents configurations, the standards and a couple more w less bitrate) DVDSP (w the last update) start to import the file, in the middle of the process the H264 it disappears from the assets list. no error message, no nothing...
    i try w/ one minute h264, w the same settings and same original 720 material, and no problem...
    any idea?
    thanks, guys and girls,
    Jim!

    lost in translation..
    when you choose 'File/New' there's a drop-down menu 'video format' which offers
    DV
    DV-widescreen
    HDV 1080i
    HDV 720p
    MPEG-4
    iSight

  • Premiere CC h264 rendering problem

    Premiere CC is changing aspect ratio of my video, from 4:3 to 109:96, whan rendering in h264. This was not hapening with Premiere CS 5.5.

    This solved my problem. But i still don't now why is this happening. I have video that is DV 720:576 PAL pixel aspect 1.0940, when i set same parameters for encoding it changes aspect ration. But when i set pixel ration to square and stretch to fill i get correct result. H264 with correct aspect ratio. It is probably bug with encoder.

  • Problems importing h264 in AME CC

    Hello and sorry for my bad english. I have a problem with AME CC. I'm running the latest update. The problem is this : i have some h264 renders from Premiere CC, today i have to encode some low res versions from that files, so i've opened them in AME. With a big surprise....files are green. I mean...no video,only a dark green screen. Scrubbed the preview and... green screen. I have tried to open different files type such as mov,avi,mpeg2,mpeg2 dvd and AME works well. I have not tested an h264 encode from AME. What i mean is encode an h264 from AME and import it again.
    My system is totally rebuild, so i have a fresh CC apps installation.On my system i have only CC Apps and a Matrox Mxo2 Mini Max. No other sw installed. In other sw the original h264 from Premiere works well (Prelude and Premiere). They are not encoded in Matrox h264, but as standard HD 720 25p from Premiere.
    My system:
    Asus P6TD Deluxe
    Intel i7980x
    24GB ram
    2 x SSD Intel DCS 3500 (System 240GB, AE Cache 120GB)
    Asus GTX680 4GB
    MXO2 MiniMax
    Win 7 Pro SP1
    CC Apps:
    Premiere Pro
    AE
    Prelude
    Speedgrade
    AME
    Bridge
    Photoshop
    Illustrator
    Any help will be appreciated.
    Best regards,
    Roberto

    Ok,i've made other tests and everything works well. h264 encoded from Premiere are seen by AME. So....i don't know why only three files (they are old and encoded before the system rebuild) show the green screen problem. I don't want to investigate more since everything works very well. I apologize for the incovenience and look forward for the October update!
    Bests,
    Roberto

  • H264 progressive / buffering problem - Media Encoder CS3

    I am exporting using adobe media encoder CS3 with the following settings:-
    Format: h264
    Video codec: MainConcept H.264 Video
    Frame height/width 640 x 360
    Frame rate 25fb
    Fields order - None (Progressive)
    Pixel aspect ratio: Square pixels
    Profile:High
    Level:4.1
    Audio:ACC, 128 (Kbps), 48Khz, Stereo
    Bitrate settings:VBR, 2 Pass, Target 2.00, Max 4.00 (Mbps)
    Stream compatability:psp
    The files are being played on the web via the Akamai player via HTTP progressive download.
    When the file is initally loaded it buffers the WHOLE file instead starting automatically - obviously this is is not acceptable when playing long files - having to wait for the whole file to buffer before it starts playing. I have used free MediaCoder to produce H264 and not had this problem - but to do this i have to export and intermediate avi file from premier and then encode again - however i am not so pleased with the encoding quality and would prefer not to have this extra step in the process.
    I have found this fix someone has made to correct the files once exported from Adobe Media Encoder CS3 - 'QTIndexSwapper2' - this works well - files play and start with continuous buffering - but again its an extra step (i have a lot of file to export - just want to export with Adobe media encoder direct to web using the built in FTP function)
    Please could someone advise on the correct setting for exporting from Adobe Media Encoder CS3 - so that file start immediatly on loading instaed of buffering the whole file.
    Many thanks indvance

    Hi,
    Thanks for posting that link...some interesting points and comments at the end...re: quicktime "save as" and streamclip ( free ).
    I don't do what you're doing ... though I've noticed if I put samples of video for web on my website for people to check out they always DL fully before playing...so I usually tell people to just save to disk first and then play the video...
    Anything I uploaded to YouTube gets converted by them and plays right away and beyond that I've had no need to get into this subject.
    Good Luck and if you find out more useful info let me know...others could benefit later from your solutions.
    Rod

  • Problems with H264 encoding -- corrupted files...

    In Media Encoder CS5 I tried to export my Premiere Pro CS5 sequence with H264 encoding(30 fps, progressive, CBR 6 mbps, 640 x 480). Audio(AAC,  48 kHz, 256 kbps). It have made a corrupt video file(with 2 GB size, and it should be ~3,5 GB). I tried to re-export with these settings, and now the size was 1045 MB. Again corrupted file, it cannot be played... The Media Encoder says that there is no errors, the rendering was successful. After several other tries with different settings, I cannot render my movie.
    What can I do?
    Thanks for help!
    Daninet

    Hello all,
    This is an old thread, but it's an old problem that I'm concerned may still be continuing.
    We're moving from 3.2 to 4.1. While copying our applications from 3.2 to a test 4.1 installation, we did a static file export for "All static files" from 3.2 and did an import to 4.1. We're seeing the same behavior that I and others have reported in the past - any static files that are javascript are corrupted when "all static files" was chosen. Exporting/importing each javascript static file individually appears to work fine.
    If the bug was in 3.2 in that it was generating a corrupted export file when "all static files" is chosen, then I'm not concerned - we're moving from 3.2 anyway. But, if the issue is in the import then it must still exist in 4.1 and that would be a concern.
    Does anyone know if this was a recognized bug in 3.2 and has since been corrected?
    Thanks!
    John

Maybe you are looking for