Shield Experience 8.2.3 - Direct Play - Android TV 2.1.14 - DTS:X

[Teddyknuddel 136]

18 minutes ago, Audiomixer said:

so is that what you expected to see on your avr with your sample? DTS:X? Not DTS-HD HRA?

Well - there's no sound coming out at all. And my Denon app on the iPad doesn't show any input either. Sound and DTS:X come out under Kodi.

13 minutes ago, CBers said:

As I said above, Stable and Beta are currently at the same version. 

 

It doesn't matter - at the moment I'm happy with the way things are going. I don't see any need to make anything worse. Don't repair anything that works.

[rbjtech 5284]

Check the Shield Advanced Audio Settings - on mine (with 2.1.21g) - if I set it to Auto - no sound, if I set it to individual codecs (manual) - it direct plays fine.

So maybe this is a Shield issue where Auto is not passing it through correctly ?

Audio Plays -

Audio does not play -

I usually keep mine on Auto ..

Direct play via SMB

Edited September 3, 2024 by rbjtech

[Teddyknuddel 136]

5 minutes ago, rbjtech said:

So maybe this is a Shield issue where Auto is not passing it through correctly ?

It is quite possible that it is somehow due to the Shield - but why does it work correctly with Kodi?

[FrostByte 5392]

1 hour ago, Audiomixer said:

I just VPN’d to UK and no 2.1.21 update. I too am on shield 8.2.3.

Kind of sounds like Google wants everyone to upgrade.

[rbjtech 5284]

1 minute ago, Teddyknuddel said:

It is quite possible that it is somehow due to the Shield - but why does it work correctly with Kodi?

It works with VLC too ..

Kodi uses it's own custom audio and video 'stack' - I believe the Emby app uses the one provided by Exo/Android - thus the differences.

But Eric would have to comment.

[Teddyknuddel 136]

1 minute ago, FrostByte said:

Kind of sounds like Google wants everyone to upgrade.

And why does @rbjtechhave  2.1.21 with Shield 8.2.3?

[FrostByte 5392]

1 minute ago, Teddyknuddel said:

And why does @rbjtechhave  2.1.21 with Shield 8.2.3?

He's an odd duck

[rbjtech 5284]

Just now, FrostByte said:

He's an odd duck

 'Special' .. 

[Audiomixer 374]

5 minutes ago, FrostByte said:

Kind of sounds like Google wants everyone to upgrade.

I just tried on shield number 3 with 9.1.1 hotfix. No difference.

[rbjtech 5284]

re the 2.1.21g - it auto updated for me (UK). 

[Audiomixer 374]

28 minutes ago, rbjtech said:

re the 2.1.21g - it auto updated for me (UK). 

Weird.

[Teddyknuddel 136]

You could also just offer it for upload before discussing for a long time where Google's error is now. Please don't post the link to the beta again now.

 

Edited September 3, 2024 by Teddyknuddel

[Teddyknuddel 136]

2 hours ago, Audiomixer said:

I just tried on shield number 3 with 9.1.1 hotfix. No difference.

It has already reached 9.2.0. That's what I have on my non-reset Shield Tube.

[Audiomixer 374]

22 minutes ago, Teddyknuddel said:

It has already reached 9.2.0. That's what I have on my non-reset Shield Tube.

It is 9.1.1+hotfix but in the about section it does indeed say 9.2.0.

[CBers 7450]

2 hours ago, rbjtech said:

re the 2.1.21g - it auto updated for me (UK). 

I have one Shield on 2.1.14 and another on 2.1.21

Both are using the same Google account, with auto updates enabled. 

 

 

Edited September 3, 2024 by CBers

[Audiomixer 374]

32 minutes ago, CBers said:

I have one Shield on 2.1.14 and another on 2.1.21

Both are using the same Google account, with auto updates enabled. 

 

 

So how does that work i wonder?

[ebr 16169]

Mystery of the version solved.  Google was doing a phased rollout.  I forced it to 100% just now.

[Audiomixer 374]

3 hours ago, ebr said:

Mystery of the version solved.  Google was doing a phased rollout.  I forced it to 100% just now.

@ebr and @rbjtech and here i thought i too was special. Was thinking it might be a staged roll out as i got it earlier today.

Edited September 3, 2024 by Audiomixer

[Teddyknuddel 136]

Very strange behaviour. No update was displayed on my Shield 2017 in the bedroom - I then uninstalled ATV 2.1.14 and reinstalled it. Then I had 2.1.21 on it. Update was displayed in my living room. But I uninstalled it there too and reinstalled it via the Appstore. And what did I have on it? 2.1.14! But the update was still offered. So I just had the update done. Now it also has 2.1.21 on it. Both shields are registered with the same Google account in the Playstore.

DTS:X profile DTS-HD HRA still doesn't like Emby. @Audiomixer and  @rbjtech, how did you connect your shields? Shield --> AVR --> TV or Shield --> TV (eARC) --> AVR?

@ebr Overwhelmed to correct the grammatical error, or is this just defiance?

Edited September 4, 2024 by Teddyknuddel

[rbjtech 5284]

 Shield --> AVR --> TV

I don't have eARC on my LG C8 - so this is the only way to connect the Shield to an AVR if I want HD Audio.

Even if I did have eARC, I would be introducing the TV into the HD Audio chain if I went Shield > TV > AVR - so I believe Shield direct to AVR is technically preferable anyway, it certainly introduces less variables into the mix.

Edited September 4, 2024 by rbjtech

[Teddyknuddel 136]

33 minutes ago, rbjtech said:

 Shield --> AVR --> TV

I don't have eARC on my LG C8 - so this is the only way to connect the Shield to an AVR if I want HD Audio.

Even if I did have eARC, I would be introducing the TV into the HD Audio chain if I went Shield > TV > AVR - so I believe Shield direct to AVR is technically preferable anyway, it certainly introduces less variables into the mix.

Just like me - I also expected a bit more from eARC - that HD sound would then also be passed through to the AVR via the apps, but fiddlesticks. I also tested the whole thing with VLC and Just Player on the Shield. VLC --> DTS:X - Just Player --> Nothing

[Audiomixer 374]

Shield > avr > tv here as well.

[ebr 16169]

9 hours ago, Teddyknuddel said:

Overwhelmed to correct the grammatical error, or is this just defiance?

Can you correct it for us so we're sure it is right?  Or has it already been done in the translation site?

http://oshotim.oneskyapp.com/collaboration

[Teddyknuddel 136]

19 minutes ago, ebr said:

Can you correct it for us so we're sure it is right?  Or has it already been done in the translation site?

http://oshotim.oneskyapp.com/collaboration

I have already displayed it here!

"aktivieren" NOT "aAktivieren"

I'm not going to trawl through any links to translate ONE word.

[GrimReaper 4739]

22 minutes ago, Teddyknuddel said:

I'm not going to trawl through any links to translate ONE word.

Well, someone has to. If you're not willing to contribute, hopefully some other fellow user will. 

I, for one, would prefer the Devs to focus/allocate limited resources on development, not translations. 

Edit: There. 

 

Edited September 4, 2024 by GrimReaper
Screenshot