Skins with CinemaVision Support?

[HiggsB 0]

Hi,
I'm just wondering, if theres a list with Kodi skins that have a buildIn CinemaVision support?

Currently, I'm still using the standard skins of kodi 16 and 17 (I have 2 different installations on different machines).
The most important feature I'd like to use is replacing the Play Button so that I dont have to use the context menu everytime I play just one movie.

thanks

[Ragnarok 193]

51 minutes ago, HiggsB said:

Hi,
I'm just wondering, if theres a list with Kodi skins that have a buildIn CinemaVision support?

Currently, I'm still using the standard skins of kodi 16 and 17 (I have 2 different installations on different machines).
The most important feature I'd like to use is replacing the Play Button so that I dont have to use the context menu everytime I play just one movie.

thanks

Hey there! The new default Kodi skin, Estuary, has native CinemaVision support now. Below are the skins that we know have support, though I'm not sure how many work with new versions of Kodi. If you want to use a specific skin, just reach out to the developer and request CinemaVision support. We've got a whole guide dedicated to helping skinners and developers integrate with the product.

AeonFlex
Aeon Madnox [MOD]
Aeon MQ5 for Kodi 15 Isengard [MOD]
Aeon MQ6
Aeon MQ7
Aeon Nox 5: SiLVO [MOD]
Aeon ScopeNox [MOD]
AppTV
Arctic: Zephyr
Black Glass Nova
Eminence 2 [MOD]
Estuary
Fuse
Mimic
Phenomenal
Rapier
SiO2-X
Titan

Even if the skin you like doesn't have support for CinemaVision, that's what the CinemaVision Launcher add-on helps with. It's a context menu add-on that adds a CinemaVision button to the context menu for content in your library. That will allow you to trigger CinemaVision in the same way that a native CinemaVision button on the Movie Information screen does.

To address the replacement of the standard Kodi Play Button, that's something that we're working on. The Kodi Team wanted us to put that in a service add-on that is currently being planned. While it's not here yet, it's coming.

Edited March 6, 2017 by Ragnarok
Forgot to address the button replacement.

[HiggsB 0]

On 06/03/2017 at 5:47 PM, Ragnarok said:

Hey there! The new default Kodi skin, Estuary, has native CinemaVision support now. Below are the skins that we know have support, though I'm not sure how many work with new versions of Kodi. If you want to use a specific skin, just reach out to the developer and request CinemaVision support. We've got a whole guide dedicated to helping skinners and developers integrate with the product.

AeonFlex
Aeon Madnox [MOD]
Aeon MQ5 for Kodi 15 Isengard [MOD]
Aeon MQ6
Aeon MQ7
Aeon Nox 5: SiLVO [MOD]
Aeon ScopeNox [MOD]
AppTV
Arctic: Zephyr
Black Glass Nova
Eminence 2 [MOD]
Estuary
Fuse
Mimic
Phenomenal
Rapier
SiO2-X
Titan

Even if the skin you like doesn't have support for CinemaVision, that's what the CinemaVision Launcher add-on helps with. It's a context menu add-on that adds a CinemaVision button to the context menu for content in your library. That will allow you to trigger CinemaVision in the same way that a native CinemaVision button on the Movie Information screen does.

To address the replacement of the standard Kodi Play Button, that's something that we're working on. The Kodi Team wanted us to put that in a service add-on that is currently being planned. While it's not here yet, it's coming.

Thanks for the info.
I had a look at all skins that work on Kodi 17. Unfortunately I don't like most of them. Also not all seemed to work with cinemavision right away after installing them.
I used Metropolis for a very long time until some features appeared to be bugged and had to switch back to the default skins. I contact the devs of the metropolis skin and ask them to add cinemavision support.
Otherwise I just wait for the button replacement add-on for the official skins.

 

 

 

[Ragnarok 193]

20 hours ago, HiggsB said:

Thanks for the info.
I had a look at all skins that work on Kodi 17. Unfortunately I don't like most of them. Also not all seemed to work with cinemavision right away after installing them.
I used Metropolis for a very long time until some features appeared to be bugged and had to switch back to the default skins. I contact the devs of the metropolis skin and ask them to add cinemavision support.
Otherwise I just wait for the button replacement add-on for the official skins.

Sure thing! When we built CinemaVision, I reached out to all of the skin developers at the time, and created a nifty document that they can use to integrate the add-on easily. We also have the CinemaVision Launcher context item add-on, which can currently be used to launch CinemaVision in skins without support. Let us know if the folks behind Metropolis need any help!

[VonMagnum 13]

On 3/18/2017 at 3:47 PM, Ragnarok said:

Sure thing! When we built CinemaVision, I reached out to all of the skin developers at the time, and created a nifty document that they can use to integrate the add-on easily. We also have the CinemaVision Launcher context item add-on, which can currently be used to launch CinemaVision in skins without support. Let us know if the folks behind Metropolis need any help!

I'm desperately trying to modify Confluence for Isengard on my FireTV 4K, but all it did was cause it to lock up.  I modified the dialogbusy.xml script and the DialogKaiToast.xml script as it described and zipped it up and updated Kodi.  It seemed to do nothing (running CinemaVision just played the movie script as usual with the "working" busy indicator showing up as usual.  So I thought maybe I needed to exit/restart Kodi to get the skin to fully function.  That's when some dialogue window appeared at the bottom that flickered and I had no remote control over Kodi what-so-ever.  It just won't respond.  I'm now reinstalling from backup....a slow SLOW process for a backup with over 3GB of data (lots of thumbnails, etc.).  I don't know what caused that.  I plan to try again without the DialogKaiToast.xml modification since i have no idea what "popup" it's supposed to be suppressing there.   All I want is the "working" box in the lower right corner to not be there when using CinemaVision.  

I have yet to find a single skin I like better than Confluence.  Unfortunately, from the conversations I've seen, they had ZERO interest in adding a single optional support thing for either Cinema plugin to it.  I had to get the skin from my Mac install of Kodi since I could find no Isengard zip file to modify even (it only became an additional plugin with 17.x and 17.x causes a good chunk of my movie library to fail so I went back to Isengard which was the most stable version of Kodi I've used.  I honestly don't know how those lines could have caused that issue.  I'm afraid there might be something else going on like it doesn't like the Mac skin (I thought the underlying skins were all identical).

 

Having no luck getting Confluence to work so I tried some of those skins.  Arctic Zephyr (in Isengard at least) still showed a busy indicator right before the main feature so I'm not sure why it's on the list unless they have an update for newer Kodi versions that DOES work.  Most of the others were such hideous interfaces I couldn't stand to use them regardless.  Oddly, the one theme that did seem to work correctly was Metropolis.  I don't know about the default button, but with the launcher it worked fine and I saw no busy indicators at all.  I'm not crazy about the interface but it wasn't totally horrible (felt a bit slow for some things, though).  I'm not sure why AppTV looked awful, but it did.  The lack of previews at the top didn't help.

I tried and tried to find the Confluence directory installed on the FireTV and could not locate it.  AdbLink backup does not show it in the addons directory (where it is on my Mac version of Isengard) and adbLink has no apparent access to the main program directory.  I still don't know why installed a modified version of the one on my mac wouldn't work.  It SHOULD be identical to the one installed minus that change and I don't see why a line telling it to hide the busy indicator if CinemaVision is running would lock the interface.  I suspect something else is amiss, but I have no idea what.

 

Edited May 5, 2017 by VonMagnum

[VonMagnum 13]

After hours of playing with this stuff, I finally figured out what was locking up the skin mods using:

    <visible>IsEmpty(Window(Home).Property(script.cinemavision.running))</visible>

 

The guide on here suggests putting the line before the <controls> line.  This locks up every skin I tested it with.  I played with all kinds of settings (finding that false values or any values other than true or yes would get rid of the busy indicator, but nothing would do that AND keep it working when not using CinemaVision).  But it locked up on true values so how could it ever work?  I tried putting this at the start of the file too (right after <window>).  Same thing.

Well, I eventually had this nagging suspicion that the place it needed to go was somewhere else in the script and in fact, that was the case.  This worked for Confluence and ConZeitGeist and I'm pretty sure it would work with all of them.

You want to put it here instead:

    <controls>
        <control type="group">
            <visible>IsEmpty(Window(Home).Property(script.cinemavision.running))</visible>
            <left>1070</left>
            <top>640</top>

            ....

            etc.

I'm attaching a dialogbusy.xml file (from Confluence) here for people to easily look at to change whatever skin you like best to hide the busy dialog

 

DialogBusy.xml

Edited May 6, 2017 by VonMagnum
Additional Testing

[VonMagnum 13]

I believe I found an error in the Guide for skins.  It repeats this twice with two different bits of code one of which shows the code for running, but says it returns the Name:

This property returns a value of True if CinemaVision is running.

!IsEmpty(Window(Home).Property(script.cinemavision.running))

This property returns the Name of the Module running currently in the Sequence.

!IsEmpty(Window(Home).Property(script.cinemavision.running))

This property returns the Name of the Module running currently in the Sequence.

Window(Home).Property(script.cinemavision.module.next.name)

 

As you can see, the code is identical for the running and first "Name" with the second name a couple of spots down with code that appears to make more sense (i.e. ...next.name)

 

Edited May 6, 2017 by VonMagnum

[VonMagnum 13]

If anyone wants Confluence 3.1.0 (for 17.3 Krypton) modified so it suppresses the "working" busy indicator, I've attached a modified version here.  It only changes one line of code as illustrated above.  If anyone wants a version for 15.2 Isengard, I can provide one there as well.  I've also got a modified Arctic Zephyr Plus that also rids it of the busy indicator only when using CinemaVision.  Use the "add with zip" option under Add-Ons in the system preferences to install it (don't unzip it yourself).  You'll still need the CinemaVision launcher add-on here.  This only gets rid of the annoying "working" busy indicator that pulls you out of the cinema feel.

SkinConfluenceCinemaKrypton3.1.0.zip

[onlyyou 2]

Hi, can't find a way to get rid of this loading screen with Aeon Nox Silvo (kodi 18)

i've uploaded what i see just before the trailer (i only want 1 trailer then my movie)

i already try to edit the dialogbusy.xml but not success (bellow, the first part of the XML)

Many thanks !

<?xml version="1.0" encoding="UTF-8"?>
<window> 
	<visible>IsEmpty(Window(Home).Property(script.cinemavision.running))</visible>
	<controls>
		<control type="progress" id="10">
			<description>progress control</description>
			<width>1</width>
			<height>1</height>
			<texturebg />
			<lefttexture />
			<midtexture />
			<righttexture />
			<overlaytexture />
		</control>
		<control type="image">
			<include>FullscreenDimensions</include>
			<texture border="1" colordiffuse="AAFFFFFF">black.png</texture>
			<animation effect="fade" time="300">WindowOpen</animation>
			<animation effect="fade" time="300">WindowClose</animation>
		</control>
		<control type="group">
			<include>DialogOpenCloseAnimation</include>
			<control type="group">
				<visible>!System.Platform.Linux.RaspberryPi</visible>
				<left>912</left>
				<top>492</top>
				<control type="image">
					<description>Busy animation</description>
					<width>96</width>
					<height>96</height>
					<texture colordiffuse="$VAR[ThemeLabelColor]">android/spinner_48_inner_holo.png</texture>
					<aspectratio>keep</aspectratio>
					<animation effect="rotate" start="0" end="360" center="auto" time="2000" loop="true" condition="true">Conditional</animation>
				</control>
				<control type="image">
					<description>Busy animation</description>
					<width>96</width>
					<height>96</height>
					<texture colordiffuse="$VAR[ThemeLabelColor]">android/spinner_48_outer_holo.png</texture>
					<aspectratio>keep</aspectratio>
					<animation effect="rotate" start="360" end="0" center="auto" time="2000" loop="true" condition="true">Conditional</animation>
				</control>
				<control type="label">
					<description>Busy label</description>
					<width>96</width>
					<height>96</height>
					<textcolor>grey</textcolor>
					<align>center</align>
					<label>$INFO[Control.GetLabel(10),,%]</label>
					<font>font12</font>
					<visible>!Integer.IsEqual(Control.GetLabel(10), 0)</visible>
				</control>
			</control>

 

[Ragnarok 193]

Hey there! This is probably something you should forward on to the author of your skin. We have a guide built that walks skinners through supporting CinemaVision, here's the excerpt you're looking for.

Quote

 

Many of our users prefer that the Busy Dialog and Pop-ups are suppressed to improve the CinemaVision experience. While both of these things do improve the experience while CinemaVision is running, please keep in mind that your users will not know what's happening when a video is buffering, for example. Use these options at your discretion. These options should be added as a direct child of the <window> tag in the XML file. If you're unsure of where in the files to add the code, add it on the line before the <controls> tag. If you know what you're doing, add it where ever you need it to be.

We recommend that you add the option to suppress the busy dialog to your skins DialogBusy.xml file. To suppress the busy dialog when CinemaVision is running, add the following to the DialogBusy.xml file:

<visible>IsEmpty(Window(Home).Property(script.cinemavision.running))</visible>

We also recommend that you add the option to suppress pop-up notifications to your skins DialogKaiToast.xml file. To suppress pop-up notifications while CinemaVision is running, add the following to the DialogKaiToast.xml file:

<visible>IsEmpty(Window(Home).Property(script.cinemavision.running))</visible>

We do not recommend that you add the option to suppress your buffering dialog as this also suppresses the information and seek bar that is seen when you pause your content. If you want to do this despite our objection, here's how. To suppress the buffering, content information, and seek bar dialogs add the following to your skins DialogSeekBar.xml file:

<visible>IsEmpty(Window(Home).Property(script.cinemavision.running))</visible>

Again, I'd recommend forwarding this information over to the developer of your skin so that they can integrate it. Some skinners have integrated it, but only enable the option if a skin setting is enabled, so you might hunt around in your skin settings for that as well.