I’m submitting this under suggestions, but I believe it’s more a consistency bug than a suggestion.
When, at the end of an episode of a series, I press the on-screen “Next” button, that episode is marked as watched and playback moves to the next one. However, if I use Siri to go to the next episode, the current one is not marked as watched. The behavior should be the same in both cases.
I don’t know for sure but I do know that some translations in the past have been a problem. Just trying to get the info that may be needed to answer your question correctly.
Just curiosity on my part but have you tried just “Next” or “Next Episode” instead of “Next Chapter”? I know there’s a next chapter command when you click the right remote button and that may be different from the “Next” button internally to Infuse.
The setting you have for Chapter Controls may also have an affect on what happens but this is just a guess on my part.
I agree with you, this seems more like a bug than a feature but I just wanted to dig a little to help narrow it down.
The voice command used with Siri is irrelevant; it makes no difference whether you say “Next”, “Next chapter”, or “Next episode”. Siri translates all of these into the same command for Infuse. I doubt that the Siri–Infuse integration is refined enough to have different commands for skipping chapters, where some mark the chapter as watched and others do not.
There are series whose end credits are very long, and this means that for the “Next episode” button to appear you have to fast-forward until it shows up and then press it. However, with the voice command “Next” it takes much less time and is more convenient, but on the other hand it leaves the episodes unmarked as watched, and in the tracking on the main Infuse page it then shows the previous episode to the one I am actually watching as not finished.
In fact, the solution is very simple and I do not understand why it does not already work. The code associated with the “Next episode” button is what should be executed when the Siri voice command skips to the next episode. Apparently, you have two separate codes that perform different actions depending on whether it is a voice command or a press of that button. This is inconsistent.