we try to enable codec "opus" in isTypeSupported() to stream opus data.
but Youtube will raise an error message.
after we trace cobalt source code, cobalt didn't deliver data by AudioRenderer::WriteSample(). and we found cobalt did not compile "opus_audio_decoder.cc".
so, we are confuse about cobalt can parse opus data now.
Cobalt platform-independent code doesn't currently support Opus out of the box. I think it might not be too hard to get it working. If so, you could submit a patch to the OSS project.
Related
Playback of 1440p/2160p content with h.264 encoding from the Cobalt test suites (YT2018 spec) fail for us on Broadcom chipset. Are these test cases even supposed to work?
The Cobalt linux-x64x11 cannot play h.264 1440p and 2160p content either, and as far as I know, all YouTube content above HD is encoded with VP9.
Jan Boquist, that is expected and not relevant to the browser(or Cobalt) you use. If you have further questions about this, please reach out to your YouTube technical account manager.
As far as I have researched, Apple is loading an audio decoder based on a file extension.
I have an .m4a file which I have manually renamed to .aac extension. After that, the decoder fails to decode it, but the apple native audio player plays it!
ExtAudioFileRef audioFile;
ExtAudioFileOpenURL(url, &audioFile);
Calling this function ends up with an error.
How can I handle this situation using the Core Audio framework? Do I have to somehow configure a custom decoder? If yes, then how?
Thanks in advance.
We have integrated Chromium Embedded Framework into our Windows game to allow us to render web pages from within our application, and everything works fine, except MP4 videos.
I understand Chromium does not include this codec due to licensing issues, but can anyone provide details on how we can add support, even if we have to license a codec for it.
All the information we can find seems to be old, and the functions referred to appear to be deprecated... so we are at a bit of a loss.
All the video serving networks we have spoken to appear to serve MP4s.. so changing encoding does not seem to be an option.
Any advice would be greatly appreciated.
Thanks
Check this url
Go to menu option Features --> Html5 Audio/Video section. It mentions that Nik's build (66.0.3359.181) has supported Mp4 (and other codecs).
If there is any licensing issues with using H.264/MP4, I am not aware about it, so please check for it before using.
Keep in mind that MP4 is not a codec it's a container format. You need to support all codecs that might be contained in a MP4 file.
In a recent post on a CEF forum someone managed to do it by setting the environmental variable:
GYP_DEFINES="proprietary_codecs=1 ffmpeg_branding=Chrome"
before running the automate-git.py script.
Source: Build CEF with proprietary codecs support
I am making a application for streaming webcam. I would like to use ffmpeg to capture camera, ffmpeg as encoder and live555 as server. I know I must implement DeviceSource.cpp in live555 to encapsulate the encoder to receive frame from ffmpeg.So can anyone provide me some tutorial or example about implementing.Thanks in advanced.
Here is a good example of what you are after here:
https://www.imc-store.com.au/Articles.asp?ID=278
It is a c++ VS2010 project showing how to encode a raw RGB frame using FFMPEG, and then sending that discrete frame onto Live555 to be streamed.
The VS2010 project includes all the library and include files so it should simply be a case of unzipping, running the .sln file in VS2010, compile and run!
Also the VLC source code implements both FFMPEG and Live555, you could take a look at their code for some extra pointers!
Good luck!
In previous version you could copy files from google Chrome's folders and paste them into the Chromium files, but that doesn't work anymore. Apparently all the files have been replaced by 1 file ffmpegsumo.dll, copying that from Chrome changes nothing.
I downloaded codecs for Chromium on linux, but I find it weird that there's no way to get them for Windows.
Why don't they just add h.264 to chromium now that cisco made it royalty free?
Google has little incentive to support H.264 when they have their own, competing format WebM that they are trying to push. (Haven’t you ever wondered why such a relatively unknown format is one of the formats the YouTube, a Google subsidiary, supports natively?)
Unfortunately, as you have learned, they re-structured Chromium so that you cannot easily drop in H.264 support as you could before. What you can try instead, is to use the Microsoft plugin that lets Chromium play H.264 through Windows Media Player. Because it is a plugin, it should still work—unless Google specifically blocked it.