Todays update crashes cinemavision

[Rippmaster 30]

I downloaded the latest cinemavision, went into addons, chose "install from zipfile" and installed cinemavision.

 

1. when i start it crashes

2. Apparently it did not find my sequence so i had to "import" the old sequence

4. still , when i try to run cinemavision (press C when on a movie, chose cinemavision) it crashes. it sais "check logs"what logs wher?

furthermore my logs say (that is what i think is erroring) i think its what sais below

 

(API): Sequence processing finished
17:11:30 T:2944  NOTICE: [- CinemaVision -]: Experience: Playing next item: VIDEO: u'C:\\cinemavision\\Video Bumpers\\Intermission\\coca cola vs pepsi spec commercial.mp4'
17:11:30 T:2944   ERROR: EXCEPTION Thrown (PythonToCppException) : -->Python callback/script returned the following error<--
                                             - NOTE: IGNORING THIS CAN LEAD TO MEMORY LEAKS!
                                            Error Type: <type 'exceptions.AttributeError'>
                                            Error Contents: 'Action' object has no attribute 'module'
                                            Traceback (most recent call last):
                                              File "C:\Users\Epic\AppData\Roaming\Kodi\addons\script.cinemavision\addon.py", line 18, in <module>
                                                player.begin()
                                              File "C:\Users\Epic\AppData\Roaming\Kodi\addons\script.cinemavision\lib\player.py", line 42, in begin
                                                e.start(seqPath)
                                              File "C:\Users\Epic\AppData\Roaming\Kodi\addons\script.cinemavision\lib\experience.py", line 853, in start
                                                return self._start(sequence_path)
                                              File "C:\Users\Epic\AppData\Roaming\Kodi\addons\script.cinemavision\lib\experience.py", line 872, in _start
                                                self.next()
                                              File "C:\Users\Epic\AppData\Roaming\Kodi\addons\script.cinemavision\lib\experience.py", line 1165, in next
                                                kodiutil.setGlobalProperty('module.next', self.processor.upNext() and self.processor.upNext().module._type or '')
                                            AttributeError: 'Action' object has no attribute 'module'
                                            -->End of Python script error report<--

[Ragnarok 192]

We made a bunch of adjustments to scrapers and the way we handled them in 0.0.45 and later versions. Some of the settings in your sequence are likely the old way of doing it, and have settings that are no longer valid. Since we're still beta software, it's always a good idea to do a clean uninstall and reinstall of the add-on and recreate your sequences if you have changed anything to use something other than a default. I would suggest doing a manual uninstall and reinstall, and any non-default settings in modules should be checked and reset.

Please keep in mind that until we hit a 1.0 release, things like this will keep changing as we improve the way we're doing things (both functionally and in regards to processing within the add-on).

[Rippmaster 30]

edit 17.30

 

 

-----------------

it seem to maby work when i create a whole new sequence. strange my old sequence wont work though

[Rippmaster 30]

Edit 18.06

 

The sequence tends to stop (blackscreen) before  trivia intro, just after a 6 minute "short movie"

Never happend before todays update. Just totally blackscreen.

 

Can i revert to a earlyer version? in the version from 2 weeks ago everything wer working glitch free.

 

plz need help

[Rippmaster 30]

We made a bunch of adjustments to scrapers and the way we handled them in 0.0.45 and later versions. Some of the settings in your sequence are likely the old way of doing it, and have settings that are no longer valid. Since we're still beta software, it's always a good idea to do a clean uninstall and reinstall of the add-on and recreate your sequences if you have changed anything to use something other than a default. I would suggest doing a manual uninstall and reinstall, and any non-default settings in modules should be checked and reset.

Please keep in mind that until we hit a 1.0 release, things like this will keep changing as we improve the way we're doing things (both functionally and in regards to processing within the add-on).

Hello

 

AFter 3-4 hours of testing and trying to find "why" my cinemavision krashes i have finally seen what it seems to be

 

its the hue actions. Whenever there is 1 hue action in my script, it will just go blackscreen after one or two video bumbers. Did something happen how the hue actions?

If i remove my hue actions it all works fine.?  ....

 

one hueaction starst a colour loop before trivia

---------------------------------

http://192.168.1.5/api/newdeveloper/groups/0/action
PUT:{"on":true,"bri":255,"effect": "colorloop"}

 

 

one hue action stops that colorloop

http://192.168.1.5/api/newdeveloper/groups/0/action
PUT:{"effect": "none"}

 

--------------------------------

 

this worked flawlessly before. something must have happend to how the hue communicates in the latest build? no problems in a couple of builds earlyer?

[Ragnarok 192]

Hello

 

AFter 3-4 hours of testing and trying to find "why" my cinemavision krashes i have finally seen what it seems to be

 

its the hue actions. Whenever there is 1 hue action in my script, it will just go blackscreen after one or two video bumbers. Did something happen how the hue actions?

If i remove my hue actions it all works fine.?  ....

 

one hueaction starst a colour loop before trivia

---------------------------------

http://192.168.1.5/api/newdeveloper/groups/0/action
PUT:{"on":true,"bri":255,"effect": "colorloop"}

 

 

one hue action stops that colorloop

http://192.168.1.5/api/newdeveloper/groups/0/action
PUT:{"effect": "none"}

 

--------------------------------

 

this worked flawlessly before. something must have happend to how the hue communicates in the latest build? no problems in a couple of builds earlyer?

Found the bug, and fixed it for 0.0.47. Thanks for reporting!

[Rippmaster 30]

fantastic!

love you guys :))