(2015-09-15, 21:34)schumi2004 Wrote: @scott,

Any plans to add extra arguments to script?

I'm asking this since you could use CinemaExperience from main screen widgets by adding extra information to the onclick action.
This is a piece of example code from MQ6 where a button is added for Cinema Experience on main screen for recently added movies.

Code:

<onclick>RunScript(script.cinema.experience,movieid=$INFO[Container(510).ListItem.Property(DBID)])</onclick>

It's this part i would like to see added (if possible )

movieid=$INFO[Container(510).ListItem.Property(DBID)

That way we could parse the current movie highlighted when using widgets in skin.

(2015-09-15, 23:14)Dave the Minion Wrote:

(2015-09-15, 21:34)schumi2004 Wrote: @scott,

Any plans to add extra arguments to script?

I'm asking this since you could use CinemaExperience from main screen widgets by adding extra information to the onclick action.
This is a piece of example code from MQ6 where a button is added for Cinema Experience on main screen for recently added movies.

Code:

<onclick>RunScript(script.cinema.experience,movieid=$INFO[Container(510).ListItem.Property(DBID)])</onclick>

It's this part i would like to see added (if possible )

movieid=$INFO[Container(510).ListItem.Property(DBID)

That way we could parse the current movie highlighted when using widgets in skin.

This would be up to the skinner, would it not?

(2015-09-16, 04:14)scott967 Wrote:

(2015-09-15, 23:14)Dave the Minion Wrote:

(2015-09-15, 21:34)schumi2004 Wrote: @scott,

Any plans to add extra arguments to script?

I'm asking this since you could use CinemaExperience from main screen widgets by adding extra information to the onclick action.
This is a piece of example code from MQ6 where a button is added for Cinema Experience on main screen for recently added movies.

Code:

<onclick>RunScript(script.cinema.experience,movieid=$INFO[Container(510).ListItem.Property(DBID)])</onclick>

It's this part i would like to see added (if possible )

movieid=$INFO[Container(510).ListItem.Property(DBID)

That way we could parse the current movie highlighted when using widgets in skin.

This would be up to the skinner, would it not?

Well, you maybe could do it just with skin code, but I took a look in Aeon MQ5 skin, and found I could hack the service.skin.widgets addon to make this work by first adding the widget movie to the video playlist then calling RunScript(cinemavision,experience) from within skin.widgets (I tried just using skin code but had a problem that cinemavision needs to wait for the playlist to get updated before running, or you get the "empty playlist" notification. It would be nicer if cinemavision could add new arguments to add-to-playlist-and-run for movies and maybe episodes.

scott s.
.

(2015-09-15, 03:06)shaktoo Wrote: CV-S : call me lazy but Will you consider an all in one download solution it feels like a SIGNIFICANT amount of customization.. helluva lot more then my Madnox ..I just dont have the luxury of having that much time spending on downloading & setting up bumpers etc etc. PLEASE consider a full .. (pre-set in appropriate folder structure as required complete) zip of EVERYTHING for maybe donors ?

(2015-09-15, 04:09)MidnightWatcher Wrote: I am happy to report that the CV actions to toggle "Adjust Display Refresh Rate" On (On Start / Stop) and Off are working perfectly! The first item in the sequence is an action to turn it "Off". All slides, video bumpers and trailers then play at 60 Hz. Once that portion of the sequence is completed, a CV action to enable "Adjust Display Refresh Rate" to "On Start / Stop" then forces the main feature to 1080/24p. Voila. After some testing I noticed that I had to go into KODI's settings and enable it there first before playing the CV sequence. Evidently KODI didn't like the CV action to turn it Off when it was already off -- this caused the sequence to crash. But now everything is a-ok. Once the Rapier skin refreshes with the new release that will suppress the busy dialog when CV is running I'll be all set. CinemaVision. Best. Add on. Ever!

(2015-09-15, 13:24)chriskeens Wrote: Using version 0.0.35. I'm having issues with trailers. I have it set to play 2 trailers from iTunes but it just keeps playing the same 2 trailers every time?

my log: http://pastebin.com/P1V9xfTf

(2015-09-15, 21:34)schumi2004 Wrote: @scott,

Any plans to add extra arguments to script?

I'm asking this since you could use CinemaExperience from main screen widgets by adding extra information to the onclick action.
This is a piece of example code from MQ6 where a button is added for Cinema Experience on main screen for recently added movies.

Code:

<onclick>RunScript(script.cinema.experience,movieid=$INFO[Container(510).ListItem.Property(DBID)])</onclick>

It's this part i would like to see added (if possible )

movieid=$INFO[Container(510).ListItem.Property(DBID)

That way we could parse the current movie highlighted when using widgets in skin.

(2015-09-15, 22:30)MidnightWatcher Wrote: @CinemaVision-Scott, are there plans to have a list to choose from when the CinemaVision button is selected in the movie info page? It would be nice to have a list of different sequences to select. For instance, if we're watch The Incredibles I'd opt for a sequence that had bumpers more geared toward that sort of genre and all the trivia slides would be Pixar-related. For an action film I'd select a sequence more geared towards that genre ...

(2015-09-16, 09:08)kgian Wrote: I tried the cinemavision plugin in two of my computers. I tried the latest version 0.0.35. To test the simplest functionality I just selected to play 1 itunes trailer and then the feature. Nothing else.

In my first desktop with kodi 14.2 and windows 10 it did not work. I que the movie, go to cinemavision plugin and select play from the context menu. Nothing happens at all. I had tried in that computer with 0.0.32. Also the same behaviour. Between uninstalling 0.0.32 and installing 0.0.35 I deleted the plugin folder manually.

In my second desktop with kodi 14.2 and windows 7 it worked fine. Did the same moves and it just worked.

I have not tried in my 2 htpcs or my openelec Raspberry pi installation. If I have time I will try them and report back...

(2015-09-16, 14:54)kgian Wrote: I tried cinema vision in my main HTPC. Windows 7, kodi 14.2.

Basic functionality is working. I get 2 trailers, then the audio bumper then the feature. I don't need anything else for now.

I tried to add the cinemavision button to the movie info page of confluence. I edited the dialogvideoinfo.xml file and pasted the code. Gave the button an unused number id. When I press info, I see the cinemavision button. I select it and then I get the cinemavision screen with the movie on the left and the buttons play and cancel on the right. I select the movie and then play.

My sequence starts and plays the trailers, the audio bumper but the movie won't play. I get returned to the movies list.

If I go through the addons-->(context) play sequence everything works, but I would like the cinemavision button to work too.

I could not try the context menu plugin as I am still using kodi 14.2 and it requires kodi 15.

(2015-09-16, 09:38)schumi2004 Wrote:

(2015-09-16, 04:14)scott967 Wrote:

(2015-09-15, 23:14)Dave the Minion Wrote: This would be up to the skinner, would it not?

Well, you maybe could do it just with skin code, but I took a look in Aeon MQ5 skin, and found I could hack the service.skin.widgets addon to make this work by first adding the widget movie to the video playlist then calling RunScript(cinemavision,experience) from within skin.widgets (I tried just using skin code but had a problem that cinemavision needs to wait for the playlist to get updated before running, or you get the "empty playlist" notification. It would be nicer if cinemavision could add new arguments to add-to-playlist-and-run for movies and maybe episodes.

scott s.
.

I also checked for function to add it to queue but only thing found is <onclick>queue</onclick>
But then we still need to identify movie highlighted and that i don't know how to accomplish.

(2015-09-16, 21:59)scott967 Wrote: Since skin widgets stores the movie dbid as a property I could use it in a JSON call to playlist.add in python. What I do is this:

Code:

xbmc.executeJSONRPC('{ "jsonrpc": "2.0", "method": "Playlist.Add", "params": {"playlistid": 1 , "item": { "movieid": %d } },  "id": 1 }' % int(self.MOVIEQUEUE))
xbmc.executebuiltin('XBMC.RunScript(script.cinemavision,experience)')

where MOVIEQUEUE is an argument I pass to my script containing the movie dbid.

scott s.
.

(2015-09-17, 00:05)popcorn903 Wrote: Hi Scott,
I just tested v0.0.37 quickly and it seems most of the time only one module will play before the movie, usually the trailer, but I have also had it play the countdown.
I'm still getting the sequence editor malfunctions as well - would this be fixed in an upcoming release or is the cause unknown?
Here is my log.

(2015-09-17, 00:17)CinemaVision-Scott Wrote:

(2015-09-17, 00:05)popcorn903 Wrote: Hi Scott,
I just tested v0.0.37 quickly and it seems most of the time only one module will play before the movie, usually the trailer, but I have also had it play the countdown.
I'm still getting the sequence editor malfunctions as well - would this be fixed in an upcoming release or is the cause unknown?
Here is my log.

Not sure about the sequence editor malfunctions - we thought we had that handled. We'll take another look. Can I also get a log from you where you're updating the content?

(2015-09-17, 00:58)popcorn903 Wrote:

(2015-09-17, 00:17)CinemaVision-Scott Wrote:

(2015-09-17, 00:05)popcorn903 Wrote: Hi Scott,
I just tested v0.0.37 quickly and it seems most of the time only one module will play before the movie, usually the trailer, but I have also had it play the countdown.
I'm still getting the sequence editor malfunctions as well - would this be fixed in an upcoming release or is the cause unknown?
Here is my log.

Not sure about the sequence editor malfunctions - we thought we had that handled. We'll take another look. Can I also get a log from you where you're updating the content?

Yep, no problem. Here you go