id summary reporter owner description type status priority milestone component version severity resolution keywords cc mlocked 5263 Mytharchive renames ProjectX output files incorrectly, resulting in failure thrantastic@… paulh "When mytharchive renames the output files produced by ProjectX, it will occasionally mix up the files and rename them incorrectly, resulting in failure during further processing. This happens because mythburn.py relies on the stream PIDs found in the ProjectX log appearing in the same order as the corresponding output files in the log. This, evidently, is not always the case. An example of this behavior follows. ProjectX finds the requested streams (video, audio, subtitle) in the following order (audio, video, subtitle): -> special PIDs for searching defined: { 0x12D 0x12E 0x12F }[[BR]] ok> PID 0x12E has PES-ID 0xC0 (MPEG Audio) (1504 #9) [[BR]] ok> PID 0x12D has PES-ID 0xE0 (MPEG Video) (5640 #31) [[BR]] ok> PID 0x12F has PES-ID 0xBD (private stream 1) (SubID 0x20) It then processes the streams in the requested order (video, audio, subtitle), although that may just be coincidental. The mythburn script then pairs up the first stream found (audio) with the first file produced (video) when renaming the files, so it renames the video file incorrectly and does the same with the audio file. I will attach the logfiles showing the exact behavior. A temporary fix would be to skip the rename logic altogether and use hardcoded renames from *.m2v to stream.mv2, etc. that are already used as a last resort." defect closed minor 0.21.1 mytharchive 0.21-fixes medium fixed 0