BD Rebuilder Beta - Bug Reports Only

[drmih]

Using BD-Rebuilder v0.29.2

Now I'm getting a lot of these while encoding:
- [07:57:18] GUI issue, no hWnd returned.
- [07:57:18] GUI issue, no hWnd returned.

2-3 every second.

Movie: http://www.imdb.com/title/tt1132620/
Region: B.
Used DVDFAB 6.06 to rip.

I had this on a title but was doing about 3 other things at the same time (primarily copying files around). When I restarted the process without the other things it went through perfectly.

[tekmobile]

I had this on a title but was doing about 3 other things at the same time (primarily copying files around). When I restarted the process without the other things it went through perfectly.

The only time I get this too is when copying files around

[writersblock29]

Using BD-Rebuilder v0.29.2

"GUI issue, no hWnd returned." I'm getting these, too. My computer was left alone, however, from the time I started it to this morning, when I checked it. Task manager tells me that the CPU's still laboring under X264, so I'm assuming the encode is going through as planned. I'm leaving it alone to see if it finishes.

Braveheart, Disk One, Region A.
Windows XP X64, all supporting programs (AVISynth, FFdshow, ect) most current version.

[jdobbs]

Maybe you Region B guys should send jdobbs your problematic movies... Consider it a sacrifice to science. :) I was able to repeat the demuxing issue on Black Hawk Down with the Region A disc. It a TSMUXER issue, though, and I'm not sure I can do anything about it.

[jdobbs]

Using BD-Rebuilder v0.29.2

"GUI issue, no hWnd returned." I'm getting these, too. My computer was left alone, however, from the time I started it to this morning, when I checked it. Task manager tells me that the CPU's still laboring under X264, so I'm assuming the encode is going through as planned. I'm leaving it alone to see if it finishes.

Braveheart, Disk One, Region A.
Windows XP X64, all supporting programs (AVISynth, FFdshow, ect) most current version.Sigh... this thing is driving me nuts. I thought I had it this time.

[Capsbackup]

Using BD-Rebuilder v0.29.2

"GUI issue, no hWnd returned." I'm getting these, too. My computer was left alone, however, from the time I started it to this morning, when I checked it. Task manager tells me that the CPU's still laboring under X264, so I'm assuming the encode is going through as planned. I'm leaving it alone to see if it finishes.

Braveheart, Disk One, Region A.
Windows XP X64, all supporting programs (AVISynth, FFdshow, ect) most current version.

Same movie, same experience here too. Only "GUI issue, no hWnd returned" for the main .m2ts though (00006.m2ts), as the smaller ones work as normally expected. Movie completes successfully and plays perfectly fine too.

[jdobbs]

What do all of you have in common? I can run this thing forever and not get that error. But in testing, I found that there are more than one window associated with the X264 process id -- so I thought "maybe they're getting the wrong window randomly"... obviously that wasn't it.

There has to be some common thread or reason why this is happening only on certain systems.

Are you all using:

Windows XP 64?
Some 64 bit O/S (as opposed to 32 bit)?
What version of FFDSHOW? (don't say "latest")
What version of HAALI?
Are you using the version of X264 included with BD-RB?

[jdobbs]

I've updated the first post of this thread to include links to a newer release of BD-RB (v0.29.03). Changes:September 8th, 2009 - v0.29.03
- Made another adjustment to attempt to prevent the
dreaded "GUI Issue, no hWnd returned" error.

September 7th, 2009 - v0.29.02
- Made changes to the code for collecting the hWnd
of X264 and updating progress. It appears that
X264 can have more than one top level hWnd that
is associated with its process id, causing BD-RB
to sometimes look for status in the wrong place.
- Corrected an issue in which stopping an encode in
ABR mode, and then resuming in 2 pass could cause
BD-RB to fail (no .STATS file).
- Updated the Movie-Only playlist selection dialog
so it accurately displays chapters (rather than
marks). Also corrected the chapter output to the
.META file in the same way. This should prevent
meta files with too many chapters.
- Updated X264 version to the latest release (r1151)
- Other minor corrections and cosmetic fixes.

I've increased the timeout period to 60 seconds (from 10) before BD-RB decides the the GUI issue exists.... hoping that on a very busy system, the issue is caused by delays in actual start of the encode process.

[Capsbackup]

@jdobbs;
XP Pro SP3, 32 bit
ffdshow - (rev 3026) (2009-07-05)
Haali Matroska Muxer - (2009-01-10)
x264 is what is included with BD-RB v2902.

This was the first time I experienced this issue. Movie Braveheart, Region A. Only happened on the main .m2ts, 00006.m2ts, which is 42.8 GB. All the smaller files worked properly.

[Aratar]

Today I used BD REBUILDER v0.29.02 to rip german blu-ray of 'The Reader'. I used KEEP_INTERLACING=1 because there are a lot of SD-quality (MPEG-2) interlaced filmed material on the disc, my hardware equipment does a better deinterlacing job than avisynth/decomb.dll does so I would prefer to keep interlaced material 'as is'. However, I noticed when using KEEP_INTERLACING=1, the field order (tff/bff) of the reencoded material is wrong, which results in strange motion jerkyness because the wrong two half pictures are assumed to be a full frame. Not sure if that's always the case when using KEEP_INTERLACING.

[jdobbs]

@jdobbs;
XP Pro SP3, 32 bit
ffdshow - (rev 3026) (2009-07-05)
Haali Matroska Muxer - (2009-01-10)
x264 is what is included with BD-RB v2902.

This was the first time I experienced this issue. Movie Braveheart, Region A. Only happened on the main .m2ts, 00006.m2ts, which is 42.8 GB. All the smaller files worked properly. Since I can't make it happen even when I try, pretty much all the "fixes" have been stabs in the dark. I say "maybe if their system is doing X it might cause Y... so I'll see if I can prevent Y"... The way I'm doing it now should work. I call the O/S using EnumWindows() and pass it a callback routine. The callback should get called for every top-level window. I retrieve and compare the process id (PID) of the window to the process id of X264 (from when I created the process). Since there are more than one window associated with it -- I look for the caption showing that it is processing ("x264 [") -- if that matches I know I have the right window.

The last version kept looking for 10 seconds (which in computer time is a long time), I just changed it to look for 60 seconds in v0.29.03.

If this doesn't work it implies that the X264 you see running in the task manager doesn't have a window associated with it or that the caption isn't being updated with the status information... and that's just inconceivable (especially since it always works on my computer).

[Groucho2004]

I call the O/S using EnumWindows() and pass it a callback routine. The callback should get called for every top-level window. I retrieve and compare the process id (PID) of the window to the process id of X264 (from when I created the process). Since there are more than one window associated with it -- I look for the caption showing that it is processing ("x264 [") -- if that matches I know I have the right window.

The last version kept looking for 10 seconds (which in computer time is a long time), I just changed it to look for 60 seconds in v0.29.03.

If this doesn't work it implies that the X264 you see running in the task manager doesn't have a window associated with it or that the caption isn't being updated with the status information... and that's just inconceivable (especially since it always works on my computer).

I sniffed a bit around with Spy++ while x264 was running. x264 creates it's main window (which has the window class "ConsoleWindowClass") and sometimes a tooltip window (same caption but with the class name "tooltips_class32"). The tooltip window only gets created when the main window is not hidden and the mouse hovers over the taskbar icon.

Basically, all this seems to be normal behaviour and I can't see anything wrong the way you coded the window capture.

I'm curious about the percentage of users who experience this problem and as you mentioned, maybe there is something common among those.

[allright]

Are you all using:

Windows XP 64?
Some 64 bit O/S (as opposed to 32 bit)?
What version of FFDSHOW? (don't say "latest")
What version of HAALI?
Are you using the version of X264 included with BD-RB?

I'm using:

Vista Ultimate 64 bit
FFDSHOW v 2661
HAALI 1.9.42.1
Using the X264 included with BD-RB.

[jdobbs]

I sniffed a bit around with Spy++ while x264 was running. x264 creates it's main window (which has the window class "ConsoleWindowClass") and sometimes a tooltip window (same caption but with the class name "tooltips_class32"). The tooltip window only gets created when the main window is not hidden and the mouse hovers over the taskbar icon.

Basically, all this seems to be normal behaviour and I can't see anything wrong the way you coded the window capture.

I'm curious about the percentage of users who experience this problem and as you mentioned, maybe there is something common among those. When I scan for the PID there are two other windows that have the same process ID. One of them has a caption that says "ActiveMovie Window" --the other says "xTrayIconWnd". I'm guessing these are associated with AVISYNTH's frame serving to X264 and FFDSHOW.

[Edit] Maybe I'll look for the "ConsoleWindowClass" as opposed to the caption. That way at least I'd have the correct window and wouldn't have to worry about timeouts...

[samtroy]

jdobbs, may I ask for your personal recommendations for BD Rebuilder regarding the used decoders for H.264 and VC-1?

Would you prefer WMP9 or libavcodec for VC-1?

And what about H.264 sources? Is libavcodec always safe to use there too, also qualitywise?

I'm sure a lot of people are unsure about this.

[jdobbs]

I personally use libavcodec for AVC and MPEG-2 and WMV11 for VC-1 (install Windows Media Player 11 and then set VC-1 to "disabled" in FFDSHOW). If using Windows 7 (which I am not) there are a couple of other hoops to jump through for VC-1 -- do a seach of this thread for details.

[PurpleMan]

Just finished doing Batman Begins again (full backup BD25).

Unfortunately, result has major PiP issues.
The problem is two-fold:

1. When you turn on the "in-movie experience" (pip), the secondary video appears even when it's not supposed to (which means I see a black frame in the pip, because there's no video there).

2. Even in parts that it IS supposed to be showing, it seems slight unsynced with when the video frame jumps from one side of the screen to another. I mean, PiP is in lower-right corner and we have this guy talking there. then the frame moves to the lower-left corner and you see the guy there for half a second, then it switches to another scene, as if that half of second was intended for BEFORE the frame moved from one side to the other. (I confirmed this on the original disc, in which it is indeed in sync with the frame-move).

I don't have a standalone player, but both these issues presented themselves in PowerDVD7, PowerDVD9 and TotalMedia Theatre 3. All of which play the original disc correctly with no problem.

Just finished backing it up yet again and the problem recreated itself.
Don't know why I thought it would magically work now. Also, don't know why I've set it to 2-pass now. Oh well.

[Furiousflea]

Today I used BD REBUILDER v0.29.02 to rip german blu-ray of 'The Reader'. I used KEEP_INTERLACING=1 because there are a lot of SD-quality (MPEG-2) interlaced filmed material on the disc, my hardware equipment does a better deinterlacing job than avisynth/decomb.dll does so I would prefer to keep interlaced material 'as is'. However, I noticed when using KEEP_INTERLACING=1, the field order (tff/bff) of the reencoded material is wrong, which results in strange motion jerkyness because the wrong two half pictures are assumed to be a full frame. Not sure if that's always the case when using KEEP_INTERLACING.

Seems to be...not sure what the problem is there jdobbs? surely just an incorrect switch being used?

[tekmobile]

I've increased the timeout period to 60 seconds (from 10) before BD-RB decides the the GUI issue exists.... hoping that on a very busy system, the issue is caused by delays in actual start of the encode process.

The only time I see this issue is when im copying files when the encode starts I have SHOW_ENCODER on and the error always happens before the x264 windows actually appears

[Groucho2004]

When I scan for the PID there are two other windows that have the same process ID. One of them has a caption that says "ActiveMovie Window" --the other says "xTrayIconWnd". I'm guessing these are associated with AVISYNTH's frame serving to X264 and FFDSHOW.

[Edit] Maybe I'll look for the "ConsoleWindowClass" as opposed to the caption. That way at least I'd have the correct window and wouldn't have to worry about timeouts...

Here is a screen shot from Spy++ while x264 is running:
http://www.iol.ie/~schubert/Image1.png

I think the "ActiveMovie Window" is the Mediasplitter tray icon and the "ffdshow_tray_737" is the ffdshow tray icon. No idea what "xTrayIconWnd" is.

All this info still doesn't explain why the code fails in some situations...

The best way to debug this would be for the people who have problems to run Spy++ and post a screen shot or log. Spy++ comes with the full version of Visual Studio but I think it's also a freely available sample that anyone could compile and distribute. I'll check if I can make this available somehow.

[Groucho2004]

The only time I see this issue is when im copying files when the encode starts I have SHOW_ENCODER on and the error always happens before the x264 windows actually appears

@jdobbs:
Could it be that you are checking for the existance of the x264 window before it is actually created?

[Capsbackup]

Since I can't make it happen even when I try, pretty much all the "fixes" have been stabs in the dark. I say "maybe if their system is doing X it might cause Y... so I'll see if I can prevent Y"... The way I'm doing it now should work. I call the O/S using EnumWindows() and pass it a callback routine. The callback should get called for every top-level window. I retrieve and compare the process id (PID) of the window to the process id of X264 (from when I created the process). Since there are more than one window associated with it -- I look for the caption showing that it is processing ("x264 [") -- if that matches I know I have the right window.

The last version kept looking for 10 seconds (which in computer time is a long time), I just changed it to look for 60 seconds in v0.29.03.

If this doesn't work it implies that the X264 you see running in the task manager doesn't have a window associated with it or that the caption isn't being updated with the status information... and that's just inconceivable (especially since it always works on my computer).

This appears to have fixed the problem for me. I am 92% complete into pass 2 of Braveheart and no more "GUI issue, no hWnd returned" :)
For me, this "GUI issue, no hWnd returned" happened only one time and with v0.29.02, on Braveheart, and on the 2nd pass of a full movie backup to BD-25.
So the changes to BD-RBV02903 has corrected the issue for me.( with ETA 0:32:00 to go) :p

EDIT:
Completed Successfully!! I hope for all this corrects this annoyance. :D

[Race Guy]

Today I used BD REBUILDER v0.29.02 to rip german blu-ray of 'The Reader'. I used KEEP_INTERLACING=1 because there are a lot of SD-quality (MPEG-2) interlaced filmed material on the disc, my hardware equipment does a better deinterlacing job than avisynth/decomb.dll does so I would prefer to keep interlaced material 'as is'. However, I noticed when using KEEP_INTERLACING=1, the field order (tff/bff) of the reencoded material is wrong, which results in strange motion jerkyness because the wrong two half pictures are assumed to be a full frame. Not sure if that's always the case when using KEEP_INTERLACING.

I'll BET this is the issue on my Abbey Road rebuild:

http://forum.doom9.org/showthread.php?p=1321265#post1321265

Come to think of it, I NEVER see "jerkiness" on 1080p/24, but depending on the content's "on screen motion", MANY of the 1080i sources I rebuilt can look jerky at times. The Abbey Road was absolutely HORRIBLE though!

[jdobbs]

@jdobbs:
Could it be that you are checking for the existance of the x264 window before it is actually created? Not really, because in the latest version I continue to check for it for a full 60 seconds...

[jdobbs]

I'll BET this is the issue on my Abbey Road rebuild:

http://forum.doom9.org/showthread.php?p=1321265#post1321265

Come to think of it, I NEVER see "jerkiness" on 1080p/24, but depending on the content's "on screen motion", MANY of the 1080i sources I rebuilt can look jerky at times. The Abbey Road was absolutely HORRIBLE though! It sounds more like a field order issue than the link you posted. I'm not really sure how to adjust field order in X264, I'll have to go back and review the documentation. I'd suggest in the meantime that you leave BD-RB at the default setting and let it do deinterlacing.

[stackner]

i have used bdrebuilder a few times now making bd25's all have worked well. however i have tried the original stargate movie to bd25 but it is compressing to 6gbs total. the movie stream is compressing to 2.5gb. im choosing bd25 so why is the final product coming out at 6gb? ive tried many different settings even. have not had this happen with any other movie and ive used all bd versions from 0.25.03 0.29.02

i tried both the latest versions 0.29.01 and 0.29.02 on the disc with same problem


@stackner

Hi!

1) What region is your original, commercial BluRay disc?

2) What software and procedures did you use to eliminate/overcome the copy protection of the original disc?

it is commercial dvd (stargate) australian pal movie,
i used anydvd hd as always to rip.

same steps as all other movies that have worked. even re-ripped the disc twice. still full disc backup to bd25 is turning out 6gb.

[stax76]

I wonder why you work with handles and don't use the CreateProcess with CREATE_NO_WINDOW flag redirecting the console output. With VB.NET it's like 5 lines code to create a console process without window and redirect it's output.

I also wonder why you never migrated to .NET, every second year a new VB.NET and .NET Framework version adds tons of cool new features making programming easier.

[cybercurves]

I also got this when running 29.02 -

- MOVIE-ONLY mode enabled
[04:38:58] PHASE ONE, Encoding
- [04:38:58] Extracting A/V streams [VID_00000]
- [04:51:02] Reencoding: VID_00000 (1 of 1)
- [04:51:13] GUI issue, no hWnd returned.
- [04:51:13] GUI issue, no hWnd returned.
- [04:51:13] GUI issue, no hWnd returned.
- [04:51:13] GUI issue, no hWnd returned......

I reverted back to 29.01 and it was fine.

I'm currently using 29.03 now and it appears to be back to normal.

cybercurves

[Capsbackup]

i have used bdrebuilder a few times now making bd25's all have worked well. however i have tried the original stargate movie to bd25 but it is compressing to 6gbs total. the movie stream is compressing to 2.5gb. im choosing bd25 so why is the final product coming out at 6gb? ive tried many different settings even. have not had this happen with any other movie and ive used all bd versions from 0.25.03 0.29.02

i tried both the latest versions 0.29.01 and 0.29.02 on the disc with same problem




it is commercial dvd (stargate) australian pal movie,
i used anydvd hd as always to rip.

same steps as all other movies that have worked. even re-ripped the disc twice. still full disc backup to bd25 is turning out 6gb.

It would be helpful if you could provide more info.. what OS are you using, BD-RB log and ini file, what settings.. 1 pass crf, hi speed, etc.

[setarip_old]

@stacknerit is commercial dvd (stargate) australian pal movieIf this is not a typo, you should be aware that BD Rebuilder only processes BluRay discs - and not DVDs, or anything else...

Perhaps you should try "DVD Rebuilder"...

[jdobbs]

I wonder why you work with handles and don't use the CreateProcess with CREATE_NO_WINDOW flag redirecting the console output. With VB.NET it's like 5 lines code to create a console process without window and redirect it's output.

I also wonder why you never migrated to .NET, every second year a new VB.NET and .NET Framework version adds tons of cool new features making programming easier. So now I'm getting programming lessons in my bug thread too? C'mon, give me a little credit. I work with handles because that's how Windows works, and I like having the kind of control that is lost when you bury it in layer after layer of virtualization. I started out life writing in machine code (note that I didn't say assembler) and I just don't like getting too far away from the real computer.

I don't use .NET because I don't want to use .NET. It may cause a couple of headaches and I have to actually write code to fix it, but in the long run its worth it to me.

[jdobbs]

@stacknerIf this is not a typo, you should be aware that BD Rebuilder only processes BluRay discs - and not DVDs, or anything else...

Perhaps you should try "DVD Rebuilder"... He's been using DVD Rebuilder for a long time (years).

I think it was a typo.

[stackner]

lol actually i was half asleep when doing that post. no im using bdrebuilder and its the stargate blu-ray not dvd sorry guys. however i have used dvd rebuilder for ages now. but ive done a few blu-ray backups first time i have this issue. ill try again and post the log file afterwards.

[writersblock29]

@Jdobbs

Is it conceivable that perhaps something in the Windows Updates might be what's throwing BDRB for a loop? I always keep my system as current as the OS allows, but I'm aware of several people (my wife included) who stick to the "why improve what ain't broke?" philosophy, and keep automatic updates turned off. This might explain why some of us report what others (using what on a forum appears to be similiar systems) don't have any issue whatsoever with. I'm more than happy to supply whatever information you feel might help. In all honesty, I don't recall a single hicup on Windows 7 X64 while I used it (after, of course, tweaking the directshow setting to allow FFdshow to run as it should). The only reason I've reinstalled XP X64 is that my Windows 7 Upgrade disk will be showing up in another month, and I needed something to upgrade FROM to install it.

If it means anything to you... the Braveheart disk works. It fails to show the menu buttons on PowerDVD9 (which is installed on the same system that's running Windows XP X64), but on Arcsoft TotalMedia Theatre (which is on my HTPC), it's fine. Leaving it alone resulted in a very good BD9 copy--better than I expected with such a long movie.

[PurpleMan]

@Jdobbs

Is it conceivable that perhaps something in the Windows Updates might be what's throwing BDRB for a loop? I always keep my system as current as the OS allows, but I'm aware of several people (my wife included) who stick to the "why improve what ain't broke?" philosophy, and keep automatic updates turned off. This might explain why some of us report what others (using what on a forum appears to be similiar systems) don't have any issue whatsoever with. I'm more than happy to supply whatever information you feel might help. In all honesty, I don't recall a single hicup on Windows 7 X64 while I used it (after, of course, tweaking the directshow setting to allow FFdshow to run as it should). The only reason I've reinstalled XP X64 is that my Windows 7 Upgrade disk will be showing up in another month, and I needed something to upgrade FROM to install it.

If it means anything to you... the Braveheart disk works. It fails to show the menu buttons on PowerDVD9 (which is installed on the same system that's running Windows XP X64), but on Arcsoft TotalMedia Theatre (which is on my HTPC), it's fine. Leaving it alone resulted in a very good BD9 copy--better than I expected with such a long movie.

Using Windows 7 x64, never experienced the issue as well.

[samtroy]

I personally use libavcodec for AVC and MPEG-2 and WMV11 for VC-1 (install Windows Media Player 11 and then set VC-1 to "disabled" in FFDSHOW). If using Windows 7 (which I am not) there are a couple of other hoops to jump through for VC-1 -- do a seach of this thread for details.

OK, thanks for sharing.

To all Windows 7 users (like me):

Could you guys please be so kind and tell me what decoders you use for BD Rebuilder in Win7 for H.264 and VC-1 and what your experiences are so far?

I've tried Win7's own (Microsoft) H.264 decoder so far with very good results. And for VC-1 movies I'm not sure yet if I should use WMP9 or libavcodec (of course I deleted the 'prefered' folder in the registry, otherwise VC-1 won't work).

I'm not even sure which VC-1 decoder is used when I select WMP9 in ffdshow. Is the most up-to-date MS decoder (WMP12?) used or is it really the 'old' WMP9 decoder like it says?

[spida_singh]

OK, thanks for sharing.

To all Windows 7 users (like me):

Could you guys please be so kind and tell me what decoders you use for BD Rebuilder in Win7 for H.264 and VC-1 and what your experiences are so far?

I've tried Win7's own (Microsoft) H.264 decoder so far with very good results. And for VC-1 movies I'm not sure yet if I should use WMP9 or libavcodec (of course I deleted the 'prefered' folder in the registry, otherwise VC-1 won't work).

I'm not even sure which VC-1 decoder is used when I select WMP9 in ffdshow. Is the most up-to-date MS decoder (WMP12?) used or is it really the 'old' WMP9 decoder like it says?

I always leave VC-1 in ffdshow set to wmv9, h.264 set to ffmpeg-mt, and never had any problems so far.

I use windows 7 x64.

regards

[PurpleMan]

I use libavcodec in ffdshow for VC1 (wmv9 simply doesn't work for me under windows 7 x64, never had a reason to find out why, as libavcodec works great).

and for h264 I use CoreAVC.

[wijko]

Hi,

I've been using BD Rebuilder for a few months now, but with the dutch retail of Pinocchio I came across an error that I haven't seen in the forum.

I hope someone can help. My OS is win7, all drives are NTFS. I used all quality settings and the new version (and two previous ones as well). The error message is as follows:

-----------------------
[17:10:27] BD Rebuilder v0.29.01 (beta)
- Source: PINOCCHIO_GBR_D1
- Input BD size: 31,82 GB
- Approximate total content: [01:52:11.558]
- Target BD size: 22,46 GB
[17:10:27] PHASE ONE, Encoding
- [17:10:27] Extracting A/V streams [VID_00001]
- [17:27:21] Reencoding: VID_00001 (1 of 18)
- [17:27:21] Reencoding secondary video [TRK_02]
- [17:33:36] Collecting video information
- Video: 1920x1080, 23,976fps, 126.216 frames
- Bitrate: 16.246 Kbs
- [17:33:36] Reencoding: VID_00001, Pass 1 of 2
- [19:01:00] Reencoding: VID_00001, Pass 2 of 2
- [22:05:52] Video Encode complete
- [22:05:52] Reencoding audio tracks (if req'd)
- [22:05:52] Multiplexing M2TS
- Error in attempt to multiplex: MUX_00001.meta
- Pes packet len too large ( >100Mb). Bad stream or invalid codec speciffed.
[22:06:58] - Failed to build structure, aborted

Thanks for any insights on this issue.

[PurpleMan]

Hi,

I've been using BD Rebuilder for a few months now, but with the dutch retail of Pinocchio I came across an error that I haven't seen in the forum.

I hope someone can help. My OS is win7, all drives are NTFS. I used all quality settings and the new version (and two previous ones as well). The error message is as follows:

-----------------------
[17:10:27] BD Rebuilder v0.29.01 (beta)
- Source: PINOCCHIO_GBR_D1
- Input BD size: 31,82 GB
- Approximate total content: [01:52:11.558]
- Target BD size: 22,46 GB
[17:10:27] PHASE ONE, Encoding
- [17:10:27] Extracting A/V streams [VID_00001]
- [17:27:21] Reencoding: VID_00001 (1 of 18)
- [17:27:21] Reencoding secondary video [TRK_02]
- [17:33:36] Collecting video information
- Video: 1920x1080, 23,976fps, 126.216 frames
- Bitrate: 16.246 Kbs
- [17:33:36] Reencoding: VID_00001, Pass 1 of 2
- [19:01:00] Reencoding: VID_00001, Pass 2 of 2
- [22:05:52] Video Encode complete
- [22:05:52] Reencoding audio tracks (if req'd)
- [22:05:52] Multiplexing M2TS
- Error in attempt to multiplex: MUX_00001.meta
- Pes packet len too large ( >100Mb). Bad stream or invalid codec speciffed.
[22:06:58] - Failed to build structure, aborted

Thanks for any insights on this issue.

That error is being returned from tsMuxer. Could you paste that metafile?

[h8t3d1]

Hello - I saw some of the posts about the dreaded
'GUI issue, no hWnd returned' I recieved it in version 0.29.03 and in 0.29.02. Been using the program since the begining and never saw this error before. I did see where you made a fix for this in the latest version so I wanted to share this log.
-----------------------
[01:13:37] BD Rebuilder v0.29.03 (beta)
- Source: FAST_AND_FURIOUS
- Input BD size: 43.94 GB
- Approximate total content: [04:05:13.498]
- Target BD size: 22.46 GB
[01:13:49] PHASE ONE, Encoding
- [01:13:49] Extracting A/V streams [VID_00238]
- [01:13:49] Reencoding: VID_00238 (1 of 35)
- [01:13:57] Extracting A/V streams [VID_00236]
- [01:13:57] Reencoding: VID_00236 (2 of 35)
- [01:14:04] Extracting A/V streams [VID_00237]
- [01:14:05] Reencoding: VID_00237 (3 of 35)
- [01:14:12] Extracting A/V streams [VID_00078]
- [01:14:13] Reencoding: VID_00078 (4 of 35)
- [01:14:56] Extracting A/V streams [VID_00061]
- [01:14:59] Reencoding: VID_00061 (5 of 35)
- [01:15:45] Extracting A/V streams [VID_00050]
- [01:15:47] Reencoding: VID_00050 (6 of 35)
- [01:16:41] Extracting A/V streams [VID_00062]
- [01:16:44] Reencoding: VID_00062 (7 of 35)
- [01:17:41] Extracting A/V streams [VID_00064]
- [01:17:44] Reencoding: VID_00064 (8 of 35)
- [01:18:55] Extracting A/V streams [VID_00212]
- [01:19:00] Reencoding: VID_00212 (9 of 35)
- [01:19:58] Extracting A/V streams [VID_00214]
- [01:20:02] Reencoding: VID_00214 (10 of 35)
- [01:21:32] Extracting A/V streams [VID_00225]
- [01:21:45] Reencoding: VID_00225 (11 of 35)
- [01:22:55] Extracting A/V streams [VID_00202]
- [01:23:02] Reencoding: VID_00202 (12 of 35)
- [01:24:37] Extracting A/V streams [VID_00215]
- [01:24:42] Reencoding: VID_00215 (13 of 35)
- [01:26:57] Extracting A/V streams [VID_00228]
- [01:27:17] Reencoding: VID_00228 (14 of 35)
- [01:29:03] Extracting A/V streams [VID_00216]
- [01:29:11] Reencoding: VID_00216 (15 of 35)
- [01:31:29] Extracting A/V streams [VID_00221]
- [01:31:51] Reencoding: VID_00221 (16 of 35)
- [01:33:49] Extracting A/V streams [VID_00217]
- [01:34:12] Reencoding: VID_00217 (17 of 35)
- [01:36:25] Extracting A/V streams [VID_00224]
- [01:36:47] Reencoding: VID_00224 (18 of 35)
- [01:38:46] Extracting A/V streams [VID_00223]
- [01:39:15] Reencoding: VID_00223 (19 of 35)
- [01:41:16] Extracting A/V streams [VID_00220]
- [01:41:40] Reencoding: VID_00220 (20 of 35)
- [01:43:43] Extracting A/V streams [VID_00226]
- [01:44:05] Reencoding: VID_00226 (21 of 35)
- [01:46:13] Extracting A/V streams [VID_00211]
- [01:46:48] Reencoding: VID_00211 (22 of 35)
- [01:49:00] Extracting A/V streams [VID_00219]
- [01:49:25] Reencoding: VID_00219 (23 of 35)
- [01:52:06] Extracting A/V streams [VID_00207]
- [01:52:42] Reencoding: VID_00207 (24 of 35)
- [01:55:34] Extracting A/V streams [VID_00011]
- [01:56:07] Reencoding: VID_00011 (25 of 35)
- [02:00:03] Extracting A/V streams [VID_00205]
- [02:00:41] Reencoding: VID_00205 (26 of 35)
- [02:04:34] Extracting A/V streams [VID_00204]
- [02:05:26] Reencoding: VID_00204 (27 of 35)
- [02:10:45] Extracting A/V streams [VID_00227]
- [02:11:56] Reencoding: VID_00227 (28 of 35)
- [02:17:52] Extracting A/V streams [VID_00222]
- [02:18:58] Reencoding: VID_00222 (29 of 35)
- [02:25:05] Extracting A/V streams [VID_00218]
- [02:26:52] Reencoding: VID_00218 (30 of 35)
- [02:27:57] GUI issue, no hWnd returned.
- Encode failed. Retrying.
- Encode failed. Retrying.
- Reached retry limit. Aborting.
[02:30:53] - Failed video encode, aborted
Using Windows Vista Ultimate 64 bit
Encoder settings = Idle/Highest/No One Pass
Setup = Color Boost Checked
Going to try it with the 0.29.01 version and see if it does it.

[wijko]

That error is being returned from tsMuxer. Could you paste that metafile?

MUXOPT --no-pcr-on-video-pid --new-audio-pes --blu-ray --vbr --auto-chapters=5 --vbv-len=500
V_MPEG4/ISO/AVC, "F:\BD25 REENCODES\FULL REENCODE\PINOCCHIO\WORKFILES\VID_00001.AVS.MKV", fps=23.976, track=1, insertSEI, contSPS
V_MPEG4/ISO/AVC, "F:\BD25 REENCODES\FULL REENCODE\PINOCCHIO\WORKFILES\VID_00001_2.AVS.MKV", fps=23.976, track=1, secondary, insertSEI, contSPS
A_DTS, "F:\BD25 REENCODES\FULL REENCODE\PINOCCHIO\WORKFILES\00001.track_4352.DTS", lang=eng
A_DTS, "F:\BD25 REENCODES\FULL REENCODE\PINOCCHIO\WORKFILES\00001.track_4353.DTS", lang=ita
A_DTS, "F:\BD25 REENCODES\FULL REENCODE\PINOCCHIO\WORKFILES\00001.track_4354.DTS", lang=spa
A_DTS, "F:\BD25 REENCODES\FULL REENCODE\PINOCCHIO\WORKFILES\00001.track_4355.DTS", lang=nld
A_AC3, "F:\BD25 REENCODES\FULL REENCODE\PINOCCHIO\WORKFILES\00001.track_4356.AC3", lang=eng
A_AC3, "F:\BD25 REENCODES\FULL REENCODE\PINOCCHIO\WORKFILES\00001.track_4357.AC3", lang=ita
A_AC3, "F:\BD25 REENCODES\FULL REENCODE\PINOCCHIO\WORKFILES\00001.track_4358.AC3", lang=spa
A_AC3, "F:\BD25 REENCODES\FULL REENCODE\PINOCCHIO\WORKFILES\00001.track_4359.AC3", lang=nld
S_HDMV/PGS, "F:\BD25 REENCODES\FULL REENCODE\PINOCCHIO\WORKFILES\00001.track_4608.sup", fps=23.976, lang=eng
S_HDMV/PGS, "F:\BD25 REENCODES\FULL REENCODE\PINOCCHIO\WORKFILES\00001.track_4609.sup", fps=23.976, lang=eng
S_HDMV/PGS, "F:\BD25 REENCODES\FULL REENCODE\PINOCCHIO\WORKFILES\00001.track_4610.sup", fps=23.976, lang=ita
S_HDMV/PGS, "F:\BD25 REENCODES\FULL REENCODE\PINOCCHIO\WORKFILES\00001.track_4611.sup", fps=23.976, lang=spa
S_HDMV/PGS, "F:\BD25 REENCODES\FULL REENCODE\PINOCCHIO\WORKFILES\00001.track_4612.sup", fps=23.976, lang=nld
S_HDMV/PGS, "F:\BD25 REENCODES\FULL REENCODE\PINOCCHIO\WORKFILES\00001.track_4613.sup", fps=23.976, lang=ita
S_HDMV/PGS, "F:\BD25 REENCODES\FULL REENCODE\PINOCCHIO\WORKFILES\00001.track_4614.sup", fps=23.976, lang=spa
S_HDMV/PGS, "F:\BD25 REENCODES\FULL REENCODE\PINOCCHIO\WORKFILES\00001.track_4615.sup", fps=23.976, lang=nld
S_HDMV/PGS, "F:\BD25 REENCODES\FULL REENCODE\PINOCCHIO\WORKFILES\00001.track_4616.sup", fps=23.976, lang=eng
S_HDMV/PGS, "F:\BD25 REENCODES\FULL REENCODE\PINOCCHIO\WORKFILES\00001.track_4617.sup", fps=23.976, lang=ita
S_HDMV/PGS, "F:\BD25 REENCODES\FULL REENCODE\PINOCCHIO\WORKFILES\00001.track_4618.sup", fps=23.976, lang=spa
S_HDMV/PGS, "F:\BD25 REENCODES\FULL REENCODE\PINOCCHIO\WORKFILES\00001.track_4619.sup", fps=23.976, lang=nld
S_HDMV/PGS, "F:\BD25 REENCODES\FULL REENCODE\PINOCCHIO\WORKFILES\00001.track_4620.sup", fps=23.976, lang=eng
S_HDMV/PGS, "F:\BD25 REENCODES\FULL REENCODE\PINOCCHIO\WORKFILES\00001.track_4621.sup", fps=23.976, lang=ita
S_HDMV/PGS, "F:\BD25 REENCODES\FULL REENCODE\PINOCCHIO\WORKFILES\00001.track_4622.sup", fps=23.976, lang=spa
S_HDMV/PGS, "F:\BD25 REENCODES\FULL REENCODE\PINOCCHIO\WORKFILES\00001.track_4623.sup", fps=23.976, lang=nld

[Pntgrd]

OK, thanks for sharing.

To all Windows 7 users (like me):

Could you guys please be so kind and tell me what decoders you use for BD Rebuilder in Win7 for H.264 and VC-1 and what your experiences are so far?

I've tried Win7's own (Microsoft) H.264 decoder so far with very good results. And for VC-1 movies I'm not sure yet if I should use WMP9 or libavcodec (of course I deleted the 'prefered' folder in the registry, otherwise VC-1 won't work).

I'm not even sure which VC-1 decoder is used when I select WMP9 in ffdshow. Is the most up-to-date MS decoder (WMP12?) used or is it really the 'old' WMP9 decoder like it says?
I am not sure but I am guessing WMP that comes with Win7 x64. I used one of the Tweakers mentioned here and if you look in FFDSHOW it says VC-1 is set to disabled. But all the VC-1 titles I do work just fine.

[Race Guy]

It sounds more like a field order issue than the link you posted. I'm not really sure how to adjust field order in X264, I'll have to go back and review the documentation. I'd suggest in the meantime that you leave BD-RB at the default setting and let it do deinterlacing.

That's the problem jdobbs, I get the "jerkies" on certain 1080i scenes using the default settings.

[Aratar]

That's the problem jdobbs, I get the "jerkies" on certain 1080i scenes using the default settings.

Could be a playback issue too, e.g. for some reason my Samsung BR player uses 1080p/24 mode for extras that BD rebuilder deinterlaced (1080i->1080p) without keep_interlacing=1. However, the framerate is tagged 29.97 in clipinfo/playlist so it shouldn't actually use 1080p/24. Of course the playback then is jerky. My PS3 is using 1080p(60) mode instead, which looks fine. This is not a field order issue (at least I never had problem with the avisynth/decomb.dll deinterlacing itself) or a bug with bd rebuilder but another reason why I'd like to keep interlacing.

[Imperial Zeppelin]

Here's an error message I got today from McAfee when I tried to start v2.8.04...

McAfee has automatically blocked and removed a Trojan.

About this Trojan
Detected: Artemis!2EA64543AD3E (Trojan), Artemis!2EA64543AD3E (Trojan)
Location: C:\BD_Rebuilder\BD_Rebuilder.exe

Trojans appear as legitimate programs but can damage valuable files, disrupt performance, and allow unauthorized access to your computer.

[setarip_old]

@Imperial Zeppelin

Hi!

This has been addressed several times.

Also, there is no reason for you to be using an outdated version of BD Rebuilder.

[jdobbs]

Here's an error message I got today from McAfee when I tried to start v2.8.04...

McAfee has automatically blocked and removed a Trojan.

About this Trojan
Detected: Artemis!2EA64543AD3E (Trojan), Artemis!2EA64543AD3E (Trojan)
Location: C:\BD_Rebuilder\BD_Rebuilder.exe

Trojans appear as legitimate programs but can damage valuable files, disrupt performance, and allow unauthorized access to your computer. Search for "Artemis" in this thread essentially the answer is "McAfee's Artemis engine creates false positives". There is nothing wrong with BD-RB's downloads.

[Race Guy]

Could be a playback issue too, e.g. for some reason my Samsung BR player uses 1080p/24 mode for extras that BD rebuilder deinterlaced (1080i->1080p) without keep_interlacing=1. However, the framerate is tagged 29.97 in clipinfo/playlist so it shouldn't actually use 1080p/24. Of course the playback then is jerky. My PS3 is using 1080p(60) mode instead, which looks fine. This is not a field order issue (at least I never had problem with the avisynth/decomb.dll deinterlacing itself) or a bug with bd rebuilder but another reason why I'd like to keep interlacing.

Aratar, logic tells me that if the original disc plays "smooth" in my Oppo, but the rebuild looks "jerky", the player is NOT the issue.

x264 is somehow "corrupting" interlaced content. To me, this is a HUGE issue! What's the point if you get "right sized" vid that you CAN'T WATCH 'cause it looks like DUMP?

Are there any "beta testers" out there with this "Live From Abbey Road" disc that can process it default to BD-25 & see what they get??

[Furiousflea]

Aratar, logic tells me that if the original disc plays "smooth" in my Oppo, but the rebuild looks "jerky", the player is NOT the issue.

x264 is somehow "corrupting" interlaced content. To me, this is a HUGE issue! What's the point if you get "right sized" vid that you CAN'T WATCH 'cause it looks like DUMP?

Are there any "beta testers" out there with this "Live From Abbey Road" disc that can process it default to BD-25 & see what they get??

You are correct. Although it's not the fault of x264 but the switches that are being used for encoding.

The problem seems to be that BDRB is not deinterlacing to 60fps and then performing interlaced encoding as it should.

It's missing out the deinterlacing part so we just get some crappy zig zag video.

This is basic stuff! :eek: