BD Rebuilder Beta - Bug Reports Only

[Wizzu]

Been some time without compressing blu-rays, so I just discovered all the improvements you brought to BD-RB since the last time I used it.

Thanks! :)

I particularly appreciate the improved Quick-play feature (actually naming the features? That's GREAT!) and the correction "of an issue that might prevent AVCHD output from playing on certain players" (it was the case with my Panasonic BD-75 and it prevented me to use Quick-play).

Kudos. Another donation is pending. :cool:

[laserfan]

I will tell you, indeed it does require a special burner, which I have it. Since they have no dye layer on disc, a high power laser is used to engrave data on disc surface.

Just for info this is how disc looks, notice how transparent are they.
http://i60.tinypic.com/10idzzm.gif
Very off-topic, so maybe jdobbs you can/will move these posts, but in honor of World Backup Day I ordered some VERY recently released BD-R M-Discs and a burner.

I suppose these discs at ~$5 bucks a pop will be useful for priceless family videos or something, but IMO not for backups of commercial movies. I'm gonna use them for data backups--literally these discs etch-in-stone and last 1000 years.

[colinhunt]

I'll also try blanking something and see what happens. I'm just trying to get the basic 3D bugs out of the way first.
Well, when you're right, you're right. The job finished without errors when no items were blanked. Howeverrrrr... based on PowerDVD 13 OSD, all video on disc is MVC (haven't checked the original for that yet) and the main movie looks like it's 2D, not 3D - even though PDVD says the video is MVC.

One unfortunate result of ditching SSIF is that I can no longer check the output on Stereoscopic Player. PowerDVD can display MVC as red/cyan anamorphic, which is what I used on Stereoscopic Player, but I don't trust PDVD like I do SSP.

I'll burn the output on a BD-RE and check it on a stand-alone player.

[jdobbs]

Well, when you're right, you're right. The job finished without errors when no items were blanked. Howeverrrrr... based on PowerDVD 13 OSD, all video on disc is MVC (haven't checked the original for that yet) and the main movie looks like it's 2D, not 3D - even though PDVD says the video is MVC.

One unfortunate result of ditching SSIF is that I can no longer check the output on Stereoscopic Player. PowerDVD can display MVC as red/cyan anamorphic, which is what I used on Stereoscopic Player, but I don't trust PDVD like I do SSP.

I'll burn the output on a BD-RE and check it on a stand-alone player.PowerDVD sucks. I have it too. Try it on a standalone player.

If Stereoscopic Player is BD compatible -- it should play these discs. If it doesn't the problem is with the player.

As for all the content being MVC -- that's ok. Stereoscopic playback only differs from 3D by the existence of the MVC stream (either in-mux or out-of-mux) which has a reserved PID. The MVC stream is separated from the 2D video and is accessed through extensions in the MPLS and CLPI files. So a 2D player simply ignores it (because it doesn't look for the extensions).

[colinhunt]

If Stereoscopic Player is BD compatible
It's not, but it can open an SSIF file directly. It can't open stereo .m2ts files like the ones BDRB now outputs :/

As for all the content being MVC -- that's ok. Stereoscopic playback only differs from 3D by the existence of the MVC stream (either in-mux or out-of-mux) which has a reserved PID. The MVC stream is separated from the 2D video and is accessed through extensions in the MPLS and CLPI files. So a 2D player simply ignores it (because it doesn't look for the extensions).
Yeah. My puzzlement with PDVD was caused by the fact that PDVD shows commercial/original 3D Blu-ray titles properly, with depth, as red/cyan anaglyph 3D. But there's no separation, no depth, in the BDRB output I tested just now. Granted, it could easily be a problem with PDVD. I'll be much wiser once the BD-RE disc is done and I get to try it on a stand-alone.

[jdobbs]

It's not, but it can open an SSIF file directly. It can't open stereo .m2ts files like the ones BDRB now outputs :/


Yeah. My puzzlement with PDVD was caused by the fact that PDVD shows commercial/original 3D Blu-ray titles properly, with depth, as red/cyan anaglyph 3D. But there's no separation, no depth, in the BDRB output I tested just now. Granted, it could easily be a problem with PDVD. I'll be much wiser once the BD-RE disc is done and I get to try it on a stand-alone.If you want it to play them with Stereoscopic Player do this:

1. Add FORCE_INMUX_3D=1 to your INI file. This is a special case setting I added that tells BD-RB to only use in-mux MVC in the output (a single M2TS). Note: The component parts of ALL multi-part playlists are encoded as in-mux MVC regardless of this setting. This is necessary for playback continuity.

2. See if Stereoscopic Player recognizes it as 3D and plays it. An in-mux M2TS is structured exactly like an SSIF.

3. If that doesn't work, you can rename them to SSIF and play them (but DON'T leave them that way -- as a BD player won't recognize them unless they have the M2TS extension).

The discs that I have done in testing will play back as anaglyph in PowerDVD 11. Sometimes it's hard to tell -- but you see the color shift.

[colinhunt]

^ Thanks, I'll give it a shot!

[J666RST]

@ colinhunt & jdobbs I have a 3D laptop, did a full backup of Brave which works fine in 3D on my Panasonic stand alone. Playing it on my laptop in 2D works fine but when played in 3D you see random blocks appearing in the 3D image.

[jdobbs]

@ colinhunt & jdobbs I have a 3D laptop, did a full backup of Brave which works fine in 3D on my Panasonic stand alone. Playing it on my laptop in 2D works fine but when played in 3D you see random blocks appearing in the 3D image.If it plays back fine on the standalone, then the issue has to be in the player.

You may want to also try FORCE_INMUX_3D=1. It's possible a questionable player might have issues with the disc access time/coordination required for out-of-mux 3D (the AVC & MVC streams exist in two different M2TS files).

The only downside to using in-mux 3D is a few minutes of added processing time because BD-RB has to scan the output and create the CLPI itself. It generally adds 5-10 minutes or so. That's the only reason I didn't make it the default. But if others have issues, I may do that on the next release.

Another note: You don't have to do the entire reencode to take advantage of FORCE_INMUX_3D if you still have the working folder. That flag affects the REBUILD only.

[J666RST]

If it plays back fine on the standalone, then the issue has to be in the player.

You may want to also try FORCE_INMUX_3D=1. It's possible a questionable player might have issues with the disc access time required for out-of-mux 3D.

The only downside to using INMUX 3D is a few minutes of added processing time because BD-RB has to scan the output and create the CLPI itself.

Another note: You don't have to do the entire reencode to take advantage of FORCE_INMUX_3D if you still have the working folder. That flag affects the REBUILD only.

Will try that, will have to do a full reencode again. Will let you know in a few hours! BTW the player used is Toshibas own software blu ray player.

[colinhunt]

Ohh-kay, first playback test on a stand-alone player: everything appears to be working and the main movie plays in proper 3D. BUT! The BD drive is making one hell of a racket - it's seeking constantly, apparently reading data from two separate files and making a nasty noise while jumping back and forth between them.

This, I'm guessing, is due to out-of-mux 3D, with main and dependent view data split into two physically separate files on disc. To be perfectly honest, I'm not a fan of this solution, even though it appears to be working fine and so far I haven't noticed any stuttering or skipping in the movie.

I'm very glad jdobbs included the INMUX option :) - which I'm testing next.

[colinhunt]

Test #1 of the mux-in-3D version of Deep Water 3D: PowerDVD 13 plays it without issues - and red/cyan anaglyph 3D has separation and depth. So far, so good. Burning data on BD-RE next for testing on a stand-alone.

[Starfiresg1]

I did a full backup of Man of Steel to BD25 without blanking etc.. There were no issues during encoding. The resulting disc played fine in TMT and my standalone Panasonic.
I currently have a job of Jurassic Park running - its about 80 percent done.

[AmigaFuture]

@jdobbs

I updated my previous post.

[Rich86]

When converting a BD movie to DVD, selecting a subtitle to be forced on does not work.
Example = "The Book Thief" blu-ray.
The 1st subtitle is regular english. The last is forced english subtitles.
I selected both english subtitles to be included in the conversion, and clicked 2nd english subtitle to be forced on, and ran BDRB.
Both subtitles were converted, but the 2nd english subtitle was not forced on.
Workaround: use PGCEdit to open up the output DVD on hard disc and insert a "setstn" command to force the 2nd english subtitle on.

[colinhunt]

Yes! Excelsior! The in-mux-3D version plays nicely on a stand-alone - and there are no extraneous seeking noises coming from the drive!

Furthermore, Stereoscopic Player is A-OK with in-muxed .m2ts files, and there's even no need to rename them to SSIF :D

[jdobbs]

Ohh-kay, first playback test on a stand-alone player: everything appears to be working and the main movie plays in proper 3D. BUT! The BD drive is making one hell of a racket - it's seeking constantly, apparently reading data from two separate files and making a nasty noise while jumping back and forth between them.

This, I'm guessing, is due to out-of-mux 3D, with main and dependent view data split into two physically separate files on disc. To be perfectly honest, I'm not a fan of this solution, even though it appears to be working fine and so far I haven't noticed any stuttering or skipping in the movie.

I'm very glad jdobbs included the INMUX option :) - which I'm testing next.It is in the standard... so the player is REQUIRED to play it. If it makes noise, it is a fault in the player. My Sony player takes it in stride.

Sorry -- but that is a fact. With that said, though, I'll probably cause fewer headached for myself if I make in-mux the default in the next release.

[jdobbs]

When converting a BD movie to DVD, selecting a subtitle to be forced on does not work.
Example = "The Book Thief" blu-ray.
The 1st subtitle is regular english. The last is forced english subtitles.
I selected both english subtitles to be included in the conversion, and clicked 2nd english subtitle to be forced on, and ran BDRB.
Both subtitles were converted, but the 2nd english subtitle was not forced on.
Workaround: use PGCEdit to open up the output DVD on hard disc and insert a "setstn" command to force the 2nd english subtitle on. Hmm... I didn't think of that when I wrote the conversion software. I'll look into forcing them.

[jdobbs]

Yes! Excelsior! The in-mux-3D version plays nicely on a stand-alone - and there are no extraneous seeking noises coming from the drive!

Furthermore, Stereoscopic Player is A-OK with in-muxed .m2ts files, and there's even no need to rename them to SSIF :DCool.

[colinhunt]

It is in the standard... so the player is REQUIRED to play it. If it makes noise, it is a fault in the player.
It's not really a fault, it's just regular seeking noise created by the motors. It's only noticeable because the drive is seeking constantly.

[jdobbs]

@jdobbs

I updated my previous post.Thanks.

[colinhunt]

Cool.
Oh, very much so. There's another donation coming your way soonish to celebrate this milestone :)

When you begin fine-tuning, looking into blanking etc., could you please give the sizing algorithms another look? It seems that currently encodes come out 1.5 gigabytes too small when Output target is BD-25. I just finished another test run of Khumba 3D, and even with a silly Custom target size of 24550MB, it came out 1.5GB short of a full disc.

[Ch3vr0n]

Well it's chugging along at 6-8fps on my rig on w7, question though jdobbs qly chance you could implement cuda encoding to speed things up at least a little for users like me that do not have an i-series rig to use quicksync?

Verstuurd vanaf mijn Nexus 7 met Tapatalk

[colinhunt]

Some info I saw on Nvidia's Whitepaper on Kepler GPUs:

"All Kepler GPUs also incorporate a new hardware-based H.264 video encoder, NVENC. Prior to the introduction of Kepler, video encoding on previous GeForce products was handled by encode software running on the GPU’s array of CUDA Cores. While the CUDA Cores were able to deliver tremendous performance speedups compared to CPU-based encoding, one downside of using these high-speed processor cores to process video encoding was increased power consumption. By using specialized circuitry for H.264 encoding, the NVENC hardware encoder in Kepler is almost four times faster than our previous CUDA-based encoder while consuming much less power.

It is important to note that an application can choose to encode using both NVENC hardware and NVIDIA’s legacy CUDA encoder in parallel, without negatively affecting each other. However, some video pre-processing algorithms may require CUDA, and this will result in reduced performance from the CUDA encoder since the available CUDA Cores will be shared by the encoder and pre-processor. NVENC provides the following:

Can encode full HD resolution (1080p) videos up to 8x faster than real-time. For example, in high performance mode, encoding of a 16 minute long 1080p, 30 fps video will take approximately 2 minutes.
Support for H.264 Base, Main, and High Profile Level 4.1 (same as Blu-ray standard)
Supports MVC (Multiview Video Coding) for stereoscopic video—an extension of H.264 which is used for Blu-ray 3D.
Up to 4096x4096 encode"

So if I read that right, NVENC can accelerate MVC encoding as well.

My apologies for going off-topic :/

[cartman0208]

Hi guys,

I hope, one of you can help me.

I've been using BD Rebuilder for quite a while now, but since some weeks or so I'm experiencing problems:
Usually I reencode audio to ac3 because I mostly do BD9 encodes.
But reencoded audio plays with like a tenth of original speed.

I probably did something wrong with my system and I know its not necessarily a BD-Rebuilder issue but maybe one of you can pinpoint me to the direction, what could be wrong here.

- Windows Version: 6.1 [7601]
- AVISYNTH Version: [2.5.8.0], Ok
- HAALI Splitter: [1.9.42.1], Ok
- FFDSHOW: [4504], Ok
- WIN7 preferred AVC CODEC: Ok
- WIN7 preferred VC-1 CODEC: Ok
- WIN7 preferred MPEG2 CODEC: Ok
- FFDSHOW VC-1 set to "wmv9", Ok
- FFDSHOW MPEG2 set to "libavcodec": Ok
- FFDSHOW AVC set to "libavcodec": Ok
- AnyDVD settings check: Ok.
- BD-RB v0.46.0.14, not current

Don't know why it says "not current", I just downloaded it from the website.
Never mind, I just found the inspect inside BDRB:
Checking System Settings
- BD-Rebuilder v0.46.14 (beta)
- Windows Version: 6.1 [7601]
- Working Path Free Space: 359,62GB
- AVISYNTH Version: 2.5.8.0, Ok
- HAALI Splitter: 1.9.42.1, Ok
- FFDSHOW: 4504, Ok
- WIN7 preferred AVC CODEC: Ok
- WIN7 preferred VC-1 CODEC: Ok
- WIN7 preferred MPEG2 CODEC: Ok
- FFDSHOW VC-1 set to "wmv9", Ok
- FFDSHOW MPEG2 set to "libavcodec": Ok
- FFDSHOW AVC set to "libavcodec": Ok
- AnyDVD settings check: Ok.
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[03.31.14] Systems Settings Check complete


Thanks for this great product!

[jdobbs]

Well it's chugging along at 6-8fps on my rig on w7, question though jdobbs qly chance you could implement cuda encoding to speed things up at least a little for users like me that do not have an i-series rig to use quicksync?

Verstuurd vanaf mijn Nexus 7 met TapatalkRight now there is only one freeware choice for MVC encoding... and its core code was written by Intel. Actually it's a pretty smart move -- it makes you wonder how NVidia let themselves get behind.

I know it has me wondering if I may want to buy an i7 processor...

[DMagic1]

Just completed Frozen and all went well. Size was perfect. No playback issue noticed.

On a side note, can want ever flag is used to stop playback if the tv isn't 3D be removed? This isn't a problem with movie only but in full backup it is. I'd like for the disc to be playable in 2D on my other 3D player that isn't connected to a 3D tv.

[jdobbs]

Just completed Frozen and all went well. Size was perfect. No playback issue noticed.

On a side note, can want ever flag is used to stop playback if the tv isn't 3D be removed? This isn't a problem with movie only but in full backup it is. I'd like for the disc to be playable in 2D on my other 3D player that isn't connected to a 3D tv.It's interesting. All 3D discs will play on 2D players. The standard was designed to assure downward compatibility. But, for some reason, some of the authors put checks in and require a 3D player and monitor. I think it is to make it necessary for consumers to buy either two discs, or to make you pay more for the 2D/3D/DVD set.

Unfortunately, the checks are done in either JAVA or via command sequences. So there's really no reasonable way to prevent it. That's one of the reasons I'm considering removing the "ignore 3D" option. On those discs you can still get the "can't play" message.

[Ch3vr0n]

Jdobbs, i don't mind paying a little if it'll do what i want it too. Perhaps neuron2 can help you in that endeavour. As afaik he has experience with cuda due to his dgdecnv. I'd be happy to pay $15 rather than a new system entirely. As for a new processor I'd need a new motherboard, which triggers new ram etc as my current mono doesn't support the i-series. It uses socket lga775. Other than that its currently estimated just over 6hrs for a full 45gb disc. Can't say that that's too bad.

Verstuurd vanaf mijn Nexus 7 met Tapatalk

[DMagic1]

It's interesting. All 3D discs will play on 2D players. The standard was designed to assure downward compatibility. But, for some reason, some of the authors put checks in and require a 3D player and monitor. I think it is to make it necessary for consumers to buy either two discs, or to make you pay more for the 2D/3D/DVD set.

Unfortunately, the checks are done in either JAVA or via command sequences. So there's really no reasonable way to prevent it. That's one of the reasons I'm considering removing the "ignore 3D" option. On those discs you can still get the "can't play" message.

I've only know one software(you can probably guess which) that partially disabled this check. It would play just as long as the player was 3D. The TV didn't have to be. So it seem the 3D player is needed probably to show menus properly but the TV part of it isn't. It would be nice to know how that was done.

[jdobbs]

Jdobbs, i don't mind paying a little if it'll do what i want it too. Perhaps neuron2 can help you in that endeavour. As afaik he has experience with cuda due to his dgdecnv. I'd be happy to pay $15 rather than a new system entirely. As for a new processor I'd need a new motherboard, which triggers new ram etc as my current mono doesn't support the i-series. It uses socket lga775. Other than that its currently estimated just over 6hrs for a full 45gb disc. Can't say that that's too bad.

Verstuurd vanaf mijn Nexus 7 met TapatalkI'm sure Nvidia will do decoding of 3D -- but I haven't heard anything about MVC encoding.

[jdobbs]

I've only know one software(you can probably guess which) that partially disabled this check. It would play just as long as the player was 3D. The TV didn't have to be. So it seem the 3D player is needed probably to show menus properly but the TV part of it isn't. It would be nice to know how that was done. There's a register in the player that can be set with commands that indicates whether the display can handle 3D. But the other important ones related to 3D are read-only. I would think you'd still have problems -- as the player would try to send a signal to the TV that is out of its capability.

The only way you could do it right would be to have a JAVA and/or command sequence interpreter that would simulate the player and look for places where the 3D registers are being read -- and it would then have to change the code during backup... but that's not practical at all.

[Ch3vr0n]

Perhaps you could contact them or neuron2. That's all i can ask, until i can find the funds for a new system. Been wanting one for a while anyway. Until you find a way, the current one will do just fine. Finally a real solution and alternative for users not wanting to relying on (in my view crappy) dvdfab/blufab

Verstuurd vanaf mijn Nexus 7 met Tapatalk

[DMagic1]

There's a register in the player that can be set with commands that indicates whether the display can handle 3D. But the other important ones related to 3D are read-only. I would think you'd still have problems -- as the player would try to send a signal to the TV that is out of its capability.

The only way you could do it right would be to have a JAVA and/or command sequence interpreter that would simulate the player and look for places where the 3D registers are being read -- and it would then have to change the code during backup... but that's not practical at all.

Could that register command setting be included as a hidden option to see how it pans out?

[Ch3vr0n]

So Top Gun 3D just finished succesfully, but with a downside. Using the default settings (no frim switches, no mux metho switches), PDVD 11 only displayed the menu in 3D, not the movie itself. I verified against the original and that one was properly displayed in 3D. will rerunning the job but this time with the FORCE_INMUX_3D=1 option make a difference? As i do not have a standalone PDVD 11 will have to suffice for now as i don't have any friends with 3D hardware.

I would love to get some recommendations for 3D standalone players though but in my pm box only as to not go offtopic. 2 requirements: either panasonic/LG and licensed pre feb 1st 2012 (want to avoid cinavia ;) i'll then go on a hunt to see where i can find one in BE, NL and/or FR)

[colinhunt]

will rerunning the job but this time with the FORCE_INMUX_3D=1 option make a difference?
It certainly did for me. Out-of-mux 3D version played in 2D on PDVD, but in-mux-3D played in 3D. This leads me to think that PDVD does not understand/support out-of-mux 3D.

[colinhunt]

I know it has me wondering if I may want to buy an i7 processor...
If you do start shopping for an i7, do keep in mind that not all of them have internal GPUs. The fastest CPU I have is the i7-3930K which belongs to Intel's "High End Desktop" series of i7 CPUs, and none of the CPUs in that series have a GPU.

[Ch3vr0n]

The one i had my eye set on before a financial setback prevented me from purchasing the rig i had configured was the i7-3770k, think that one did have the untenable gpu

@Colin: i wonder why the menu was in 3d then though.
Verstuurd vanaf mijn Nexus 7 met Tapatalk

[colinhunt]

@Colin: i wonder why the menu was in 3d then though.
I bet that's processed somehow differently, because in my out-of-mux test menu was also in 3D, but the movie was in 2D.

[montana72]

I don't understand what you are saying.

Sorry my English.

In the new version, said, although the output size is 25 gigabytes of disk, the programe re-encoded. If I put 50 gigabytes of output size, do not return to encodes and the result is less than 25, because the program does not detect that you don't have to re-encode because it fit on a BD-25?

Thanks a lot.

[Starfiresg1]

I can conform that Power DVD 11 seems to have issues with out-of-mux-3D. I loaded my Disc from yesterday (Man of Steel) up in Power DVD for a quick red/cyan-test. While the 3D controls are enabled and you get the color shift when enabling red/cyan output the movie doesn't show any depth whatsoever.
The same disc plays fine in my standalone Panasonic and in Arcsoft TMT6.

[colinhunt]

I can conform that Power DVD 11 seems to have issues with out-of-mux-3D. I loaded my Disc from yesterday (Man of Steel) up in Power DVD for a quick red/cyan-test. While the 3D controls are enabled and you get the color shift when enabling red/cyan output the movie doesn't show any depth whatsoever.
The same disc plays fine in my standalone Panasonic and in Arcsoft TMT6.
Thanks for the confirmation!

[jdobbs]

The one i had my eye set on before a financial setback prevented me from purchasing the rig i had configured was the i7-3770k, think that one did have the untenable gpu

@Colin: i wonder why the menu was in 3d then though.
Verstuurd vanaf mijn Nexus 7 met TapatalkI think I'll stick with what I have. Those i7s are really expensive. My AMD FX-8350 gets about 9-10.5fps for MVC encodes, and I can live with that. A 2 hour movie takes a little less than 5 hours.

Menus are almost always multipart. Multipart sources are always done in-mux.

I'm making in-mux MVC the default in the next release.

[jdobbs]

I can conform that Power DVD 11 seems to have issues with out-of-mux-3D. I loaded my Disc from yesterday (Man of Steel) up in Power DVD for a quick red/cyan-test. While the 3D controls are enabled and you get the color shift when enabling red/cyan output the movie doesn't show any depth whatsoever.
The same disc plays fine in my standalone Panasonic and in Arcsoft TMT6. Without a doubt the issue is PowerDVD, not BD-RB. I can't fix, and can't take responsibility for PowerDVD's problems. So I'd suggest anyone having that issue post it on THEIR forum.

But, as I said, I am making in-mux the default. This kind of thing is exactly why I limited the release of v0.47.3 -- to pick up anomalies the happen in the real world that aren't necessarily "bugs".

[colinhunt]

Without a doubt the issue is PowerDVD, not BD-RB.
I don't think anyone's pointing the finger at BD-RB here :)

[jdobbs]

I don't think anyone's pointing the finger at BD-RB here :)I appreciate people posting their experiences, even if it isn't a bug. That's how the software improves. I just want to be clear what is and isn't a problem in BD-RB

[rusty666]

when will it be posted @jobbs .

[rusty666]

@ jdobbs i ment

[jdobbs]

when will it be posted @jobbs .I'm not sure. I also have to make changes to movie-only rebuilds so they use in-mux, and it isn't as simple since BD-RB will have to create the BD structure in addition to CLPI. In the meantime the FORCE_INMUX_3D option works.

[wakko709]

[03/30/14] BD Rebuilder v0.46.14 (beta)
[20:42:15] Source: THE_ODD_LIFE_OF_TIMOTHY_GREEN
- Input BD size: 39.99 GB
- Approximate total content: [02:27:53.489]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- Auto Quality: Good (Very Fast), ABR
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[20:42:20] PHASE ONE, Encoding
- [20:42:20] Processing: VID_00800 (1 of 20)
- [20:42:20] Extracting A/V streams [VID_00800]
- [21:02:14] Reencoding video [VID_00800]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 150,504 frames
- Bitrate: 20,301 Kbs
- [21:02:14] Reencoding: VID_00800, Pass 1 of 1
- [21:51:10] Video Encode complete
- [21:51:10] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [21:51:11] Multiplexing M2TS
- [21:56:26] Processing: VID_00875 (2 of 20)
- [21:56:26] Extracting A/V streams [VID_00875]
- [21:56:53] Reencoding video [VID_00875]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 2,992 frames
- Bitrate: 18,696 Kbs
- [21:56:53] Reencoding: VID_00875, Pass 1 of 1
- [21:59:26] Video Encode complete
- [21:59:26] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [21:59:26] Multiplexing M2TS
- [21:59:33] Processing: VID_00876 (3 of 20)
- [21:59:33] Extracting A/V streams [VID_00876]
- [22:01:08] Reencoding video [VID_00876]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 13,310 frames
- Bitrate: 18,506 Kbs
- [22:01:08] Reencoding: VID_00876, Pass 1 of 1
- [22:12:09] Video Encode complete
- [22:12:09] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [22:12:09] Multiplexing M2TS
- [22:12:30] Processing: VID_00877 (4 of 20)
- [22:12:30] Extracting A/V streams [VID_00877]
- [22:14:15] Reencoding video [VID_00877]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 14,689 frames
- Bitrate: 18,509 Kbs
- [22:14:15] Reencoding: VID_00877, Pass 1 of 1
- [22:26:24] Video Encode complete
- [22:26:24] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [22:26:24] Multiplexing M2TS
- [22:26:43] Processing: VID_00878 (5 of 20)
- [22:26:43] Extracting A/V streams [VID_00878]
- [22:26:48] Reencoding video [VID_00878]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 168 frames
- Bitrate: 6,674 Kbs
- [22:26:48] Reencoding: VID_00878, Pass 1 of 1
- [22:26:51] Video Encode complete
- [22:26:51] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [22:26:51] Multiplexing M2TS
- [22:26:55] Processing: VID_00879 (6 of 20)
- [22:26:55] Extracting A/V streams [VID_00879]
- [22:27:06] Reencoding video [VID_00879]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 954 frames
- Bitrate: 18,736 Kbs
- [22:27:06] Reencoding: VID_00879, Pass 1 of 1
- [22:27:55] Video Encode complete
- [22:27:55] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [22:27:55] Multiplexing M2TS
- [22:27:59] Processing: VID_00880 (7 of 20)
- [22:27:59] Extracting A/V streams [VID_00880]
- [22:28:04] Reencoding video [VID_00880]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 168 frames
- Bitrate: 6,674 Kbs
- [22:28:04] Reencoding: VID_00880, Pass 1 of 1
- [22:28:06] Video Encode complete
- [22:28:06] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [22:28:06] Multiplexing M2TS
- [22:28:10] Processing: VID_00881 (8 of 20)
- [22:28:10] Extracting A/V streams [VID_00881]
- [22:28:22] Reencoding video [VID_00881]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,145 frames
- Bitrate: 18,634 Kbs
- [22:28:22] Reencoding: VID_00881, Pass 1 of 1
- [22:29:19] Video Encode complete
- [22:29:19] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [22:29:19] Multiplexing M2TS
- [22:29:24] Processing: VID_00882 (9 of 20)
- [22:29:24] Extracting A/V streams [VID_00882]
- [22:29:28] Reencoding video [VID_00882]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 168 frames
- Bitrate: 6,674 Kbs
- [22:29:29] Reencoding: VID_00882, Pass 1 of 1
- [22:29:32] Video Encode complete
- [22:29:32] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [22:29:32] Multiplexing M2TS
- [22:29:35] Processing: VID_00883 (10 of 20)
- [22:29:35] Extracting A/V streams [VID_00883]
- [22:29:51] Reencoding video [VID_00883]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,583 frames
- Bitrate: 18,665 Kbs
- [22:29:51] Reencoding: VID_00883, Pass 1 of 1
- [22:31:08] Video Encode complete
- [22:31:08] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [22:31:08] Multiplexing M2TS
- [22:31:13] Processing: VID_00884 (11 of 20)
- [22:31:13] Extracting A/V streams [VID_00884]
- [22:31:18] Reencoding video [VID_00884]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 168 frames
- Bitrate: 6,674 Kbs
- [22:31:18] Reencoding: VID_00884, Pass 1 of 1
- [22:31:21] Video Encode complete
- [22:31:21] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [22:31:21] Multiplexing M2TS
- [22:31:24] Processing: VID_00885 (12 of 20)
- [22:31:24] Extracting A/V streams [VID_00885]
- [22:31:34] Reencoding video [VID_00885]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 790 frames
- Bitrate: 18,676 Kbs
- [22:31:34] Reencoding: VID_00885, Pass 1 of 1
- [22:32:12] Video Encode complete
- [22:32:12] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [22:32:12] Multiplexing M2TS
- [22:32:17] Processing: VID_00886 (13 of 20)
- [22:32:17] Extracting A/V streams [VID_00886]
- [22:32:21] Reencoding video [VID_00886]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 168 frames
- Bitrate: 6,674 Kbs
- [22:32:21] Reencoding: VID_00886, Pass 1 of 1
- [22:32:24] Video Encode complete
- [22:32:24] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [22:32:24] Multiplexing M2TS
- [22:32:27] Processing: VID_00887 (14 of 20)
- [22:32:27] Extracting A/V streams [VID_00887]
- [22:33:17] Reencoding video [VID_00887]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 6,749 frames
- Bitrate: 18,632 Kbs
- [22:33:17] Reencoding: VID_00887, Pass 1 of 1
- [22:37:17] Video Encode complete
- [22:37:17] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [22:37:17] Multiplexing M2TS
- [22:37:31] Processing: VID_00888 (15 of 20)
- [22:37:31] Extracting A/V streams [VID_00888]
- [22:37:41] Reencoding video [VID_00888]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,537 frames
- Bitrate: 9,583 Kbs
- [22:37:41] Reencoding: VID_00888, Pass 1 of 1
- [22:38:36] Video Encode complete
- [22:38:36] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [22:38:36] Multiplexing M2TS
- [22:38:41] Processing: VID_00890 (16 of 20)
- [22:38:41] Extracting A/V streams [VID_00890]
- [22:38:55] Reencoding video [VID_00890]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 2,668 frames
- Bitrate: 10,215 Kbs
- [22:38:55] Reencoding: VID_00890, Pass 1 of 1
- Encode failed. Aborting.
- BD-Rebuilder v0.46.14 (beta)
- Windows Version: 6.1 [7601]
- Working Path Free Space: 35.33GB
- AVISYNTH Version: 2.5.8.0, Ok
- HAALI Splitter: 1.9.42.1, Ok
- FFDSHOW: 4504, Ok
- WIN7 preferred AVC CODEC: Ok
- WIN7 preferred VC-1 CODEC: Ok
- WIN7 preferred MPEG2 CODEC: Ok
- FFDSHOW VC-1 set to "wmv9", Ok
- FFDSHOW MPEG2 set to "libavcodec": Ok
- FFDSHOW AVC set to "libavcodec": Ok
- AnyDVD settings check: Ok.
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[22:38:56] - Failed video encode, aborted
- Windows Version: 6.1 [7601]
- AVISYNTH Version: [2.5.8.0], Ok
- HAALI Splitter: [1.9.42.1], Ok
- FFDSHOW: [4504], Ok
- WIN7 preferred AVC CODEC: Ok
- WIN7 preferred VC-1 CODEC: Ok
- WIN7 preferred MPEG2 CODEC: Ok
- FFDSHOW VC-1 set to "wmv9", Ok
- FFDSHOW MPEG2 set to "libavcodec": Ok
- FFDSHOW AVC set to "libavcodec": Ok
- AnyDVD settings check: Ok.
- BD-RB v0.46.0.14, not current
bd-rb not current?
this was wierd cuz i jusr d/l the soft ware from this site