Database Develop

Chromecast Video - A Chrome App That Streams Local Video From Your Computer To Chrome

I've posted my Chrome App late last night and has been a big hit on Reddit. Anywho, while we've ran into a couple people with issues it's been a pretty smooth rollout.
If you want to try it, here it is. It's, rather cleverly, called "Chromecast Video" .
https://chrome.google.com/webstore/detail/chromecast-video/cnciopoikihiagdjbjpnocolokfelagl
Let me know how much you love it, hate it, and want to see your bug fixed
-----------
Known issues:
// TODO
Mat.

Great start! So far gives me about a 50% success ratio, at least with mp4 files. And some of those that start successfully die after about 30 seconds. But the ones that stream successfully are smooth.

Reddit comments thread, that should be added in OP:
http://www.reddit.com/r/Chromecast/comments/1ybzw3/chromecast_video_a_chrome_app_that_streams_local/
Could you also add download link that does not require google account login?
PS if you want to know literally everything about acidhax start HERE and dig google

Avia does that

I'm going to check this out tonight, but given that there doesn't appear to be any transcoding going on, is it safe to assume that you still can't play .mkv files with audio?
I keep holding out in hopes that I don't need to convert my huge collection of media to h.264 in an .mp4 container.

mkhopper said:
I'm going to check this out tonight, but given that there doesn't appear to be any transcoding going on, is it safe to assume that you still can't play .mkv files with audio?
I keep holding out in hopes that I don't need to convert my huge collection of media to h.264 in an .mp4 container.
Click to expand...
Click to collapse
LOL, well, if anyone here is good at NaCl development we can get some ffmpeg transcoding happening

Yet another reason to run Chrome... I may be converted yet...
BTW, added your extension to the FAQ.

It seemed to work but would stop after a few minutes

mkhopper said:
I'm going to check this out tonight, but given that there doesn't appear to be any transcoding going on, is it safe to assume that you still can't play .mkv files with audio?
Click to expand...
Click to collapse
Doesn't play mkv at all as far as I can tell. I just get a spinning circle forever if I try.

enricong said:
It seemed to work but would stop after a few minutes
Click to expand...
Click to collapse
Some users have this problem. I honestly don't know what it is, it could be a Chrome bug or a WiFi driver bug.
Edit:
All I'm really doing is creating a Webserver on the Chrome App, and the Chromecast requests media from you. It'll just drop randomly for certain people.

acidhax said:
Some users have this problem. I honestly don't know what it is, it could be a Chrome bug or a WiFi driver bug.
Edit:
All I'm really doing is creating a Webserver on the Chrome App, and the Chromecast requests media from you. It'll just drop randomly for certain people.
Click to expand...
Click to collapse
Is there an option to show debugging info or logging to try to determine the cause?

acidhax said:
All I'm really doing is creating a Webserver on the Chrome App, and the Chromecast requests media from you. It'll just drop randomly for certain people.
Click to expand...
Click to collapse
Could also be other extensions or antivirus
On this thread the tab casting problem (yes, I realize it probably uses a different mechanism, but it's still within Chrome) ended up being Adware Antivirus, and reinstallation of the Cast extension.

enricong said:
Is there an option to show debugging info or logging to try to determine the cause?
Click to expand...
Click to collapse
Not that I'm aware of..

enricong said:
Is there an option to show debugging info or logging to try to determine the cause?
Click to expand...
Click to collapse
Fixed it. Update is being processed as we speak!
Thanks

MKV plays fine, but without sound.
Also, is it possible to support subs?

acidhax said:
Fixed it. Update is being processed as we speak!
Click to expand...
Click to collapse
Confirmed - all better now. With version 0.9.6.5 all mp4 videos play without interruption.
Another minor problem: if I attempt to play a video that doesn't load successfully (for example one of my mkv files), the Chromecast remains stuck on a blank screen and I cannot cast any more videos successfully until the Chromecast Video extension is shut down and restarted. It looks like the UI is still functioning, but maybe the background http server is stuck?

DJames1 said:
Confirmed - all better now. With version 0.9.6.5 all mp4 videos play without interruption.
Another minor problem: if I attempt to play a video that doesn't load successfully (for example one of my mkv files), the Chromecast remains stuck on a blank screen and I cannot cast any more videos successfully until the Chromecast Video extension is shut down and restarted. It looks like the UI is still functioning, but maybe the background http server is stuck?
Click to expand...
Click to collapse
Guys MKV is a container, and have slim to none information about whats in it.
Really think the developer would love to know which Audio/Video codec you use
http://www.videohelp.com/tools/MediaInfo <- Download that tool and the codecs will show up, they would help the developer understanding which codecs works and not.

bormeth said:
Guys MKV is a container, and have slim to none information about whats in it.
Really think the developer would love to know which Audio/Video codec you use
http://www.videohelp.com/tools/MediaInfo <- Download that tool and the codecs will show up, they would help the developer understanding which codecs works and not.
Click to expand...
Click to collapse
Generally my mkv files are all H.264 video generated by Handbrake, the same as my mp4 files. The difference is likely to be in the audio tracks. My mkv files all have either a single AC3 DD5.1 sound track, or else an AC3 DD5.1 sound track plus an AAC stereo sound track like the mp4 files. I stopped including the AC3 DD5.1 sound track in my mp4 files because I found that many (if not most) mp4 players will only accept a single AAC stereo sound track and nothing else. I sometimes wonder what was the point of designing container file formats that allow multiple sound tracks when so many players seem to choke on files that use that capability! Even Microsoft Windows Media Player doesn't have the basic ability to select which audio track to use when there are multiple tracks.

DJames1 said:
I sometimes wonder what was the point of designing container file formats that allow multiple sound tracks when so many players seem to choke on files that use that capability! Even Microsoft Windows Media Player doesn't have the basic ability to select which audio track to use when there are multiple tracks.
Click to expand...
Click to collapse
Yes, that's the general problem with containers... Having multiple streams requires additional logic on the player's side that takes it more toward a DVD/BD player, while most media players are more simple. In some cases players "cheat" and their "support" for a container is simply "pretend it's just a raw media stream."
While it does often work, it's bad practice because the kludge fails once the container is actually used as a container.
It's much like how people often like to rename VOB files to MPG to make them "work" but run into trouble when things leave the most-simple cases as VOBs also contain other data like navigational data, subtitles, etc. A proper demux works, but of course requires actual understanding of the container format.

bhiga said:
Having multiple streams requires additional logic on the player's side that takes it more toward a DVD/BD player, while most media players are more simple.
Click to expand...
Click to collapse
Exactly! MKV was pretty much invented as a Universal Library container format to better support the different media that would normally be on a DVD/BR disc such as Multiple Language, Commentary tracks and Multiple Subtitles all in one tidy package.
But to support all that it requires Client side support that allows you to pick which tracks to actually use.
Unfortunately the player apps on the CCast are still very young and not yet mature enough to deal with this complexity as most developers are more focused on the communication and linkage needed to cast than they are with developing a full featured player on the CCast side.
This is why Subs and Multi Audio track content have hit or miss issues when sent to a CCast.
It gets even worse if transcoding is required.
And the fact that MKV can contain just about any codec it's even harder to write a transcoder profile or CCast player that can deal with it all.
There is no hardware I know of that supports MKV on chip. All the devices that play them without transcoding use software decoding built into the player. and I suspect in time someone will create a CCast player capable of doing that at some point as well as the capability to select Subtitle Overlay and Audio Track from the client side.
Once someone does that most if not all of our MKV issues will go away. Transcoding will no longer be needed and the selection of what gets seen and played will all happen where it should on the client side.

Will CC ever get native ac3 support?

Will the Chromecast ever get native AC3 support? Would it be possible to implement support for other audio codecs like ac3, in a custom rom?
Just curious, as i think this is a huge let down so far for the CC...

Linkdk said:
Will the Chromecast ever get native AC3 support? Would it be possible to implement support for other audio codecs like ac3, in a custom rom?
Just curious, as i think this is a huge let down so far for the CC...
Click to expand...
Click to collapse
Chromecast supports DD+
I don't necessarily think codec support falls in the ROM realm as much as it does in the player app.
Chromecast loads a player app to handle a specific request (that's what the whitelist is for). So even if a custom ROM were to add support for some special format, the player app would need to take advantage of that support.

No, at least not for now:
https://code.google.com/p/google-cast-sdk/issues/detail?id=192&can=1&start=100

It's really about the Player side of things that determine what Dolby it supports.
Netflix I understand does support AC3 but then again they probably paid the License fee to Dolby to use their decoding system.
Since Netflix sends it's own proprietary stream to the end user they can pretty much do things in a CCast other apps are not likely to do both because of the Money they have from subs and the proprietary creator of the stream that will be played.
Their Player already has to decode encryption so it doesn't take much to add Dolby Decode to that operation.
Google could have done us all a favor and paid the license to build full dolby support into the Hardware but I wouldn't expect them to do that until whatever second Gen CCast gets made.
Lets face facts we are all guinea pigs to test their concept and now that it has proved a success and Apps support it they will le the rest of the world in on it and when sales peter out start looking at CCast2 with wired Network and more Hardware Codec support.

AC3 passthrough support added in last Chromecast Update....

Video Player with Chromecast Support

Am I correct in thinking there is no video play with chromecast push support? I.e. MX Player, you are watching video on phone then you press cast button?
Not possible or just no app has done it yet?

Avia has paid ($2.99) CC support.
Sent from my Galaxy Nexus using xda app-developers app

There is an app called y2cast which can cast videos to the Chromecast together with an app called Moliplayer. The 1. problem of this is that everytime you turn on your TV, you have to connect y2cast with your Chromecast before you can start casting via Moliplayer and the 2. is that Moliplayer doesn't play every file format (even when you haven't connected it to the Chromecast) and is also very slow/has a lot of lag.
---------- Post added at 03:43 PM ---------- Previous post was at 03:27 PM ----------
Does Avia play every file format and can avia cast every file format to the chromecast?

There are loads of apps now that will play media from phone to Chromecast - BubbleUPnP is my personal choice, Allcast, Localcast, Avia....there are more.
They vary in their capabilities - most can't cast videos that are not encoded in a Chromecast friendly format. BubbleUPnP can with the help of a Bubble Server installed on a PC on the local network.

neu - smurph said:
There are loads of apps now that will play media from phone to Chromecast - BubbleUPnP is my personal choice, Allcast, Localcast, Avia....there are more.
They vary in their capabilities - most can't cast videos that are not encoded in a Chromecast friendly format. BubbleUPnP can with the help of a Bubble Server installed on a PC on the local network.
Click to expand...
Click to collapse
Well then you could just cast the video in a tab via Chrome. I'd love to see a solution where an android device does that, most of the devices are probably capable of doing it.

Pete1612 said:
Well then you could just cast the video in a tab via Chrome. I'd love to see a solution where an android device does that, most of the devices are probably capable of doing it.
Click to expand...
Click to collapse
Share the page to either vGet or Web Video Caster, and cast from there.
It's one extra step - sharing the link - but it works great for supported video formats.
vGet has more options and is a paid app. Web Video Caster just casts and is free.

EarlyMon said:
Share the page to either vGet or Web Video Caster, and cast from there.
It's one extra step - sharing the link - but it works great for supported video formats.
vGet has more options and is a paid app. Web Video Caster just casts and is free.
Click to expand...
Click to collapse
for thus you can also use chrome for android (free from google obviously), go to chrome://flags and turn on chromecast support

Avia does NOT work on all formats. It's a bit of a hit and miss. Some work some dont
The moment everyone is waiting for is for mx player or vlc to support Chromecast !

I think that the limitions are not in the players but in the software of ccast that can play only a few format and codecs.
Do you think that, in future, ccast will be updated and so it will play other video format? Is a feature that can be implemented with a firmware upgrade?
Thanks!

davboc said:
I think that the limitions are not in the players but in the software of ccast that can play only a few format and codecs.
Do you think that, in future, ccast will be updated and so it will play other video format? Is a feature that can be implemented with a firmware upgrade?
Thanks!
Click to expand...
Click to collapse
Yes and Maybe....
You're right in that the CCast is limited in codec and container support.
But that is really only true if the Player app that gets loaded into CCast relies on the CCast hardware to play the files.
Android itself is almost as limited as the CCast is as far as Compatible file formats are concerned but the video players we use on Android add the support for those different codecs and container types into the APPs themselves.
The same could be done on the CCast side and BubbleUPnP seems to be the one (and Only) app that has gone the farthest in doing that.
All the others seem to just send whatever format the file is in and if it isn't CCast compatible it won't play.
What needs to happen is for someone to create an MX Player type CCast Player app that can play many Container and Codec types without the need for Transcoding. Then others could potentially use that Player App (think along the lines of a JW Player type CCast Application) when sending Media to the CCast without the worry of incompatible file and codec format.
Or Google needs to create it and add it to the CCast OS as the default player.
As of now there is no option close to that...Bubble supports more container types than others and in conjunction with the Bubble Server will transcode the ones it doesn't support.
Plex seems to transcode everything that isn't directly CCast compatible and the other Player Apps we have for Android don't deal with Compatibility at all they merely send the media to CCast and it works only if it is compatible.
Perhaps in time they will add to the CCast Player side to gain more support but Bubble is so far the only one to really focus as much on the Player side compatibility expansion and features.
Plex is working on it as well but they are less focused on Compatibility due to the fact they are able to transcode everything to whatever format they want. After they get all the transcoding perfected they might turn focus into finding ways to avoid transcoding for those who have issues due to low power servers.

Asphyx said:
...
Click to expand...
Click to collapse
perfect explanation! Really thank you. I hope that this device will be supported with the right software, meaning apps, in the near future.
Thanks again.

davboc said:
perfect explanation! Really thank you. I hope that this device will be supported with the right software, meaning apps, in the near future.
Thanks again.
Click to expand...
Click to collapse
The problem right now seems to be that every App creates their own CCast Player App (called the receiver) but the DIAL protocol really doesn't require that to happen.
If the Open Source community would create a FREE TO USE Player App for CCast that any Android (or iOS app for that matter) could have the CCast load You might see a situation where all players could use that app to play to CCast and remove the need to code a Player themselves.
The only reason to code your own player then would be if you wanted to add other features like Media Info Mirroring and if the Player was Open Source it could be used inside their custom versions as well provided there is no issue with GPL license and Commercial Use.
the CCast support has come a long way since December...
I hope by next December we see more after people figure it out better.
The holdup is Google Locking it all up with the Whitelist.
I keep looking here hoping to find a developer that has decided to work on a CCast Player side to bring full client side support that others can use.
So Far Bubble is the only one focused on that side of the coding.
In the end the CCast player should support any container, Most Codecs, Client side selectable Subtitles and Multitrack Audio with Client side selection as well.
If they could add Dolby Support (not likely given the Licensing requirements) it would set the bar for all the others.

Localcast works well for me. Even let's me access and stream movies/TV shows straight from my USB stick on my Note 2 using an otg cable.
Sent from my Sinclair ZX81.

Koush tried software decoding for H.264 video - the processor ran hot enough to destroy his Chromecast, and that was using a known and mature routine.
The MediaTek processor is very good but it has limitations.
Maybe someone will take it further and succeed. I think it's more reasonable to look for more codecs on Chromecast 2, if at all.
Btw, LocalCast now lets you use your phone for headphones for stuff you're casting.

Not doubting you here...I know the Hardware is close to being an Egg Cooker even under normal usage....
But I'm curious as to why would he software decode H.264? No need to do that as it's already supported.
I'm just wondering if he was trying to do transcode from unsupported codec to H.264 on the device.
That method I would expect to not work at all.
But by adding loadable Software codecs it should not require the same proc cycles and speed as trying to transcode as it's really just a decoding operation which is roughly half the intense of transcoding which both decodes then re-encodes.
The Tricky part would be getting the player to load codecs on an as needed basis which is where I expect it might make the approach impossible.
I'm personally less concerned with codec support as I am with Containers, Subtitles and Audio Track selection being done on the Player side.
All of my Library is already H.264 But I much prefer MKV container for keeping Subs and Multiple Audio (for Commentary) so once a player comes out that supports all of those without transcoding I'll be a very happy puppy.

I don't know but I imagine that he was simply following a standard best practice -
Comparing known quantities to map the solution space before proceeding into the unknown.
The H.264 routine (just a software codec attached to a simple player from what I recall looking at the time) made sense for that, precisely because it was a mature, known quantity that could be compared to the existing feature in hardware.
Apples to apples.

perhap he tried that since H.264 is the most hardware intensive compression compared to say On2, Cinepak or the older Indeo...
If it could software decode H.264 then it could pretty much decode everything else just fine with the exception of MPEG2 which requires specific hardware.

Asphyx said:
What needs to happen is for someone to create an MX Player type CCast Player app that can play many Container and Codec types without the need for Transcoding. Then others could potentially use that Player App (think along the lines of a JW Player type CCast Application) when sending Media to the CCast without the worry of incompatible file and codec format.
Click to expand...
Click to collapse
Are you saying if a player i.e. MX player had the cast function builtin into it then you can cast any video format that MX player supports?

ermacwins said:
Are you saying if a player i.e. MX player had the cast function builtin into it then you can cast any video format that MX player supports?
Click to expand...
Click to collapse
That's what a lot of people want.

ermacwins said:
Are you saying if a player i.e. MX player had the cast function builtin into it then you can cast any video format that MX player supports?
Click to expand...
Click to collapse
No not at all.....an App's (aka Transmitter) ability to cast to a CCast has little to do with it can support but what the CCast supports....Other than through the player app it tells CCast to load to receive the stream (aka the Receiver app).
Every App tells the CCast to load a player and it is that player that determines what format can be played not what the App that started the cast supports.
So even if MX Player supported CCast now...Doesn't mean at all that streaming from it to a CCast means MKV or MOV files will play on the CCast despite the fact they play in MX Player just fine.
That is unless MX Player wrote a custom player (receiver) for the CCast that supported all the formats MX Player does or MX Player added the ability to transcode any format to work with the receiver they load into the CCast.
As of today just about every app that supports more than just the standard CCast compatible media do so via Transcoding.
And thats not likely to change soon unless someone figures out a way to do it without frying the unit.
I bet it would work a lot better if the player app was run outside of the Google Sandbox the way Netflix is when it does it's own decryption.
The question is will anyone other than one of the Partners who invented the DIAL protocol ever get that type of access to the hardware?
Not without Google being fully on board....

[Q] why is google shying away from playing all video formats in chromecast??

hi
has any one got an opinion why chromecast despite having the required hardware to play many more video formats is not given the ability to do so??

mahi98 said:
hi
has any one got an opinion why chromecast despite having the required hardware to play many more video formats is not given the ability to do so??
Click to expand...
Click to collapse
Licensing of Codecs for one....
Understand that CCast is really meant to be an HTML5 appliance so it is built to play anything that is HTML5 compatible and that leaves a lot of codecs off the supported list because they are old and inefficient or not suited for streaming over WiFi.
The device is simply not meant to be a ROKU, it is a device that is meant to put Web content onto a big screen and not much more.
If you want more features and video support then AndroidTV is probably the device you are looking for.

It's not like Roku plays a lot of formats either - just mp4 with the standard expected codecs and a small subset of mkv files that happen to be compatible.
I just don't worry about it. I mostly play downloaded files via Plex, relying on Plex to do the transcoding. I only check out the actual file format if Plex seems to be stumbling over some HD file with a rare slow codec. In that case I run it through a video converter utility with hardware GPU acceleration on my desktop PC that can convert a 1-hour video to standard mp4 in about 60 seconds. Problem solved.

DJames1 said:
It's not like Roku plays a lot of formats either - just mp4 with the standard expected codecs and a small subset of mkv files that happen to be compatible.
Click to expand...
Click to collapse
Aren't mp4 and MKV containers? Meaning two different mkv files could use two different codecs (the reason why *some* mkv files are compatible and other are not).
Like you, I use Plex or Allcast and let them do the transcoding. I haven't run into many issues with this approach.

That's correct, but you'd find that most mp4 files today consistently use H.264 as the video codec and stereo AAC as the audio codec. It's possible to use other codecs in an mp4 files, but with so many devices that will play standard mp4s and most of them choking on any unexpected codec it's just easiest to stick to the standard. mkv files tend to have more variety, so a large percentage of them will fail on devices like the Roku or Chromecast that support a very narrow range of codecs and format variations. For example an extra track of chapter marks or an extra audio track will cause many devices to fail even though these are allowed within both the mkv and mp4 container format.

DJames1 said:
It's not like Roku plays a lot of formats either - just mp4 with the standard expected codecs and a small subset of mkv files that happen to be compatible.
I just don't worry about it. I mostly play downloaded files via Plex, relying on Plex to do the transcoding. I only check out the actual file format if Plex seems to be stumbling over some HD file with a rare slow codec. In that case I run it through a video converter utility with hardware GPU acceleration on my desktop PC that can convert a 1-hour video to standard mp4 in about 60 seconds. Problem solved.
Click to expand...
Click to collapse
Yes but the main focus of the Roku is for Alternative video where as the CCast will play video but is designed more as a Web Content device.
This is why the Roku all have wired network connections (recent dongle excluded of course as it is meant to compete with CCast.)
Roku supports more merely because it has the App support.
There is nothing to stop someone like MX Player from making a receiver app that will add codec and container support to the CCast.
What is keeping some developers away is the convoluted discovery and control protocol needed.
Roku doesn't need any of that so they can just focus on the player code cause the remote does the navigation for them.
And in time as more support for the CCast comes around you will find that killer receiver app made that supports more codecs and containers and if the folks at plex are smart they will either license it or make it themselves!
99% of their complaints could all be handled better and go away with a little work on the player side.

Congrats to BubbleUPnP! Transcoding on Mobile!

Just in case anyone is interested (I'm sure there is an announcement somewhere on XDA)
BubbleUPnP for Android will now do some transcoding on the fly when needed without the need to have a PC running the server.
Not sure what this might mean for it's CCast support (This may be DLNA only) but if it is supported for CCast Streaming that is a MAJOR feature for those wanting to Cast local ON DEVICE content that needs transcoding.
So Congrats and Great Job to the Bubble Dev!

Haven't all the major clients done some transcoding on the fly since they were introduced?
I'd test its behavior on high resolution photos, but right now my only television is occupied.

primetechv2 said:
Haven't all the major clients done some transcoding on the fly since they were introduced?
I'd test its behavior on high resolution photos, but right now my only television is occupied.
Click to expand...
Click to collapse
Not on the Mobile device....All required a PC running a Server.

Asphyx said:
Just in case anyone is interested (I'm sure there is an announcement somewhere on XDA)
BubbleUPnP for Android will now do some transcoding on the fly when needed without the need to have a PC running the server.
Not sure what this might mean for it's CCast support (This may be DLNA only) but if it is supported for CCast Streaming that is a MAJOR feature for those wanting to Cast local ON DEVICE content that needs transcoding.
So Congrats and Great Job to the Bubble Dev!
Click to expand...
Click to collapse
It's useful to mention that this is usable for transcoding audio only (including audio tracks in videos), which is not very CPU intensive.
Do not expect to transcode video, unless it is really low resolution.

Well considering your project seems to be the first to transcode anything on a mobile I thought it worth mentioning. LOL
Question is...
Will it transcode audio while sending Video track if the Video track needs no transcode?
Useful for those who have a H.264 Video but AC3 or DHT Audio that is incompatible with CCast...
I have the Server and never keep content locally because of that so I don't really need the feature but many more do I'm sure.

Asphyx said:
Well considering your project seems to be the first to transcode anything on a mobile I thought it worth mentioning. LOL
Question is...
Will it transcode audio while sending Video track if the Video track needs no transcode?
Useful for those who have a H.264 Video but AC3 or DHT Audio that is incompatible with CCast...
I have the Server and never keep content locally because of that so I don't really need the feature but many more do I'm sure.
Click to expand...
Click to collapse
This! Can't tell you how many times I had a compatible video file but audio wasn't. Keeping my fingers crossed.

Asphyx said:
Well considering your project seems to be the first to transcode anything on a mobile I thought it worth mentioning. LOL
Question is...
Will it transcode audio while sending Video track if the Video track needs no transcode?
Useful for those who have a H.264 Video but AC3 or DHT Audio that is incompatible with CCast...
I have the Server and never keep content locally because of that so I don't really need the feature but many more do I'm sure.
Click to expand...
Click to collapse
Yes of couse, It transcodes only what is required. For a MKV with H264 + AC3 (or DTS) , only the AC3 track is transcoded.
Depending on the input video it will transcode only audio, only video, video+audio, or even do just a remux (if both the audio and video tracks are compatible but the container is not).

How are these apps at transcoding high resolution pictures? They always ended up looking like photo CDs loading pictures in my DVD player.. or do they just have to be batch resized to 720×n beforehand?

bubbleguuum said:
Yes of couse, It transcodes only what is required. For a MKV with H264 + AC3 (or DTS) , only the AC3 track is transcoded.
Depending on the input video it will transcode only audio, only video, video+audio, or even do just a remux (if both the audio and video tracks are compatible but the container is not).
Click to expand...
Click to collapse
That will help a lot of people I know!