Tidal-Media-Downloader
Tidal-Media-Downloader copied to clipboard
yaronzz
Dolby atmos format
Dolby atmos format songs can't download.would you update the git
This won't happen anytime soon. Tidal uses according to a German website https://www.heise.de/newsticker/meldung/3D-Musikformat-Dolby-aeussert-sich-zur-Zukunft-von-Dolby-Atmos-Music-4630101.html Dolby AC-4 which is a proprietary format from Dolby Laboratories. Even when you can download the Dolby AC-4 file, there is (currently) no way to playback these files, read more here: https://en.wikipedia.org/wiki/Dolby_AC-4. Here is an example ac-4 file: https://github.com/google/ExoPlayer/blob/release-v2/library/core/src/test/assets/ts/sample.ac4 where you can try playing this file.
According to the newest update of the tidal app on Apple TV 4K, Tidal now uses Dolby Digital Plus instead of Dolby AC-4: https://www.heise.de/news/Tidal-streamt-Dolby-Atmos-Music-auf-Apple-TV-4K-4768156.html So it might be possible to play back Dolby Atmos and even download the Dolby Atmos music tracks. So hopefully we'll get an update ;)
There is a new Tidal app update (version 2.26.1) which supports Dolby Atmos on Android TV: https://www.apkmirror.com/apk/tidal/tidal-tidal/tidal-tidal-2-26-1-release/ Maybe it could be reversed engineered, how the Android TV plays Dolby Atmos content.
It may be that the Tidal Dolby Atmos audio just needs to be wrapped in one of the video containers that supports Dolby Digital Plus: MPEG-4, MPEG-2 Transport Stream, or QuickTime
So .mp4 may work fine
sample .mp4 dolby atmos files - https://www.dolby.com/us/en/guide/dolby-atmos-trailers.html
Would absolutely like to see support for this.
Tidal delivery of Atmos music is a huge breakthrough as would be the ability to download it with this tool
You don't need to wrap it to MPEG-4. Dolby Digital Plus can be wrapped in .ac3 which is audio only and can be passed through to the AV Receiver which supports Dolby Digital Plus with Joint Object Coding.
If you look at one of those .mp4 trailers referenced earlier with mediainfo you'll see it contains E-AC-3
Another discussion of same
Other examples in containers as previously listed.
Another example specifically referencing the Dolby Digital Plus (EAC3) codec and the specific containers I previously mentioned.
I have some regular 5.1 audio in .ac3 files I play with foobar connected via hdmi and bitstreamed to an a/v receiver but I suspect Atmos object oriented data cannot be wrapped in an .ac3 container
I like your idea of looking at that APK to see if some clues could be found.
Yeah exactly. E-AC-3 is "Dolby Digital Plus" and E-AC-3 JOC is "Dolby Digital Plus with Dolby Atmos". So I want to prove that you can wrap E-AC-3 JOC inside a .ac3 file: I created a .ac3 file with Dolby Atmos based on the Dolby Digital Plus codec. If you have a Dolby Atmos capable receiver try to bitstream this .ac3 file to your receiver via HDMI. Amaze.ac3.zip
Yeah exactly. E-AC-3 is "Dolby Digital Plus" and E-AC-3 JOC is "Dolby Digital Plus with Dolby Atmos". So I want to prove that you can wrap E-AC-3 JOC inside a .ac3 file: I created a .ac3 file with Dolby Atmos based on the Dolby Digital Plus codec. If you have a Dolby Atmos capable receiver try to bitstream this .ac3 file to your receiver via HDMI. Amaze.ac3.zip
Yep it works.
I played this file in Kodi on my Nvidia Shield TV connected via HDMI to my Denon AVR-X3200 receiver and got Atmos audio with no video. Kodi saw it as a 'Music' file. I'm sure many other platforms and players would do the same.
Related to all this is the concept of codecs vs containers vs file extensions in terms of what's going on here.
Mediainfo ID's the container of this this file you created as MPEG-4 and the codec as E-AC3.
In many cases one can manipulate the file extension on any given file independent of the container to get any given media player to see (get fooled by) the file and play it when it otherwise wouldn't recognize the file type/extension. I'm not saying this is important, it's probably not, just an observation, but I believe the file extension itself is immaterial.
I guess the next question is exactly how the Tidal server side file is presented to Tidal-Media-Downloader or the stream that needs to be captured and possibly wrapped in an MPEG-4 container using ffmpeg?
Oh I didn't know that the file is a MPEG-4 container. I tried MediaInfo and the determined format is "E-AC-3 JOC" so I thought it would only be a audio only file. But you have to be correct, I can rename the file from .ac3 to .mp4 without any problems.
How did you find out that the created file ist a MPEG-4 file? I could not determine the file container format you mentioned.
According to the newest update of the tidal app on Apple TV 4K, Tidal now uses Dolby Digital Plus instead of Dolby AC-4
So I would guess that Tidal on Apple TV 4K is using some form of HLS Streaming. The HLS Authoring Specification specifies Dolby Digital Plus with Dolby Atmos with a bitrate of 384 to 768kb/s, which would perfectly match with the detected bitrate of 768kb/s. According to the specification the file extension of Dolby Digital Plus is:
2.1. Audio data SHOULD be provided as an elementary audio stream or in fMP4.
So in theory you "only" have to download the separate fileSequence00.mp4, ..., fileSequenceXX.mp4 and merge them into one .mp4 file, which could be done using ffmpeg.
How did you find out that the created file ist a MPEG-4 file? I could not determine the file container format you mentioned.
Actually I was wrong when I said Mediainfo ID's the container of this this file you created as MPEG-4
I was looking at the original .mp4, sorry about that.
Based on this I believe you are actually correct in saying that E-AC-3 JOC is the container in the case of the file you created and that you in fact accomplished what you set out to do, took the content wrapped in the MPEG-4 container and re-wrapped it in an AC3 container or in this case a little fancier extended version of AC3.
So it appears I was incorrect when I said I thought that Atmos object oriented data cannot be wrapped in an .ac3 container. I will fully admit I'm far from an expert in any of this in case it isn't obvious already :)
It is my understanding that 'Format' in medinfo indicates the container.
For whatever reason medianfo shows the entry 'Codec ID: ec-3' in the Audio section of the original .mp4 but omits this when displaying info for the .ac3 version you created. Possibly a by product of the .ac3 file containing no video?
From my limited understanding so far, it sort of looks like E-AC-3 JOC is both the container and the codec in this case.
"It's a floorwax and a desert topping"
Or perhaps you've created a monster :)
Great detective work on what you're finding so far.
Am curious what criteria yaronzz uses to decide issues to acknowledge/implement/pay attention to. If it's most commented, we're in the top 3 right now :)
And oops, it looks like there was another Atmos download request thread. Since that one got abandoned in April, we need to make this the master :)
I'd be the first to admit Atmos may be the 8 track of the year 2021 and insignificant to 'most' people but for the longtime freaks into surround* this is like the new second coming of quad from the 1970s. And we've seen 'em all come and go since then. I'm looking at you DVD-Audio, SACD, DualDisc. I treasure each and every one of the thousands of surround titles I have.
*www.quadraphonicquad.com
I was looking at the original .mp4, sorry about that.
No Problem - I was just wondering.
Based on this I believe you are actually correct in saying that E-AC-3 JOC is the container in the case of the file you created and that you in fact accomplished what you set out to do, took the content wrapped in the MPEG-4 container and re-wrapped it in an AC3 container or in this case a little fancier extended version of AC3.
Yes that is exactly what I did. :)
So it appears I was incorrect when I said I thought that Atmos object oriented data cannot be wrapped in an .ac3 container. I will fully admit I'm far from an expert in any of this in case it isn't obvious already :)
I am also far from en expert and I have to explain myself better. So thank you for the great discussion here.
From my limited understanding so far, it sort of looks like E-AC-3 JOC is both the container and the codec in this case.
That is exactly what I thought.
Or perhaps you've created a monster :)
I created a Frankstein Dolby Atmos file :)
Great detective work on what you're finding so far.
Thank you very much! That would not be possible without your great discussion!
If it's most commented, we're in the top 3 right now :)
Oh you are right, I did not even notice that. So maybe we will get more attention.
@yaronzz maybe this works for you and you can build on this https://github.com/zpoo32/RedSea evan-goode/mania#5 (comment)
Uhh nice found! I have to try it out and confirm if Dolby Atmos is working.
@Dniel197 fyi lots of interesting related discussion in the Telegram Tiedown forum. I find Telegram a bit silly for serious discussion but nevertheless results of significant progress are being posted there at the moment.
Here is a zip'd version of a 01 - Believer (feat. Lil Wayne).mp4.zip sample file created by Telegram Tiedown user Yarr! captured from Tidal, in Dolby AC-4 format, ostensibly Atmos. So far it is not recognized/won't play on anything I've tried. He says it played fine for him on his phone with Google Play Music. He suggests exoplayer may also work.
@dabl2 I'm confused, I don't know how to play this song on google play music
You and me both my brother :)
So far Dolby AC-4 appears to be useless to anyone but people trying to play Atmos on phones which is pointless anyway.
Are downloads from https://github.com/zpoo32/RedSea in Dolby AC-4 only TIDAL now supports Dolby Atmos on Android TV
As I mentioned on Telegram (Yarr here), to play the file on a phone, you need a phone with a hardware AC-4 decoder nd Dolby Atmos DSP support at the same time, which the Samsung Galaxy S9 and above do, the Huawei P20 abd above, Oneplus 7 and 7 Pro, and like two high end Oppos. Most TVs also support this (apparently 2/3 of all 4K TVs sold in Europe according to the marketing, but basically any that gets software updates, supports EAC-3 (as AC-4 is free to those that can play these afaik) and can play MP4s), though I assume I have to change the container to MP4 for them to play it. I doubt this will get much more support, as making the process user friendly requires reverse engineering a newer version of the Tidal app, while not many can even play them, and the songs honestly just sound weird
As I mentioned on Telegram (Yarr here), to play the file on a phone, you need a phone with a hardware AC-4 decoder nd Dolby Atmos DSP support at the same time, which the Samsung Galaxy S9 and above do, the Huawei P20 abd above, Oneplus 7 and 7 Pro, and like two high end Oppos. Most TVs also support this (apparently 2/3 of all 4K TVs sold in Europe according to the marketing, but basically any that gets software updates, supports EAC-3 (as AC-4 is free to those that can play these afaik) and can play MP4s), though I assume I have to change the container to MP4 for them to play it. I doubt this will get much more support, as making the process user friendly requires reverse engineering a newer version of the Tidal app, while not many can even play them, and the songs honestly just sound weird
Yeah exactly. Take a look here:
https://www.heise.de/news/Tidal-streamt-Dolby-Atmos-Music-auf-Apple-TV-4K-4768156.html
The Apple TV 4K got a E-AC-3 stream also known as ec-3 and no AC-4 stream so I might guess that Tidal/Dolby have 2 files lying on there servers: 1 for the phone encoded in AC-4 and another one in E-AC3 for Nvidia Shield TV and Apple TV 4K. So this might be the solution why it takes so long for Tidal to release Dolby Atmos for Apple TV 4K and Nvidia Shield - they reencoded every AC-4 to E-AC-3.
I doubt this will get much more support, as making the process user friendly requires reverse engineering a newer version of the Tidal app, while not many can even play them, and the songs honestly just sound weird
Certainly there will be little to no motivation for people who either don't understand Atmos or who aren't interested in surround to enable a feature to allow download of Atmos files.
A phone is simply not a good playback device for Atmos and it never will be. Of course the songs sound weird on them.
This effort will probably need to be spearheaded by one or more surround enthusiasts with real audio systems. They are the true target audience for Atmos.
There is no question Dolby muddied the waters and confused tons of people in the initial marketing push of Atmos on phones and that dinky little Amazon speaker back in January. That was a mistake and we're paying for it now.
There is zero benefit of an Atmos encoded file over stereo when played back on stereo (or worse) speakers. Those devices should simply use the stereo version of the track. Who knows what Dolby was thinking. Apparently they listened to 20 something marketing idiots who don't know the first thing about who their real target audience is.
Surround enthusiasts have been buying content for 50 years, starting with Quad in the 1970s. Dolby and Tidal should be focusing on them as early adopters of Atmos streaming. I can promise you that community is super excited about it.
We need a developer who aligns with this audience or is at least interested in trying to help them.
If there really are E-AC-3 versions of Atmos tracks available to grab we're golden, it should be doable.
I'll be checking out the TV versions of Tidal, although without any Android TV or Apple TV it will be difficult, if anyone has one of these, it will be very useful
I need the help of someone with one of these devices: Fire TV Stick 4K, Fire TV Cube, Fire TV Stick (2nd/3rd gen), the Nvidia Shield TV or Nvidia Shield TV Pro (2019 or newer models) or a Dolby Atmos-enabled Android TV from Sony or Philips Edit: also I post some info about my efforts on the another Tidal downloader called Mania's issue thread for Atmos downloading too, but I still need someone with one of these Android TVs
I need the help of someone with one of these devices: Fire TV Stick 4K, Fire TV Cube, Fire TV Stick (2nd/3rd gen), the Nvidia Shield TV or Nvidia Shield TV Pro (2019 or newer models) or a Dolby Atmos-enabled Android TV from Sony or Philips Edit: also I post some info about my efforts on the another Tidal downloader called Mania's issue thread for Atmos downloading too, but I still need someone with one of these Android TVs
Awesome thanks, happy to help. I have an Nvidia Shield TV 2017 feeding a Denon AVR-X3200 driving a 5.1.2 Atmos speaker setup. FYI though Tidal seems to indicate in some of their specs that the only the 2019 Shield or later are supported I believe elsewhere that is contradicted. In any case I get Atmos from Tidal just fine.
TYPE tidal-dl USE pip3 install tidal-dl --upgrade DESC This version requires some tests, there may be many problems
2020-06-14
- Reduce the number of logins
- Use another login method(from Redsea)
- Download Dolby Atmos(AC4 Codec\Low Quality\Mp4 format)
- Download SONY_360RA(MHA1 Codec\Low Quality\Mp4 format)
- Skip convert to mp4 if File-Codec is AC4 or MHA1
The new version works well to the grab AC4 mp4 files, but unfortunately they are not playable by anything except for a few phones. Is there a way to get the E-AC-3 versions that are presumably there?
The new version works well to the grab AC4 mp4 files, but unfortunately they are not playable by anything except for a few phones. Is there a way to get the E-AC-3 versions that are presumably there?
If you have a compatible device such as: Apple TV 4K, Fire TV Stick 4K, Fire TV Cube, Fire TV Stick (second-gen), Fire TV (third-gen), or the 2019 models of the Nvidia Shield TV or Shield TV Pro then yes you dan get the E-AC-3 versions.
If you have a compatible device such as: Apple TV 4K, Fire TV Stick 4K, Fire TV Cube, Fire TV Stick (second-gen), Fire TV (third-gen), or the 2019 models of the Nvidia Shield TV or Shield TV Pro then yes you dan get the E-AC-3 versions.
If by 'get' you mean 'play' then yes but I believe harync means 'download' the E-AC-3 versions which is not yet possible with this tool.
I very much hope yaronzz is able to implement downloading E-AC-3 versions of Tidal tracks where available.
@dabl2 Do you still have access to a FireTV 4K Stick or your Nvidia Shield? We found a way to get the token without SSL certificate.
@dabl2 Do you still have access to a FireTV 4K Stick or your Nvidia Shield? We found a way to get the token without SSL certificate.
Yes, sorry for being out of the loop. Am definitely still willing to help.
Would be really awesome if you could be online on Telegram, we are really close.
If you will open it in Media Player Classic, it will play it as Atmos if you have Dolby atmos for headphones activated or have a LG C9, for example, that is already Dolby Atmos activated. It will print that Atmos is being played.
The correct name would be .eac3 and yeah, you can do this, just like there exists ANNEX B .hevc and ANNEX B .avc, there exists naked .eac3, .ac4, .ac3 and .thd, that is normal. The consensus is to put it in mp4/m4a/mkv/mka though, for faster seeking.
If you will open it in Media Player Classic, it will play it as Atmos if you have Dolby atmos for headphones activated or have a LG C9, for example, that is already Dolby Atmos activated. It will print that Atmos is being played.
I don't think you can play Dolby Atmos with Headphones on Media Player Classic, if I remember correctly you need an UWP app such as the "Movies & TV" app which can play Dolby Atmos. You are only listening to the 5.1 Bed of the E-AC-3 audio.
The correct name would be .eac3 and yeah, you can do this, just like there exists ANNEX B .hevc and ANNEX B .avc, there exists naked .eac3, .ac4, .ac3 and .thd, that is normal. The consensus is to put it in mp4/m4a/mkv/mka though, for faster seeking.
I never seen the file extension .eac3 ... I only used .ac3, because that was the file extension ffmpeg recognized. Dolby themselves only mention .ec3 or .eb3 as a file extension for Dolby Digital Plus (with Dolby Atmos metadata):
"Movies & TV" app which can play Dolby Atmos
It does not support music in m4a. But it does support music in mp4 (or you can just rename m4a to mp4, m4a IS almost mp4 after all, only M4A band is tgere to signal m4a). It does not really matter, they both use MFF (Media foundation framework with Dolby Access/Dolby Vision extensions) and play it the same and bitstream it the same. For bitsreaming of TrueHD you will need Media Player Classic though with LAVFilters (it will put TrueHD atmos inside MAT 2.0) and it cannot be played AFAIK with Headphones, that is unfortunate, it also cannot be played on LG C9 internal player, you can only bitstream to LG C9 in MAT 2.0 and then it will work. Ridiculous.
I never seen the file extension .eac3
https://trac.ffmpeg.org/ticket/3595
You are only listening to the 5.1 Bed
Bed is ONLY LFE in Atmos. Everything else is dynamic objects. 5.1 bed and more (9.1) is only in Cinemas.
Bed channel count : 1 channel
Bed channel configuration : LFE
they both use MFF (Media foundation framework with Dolby Access/Dolby Vision extensions) and play it the same and bitstream it the same.
Oh you meant MPC-HC, yeah that supports the MFF, I thought you meant Windows Media Player because of your picture showing it.
it also cannot be played on LG C9 internal player, you can only bitstream to LG C9 in MAT 2.0 and then it will work. Ridiculous.
So if you copy a .mkv/.mka with TrueHD Atmos on a USB Stick and open it on your LG C9, your TV cannot play it back?
https://trac.ffmpeg.org/ticket/3595
Yeah .thd is also not corret, it should be .mlp for Meridian Lossless Packing and .ec3 for Dolby Digital Plus, but thats just preference.
Bed is ONLY LFE in Atmos. Everything else is objects. 5.1 bed and more (9.1) is only in Cinemas.
My bad, I meant the 5.1 backwards compatible legacy mix: https://developerkb.dolby.com/support/solutions/articles/16000067758-what-is-dolby-digital-plus-joc-joint-object-coding- You can also create a Dolby Digital Plus 7.1 with Dolby Atmos metdata file and so it has a 7.1 legacy mix.
Windows Media Player
Also supports Atmos and bitsreaming Atmos on 20H2. I am waiting for Chromium Edge to support it. ;)
USB your TV cannot play it back
No. I suppose it can if you will add a video track like testsrc in ffmpeg to eac3 for example. TrueHD DOES NOT WORK AT ALL. It just says the audio is not supported. Only bitstream from PC works in Lavfilters.
be .mlp for Meridian Lossless Packing
That also exists, but is not the same as thd.
MPC-HC, yeah that supports the MFF
No, it does not. At least in my configuration, but is being developed rapidly. No Atmos for headphones support.
MAT 2.0, BTW, as in MPC in LAVFilters, requires decoding of base layer of TrueHD (first 3 substreams: 0, 1, 2) into LPCM and then puting 4th Atmos data substream into metadata extension. MLP streaming is only proposed, that is what is called TrueHD in EDID. It will also not be supported on internal speakers of LG C9, I suppose. Only ATMOS in EAC3 and MAT 2.0 can be decoded on LG C9 itself. MLP/TrueHD will not be decoded and will require a AVR. It will of course require MFF, patches are only proposed by intel to ffmpeg. See: https://github.com/Nevcairiel/LAVFilters/issues/267
Hello everyone! I literally only created a github account to let you all know this. This project works AMAZING.
TO DOWNLOAD the dolby atmos files unselect convert mp4 to m4a and on the search screen select master and p1080 then play your downloaded files on VLC
Thanks so much to the creator of this amazing project!!
your TV can play it back if you will add a video track like testsrc in ffmpeg to eac3 for example
Yes, and it will even trigger atmos! Perfect. So I just used a very simple command
ffmpeg -f lavfi -i rgbtestsrc -i "01 - John Williams - Fanfare and Prologue.mp4" -c:a copy -shortest -pix_fmt yuv420p "01 - John Williams - Fanfare and Prologue1.mp4"
and it works! Nice. Though it is still not cool you have to add a video track to open in normal internal player (not small audio one, it plays only eac3 without atmos), shameful LG. You can have a test file here:
https://www.upload.ee/files/13604682/01_-John_Williams-_Fanfare_and_Prologue1.mp4.html
That also exists.
I mean TrueHD is just the commercial name of Meridian Lossless packing with some metadata.
MPC-HC, yeah that supports the MFF
No, it does not. At least in my configuration, but is being developed rapidly. No Atmos for headphones support.
Oh I really thought that would support it, I only use my AVR for Dolby Atmos so I had no idea.
Though it is still not cool you have to add a video track to open in normal internal player (not small audio one, it plays only eac3), shameful LG.
So so need to add a video to the MP4 file? What happens if you rename the .MP4 (without video) to .M4A to tell the TV it's just audio?
rename the .MP4 (without video) to .M4A to tell the TV it's just audio?
Nothing. It will not open (it does not even see m4a files on usb flash). It will only work in that little player (without triggering Dolby Atmos icon) if you DLNA send the file.
Anyone have any idea about Apple Music's Atmos format? Are they FairPlay protected?
There's no other thread on the internet about it.
I'm just afraid Apple won't support Spatial on Windows 10 like Tidal, when Netflix already supports Atmos EAC-3-JOC properly.
Seems like Apple Music is using E-AC-3-JOC only, since there is no mention of AC-4:
https://developer.dolby.com/platforms/apple/ios/device-support/
There is also another service with Atmos support now, Hungama:
https://www.bollywoodhungama.com/news/features/hungama-music-brings-dolby-atmos-music-streaming-india/
I'm just surprised at the disparity between Tidal and Apple Music in their Atmos library. So many songs on Atmos are still Apple exclusive. And I'm guessing a lot of Indian songs in Atmos will be exclusive to Hungama.
Yes currently all Dolby Atmos tracks and albums on Apple Music are FairPlay protected right now.
Apple is using E-AC-3 JOC 768 kbit/s - the same bitrate as Tidal. And is currently only really supported on Apple TV and partially on macOS Big Sur (it can only output 5.1 PCM and no real Dolby Atmos sadly).
So I really doubt Apple would allow Dolby Atmos on Windows...
The consensus is to put it in mp4/m4a/mkv/mka though, for faster seeking.
Sorry YOU MUST put it in mp4 because it is only gapless there (all those codecs except thd create priming silence and silence in the end that should be trimmed). Yeah. It is done with editlist, media time and duration in it.
New link: https://www.upload.ee/files/13604682/01_-John_Williams-_Fanfare_and_Prologue1.mp4.html
New link: https://www.upload.ee/files/13604682/01_-John_Williams-_Fanfare_and_Prologue1.mp4.html
Where did you get that??
Where did you get that??
ffmpeg command is above.
No I mean on which music service. Tidal or Apple Music?
Tidal or Apple Music?
I only know how to download atmos from Tidal. I am using Apple Music right now, though.
New link: https://www.upload.ee/files/13604682/01_-John_Williams-_Fanfare_and_Prologue1.mp4.html
Where did you get that??
I would use something like that:
ffmpeg -i "cover.jpg" -i "input_song.mp4" -c:v libx264 -tune stillimage -c:a copy "output_song.mp4"
Then you create a video with the cover, instead of a 320x240px test video.