CinemaVision crashing during local trailers

[munificent 1]

On 13/12/2015 at 6:18 AM, Rippmaster said:

am i thinking wrong here, couldnt you use any folder using cinemavision and just naming it trailers in the sequence?

Very late in replying to this, thanks to the Christmas break, but CinemaVision regularly crashes when local trailers are part of the sequence. I have been trying to get it to work for months and am close to giving up on CinemaVision because of it.

Another small scraper pulls down trailers for me overnight to a local folder. I ask CinemaVision to play some items from this local folder within the sequence. To pre-empt the question, yes, CV can see the source folder (Trailers within the CV content folder). Sometimes it will play one, maybe two of the local trailers I ask it to play before crashing out of the sequence and returning me to Kodi.

I have checked that Kodi can play the trailers which are scraped from HDTrailers.net and yes it can. I've tried with an adapted default sequence and a new sequence from scratch. I've tried asking CV to play one Trailer item with 3 trailers or 3 Trailer items with 1 trailer each. It doesn't matter. Crash upon crash upon crash.

As trailers are a huge part of the CV experience for me, this is a real game-breaker.

[munificent 1]

2 hours ago, Ragnarok said:

Version 1.0.9 is in the official repository with the fix! Let me know how it goes.

Rag, the fix is in and the one time I have tried it so far, it worked like a charm. I will do some testing to confirm but I'd like to thank you again for getting on this and identifying the problem.

You were right about two trailers. I guess I must have switched that up at some point to try and break the cycle of crashes.

I'm glad to have helped play a part in improving the addon in a small way and I'm very grateful to you and the team for the work you've done in taking this on and helping a film become an experience. Seeing the sequence actually work is a joy.

[Ragnarok 198]

On 1/3/2016 at 2:37 AM, munificent said:

Very late in replying to this, thanks to the Christmas break, but CinemaVision regularly crashes when local trailers are part of the sequence. I have been trying to get it to work for months and am close to giving up on CinemaVision because of it.

Another small scraper pulls down trailers for me overnight to a local folder. I ask CinemaVision to play some items from this local folder within the sequence. To pre-empt the question, yes, CV can see the source folder (Trailers within the CV content folder). Sometimes it will play one, maybe two of the local trailers I ask it to play before crashing out of the sequence and returning me to Kodi.

I have checked that Kodi can play the trailers which are scraped from HDTrailers.net and yes it can. I've tried with an adapted default sequence and a new sequence from scratch. I've tried asking CV to play one Trailer item with 3 trailers or 3 Trailer items with 1 trailer each. It doesn't matter. Crash upon crash upon crash.

As trailers are a huge part of the CV experience for me, this is a real game-breaker.

Does that scraper store the trailers in the root of that local folder? If it's a custom folder, and not the %CVROOT%\Trailers folder, CinemaVision won't scan recursively through it to get nested content. Can I get a log from you where you update the content and try to play your sequence with a crash? Once we know what it's doing we should be able to fix the issue. I will say that because of all the conferences Team Kodi is headed to, that a fix might be a little delayed as our developer is out of pocket until the conferences are finished.

We have two items on our list that should fix this issue for good. We'll be adding support for HDTrailers and a few others, and adding support to download trailers in the background or during content updates as well.

[munificent 1]

Yes, sure. I will read up how to generate a log and get one to you. To answer your questions, it's the %CVROOT%\Trailers folders (my root folder being called Cinema Experience). All trailers are dumped in that folder, not sub-folders, so a recursive scan is not required. Crashes still happening all the live long day.

A log to follow.

[munificent 1]

On 04/01/2016 at 6:28 PM, Ragnarok said:

Does that scraper store the trailers in the root of that local folder? If it's a custom folder, and not the %CVROOT%\Trailers folder, CinemaVision won't scan recursively through it to get nested content. Can I get a log from you where you update the content and try to play your sequence with a crash? Once we know what it's doing we should be able to fix the issue. I will say that because of all the conferences Team Kodi is headed to, that a fix might be a little delayed as our developer is out of pocket until the conferences are finished.

We have two items on our list that should fix this issue for good. We'll be adding support for HDTrailers and a few others, and adding support to download trailers in the background or during content updates as well.

The log is attached. This one is a good log since it shows the sequence playing three trailers as it should for the first time ever. I then ran CinemaVision a second time and got a crash of the kind I regularly get. In case it helps troubleshoot the issue, the only thing that appeared to be different with the successful running of CinemaVision that first time was that the content scraper seemed to have hung, or was still processing. Quite possibly a complete red herring but worth mentioning in case it proves not to be.

munificent_log.txt

Edited January 11, 2016 by munificent

[Ragnarok 198]

On 1/11/2016 at 6:22 AM, munificent said:

The log is attached. This one is a good log since it shows the sequence playing three trailers as it should for the first time ever. I then ran CinemaVision a second time and got a crash of the kind I regularly get. In case it helps troubleshoot the issue, the only thing that appeared to be different with the successful running of CinemaVision that first time was that the content scraper seemed to have hung, or was still processing. Quite possibly a complete red herring but worth mentioning in case it proves not to be.

munificent_log.txt

Alright we're a bit of the way there. From your log, it looks like the initial crash happens 11 seconds after CinemaVision finishes, and there are a number of services running at that time including Next Up and Genesis. Both of which crash after CinemaVision exits successfully:

20:49:09 T:4084  NOTICE: [- CinemaVision -]: Experience: Visualization: RESTORED
20:49:09 T:4084    INFO: CPythonInvoker(19, C:\Users\Affirmative Action\AppData\Roaming\Kodi\addons\script.cinemavision\addon.py): script successfully run
20:49:09 T:4084    INFO: Python script stopped

What I need from you are two more logs with crashes. That will show us if there's a pattern surrounding the crashes. I'm not real sure if one of those services is attempting to run against content in CinemaVisions playlist or what, yet.

[munificent 1]

Roger that, I will get on it and provide two more crash logs.

Very interesting to see that CinemaVision exits successfully, though, as surely it would not exit successfully until it had completed its sequence? In the case of this crash it had definitely not completed its sequence as it had not played the trailers, nor the audio format bumper, nor the feature itself!

Whether that is irrelevant semantics or not I don't know but it seems like the definition of successful in the eyes of the script may be wrong. Either way, I will provide two more logs shortly to shed more light on this one and I appreciate you taking the time to investigate.

[Ragnarok 198]

6 hours ago, munificent said:

Roger that, I will get on it and provide two more crash logs.

Very interesting to see that CinemaVision exits successfully, though, as surely it would not exit successfully until it had completed its sequence? In the case of this crash it had definitely not completed its sequence as it had not played the trailers, nor the audio format bumper, nor the feature itself!

Whether that is irrelevant semantics or not I don't know but it seems like the definition of successful in the eyes of the script may be wrong. Either way, I will provide two more logs shortly to shed more light on this one and I appreciate you taking the time to investigate.

That was our thought exactly. I'm wondering if one of the services running sees that a video played and finished, and does something to stop playback as if the script exited successfully. We'll see if there's a pattern in the logs, and might get you to disable some stuff one by one till we figure out what's up. We're always happy to help!

[munificent 1]

Two more logs are attached. In log 2, CV did not reach the trailers at all. In log 3 it got to one trailer played then crashed out before trailer 2 or 3 could play. In case it helps, my sequence goes:

Theatre Intro

Policy Spot

Trailer Intro

(inevitably, CV will play these just fine. I can skip ahead or mess around and it's not bothered, it's only after that where things go wrong)

Trailers exclusively from local folder x3

Feature Intro

Audio Bumper

BBFC Rating

Feature

Sometimes when CV crashes it will just kick back out to the Movies launch page of Confluence. Sometimes there is a flash of the code behind CV. I see a small amount of white text on a black BG (estimate 15 lines or so) before it kicks me back out. There is no possibility to read what's on the screen as it's a flash of less than half a second.

I am more than happy to eliminate services one by one to try and help track down the cause of this. Also by way of an FYI I am running Beta 2. If you need me to update I will but I was waiting on a release candidate before I did that as updating seems to break so much stuff!

munificent_log2.log

munificent_log3.log

[Ragnarok 198]

2 hours ago, munificent said:

munificent_log2.log

munificent_log3.log

So from your log, it looks like your trailer module is set up to play two trailers instead of three.

16:35:58 T:1624  NOTICE: [- CinemaVision -] (API): [- trailer -]
16:35:58 T:3776   DEBUG: ------ Window Deinit (C:\Users\Affirmative Action\AppData\Roaming\Kodi\addons\script.cinemavision\resources\skins\Main\1080i\script.cinemavision-playlist-dialog.xml) ------
16:35:58 T:1624  NOTICE: [- CinemaVision -] (API): source: 'dir'
16:35:58 T:1624  NOTICE: [- CinemaVision -] (API): scrapers: 'Content'
16:35:58 T:1624  NOTICE: [- CinemaVision -] (API): order: 'random'
16:35:58 T:1624  NOTICE: [- CinemaVision -] (API): file: ''
16:35:58 T:1624  NOTICE: [- CinemaVision -] (API): dir: 'C:\\Cinema Experience\\Trailers\\'
16:35:58 T:1624  NOTICE: [- CinemaVision -] (API): count: 2
16:35:58 T:1624  NOTICE: [- CinemaVision -] (API): ratingLimit: 'none'
16:35:58 T:1624  NOTICE: [- CinemaVision -] (API): ratingMax: 'BBFC.R18'
16:35:58 T:1624  NOTICE: [- CinemaVision -] (API): limitGenre: False
16:35:58 T:1624  NOTICE: [- CinemaVision -] (API): filter3D: False
16:35:58 T:1624  NOTICE: [- CinemaVision -] (API): quality: '1080p'
16:35:58 T:1624  NOTICE: [- CinemaVision -] (API): volume: 100

Where do you see three in the interface? It's possible something isn't reporting right. That said, we've fixed the problem. CinemaVision was trying to play the NFO and JPG files stored with your trailers in addition to the trailers themselves. We just pushed an update to the repository that will fix that issue.

[Ragnarok 198]

On 1/14/2016 at 11:05 AM, munificent said:

munificent_log2.log

munificent_log3.log

Version 1.0.9 is in the official repository with the fix! Let me know how it goes.