Jump to content


Cast Members
  • Content Count

  • Joined

  • Last visited

Community Reputation

2 Neutral

About Assi

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. ...sorry, forgot to mention: The same sequence works like expected on Kodi 19.4 on a Windows HTPC. Therefore the problem is most likely not in the content.
  2. Assi

    CV on ZDMC

    Is there a way to make CV run on ZDMC? For those who not know: ZDMC is a modified version / fork of Kodi developep by the folks from Zidoo that uses by default a external player that is fully adapted to work with the Zidoo Hardware. This leads to pretty supreme Video+Audio Playback performance. But unfortunately the external player seems to interfere with CV. Using the latest Version ZDMC 19.4 on my Zidoo UHD3000 with CV 1.5.0 only the very first element of the Sequence is played and after a few hickups CV returns to its main screen. Has anybode here managed to make this combination work?
  3. btw. i had the same problem with CV not playing trailers just using local trailers. But also in this case: deactivating the "match genre" and "match 3D" optoion was the solution.
  4. I have already posted the same problem here: https://cinemavision.tv/forums/topic/1406-dolby-atmos-and-dts-x-flags-in-kodi/ My impression is that nobody of the CV Authors seems to know, were the Audio Bumper information is supposed to come from to have an effect in CV: - The Kodi Audio Flag - The Filename - The media Information of the video file ....
  5. Just to mention: The above described Problem is still there in 1.5.0:I Created a new Sequence, safed it as "MCU" wich led to the file MCU.cvseq. Then i modified the sequence, safed it under a new name MCU 4k (File: MCU 4.cvseq). But the load window displays this sequence as "MCU (MCU 4k)" and not like expected "MCU 4k". ....still pretty confusing.
  6. ANY Update is highly appreciated!
  7. @rdsp I think it is not fair to say that Kodi is "BREAKING" any Add-ons. The Add-ons still fuction like they did before. But if the Platform that the Add-ond run on (=Kodi) changes then is is simply a matter of fact that the output of the Add-ons is affected as well. It was not Team Kodi´s decission, that Python2 is not supported anymore and nobody is forced to upgrade to Matrix before your most beloved Add-ons are adjusted.
  8. I Have updated tp Matrix as well. Now i miss CV
  9. I Upgraded to Matrix as well, unfortunately at the Price of loosing CV
  10. Hi! Any news to this topic, now that 19.0 is out? Has anybody already tried? I am stil on 18.9 with CV working just fine...
  11. Hi! Any news to this topic, now that 19.0 is out? Has anybody already tried?
  12. 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? 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
  13. ...more a question than a Feature Request: With Kodi 19 just around the corner and CinemaVison not listed on the Matrix Repository (yet) i woud be curious if Cinemavision will run on Matrix?
  14. 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.
  15. @MartinsVision: ...correct, Filename, not Folder.
  • Create New...

Important Information

By using this site, you agree to our Guidelines and Terms of Use.