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.

Similar Messages

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.

H.264 encoding issues with Premiere Pro CC 2014

After updating to Premiere Pro CC 2014 yesterday, I see encoding artifacts on my H.264 exports.
Same source video imported into CC v2014 and v7, and exported using the YouTube 1080p 29.97 fps settings. The artifacts manifests itself as softness/blurriness in parts of the image every few seconds, especially notice the area with a red circle below.
Here are the source file (GoPro HERO3 Black Edition), the v2014 render and the v7 render.
Original: https://drive.google.com/file/d/0B2rJe0xgMTxFYXJiMjZpZ0stUzQ/edit?usp=sharing
CC v2014 render: https://drive.google.com/file/d/0B2rJe0xgMTxFQ1B0Z09GS3I0a1E/edit?usp=sharing
CC v7 render: Premiere Pro CC.mp4 - Google Drive
[Version numbers corrected.]
Message was edited by: Jim Simon

Mark Mapes wrote:
This is a known issue introduced in CC2014.0. Some h.264 encodes have blurriness or noise periodically in some areas of the frame. The problem is most pronounced in regions of the frame with very little detail, like grass or pavement--or the T-shirt in the sample frame. We are working on a fix. Before you ask when the patch will be forthcoming, I'm not authorized to even hint at the timeframe.
Unfortunately, the only real workaround is to export to a format other than h.264. If that's not an option for you, then your best bet is probably to keep working in CC7.2.2 until the patch is released.
Sorry, but thats not completely true and by far not the correct answer:
The problems with random artifacts occurred with the introduction of a new version of H264 in CS6 but there you still had the option to export with the previous H264 Version via Media Encoder.
Since the previous H264 version is not available in CC, using CC7.2.2 is not a solution either.
BTW
Updating to CC and using the new Mac Pros with Mavericks is currently a total mess - no open cl rendering, random crashes, no usable h264 ... thanks adobe!!
... but we can track masks in premiere now ... wow!

Encoding issue with Chinese and Japanese characters but not for Korean

Hi All,
I am dealing with the problem below and have tried a lot of options to correct this. Could anyone help me resolve the issue?
Some japanese text is returned to my jsp from SAP, the text looks like PTú÷»à .
When I manually set the encoding of my browser to Shift-JIS, the problem is resolved and the text is seen as １５日締当月末現金
However, I set my response.setContentType as Shift-JIS, the browser automatically selects the encoding as Shift-JIS, but my characters get displayed as ??????
I had a similar problem with Korean characters, and I used,
decodedString = new String(strToBeDecoded.getBytes("iso-8859-1"),"EUC-KR");
It worked and I did not have to use the setContentType method of servlet response. This code however does not work for either Japanese or Chinese characters.
Please let me know, if there is anyway of getting the characters right on the screen.
I am using Sun Java Application Server 8.1.
Thanks,
Priya

Get rid of legacy character encodings and just use UTF-8 all the way.
Read this to learn more: [http://balusc.blogspot.com/2009/05/unicode-how-to-get-characters-right.html].

Latest Update of Adobe Media Encoder Issue with C4D Source

Updated Media Encoder to Build 8.0.0.173 this AM when the Adobe notification came through and it now refuses to encode any project with C4D source. The issue is codec agnostic. Tried with both C4D R15 and R16. No joy. Any clue? Would like to roll back to the previous version but not sure that option is available within the uber-slick CC Adobe world.

I'm confused. You say that you updated ths morning, but then you give the version number for the previous version (8.0), rather than the current version for AME (8.1).
I just tried rendering and exporting an After Effects composition containing a .c4d scene file through AME 8.1, and it works fine for me on Windows and Mac OS.

HTML5 Encoder issue with publishing - URGENT

I am running Captivate 8 on a Mac. I have created a course with many .flv files. (These were converted from other formats, then uploaded - I did not try to add then let the Encoder convert them upon upload.)
The course publishes fine to .swf.
When I try to publish HTML5 with scalable content, I get hung opening the Media Encoder.
The message reads "Launching Adobe Media Encoder. Generating MP4."
This screen gets stuck. I have Media Encoder open currently.
I need to get this published for a client ASAP. Anyone have any ideas? Thanks for your help!

In case anyone else has this issue, this type of an error is an indicator that the files have not been properly encoded for Captivate. You will need to open Adobe Media Encoder (even if your file is already an .mp4) and encode it.

Encoding issue with pages serving from Linux Apache to Firefox

Hi,
I had a problem last year where my help files displayed as a blank page with a question mark when they were served from a Linux Apache Server to Firefox. All other browsers displayed the content perfectly fine.
I discovered that the issue had something to do with encoding. From what I understood at the time: RH 8 outputs in UTF-8 but Apache prefers UTF-16 so it tries to modify the page. Net result: Firefox can't interpret the page. I apologise if my description is terrible I never fully got my head around the issue.
To cut a long story short: I was able to fix this by chaging the encoding information at the top of each page from <?xml version="1.0" encoding="utf-8" ?> to <?xml version="1.0" encoding="utf-16" ?>
My client has produced a new version of their software this year and for some reason my Help doesn't work again, even with modified encoding information. I am assured that the Apache web server has not changed.
Does anybody have any suggestion?
Many thanks,
Alex

I think this is what I posted last year.
This is what I was
advised by the company hosting my site.
"I would therefore
conclude that the solution to this problem (on Linux systems running Apache) is
to add the AddDefaultCharset utf-8 directive to either the Apache config or the
site .htaccess file. The advantage of the latter is that it only affects individual
sites. The default Apache character set is taken from the locale file on Linux
and defaults to iso-8859-1. It is the conflict between the Apache header with
iso-8859-1 and the page character set of utf-8 that obviously causes Firefox a
problem."
In a forum post
Chrissy_Tissy added
My machine is
Windows, but this fix still worked -
some notes about making the fix visible:
1. Do the fix itself
(httpd.conf: AddDefaultCharset utf-8).
2. Restart the box
to apply the fix.
3. Once the box is
restarted, clear your cache in FireFox to make sure you don't continue to see
the cached file.
Once all this is
done you will see the output content as expected.
There is a tool to change the encoding but that does nothing more than you have already done. Maybe showing your client the above will persuade them to change things at their end.
See www.grainge.org for RoboHelp and Authoring tips
@petergrainge

Adobe Media Encoder - Issue with exporting file

When I send a file to Adobe Media Encoder and I hit queue I get an error, "could not read from source file, please check if it has been moved or deleted".
The source file location that the AME is trying to use is C:\Users\User Name\AppData\local\temp\file name.prproj
Is this file location correct?
Why is not using my scratch disk file?
How do I change the file that AME is trying to use?
I have not been able to export a video since I have purchased Premiere CS4.
Any help with this would be greatly appreciated.

If you want a quick work-around do not try exporting from Premiere, just save and exit the project after you are through editing. Open AME and under File, select Add Premiere Pro Sequence, browse for your project file and click on it once--have patience Adobe's feedback here is lousy--your sequence will finally appear in the Sequence window, click on it and then click on OK. Select your Format,.Preset and Output location. If you want to tweak your settings just click on the Settings button. Then hit Start Queue.
Do you have the project on an external removable drive?

Able to solve Mail encoding issue with a stationery?

To my knowledge there is no final work around to be sure to send multipart messages (consisting of formated text and attachement) in an encoding which will present the message on an outlook client the way you created it in mail.
In my special case the attachement is a company logo so that could be integrated in the stationery.
I tried to overcome the encoding problem by using a stationery manualy created.
The first time I was able to create a stationery with arial formated text including the company logo. When I sent that stationery with some added text and special characters it was the first time it was displayed correctly on the outlook client.
As the company font is verdana (not my decision) I made the exact same (so I thought) stationery just with verdana formated text and the same image attachemend embedded in the staionery. This resulted in the Message displayed wrong again on the outlook client the text was shown in Times New Roman. From there on I was not even able to reproduce the Arial Stationery which seemed to work. Any Ideas on what is going on with the encoding?
Stationery might not be a final solution overall as I will not be able to send addtional attachements not embedded in the stationery but still knowing that it would work might be a step in the right direction.
Robert

If I send an email with attachement to an outlook client there is shown the wron font which changes if the encoding used to view is manualy changed on the outlook client after the message is received. Any hints on that?
I don't know of any way an encoding switch could change the display font. But if you would like to send me an example I'll have a look. You have to go to your Sent folder and find a message where this happened, then do Message > Send Again and put my address (tom at bluesky dot org) in place of the original addressee.

Encoding issue with Servets

I am facing a strange issue to display non-english characters in a servlet. I have an helper class produces non-english characters as below
public String getContent()
String content = "કેન્દ્ર સરકારે ચૂંટણી નજીક આવતાં સામાન્ય જનતાને ";
char[] newch = content.toCharArray();
byte[] bytes = Charset.forName("UTF-8").encode(CharBuffer.wrap(newch)).array();
String text1 = new String(bytes);
System.out.println("Non-english content :"+text1);
return text1;
I can see non-english text on console when run standalone but when called from servlet it shows some garbage e.g.
ArticleLocalProcessor localProcessor = new ArticleLocalProcessor();
String jsonString = localProcessor.parseNeko();
resp.setHeader("Content-Type", "text/plain; charset=ISO-8859-1");
resp.setCharacterEncoding("ISO-8859-1");
PrintWriter out = resp.getWriter();
out.println(jsonString);
Output: àªà«àª¨à«àª¦à«àª° àª¸àª°àªàª¾àª°à« àªà«àªàªàª£à«
Any help

So perhaps if your characters turn into garbage, you're using the wrong character set then.
I think the only "problem" here is that you labelled this is strange, don't ever do that because it is a flight response. You need to fight - find the mistake you're making.

File encoding issues with Mac OSX?

I really love DreamWeaver and I think its the best editor our there, except for one thing - the file encoding!
I tried setting the default encoding to UTF-8 under Preferences -> New Document, but that won't cut it.
Dreamweaver always creates/saves new files as Western/ISO format, so I always have to open them up with another text editor and overwrite the file with UTF-8 format.
Is there a fix to this or a extension to download?
I'm using CS4 on Mac OSX Leopard.

CS4 should automatically save files as UTF-8. It's the default setting. You shouldn't need to do anything special.
One thing you could try is removing the Prefs file. On a Mac, it's located at <username>:Library:Preferences:Adobe Dreamweaver CS4 Prefs.

Encoding issues with web application

Hi guys,
I have this wired problem that I can't seem to understand.
I use Tomcat 6 and Eclipse 3.5.1.
when I'm debugging my project, I come to this simple line:
String str = "Hebrew word";
when I look at the code, the Hebrew word is just fine, but after the debugger commit this line, the 'str' variable holds gibberish.
my project is in utf8. I have no idea what cause this.
please advise.
EDIT:
I tried using Glassfish 2.1 to see what happens, the same thing. maybe its not the server...?
Edited by: MadUser on Feb 15, 2010 1:48 AM

Thanks but not really.
I don't think that My problem concern the HTML encoding, it looks like something else messes things up.
if I write in a simple class:
String str = "non English text";
and I see it just fine in the Eclipse editor but on run time or debug the str variable holds gibberish, I am not sure who or what part is responsible for this issue.
P.S
This project use AspectJ.
Edited by: MadUser on Feb 23, 2010 2:13 AM

Encoding issues with Instant Client and Win-1252 database

Hi,
I'm connecting to a Win-1252-encoded Oracle XE database from a Ruby on Rails application via ruby-oci8.
NLS_CHARACTERSET WE8MSWIN1252
NLS_NCHAR_CHARACTERSET AL16UTF16
When the database and the application reside on the same physical server, the application retrieves the correct characters from the tables. But if the database resides on a different machine, then I use Oracle Instant Client; unfortunately the characters I get back from the database are then incorrect ('e' instead of 'é', 'a' instead of 'à', etc.).
Is there some kind of setting (or another version of the Instant Client) that I can use to fix this encoding problem?
Thanks,
Chris.

Hi,
>>then I use Oracle Instant Client
It's possible that maybe a NLS environment variables configuration problem ... For more information, I advise you to take a look at [url http://www.oracle.com/technology/tech/globalization/htdocs/nls_lang%20faq.htm] NLS_LANG FAQ
Cheers
Legatti

Premiere and Media Encoder CC encoding issue

Hi all,
I am having an encoding issue with PP and ME CC. My video assets are fine, and on the timeline they appear how they should, but when I look at the rendered h264 video there are encoding errors in the video. I have attached two images, the black is how it should look and the white is the error. The video plays fine and then it flickers between the images shown.
It has done this on a few different videos I have rendered over the last few days and I don't know why. It also happens to a different machine on CC as well. Does anyone have any suggestions?

Hi James,
I've never seen this before. Can you give us more info? Answer all the questions on this FAQ: What information should I provide when asking a question on this forum?
Thanks,
Kevin

FTP Server encoding issues

I have an encoding issues with FTP Server of OS X ML
1. When users connected from NT machine (Windows 2008 R2, Windows 7 etc) to OS X ftp server
user cannot see cyrilic names, it looks like - РђР»РµРєСЃР°РЅРґСЂ РђРјРµР»РёРЅ
2. When user trying to create file or folder with cyrilic name system return an error "While creating Новая папка on FTP server occured error..." in meantime on Server can observe that file actualy creater BUT with strange name - %CD%EE%E2%E0%EF%E0%EF%EA%E0
Is there way set charset encoding for OS X FTP Server? or any other way to fix this from Server side?

auto complete is bash or whatever shell you are running.
ls is not bash. Different programs treating data differently.
So Vim and nano could be doing the same wrong thing ls is doing.
Each individual program is its own world and gets to mess up that world the way it wants

H264 encoding issue with FlashPlayer 11

Similar Messages

Maybe you are looking for