Incorrect Audio Bumper for 3D Audio Formats

[Assi 2]

Hi!

I know that Dolby Atmos and DTS-X are no "Stand Alone" formats as they need to be embedded in a container e. g. a Dolby Atmos Audio Track inside a Dolby TrueHD Container but i still would expecz that CV uses the Atmos Bumper whenever a movie with a Dolby Atmos Track is played.

From my experience this is not the case. The Audio Bumper from the Container is used e. g. True HD.

 

Therefore i ask myself: Based on WHAT  is the Audio Bumper selected? A Movie can have several Audit Tracks with different formats.

 

In my example: The corresponding video file is named XXX.atmos.iso. The corresponding Movie is taged correctly in Kodi (Leia 18.9 with Rapier Skin) as a 4k H.265 Movie with Dolby Atmos 7.1. When playing the Movie i can confirm that really Dolby Atmos is given out to the reciever. But still Cinemavision does not use the Atmos Bumper. Same Problem with DTS-X.

 

Does anybody know how to fix this?

 

....and not to forget: Happy Christmal to all of you;-)

[Assi 2]

So this is clearly a CV Problem, not an error from Kodi: Kodi flags the movie correctly with Atmos but when switching over to CV the splash screen clearly indicates that this flag is not transfered. Here the movie is just marked as Dolby Digital + and consequently the incorrect DD+ audio bumper is played. See pictures attached.

 

Can anybody from the developers comment on this?

[dyhometheaterguy 8]

I been having this problem for quite some time and it was never addressed. My default track would be English Dolby Atmos and would always have a secondary DD 5.1 foreign language track. CV would always pick up the standard DD 5.1 track and play that bumper instead of the atmos one so its definitely a CinemaVIsion issue. 

[OTA 78]

I ran across this too.  It USED to work properly, but I think it's when Kodi started detecting 3D audio automatically when it used to not, or it could have been one of the CV fixes to get it to work with 18.  Even using my tags it no longer works.  I haven't messed around with it to see if I could fix it one way or another.  Fixing bugs currently is not a priority as the project is on life support and we are grateful to have members of the community who have taken it upon themselves to keep CV afloat.

[dyhometheaterguy 8]

2 hours ago, OTA said:

I ran across this too.  It USED to work properly, but I think it's when Kodi started detecting 3D audio automatically when it used to not, or it could have been one of the CV fixes to get it to work with 18.  Even using my tags it no longer works.  I haven't messed around with it to see if I could fix it one way or another.  Fixing bugs currently is not a priority as the project is on life support and we are grateful to have members of the community who have taken it upon themselves to keep CV afloat.

Getting the app working in 19 is the priority but I am happy people are bringing up the issues so they can fixed at a later date. Does Kodi now detect 3D audio formats automatically or does it rely on tags for that still?

[OTA 78]

I looked through the changelog of Kodi 18, but can't find a mention of 3D audio.  I don't know for sure, but I recall somebody telling me it was working automatically, but they could have been wrong.

All my tags are still in place, but CV doesn't play Atmos or DTS:X bumpers anymore, just the 7.1.  I just haven't had the time to sit down and see what's going on.

[OTA 78]

So, just thought I'd do a little update.  I recreated my sequences and they are working again with my tags.  I guess I just had to start from scratch.  So my Atmos and IMAX sequences are running again and all others work with auto-detect.  I use tags in .nfo files in the movie directories.

[dyhometheaterguy 8]

On 1/4/2021 at 10:27 PM, OTA said:

So, just thought I'd do a little update.  I recreated my sequences and they are working again with my tags.  I guess I just had to start from scratch.  So my Atmos and IMAX sequences are running again and all others work with auto-detect.  I use tags in .nfo files in the movie directories.

If you don't mind can you be a little more specific of what you did and how you got it working again because I am still having issues.

[OTA 78]

I think I may have found what was keeping it from working.  My Atmos and IMAX sequences were set to work with "any" type in the conditions, but my default was set for "2D".  I went through and redid my sequences and figured I'd go ahead and set the type to "2D" as well just to keep them the same and boom, they started working again.

What type is your sequence set to?  Any or 2D?  I can try and reproduce the issue this weekend and confirm if that's the problem.

[dyhometheaterguy 8]

12 hours ago, OTA said:

I think I may have found what was keeping it from working.  My Atmos and IMAX sequences were set to work with "any" type in the conditions, but my default was set for "2D".  I went through and redid my sequences and figured I'd go ahead and set the type to "2D" as well just to keep them the same and boom, they started working again.

What type is your sequence set to?  Any or 2D?  I can try and reproduce the issue this weekend and confirm if that's the problem.

I have mine on 2D i believe. My problem may be I have 2 different audio tracks in the file. Is CV choosing the bumper based on tags in the filename or the actual media info?

[OTA 78]

I think there is a priority.  The priority would be either .nfo tags or manual tagging then audio track.  I don't use file name formatting to identify stuff, so I don't know where in the priority that may be.  I'll see if I can do some testing tonight and see.  Are your two audio tracks for different languages or different mixes, like stereo and 5.1?  Which one is primary?  If the one you want isn't primary, you should be able to swap them using MKVtoolNix if your container is MKV.

Edited January 9, 2021 by OTA

[Assi 2]

Hi Guys!

from my experience Kodi cannot detect 3D Audio Formats directly. You need  an ".atmos." or ".dtsx." in the filename to make the corresponding flag show up in the library. And then it denpends on you skin, what properties are displayed. e, g. Rapier has a flag for Atmos and DTS-X, Estuary has not.....

So my media files have the atmos or DTS-X Info in the filename. But this is not considered by CV. See screenshots in post #2.

Edited January 10, 2021 by Assi
additional information

[OTA 78]

I dunno.  I tried to just create a sequence for an AAC movie I had using conditions for the tags and it still didn't work.  I can't seem to pin it down.  Not sure how mine started working again.

[dyhometheaterguy 8]

On 1/9/2021 at 1:12 PM, OTA said:

I think there is a priority.  The priority would be either .nfo tags or manual tagging then audio track.  I don't use file name formatting to identify stuff, so I don't know where in the priority that may be.  I'll see if I can do some testing tonight and see.  Are your two audio tracks for different languages or different mixes, like stereo and 5.1?  Which one is primary?  If the one you want isn't primary, you should be able to swap them using MKVtoolNix if your container is MKV.

 

On 1/10/2021 at 12:31 PM, Assi said:

Hi Guys!

from my experience Kodi cannot detect 3D Audio Formats directly. You need  an ".atmos." or ".dtsx." in the filename to make the corresponding flag show up in the library. And then it denpends on you skin, what properties are displayed. e, g. Rapier has a flag for Atmos and DTS-X, Estuary has not.....

So my media files have the atmos or DTS-X Info in the filename. But this is not considered by CV. See screenshots in post #2.

I have my Dolby atmos track as the primary track and a DTSMA 5.1 track as the secondary. I do have atmos in my filename as well. Now I do have some movies with just the atmos track an CV seems to trigger the Other audio bumper for some reason so I'm not sure what the problem is.

[Assi 2]

Hi Guys!

....strange that this is not working🤔

But somehow CV must have been designed to play Atmos and DTS-X Bumpers. Otherwise there would not be dedicated folders.....

What conditions must be fullfilled to trigger a Atmos/DTS-X Bumper?

Based on what does CV decide  wich Bumper to use?

On 12/28/2020 at 8:28 PM, dyhometheaterguy said:

.....Getting the app working in 19 is the priority ....

Glad to hear that you are working on the Matrix Compatibility of CV👍

Maybe the 3D Audio Bumper Problem can be adressed in this major Update as well?

Kind Regards