• 1
  • 4
  • 5
  • 6(current)
  • 7
  • 8
  • 21
Android 2019 - Amazon Fire TV Cube - AMLogic S922Z
#76
(2020-03-09, 21:03)fritsch Wrote: See: https://github.com/xbmc/xbmc/pull/17463

@fritsch I ordered a cube yesterday to replace my 2017 shield, due to no DV HDR10+ capability. I have been running matrix on the shield, any idea how this should perform on Matrix?

Are there any known issues, things that need testing?

To be clear from reading the thread, the Cube will not breakthrough DTS-HD/TrueHD at all correct?
Could Amazon fix this or is this a case of an issue dead in the water to be forgotten about?


Thanks.
Reply
#77
Ok so new Cube came today, installed the latest ARMV7A nightly for Matrix and the audio is a terrible mess.

I use HDMI to the TV then ARC to the soundbar.

So far I cannot get any DTS files to play at all. Nightmare.
Reply
#78
If you want it to stay your personal mess, don't provide a Debug Log :-)
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#79
(2020-04-05, 17:33)fritsch Wrote: If you want it to stay your personal mess, don't provide a Debug Log :-)
http://paste.kodi.tv/owubitetol

Playing the DTS test file and my soundbar reports it as PCM-Dolby

Thank you :-)
Reply
#80
Good news first: Kodi properly opens the device using its IEC packages. Bad news: Audiotrack does not eat it.

Try the following: Use Audiotrack (RAW) as the PT device and check again please.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#81
Which soundbar is it? Cause if it does not accept the IEC packages (while Android does it), it's a problem we cannot solve. If that's really the case, only enabling AC3 + AC3 Transcoding and setting PCM channels to 2.0 will help out of that.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#82
@fritsch 

When I change the passthrough device to RAW I lose DTS from the menu, all I have is DD and DD+

Here is the log playing that file in RAW.

The soundbar is a Panasonic SC-HTB700
https://www.panasonic.com/uk/consumer/ho...specs.html

I have the Fire Cube connected to HDMI 1 on my TV then the soundbar plays via ARC on HDMI 2

I used the same system with my Nvidia shield and all seemed to work fine.

I cannot plug the Cube into the soundbars HDMI as it does not passthrough HDR10+ and Dolby Vision.
Reply
#83
I also have an issue that it will not play plain DD on IEC, just skips with no audio. The log is too large to upload tho so I am trying to find a way to get it to you.

Here we go:
http://paste.kodi.tv/kegubomoce.kodi

I have had to trim a load of
`2020-04-05 17:22:11.965 T:10167 WARNING: ActiveAE - large audio sync error: 8365.412708
2020-04-05 17:22:11.965 T:10167 ERROR: CAEStreamInfo::GetDuration - invalid stream type`

errors from the end of the log tho as it was huge.
Reply
#84
I just plugged the Cube directly into the soundbar and when playing the DTS file i get no sound and it just skips with the log full of large audio sync errors.

When I had my 2017 shield plugged into this same soundbar I would get all audio formats and they worked perfectly on matrix so I am unsure whats going on here. I know this Cube doesn't support > 5.1 HDMI passthrough but we souldnt be having issues with plain Dolby Digital and DTS?

Here is the log of me trying to play a DTS file with the cube plugged into the soundbar, this exact same setup on my Shield 2017 plays DTS perfect.
https://paste.kodi.tv/efudaxowus.kodi
Reply
#85
Quote:2020-04-05 17:43:14.360 T:12566  NOTICE: Float is supported
2020-04-05 17:43:14.361 T:12566   DEBUG: AESinkAUDIOTRACK - 32000 supported
2020-04-05 17:43:14.361 T:12566   DEBUG: AESinkAUDIOTRACK - 44100 supported
2020-04-05 17:43:14.362 T:12566   DEBUG: AESinkAUDIOTRACK - 48000 supported
2020-04-05 17:43:14.362 T:12566   DEBUG: AESinkAUDIOTRACK - 88200 supported
2020-04-05 17:43:14.363 T:12566   DEBUG: AESinkAUDIOTRACK - 96000 supported
2020-04-05 17:43:14.363 T:12566   DEBUG: AESinkAUDIOTRACK - 176400 supported
2020-04-05 17:43:14.364 T:12566   DEBUG: AESinkAUDIOTRACK - 192000 supported
2020-04-05 17:43:14.468 T:12566   DEBUG: AESinkAUDIOTrack: Using IEC PT mode: 13
2020-04-05 17:43:14.469 T:12566   DEBUG: AC3 and DTS via IEC61937 is supported
2020-04-05 17:43:14.545 T:12566   DEBUG: E-AC3 and DTSHD-HR via IEC61937 is supported
2020-04-05 17:43:14.552 T:12566    INFO: AESinkAUDIOTRACK - AudioTrack creation (channelMask 0x000018fc): java.lang.IllegalArgumentException: ENCODING_IEC61937 must be configured as CHANNEL_OUT_STEREO
2020-04-05 17:43:14.660 T:12566  NOTICE: Float is supported
2020-04-05 17:43:14.660 T:12566   DEBUG: AESinkAUDIOTRACK - 32000 supported
2020-04-05 17:43:14.661 T:12566   DEBUG: AESinkAUDIOTRACK - 44100 supported
2020-04-05 17:43:14.661 T:12566   DEBUG: AESinkAUDIOTRACK - 48000 supported
2020-04-05 17:43:14.661 T:12566   DEBUG: AESinkAUDIOTRACK - 88200 supported
2020-04-05 17:43:14.661 T:12566   DEBUG: AESinkAUDIOTRACK - 96000 supported
2020-04-05 17:43:14.662 T:12566   DEBUG: AESinkAUDIOTRACK - 176400 supported
2020-04-05 17:43:14.662 T:12566   DEBUG: AESinkAUDIOTRACK - 192000 supported
2020-04-05 17:43:14.723 T:12566   DEBUG: Firmware implements AC3 RAW
2020-04-05 17:43:14.784 T:12566   DEBUG: Firmware implements EAC3 RAW
2020-04-05 17:43:14.899 T:12566   DEBUG: Firmware implements DTS RAW
2020-04-05 17:43:14.974 T:12566   DEBUG: Firmware implements DTS-HD RAW

All perfectly fine from the logs.

But now the problem starts:

Quote:2020-04-05 17:43:24.725 T:12567   DEBUG: Minimum size we need for stream: 7696
2020-04-05 17:43:24.725 T:12567   DEBUG: Created Audiotrackbuffer with playing time of 160.333333 ms min buffer size: 30784 bytes
2020-04-05 17:43:24.740 T:12567   ERROR: AESinkAUDIOTRACK - Unable to create AudioTrack
2020-04-05 17:43:24.740 T:12567   DEBUG: CAESinkAUDIOTRACK:Big Grineinitialize
2020-04-05 17:43:24.741 T:12567   DEBUG: Previous line repeats 1 times.
2020-04-05 17:43:24.741 T:12567   ERROR: CActiveAESink::OpenSink - no sink was returned
2020-04-05 17:43:24.741 T:12566   ERROR: ActiveAE::InitSink - returned error

That looks like an incompatibility between your cube and the soundbar, which is sadly out of my hands. As you just bought it just now -> send it back and replace it with a FireTV 4K Stick and retry. When reading back in this forum you can see that others have those above listed enumerated formats perfectly working.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#86
Ouh and yeah, always plug it directly into your soundbar, don't use it via ARC from the TV. I have a
Quote: Samsung HW-J450 2.1
in one of my setups and AC3, DTS works perfectly fine there via IEC mode, though - as said before - I am running a FireTV 4K here.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#87
Additionally, for the time testing, make sure you have "Adjust Refreshrate to match video" off - for now, to not add additional issues towards the debuggin.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#88
(2020-04-05, 19:08)fritsch Wrote: Additionally, for the time testing, make sure you have "Adjust Refreshrate to match video" off - for now, to not add additional issues towards the debuggin.

Thank you for all of your help, really appreciate it :-)
Reply
#89
@fritsch After restarting everything I do indeed get DTS when plugged into the soundbar, the issues are only happening when using ARC

This does present a problem for me as I only left the 2017 shield as it did not have DV or HDR10+ so I was hoping i could get the visual on the cube and still get decent sound via ARC as I assume ARC supported the TOSLINK formats. I am not really sure why theres iddues even having basic DD down ARC but for the time being I will just have to turn passthrough off. It is strange as I never had an ussue with the non HD audio formats via arc with the shield. Im lost as to why this is a problem but what do I know about audio haha.

If Netflix/Prime/Disney+ are able to send Dolby Digital and DD+/ATMOS over ARC is there not a way for Kodi to do this without these issues?

Thank you for all the help.
Reply
#90
AC3 and DD+ (EAC3) should work via RAW even through your ARC port - please try that again with all your restarting ideas. (1)
(2) Try it with IEC again via ARC, but keep DTS disabled, set speakers to 2.0 and AC3 and Dolby Transcoding (Keep EAC3 off).

What are the results? Btw. The shield also does IEC by default, therefore I highly wonder, that you got DTS, AC3 and EAC3 from the shield "over your TV" via ARC. IEC is the same everywhere ... therefore I wonder.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
  • 1
  • 4
  • 5
  • 6(current)
  • 7
  • 8
  • 21

Logout Mark Read Team Forum Stats Members Help
2019 - Amazon Fire TV Cube - AMLogic S922Z0