ClownBD in Windows 10

[Nu©leus]

Hi folks,

Been quite a few months since I ripped a BD, I always used Clown BD then BD Rebuilder with no problems. However, I'm now running Win 10 and it seems there's some component of Clown BD that doesn't like Win 10. I tried two retail BD’s, A Most Violent Year and Forrest Gump and everything goes well in Clown BD until the actual ripping to HD stage, when the eac3to progress bar at top of screen seems to freeze at around 4%-7%.

I saw a post in the Clown BD thread at Slysoft saying it was still good but to update eac3to, which I did but no difference. Is this a known problem on Win 10, if so is there a workaround?

I eventually ripped to HD with CloneBD (no compression) but don’t like it, after processing through BD Rebuilder I had an OOS movie, never had that with any of the discs I ripped with Clown BD. If no workaround for Win 10 what else is good for ripping the disc to HD? TIA.

Edit: Sorry, can a mod fix thread title please - ClownBD

Edit 2: Fixed - Thanks @ johns0

[johns0]

You can fix your own thread title,go to edit/go advanced.As to your issue did you try and set clownbd to use windows 7 compatibility?

[Nu©leus]

You can fix your own thread title,go to edit/go advanced.As to your issue did you try and set clownbd to use windows 7 compatibility?

Yes, tried ClownBD in compatibility modes. Selecting mpls and selecting streams is fine, the problem arises at eac3to 3rd Pass.

Specifically it comes to a halt at...

eac3to 3rd Pass:h.sup"... process: 5%

Something to do with BDSup2Sub? Java is intsalled.

Was fine in Win8/8.1 just gone skewiff in Win 10.

[johns0]

Try makemkv.

[_Al_]

3rd pass should be demuxing process in ClownBD term ,..., so it gets halted while demuxing streams, so java should not be in use yet ...

[gonca]

Why do you need to use ClownBD before using BD_RB

[Nu©leus]

Why do you need to use ClownBD before using BD_RB

Because if/when I rip a BD I do main movie only, so rip just that and its relevant English audio/subtitle streams to HD before compressing to BD25 through BD Rebuilder. What is the other option, to rip the whole disc to HD before doing main movie only through BD Rebuilder? If so that would seem a bit of a long way round to get main movie onto HD.

Edit: Just did Forrest Gump by ripping the whole disc to HD with AnyDVDHD, then main movie only through BD Rebuilder.

Also, having just read posts by the ClownBD author on the Slysoft forum saying it's over five years old (I didn't know that), and that he has no plans to change it. I guess it's time to learn another method of ripping BD to HD (AnyDVDHD will do). He also mentions that most now use Slyce (CloneBD isn't it)?

Thanks to those who gave help. Cheers.

[HemLok]

Why do you need to use ClownBD before using BD_RB

This is a somewhat old thread but...

Clown_BD can be extremely useful in situations where there are problems with seamless branching and audio problems. Some standalone players tend to choke with the branching and TrueHD. The Oppo BDP-93 is an example of one such player. Do a web search for "seamless branching audio problems". If you use Clown_BD the output is a single m2ts file which removes the complexity and the issue goes away. Clown_BD existed before this problem ever came into existence but it's still useful as a workaround and, frankly, just useful to remove junk from what's important.

With respect to Clown_BD working or not working under Windows 10 it's working just fine on my Windows 10 Pro x64 system.

[gonca]

Why do you need to use ClownBD before using BD_RB

This is a somewhat old thread but...

Clown_BD can be extremely useful in situations where there are problems with seamless branching and audio problems. Some standalone players tend to choke with the branching and TrueHD. The Oppo BDP-93 is an example of one such player. Do a web search for "seamless branching audio problems". If you use Clown_BD the output is a single m2ts file which removes the complexity and the issue goes away. Clown_BD existed before this problem ever came into existence but it's still useful as a workaround and, frankly, just useful to remove junk from what's important.

With respect to Clown_BD working or not working under Windows 10 it's working just fine on my Windows 10 Pro x64 system.

I know what Clown_BD does
BD_RB handles seamless branching just fine

[HemLok]

I know what Clown_BD does
BD_RB handles seamless branching just fine

Hrm. Thanks for the corrrection. For some reason I didn't recall that BD Rebuilder would output to a single m2ts file, as well. I guess for movie-only it does. Apparently I haven't paid too much attention in awhile. I'll have to remember this. Regardless, both programs accomplish the same goals with respect to movie-only output if compression isn't required. Ease-of-use is debatable for some. I think both are interchangeably easy to use. BD Rebuider is updated more but also has more capabilities.

And most importantly given this thread topic they both work under Windows 10.

[fritzi93]

Once in a great while, BDRB (and Ripbot for that matter) will have trouble correctly joining the m2ts files. I'm thinking of the last Harry Potter movie and Ender's Game.

Clown_BD, OTOH, has never gotten it wrong in my experience. And at the beginning of the process you're presented with the playlists, longest listed first. So you're less likely to choose the wrong playlist when there are alternate versions.

Not a very big deal, but that's why I like to use Clown_BD to extract main movie from disc (DVDFabPasskey running in background).

[Nu©leus]

With respect to Clown_BD working or not working under Windows 10 it's working just fine on my Windows 10 Pro x64 system.

And most importantly given this thread topic they both work under Windows 10.

Thread topic is correct as far as I'm concerned. I'm surprised to learn you say ClownBD works fine under Win 10.

Win 10 Pro x64 here (up to date TH2) with Java installed. Problems with ClownBD, exactly as outlined in previous posts (above) persist, same on a clean install of Win 10.

eac3to 3rd Pass always freezes at 4-7%

[Kerry56]

Windows 10 64bit Pro here. No issues with ClownBD for me. I use it infrequently, but it is a handy tool to have.

[HemLok]

I recently did a clean install of Windows 10 Pro Threshold 2 x64 with Java 8 update 66 installed both x86 and x64. I've been using Java 8 for quite some time now but never had issues using Java 7. I did a straight copy and paste of my Clown_BD program folder from Windows 8.1 Pro x64 to Windows 10. I updated eac3to, Mencoder, and tsMuxer to newer versions some time ago. My Mencoder install is most likely behind the current now but newer than came with Clown_BD 0.81. eac3to is v3.31 and tsMuxer is v2.6.12 which are the latest. No issues on my system.

You note that the percentage stops. Is it actually halting? Have you used Task Manager or a similar program to see if resources are still being used? Have you tried simply waiting to see if it completes? I haven't sat and watched Clown_BD run to completion but it's always possible that something related to Windows 10 is causing the usual visible notifications for Clown_BD to not all appear properly.

[Nu©leus]

Have you used Task Manager or a similar program to see if resources are still being used? Have you tried simply waiting to see if it completes? I haven't sat and watched Clown_BD run to completion but it's always possible that something related to Windows 10 is causing the usual visible notifications for Clown_BD to not all appear properly.

@Hemlok - Thanks so much for your posts friend, nice one. Don't I feel like an idiot!

Just ripped The Bourne Ultimatum to my HD, main movie, audio and subs streams I wanted. Again the ClownBD progress indicator (top of screen) was stuck at "eac2to 3rd Pass:h.sup"... process:5%" but I followed your advice and opened Task Manager, audio conversion tool process was working (eac3to) so I left it and sure enough heard the audible alert that plays when the tsMuxer stage of the process starts. Strangely enough the ClownBD progress indicator is displaying the tsMuxer process increasing correctly.

I also updated as you mentioned. tsMuxeR v2.6.12 - eac3to v3.31 and Mencoder 37569 (v1.2.0.0).

Thanks a mil for your posts friend, appreciated.

[HemLok]

@Hemlok - Thanks so much for your posts friend, nice one. Don't I feel like an idiot!

Just ripped The Bourne Ultimatum to my HD, main movie, audio and subs streams I wanted. Again the ClownBD progress indicator (top of screen) was stuck at "eac2to 3rd Pass:h.sup"... process:5%" but I followed your advice and opened Task Manager, audio conversion tool process was working (eac3to) so I left it and sure enough heard the audible alert that plays when the tsMuxer stage of the process starts. Strangely enough the ClownBD progress indicator is displaying the tsMuxer process increasing correctly.

I also updated as you mentioned. tsMuxeR v2.6.12 - eac3to v3.31 and Mencoder 37569 (v1.2.0.0).

Thanks a mil for your posts friend, appreciated.

Good to hear that things are working albeit not quite as they used to - and as were intended - under earlier versions of Windows. Glad I could help.

[wyliec2]

Resurrecting this - I was using AnyDVD + Clown_BD + Imgburn to rip Blurays to files, remove unwanted materials and then recreate the image to store on my media server. In many cases file sizes were reduced 30-50%. One Windows 8.1 (64-bit Home) Clown_BD would run and then start Imgburn to complete the process.

Since upgrading to Windows 10 (Home) Clown_BD does not start Imgburn. Clown_BD finishes and stops. When I run Imgburn manually and process the Clown_BD txmuxer output to create the image I am not getting the size reduction.

I'm not sure why the Clown_BD --> Imgburn process won't run as it did on Windows 8.1 or why I've lost the file size reduction. For example on Win 8.1 I processed Zombieland - original ISO was 38Gb and Clown_BD --> Imgburn reduced it to 20Gb. Using the manual steps now on Win 10 it winds up being the original 38Gb.

I must confess to having limited knowledge about all of the details (eac3to, tsmuxer, etc) of the overall process. I was able to get great results on Win 8.1 and am now stuck trying to figure what is broken on my Win 10 install... Any suggestions would be greatly appreciated!! TIA

[HemLok]

Resurrecting this - I was using AnyDVD + Clown_BD + Imgburn to rip Blurays to files, remove unwanted materials and then recreate the image to store on my media server. In many cases file sizes were reduced 30-50%. One Windows 8.1 (64-bit Home) Clown_BD would run and then start Imgburn to complete the process.

Since upgrading to Windows 10 (Home) Clown_BD does not start Imgburn. Clown_BD finishes and stops. When I run Imgburn manually and process the Clown_BD txmuxer output to create the image I am not getting the size reduction.

I'm not sure why the Clown_BD --> Imgburn process won't run as it did on Windows 8.1 or why I've lost the file size reduction. For example on Win 8.1 I processed Zombieland - original ISO was 38Gb and Clown_BD --> Imgburn reduced it to 20Gb. Using the manual steps now on Win 10 it winds up being the original 38Gb.

I must confess to having limited knowledge about all of the details (eac3to, tsmuxer, etc) of the overall process. I was able to get great results on Win 8.1 and am now stuck trying to figure what is broken on my Win 10 install... Any suggestions would be greatly appreciated!! TIA

Letting Clown_BD run and then manually burning with ImgBurn should result in absolutely zero difference in the size of the output versus having Clown_BD run and having it automatically open ImgBurn and having it burn the processed output. It makes absolutely no sense to me why there would be any difference and I know for fact that processing does remove content properly under Windows 10 when manually burning via ImgBurn because that's how I do it. When you process with Clown_BD and remove the unwanted fluff then POOF it's gone from the resulting output. It't can't just re-appear on its own. Are you absolutely sure you aren't accidentally picking the wrong folder when you manually go to burn the output using ImgBurn? Please don't take question wrong but that's the only way I can see the size ballooning back to its original size.

The reasoning behind Clown_BD not being able to automatically launch ImgBurn may be a change to Windows 10 that just doesn't make it possible or some difference in configuration. I can't say. I'll try doing it myself when I have some time but I can't do it right now.

On a side note, I never let projects complete and then automatically burn so I've never had Clown_BD do this regardless of OS. Same goes with BD Rebuilder, CloneBD, etc. I process to an output folder and let a number of completed projects pile up and then do burning in batches when I have the fre time and I'm not using my computer for other things. I like more control over my projects and I do a lot of multi-tasking. I don't like doing a lot of burning when I'm doing a lot of other things on my system.

[HemLok]

I did a test with Clown_BD set to create an ISO image via ImgBurn after processing while I was away from the computer for awhile. ImgBurn never opened. So, it appears to be breakage due to some sort of change in Windows 10.

[_Al_]

I do not burn with imgBurn, but,
Clown_BD can create *.BAT in Clown_BD directory if you check "batch" box at the end of user selection process - step3 window, so you can just create that batch script , Clown_BD would not run. You can run that Batch script manually afterwards. So before running it just check that script or pause it before burning (including pause line) and experiment with that line or just enter that line yourself in cmd prompt, whatever, look at it closely why it does not work under win10. Or perhaps that batch script would work then as oppose to not creating it, for whatever reason.

[wyliec2]

I just rebuilt an old PC on Win 7 and Clown_BD + Imgburn worked perfectly and created the 20Gb ISO output file.

I then redid everything on my Win 10 PC, recreating the folders, etc. so that I could use the same Clown_BD settings without any change. And it did not launch Imgburn.

Here is the tsmuxer log from Win 7:

Command Line="C:\Users\Downloads\ClownBD\Clown_BD_v0.81\tsMuxeR\tsMuxeR.exe" "C:\Users\Downloads\ClownBD\eac3to_TEMP\eac3to_TEM P.meta" "C:\Users\Downloads\ClownBD\txMuxeR_Out\eac3to_TEM P"

SmartLabs tsMuxeR. Version 1.10.6 http://www.smlabs.net
Decoding H264 stream (track 1): Profile: High@4.1 Resolution: 1920:1080p Frame
H.264 muxing fps not set. Get fps from stream.
H.264 stream does not contain fps field. Muxing fps=23.976
0.0% complete
Decoding DTS-HD stream (track 2): Bitrate: 1536Kbps core + MLP data.Sample Rate
: 48KHz Channels: 5.1 (DTS Master Audio)
Decoding PGS stream (track 3): Resolution: 1920:1080 Frame rate: 23.976
Decoding PGS stream (track 4): Resolution: 1920:1080 Frame rate: 23.976
99.9% complete
Processed 126168 video frames
100.0% complete
Creation of Blu-ray playlist
Creation of Blu-ray stream info and seek index
Mux successful complete.
Muxing time: 2 min 31 sec

Here is the Win 10 tsmuxer log (the command line is missing from it):

SmartLabs tsMuxeR. Version 1.10.6 http://www.smlabs.net
Decoding H264 stream (track 1): Profile: High@4.1 Resolution: 1920:1080p Frame rate: 23.976
H.264 muxing fps not set. Get fps from stream.
H.264 stream does not contain fps field. Muxing fps=23.976
0.0% complete
Decoding DTS-HD stream (track 2): Bitrate: 1536Kbps core + MLP data.Sample Rate: 48KHz Channels: 5.1 (DTS Master Audio)
Decoding PGS stream (track 3): Resolution: 1920:1080 Frame rate: 23.976
Decoding PGS stream (track 4): Resolution: 1920:1080 Frame rate: 23.976
0.7% complete
1.6% complete
2.6% complete
3.6% complete
4.6% complete
5.6% complete
6.6% complete
7.6% complete
8.6% complete
9.6% complete
10.5% complete
11.5% complete
12.5% complete
13.5% complete
14.4% complete
15.4% complete
16.4% complete

It has a whole bunch of completion percentages that the Win 7 log doesn't have but is otherwise identical aside from the missing command line.

I'll try playing with the .BAT file option...

[wyliec2]

I do not burn with imgBurn, but,
Clown_BD can create *.BAT in Clown_BD directory if you check "batch" box at the end of user selection process - step3 window, so you can just create that batch script , Clown_BD would not run. You can run that Batch script manually afterwards. So before running it just check that script or pause it before burning (including pause line) and experiment with that line or just enter that line yourself in cmd prompt, whatever, look at it closely why it does not work under win10. Or perhaps that batch script would work then as oppose to not creating it, for whatever reason.

Thanks Al - creating the .BAT file and then running it manually seems to work!! I'll do some more playing around with it to confirm the process and document for repeatability!!