H.264 Video Encoding Bug Introduced?

I'm not sure if the issue is related to a fix for a previous bug, or just a new bug introduced for this player.
My original problem was with the reporting of Camera.activityLevel. It only reports 0 and 100 when encoding with H.264 in FP11+ release, Sorenson reports the results properly. I was told it was fixed in this beta, which it does appear to be
See this post: http://forums.adobe.com/message/3999479
However I now see a new problem in this beta. My application allows me to change the video settings on my H.264 encoded stream (quality, resolution, fps, etc) during the broadcast. And it works perfectly in FP11+. However, with the beta it now appears to cause problems and be broken.
Changing settings on an existing stream (it looks to be when changing from 320x240 to 640x480) causes streaks of red, green, and blue vertical lines over the video image and the aspect ratio is wrong. The image appears squished - everything short and fat like mabe it's increaing the width value, but not the height. I'm testing the beta on Windows 32bit IE7 with a Logitech 9000 and on a different machine using Windows 32bit IE8 with a Logitech C910 with the same results.
The camera.width & camera.height properties to seem to report their values properly, but the stream as viewed on the server is definitely not at the correct resolution.
Can anyone verify this or advise? This version looks like it will break my app if released so thankfully it's still a beta.
Thank you!

OK, in FP11 Beta 2 it appears you have fixed this bug (aspect ratio messed up when switching from 320x240 to 640x480), but now you've reintroduced the Camera.activityLevel bug again. It only reports 0 and 100, this was fixed in Beta 1.
To summarize:
FP 11 release
Camera.activityLevel - broken, only reports 0 and 100
Changing camera size from 320x240 to 640x480 - works
FP 11.2 beta 1
Camera.activityLevel - fixed
Changing camera size from 320x240 to 640x480 - broken, turns video from color to black and white and has a strange aspect ratio
FP 11.2 beta 2
Camera.activityLevel - broken, only reports 0 and 100
Changing camera size from 320x240 to 640x480 - works
Hopefully you'll have everything working in beta 3.
Do I need to submit a bug report for the Camera.activityLevel bug in FP 11.2 Beta 2?

Similar Messages

Anyone gotten a self encoded H.264 video to work yet?

I'd like to know if anyone out there has been able to successfully play a video encoded with H.264 that you encoded yourself (not from the music store)
I've only been able to get MPEG4 videos to work, even when I set the encoding options identical to the video output stats provided on the iPod page.

The codec is supported but it is a very odd aspect ratio and it is a very odd framerate.
The aspect ratio should be OK although it will need to be letterboxed in iMovie.
The frame rate is 6.1 frames per second. iMovie projects are usually 30 frames per second, but can be 24 frames per second at the slowest, so I don't know how it would react to something that is 6 frames per second. You rarely see something this slow unless it is from a security camera.
Also the audio is 16000 Hz. iMovie expects audio to by recorded at 48,000 Hz. The audio may work, but it will likely get out of synch with the video.
I would suggest that you get a free app called MPEG Streamclip. Here is a link.
http://www.squared5.com/svideo/mpeg-streamclip-mac.html
Drag your h.264 file into MPEG Streamclip.
In MPEG Streamclip, see if it will play by pressing the Play button (or by tapping the space bar).
If it does, use FILE/EXPORT TO QUICKTIME.
Choose Apple Intermediate Codec for compression. For Sound choose Uncompressed 48 kHz.
For Frame size choose OTHER and type in 1440x900.
For Frame Rate, try 24, and check the box that says Frame Blending. (You may want to uncheck frame blending and try that as well.)
Uncheck the box that says Interlaced Scaling. If the final result looks bad, come back and try Interlaced Scaling / Upper Field First.
Click Make Movie and save it in a place you can find it.
Then open iMovie and use FILE/IMPORT MOVIE to import the new movie you just made.
At least that is what I would try.

Flash 9 streams video encoded in H.264 question

We would like to stream the captured video from cameras to a
browser. Our DVR streams the video using RTP/RTSP and also using
HTTP. I realize the RTMP is what is used in Flash. Could you please
provide us inputs us on how we can display the streaming H.264
video coming from our DVR using Flash player.
Can I receive the video stream encoded in H.264 from a Darwin
Streaming Server (Apple/ Open Source & using RTP/RTSP) and play
it in Flash Player 9?

quote:
Originally posted by:
davemachews
We would like to stream the captured video from cameras to a
browser. Our DVR streams the video using RTP/RTSP and also using
HTTP. I realize the RTMP is what is used in Flash. Could you please
provide us inputs us on how we can display the streaming H.264
video coming from our DVR using Flash player.
Can I receive the video stream encoded in H.264 from a Darwin
Streaming Server (Apple/ Open Source & using RTP/RTSP) and play
it in Flash Player 9?
Hi Dave,
I’m unfamiliar with the Darwin Streaming Server, but I
can recommend using Adobe Flash Media Encoder 2.5 and Adobe Flash
Media Server to stream H.264:
http://www.adobe.com/products/flashmediaserver/flashmediaencoder/
http://www.adobe.com/products/flashmediaserver/

HTML5 video encoding

What are people using to encode video for HTML5? The players I have looked at want .mp4, .ogg, and .webm. Media Encoder (At least the CS5 version) doesn't do the last 2. I tried the Miro encoder, but that has no controls, and has quality issues. I'm looking for a professional solution (hopefully not crazy expensive) for OSX.

heres some info re: html5 and video and various mobile devices and also browsers.. there's 2 different pastes ..first is from a doc file I have ..then theres a txt file....the info is about 9 months or a year old ...
plenty of links in articles to follow thru
=====
This is all done without JavaScript and requires only two video encodes, one Ogg file, and one MP4 file. Instructions on how to convert your videos to these formats are provided further down this article.
It’s compatible with HTML 4, HTML5 (valid markup), XHTML 1 and additionally also works when served as application/xhtml+xml.
For a full browser compatibility list, see the Video for Everybody Test Page.
The Code
Here follows the full source code. It’s very large because it’s fully commented.
You can easily compact this down (one such example follows afterwards).
To save time you could use the Video for Everybody generator by Jonathan Neal to generate the code snippet according to your options.
Do not miss the important notes below or you will be kicking yourself after wasting hours trying to get it to work.


<video width="640" height="360" controls>
 
 <source src="__VIDEO__.MP4" type="video/mp4" />
 <source src="__VIDEO__.OGV" type="video/ogg" />
 
 <object width="640" height="360" type="application/x-shockwave-flash" data="__FLASH__.SWF">
 
 <param name="movie" value="__FLASH__.SWF" />
 <param name="flashvars" value="controlbar=over&image=__POSTER__.JPG&file=__VIDEO__.MP4" />
 
 <img src="__VIDEO__.JPG" width="640" height="360" alt="__TITLE__"
 title="No video playback capabilities, please download the video below" />
 </object>
</video>

 Download Video:
 Closed Format: <a href="__VIDEO__.MP4">"MP4"</a>
 Open Format: <a href="__VIDEO__.OGV">"Ogg"</a>

(If you would like your video to automatically start playing, check out the sample code on the test page.)
Here’s a compacted version as an example:
<video width="640" height="360" controls>
 <source src="__VIDEO__.MP4" type="video/mp4" />
 <source src="__VIDEO__.OGV" type="video/ogg" />
 <object width="640" height="360" type="application/x-shockwave-flash" data="__FLASH__.SWF">
 <param name="movie" value="__FLASH__.SWF" />
 <param name="flashvars" value="controlbar=over&image=__POSTER__.JPG&file=__VIDEO__.MP4" />
 <img src="__VIDEO__.JPG" width="640" height="360" alt="__TITLE__"
 title="No video playback capabilities, please download the video below" />
 </object>
</video>
 Download Video:
 Closed Format: <a href="__VIDEO__.MP4">"MP4"</a>
 Open Format: <a href="__VIDEO__.OGV">"Ogg"</a>

And one that auto plays: (notice the changes “autoplay” and “autostart=true”)
<video width="640" height="360" controls autoplay>
 <source src="__VIDEO__.MP4" type="video/mp4" />
 <source src="__VIDEO__.OGV" type="video/ogg" />
 <object width="640" height="360" type="application/x-shockwave-flash" data="__FLASH__.SWF">
 <param name="movie" value="__FLASH__.SWF" />
 <param name="flashvars" value="autostart=true&controlbar=over&image=__POSTER__.JPG&file=__VIDEO__.MP4" />
 <img src="__VIDEO__.JPG" width="640" height="360" alt="__TITLE__"
 title="No video playback capabilities, please download the video below" />
 </object>
</video>
 Download Video:
 Closed Format: <a href="__VIDEO__.MP4">"MP4"</a>
 Open Format: <a href="__VIDEO__.OGV">"Ogg"</a>

It’s advised you subscribe to the RSS to be kept informed of new releases in case you get caught out by new bugs introduced by vendors *cough*Apple*cough*. The version isn’t <1 for no reason.
IMPORTANT Notes
Ensure your server is using the correct mime-types. Firefox will not play the Ogg video if the mime-type is wrong. Place these lines in your .htaccess file to send the correct mime-types to browsers
Replace __VIDEO__.MP4 with the path to your video encoded to MP4 (a warning on using H.264) and
replace __VIDEO__.OGV with the path to your video encoded to Ogg.
Optionally you could also include a WebM video.
Replace __POSTER__.JPG with the path to an image you want to act as a title screen to the video, it will be shown before the video plays, and as a representative image when the video is unable to play (Also replace “__TITLE__” for the poster image’s alt text). Not all browsers support the poster attribute, it’s advisable to encode the poster image into the first frame of your video.
2. AddType video/ogg .ogv
3. AddType video/mp4 .mp4
AddType video/webm .webm
DO NOT INCLUDE THE poster ATTRIBUTE (<video poster="…">) FOR iOS 3.x SUPPORT. There is a major bug with iOS 3 that means that playback will not work on any HTML5 video tag that uses both the poster attribute and <source> elements. This was fixed in iOS 4.0, but of course for now there will still be a large number of OS 3 users. This bug does not affect use of the poster image in the flashvars parameter, which you should retain
Replace __FLASH__.SWF with the path to the Flash video player you are using. I use JW Player (download and place ‘player.swf’ in the right place), but this could be any Flash resource including YouTube. Sample code for using YouTube can be seen on the Video for Everybody YouTube Test Page
Safari buffers the video automatically even if autobuffer is absent. This has been fixed in WebKit nightlies with a change to the HTML5 spec; the “preload="none"” attribute on the video element prevents autobuffering. A current bug in WebKit causes Safari to perpetually display “loading” until the play button is clicked
The iPhone will not autoplay. This is done to save bandwidth which may cost some users.
It is not a bug, it’s a feature
HTML5 video on Android is badly broken. Resolution support varies from one handset to the next (often just 480x360), the fallback image usually doesn’t show and the code requires special adjustments. The Android emulator is completely useless as it doesn’t represent any real hardware and does not play HTML5 video. THERE IS NO WAY TO TEST ON ANDROID WITHOUT A PHYSICAL PHONE. BLAME GOOGLE.
Android 2.3 (Gingerbread) now finally supports the controls attribute, so that VfE can work, but this still leaves all previous Android versions in the lurch. Use MediaElement.js or VideoJS for better Android support.
Some web hosts, in trying to save bandwidth, gzip everything by default—including video files! In Firefox and Opera, seeking will not be possible or the video may not play at all if a video file is gzipped. If this is occurring to you please check your server / hosts and disable the gzipping of Ogg and other media files. You can switch off gzipping for video files in your .htaccess file by adding this line:
SetEnvIfNoCase Request_URI \.(og[gv]|mp4|m4v|webm)$ no-gzip dont-vary
With thanks to Bas van Bergen for this tip
There are some instances where people will simply not be able to view the video inside the web-page (e.g. Opera Mobile / Mini). It is absolutely essential that you provide download links outside of the video to ensure your message gets through
A current bug in Firefox means that when JavaScript is disabled (NoScript for example) the video controls do not display. For now, right-click on the video for the controls, use autoplay on your videos or rely on users allowing your site in NoScript
The Eolas ‘Click to Activate’ issue affects Flash in Internet Explorer 6 / 7 as the ActiveX controls are not inserted using JavaScript—however Microsoft removed ‘Click to Activate’ in a later update patch. This issue will not affect users who have run Windows Update.
Please also note that Windows XP originally shipped with Flash v6, and H.264 playback in Flash requires v9 or 10. Depending on what Flash video player you use, this may cause problems if you intend to support users with out of date Flash versions
A parsing bug in Camino 2.0 / Firefox 3.0 means that the image element inside the video element will ‘leak’ outside of the video element. This is not visible however unless some kind of background image or colour is applied to that image element. You can stop this by either wrapping the video element in another element or modifying the code from “<source … />” to “<source …></source>”. This works, but will not validate as HTML5
In IE9 beta, both the HTML5 video and Flash video underneath play at the same time. This does not occur in IE9 Platform Preview 7, which is newer than IE9 beta. It is assumed that an update to IE9 beta will fix this issue
Adding Custom Controls
Since VfE doesn’t come with any JavaScript the HTML5 video will use whatever native interface the browser provides. This is in the best interest of the user because it provides an interface best tailored to that device. For example, the iPhone always plays video fullscreen so that the edges of the video are not cut off in the browser and the user does not have to pan around to get it all in view. The iPad provides finger-friendly sized controls.
Different native video controls in Opera 10.5 and Google Chrome
Designers however don’t like the inconsistency and would like a unified set of controls. Both MediaElement.js and VideoJS use VfE and custom controls you can style how you please with CSS.
Encoding the Videos
Full instructions are beyond the scope of this article, please refer to Mark Pilgrim’s Video on the Web article for an excellent introduction to video formats and encoding instructions.
There is no restriction on the resolution of the Ogg video
The iPhone can play MOV and MPEG4 videos with a maximum size of 640x480 and only allows the Base Profile for H.264 (See Apple’s own instructions for the specifics). If your desired video is bigger than that, please read the instructions below for how to adjust the code to use hi-res videos whilst keeping iPhone compatibility
The iPad can play H.264 up to 720p, 30 FPS
Firefox will only play Ogg (WebM is also supported in Firefox 4), and it will not degrade to Flash if there is no Firefox-compatible video file
For best results I recommend including the poster image as the first frame when you encode the video
Using HD Video
If you would like to use a larger video than 640x480, you can use a QuickTime reference movie to auto-select between an iPhone compatible version and the full-size video. In QuickTime Pro use the ‘File » Export for Web…’ option to output a reference movie (you can also use Apple’s MakeRefMovie tool for finer control). You’ll have three files along these lines: “video.mov”, “video-desktop.mp4” (or m4v) and “video-iphone.mp4”. Now replace the two source elements in the code with these three: (substituting the right file paths)
<source src="video.mov" type="video/mp4"></source>
<source src="video-desktop.mp4" type="video/mp4"></source>
<source src="video.ogv" type="video/ogg"></source>
What happens here is that the browser will play the QuickTime reference movie (Safari / iPhone / iPad) which will auto-select between the desktop and iPhone versions of the video automatically. If the MOV format isn’t supported by the browser (Chrome for example), we point to the same MPEG4 video that the QuickTime reference movie uses.
A Warning About H.264
I made Video for Everybody because since I don’t have Flash installed I wanted to create a way websites could provide me access to their videos (currently needlessly trapped inside Flash) without having to lose viewers from older browsers. VfE is not a tool I would use myself (other videos on this site are HTML5/Ogg only) because of the threat that H.264 represents to freedom on the web. Websites that are already serving H.264 video to users using Flash have already made the conscious decision to buy into H.264. I am not making that decision for you with Video for Everybody.
Just be aware that if you decide to use H.264 video for commercial use then you will need to purchase a licence from the MPEG-LA. Be warned that ‘commercial use’ may also include the scenario where your website has advertisements, even though your use of video is unrelated to those adverts. If you are making any any money in any way from a page that also includes an H.264 video, then you should contact the MPEG-LA for help on licencing.
On the 27th of August 2010, the MPEG-LA announced (arguably in response to growing WebM support) that the terms of “free use” of H.264 Internet broadcast would not change in 2016. This does not change a thing.
This is similar to Nikon announcing that they will not charge you if you put your pictures up on Flickr, or HP promising that they will never charge you additionally if you photocopy something that you printed on a LaserJet.
Mike Shaver
Using WebM Video
On the 19th of May 2010 Google released the VP8 codec as open-source and royalty free with the full intent to drive broad adoption via industry backing and switching YouTube over to the new format in the long term. “WebM” is a rebranded Matroska container utilising VP8 video and Vorbis audio.
This represents major competition to H.264—Mozilla, Google and Opera have already added support into special builds of their browsers and even Microsoft have about-faced on their H.264-only policy and said that IE9 will support WebM—but only if the codec has been installed by the user. Obviously absent from any support is Apple, and this means that unfortunately codec-fragmentation will continue into the foreseeable future so that you will still need to provide more than one video encode.
Adding a WebM video to Video for Everybody is easy, just add it to the source list! It has to go below the MP4 video due to an iPad bug that ignores anything but the first source element, and ideally above the Ogg source so that browsers that play both Ogg and WebM choose the WebM video first. Here is an example source stack:
<source src="video.mp4" type="video/mp4" />
<source src="video.webm" type="video/webm" />
<source src="video.ogv" type="video/ogg" />
Note the new mime type, which you will have to add to your server.
At this extremely early stage for WebM I will not provide any help via e-mail on how to encode or use WebM video. If you don’t know how to use it already, it’s not for you—wait until support is added to your favourite tools and more information is readily available. I will update this article as the situation with WebM progresses.
================
mobile device video info
The options actually match those of the most recent iPod Video, which uses H.264 video, up to 1.5Mbps, 640 x 480 pixels, and 30 frames per second with low-complexity AAC audio up to 160 Kbps, 48kHz stereo audio. On the lower end, bandwidths up to 768Kbps, 320 x 240 pixels, and 30 frames per second are also used, known as Baseline Profile up to Level 1.3. Both options can be output with .m4v, .mp4, or .mov extensions.
iTunes. The simplest way is to use iTunes built-in converter. Apple makes it fairly simple to convert videos to play on the Apple TV or iPod, which are also conversions that can be used on the iPhone. Any video that can play in iTunes, then, can be converted to play on the iPhone, and local files can also be synced directly to the iPhone via iTunes sync conduit, making for a fairly easy process. Two downsides: first, iTunes uses a "lowest common denominator" approach, meaning that there are no customized options for encoding into H.264. Also, some users have reported a bug in the most recent version of iTunes that creates video files with no audio, so don’t toss your original video clips until you’ve had a chance to test out the new H.264-compressed video clips.
Handbrake. Handbrake is the next most-popular encoding tool for both Windows and Macintosh platforms, and it’s available in a command-line version for Linux. Handbrake does a lot more than just H.264 conversions, but for purposes of this article, Handbrake would be used to transcode an MPEG-2 transport stream or other non-H.264 formats and codecs into H.264 video files. Speed on the product is quite good, and it has the option of a single-profile conversion (like iTunes) or the ability to customize encoding or profiles and then save the tweaks for future encodings. Handbrake has made a name for itself in DVD-to-iPod conversion, so the extension of Handbrake to the iPhone is one that many users trust.
On any of the last three products, the H.264 files output from these products can be added to the iTunes library for uploading to the iPhone. For those choosing to put their iPhone-compliant videos on the web, it’s also helpful to choose hinted streaming to allow the videos to begin playing immediately rather than waiting for the entire cache to fill.
http://www.webmonkey.com/2010/05/embed-videos-in-your-web-pages-using-html5/
So, you want in on the fun? Do you want to use some HTML5 video tags on your site right now? No problem. Fasten your seat belts, as we’re about to take a tour of the wonderful world of HTML5 video.
Browser Support for HTML5
First, let’s deal with some very basic stuff, like where this will work and where it won’t. As you can see in the table below, only the latest versions of most browsers support native video playback using HTML5’s <video> tag.
HTML5 <video> support by browser: Fx 3.0 Fx 3.5 IE7 IE8 IE9 Safari 3 Safari 4 Chrome 3+ Opera 10.5
Since Firefox 3.0 and IE 7 & 8 lack any support for HTML5 video, you’ll have to come up with a fallback plan for serving video to those users. Depending on what you want to do you, could fallback first to Quicktime and then, failing that, to Flash. That’s the strategy used in Video for Everyone (note that as of v0.4, Video for everyone no longer falls back to QuickTime).
To keep things simple we’re just going to fall straight from HTML5 to Flash.
Formats, Codecs and Technicalities
The next thing you need to understand is what is actually happening when you load and play a video file in your web browser. You’re probably used to thinking of video as .mp4 or .mov files, but unfortunately it’s not that simple. The actual file formats are just containers. Think of them as a bit like a .zip file — they hold other stuff inside.
Each container holds at minimum one video track and, most likely, one audio track. When you watch a movie online, your video player (most likely Flash) decodes both the audio and video and sends the information to your screen and speakers.
Why does this matter? Well, because the process of decoding what’s inside the video container file varies. To know how to decode a movie, the player (which is your web browser in the case of HTML5 video) has to know which codec the movie was encoded with.
When it comes to web video there are two codecs to worry about: H.264 and Theora.
There’s a huge debate right now among web developers, browser makers and just about everyone else as to which codec is right for the web. We believe that a free, open codec without patent and licensing restrictions is the best solution for the web. Sadly, neither codec exactly fulfills that dream, so for now, let’s just skip the whole argument and be practical — we’re going to use both codecs.
Why? Well, have a look at the table below, which shows which codecs work where and you’ll quickly see that there is no one-size-fits-all-browsers solution. Only Google Chrome can play both H.264 and Theora.
Codec support by browser/platform: Firefox Opera Chrome Safari IE 9 iPhone Android
Ogg Theora
H.264
So, you may be thinking … if HTML5 video doesn’t work in IE7 or IE8 and it means I’m going to have to encode my videos twice, then why bother at all? Well, the best answer is simple: mobile users. If you want iPhone and Android users to be able to see your video, HTML5 is the only way to do it — Flash support is coming to Android sooner or later but for now HTML5 is the only option, and we all know Flash doesn’t run on the iPhone or the iPad.
The HTML5 Code
Here’s how to actually embed your videos. First, we encode video in both .ogv and .mp4 containers. Encoding video is beyond the scope of this article, so instead we suggest you check out Mark Pilgrim’s online book Dive Into HTML5, which has a whole chapter devoted to understanding video encoding. Pilgrim’s encoding suggestions use free software to get the job done, and in the end you’ll have two files — one .mp4 and one .ogv.
Now it’s time to unleash those movies in pure HTML glory. Here’s the code:
view source
print?
1 <video width="560" height="340" controls>
2 <source src="path/to/myvideo.mp4" type='video/mp4; codecs="avc1.42E01E, mp4a.40.2"'>
3 <source src="path/to/myvideo.ogv" type='video/ogg; codecs="theora, vorbis"'>
4 </video>
Yes, that’s it. What we’ve done here is use the <video> tag to specify the dimensions of our video, and to denote that we want to use the browser’s default controls. Then, within the video tag, we’ve added two <source> elements which link to our video files.
The “type” attribute of the <source> tag helps the browser understand which file it should load. It’s a bit of an ugly chunk of code that needs to specify the container format, the video codec and the audio codec.
In this case we’ve assumed standard .ogv and baseline encoded H.264 video as per Pilgrim’s tutorial. See the WHATWG wiki for more information on which video types you can specify.
And there you have it — native web video, no plugins required.
Dealing With Everyone Else
What about IE7, IE8 and older versions of just about any other browser? Well, for those users, we’ll fall back on Flash. To do that, we just use an <embed> tag within our video tag:
view source
print?
1 <video width="560" height="340" controls>
2 <source src="path/to/myvideo.mp4" type='video/mp4; codecs="avc1.42E01E, mp4a.40.2"'>
3 <source src="path/to/myvideo.ogv" type='video/ogg; codecs="theora, vorbis"'>
4 <object width="640" height="384" type="application/x-shockwave-flash"
5 data="path/to/swf/player.swf?image=placeholder.jpg&file=path/to/myvideo.mp4">
6 <param name="movie" value="path/to/swf/player.swf?image=placeholder.jpg&file=path/to/myvideo.mp4" />
7 </object>
8 </video>
Now any browser that doesn’t understand the HTML5 video tag will just continue on its way until it hits the object tag, which it should understand (note that the order, mp4 before ogv, is important for iPad support — Apple requires that mp4 be the first video file).
Of course for this to work you need a Flash video container. JW Player is one popular example, or you can roll your own using Adobe’s tools. Also remember that we still haven’t handled the case of an older version of Firefox with no Flash plugin installed (maybe your users are surfing your tubes with an outdated Linux machine). You can always add good old text-based links to the video files as a catch-all fix for anyone who can’t, for whatever reason, see either the HTML5 or Flash versions.
Conclusion
Embedding HTML5 video isn’t significantly more difficult than using Flash, especially if you’ve been using H.264 video files in your Flash player — which is exactly what YouTube has done with its HTML5 beta.
While we’re concerned about the licensing and patent requirements of H.264, it isn’t hard to notice that if you skip Theora and make all non-H.264 fall back to Flash, you’ve still saved yourself a considerable encoding headache. In fact, that’s probably the best practical argument against Mozilla and Opera’s refusal to support H.264.
If you’d like to use some of the more advanced aspects of HTML5 video, be sure to check the SublimeVideo player, which offers very nice JavaScript-powered set of custom controls. Also be sure to have a look at Video for Everybody, which makes for more complex code but handles just about every use case you could imagine. And there’s a handy Video for Everybody WordPress plugin as well.
http://camendesign.com/code/video_for_everybody
good luck

H.264 videos that played in Firefox 34 won't play in Firefox 35.0

We host a ton of h.264 videos in the mp4 container displayed through JW Player. We had zero problems with Firefox 34 and earlier playing these videos, the video is H.264 and the audio is AAC, the whole thing is around 500 kbit/s.
They play fine on Firefox 34, Chrome and IE but after updating to Firefox 35.0 we get an error: "Error loading media: File could not be played".
We have found a fix to get them to work in the about:config, switching "media.fragmented-mp4.enabled" to false OR switching "media.fragmented-mp4.exposed" to false will allow our videos to play. Single file mp4's will also begin to download where before we would get a "Video can't be played because the file is corrupt."
Alternatively for Mac users if they just set media.apple.mp4.enabled to False it also works fine.
Non h.264 mp4 videos will play fine.
Here is a playlist that won't play: http://media.vineyardinstitute.org/other/vi_announcement/firefox-test.html
Here is the single video file: http://media.vineyardinstitute.org/other/vi_announcement/05_kingdom_theology.mp4
Is there anything I can change on either the playlist or the video files to get this to work? Why would the h.264 files that worked in Firefox 34 NOT work in 35? I will not be able to re-encode all of the videos, it would take me months. Is this a bug with Firefox?
Also I have tried this in safe mode, tried with every plugin deactivated, I have uninstalled Flash and the videos would not play as well as reinstalling a new version of Flash and a fresh copy of Firefox 35.0
Any help would be much appreciated, we are currently directing all of our users away from Firefox till we get this resolved.
Thanks,
Kyle

Do you have H.264 codec enabled in the plugins list of Firefox?
Does this happen in the most recent version of JWplayer?
There was an error loading the media:
"Media resource http://media.vineyardinstitute.org/other/vi_announcement/05_kingdom_theology.mp4 could not be decoded. firefox-test.html
13:43:48.280 "Error playing media: " MediaError { code: 3 } jwplayer.js:11:373
13:43:48.280 "CAPTIONS([object Object])""
jwplayer("myElement").setup({
playlist: [{
image: "http://media.vineyardinstitute.org/other/vi_announcement/images/05_kingdom_theology.jpg",
sources: [
{ file: "http://media.vineyardinstitute.org/other/vi_announcement/05_kingdom_theology.mp4" }
title: "Kingdom Theology",
description: "A look at what makes VI theologically unique.",
height: 720,
listbar: {
position: 'bottom',
size: 240,
thumbs: 'false',
repeat: 'list',
width: 640,
You might also find better help with this error on the JWplayer support site:
*similar topic/error: [http://support.jwplayer.com/customer/portal/questions/6062663--error-loading-media-file-could-not-be-played-error-in-jw-player-6-while-playing-mp4-with-chrome-html5]
In that one there were two errors: needed a higher version of Flash installed and the codec issue. As you mentioned this had been narrowed down to the codec of the mp4 file. And this codec is added with the default cisco h.264 player. [https://gigaom.com/2014/10/14/h-264-support-arrives-in-firefox-thanks-to-cisco-but-h-264-web-videos-still-wont-play/]

Momentary gamma shifts in PS-CS6 composed image h.264 video

Before I finalize a bug report, wonder what others are seeing?
Having discovered the problem in a more complex scenario, I've narrowed down to a simple set of jpg images placed sequentially in a video group, and exported as an h.264 video from Photoshop PS6. All is on Windows 7 Professional SP1, all software involved completely up-to-date.
I first noticed the gamma shift using the 'High Quality' preset. It occurs with variations on Vimeo 29.97 and Youtube 29.97 presets. The gamma problem does not occur on HD 720p or 1080p 29.97 presets.
When I view the resulting video through Quicktime, I see a gamma shift for a moment on the first image, making it look washed out. After another moment, the gamma goes back to normal. On other players such as Windows Media or VLC, no such shift is visible.
Interestingly, the shift comes at 1 second when exporting to the Vimeo 29.97 preset, or 'High Quality', while at 3 seconds on Youtube 29.97. Similarly, the shift back occurs at 2 seconds, or 6 seconds for Youtube.
What the gamma shift looks like sounds like the now age-old Apple Quicktime fault on h.264. -- except it occurs only for one or a few seconds, then reverts to proper gamma, instead of continuing..
With the simple setup of single image (jpg) sequence, it occurs only on the first image. With a more complex scenario, some actual videos included, I've seen it occur on every jpg -- or on some -- in a sequence.
This is very repeatable here - 100%. Anyone else who's noticed it? I'm on the CS6 trial, and still thinking whether to purchase, or go on the Creative Cloud.
Regards,
Clive

We're seeing a worse issue when exporting in H.264 and playing in QuickTime 10.0 (Mac OS 10.6). We are using a custom size video to fit a spot on our website (398x498). When exported and played in QuickTime 10.0 the white inverts throughout the video (back and forth). The same issue is not seen when viewed in VLC or QuickTime 10.1.
This is how the video should look:
And this is how they are appearing:
But like I said, the issue is very specific to QuickTime 10.0 on Mac 10.6. VLC, Flash, Chrome, FireFox all play it correctly.

Flash Video Encoder Quit Unexpectedly

I have an Intel iMac and when I first loaded my Adobe Suite
everything worked fine, but then the Flash Video Encoder stopped
working with "Flash Video Encoder Stopped Unexpectedly" and I
cannot get it to work again. I deleted the files and reloaded the
program from the original DVD and that did not work.
When I was setting up a new user on my iMac, I tried running
the Flash Video Encoder in the other user and it ran fine, but when
I returned to the main user, it would not start and gave the same
error. I'm relatively new to Macs - a bit more than a year - so I
suspect it is some setting or preference or something that I have
wrong.
Any suggestions would be most appreciated. Thanks.
-Brian-

I am getting the exact same error on my windows vista x64.
I've also tried uninstalling and reinstalling quite a number of
times with no luck. I don't believe it is anything done wrong but
has to be some kind of bug in the installation somewhere.
Also any help would be appreciated.
Mike

N80 Gallery Bug introduced in firmare 5.0719.0.2

In case you guys from Nokia didnt notice it yet ...
There was a new bug introduced into the Gallery application of the Nokia N80 with Firmware 5.0719.0.2.
The bug looks as following:
If you open the Picture Gallery there simply wont be any pictures or videos shown (from both internal memory and memory card). All one can see are the two weblinks in the gallery.
Only thing that help to bring the Gallery back to normal condition is to reboot the phone.
Several people who have upgraded to 5.0719.0.2 have this problem. And it definitely was not there before in any other Firmware Version 3.x or 4.x.
Is Nokia already aware of this bug and will fix it in a future firmware release? It really annoys me a lot. So much that i already think of buying a new phone from another manufacturer.
Besides ... Why doesnt Nokia release the 5.0725.0.1 firmware for European N80s? Maybe the bug is already corrected in this newer firmware...

Hey
To tell the truth this is one of the most common most annoying and of course older bug from N73, N80, N91.
Later nokia introduced new gallery in N93, N93i and N91 8GB.
I discussed a tip here:/discussions/board/message?board.id=smartphones&message.id=54784&page=1
It would just **bleep** me off.Message Edited by korngear on 04-Oct-200704:31 PM

Qmaster and Flash Video Encoder 8

Can I use Qmaster to set up a render farm to encode Quicktime movies to FLVs using Flash Video Encoder? If so, does anyone know where i can find the command lines samples to se up the Macs?

http://manuals.info.apple.com/en/AppleQmaster3_UserManual.pdf
Pages 18 and 29 should be helpful.
However, it might just be easier to encode to H.264.

Flash Video Encoder conflict with Safari for Windows

I installed Safari for Windows (AMD/Windows XP) without the
options (no Bonjour) and found that it disabled Adobe Flash Video
Encoder (tries to reinstall, can't find msi, can't reinstall from
disk, 1 keeps asking for disk 1). Uninstalled Quicktime, didn't
help. Uninstalled Safari, rebooted, still can't get Flash Encoder
working.

timtro;
Many (myself included)won't be installing safari/win until
the final
release, and I suspect Adobe won't test much until then
either, so it's
probably best to report this to apple as a possible bug with
their
beta. -Tom Unger

H.264 video wont play on iphone

I went to the Apple store this weekend to check out the phone. I went to some video on the internet that I knew was H.264 encoded (for instance the movie at http://www.soothingenvironments.com/pacificrhythmsvideo.html) but it would not play on the phone. It seems to be within spec (h.264 and below 1.5 mb/s). Does anyone know why this wouldnt play or if there is additional specific requirements for video for the phone?

Yeah I've had a few video podcasts from itunes and even some videos from apple.com not play. I think it has something to do with the scale of the video that has to be with in spec, so does the audio encoding.
Here is the video spec list from apple.com:
Video
Video formats supported: H.264 video, up to 1.5 Mbps, 640 by 480 pixels, 30 frames per second, Low-Complexity version of the H.264 Baseline Profile with AAC-LC audio up to 160 Kbps, 48kHz, stereo audio in .m4v, .mp4, and .mov file formats; H.264 video, up to 768 Kbps, 320 by 240 pixels, 30 frames per second, Baseline Profile up to Level 1.3 with AAC-LC audio up to 160 Kbps, 48kHz, stereo audio in .m4v, .mp4, and .mov file formats; MPEG-4 video, up to 2.5 Mbps, 640 by 480 pixels, 30 frames per second, Simple Profile with AAC-LC audio up to 160 Kbps, 48kHz, stereo audio in .m4v, .mp4, and .mov file formats
15" SR 2.4 MBP Mac OS X (10.4.10)

Final Cut Pro, Flash Video Encoder & Flash Player

Well, let's get started.... I'm getting real frustrated with
Adobe. I emailed them about this problem two months ago and NEVER
got a response. This is extremely unacceptable product support. We
just purchased the Creative Suite Premium two months ago and have
never gotten Flash Video Encoder to properly encode a Quicktime
video exported from Final Cut Pro.
I have heard from a few on the Final Cut Pro forum on
Creative COW that there is a bug with this issue between Flash and
Final Cut Pro. Adobe doesn't seem to care if I report it, so that's
why I am here.
I create my program as usual, export a Quicktime file (not
reference video, but a full self-contained Quicktime). BTW, I have
Quicktime 7.2 on my Mac Pro Quad 3.0 with 8 gig of RAM. I open
Flash Video Encoder to make my flash files. Import the Quicktime
and select my settings which are custom. I set it to encode and
wait for the encoding to be done. It takes about 1 1/2 hours to
encode a 23 minute program. After the encode is finished, I check
the Flash file by opening it up. BTW, I also have installed a copy
of On2 Flix Exporter, which encodes Flash files, too. The On2 Flash
player is the only player that works. Adobe's Flash player opens
but it won't open ANY Flash files.
Has anyone seen this?

When I try to import it on FCPX it says "None of the selected files or folders can be imported. Change the selection and try again." and even on Compressor it either doesn't play and fails to convert, or else it plays only a the audio but once I've completed the process the outputted file doesn't play anything.
Here's a screenshot at my different attempts to convert it. I managed to get the record the video on VLC, but I can't record the audio so I tried getting only the audio form Compressor as well, but like I said the outputted file doesn't play any audio even though it's as long as the video (36 mins approx.).

Live Streaming H.264 Video on iOS using AIR

We would like to build an AIR app that plays Streaming H.264 Live/VOD videos that would work through AIR on the iOS platform.
I've seem some traffic on the forums that RTMP will work to iOS - but additionally heard that video applications that use RTMP streams will be rejected by the Apple App store.
I have seen that progressive H.264 will work - but that's not streaming or live.
HLS would work if we use the StageWebView object; however, that provides us little control/monitoring over the video inside of it; and it's not "really" integrated as a video player.
For OSMF there seems to be a 3rd-Party plugin which will allow OSMF to read HLS streams - but (from what I've heard) is incomplete because it doesn't play adaptive nor is it completely updated for OSMF 1.6.1.
I would love to be wrong here - but is there currently a way to play a Streamed H.264 Video to iOS that is non-RTMP?
I've seem little information as to if F4M streamed files played via OSMF will work on iOS.
Thanks for the info in advance.
-Will

I pasted a stripped down version of my test app below, that attempts to playback an m3u8 file. This works for me on an IPad2.
Remember to test on the device itself otherwise wont work.
Dependencies:
1. Air 3.1
2. OSMF 1.6.1
3. Flex SDK 4.6.0
renderMode="direct"
HTH
- Abey
<?xml version="1.0" encoding="utf-8"?>
<s:Application xmlns:fx="http://ns.adobe.com/mxml/2009"
 xmlns:mx="library://ns.adobe.com/flex/mx"
 xmlns:s="library://ns.adobe.com/flex/spark"
 backgroundAlpha="0"
 backgroundColor="#000000"
 addedToStage="onViewActivate(event)"
 applicationDPI="160">
 <fx:Script>
 <![CDATA[
 private var nc:NetConnection;
 private var ns:NetStream;
 private var video:Video;
 private var currentVidUrl:String;
 protected function onViewActivate(event:Event):void
 nc = new NetConnection();
 nc.addEventListener(NetStatusEvent.NET_STATUS, onNetStatus, false, 0, true);
 nc.addEventListener(SecurityErrorEvent.SECURITY_ERROR, onSecurityErrorHandler, false, 0, true);
 currentVidUrl = "http://fmsserver/hls-vod/sample.mp4.m3u8";
 nc.connect(null);
 private function onNetStatus(evt:NetStatusEvent):void
 switch (evt.info.code) {
 case "NetConnection.Connect.Success":
 ns = new NetStream(nc);
 var client:Object = {};
 client.onMetaData = onMetaData;
 client.onCuePoint = onCuePoint;
 client.onBWDone = onBWDone();
 ns.client = client;
 nc.client = client;
 var v:Vector.<StageVideo> = stage.stageVideos;
 if (v.length >= 1) {
 var stageVideo:StageVideo = v[0];
 stageVideo.viewPort = new Rectangle(0, 0, mediaContainer.width, mediaContainer.height);
 stageVideo.attachNetStream(ns);
 else {
 video = new Video();
 video.width = mediaContainer.width;
 video.height = mediaContainer.height;
 mediaContainer.addChildAt(video,0);
 video.attachNetStream(ns);
 if (currentVidUrl) {
 ns.play(currentVidUrl);
 break;
 case "NetStream.Publish.BadName":
 break;
 default:
 break;
 private function onSecurityErrorHandler(event:SecurityErrorEvent):void
 protected function onMetaData(item:Object):void
 protected function onCuePoint(item:Object):void
 protected function onBWDone():void
 ]]>
 </fx:Script>
 <mx:UIComponent id="mediaContainer"
 height="100%"
 width="100%"/>
</s:Application>

New H.264/AVC encoding for cameras

Hi All,
Please let me know, how can we activate H.264/AVC video encoding (new feature in Flash player 11 [H.264/AVC software encoding for cameras]) using actionscript 3 in AIR application, I think, it could not be by default as there are no updates available for flash builder 4.5. So, how can we pick the encoding option. Any new API or methodology for this?
In short, how to publish live stream to FMS using H.264 encoding with actionscript 3. [not with FMLE]
Any one any idea??

Hi All,
Please let me know, how can we activate H.264/AVC video encoding (new feature in Flash player 11 [H.264/AVC software encoding for cameras]) using actionscript 3 in AIR application, I think, it could not be by default as there are no updates available for flash builder 4.5. So, how can we pick the encoding option. Any new API or methodology for this?
In short, how to publish live stream to FMS using H.264 encoding with actionscript 3. [not with FMLE]
Any one any idea??

Problem in Flash CS3 video Encoder

Hi,
I am experiencing a bug in the Flash CS3 Video encoder. I
have saved an XML file with settings that I will be using for
numerous video. I have basically set the Data Rate, Frame Rate, Key
Frame Interval, Audio and Video Size. The frame rate is set to
14.98.
When I load the profile that I have saved, the frame rate
stays at 14.98, but if i hit ok, and then click on the settings
again to modify them, the frame rate goes to 'same as source' and
does not stay at 14.98. If I change the frame rate to 14.98 at this
point, it sticks. My question is, why does it go to 'same as
source', and it concerns me, that if I do not manually go in and
change the settings back to 14.98, is it encoding the video at its
current frame rate.
Here is the XML file I use for encoding:

It appears that the <FrameRate></FrameRate> node
is only saved to the XML file if you choose something other than
"Same as source". However, it's always a non-standard value.
Evidently, if you are creating your own <FrameRate> value in
a custom XML setting file, you need to multiply the frame rate by
65536. For example, if you want 24 fps in the profile, your XML
should look like the code snippet below.

H.264 Video Encoding Bug Introduced?

Similar Messages

Maybe you are looking for