LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
keypusher has quit [K-Lined]
syphyr has quit [Quit: Leaving]
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
minimal has quit [Quit: Leaving]
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
Fenster` has joined #libreelec
buzzmarshall has quit [Quit: Konversation terminated!]
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
<MrTAP>
any thoguhts on why my rpi4 with 10.0.3 is struggling with a 1080p h264 7.1 e-ac3 file?
<MrTAP>
i thought that was well within its abilities. plays all my other media without complaint
<MrTAP>
this is stuttery video and significant audio dropping out
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
BlueyHealer has joined #libreelec
riot_dd_ has joined #libreelec
riot_dd has quit [Ping timeout: 246 seconds]
donofrio_ has joined #libreelec
donofrio__ has joined #libreelec
donofrio has quit [Ping timeout: 272 seconds]
donofrio_ has quit [Ping timeout: 260 seconds]
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
<MrTAP>
huh. when i disable passthru audio its working normally. wonder what is different about this one than the other stuff
BlueyHealer has quit [Quit: random crits are fair and balanced]
<LEBot>
[slack] <chewitt> e-ac3 is not widely supported in AVR hardware
<LEBot>
[slack] <chewitt> e-ac3 is not the same as ac3
<MrTAP>
it plays other e-ac3 tracks fine
<MrTAP>
i'll experiment further later and see if i can isolate some aspect about it
<LEBot>
[slack] <chewitt> run mediainfo against it
<LEBot>
[slack] <chewitt> vs. some other working media
<MrTAP>
yep but that's a project for another day. nearing bedtime now
<MrTAP>
only immediate thing that jumped out at me is this is 7.1, usually i play 5.1... but the receiver shows all the channel it gets and seems to understand that it's a dolby digital plus 7.1 no problem
<LEBot>
[slack] <chewitt> 7.1 will have a higher overall bitrate than 5.1
<MrTAP>
indeed but that should be insignificant compared to the video
<LEBot>
[slack] <chewitt> I know with older pi hardware that very high-bitrate media could go beyond hardware capabilities
<MrTAP>
when i shut off passthru the audio was flawless with the pi downconverting to 5.1 pcm
<MrTAP>
didn't try 7.1 pcm but i'd expect the uncompressed audio has got to be higher demand than the compressed e-ac3 stream
<LEBot>
[slack] <chewitt> I’m not the expert, but handling pass-through prob. uses a different part of the SoC vs. downmixing which is prob. done on the CPU
<LEBot>
[slack] <chewitt> If the SoC is handling video in hardware, the CPU isn’t heavily loaded
<MrTAP>
i mean in theory passthrough shouldn't be using much processing at all. litearlly just passing it along untouched
donofrio has joined #libreelec
<LEBot>
[slack] <chewitt> If the SoC is hitting some audio hardware limit (hypothetically, I’m theorising) then that can cause an issue while video (different part of SoC) is processed fine, etc.
<LEBot>
[slack] <chewitt> There is no such thing as “untouched” .. the audio stream has to be read and processed by the audio IP block
<LEBot>
[slack] <chewitt> The user created construct of “pass-through” just means the input and output should remain the same
<LEBot>
[slack] <chewitt> but data is still processed; hence the dependency on hardware needing to support formats that can be passed-through
<MrTAP>
yes i appreciate it has to be demuxed, copied over, then spit back out onto the wire which all involve various code paths
donofrio__ has quit [Ping timeout: 246 seconds]
<MrTAP>
it just shouldn't need to be deconstructing the audiostream and doing anythign with the data. so in theory if it works well, it could be my receiver's fault
<LEBot>
[slack] <chewitt> I have fuzzy recall of someone saying before that Kodi support for e-ac3 is a bit more patchy than other formats
<LEBot>
[slack] <chewitt> that probably means ffmpeg more than actual Kodi
<LEBot>
[slack] <chewitt> (since Kodi is basically a big fancy wrapper around ffmpeg)
<MrTAP>
ah well like i said when i'm not on my way to bed i'll go through my media and see what else i have for e-ac3 and see if i can isolate some aspect about it
<MrTAP>
dunno what i can do with that info, but it seems to be a good start
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
TomTom has joined #libreelec
TheSilentLink has quit [Ping timeout: 248 seconds]
TheSilentLink has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
gouchi has joined #libreelec
keypusher has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
BlueyHealer has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
gouchi has quit [Remote host closed the connection]
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
keypusher has quit [Ping timeout: 256 seconds]
keypusher has joined #libreelec
LEBot has quit [Remote host closed the connection]
LEBot has joined #libreelec
BlueyHealer has quit [Quit: random crits are fair and balanced]
keypusher has quit [Ping timeout: 264 seconds]
minimal has joined #libreelec
keypusher has joined #libreelec
keypushe- has joined #libreelec
keypusher has quit [Ping timeout: 272 seconds]
keypushe- is now known as keypusher
gouchi has joined #libreelec
LEBot has quit [Remote host closed the connection]