Amazon Firestick 4K Max for Surround Music

QuadraphonicQuad

Help Support QuadraphonicQuad:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
@audioWolf212 and @MrSmithers

I found the issue that caused the initial installs to fail. This is now fixed in Version 1.2 of the docs and files. (I had to create all the Kodi 'user accessible' folders before users run Kodi for the first time - that's all in Install-1.bat now)

I also could remove the previous manual STEP 3C: Setting Kodi File Permissions as it’s now done in the install-1.bat

I tested on a reset to new FTV 4k Max today. Two thumbs up!

I also added a new Screenshot.bat to the zip file: This is it so you can create your own:

Code:
adb connect [YOUR IP Address here e.g. 192.168.1.45 no brackets]
adb shell screencap /sdcard/screenshot1.png
adb pull /sdcard/screenshot1.png screenshot1.png

pause

It creates the screen shot on the FTV then copies it to the folder the bat file is run from (rename it if you don't want it overwritten with next screen shot)
 
Last edited:
I will move some of the posts in this thread to a new thread but in the mean time here’s some info on the QQ Logo Kodi skin mod I did. The source files are in the zip.

Here is the QQ Logo skin mod in action (video) when I play a Penteo Upmix in Kodi with the Artists Slideshow running:

(actually an old video I made with my iPhone and TV screen, the latest skin mod has a smaller album cover image).

The mod provides the codec logo at bottom and the word ‘Quad’ to the codec information line displayed.

The following is from the original QQ Logo skin mod thread from a few years ago here on QQ so users can customise for their folder naming:

How does this work:
This mod will display logos by reading certain user defined text from the album folder name. Examples for Pink Floyd albums:

Atom Heart Mother (Quad Q8)
Dark Side of the Moon (SACD)
Wish You Were Here (Quad BDA)

So no need to re-tag any music files, just add a ‘codec/format’ to the folder name. Valid Codecs are in the Rules section below and are user definable. You will need to rescan your Music Library in Kodi for it to see the any albums with changed folder names.

In my music collection I have created sub-folders for surround music ‘types’ which I use to navigate in Kodi:

Music\Atmos
Music\Quad
Music\Upmixes
Music\Surround (everything else not that’s Atmos, Quad or upmixed)
Music\Stereo

So instead of renaming all your album folders you could move them under sub-folders named like the above. This has the benefit of allowing Kodi to ‘filter’ its music library by those ‘Source’ folder names. Basically, ‘Show me Quad music’ or ‘Show me Atmos music’ etc.

Users can modify the 'rules' I've defined and/or modify/add new logs to the QQ Logos folder (named QQcodec):

The Variables.xml file contains the rules for selecting the desired logo based on a user defined string (text) in the rule condition. This is just a simple xml text file that can be edited easily. (you must restart Kodi for any changes to be applied).

This is what the current variable definition is for 'QQLogoFromPathvar' is:

<variable name="QQLogoFromPathvar">
<value condition="String.Contains(Player.Folderpath,DVDA UM)">QQcodec/upmix.png</value>
<value condition="String.Contains(Player.Folderpath,SACD UM)">QQcodec/upmix.png</value>
<value condition="String.Contains(Player.Folderpath,SACD)">QQcodec/SACD.png</value>
<value condition="String.Contains(Player.Folderpath,DVDA)">QQcodec/mlp.png</value>
<value condition="String.Contains(Player.Folderpath,DVD-A)">QQcodec/mlp.png</value>
<value condition="String.Contains(Player.Folderpath,DTS 9624)">QQcodec/dts9624.png</value>
<value condition="String.Contains(Player.Folderpath,DTS9624)">QQcodec/dts9624.png</value>
<value condition="String.Contains(Player.Folderpath,ADVD)">QQcodec/DVDV.png</value>
<value condition="String.Contains(Player.Folderpath,DVDV)">QQcodec/DVDV.png</value>
<value condition="String.Contains(Player.Folderpath,DVD-V)">QQcodec/DVDV.png</value>
<value condition="String.Contains(Player.Folderpath,Quad BDA)">QQcodec/BDA.png</value>
<value condition="String.Contains(Player.Folderpath,Quad SQ)">QQcodec/QuadSQ.png</value>
<value condition="String.Contains(Player.Folderpath,Quad Q8)">QQcodec/QuadQ8.png</value>
<value condition="String.Contains(Player.Folderpath,Quad QR)">QQcodec/QuadQR.png</value>
<value condition="String.Contains(Player.Folderpath,Quad Reel)">QQcodec/QuadQR.png</value>
<value condition="String.Contains(Player.Folderpath,Quad QS)">QQcodec/QuadQS.png</value>
<value condition="String.Contains(Player.Folderpath,Quad CD4)">QQcodec/QuadCD4.png</value>
<value condition="String.Contains(Player.Folderpath,Quad Q4)">QQcodec/QuadQ4.png</value>
<value condition="String.Contains(Player.Folderpath,Quadradisc)">QQcodec/quadradisc.png</value>
<value condition="String.Contains(Player.Folderpath,Quad)">QQcodec/quadraphonic.png</value>
<value condition="String.Contains(Player.Folderpath,BDA)">QQcodec/BDA.png</value>
<value condition="String.Contains(Player.Folderpath,BDV)">QQcodec/BDA.png</value>
<value condition="String.Contains(Player.Folderpath,Penteo)">QQcodec/upmix.png</value>
<value condition="String.Contains(Player.Folderpath,Upmix)">QQcodec/upmix.png</value>
<value condition="String.Contains(Player.Folderpath,Multitrack)">QQcodec/multitrack.png</value>
<value condition="String.Contains(Player.Folderpath,Atmos)">QQcodec/dolbyatmos.png</value>
<value condition="String.Contains(Player.Folderpath,DTSX)">QQcodec/dtsx.png</value>
<value condition="String.Contains(Player.Folderpath,DTS-CD)">QQcodec/dtssurround.png</value>
<value condition="String.Contains(Player.Folderpath,DTSCD)">QQcodec/dtssurround.png</value>
<value condition="String.Contains(Player.Folderpath,DTS CD)">QQcodec/dtssurround.png</value>
<value condition="String.Contains(Player.Folderpath,DTSDVD)">QQcodec/dtssurround.png</value>
<value condition="String.Contains(Player.Folderpath,Dolby DVD)">QQcodec/dolbydigital.png</value>
<value condition="String.Contains(Player.Folderpath,DTS DVD)">QQcodec/dtssurround.png</value>
<value condition="String.Contains(Player.Folderpath,DSF)">QQcodec/dsd.png</value>
<value condition="String.Contains(Player.Filename,.flac)">QQcodec/flac.png</value>
<value condition="String.Contains(Player.Filename,.dsf)">QQcodec/dsd.png</value>
<value condition="String.Contains(Player.Filename,.dff)">QQcodec/dsd.png</value>
<value condition="String.Contains(Player.Filename,.mp3)">QQcodec/mp3.png</value>
</variable>

This works as a stacked rule list, when run each rule is sequentially tested, top down, and if its condition is True the value is returned and no further rules are tested.

In the 3rd rule:
<value condition="String.Contains(Player.Folderpath,SACD)">QQcodec/SACD.png</value>

The condition (test) means: If the current playing file's folder path contains the word 'SACD' then return the logo file name 'SACD.png' from the logo folder.

So its easy to add a new rule (copy a line and modify) or to change a rule to check for different text value or use a different logo file.

NOTE: In Linux and Android filenames are case sensitive (Example: FileName.png is not the same as filename.png). In Windows they are seen as the same file.

In this attached screen grab the following logo rule was found (the album folder name had ‘DVD-A’ in the name):
<value condition="String.Contains(Player.Folderpath,DVD-A)">QQcodec/mlp.png</value>

So the mlp.png file is displayed while a song plays:
View attachment 99928

The FLAC file has 6 channels so ‘5.1’ is shown in the codec info line (see below on how that is done)

I have also added a new variable used in this mod named 'QQNoOfChannelsFromPathvar'. This variable is used to update the Number Of Channels based on rules.

The new variable basically returns 'Quad' for any album path with the word 'Quad' in it, likewise 'Atmos' and 'DTS:X', otherwise it looks at the number of channels and returns it converted to MCH naming:

<variable name="QQNoOfChannelsFromPathvar">
<value condition="String.Contains(Player.Filename,Quad) + String.Contains(Player.Folderpath,Penteo)">4.1</value>
<value condition="String.Contains(Player.Folderpath,Quad) + !String.Contains(Player.Folderpath,Quad Penteo)">4.1</value>
<value condition="String.Contains(Player.Folderpath,Quad)">Quad</value>
<value condition="String.Contains(Player.Folderpath,Atmos)">Atmos</value>
<value condition="String.Contains(Player.Folderpath,DTSX)">DTS:X</value>
<value condition="String.IsEqual(MusicPlayer.Channels,5)">5.0</value>
<value condition="String.IsEqual(MusicPlayer.Channels,6)">5.1</value>
<value condition="String.IsEqual(MusicPlayer.Channels,8)">7.1</value>
<value condition="String.IsEqual(MusicPlayer.Channels,2)">stereo</value>
<value condition="String.IsEqual(MusicPlayer.Channels,1)">mono</value>
<value>$INFO[MusicPlayer.Channels]</value>
</variable>

You can modify rules above in the Variables.xml file in the Aeon.Nox.Silvo 16x9 folder provided in the zip file then ‘push’ it to your FTV Kodi folder equivalent (see the install-2.bat for an example adb command line).


Thanks for all the logos QQ members supplied.

I encourage all users to continue to modify these rules and logos, create new rules and logos and share them here for all QQers using Kodi.
 
Last edited:
Nice one Garry, you always go the extra mile to get things running perfectly…

Yeah I’ve had some fun adapting the logos and the rules, quite happy with how it looks.

I’ll have to ask you at some stage how to group albums from the menu in the way you have setup...

Here’s an example of me playing Atmos using the logo mod…

thinlizzy.jpg
 
My memory is a little fuzzy, but is it still the case with this that it can't output certain channel configurations of 192kHz FLAC?

I'd like to upgrade from my 7th gen NUC to something that supports Dolby Vision output - the only option previously was the NVidia Shield, but if this can do the same at less half the price I'm in, unless it has the aforementioned FLAC issues, which are dealbreakers.
 
is it still the case with this that it can't output certain channel configurations of 192kHz FLAC?

I tested a single random 192kHz FLAC a few days back and it wouldn’t play. But I will go back and retest with more sample files and report back. Ffmpeg was doing bad 192kHz conversions a while back, my random test file may have been one of them or it may have been a 4 channel FLAC and that was the issue not the sample rate.
 
I tested a single random 192kHz FLAC a few days back and it wouldn’t play. But I will go back and retest with more sample files and report back. Ffmpeg was doing bad 192kHz conversions a while back, my random test file may have been one of them or it may have been a 4 channel FLAC and that was the issue not the sample rate.
For the purposes of testing, I wonder if it makes any difference if the 192.0kHz flac files are 2Ch, 4Ch, 6Ch or 8Ch.

Personally speaking...
I'm not entirely sure how many music sources I have that were originally encoded at 192.0kHz... One that does spring to mind is Beck's, Sea Change [2013 BRD-A].
 
Last edited:
For the purposes of testing, I wonder if it makes any difference if the 192.0kHz flac files are 2Ch, 4Ch, 6Ch or 8Ch.

Personally speaking...
I'm not entirely sure how many music sources I have were originally encoded at 192.0kHz... One that does spring to mind is Beck's, Sea Change [2013 BRD-A].
For stereo only, I think a bunch of Neil Young releases were/are available as 24/192 digital downloads. For mch I have no clue.
 
HOLD EVERYTHING ON THE FTV & KODI OMEGA:

EDIT: 19 January:
No issues with the Firestick 4K Max with Kodi playing Atmos, 7.1 and 192kHz --------------------------------
I changed my FireTV Kodi v21 Beta version from Kodi.Nerds (11 Jan build) to the official Kodi v21 Android nightly (18 Jan) and all my FireTV 4K Max problems are solved 7.1 output, rears on Atmos and LFE all working. No changes to my AVR. We are back in business using a FTV to play all your surround files. (I will do more testing)
------------------------------------------------------------------------------------------------------------------------------------------

I've been doing some testing on my current FTV today and have reported these issues to a Kodi developer. Until this is resolved don't go out and buy a FTV for Kodi Atmos and 7.1 listening:

FTV 4K Max 2nd Gen (2023): Does not output anything to rears from any 7.x.x Atmos file (DD Plus or TrueHD).
FTV 4K Max 2nd Gen (2023): Does not output anything to rears from any 7.1 TrueHD file
FTV 4K Max 2nd Gen (2023): Does not output LFE channel from any Atmos file
FTV is set to 'Kodi IEC Packer' - I have changed the 'No. of Channels' to 7.1 and 2.0 - no difference. My AVR show 'Atmos' decoding but the AVR speaker output never has 'rears' activated using the FTV device (connected directly to an AVR HDMI port)

LibreElec Kodi (Linux): Does not output anything to rears in any 7.x.x or 9.x.x Atmos file (DDPlus or TrueHD). This is a surprise. I have never noticed this previously and immediately presume there has been a recent change in Kodi Omega that has stopped 7.1. I have been listening to 7.1 in Kodi for many years (and 7.1.x Atmos and DTS:X for 3 or 4 years now)

I have confirmed my AVR is setup correctly for my 7.1.4 speaker layout.

I have made a zip file for Kodi developers to use to test on my OneDrive containing:
A single 7.1 file
9.1.6, 7.1.4 and 5.1.4 Atmos mixes in TrueHD
9.1.6, 7.1.4 and 5.1.4 Atmos mixes in DDplus

So I am hoping there is a fix very soon! In the mean time hang back (There are no FTV 4K Max in stock at Amazon US and UK now anyway)
 
Last edited:
@himey if users have a 5.1.x system the only issue is 'no LFE' (all other issues are 7.1.x problems).

I'm sure this will be resolved fairly soon as Kodi is getting close to its official v21 Omega release.
 
HOLD EVERYTHING ON THE FTV & KODI OMEGA:

I've been doing some testing on my current FTV today and have reported these issues to a Kodi developer. Until this is resolved don't go out and buy a FTV for Kodi Atmos and 7.1 listening:

FTV 4K Max 2nd Gen (2023): Does not output anything to rears from any 7.x.x Atmos file (DD Plus or TrueHD).
FTV 4K Max 2nd Gen (2023): Does not output anything to rears from any 7.1 TrueHD file
FTV 4K Max 2nd Gen (2023): Does not output LFE channel from any Atmos file
FTV is set to 'Kodi IEC Packer' - I have changed the 'No. of Channels' to 7.1 and 2.0 - no difference. My AVR show 'Atmos' decoding but the AVR speaker output never has 'rears' activated using the FTV device (connected directly to an AVR HDMI port)
Bummer...

This is why you can't beat having a selection of good old fashioned 'speaker mapping' audio test files in your collection ;)
 
Good News: No issues with the Firestick 4K Max with Kodi playing Atmos, 7.1 and 192kHz

I changed my FireTV Kodi v21 Beta version from Kodi.Nerds (11 Jan build) to the official Kodi v21 Android nightly (18 Jan) and all my FireTV 4K Max problems are solved 7.1 output, rears on Atmos and LFE all working. No changes to my AVR. We are back in business using a FTV to play all your surround files. (I will do more testing)

I can also confirm Beck - Sea Change 192/24 FLAC 5.1 plays without a glitch: @steelydave

I will update by FireTV Kodi install/pre-configure zip file tomorrow and post here when ready.
 
Back
Top