Jump to content

Chromecast - WebM


NWW

Recommended Posts

Hi all! Just got a Chromecast and started playing a bit with it. I am wondering Emby uses WebM when the content is already H264/AC3 Inside an .mkv? Wouldn't a container swap to .mp4 be better?

 

Thanks!

Link to comment
Share on other sites

All right, here's what I've been doing:

 

Using an Ipad with the iPhone application (the old one, the free one) I start remote playback on the Chromecast. Everything is on the same network.

 

On the server (i5-2500k@4.2Ghz), ffmpg starts up to 100% then stabilizes at 25 with some bursts.

 

Here are the logs!

transcode-40b21581-4b1e-4459-b923-8aea69795aa0.txt

server-63569080792.txt

Link to comment
Share on other sites

Ok, for the iphone, we are soon releasing a new app that will use our new Chromecast receiver. There will be no webm. Stay tuned for that as it's almost ready.

Link to comment
Share on other sites

android. the web client with chrome. you can also contact the developer of your existing apple app for help or improvement.

Link to comment
Share on other sites

You're not doing anything wrong. The will convert to formats the clients understands. I would just enjoy your videos.

Link to comment
Share on other sites

I would prefer to not transcode if I can avoid it. According to Google's guideline's (and other posts on this forum) H264/AC3 shouldn't transcode.

Link to comment
Share on other sites

I've been doing some tests.

 

I've converted an H264/AC3 .mkv file to a 1:1 copy H264/AC3 .mp4 file using this command

ffmpeg -i input.mkv -c:v copy -c:a copy output.mp4

The resulting file has been placed in lieu of the original file in the file structure. A refresh of the database has been done.

 

Playing that file from the Chrome browser (on a desktop) to the Chromecast will do the following:

 

1: transcoding the H264 to H264 using libvx264 at ORIGINAL QUALITY (?!?) but with 100% CPU usage !!!

2: downgrading the 5.1 AC3 to a stereo AAC

 

This results in a lower quality video and audio. This shouldn't be the case as the Chromecast supports H264/AC3 natively, as per this forum and Google's dev guidelines.

 

I have searched every inch of the Dashboard for a setting, nothing is appearing as relevant to the Chromecast. In user profile, Chromecast bitrate has been set to 12 mbps, streaming to 20 mbps.

 

So Luke, sorry but I can't "enjoy" my videos like that, the geek in me is going nuts over the unnessecary CPU usage.

 

I am somehow sure that I have done something wrong to mess with Chromecast streaming but I can't find a reason why.

transcode-62dbbb43-b893-460f-b0ef-dc7317d38020.txt

Link to comment
Share on other sites

you can always review the server log in debug mode to find the reason it is transcoding

Link to comment
Share on other sites

2015-06-07 16:51:35.2637 Info - App: C:\Users\****\AppData\Roaming\MediaBrowser-Server\ffmpeg\20150331\ffmpeg.exe -loglevel debug -i file:"D:\Videos\TV Shows\Arrow\Season 3\Arrow - S03E23 - My Name Is Oliver Queen.mp4" -map_metadata -1 -threads 0 -map 0:0 -map 0:1 -map -0:s -codec:v:0 libx264 -pix_fmt yuv420p -preset superfast -crf 23 -maxrate 5075930 -bufsize 10151860 -vsync vfr -profile:v high -level 50 -force_key_frames expr:gte(t,n_forced*3) -vf "scale=trunc(min(max(iw\,ih*dar)\,min(1920\,1080*dar))/2)*2:trunc(min(max(iw/dar\,ih)\,min(1920/dar\,1080))/2)*2" -flags +loop-global_header -sc_threshold 0 -copyts -codec:a:0 aac -strict experimental -ac 2 -ab 128000 -af "adelay=1,aresample=async=1,volume=1" -hls_time 3 -start_number 0 -hls_list_size 0 -y "C:\Users\****\AppData\Roaming\MediaBrowser-Server\transcoding-temp\680a4ed6408331a882877c5de4d80a34.m3u8"
2015-06-07 16:51:35.8177 Error - NotFoundHttpHandler: 192.168.1.100:8096 Request not found: /favicon.ico
2015-06-07 16:51:36.3857 Info - App: returning C:\Users\****\AppData\Roaming\MediaBrowser-Server\transcoding-temp\680a4ed6408331a882877c5de4d80a340.ts

That's the server log when I start the .mp4. I'll look at the transcode log.

 

EDIT: The transcode log looks like the one I posted above, I already had dev logging in the transcoding section enabled.

Edited by NWW
Link to comment
Share on other sites

Okay, I'm posting it here and I'm going though it as well.

 

EDIT: found this:

2015-06-07 17:02:53.9268 Debug - App: Starting transcoding because currentTranscodingIndex=null

server-63569293326.txt

Edited by NWW
Link to comment
Share on other sites

Right. the only reason we have not yet added ac3 to chromecast direct streaming is because we can't assume the user's audio equipment will support it. chromecast supports ac3 passthrough but not ac3 decoding. when we originally enabled passthrough for everyone, we received a lot of reports of video playing without sound. so it is just waiting until an option is added for the user to specify.

Link to comment
Share on other sites

Okay, that's for the audio

 

Does the fact that it transcodes the audio also triggers the video transcode?

 

Because on WP, it doesn't

Link to comment
Share on other sites

Just want to report that using the latest dev build, direct play works on an .mkv with H264/AC3 on the Chromecast!

 

Cheers!

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...