Welcome to Doom9's Forum, THE in-place to be for everyone interested in DVD conversion. Before you start posting please read the forum rules. By posting to this forum you agree to abide by the rules. |
|
|
Thread Tools | Search this Thread | Display Modes |
17th July 2017, 10:32 | #1361 | Link | |||||
PgcEdit daemon
Join Date: Jul 2003
Posts: 7,469
|
Quote:
Quote:
Quote:
Quote:
However, I agree that it saves a lot of PNG files. And currently, it doesn't force the user to create a new directory to keep all these files together. Perhaps you could add (as an option?) the automatic creation of a sub-directory when the XML is saved? That way, you won't need to pay attention to where you save it. It's just a suggestion... Quote:
Also, if currently, most (if not all, I don't know) timings internal to video, audio and subtitles streams are expressed in absolute and precise times (for their real frame rate), it's not at all the same thing in production, where precise time codes are not handy. They HAVE to be rounded at 24 fps, because we are human beings, and not machines. The fact that XML/PNG permits to use drop or non-drop times is complex, but that means only that that format has been correctly designed with video production and human beings in mind. It's one of its obvious advantages over the other formats. I haven't tried to change the DropFrame="False" option in the XML, but I suppose that it is there to support both drop and non-drop frames timecodes. If it's the case, it should be possible to use exactly the same time codes in the XML than with the other formats. Of course, when an XML/PNG file is saved at 24 or 25 fps (or any integer FPS), the drop frames problem is totally absent, and XML/PNG can be used very simply.
__________________
r0lZ PgcEdit homepage (hosted by VideoHelp) BD3D2MK3D A tool to convert 3D blu-rays to SBS, T&B or FS MKV Last edited by r0lZ; 2nd October 2017 at 14:24. Reason: typo |
|||||
17th July 2017, 10:57 | #1362 | Link | ||
PgcEdit daemon
Join Date: Jul 2003
Posts: 7,469
|
Quote:
Quote:
Are there other changes in later versions (except the problem of the missing subtitles) that have not been ported to your version, or is your version totally compatible with v5.1.2? I use v5.1.2 with BD3D2MK3D, and I would like to replace it with your version, but I don't want to risk some incompatibilities. Can you breifly summarize the changes that your version has not implemented, or direct me to the history of the changes of the old BDSup2Sub?
__________________
r0lZ PgcEdit homepage (hosted by VideoHelp) BD3D2MK3D A tool to convert 3D blu-rays to SBS, T&B or FS MKV Last edited by r0lZ; 17th July 2017 at 11:04. |
||
17th July 2017, 16:32 | #1363 | Link |
Registered User
Join Date: Jul 2017
Posts: 7
|
I based my version from 5.0.0. There are a lot of changes in later versions I guess, but those versions don't really work well. You would have to go to github and read each commit one by one after 5.0.0 to see what was implemented/fixed. They are a lot: https://github.com/mjuhasz/BDSup2Sub/commits/master
I tried to fix 5.1.2. I really tried. But it was so messy with so many errors that I picked the last version that worked (5.0.0) and started from there. Also I'm wondering what's the use you guys have for this software. Nowadays you can mux a SUP file into an MKV container, so you don't really need to convert SUP to anything else. In my specific use case, I want my MKVs untouched for several reasons and the subtitles external. SUP files can't be external files, they only work when they are inside of a container like MKV. But if I wouldn't mind to modify my MKVs, I would just put the SUPs inside of them, and there wouldn't be a need for BDSup2Sub. Last edited by Scorpius666; 17th July 2017 at 16:35. |
17th July 2017, 18:43 | #1364 | Link |
PgcEdit daemon
Join Date: Jul 2003
Posts: 7,469
|
Thanks for the link. I'll have a look...
I agree that untouched BD SUP muxed in MKV is the best solution... if your standalone player or TV supports that format. Personally, as I wrote above, I distribute BDSup2Sub with BD3D2MK3D (a GUI to convert 3D BDs to SBS or T&B MKVs). It is necessary to convert the 2D subtitles to 3D. The resize and combinations of the 2 views with the correct offset can only be done on XML/PNG streams, hence my interest for that format. But XML/PNG is used only to compose the images of the final 3D stream, that is finally re-converted to BD or DVD SUP format. BDSup2Sub is also used to extract the forced subtitles from the full stream. It's necessary for MKV, because most players are unable to dynamically display only the forced subs of a stream.
__________________
r0lZ PgcEdit homepage (hosted by VideoHelp) BD3D2MK3D A tool to convert 3D blu-rays to SBS, T&B or FS MKV Last edited by r0lZ; 17th July 2017 at 18:50. |
17th July 2017, 18:47 | #1365 | Link |
QB the Slayer
Join Date: Feb 2011
Location: Toronto
Posts: 697
|
My use for this software is pretty simple... when I remux BDs to MKV I only keep the subs for foreign/alien dialogue. And as we all know, many BD authors do different things to achieve this. I use this software to see what each sub track contains and see what is forced.
QB
__________________
|
17th July 2017, 19:25 | #1366 | Link | ||
Registered User
Join Date: Jul 2017
Posts: 7
|
Quote:
Quote:
|
||
18th July 2017, 07:59 | #1367 | Link | |
PgcEdit daemon
Join Date: Jul 2003
Posts: 7,469
|
Quote:
But I agree that currently, the conversion to 3D is slow and may be faster if I write the parsing combined with the conversion to 3D myself. However, I'm not sure it is worth doing it. The 3D is slowly dying, BD3D2MK3D is mature and stable, and I don't have the intention to modify it deeply any more. But perhaps YOU are interested in adding the conversion to 3D inside BDSup2Sub ? If it's the case, I can help you. I know how the images must be combined, how to retrieve the 3D offsets from the so called 3D-Planes (or from the SEI messages of the MVC video stream), and the resize of the bitmaps is already present in BDSup2Sub. IMO, that could be a valuable addition to BDSup2Sub, as currently, as far as I know, there is no subtitle editor or converter that is able to convert the subtitles to 3D, at least with the correct 3D offsets from the original BD. If you're interested, just let me know...
__________________
r0lZ PgcEdit homepage (hosted by VideoHelp) BD3D2MK3D A tool to convert 3D blu-rays to SBS, T&B or FS MKV Last edited by r0lZ; 18th July 2017 at 08:05. |
|
29th July 2017, 17:02 | #1368 | Link | |
Registered User
Join Date: Feb 2015
Posts: 43
|
Quote:
This does require to export to XML\PNG > merge forced events > export back to SUP. I have my own editor GUI but it uses BDSup2Sub 4.0.0 from the command line.
__________________
Blu-Ray Ripper 0.112c/0.21a |
|
20th September 2017, 18:12 | #1369 | Link | |
Registered User
Join Date: Feb 2015
Posts: 43
|
Quote:
java.lang.NullPointerException bdsup2sub.supstream.bd.Sup.BD.(Sup.BD.java:301) bdsup2sub.core.Core.readSup(Core.java:301) bdsup2sub.core.Core.run(Core.java:158) java.lang.Thread.run(Unknown Source) With 4.0.0, you will receive error: WARNING: missing PDS/ODS: last epoch is discarded
__________________
Blu-Ray Ripper 0.112c/0.21a |
|
2nd October 2017, 14:44 | #1370 | Link |
PgcEdit daemon
Join Date: Jul 2003
Posts: 7,469
|
As an additional evidence that there is really a bug with the way BDSup2Sub handles the frame rates and subtitle timings, have a look at this recent post in the BD3D2MK3D thread.
Users should NEVER have to wonder why their subtitles are not in sync any more after having processed them with BDSup2Sub (including with your version). The fact that they are not in sync except if the user does something obscure that he should NEVER be obliged to do is obviously the signature of a big bug. Please try to understand and fix that bug. It should be extremely easy to fix it, as it is sufficient to simply use the same output frame rate than the input. It's probably simply a single line of code to fix or add, and the nightmare of the out of sync streams produced by BDSup2Sub will be definitively a thing of the past. (Note that I don't need the fix to use BDSup2Sub with BD3D2MK3D. I have added the "convert from 23.976 fps to 23.976 fps" arguments to the command line used by BD3D2MK3D, and it's sufficient to obtain the correct output. But is it really normal to have to do it? And do you really want to have to explain to all users that have encountered the bug that they have to force a theoretically useless frame rate conversion to obtain the correct output?)
__________________
r0lZ PgcEdit homepage (hosted by VideoHelp) BD3D2MK3D A tool to convert 3D blu-rays to SBS, T&B or FS MKV Last edited by r0lZ; 2nd October 2017 at 14:50. |
7th October 2017, 17:46 | #1371 | Link | |
Registered User
Join Date: Feb 2015
Posts: 43
|
Quote:
__________________
Blu-Ray Ripper 0.112c/0.21a |
|
11th November 2017, 14:27 | #1372 | Link |
Registered User
Join Date: Mar 2016
Posts: 6
|
BDSup2Sub for image extraction...
Hello everybody! I have recently discovered BDSup2Sub512.jar , but my main usage is oddly for conversion from SUP and IDX/SUB to SRT for Asian languages (Korean, Japanese and Chinese)... Thanks to its support for XML/PNG , I am able to extract all the images from the subtitles in a decent form in order to process before OCR by ONeNote and Acrobat.
The image extraction is far better than Vobsub, XilisoftDVD Subtitle Ripper ... because each image focusses on the subtitles , not the whole screen. I do not use its XML. I further enhance the resulting images with Irfanview in order to OCR with One Note and Acrobat. Subtitle Edit is also used on the Sub/Sup to get a draft of the SRT with the timings ( and its rich conversion skills to other subtitle formats are very helpful), but its OCR capabilities are very limited . All that combined allows me to get a correct Srt , with some processing and a little proof-reading. But its great fun because of all the scripting involved. The essential part is the extraction of the png from the sub.sup to convert to text (thanks to the developpers!)...Quite the reverse of the initial philosophy of BDsuptosub I presume . Last edited by dngnt; 11th November 2017 at 14:30. |
28th December 2017, 13:03 | #1373 | Link |
PgcEdit daemon
Join Date: Jul 2003
Posts: 7,469
|
I've just encountered a palette problem with bdsup2sub. There are warning messages telling "fade detected. Patching palette." After the patch, sometimes the palette is totally wrong. For example, the white text appears correctly, but the transparent background is opaque black, and the outline is fully transparent. Or everything seems almost correct, but the background is not fully transparent.
The bug happens in the two java versions (the original and the enhanced), but the C++ version doesn't have that bug. (And, BTW, the C++ version doesn't have the sync bug discussed above either. Unfortunately, it has other bugs, so it's not really a good candidate to replace the java versions.) If someone wants to fix the bug, he can download original.sup here. Thanks in advance.
__________________
r0lZ PgcEdit homepage (hosted by VideoHelp) BD3D2MK3D A tool to convert 3D blu-rays to SBS, T&B or FS MKV Last edited by r0lZ; 28th December 2017 at 13:15. |
29th December 2017, 01:03 | #1375 | Link |
Registered User
Join Date: Feb 2015
Posts: 43
|
I guess it would depend on your needs.
I use 4.0.0 because all the other versions can't reliably give me the results I am looking for. I believe I gave reasons why in an earlier post.
__________________
Blu-Ray Ripper 0.112c/0.21a |
29th December 2017, 06:40 | #1376 | Link |
21 years and counting...
Join Date: Oct 2002
Location: Germany
Posts: 716
|
Okay. I will go back to the old 4.0.0 I guess.
Scorpius' version is no alternative to me: -It does not remember settings like output format, palette or filter. It always goes back to SUB/IDX, create new, bilinear upon start. -It has no keyboard shortcuts for the commands anymore. -It does not use the input file names folder by default for export. -It does not add an _exp to the filename like any other version does. |
29th December 2017, 11:49 | #1377 | Link |
PgcEdit daemon
Join Date: Jul 2003
Posts: 7,469
|
Where can I download v4.0.0 ? The link in the first post of this thread is dead, and I would like to compare it with the 3 current versions.
[EDIT] Never mind. I've found it with your Blu-Ray Ripper files, Bandit. Thanks.
__________________
r0lZ PgcEdit homepage (hosted by VideoHelp) BD3D2MK3D A tool to convert 3D blu-rays to SBS, T&B or FS MKV Last edited by r0lZ; 29th December 2017 at 12:14. |
29th December 2017, 14:49 | #1378 | Link |
PgcEdit daemon
Join Date: Jul 2003
Posts: 7,469
|
OK, I did some tests with various versions of BDSup2Sub. I have tested BDSup2Sub v4.0.0 (as far as I know, it's the latest version written by 0xDEADBEEF, still available in the files.zip here), v5.1.2 (the current "official" version), BDSup2SubEnhanced v0.0.9 (originally based on v5.0.0) and BDSup2Sub++ v1.0.2 (the only version that doesn't require Java). Unfortunately, none is bug free.
Here is the detail of the tests I did. Let's begin with the little bugs or discrepancies, not really harmful if you know what you are doing. 1. The irritating problem of the frame rate assumed wrongly is present in all Java versions, but the ++ version doesn't have that problem. Note that it's not really a bug, only a discrepancy. When you load a stream, the program detects correctly the source frame rate, but it sets 25 fps as the default output frame rate, for totally obscure reasons. That means that the time codes are rounded with the wrong output frame rate, and they are therefore not strictly identical than in the input stream, even if the user doesn't explicitly require a conversion. Furthermore, the wrong frame rate is written in the XML file if you convert to XML/PNG, and that can lead to completely wrong time codes and grave sync problems. Luckily, it is easy to avoid that bug simply by specifying that you WANT a conversion, and specifying the output frame rate equal to the input frame rate. It's a pity, but if you know that you have to do it, the workaround is easy. (That works with the GUI and the command line.) 2. Related to point 1 is the bug that prevents the user to store a different output frame rate by default. The output frame rate is always 25 fps in all Java versions, regardless of what you have used the last time and/or the usage of the "Store" button. That means that even if you use only, say, BD sources at 23.976, you have to pay attention to the output frame rate each time you load a stream. Pity, but again, it's an annoyance and not really a bug. Again, the ++ version does a better job. It doesn't store the output frame rate, but it uses by default the same frame rate than the input. Perfect. 3. Related to point 2 is the way the program store its settings. All versions store them in .ini files, but v4.0.0 and the Enhanced versions store them in the folder containing the executable. It's against the Microsoft rules, but you may accept that little problem. V5.1.2 and ++ store their ini respectively in the user's home and in APPDATA\Roaming, as they should. Now, the real bugs. 4. When a subtitle is included in a larger bitmap (therefore with more or less large transparent borders around them), all Java versions have problems with the colours or the transparency values of the different parts of the subtitles. For example, the background can be opaque instead of fully transparent, or the outline can be missing. This is the case of v4.0.0 and Enhanced. V5.1.2 outputs completely transparent frames ! Only the ++ version does the job perfectly. I guess that bug is caused by the method used to discover the colours and transparency levels of the different parts of the pictures. They check probably only some pixels near the border of the subtitle, and fail when there is no subtitle at that place. It's a very important bug, that occurs relatively frequently (especially with Asian BDs). It explains why some peoples have reported that some subtitles are missing when using a recent version. v4.0.0 and Enhanced give totally wrong results, but at least, they are visible. 5. The Enhanced version has been written to fix the bug of missing subtitles when several subtitles are displayed AT THE SAME TIME (technically: Multiple ODS). It's often the case with Japanimation (mangas) but that can happen with other movies as well, although it's relatively rare. Indeed, v4.0.0 and v5.1.2 have that problem, as well as the entire "official" branch of BDSup2Sub. And of course, the Enhanced version does it well. Strangely, the ++ version works also perfectly well ! It's an important bug, but unless you are a fan of mangas, you may not have noticed it. 6. When an XML/PNG stream is loaded in any version of BDSup2Sub, the fully transparent borders are cropped so that the picture occupies the smaller possible areas. (Of course, nothing changes when the subtitle touches the 4 borders.) Since the border is removed, the X, Y, width and height coordinates of the bitmap must be adjusted. All Java versions do that job correctly. The ++ version has its first bug here. The X coordinate is always wrong after a crop. For example, the subtitle is not centered on screen any more, and may appear slightly to the left, or completely near the left border of the video frame. Of course, it's a big bug, that happens only when loading XML/PNG streams containing subtitles in large canvas. It's a pity, as otherwise AFAIK ++ is the only bug free version. Unfortunately, the development of the ++ version has stopped, so the crop bug will probably remain for a long time. 7. The ++ version tries to detect when several subtitles are displayed at the same time in a BD SUP stream (Multiple ODS), just like the Enhanced Java version, and usually it does it well. When it converts the SUP stream to XML/PNG, it creates several PNG images for the same subtitle (instead of a single image combining all subtitles together). It is not clear if doing so is legal, but it is able to load the XML/PNG and convert it back to another format without problem. However, it has a big bug occurring only with some specific SUP streams (like the subtitles of Avatar 3D). It detects wrongly some additional subtitles that are in fact not present. When it encounters such false positives, it creates bizarre empty PNG images, and it references them in the XML badly. The result is that the XML/PNG stream cannot be reloaded in any version of BDSup2Sub. See this post for more info. 8. It's probably not a bug, but I notice that there are many warning messages displayed by all java versions, like for example: WARNING: multiple PDS/ODS definitions: result may be erratic WARNING: end time of frame 39 < start time -> fixed WARNING: fade out detected -> patched palette Strangely, the ++ version does NOT display these warnings. Is it because it deals with the potential problems correctly ? It's certainly the case of the multiple PDS/ODS definitions, but for the other warnings, I don't know. 9. With some BDs, it appears that BDSup2Sub++ is unable to merge the identical subtitles together. So, in that BDs, a single subtitle can be repeated several times, with no gap (or only a few ms) between the time codes. The resulting subtitle stream is therefore larger than the original one. The java version doesn't have that bug. Both versions have the CLI option -x <time> or --merge-time <time> to "Set maximum time difference for merging subtitles in ms", with the default value of 200 ms, but it seems that that option doesn't work well with ++ and some subtitle streams. 10. When BDSup2Sub++ loads and re-saves (without modification) a BD SUP file, it creates a new file larger than the original file. The overhead is usually around 10%. Even the new version, re-saved again, has again a small size increase. The origin of the problem is not known, but it seems that the stream is still correct and compatible with the decoders. The Java version doesn't have that problem. There might of course be other bugs that I'm not aware of, or very small bugs that are not really important like the little GUI bugs of v4.0.0. Note also that the ++ version doesn't have exactly the same command line parameters than the Java versions. And, about the command line, the 3 Java versions may require to launch Java with the obscure -Xmx256m command line parameter, as otherwise it may crash when processing a big subtitle file due to lack of memory. Anyway, with the 4 "problematic" streams I've tested so far, there is no version that works constantly as expected. I suggest therefore to use the ++ version if you don't need to convert from or to XML/PNG, and the Enhanced version otherwise. Anyway, don't forget to pay attention to the output frame rate (bug 1) with all Java versions. P.S. The bugs 4 and 6 can be reproduced with this sample. Bug 7 is clearly demonstrated with the subtitles of the Avatar 3DBD (not sure for the 2D version). If someone wants to check a specific stream or bug, send me a PM and I'll give you the demo stream.
__________________
r0lZ PgcEdit homepage (hosted by VideoHelp) BD3D2MK3D A tool to convert 3D blu-rays to SBS, T&B or FS MKV Last edited by r0lZ; 20th March 2019 at 15:27. Reason: Added ++ bug #10. |
29th December 2017, 17:52 | #1379 | Link | |
Registered User
Join Date: Mar 2009
Location: Germany
Posts: 5,769
|
Quote:
__________________
Born in the USB (not USA) |
|
29th December 2017, 18:12 | #1380 | Link |
Registered User
Join Date: Feb 2015
Posts: 43
|
Thanks for your testing r0lZ.
I use BDSup2Sub to extract .sup to .xml, merge 2 .xml files together, then create a new .sup, all from command line (I never use GUI). After your testing it would seem best to use ++ to extract and 4.0.0 to create new .sup? Everything is automated so using 2 versions would not be an issue. I just want the best possible results without missing subtitle events. If I could figure out how to extract the data myself I would write some code myself removing the need for BDSup2Sub but getting the png's out of a .sup does not make any sense to me.
__________________
Blu-Ray Ripper 0.112c/0.21a |
|
|