On Wed Dec 7 09:50:52 2022 +0000, Nikolay Sivov wrote:
Does this change too much? Instead of letting stop command pass through pending check, all commands know won't wait for completion of currently executing command. For example doing start -> pause won't have END_OF_PRESENTATION set, and I don't think it should try to pause before pipeline completed transition.
I think the normal commands are still executed one after another? The `session_submit_command` still checks whether the command list is empty before queueing the command to the thread pool. If it's not empty it means another command is either pending for execution, or waiting on `END_OF_PRESENTATION` to complete.