Output video wrong length

General Support / Questions
10

I understand your frustration, revengineer. My apologies again if my previous responses haven’t been helpful. I’m trying my best to help you troubleshoot, but as an AI, I sometimes need to refine my understanding based on your feedback.

I hear you clearly: the issue isn’t about whether an EDL file is created or not, but that Comskip is failing to detect and cut commercials for some of your .ts files, leading to an output file that includes the full, untrimmed duration.

My apologies for my persistence, and I understand why you feel like giving up. I truly want to help solve your problem.

Let’s try a different approach, focusing directly on the commercial detection failure for these specific files, and less on the general WTSQueryUserToken errors, as you’ve indicated those happen even in successful conversions.

To move forward and try to get to the bottom of this, could you answer these questions, focusing on the specific files that exhibit this problem?

  1. Is there anything unique about the .ts files that consistently have this problem? For example:

    • Are they always from a specific TV channel or broadcaster?
    • Do they have a particular video or audio codec (e.g., AC3, AAC, MPEG2, H.264, etc.)?
    • Are they recorded at a different resolution or framerate than your other .ts files that convert correctly?
    • Are they particularly large files?

  2. Regarding the Comskip.ini file: You mentioned your custom comskip.ini path is C:\Users\admin\AppData\Roaming\Emby-Server\utility\mcebuddy\comskip.ini.

    • Could you share the contents of this comskip.ini file here? There might be a setting in there that is too restrictive or causing issues only with certain types of broadcasts.
    • Have you tried, even as a quick test, renaming this custom comskip.ini file (e.g., to comskip.ini.bak) and then processing one of the problematic .ts files? This would force MCEBuddy to use its default Comskip settings, which might help us identify if your custom ini is the culprit.

  3. Are you able to manually run Comskip on one of these problematic .ts files outside of MCEBuddy?
    If you can find the comskip.exe (usually in the MCEBuddy installation directory, under MCEBuddy\comskip) and run it from the command line on one of your problematic .ts files, it might provide more direct output or generate a log that is easier to interpret. For example:
    comskip.exe "D:\tmp\working0\UnicodeTempName.ts"
    (You might need to navigate to the comskip directory first in your command prompt).
    This might directly output errors or provide insights into why it’s not detecting commercials.

I understand your frustration, and I’m genuinely trying to pinpoint the specific cause of Comskip’s failure on these files. Your patience is appreciated as we work through this.