jriker1 20 Posted April 21, 2021 Posted April 21, 2021 (edited) Looks like it but may be 2.0. I have loads of legacy WMV HD files with 5.1 WMA audio. Looking at my receiver was surprised at what looked like 2.1 audio. Then noticed in Emby it was transcoding it. Ok won’t get into a discussion that the NVidia Shield Pro 2019 is supposed to support this but why is it converted that way? If the source is 5.1 shouldn’t the transcoding of audio be the same # of channels as the source? We aren’t even talking 7.1 here. Edited April 21, 2021 by jriker1
Luke 42077 Posted April 21, 2021 Posted April 21, 2021 Hi there, let's look at an example. Please attach the information requested in how to report a media playback issue. thanks !
jriker1 20 Posted June 14, 2021 Author Posted June 14, 2021 (edited) Sorry for the delay. Can't be positive, it may be trying to convert it to 5.1 but for some reason the receiver may not like what it's receiving. I know if I play a standard ac3 movies or DTS MKV it plays in 5.1 surround fine. Receiver auto selects based on the material and does a good job of it. When it's playing a a movie that is transcoding because it's WMV/WMA, it comes out in stereo. Below are the transcoding logs during playback. ffmpeg-transcode-a4784333-6ad3-4cac-a4cd-08c18677c6e9_1.txt EDIT: Note I believe looking at the web console for my Denon receiver, it's coming thru as E-AC3 maybe? Says DD+. I have a lot of titles that are E-AC3 within MKV containers and they direct play and don't have this issue. Edited June 14, 2021 by jriker1
Happy2Play 9780 Posted June 14, 2021 Posted June 14, 2021 Per the log it is maintaining same amount of channels as the wmapro 5.1 is converted to ac3 5.1. 18:21:38.132 Stream mapping: 18:21:38.132 Stream #0:1 -> #0:0 (wmv3 (native) -> h264 (libx264)) 18:21:38.132 Stream #0:0 -> #0:1 (wmapro (native) -> ac3 (native)) 18:21:38.605 Stream #0:0: Video: h264 (libx264), yuv420p(progressive), 1920x1080 [SAR 1:1 DAR 16:9], q=-1--1, 23.98 fps, 90k tbn, 23.98 tbc 18:21:38.605 Metadata: 18:21:38.605 encoder : Lavc58.62.100 libx264 18:21:38.605 Side data: 18:21:38.605 cpb: bitrate max/min/avg: 5000000/0/0 buffer size: 10000000 vbv_delay: N/A 18:21:38.605 Stream #0:1(eng): Audio: ac3, 48000 Hz, 5.1, fltp, 384 kb/s (default) 18:21:38.605 Metadata: 18:21:38.605 encoder : Lavc58.62.100 ac3
jriker1 20 Posted June 14, 2021 Author Posted June 14, 2021 Quote Yes however to what? It says ac3 but my receiver doesn't feel that's the format. Says DD+ which would really be E-AC3, not what is listed above, so curious if what's being passed to the receiver isn't clean and it's having a difficult time with it.
Happy2Play 9780 Posted June 14, 2021 Posted June 14, 2021 2 minutes ago, jriker1 said: Quote Yes however to what? It says ac3 but my receiver doesn't feel that's the format. Says DD+ which would really be E-AC3, not what is listed above, so curious if what's being passed to the receiver isn't clean and it's having a difficult time with it. Don't see why but I would think it would that hard to go to the transcode folder a get the media info from the files themselves. But the log is clear on what is being sent to your reciever. 1
rbjtech 5284 Posted June 14, 2021 Posted June 14, 2021 Agreed - the command line used in ffmpeg (from the log) is asking for it to be a 5.1 AC3 (Dolby Digital) file - -c:a:0 ac3 -ab:a:0 384000 -ar:a:0 48000 -ac:a:0 6 -metadata:s:a:0 language=eng
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now