tsMuxeR Blu-ray output and Fixclpi

[jdobbs]

My first PowerDVD test with fixclpi 2.2 looks promising :) FF seems to be normal.

I'm going to burn a BD-RE and test on the Pioneer :cool:Great. Fingers are crossed.

[quantum]

Great. Fingers are crossed.

I just re-applied the new 2.2 (on a clean untreated source) and retested in PowerDVD, just to be sure ;-)

I noticed something: before applying fixclpi (using straight tsMuxer output), FF worked in PowerDVD, but REW never displayed any frames, and tended to max the CPU. After the new fixclpi, both FF and REW work great, and both show frames as you would expect, even up to 4x (didn't test any higher). I thought a little positive news would be appreciated :)

Now burning a BD-RE to test the Pioneer.

[jdobbs]

Definitely appreciated. If this works correctly I'm going to integrate the updates it into BD-RB.

[laserfan]

I have always used fixclpi with all my muxes, and am interested in 2.2 because I sometimes have chapter marks that fail to land properly (usually a bad one will land a few frames early, which can be very disconcerting). Using 2.1, I made a whole bunch of different tries, including with/without insertSEI, contSPS, and fps= options w/tsmuxer, and with versions 1.8.8 and then 1.8.4. With these tests it was clear that fixclpi made things much better ie. sometimes a chapter advance would not only land MANY SECONDS early, it would also show an incorrect timecode for the landing, i.e. the timecode would be for the landing point of the mark, but the wrong frame!

With all combos of tsMuxeR and its opts and fixclpi 2.1, I was still getting one mark that wasn't right (a frame or two early). Finally I tried 1.8.18 and fixclpi and it all now is perfect! :eek:

So IMO there's at least one problem with tsMuxeR 1.8.4/5 and 1.8.8 that 1.8.18 latest fixes, altho fixclpi is still needed of course.

I'll fiddle with 2.2 next but I therefore suggest jdobbs that you try 1.8.18 yourself.

P.S. with my players and x264 encodings as input to the muxes, it appears I don't need ANY OF tsMuxeR's fps=, insertSEI, or contSPS options!

Sorry that I have nothing to contribute wrt FF/REW or compatibility--these muxes always work on my BH200 player.

[quantum]

Tested a shortened tsMuxer 1.8.4 Blu-ray mux after applying fixclpi 2.2 on my Pioneer standalone. Everything looks perfect! I'm going to test a full length disk from another source where I know exactly where the chapters are, and I remember distinctly how slow chapter advances were before fixclpi. Of course I'll also double check FF/REW, but I'm thinking we have a winner here.

Very much appreciated jdobbs!

[nwg]

Will the current Fixclpi gui work ok with the new version?

[anode]

Hello jdobbs and the others,

I'm glad that you found some issues according to my first post.
Thank you for reacting so fast.
I tried to fix it for myself but i have not much programming skills and so my own tests take always some time.
For me (i have a Samsung BD-P2500 standalone) tests with the fixed clpi-files did improve ff/rw: now the picture displayed while searching is not longer divided in some parts, but a complete frame is shown. This is nothing very important, since chapter skipping did work with the older, fixed clpi.
Sometimes after chapter skip there are audio/video resync issues. This may have to do with the chapter point not being placed exactly on a I-Frame or (as i use hd-broadcasts) the streams have longer GOPs than within blu-ray specs. Will have to do some tests....

For anybody interested in clpi-file format i have found 2 patents describing the binary structure:
EP 1873780 and EP 1715686 (sorry, you have to google for them. Get the pdf with the pictures...)

Another issue with the clpi's from tsMuxeR is that the "NumberOfSourcePackets" in the ClipInfo-Section is wrong. This should be the number of 192-byte Packets in the corresponding m2ts-stream.
I have found two tools which fixes this, one "AVCHDme 1.4" and another "ClipInf Editor v0.01b". The second one calculates this number sometimes wrong by one packet?
Perhaps we can correct all this little tsMuxeR-bugs, so that even the Panasonics should accept the clpi's. (Hard to understand that they play with the obvious wrong tables!)

[laserfan]

Hey anode great to have you back, awesome first & second posts!!! ;)

I can vouch for audio sync issues following a chapter/I-frame mismatch, but even if this is the case the audio syncs-up again probably at the next GOP.

Welcome to doom9! :)

[quantum]

I did another test, this time using a different source, and with tsMuxer 1.8.18b. Everything is perfect in PowerDVD and my Pioneer standalone. FF/REW works fine, and chapters are fast and accurate.

Now we just need confirmation from a Panasonic owner.


Another issue with the clpi's from tsMuxeR is that the "NumberOfSourcePackets" in the ClipInfo-Section is wrong. This should be the number of 192-byte Packets in the corresponding m2ts-stream..
...Perhaps we can correct all this little tsMuxeR-bugs, so that even the Panasonics should accept the clpi's. (Hard to understand that they play with the obvious wrong tables!)
Thank you for your excellent observations anode. Hopefully jdobbs will turn fixclpi into a complete tsMuxer fixer!

I do notice that Clipinf Editor 0.02b reports the clipinf packets are not sized correctly.

[jdobbs]

Will the current Fixclpi gui work ok with the new version? What kind of GUI do you want? I can make one very easily as a part of it.

[jdobbs]

Hello jdobbs and the others,

I'm glad that you found some issues according to my first post.
Thank you for reacting so fast.
I tried to fix it for myself but i have not much programming skills and so my own tests take always some time.
For me (i have a Samsung BD-P2500 standalone) tests with the fixed clpi-files did improve ff/rw: now the picture displayed while searching is not longer divided in some parts, but a complete frame is shown. This is nothing very important, since chapter skipping did work with the older, fixed clpi.
Sometimes after chapter skip there are audio/video resync issues. This may have to do with the chapter point not being placed exactly on a I-Frame or (as i use hd-broadcasts) the streams have longer GOPs than within blu-ray specs. Will have to do some tests....

For anybody interested in clpi-file format i have found 2 patents describing the binary structure:
EP 1873780 and EP 1715686 (sorry, you have to google for them. Get the pdf with the pictures...)

Another issue with the clpi's from tsMuxeR is that the "NumberOfSourcePackets" in the ClipInfo-Section is wrong. This should be the number of 192-byte Packets in the corresponding m2ts-stream.
I have found two tools which fixes this, one "AVCHDme 1.4" and another "ClipInf Editor v0.01b". The second one calculates this number sometimes wrong by one packet?
Perhaps we can correct all this little tsMuxeR-bugs, so that even the Panasonics should accept the clpi's. (Hard to understand that they play with the obvious wrong tables!) I made a lot of streams a while back that had long GOPs -- I can confirm that when you use them you will get video delays at chapter points. For Blu-ray compatibility you need to make sure the GOPs are no more than one second long. In BD-RB I set them to 24 as the default. If you stick to that rule the chapters should sync up immediately.

I forgot about the number of packets bug in TSMUXER. I'd fixed it in BD-RB but not in FIXCLPI. I'll put another version up shortly that fixes that too (as long as FIXCLPI runs in folder mode and the BDMV\STREAM folder can be found).

[nwg]

What kind of GUI do you want? I can make one very easily as a part of it.

There has been one available for a while now from here somewhere done by someone else. It just allows the user to select the files/folders and process them. I tried it with 2.2 and it works fine.

I am trying it in a minute on a ripbot avchd (BDMV folder on a DVD). When I play it them in a Sony S350. The picture freezes when trying to ff/rwd. Skip chapters work but there is no sound for a few seconds and then it plays normally. I have been blaming the player as the same disc works perfectly in a Samsung 1500 player.

[jdobbs]

Hello jdobbs and the others,

I'm glad that you found some issues according to my first post.
Thank you for reacting so fast.
I tried to fix it for myself but i have not much programming skills and so my own tests take always some time.
For me (i have a Samsung BD-P2500 standalone) tests with the fixed clpi-files did improve ff/rw: now the picture displayed while searching is not longer divided in some parts, but a complete frame is shown. This is nothing very important, since chapter skipping did work with the older, fixed clpi.
Sometimes after chapter skip there are audio/video resync issues. This may have to do with the chapter point not being placed exactly on a I-Frame or (as i use hd-broadcasts) the streams have longer GOPs than within blu-ray specs. Will have to do some tests....

For anybody interested in clpi-file format i have found 2 patents describing the binary structure:
EP 1873780 and EP 1715686 (sorry, you have to google for them. Get the pdf with the pictures...)

Another issue with the clpi's from tsMuxeR is that the "NumberOfSourcePackets" in the ClipInfo-Section is wrong. This should be the number of 192-byte Packets in the corresponding m2ts-stream.
I have found two tools which fixes this, one "AVCHDme 1.4" and another "ClipInf Editor v0.01b". The second one calculates this number sometimes wrong by one packet?
Perhaps we can correct all this little tsMuxeR-bugs, so that even the Panasonics should accept the clpi's. (Hard to understand that they play with the obvious wrong tables!) I did a lot of file dumps and analysis to find those table formats... it sure would have been nice to find docs a month or two ago :)

[nwg]

I think the new version has improved the ripbot files. Both the Sony S350/S550 doesn't have great navigation with discs. Even at full speed it is pretty slow going through a film but it jumps from one bit to another as it freezes periodically on frame while the counter does the same thing. It can be quite hard to find certain bits sometimes. The new Fixclpi has managed to make the navigation a little smoother.

I am going to compare a TsMuxed BD that has the first fixclpi done to it and then redo it with the 2.2 version.

[rack04]

I made a lot of streams a while back that had long GOPs -- I can confirm that when you use them you will get video delays at chapter points. For Blu-ray compatibility you need to make sure the GOPs are no more than one second long. In BD-RB I set them to 24 as the default. If you stick to that rule the chapters should sync up immediately.

Are you referring to --keyint 24?

[jdobbs]

Yes. And, of course, you have to also use "--min-keyint 1" along with it.

[jdobbs]

And here is one more release (http://www.jdobbs.net/freeware/fixclpi_v23.zip) (v2.30) of FixCLPI. In this one if you pass it a folder as the parameter, it will also automatically fix the packet_count variable (the one written by TSMUXER is often if not always wrong). Of course it will only correct it if the CLPI is in a standard BD format (CLPI is in either the BACKUP/CLIPINF or the CLIPINF folder, and the M2TS is in the STREAM folder). The program is verbose, so if it gets changed, you'll know it.

[quantum]

And here is one more release (http://www.jdobbs.net/freeware/fixclpi_v23.zip) (v2.30) of FixCLPI. In this one if you pass it a folder as the parameter, it will also automatically fix the packet_count variable (the one written by TSMUXER is often if not always wrong). Of course it will only correct it if the CLPI is in a standard BD format (CLPI is in either the BACKUP/CLIPINF or the CLIPINF folder, and the M2TS is in the STREAM folder). The program is verbose, so if it gets changed, you'll know it.
Awesome work! I double checked the math, based on anode's comments, and it looks like you have it right. Clipinf Editor reports it wrong in my test, off by one packet as anode said.

[turbojet]

fixclpi 2.30 worked great on Panasonic BD30, ff, rw, chapter skips work like retail BD's which is a lot better then no fixclpi.
previous fixclpi broke playback in this player.

[MadMonkey57]

Pana BD35 latest fw + fixclpi 2.3: chapter seeking as good as without fixclpi, FF/RW seems a little "smoother" than without fixclpi.
Same as the BD30 regarding previous version of fixclpi.

[jdobbs]

Looks like we're good to go then.

I'm removing all previous versions of FixCLPI from my site. So v2.30 should be the one to use.

Thanks to all for testing and to anode for his very observant and helpful report. :)

[turbojet]

Your welcome and thanks for the fix jdobbs and for reporting the issue anode.

[MadMonkey57]

Well thank YOU jdobbs and anode.

[Elesias]

** Edited **

[laserfan]

Looks like we're good to go then.

I'm removing all previous versions of FixCLPI from my site. So v2.30 should be the one to use.

Thanks to all for testing and to anode for his very observant and helpful report. :)It appears "fixclpi" is built-in to BD-RB and not an external Tool, so can we expect you will update that shortly? It seems the new version does not work "over" BD-RB output as it stands right now. Thanks jdobbs for all the energy you put-in to this the last couple days!

[jdobbs]

It appears "fixclpi" is built-in to BD-RB and not an external Tool, so can we expect you will update that shortly? It seems the new version does not work "over" BD-RB output as it stands right now. Thanks jdobbs for all the energy you put-in to this the last couple days! Yes. You should see a new BD-RB later today that includes (internally) the updates included in FixCLPI.

[MB2]

Hi all... i have done quite a few encodes with BD-RB, and yes they dont work on the Panasonic BD35 (or the 55)

Is there anyway I can copy them back to my pc and correct them in anyway without reencoding them again? And how do i do it??

Many Thanks!

[jdobbs]

Hmmm... I'll update FixCLPI.EXE to recognize that condition and rewrite the CLPI files. I have quite a few that, even though they work for me, need to be corrected. I like things to be straight on my backups. Luckily I keep an ISO for almost all my backups on a harddrive.

[EDIT] Ok. I stand corrected. As long as they weren't done by one of the versions from the past couple of days, you can run FIXCLPI v2.30 against them and it should fix them. :)

I just did it on a couple of mine. So, no need for a new version.

Example (for APOCALYPTO):

1. Create a folder called c:\APOCALYPTO
2. Copy the root folders (BDMV and CERTIFICATE) to the new APOCALYPTO folder.
3. run "c:\path\to\fixclpi.exe" c:\APOCALYPTO
4. you'll see messages for CLPI files that are corrected
5. Reburn or rewrite to UDF 2.5 ISO or disc.

[EDIT AGAIN] Not positive if this will work for the Panasonic on previously "fixed" files, waiting for feedback.

[MB2]

EDIT!!! YOU STAR!!! Thank you will try in the morning!





Thanks for that - i have about 30 i might need to redo... eek! Just donated aswell... i encourage others to also :)
LMK when a simpleton like me can redo em all LOL

[MB2]

I tell you what ive done

Ive ripped everything using TSremux 1.8.8 movie only... stored on hd.
Then gone to mainly the v.1.9.01 of rebuilder and done quite a few...

Excuse my igorance, what do i then do? Copy the BDMV folders etc to pc and run FixCLPI.EXE

I double click on it and im not sure whats its doing...

Ive also started your new version of BDRB on 2 films - these should play ok now on the BD35/55 if im correct??

[jdobbs]

EDIT!!! YOU STAR!!! Thank you will try in the morning!





Thanks for that - i have about 30 i might need to redo... eek! Just donated aswell... i encourage others to also :)
LMK when a simpleton like me can redo em all LOLTry it once and let me know if it works on the Panasonic... I just remembered there was one change that may not make it through if the source had been "fixed" before -- but I'm not sure if it matters...

Please let me know when you find out for sure, ok?

[jdobbs]

I tell you what ive done

Ive ripped everything using TSremux 1.8.8 movie only... stored on hd.
Then gone to mainly the v.1.9.01 of rebuilder and done quite a few...

Excuse my igorance, what do i then do? Copy the BDMV folders etc to pc and run FixCLPI.EXE

I double click on it and im not sure whats its doing...

Ive also started your new version of BDRB on 2 films - these should play ok now on the BD35/55 if im correct??Run CMD.EXE and then type in the lines from the command window. Just double clicking isn't going to do anything, it is a console command.

[~bT~]

I tell you what ive done

Ive ripped everything using TSremux 1.8.8 movie only... stored on hd.
Then gone to mainly the v.1.9.01 of rebuilder and done quite a few...

Excuse my igorance, what do i then do? Copy the BDMV folders etc to pc and run FixCLPI.EXE

I double click on it and im not sure whats its doing...

Ive also started your new version of BDRB on 2 films - these should play ok now on the BD35/55 if im correct??
try the gui if u dont know cmd.

http://forum.doom9.org/showpost.php?p=1207707&postcount=2196

[jdobbs]

Can you select a directory with the GUI?

[MB2]

Ive seemed to have got it to work, i will send em to a mate today, and should know tomorrow if they worked, thanks ;-)

[~bT~]

Can you select a directory with the GUI?

yes u can.

edit: i guess u can't. i was thinking of the CLIPINF folder.

[BZeeme]

yes u can.

If I select the BDMV folder, the GUI says something like it can't find any files in that folder. I guess you have to go to each CLIPINF folder (or use CLI)

[turbojet]

With the gui even after choosing the clipinf directories I notice the packet header doesn't get checked/fixed.

It would be really nice to have a simple gui with a browse for BDMV directory or something in a future version of fixclpi all in one little exe, no need to hunt for other downloads.

[jdobbs]

With the gui even after choosing the clipinf directories I notice the packet header doesn't get checked/fixed.

It would be really nice to have a simple gui with a browse for BDMV directory or something in a future version of fixclpi all in one little exe, no need to hunt for other downloads.That's because you have to select a directory (not a file) in order to get the sizing fixed.

I'll compile a GUI version. I just wanted to make a command line version in order to keep it simple. It was never meant to become a full-up project... only a quick fix until TSMUXER is fixed. But I guess it isn't a priority with the developers.

[turbojet]

Possible to just add a gui while keeping cli?

Also I noticed file version is 2.1.0.0 in current exe.

[jdobbs]

Possible to just add a gui while keeping cli?

Also I noticed file version is 2.1.0.0 in current exe. I probably forgot to update it. It should say "v2.30" when you run it, though.

[G_M_C]

That's because you have to select a directory (not a file) in order to get the sizing fixed.

I'll compile a GUI version. I just wanted to make a command line version in order to keep it simple. It was never meant to become a full-up project... only a quick fix until TSMUXER is fixed. But I guess it isn't a priority with the developers.

Is fixCLPI still needed, even in version 1.8.19 of tsMuxeR ?

(http://forum.doom9.org/showthread.php?p=1256299#post1256299)

[jdobbs]

I don't know. I'll run a mux with .19 and see...

[G_M_C]

I don't know. I'll run a mux with .19 and see...

YEah, hopefully it is fixed now :) But at least the TrueHD problems seems to have been fixed !

Speaking of fixed problems: Thanx Jdobbs for fixing the problems we saw with fixCLPI and the Panny's BD30/BD35 :)

[jdobbs]

Yep, still needed. The packet_size parameter was set correctly on the one I just tested, so apparently that was fixed, but the ep tables (COARSE/FINE) are still wrong.

[mouw]

new FixClip v2.3 seems smoother w/ PowerDVD v7.3

however on my Sony BDP-S350 maybe a little FASTER on Chapter jumps
but Sound still a couple seconds behind video at jump
and FF/RW really doesn't work

FixClipGUI works just find in Vista
just copy FixClip v2.3 (replace old ver) into directory w/FixClipGUI
and use a ShortCut to run program...

i only FIX the Clipfile in BDMV\CLIPINFO
never bother with BDMV\BACKUP\CLIPINFO
any1 think this is a problem??

[Duppie]

jdobbs

Does your fixclpi work on AVCHD format for PS3. I have noticed you have mentioned only Blu-Ray structure?

Thanks

[deank]

Most of the time I'm getting 2 error messages


D:\multiAVCHD>"c:Users\Dean Kasabow\Desktop\multiAVCHD\tools\fixclpi.exe" AVCHD_testpip

FixCLPI v2.30, jdobbs softworks

Fixing CLPI files in directory tree.
- AVCHD_testpip\BDMV\BACKUP\CLIPINF\00000.clpi ep tables corrected.
- AVCHD_testpip\BDMV\BACKUP\CLIPINF\00001.clpi ok.
Target does not appear to be a CLPI file.
- AVCHD_testpip\BDMV\BACKUP\CLIPINF\01300.clpi ok.

After 01300.clpi I get runtime error 5 "File already open" and I get the same error with all files with names above 01000.clpi. (my menu files) and the files are not open in any other application.

[mrr19121970]

I got a Run-time error '6': Overflow

[mrr19121970]

With the gui even after choosing the clipinf directories I notice the packet header doesn't get checked/fixed.

It would be really nice to have a simple gui with a browse for BDMV directory or something in a future version of fixclpi all in one little exe, no need to hunt for other downloads.


Try this...

fixCLPI GUI v0.02b.exe (http://clownbd.techxt.com/Downloads/fixCLPI GUI v0.02b.exe)

Includes v2.31