Log in

View Full Version : BD Rebuilder Beta - Bug Reports Only


Pages : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 [101] 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648

Shuttle99
6th September 2009, 17:06
It shows x264 running on 4 cores and bouncing between 93 100% its been running now for about 6 hours and its a 35 gig file so it should be done at most in the next hour. No errors coming back in BD RB so I think it's fine and I will let it run another hour or so. I also refreshed the workfiles folder and the MKV file went from around 5 gig to 6 gig on the update.

It finished just fine.

Now testing on another with multiple files and it has stopped again at 22% on pass two of the third file. Seems to be random.

steelfatboy
6th September 2009, 19:10
Just running 29.01 and it's progress bar stopped at 50% but appears that it's still running according to the CPU. Is there anyway to tell the progress if it the progress bar stops.

I am experiencing the same thing encoding Harry Potter and the Order of the Phoenix.

The movie is still encoding, it is just the progress bar that has stopped.

steelfatboy
6th September 2009, 19:15
Have you seen a message in the log that says "GUI issue, no hWnd returned"? If not, then it isn't that the progress bar isn't updating, it means it just happens to be going slow right now and if you give it some time it will update.



Oops, that message is not in the log, so it must just be going slow.

bassnut
6th September 2009, 19:41
I can confirm this as well ...... I have been stuck at 68.6% now for a bit but all 4 processors are lit. X264 is running and no message in the log.

http://209.91.177.82/Images/pic.jpg

Shuttle99
6th September 2009, 20:03
It's not slow it stops. I am running another movie now with multiple files and it randomly stops on them and starts again when it starts the next file in line.

jdobbs
6th September 2009, 20:07
It's not slow it stops. I am running another movie now with multiple files and it randomly stops on them and starts again when it starts the next file in line. All I can say is that if you don't get the message, BD-RB is getting the window handle. I guess there's always the possibility that X264 is frozen -- but I doubt it.

You didn't answer my question -- did you get the GUI error message?

Shuttle99
6th September 2009, 20:34
Sorry there was no error messages. The bar stopped 22% of pass 2 and started again at the end when the audio and video are being put together and it's writing the folder. BD Rb is working fine and not hanging nor is X264 it's only the progress bar that stops updating.

bassnut
6th September 2009, 20:48
Well it might be just slow as JD has stated. Movie (Hellboy 2)finished completely without any errors or messages. I did notice at the begining with quicker encode for extras that the gooy was not updating, it just seemed like it went from 0% to 2.5% ...... but then the files could just have been too small to require an update and BDRebuilder did it at the end though I have never seen this befor ver 29.01.

Windows Vista 64 Bit

Shuttle99
6th September 2009, 21:15
When it stops updating nothing updates speed, ETA,FPS, frames it all stops and never resumes. The first time it stopped was on a movie with a single file to process it only started again when it started to write the final folder. Then the next one it did it on had multiple files to process and when it sops on a file it only resumes when it starts the next file but then it will hang again. The program continues just fine so it's more cosmetic and has no affect in the end you just have no idea how its coming along.

Windows Vista x64 here.

Sophocles
6th September 2009, 21:52
Sorry there was no error messages. The bar stopped 22% of pass 2 and started again at the end when the audio and video are being put together and it's writing the folder.

I experienced what I thought was a reencode issue on the second pass that seemed to do something similar. It appeared as though nothing was going on, the meter simply wasn't moving. I avoided the temptation to restart BD RB, and I'm glad I did, because a short time later the reencode finished and everything played back perfectly. Since the entire process finished in 3 hours and 43 minutes with two pass (Eagle Eye) and that's about average for a standard 105 to 120 minute movies I can't say why that happened.BTW, it was on Windows 7 64 bit.

MILLZY
6th September 2009, 22:40
I wonder i somebody could please help me out.I am trying windows 7 on one of my pc`s and i am not comfortable editing the registry for the problems with vc-1.I have tried the tweaks but can not seem to get them to work.I am looking for the one-click batch file that turbojet came up with(thanks) but the link is dead.Any help please..........:confused:Thinking of going back to xp64

jdobbs
6th September 2009, 22:57
I experienced what I thought was a reencode issue on the second pass that seemed to do something similar. It appeared as though nothing was going on, the meter simply wasn't moving. I avoided the temptation to restart BD RB, and I'm glad I did, because a short time later the reencode finished and everything played back perfectly. Since the entire process finished in 3 hours and 43 minutes with two pass (Eagle Eye) and that's about average for a standard 105 to 120 minute movies I can't say why that happened.BTW, it was on Windows 7 64 bit. Was that also on v0.29.1? Did you get any kind of error message in the log?

jdobbs
6th September 2009, 22:59
Sorry there was no error messages. The bar stopped 22% of pass 2 and started again at the end when the audio and video are being put together and it's writing the folder. BD Rb is working fine and not hanging nor is X264 it's only the progress bar that stops updating. That's just really weird. I wonder if this is something related to the latest X264 updates? If you get to 22% it means it had to have had the window handle to show the status to that point... all that BD-RB does after that is check the window caption for updates a few times a second. The 22% was on the "Current Progress" bar, right (not "Overall Progress")?

Groucho2004
6th September 2009, 23:10
That's just really weird. I wonder if this is something related to the latest X264 updates? If you get to 22% it means it had to have had the window handle to show the status to that point... all that BD-RB does after that is check the window caption for updates a few times a second. The 22% was on the "Current Progress" bar, right (not "Overall Progress")?

Hi jdobbs,

I sent you a PM about this problem.

Shuttle99
6th September 2009, 23:13
I remember in one of the post there was a line you could add to bdrebuilder.ini that opened a dos window and you could see the progress there can you tell me the line to again and I can add it and run another and watch what happens beween BD rb and the dos open window.

Yes the 22% was on the current progress the overall was over 50% but nothing was updating.

Capsbackup
6th September 2009, 23:25
i remember in one of the post there was a line you could add to bdrebuilder.ini that opened a dos window and you could see the progress there can you tell me the line to again and i can add it and run another and watch what happens beween bd rb and the dos open window.

Yes the 22% was on the current progress the overall was over 50% but nothing was updating.

show_encoder=1

Sophocles
7th September 2009, 00:02
Was that also on v0.29.1? Did you get any kind of error message in the log?

Sorry should have posted that it was on the previous version. Was this an issue that was recently fixed?

meatwad
7th September 2009, 01:06
Just running 29.01 and it's progress bar stopped at 50% but appears that it's still running according to the CPU. Is there anyway to tell the progress if it the progress bar stops.


I found that if CoreAVC 1.9.5 is your default H264 decoder you'll experience symptoms like these. Check and see if CoreAVC is doing the decoding instead of FFDshow. I've experienced lock-ups of other running programs when this happens as well. It might possibly be due to having CUDA acceleration enabled, but I never did any further troubleshooting once I found out what was causing it on my system.

writersblock29
7th September 2009, 01:36
Windows XP X64 here. I can confirm that the progress bars aren't reporting back in real time; it's sporatic at best. Some streams, both bars read fine... then it'll hit a spot where both bars appear to freeze. Task manager still reports the CPU's being taxed. Framerate and frames encoded information also freezes.

I did Bee Movie last night, and when I noticed the behavior, I left it alone all night. The result was a completed project when I checked it this morning: And both bars showed 100% completion. I'm working on Braveheart, Disk One now, and six hours into it, it's showing an overall progress of .18% with no activity on the current progress bar. I'm betting that leaving it alone will result in completion, but point being, the progress bars aren't reporting accurately here, either.

To my recollection, earlier versions worked fine--but I won't swear to that, since I usually start projects in the evening, and ignore the computer until I wake up the following day. That, and I've been using Windows 7 RC right up until two days ago, when I re-installed XP X64. So I really hate to report anything on any platform that's A) Not yet supported, B) Itself, still in beta, and C) different than the environment I'm using now and noticing strange behavior on.

[Edit] A half an hour from posting this, I checked BDRB again out of curriousity. 54% overall, 13% current, with framerate info and encoded frames info going strong. So it jumped from .18% to 54% in a half an hour.

Also, this is using FFdshow as the decoder.

meatwad
7th September 2009, 02:31
Windows XP X64 here. I can confirm that the progress bars aren't reporting back in real time; it's sporatic at best. Some streams, both bars read fine... then it'll hit a spot where both bars appear to freeze. Task manager still reports the CPU's being taxed. Framerate and frames encoded information also freezes.

I did Bee Movie last night, and when I noticed the behavior, I left it alone all night. The result was a completed project when I checked it this morning: And both bars showed 100% completion. I'm working on Braveheart, Disk One now, and six hours into it, it's showing an overall progress of .18% with no activity on the current progress bar. I'm betting that leaving it alone will result in completion, but point being, the progress bars aren't reporting accurately here, either.

To my recollection, earlier versions worked fine--but I won't swear to that, since I usually start projects in the evening, and ignore the computer until I wake up the following day. That, and I've been using Windows 7 RC right up until two days ago, when I re-installed XP X64. So I really hate to report anything on any platform that's A) Not yet supported, B) Itself, still in beta, and C) different than the environment I'm using now and noticing strange behavior on.

[Edit] A half an hour from posting this, I checked BDRB again out of curriousity. 54% overall, 13% current, with framerate info and encoded frames info going strong. So it jumped from .18% to 54% in a half an hour.

Also, this is using FFdshow as the decoder.

So it's not CoreAVC? I've done two movies with 0.29.01 and haven't experienced this yet (using Windows 7 X86). Anyway, I'm sure J. Dobbs will get to the bottom of this for those that are experiencing this issue.

writersblock29
7th September 2009, 03:15
@Meatwad

At least in my case, no, it's not CoreAVC. I do own it, but haven't used or even installed it on this system. The projects do complete if left alone--and to keep checking back on a project that's "frozen," you'll sometimes see that it's frozen at a different spot than it was before. The disk I'm running now, Braveheart Disk One, went from locked up to running fine (it's chewing on the main feature now)... but I doubt the process of doing the work was interupted at all when the progress bars weren't operational. Bee Movie, last night, didn't seem to take any longer than a normal project. My daughter's watching it right now on our HTPC, and it's working fine.

jdobbs
7th September 2009, 03:28
@Meatwad

At least in my case, no, it's not CoreAVC. I do own it, but haven't used or even installed it on this system. The projects do complete if left alone--and to keep checking back on a project that's "frozen," you'll sometimes see that it's frozen at a different spot than it was before. The disk I'm running now, Braveheart Disk One, went from locked up to running fine (it's chewing on the main feature now)... but I doubt the process of doing the work was interupted at all when the progress bars weren't operational. Bee Movie, last night, didn't seem to take any longer than a normal project. My daughter's watching it right now on our HTPC, and it's working fine.Just brainstorming... have you changed the default priority?

writersblock29
7th September 2009, 03:36
Just brainstorming... have you changed the default priority?

No. When I was using Windows 7, I had to in order to get BDRB to work on it, but I've reinstalled Windows XP X64 two days ago. When installing FFdshow, I pretty much left everything to defaults other than enabling Mpeg2 and using the MT codec for H264.

jdobbs
7th September 2009, 03:40
Sorry should have posted that it was on the previous version. Was this an issue that was recently fixed? Yes. In v0.29.1 I rewrote the routine that collects the window's handle so it uses EnumWindows()...

This is a new issue completely. Now it never fails to collect the handle (or there would be an error report in the log) -- but for some reason it's not getting updates from the X264 window's caption at some point during the encode.

It's working 100% for me on Windows Vista.

Capsbackup
7th September 2009, 03:48
Yes. In v0.29.1 I rewrote the routine that collects the window's handle so it uses EnumWindows()...

This is a new issue completely. Now it never fails to collect the handle (or there would be an error report in the log) -- but for some reason it's not getting updates from the X264 window's caption at some point during the encode.

It's working 100% for me on Windows Vista.

Just to confirm, its working fine for me too, with XP Pro 32bit.
Both BD-RB's and x264's display are advancing/progressing congruently together, both on screen or when minimized.

prospeed
7th September 2009, 07:20
Same reported issue regarding progress bar updating..
x264.exe running fine. About 2.25hrs into job.

Pass 1/2 - Speed:0.0x - ETA: 00:00:00 - FPS:0.00
Frames: 000000 / 000000

PurpleMan
7th September 2009, 09:43
jdobbs,

I have reported this issue before, but never got a reply.

When doing titles that have seamless branching (disney titles, for instance), or in my case - Gladiator (original disc this time), in which the main movie is split across like 50 different m2ts's, the BD25 backup (complete backup) often shows a slight pause during playback in parts where there's a file-change.

For example, in Gladiator theatrical cut, PowerDVD7 completely hangs at the scene-change (and file-change) at around 1 hour 34 minutes, while PowerDVD9 shows a slight pause (less than 1 second) then resume playing.

This *might* be a powerdvd issue, but then again - it might not be.

You have any idea why this would/should happen?

PurpleMan
7th September 2009, 10:07
Also, another question.

I noticed that secondary audio (dd+) is usually mapped to track 6656 on original m2ts's (I suppose this signifies that it's a secondary audio stream), but on the bd25 backup, they are mapped to 435x (like primary audio tracks).

Is this on purpose?

DK
7th September 2009, 10:16
Concerning the "freezing issue" when jumping a chapter forward or backward I had problems with "Swing Vote" and 28.04 but I do NOT have this problem with 29.01 - at least not after re-doing Swing Vote.

Attached you may find log, inf, index.bdmv and movieobject.bdmv of both conversions in case it may be useful.

Thanx for all the effort!

BZeeme
7th September 2009, 10:59
BD Rebuilder v0.29.01 (beta)

This is the 1st version that properly did a movie-only backup of CJ7!
With other versions the backup would play until I jumped to a different chapter - then the video would turn to garbage (audio and subtitles were fine).

jdobbs
7th September 2009, 13:49
Also, another question.

I noticed that secondary audio (dd+) is usually mapped to track 6656 on original m2ts's (I suppose this signifies that it's a secondary audio stream), but on the bd25 backup, they are mapped to 435x (like primary audio tracks).

Is this on purpose?Not on purpose -- but the only way TSMUXER will do it. It plays back correctly...

jdobbs
7th September 2009, 13:52
jdobbs,

I have reported this issue before, but never got a reply.

When doing titles that have seamless branching (disney titles, for instance), or in my case - Gladiator (original disc this time), in which the main movie is split across like 50 different m2ts's, the BD25 backup (complete backup) often shows a slight pause during playback in parts where there's a file-change.

For example, in Gladiator theatrical cut, PowerDVD7 completely hangs at the scene-change (and file-change) at around 1 hour 34 minutes, while PowerDVD9 shows a slight pause (less than 1 second) then resume playing.

This *might* be a powerdvd issue, but then again - it might not be.

You have any idea why this would/should happen?Definitely a PowerDVD issue IMHO... it doesn't seem to be buffering enough to account for the delay associated with switching to a new file.

drmih
7th September 2009, 13:56
Not on purpose -- but the only way TSMUXER will do it. It plays back correctly...

Has there been any further developments on the other types of Secondary Audio (PiP) as that seems to be on the majority of discs?

PurpleMan
7th September 2009, 13:59
Definitely a PowerDVD issue IMHO... it doesn't seem to be buffering enough to account for the delay associated with switching to a new file.

Well, considering I'm playing it from a mounted ISO file, I'd reckon it doesn't take my HD a complete second to read another file.

Mentioning again that on PowerDVD7 it hangs altogether (doesn't resume playing even after many seconds).

jdobbs
7th September 2009, 14:07
Well, considering I'm playing it from a mounted ISO file, I'd reckon it doesn't take my HD a complete second to read another file.

Mentioning again that on PowerDVD7 it hangs altogether (doesn't resume playing even after many seconds). C'mon. I'm not going to argue about it... no other reports and PowerDVD only? Seems straightforward to me. Threre's really nothing I can do about bugs in PowerDVD.

jdobbs
7th September 2009, 14:08
Has there been any further developments on the other types of Secondary Audio (PiP) as that seems to be on the majority of discs? Not yet. The only way I can think of to support it is to demux and remux myself... and thats no small task.

PurpleMan
7th September 2009, 14:44
C'mon. I'm not going to argue about it... no other reports and PowerDVD only? Seems straightforward to me. Threre's really nothing I can do about bugs in PowerDVD.

I'm not arguing, I'm contemplating the idea. We're on the same side here :).

I just figured that if this was a PowerDVD issue, it would have been apparent on the original disc too, wouldn't it?

Since it's not, it should indicate that something is different on the backup up disc. Unless my logic is wrong here.

Capsbackup
7th September 2009, 15:43
I use PowerDVD 7.3, and my full movie backup to BD-25 has an ever so slight hesitation with Gladiator at 1:34:04, no freezing, and continues playing. However, when I play it back on my Sony BX1, it is hardly noticeable, but reminds me of a slight pause that is sometimes associated with a layer change when watching a DVD DL movie.
To me, this is extremely hard to detect, and if you blink, you would miss it. The original does seem to avoid this at this same location. This is not a concern to me though.

jdobbs
7th September 2009, 16:05
I've just updated the link on the first post of this thread with a new version of BD-RB (v0.29.02). The changes for this release are:- 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.

daberti
7th September 2009, 18:29
I've just updated the link on the first post of this thread with a new version of BD-RB (v0.29.02). The changes for this release are:- 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.

Just asking, but when will it be fixed the subtitles' error when encoding in 720p?

TIA

jdobbs
7th September 2009, 20:14
Just asking, but when will it be fixed the subtitles' error when encoding in 720p?

TIACan you give me a title for which it fails? The ones I've tested work fine.

worknstiff
7th September 2009, 20:14
:thanks: JDobbs for President! No Wait JDobbs for Master of the Universe! Besides the frozen status on RBLD 29.01, it still turned out an excellent copy of Watchmen in a high quality (slow) Movie Only BD9 encode that has fixed the FF/Chapter seek problem. It also picked out the correct playlist and not the longer Director's commentary movie, and produced a copy that is identical (on my 50in plazma using my 50+ eyes ) with the original. What more can I say! I think he has produced the holy grail of BD movie backup, the crown for the BD_DVDShrink if you will. I think there is lots of stuff going on with the Full Disk & PNP and java stuff that will be a pain but thats not what I am after. I have had Watchmen lying around with dust accumulating on it and the 3 duds I had previously burned for weeks and can finally put it away.
Thanks-Again JDobbs and soon as Paypal gets my deposit look for another donation for the great program.

Sharc
7th September 2009, 20:54
Can you give me a title for which it fails? The ones I've tested work fine.
Some titles work fine, some do not. One I had which did not work was PERFUME: The Story of a Murderer, Region B.
(I could give you more titles if it helps, all are Region B, however).

PurpleMan
7th September 2009, 21:34
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.

daberti
7th September 2009, 21:59
Can you give me a title for which it fails? The ones I've tested work fine.

http://forum.doom9.org/showpost.php?p=1305325&postcount=3936

Title is Black Hawk Down (Region B)

GaPony
8th September 2009, 04:10
Maybe you Region B guys should send jdobbs your problematic movies... Consider it a sacrifice to science. :)

stackner
8th September 2009, 05:16
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.

setarip_old
8th September 2009, 06:43
@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?

allright
8th September 2009, 06:59
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.

Groucho2004
8th September 2009, 09:45
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.

Are you using "SHOW_ENCODER=1" in your ini file?