Does the chapter file info generated by DJATOM's tool match what you are looking for? Here is an example of its output
That is a txt type of chapters and it's ok. It can be xml too. Currently I am using eac3to to extract from BD and MKVExtract for MKV containers (which DGIndexNV already deal with).
Help me out, guys, I'm confused. I ran DJATOM's tool on the Alien 1 rip and it generated a whole bunch of EPxx.txt files, one of which looks like this:
The name fields are blank because this is to be filled in when merging with a file (non BD), i.e. MKV
They tend not to have names in a BluRay movie that I have noticed
Merged together with video, audio, etc for file playback like MKV.
Some people name the chapters for better seeking I guess
Why does it think it is a bunch of episodes?
I don't know, authoring issues maybe
Just read the usage info for DJAtom's tool'
Since Alien is a seemless branching movie it thinks that every m2ts is a separate episode and the mpls is a sort of playall playlist
Just read the usage info for DJAtom's tool'
Since Alien is a seemless branching movie it thinks that every m2ts is a separate episode and the mpls is a sort of playall playlist
OK, thank you for the explanation. But then the tool should be smart enough to know that and operate accordingly.
Help me out, guys, I'm confused. I ran DJATOM's tool on the Alien 1 rip and it generated a whole bunch of EPxx.txt file
Use eac3to with a GUI. One file only will be generated.
The chapters.txt or .xml is then fed to MKVToolnix GUI to replicate same chapter structure in muxed output mkv (of course this is useful when you convert a BD to x264/x265 plus multiple audio and srt). You just need to drag and drop like other files in the upper blank window space and it will be recognized as such.
Yeah, my script tuned for my usecase (anime blurays with 2-3 episodes per volume), and I rarely make anime movies, so I didn't run on that scenario (seemless branching, etc). If eac3to produces desired output, indeed it's better to use that approach.
I have DGIndexNV extracting chapters now that match EAC3TO for Guest 2's Aliens rip. In order not to complicate the UI, a chapters file is automatically created when an MPLS is opened.
Before giving a test version, I want to ask DJATOM if he can provide or refer me to a bluray that has multiple episodes such that his parser is applicable. I can then ensure that it will also be supported.
Hats off to Jarrett Vance, whose Chapter Grabber code showed how to do it.
Thanks to DJATOM for providing a Japanese-style rip suitable for his parsing tool.
I slipstreamed a first step supporting normal chapters as output by EAC3TO. I hope to support DJATOM's case in a future version. It will require UI changes, whereas this first step does not.
I have DGIndexNV extracting chapters now that match EAC3TO for Guest 2's Aliens rip. In order not to complicate the UI, a chapters file is automatically created when an MPLS is opened.
Thanks @admin!
Don't you think it's better to save chapters when saving DGI? We could give path and save only when interested and not anytime you open a mpls.
It might be better but I don't think it's worth the effort. I already parse the MPLS on open, so that's a fine time to write the chapters file. Maybe it will change when I implement DJATOM's use case.
After some thought I decided to generate it as Guest 2 suggested, i.e., when the project is saved. The chapters file is generated in the same directory as the DGI file. This will be in the next slipstream.
The main reason is that (I think) when a bluray is decrypted with anydvd the playlist directory is not writable, so the chapter file generation would fail.