[Bug 52979] New: TSMuxer introduces a rectangle at the end of every line when muxing an .srt file into a .m2ts container
https://bugs.winehq.org/show_bug.cgi?id=52979 Bug ID: 52979 Summary: TSMuxer introduces a rectangle at the end of every line when muxing an .srt file into a .m2ts container Product: Wine Version: 7.8 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs(a)winehq.org Reporter: shagooserver(a)gmail.com Distribution: --- Created attachment 72348 --> https://bugs.winehq.org/attachment.cgi?id=72348 error example TSMuxer is essentially a muxing program to combine the 3 types of streams found in a movie, video, audio and subtitles into a container file so the movie can be watched on a player, VLC for example, in this instance that is a .m2ts container file. As part of the muxing process TSMuxer converts the .srt file into a .pgs stream/file to meet the specification for a .m2ts container. My testing has shown that any .srt file is affected, regardless of it's source. Please see the attachment which shows the rectangle which is added to the end of every line. TSMuxer is available at: https://github.com/justdan96/tsMuxer I have spot tested releases for the last 2 years with the same result because everything is labelled as pre release. The program was originally launched in 2004 as far as I can tell. I have mainly been testing the Windows 64 bit releases but also a 32 bit release with exactly the same problem. The easiest way to get the files needed would be to download a TV show from the internet which includes subtitles and is in a .mkv container. MKV containers support .srt subtitles natively so it just needs to be demuxed. Any other container type other than mkv will require additional steps to convert whatever subtitle stream it contains into an .srt file. Once you have the 3 file types (usually h264, ac3 and srt) just open TSMuxer and drag these 3 files into the top window from your file manager, h264 file first. Apologies if you feel I am trying to teach you how to suck eggs. I am available to lend any assistance if needed. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52979 --- Comment #1 from Scott <shagooserver(a)gmail.com> --- I missed another issue when reporting this. After the letter U is encountered the remainder of the line of text is rendered in black as opposed to the normal white colour. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52979 Scott <shagooserver(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #2 from Scott <shagooserver(a)gmail.com> --- This bug was in the code of TSMuxer (GraphicsPath::AddString call in the Win32 subtitle renderer.). For info, this bug was not apparent when the program was run on Windows. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52979 Scott <shagooserver(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |UNCONFIRMED Resolution|INVALID |--- --- Comment #3 from Scott <shagooserver(a)gmail.com> --- Upon fixing this bug a movie rendered by TSMuxer now shows no subtitles. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52979 Scott <shagooserver(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|TSMuxer introduces a |TSMuxer produced movies do |rectangle at the end of |not provide a subtitle |every line when muxing an |stream available to VLC or |.srt file into a .m2ts |MPV. |container | -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52979 Ken Sharp <imwellcushtymelike(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|TSMuxer produced movies do |TSMuxer introduces a |not provide a subtitle |rectangle at the end of |stream available to VLC or |every line when muxing an |MPV. |.srt file into a .m2ts | |container Keywords| |download, source See Also| |https://github.com/justdan9 | |6/tsMuxer/issues/598 URL| |https://github.com/justdan9 | |6/tsMuxer --- Comment #4 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- (In reply to Scott from comment #2)
This bug was in the code of TSMuxer (GraphicsPath::AddString call in the Win32 subtitle renderer.).
For info, this bug was not apparent when the program was run on Windows.
Interesting. But could a Wine bug be found here? TSMuxer is open source - so in theory yes, but I'll let someone more knowledgeable decide this. https://github.com/justdan96/tsMuxer/issues/598 Don't just change the scope of bug reports! If you have a new bug open a new bug report. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52979 --- Comment #5 from Scott <shagooserver(a)gmail.com> --- The change in, "the scope of bug reports" is the result of progress in the code by the developer. The issue you quote in your reply is an issue I opened with them which has now been corrected. That issue was masking the fact that TSMuxer does not work on wine. I am trying to make the wine devs aware of what has happened so they are not wasting time chasing a problem that has been corrected. If you feel this bug as initially reported should be closed as it is no longer a bug I am happy with that and I am happy to create a new one reflecting the result of the recent changes to the program, please advise. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=52979 --- Comment #6 from Ken Sharp <imwellcushtymelike(a)gmail.com> --- New bug = new bug report. If this should be closed I'm leaving to a developer to consider. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla