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.

Similar Messages

Issue with encoding while reading email msg from pst

I have a pst and I have issue with few messages which has russian characters in it, when i open the email it shows garbage values. But when i go to OtherActions->Encoding from the email menu option I see that the Encoding was set to "Cyrillic (KOI8-R)",
I have to change the Encoding to Unicode (UTF-8) inroder to read the email correctly. Also observed that this encoding is different for different emails from same pst.
Can I change the encoding to Unicode (UTF-8) for reading the email message so that i dont get the issue for any email (I know there are options to set default encoding for sending emails but could not file an option for reading the email in a specific
encoding.)

Hi Srikanth,
Did someone get back to you on this?
Or did you already find a resolution on this. In that case can you please share?
Thanks,
Sudarshana

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?

Issues with encoding a Dolby 5.1 soundtrack

The problem we're having is with getting DVD Studio Pro to accept a Dolby 5.1 suround audio stream.
All the audio for this project has been to an audio post facility to be mixed, and they've sent back individual files for each channel - so for the main program, 2 seperate files for left and right, and 6 separate files for the 5.1 surround. So the problem I have is two fold:
1.) I've come to the conclusion (possibly wrongly) that for DVD Studio Pro I need to have 1 multiplexed file for each audio stream ie 1 for the 5.1 surround and 1 for the stereo. I've reached this conclusion because outputting the original sound (which was stereo left and right) from Final Cut Pro through Compressor gives me a single audio file. So... how do I multiplex the 6 surround files into 1 for DVD Studio Pro? I can do the stereo by re-importing into Final Cut and outputting through compressor, but Final Cut has no facility for 6 channel surround (as far as I can tell)
2.) If my presumptions in 1.) are right I'm not sure how best to set up the DVD so the user can pick between 5.1 surround and ordinary stereo options - whether I need to build a menu for this or rely on people's DVD player controls.
Dropping 8 channels of sound (2 stereo, 6 for 5.1) into the main program track of DVD Studio Pro gives too high a bit rate when building the DVD, and anyway as far as I can tell the idea is that the DVD player plays just one audio and video stream at a time - so if you have more than one presumably you have to include a script or something by which one audio stream is picked....!?
Please help!!! The manual has seemed remarkably ineffective in resolving these issues
Thanks
jON

I've come to the conclusion ... that for DVD Studio Pro I need to have 1 multiplexed file for each audio stream ie 1 for the 5.1 surround and 1 for the stereo.
This is correct.
they've sent back individual files for each channel - so for the main program, 2 seperate files for left and right, and 6 separate files for the 5.1 surround
Perfect; just what you need. If you are using DVD SP3 (or earlier) there is a little program called "aPack" included; which is a Dolby Digital encoder. It creates one .ac3 file out of the split tracks you've got. Quick precis: you drop each sound file into it and it multiplexes them for you.
Search this forum for fuller description [for example] http://discussions.apple.com/thread.jspa?messageID=1090454

Issue with Weblogic character encoding

I have struts2 based web application which works fine with tomcat server but when i deployed the application to weblogic 10.3 server it is creating following issue-
1) when i enter data in application forms with £ (pound sign), £ gets converted to ?
My Jsp Page is using ISO-8859-1 charset. please look at the snapshot from jsp page.
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1" />
I have debug the application and came to know that this data (£ sign) is converted to ? before being assigned to corresponding property in action class.
this seems to be issue with encoding of characters with weblogic server.
I have also tried to fix this issue by defining the charset in weblogic.xml file in my application as follows but it does'nt solve this issue. please see the snapshot from weblogic.xml file.
<wls:weblogic-version>10.3</wls:weblogic-version>
<wls:context-root>APMApplication</wls:context-root>
<wls:charset-params>
<wls:input-charset>
<wls:resource-path>/*</wls:resource-path>
<wls:java-charset-name>ISO-8859-1</wls:java-charset-name>
</wls:input-charset>
</wls:charset-params>
Please suggest some solution to fix this issue. thanking you in advance.

"I can not change the charset in jsp pages i.e i have to use ISO-8859-1 in my jsp page which is a must have requirment."
You are right here as the pound sign is not included in UTF-8 (did not know that sorry).
Could you try setting the page directive of the JSP to
<%@ page contentType="text/html;charset=ISO-8859-1" language="java" %>or when you are working with jspx
<jsp:root xmlns:jsp="http://java.sun.com/JSP/Page" xmlns="http://www.w3.org/1999/xhtml" version="2.0">
<jsp:directive.page contentType="text/html;charset=ISO-8859-1"/>
</jsp:root>

Issues with video playback

Seem to be having quite a few difficulties with video playback in apps, it seems often once a video has played once it doesn't want to play again.
Can anybody explain why this is happening please?

I am having the same problem. I load a video on to my IPad. If I watch part of the video and then stop, it will not loud the video portion again. When I launch it, I hear the audio, but no picture. Just black screen. If I then unload the video file, reload it...it will work, but again only the first time. Just started happening. Not an issue with encoding as for the first 3 months I never had a single problem with any of these. Also, happens whether I load the video on my IPad or watch it streaming with AirVideo.
Any answers?

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.

Issue with Pro Res sources when encoding in Media Encoder.

There seems to be a big issue with Pro Res sources in Media Encoder. I've noticed that when exporting using the 'software only' mode my graphics and titles look horrible, they are pixelated around the edges and the compression looks bad. This issue only happens when it's being made from a Pro Res source, if I make the exact same file Uncompressed this issue is resolved. If I use the 'Cuda' option (which I already know is the better option) this issue is resolved. The thing is, in a work environment not all of our systems are Cuda enabled and I would like to use Media Encoder as a exporting option overall. I love Media Encoder, it's fast and easy to use but this Pro Res issue is huge because the majority of the time we are working in Pro Res. I also did a test out of Avid Media Composer to Media Encoder, I sent a reference file referencing the Avid MXF material and the issue is gone, this seems to my knowledge to be a Pro Res only issue. The settings I am exporting to is 960 x 540 h.264 and also .mp4. This is coming from a 1080p source and yes I do have the 'maximum render quality' checked for best scaling. I understand that Software only vs Cuda and Open CL use different algorithms when scaling but this seems crazy to me that it would look this much worse.
Anyways if somebody can please look into this that would be great, this seems to be an issue where I can't continue at this moment to use Media Encoder. Making my source files Uncompressed every time to do an export is just not a real workflow I want to do.
On a side note I've also recently noticed on a clip that had text over a grey background that there are lines going all down the screen evenly when exporting to even a non scaled 1080p .mp4. Once again, this issue goes away with any format but Pro Res. The weird part is this happens even with Cuda enabled. This is why I am thinking Media Encoder is having some sort of issue with the Pro Res codec.
I am on a current new 27'' fully loaded iMac with the latest Adobe CC updates.
Has anyone else experienced this?
thank you

No, it is why advance users do not use the wizard.
Have a look at OpenOffice.org and its form creation. Once you add your fields in OpenOffice.org, just export to PDF and the form fields will be named just like you named in them in OpenOffice.org and the drop down values carry over.

Continuing font encoding and tag issues with snow leopard and CS4oI

I am looking for help with a font handling issue with snow leopard and cs4 Indesign. Despite numerous calls and hours on the phone neither Apple nor Adobe has been helpful. I have had this issue open with Adobe since oct 5 but they remain totally unresponsive to date. I need to be able to use Type 1 fonts and do the following , export a pdf from Indesign with the following attributes: 1) xml tags for stories and objects. 2) have the fonts encoded as ansi and embedded.
Some additional information - exporting to ps is not an option as it destroys the xml tags. and doesn't guarantee that the fonts won't become CID or some other odd encoding.
As it stands now,
Leopard (10.5.8) and CS3 creates ansi encoded fonts with xml tags.
Leopard (10.5.8) and CS4 creates ansi encoded fonts with xml tags.
Snow leopard and CS3 creates ansi encoded fonts and xml tags
Snow leopard and CS4 creates custom subsetted fonts and some xml tags.
If any one has any advice on how to force specific font encodings from CS4 pdf exports so that i can preserve the tags and get the correct fonts I would be grateful.

The font encoding is not a function of the OS version, but rather of how a font is internally encoded and the content you are representing with the font.
If you are seeing a difference between MacOS 10.5 and 10.6 with the same Adobe software, it probably has something to do with use of a system font that is somehow different from one version of the OS to another. InDesign does not use any of the OS' font handling software.
Assuming that the fonts are embedded, subset or not, what is your issue with whether a font is ANSI-encoded, custom-encoded, or CID-encoded? It should make no difference for purposes of workflow beyond InDesign for software that adheres to the PDF specification (including all versions of PDF from 1.3 and up to 1.7 plus ISO 32000-1 PDF and all versions of PDF/X and PDF/A).
Neither InDesign or any other Adobe application provides user choices for the encoding since it shouldn't make a difference. The encodings chosen by Adobe's core technology components are for a combination of optimization and to support proper text search, copy, etc.
- Dov

Encoding issue with " " Less than sign

Hello Experts,
I am working on Receiver Webservice scenario where I am facing issue with "<" less than sign. SAP XI system automatically replace it with "<" sign. I can see the changed value in Audit log of communication channel.
Web service is not able to accept the data and I can see error message in audit log
SOAP: response message contains an error XIAdapter/PARSING/ADAPTER.SOAPEXCEPTION - soap fault: Server was unable to read request. ---> There is an error in XML document (1, 573). ---> The specified node cannot be inserted as the valid child of this node, because the specified node is the wrong type._
When I check the payload in audit log I can see the XML structure properly but as I open it in Notepad I can see character code "<" instead of u201Cless than <u201D symbol.
Audit log XML file is as given below
<?xml version="1.0" encoding="utf-8" ?>
- <ns1:TurnaroundDetail xmlns:ns1="http://isotrak.com/webservices">
<ns1:sessionid>3f2f2592-39d5-456e-8cf2-5d7ee81402c8</ns1:sessionid>
<ns1:data><Request xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><TurnaroundDetail><PlannedJobDepartureDatesFrom="2011-03-01T12:01:23.00" To="2011-03-01T12:07:10.00"/><DepotReference DepotReference="EASTLEIGH"/><DepotReference DepotReference="CHANDLERS"/></TurnaroundDetail></Request></ns1:data>
</ns1:TurnaroundDetail>
When I open it in notepad I can see converted value
<?xml version='1.0' encoding='utf-8'?>
<TurnaroundDetail xmlns='http://isotrak.com/webservices'><sessionid>dcc4adcd-ce8f-403d-a1cf-01fcc5aab066</sessionid><data><Request xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><TurnaroundDetail><PlannedJobDepartureDatesFrom="2011-03-02T08:28:29.00" To="2011-03-02T08:38:09.00"/><DepotReference DepotReference="EASTLEIGH"/><DepotReference DepotReference="CHANDLERS"/></TurnaroundDetail></Request></data></TurnaroundDetail>
I hope this is not caused due to AnonymizerBean configured in receiver SOAP comm channel.
anonymizer.acceptNamespaces http://isotrak.com/webservices ''
anonymizer.encoding ISO-8859-1 (also tried utf-8)
anonymizer.quote ''
Could you please suggest if I can get rid of "<" character and get < less than sign? Or it is obvious behaviour by SAP XI system w.r.t Encoding and Receiver end needs to decode this character?
Note: As per Web service requirement whole XML data to be processed by webservice is populated in single Data field. As here we are populating whole XML data file in one field named data
Thanks in advance.
Vinit.

Simply typing "Test <test> test" into a frame and exporting that yields
<ParaStyle:Body>Test \<test\> test
and reading it back into ID gives the expected result.

Issues with Japanese encoding using Mail

Since recently (I would say since I updated to 10.6), I have an issue with Japanese-encoded (ISO 2022-JP) mails on my English MacOS.
I have no problem to read, edit and write answers to any mails.
However with some ISO JP-2022-JP encoded messages (sent with Thunderbird 2.0.0.23 (Windows/20090812) btw) I have the following misbehaviour:
- if I send the message and let the encoding to "automatic", Mail sends the mail in UTF-8, which I do not want since most of Japanese computer do not understand UTF-8 by default (and the receiver gets panicked: "I can not read your mail T_T !")
- if I set the encoding to "ISO JP-2022-JP", I can not send nor save the message (see [1] at the end of the post). One should note that the error message when saving is really misleading (and yes my hard-drive has a lot of space left) and it should be fixed by Apple.
- if I dig a bit deeper, I can in effect find some characters in the original message which prevent Mail to send my mail. It however does not make any sense since:
- those char were in the original message properly encoded in ISO JP-2022-JP
- those char are always very common ones
The only solution I have found so far is to delete the original message in my mail, which is very frustrating...
A sample of such mail can be found at (I removed personal info. and the mail is about a drinking party):
- http://files.me.com/trouve.antoine/73w3w9
Help would be very appreciated.
Thank you very much.
Antoine
[1] I get the following error messages:
-> try to save:
*This message can’t be saved to the Drafts mailbox.*
The message contains one or more attachments that
are too large to be saved in the Drafts mailbox. Try
deleting some attachments.
->try to send
*Invalid Text Encoding*
Some characters in your message could not be
converted to the “Japanese (ISO 2022-JP)” text
encoding. Choose a different encoding from the
“Text Encoding” menu.

You can find out about the different versions here, for example:
http://en.wikipedia.org/wiki/ISO/IEC_2022
Thank you. I feel a bit stupid for not having looked in Wikipedia at first...
I sometime wonder how could such basic problem like charset not being solved after more than 40 years of computer science...
Here is a note that addresses that problem, but I don't think it works with 10.6. Might be worth a > try:
http://discussions.apple.com/thread.jspa?threadID=121808&tstart=60
Thank for the link.
It seems to still work: new japanese mails are now sent in "ISO 2022-JP-2".
However, for messages with the header explicitly specifying "ISO 2022-JP" (which should be "ISO 2022-JP-2" on my mac) it has no influence.
The only ways I see to solve this issue would be:
i) to force "ISO 2022-JP-2" for all mails (a bit too extreme)
ii) to force the use of "ISO 2022-JP-2" instead of "ISO 2022-JP", but I do not think such precise configuration is possible
This mess appears to be due to Thunderbird which seems to mix "ISO 2022-JP-2" and "ISO 2022-JP", but I do not have any working Thunderbird to test now...

Issue with Adobe Encore CS5.1 and Matrox MAX H.264 encoding on Windows

Here's some information on an issue that we've identified with Matrox products and Encore CS5.1:
"Issue with Adobe Encore CS5.1 and Matrox MAX H.264 encoding on Windows"

Still flickering on Encore even when rendered in MPEG-2 DVD in Pemiere Pro CS5.5. Looks perfect in Premiere Pro.
Any other ideas?
EDIT: Was looking for Google for people with similar problems to me and I came across this http://forums.adobe.com/message/3959757?tstart=0
I am currently re-rendering the video in PAL DV Widescreen MPEG-2 DVD and using maximum render quality.

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.

Issue with Google Analytics Character Encoding (Contribute changes the code)

I am wondering if there are any admin settings to work around this issue. This is an issue with Contribute CS3/CS4.
Editing a page in Contribute turns encoded characters into unencoded characters. For example, turning "%3C" into "<". Encoded version has no errors.
Un-encoded characters in Google Analytics code causes Scripting Errors on each page you open in Contribute, make loading slower, and make it difficult just to browse the site using Contribute.
Specifically changing this:
<script type="text/javascript">
var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
</script>
to this:
<script type="text/javascript">
var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
document.write(unescape("<script src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'></script>"));
</script>
(I believe it is the double </script></script> that might be causing the error to pop up.)

Set the link encoding option as "Insert Links As Is", under Administer website dialog.

Terrible Quality issue with MPEG 2 (DVD- encode plz HELP!!!

Hello,
I edited something short in FCP 5 and wanted to make a DVD but the resulted mpeg-2 file has grabage all over. Not just square artefacts but a lot of problems like an old VHS maybe (but it isn't video noise either). It's more like a DV tape that would be ******.
I tried to recompress in DV and the resulting quicktime .mov file is fine. But every time I encode it in any of the DVD presets it is terrible. Also tried MPEG-1. Same.
As for the 2 pass encodes they crash my computer...
Please help Obi-Wan Compressor you are my only hope.

If you're running some flavor of Compressor 2, then try using the One Pass setting (but not the One-Pass VBR setting) at 6.5 Mbps. If you're still having issues, other things to try:
up the One Pass bit rate to 7.5 Mbps
Alter GOP to Open (from the default Closed)
Alter GOP structure to IP (from the default IBBP)
If I'm having issues with Compressor 2's Two Pass encodes, I can usually save my hide with a One Pass 7.5 Mbps Open IBBP GOP encode. If that doesn't work, Plan B is to do a One Pass 6.5 Mbps Closed IP GOP encode.
Or are you using Compressor 1?

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

Similar Messages

Maybe you are looking for