Issues with h264 in AME CC

My usual workflow consists of exporting out a prores version, then using the youtube presets in AME.
Today, I encoded 2 videos into the youtube 720p 23.94 preset.
One of the videos exported fine (looks fine, file size was about 80mb), the other video ended up only being about 9mb.
the resolution was 1280x720, but the bit rate was super low.
I tried on another workstation, same thing. Tried the vimeo preset, same thing.
I exported another version of the prores file...same thing.
Exported straight out of premiere. same again.
Then I exported out of AME CS6 on a different workstation.
Everything exported fine. Although the file size was smaller than expected (38mb, the video is similar length as the 80mb version).
Also exported a match source - high bitrate h264, that one worked as expected ended up around 120mb.
Anyone else running into issues like this?

It looks like there is a bug when exporting to h.264 with 2-pass VBR. http://forums.adobe.com/message/5442913
I believe the YouTube preset uses 2-pass VBR. After selecting the preset, can you manually change it to 1-pass VBR and see if the quality improves?
And just to be clear...is the entire video being rendered? Or just a part of it?

Similar Messages

Issues with encoding in AME vs. PP CS 6 ...

I have an .avi file with SD 720x480i LFF 29.97fps .9091 originally edited from miniDV material. If I place that clip in an 1080i sequence and export with the H.264 Blu-ray format 1080i UFF 29.97fps and select multiplexing to produce an .m2t file and export it plays fine on my PC and my PS3. I tried as-is and also another variant with scale to frame.   However, if I pull that same file into AME, select the the same format and match the same preset settings, then export a .m2t that resultant file plays ok, but on my PS3 there is no audio and video has this weird stutter effect over the whole frame.   (The same thing happens if I start with a .mpeg format file with the same video characteristics.)
Please ignore the why are you putting SD into HD, etc. topic, that's not the point and I can go into the details if really necessary.   What I'm confused about is why I'm getting different results.   Is there some sort of magic that is occuring dropping into a 1080i sequence first before exporting out of PP CS6?   Or something else that I need to do in AME?
PS The reason I'm asking is I that have 57 files covering twelve years of home video I was hoping to batch convert to the above format for primary playback on PS3, PC secondary, without discs.

Ignore everything above just read from here.   The problem has been reproduced and simplified exporting from PP CS 6 only ...
I have a number of AVI and MPEG files that are SD 720x480i, lower, 29.97fps, PAR .9091.   Please ignore why I am doing the following for now. If I create a new sequence using the AVCHD 1080i30 (60i) preset, drop in this footage with no other edits, then choose export to H.264 Blu-ray 1080i with audio multiplexing to produce an .m2t file, leaving all other settings default the resultant file plays just fine on my PC with several media players and my PS3.   However, if the only thing I do differently is queue (vs. export) from PP, then the start encode button in AME, the resultant file plays ok only on some media players on the PC and on the PS3 the audio is gone and video has this pulsating hiccup behavior, very weird.   Not that his occurs for either VBR 1-pass or VBR 2-pass, but not CBR.
I do not understand why the result would vary based on queue vs. export working with a sequence from within PP CS6.    And why CBR is ok, but either VBR variant is not.
Thoughts?
PS Jeff: I thought the situation was different enough from the prior that it warranted a new discussion thread.    New readers will now go through several screens of information that can be skipped.

Having major issues with Adobe Media Encoder (AME) - exporting with weird image flickering/colour anomalies, crashing regularly, freezing during encode...!

Hi Guys
I am having some real issues with Adobe Media Encoder (AME) at the moment. It appears that I am unable to encode an h.264 for Vimeo from a Premiere Pro Project file at the moment without at least some weird image issues that are not supposed to be there. These include weird flickering, colour changes, artefacts etc. This is if I am lucky...often I am unable to get the process to complete as the application either crashes and tells me there has been a problem or it simply freezes and I have to force quit the application and often restart my machine.
The problem seems to not to just be with h.264 for the web encodes but also with BluRay h.264 as well. As yet I haven't seen if there is a problem with MPEG-2 for DVD so I will check this out too!
Does anyone else see this happening or does anyone know what might be the problem?
I thought the Premiere Pro project might have been corrupt so tried a different project but the same issues were happening here too.
Any help would be really gratefully received.
Cheers
EDIT - I have just found this online which is exactly the problem I am having! Thanks a bloody bunch Apple! 10.9.3 causing headaches for Mac Pro users | MacIssues
Message was edited by: Alex Cameron

Agreed, I now have a project to GET OUT, and AME crashes consistently 1/3 into the render. It appears to halt all processing after (real time) 00:02:30
Am seriously considering uninstalling CC as I am beginning to find other issues in some apps, and going back to CS6/MC just so I can get work out. Durn it Adobe this is AWFUL!!
Alright, let's try to be constructive instead of throwing rocks... but the frustration level is high, and I have material on deadline. Let's get with this, guys...
What OS Win7, 64-bit
What version of AME/PPro (Please be specific by getting the full version number in the About Adobe Media Encoder screen) 8.2.0.54 Ppro: 8.2.0 (65)
When is it crashing (Again, the more detail here about where it was in the encoding process the better) roughly 1/3 into the sequence, always on exactly the same frame - tried replacing the clip with something different to see if it was a timeline error, and NO EFFECT.
What is your source (PPro project or media file (what kind?)) PPro
If the source if a PPro project, does it work when exporting directly from PPro? NO
What format are you exporting to? H.264, QT, WM, tried everything my client can play.
Do other formats work? MPEG2, QuickTime, etc? NO
Have you tried with GPU rendering on? How about turning it off by switching to Software-only mode? Mine doesn't have any choice, it's software-only.
Have you tried disabling Native Sequence Loading? (AME Preferences: General > Enable Native Sequence Loading) No effect
Other things I tried: uninstalling/reinstalling AME, setting cache to a fast local disk.

H264 encoding issue with FlashPlayer 11

Hi,
When encoding live in h264 with the FP 11 then playing it live on another client (through FMS r) the video sometimes (1/3 of times) has major skips or jerks. It's almost as if the video goes back to some older keyframes and then returns to live. Same experience with non-h264 produces smooth video.
If the server (FMS ) records the video, the replay looks smooth, which is strange because I would have assumed the FP was not encoding well with H264.
Has anyone had this issue? please reply
Thank you.

Hi,
When encoding live in H264 with the FP 11 then playing it live on another client (through FMS r) the video sometimes (1/3 of times) has major skips or jerks. It's almost as if the video goes back to some older keyframes and then returns to live. Same experience with non-h264 produces smooth video.
If the server (FMS ) records the video, the replay looks smooth, which is strange because I would have assumed the FP was not encoding well with H264.
Has anyone had this issue? please reply
Thank you.

Interlacing issue with AME/Premiere CS5?

Hi,
I am having some issues with a file that I am trying to conform using AME CS5 from XDCAM-HD mxf wrapped to wmv output that I need to be able to playout of a black magic card to SDI.
The source file is 25fps PAL
If I import the mxf directly into AME (without going via Premiere), I can successfully output an interlaced file at 6Mbit CBR using the main profile and it plays out correctly on the monitor I am using to check playback.
However, I need to remove 2 channels of audio from the hires and overlay a logo. I have done this by importing the file into Premiere, making the necessary changes and exporting it to AME.
When I do this, if I chose interlaced as my output from AME the resultant file is terrible and movement is extremely jerky. If I change the output to deinterlaced I see an improvement but it is still not as good as the file that has been imported directly to AME without going via Premiere.
I need to understand (and resolve) what is happening within Premiere that is making a difference to the output file from AME.
Changing the output format to something other than wmv is not really an option at present.
I have tried changing the Interpret Footage settings in AME along with various other options. I appreciate that I may not have supplied enough information here for someone to be able to assist but if you let me know what else you need to know I will happily provide it.
Thanks

thanks for the clarification and apologies for the misunderstanding. I don't work in the video editing side of the industry so I'm not familiar with a lot of the lingo.
Unfortunately I have an absolute requirement to either use the prproj (or ideally the FCP xml option) output so that I can substitue the source media in the project and send multiple jobs to AME using an automated process.
I'm trying to understand what Premiere is doing to the hires file when it exports it that is causing the difference in the resulting output from AME when compared to submitting the hires directly to AME.
I'm just in the process of setting up a new project that only contains the hires, with no logo added, no settings changed and I am going to run that through AME using the same epr that I used on the direct import of the hires.

Linear workflow issues with Media Encoder CC 2014

I'm using After Effects CC 2014 and doesn't seem to be the option anymore to export via AE to H264. There used to be a button in the preferences to enable outdated codecs... not there anymore with CC 2014. So... I added my renders into Media Encoder. The problem is that it is not calculating my project working in Linear Workflow so all my renders are very dark & wrong colors.
Anyone find a work around for this? is there a button in Media Encoder that I need to switch on for linear workflow?

I've been validating in QT, but per your comment I opened up in VLC player as well. VLC player does playback the correct color. I attached SS of same lossless rendered video from AE open in AE, QT, VLC, and then the rendered H264 in QT & VLC from AME in one screen shot. You can see that the H264 file from AME is always just a little bit off when opened in QT or Preview mode (OSX) or uploaded to Vimeo. The rendered H264 file is just the lossless file being encoded into H264 via AME.
That's great that VLC player will playback the correct color, but when uploading to Vimeo, the color shifts as well during playback. I've never had this issue when rendering to H264 directly from AE before. I'm a little new to AME so I'm not sure if there is a setting I am missing or is there a limitation to the H264 codec where I've never noticed the slight color shift? Is there anyway to get a H264 file that will play back via Vimeo/QT without the color shift?

Issues with Quicktime in Mavericks. I cant export to quicktime codecs in After Effects Or Premiere

Hi,
I recently updated to OS Mavericks. And in the beginning I really liked the update, but I recently fired up my After Effects CC and Premiere CC to work on some animation videos I had to produce for client. And when I wanted to export my animation. I could not find my Quicktime Codec settings like. H264, Mp4, Apple Pro res or any other quicktime codec. I read some articles on issues with Mavericks/Qucktime and this export problem in After Effects and Premiere. But I could not find a solution. It used to work on 10.8.5!
I tried this... But it did not work ;-(
http://blogs.adobe.com/aftereffects/2013/08/solutions-for-problems-with-quicktim e-files-in-after-effects-cc-12-0-because-of-conflict-with-dvcprohdvideoout-quick time-component.html
I tried to uninstall perian. But did not help at all. They even discontinued the product.
Does anyone else stumbled on this problem? Or maybe has a solution? I thought of downgrading to 10.8.5 But that is not ideal because I don't have a Time machine Backup from that period or earlier. And otherwise I have to collect all my data, emails, pictures etc. I seriously could use some help!

After uninstalling and reinstalling the entire Adobe CC suite and all QuickTime components I was still dead in the water. I then tried another User account on my computer and AE and AME worked perfectly with fast startup and all QT/H.264 components in place. This established the problem was in my main User directory...
After some backing up, I deleted all Adobe and com.Adobe.whatever files from User/Library/Preferences and then restarted the computer. I then copied all Adobe and com.Adobe.whatever files from the other user folder and restarted and found that After Effects and Adobe Media Encoder were working perfectly:
https://www.dropbox.com/s/lfd3k8au6exfxqb/yes.mov
YES!!

Built in iSight issue with Vonage softphone?

I'm not certain if this is similar to the post by Francisco Viana but I've lost my built in iSight too, and as far as I can tell started after having loaded Vonage's softphone which has a known issue with the Intell processor in MacBook.
I'll remove softphone from my MacBook but is there any way to tell if this is the culprit otherwise?
John

I'm not certain if this is similar to the post by
Francisco Viana but I've lost my built in iSight too,
and as far as I can tell started after having loaded
Vonage's softphone which has a known issue with the
Intell processor in MacBook.
I'll remove softphone from my MacBook but is there
any way to tell if this is the culprit otherwise?
John
Removed softphone, then tried to see if I could find the driver in extensions, couldn't so then ran a test and got this:
090154.054092 Loading hardware rules from hardwarerulesH264-G4.plist
090154.054195 Checking H264 hardware rules
090154.054244 Satisfied rule #1 (20:640x480)
090154.054515 setLocalUserName: John [email protected]
090154.091405 Default video size is (640x480)
090154.102408 ### NEW STATE: to: VC_INIT, from: VC_INVALID
090154.103163 ### NEW STATE: to: VC_IDLE, from: VC_INIT
090154.103258 ++++++++ confStatusMapRemoveAll
090154.103311 ( ) -- mapUserIDToSecurityInfo cleared --
090154.103553 UPnP init passed
090154.103779 NATTraversal created
090154.103916 QT automatic setting = 16777216
090154.103932 Bandwidth based on QT prefs = 0
090154.108016 BWD: GotBandwidth: 481403/1335882 (up/down) @[192.168.0.2:255.255.255.0]
090154.108088 BWD bandwidth: 481 kbits up, 1335 kbits down.
090154.108130 videoNetworkCapable: 1 -- 3 max participants.
090154.108164 audioNetworkCapable: 1 -- 9 max participants.
090154.108230 vcCapabilities returns: 0x0000003f
090154.108273 VCCapAudio
090154.108308 VCCapVideo
090154.108349 VCCapMultiAudio
090154.108378 VCCapMultiVideo
090154.108407 VCCapMultiAudioHost
090154.108446 VCCapMultiVideoHost
090154.164494 Found 0 cameras:
090154.164828 Found 0 cameras:
090154.164879 selectCamera: returned 0
090154.178749 Microphone devices:
090154.179078 Internal microphone
090154.179182 Line In
090154.179266 Selected mic: Built-in Microphone / imic
090154.179404 Found 0 cameras:
090154.179506 Found 0 cameras:
090154.179543 selectCamera: returned 0
090154.181861 Microphone devices:
090154.181962 Internal microphone
090154.182056 Line In
090154.182116 Selected mic: Built-in Microphone / imic
090154.185927 Found 0 cameras:
090154.186151 Found 0 cameras:
090154.186193 selectCamera: returned 0
090154.189079 Microphone devices:
090154.189190 Internal microphone
090154.189347 Line In
090154.189418 Selected mic: Built-in Microphone / imic
090154.352672 UPnP Router Info:
- manufacturer []
- friendly name [Residential Gateway]
- model name [Residential Gateway]
- model desc [Residential Gateway]
090154.353258 UPnP: Begin TCPProc
090154.507120 UPnP: TCPProc begin loop
090155.568456 Found 0 cameras:
090155.568727 Found 0 cameras:
090155.568827 selectCamera: returned 0
090155.571801 Microphone devices:
090155.571954 Internal microphone
090155.572178 Line In
090155.572252 Selected mic: Built-in Microphone / imic

Dynamic Link (Adobe Premiere Pro to Encore) issues with burning a DVD from the project file

Hello,
I am running Adobe Suite CS 5.1 on my Mac:
2.8 GHz Quad Core
6GB Memory
I've been having issues with a few projects; using Dynamic Link, directly from my project in Premier, to send them to Encore:
When attempting to burn a DVD, Encore will 'hang up' and not burn; I rarely burn to DVD, usually I'm always encoding for web, and just always use the 'default settings' in Encore.
A few things to note:
*In my project I'm using MOV files, from a Canon 7D, and MP4 files, from a Sony EX-1.
*I am working off of 3 separate hard drives; very large projects with over 5TBs of media files.
*I noticed that after inserting a DVD, it caused one of my hard drives to eject; this happened once, as far as I know.
*This only happens when I use Dynamic Link to send to Encore, via my Premiere Pro project file.
*My Project settings are always: XDCam HD-1080p/24p
Please help.
Thanks

So you must downrez at some point in the workflow. Some users have problems and/or think they get better quality out of direct PR/AME exports than using DL for this purpose.
I would test the workflow by creating three short test sequences - one with a clip from one camera, a second from the other, and a third with both in a sequence using the same settings you are using in your edit. I would use the "drag a clip" to the new item method for making each of the first two sequences. By short I mean 30 seconds to 2 minutes with a mixture of still and action.
Export using whatever method you pick of those recommended, but use CBR 8 instead of VBR etc. Bring the resulting files into Encore. Yes, look at the files exported on the computer, and look at Encore preview, etc, but also burn to a disk and watch on multiple TVs. There are lots of issues in best quality.

Please help! Issues with file permissions on the 'Edit' file created by LR for editing in Photoshop?

I am running a Macbook Pro with Mountain Lion. I use a Netgear ReadyNas as my storage device. I can Save, Re Save, Delete and add files without any concern on the ReadyNas from within PS or LR. However when I use the 'Edit in Photoshop" command on LR. I chose the 'Edit a copy with edits', LR creates the new duplicate 'edit' file in the same directory as the original. It opens in PS, I edit as required, however when I save the file to return to LR, I am informed that the file is locked and that I need to edit settings on file or folder, even though the settings are working for all other edits etc. I have had Netgear on this for 3 hours this evening and they cannot see any issues with the setting on the ReadyNas. Does anyone know what permissions are changed or why they are changing when the file is being created by LR?
Sorry bit of a long winded one - but I hope that all makes sense?

h264 is highly compressed and might be the reason your skimming isn't smooth, it may also take a bit more time to convert. I don't have to worry all that much about space so I haven't particularly tried it and can't say whether there are any drawbacks of doing so.
If you google 'mpegstreamclip tutorials', you will see quite a few tutorials you can look at, they do tend to be specific to one task which may not exactly fit in with what you are trying to do, but looking at a few might give you a better understanding of what some options do and when to use them if at all.

Video export issues with 5D mk II video

Using a trial version I keep running into issues with video slideshow export.
I have some 1080p '24fps' video clips from the 5D II, added them to a new Slideshow, did a Custom Export to h264 with height 720 (which from memory took the width to 1152) and 24fps - I want this to play on AppleTV, but the resulting video starts ok, but has multiple sections of blank video - in QT the frame rate has also been upped to 36fps!
It also takes a ridiculous amount of time to export a short clip, but that's seems par for the course for many of Apple's apps. This is on a 2008 8x3GHz Mac Pro with plenty of RAM, though running Leopard.
Anyone done any A/Bs of performance in Leopard vs Snow Leopard - does it make better usage of multiple cores? (They all have a little activity but it's 10% or so, perhaps 1 core at 70-80%, I can't understand even if it's not using all fully why one isn't getting maxed out with the conversion process).
The slideshow export function seems incredibly buggy - it used to output using AppleTv preset with incompatible frame rates, though they may have fixed that.
Message was edited by: Alley_Cat

DLScreative wrote:
Just a thought, but 24p was just added to the markII through a firmware update.
Yes, which is why I thought it would be great for AppleTV which can only officially support 720p at 24fps (though 25fps will often work).
If I use an AppleTv preset it will now rescale to 960x540, but I want to use 1280x720.
Previously in 3.0 the AppleTV preset output 720p but at 30fps which is too high for AppleTV.
Are you sure it's not the footage? Have you tried it in FCP? Also, it maybe that 24p isn't supported in A3, but this all just conjecture on my part.
Good thought, but I would imagine QT is the engine supporting the Aperture exports, and if parameters are set correctly it should give the appropriate output.
I'll try using QT Pro and see what that does with a clip.

Issue with Dynamic Link with Premiere CC and After Effects

I'm having a strange and annoying issue with Dynamic linked clips in Premiere CC:
When I render or export my timeline the progress will stall when it hits a dynamic linked clip. It will stay stalled until I click the After Effects application and make it the active window. Once that happens the render/export resumes at normal speed.
This is annoying as I can't start a render and walk away or work on different windows, I have to babysit all the renders to make sure they go through.
Has anybody experienced this and know of any solutions?
I'm running the latest version of Premiere (7.2.1) and After Effects 12.2.0.52 on Mavericks 10.9.1 with a GTX 770 Video Card.

Does it still pause if AE is closed completely? I often experience slower AME renders from Premiere over dynamic link material when AE is open. Closing AE speeds things up. Go figure.

Any known issues with Premiere CC and imported HDV clips?

I'm having consistent difficulty with Premiere CC playback of HDV video that originated in FCP 7. This was not an issue in Premiere CS6. The problem is dropout and pixelization which is consistent, pass after pass, and occurs at the same TC location on some clips. It is almost like some clips are corrupted in a consistent manner, while others are not, and don't seem to become corrupted.
For a variety of reasons, I still shoot HDV on a Z1U, and use an old FCP7 workstation to digitize media. I then import these individual video clip files into CS6. These are clips that play correctly in FCP, Premier CS6, and in the Finder, and Quicktime Pro, but not Premiere CC.
I have Dropboxed a sample clip to my service contact at AJA, and she is reporting the same issue with Premiere CC. (The technical support at AJA is the best I've experienced in over 30 years of video production).
The same issue presents itself with HDV clips that were converted to such from .m2v via Clipwrap.
Any other types of media play correctly within Premiere CC. For example, I have a CS6 project that is nothing but After Effect CS6 anims comiled into a program in Premiere CS6; it plays perfectly. So do any media that Premiere CC puts through its own conversion or import "routine," like AVCHD. Even XDCAM clips that went into FCP via XDCAM Transfer play well.
Any thoughts?

Tim,
I would assume the clips work fine in FCP7, so you're not totally busted. Maybe try using Compressor or AME, like the other guy said, to export them in another format; I'd recommend Apple ProRes 422. Fallback is to work in FCP7, as the tapes are gone.
When I 1st posted this problem, I left for vacation. I saw briefly that someone suggested a plugin in another reply, but I haven't had a chance to pursue that yet. I'm in northern Michigan (USA) with limited access to email. I'll do some follow up this Monday when I return. Good luck!!
Sent from my iPhone
Phil Mariasy
Allied Media Group
[email protected]
419-297-2730
151 N. Michigan
Ste. 300
Toledo, OH 43604

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

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

Issues with h264 in AME CC

Similar Messages

Maybe you are looking for