After reading a lot, apparently the issue has to do with changes in JF database that were made when going from 10.8.13 to 10.9. The plugin only provides the pre roll video before the movie, but playback is in charge of JF. From what I’ve read, the problem would be that API calls are no longer correctly sent/received when it comes to the transition from the pre roll video to the movie. In other words, the plugin should be fine, no permissions issues, files should be ok, but because of breaking changes the server is no longer following the instruction of going from the pre roll to the movie (hence, if you press the play next button, the movie does indeed start).
And apparently it’s a very extended issue, I found a lot of reports and even Google’s AI, when asked about issues of the local intros plugin, always mentions this very same issue as the most prevalent one (pre roll playing ok, movie not starting automatically until play next is pressed). This being a database/API calls issue may also explain why it suddenly started happening after a major JF update, and also why other third party plugins with the same purpose (like Cinema Mode) exhibit the exact same behavior (it shouldn’t be a plugin issue, but most likely a JF Server or Web one). The only weird thing if this is the real reason of the issue is why it doesn’t happen to everyone, but it does make sense. Going back to 10.8.13 being the only proven fix for this (and in all cases) just adds to the argument that it must be something in JF server or Web (probably server) that broke the plugin since 10.9.
I wouldn’t even know how to start to troubleshoot this (don’t have a clue which files of source should I start looking into), but if that’s the reason the plugin is not usable, then it probably won’t be fixed until JF devs get their hands on it instead of the plugins authors.
Hopefully someone can take a look at this, but since the plugin apparently is not working for a bit chunk of the user base, shouldn’t it be taken out of the repo until it’s fixed? Or marked as “experimental” or “buggy”, to avoid confusion?
PS: I remember that the logs I obtained when the pre roll didn’t transition to the movie mentioned some issues regarding the database. I don’t have them at hand now, but that would make it even more clear where the issue is and where to start looking at.
And apparently it’s a very extended issue, I found a lot of reports and even Google’s AI, when asked about issues of the local intros plugin, always mentions this very same issue as the most prevalent one (pre roll playing ok, movie not starting automatically until play next is pressed). This being a database/API calls issue may also explain why it suddenly started happening after a major JF update, and also why other third party plugins with the same purpose (like Cinema Mode) exhibit the exact same behavior (it shouldn’t be a plugin issue, but most likely a JF Server or Web one). The only weird thing if this is the real reason of the issue is why it doesn’t happen to everyone, but it does make sense. Going back to 10.8.13 being the only proven fix for this (and in all cases) just adds to the argument that it must be something in JF server or Web (probably server) that broke the plugin since 10.9.
I wouldn’t even know how to start to troubleshoot this (don’t have a clue which files of source should I start looking into), but if that’s the reason the plugin is not usable, then it probably won’t be fixed until JF devs get their hands on it instead of the plugins authors.
Hopefully someone can take a look at this, but since the plugin apparently is not working for a bit chunk of the user base, shouldn’t it be taken out of the repo until it’s fixed? Or marked as “experimental” or “buggy”, to avoid confusion?
PS: I remember that the logs I obtained when the pre roll didn’t transition to the movie mentioned some issues regarding the database. I don’t have them at hand now, but that would make it even more clear where the issue is and where to start looking at.