BD Rebuilder Beta - Bug Reports Only

[jdobbs]

While you are at it, you may want to check the following. Basically I replace tsmuxer.exe with new version from Roman (tsMuxeR_2.6.12) and inspect said ok in my case, it shouldn't be doing that or it is expected. Unfortunately the version number doesn't seem to be a part of the EXE file's header. So I just check for filesize. It seems, though, that each release of TSMUXER has exactly the same file size, which seems odd. I'll have to figure out another way to determine the version. I may have to do a file checksum, it's a pain, but that would at least distinguish it.

[Adbear]

There is an undocumented hidden option called IGNORE_3D that can be used. It's only undocumented because I forgot... You'd just add IGNORE_3D=1 to the [Options] area of the Config/INI file.

I need to remove the DTSX_ENABLE setting and add the new one (IGNORE_3D). DTSX_ENABLE has no effect now.
Would it not be possible to add the 2D/3D output as a menu option, as I often make a 2d & 3d version of my discs

[jdobbs]

Would it not be possible to add the 2D/3D output as a menu option, as I often make a 2d & 3d version of my discsYes, I'll do that.

[HWK]

How about ability to choose encoder when backing up to 2D between HC, X264 and FRIM Encoder.

[jdobbs]

How about ability to choose encoder when backing up to 2D between HC, X264 and FRIM Encoder.I can't imagine why anyone would want to use anything other than X264 except for MVC or DVD output. HC would result in MPEG-2 which would look poor in comparison, and X264 creates better quality at a give bitrate and is faster for AVC.

[HWK]

You are right, x264 is quite fast and it doesn't make sense to change default.

I was thinking if output is BD25, ability to choose encoder would be good option but like you mention there is no need for this.

Finally, I am not sure if you have considered this or not but since tsmuxer can create iso means no need for ImgBurn unless burning. Maybe for 2D part use tsmuxer and create iso as well.

[DoctorM]

@hwk pretty sure he was being a bit sarcastic. Smiley at the back.

Verstuurd vanaf mijn Nexus 7 met Tapatalk
A bit of both. I knew it wouldn't work but doesn't mean I wouldn't give it a go with XP if it did support it.

[HWK]

Didn't want to sound harsh but Intel compiled Media SDK in such way that it doesn't work with anything below Windows 7.

On a side note Microsoft is ending support in April are you gone stay with Xp after that.

[Sharc]

jdobbs
This (http://forum.doom9.org/showpost.php?p=1661954&postcount=453)could be interesting for BD-RB.

[jdobbs]

jdobbs
This (http://forum.doom9.org/showpost.php?p=1661954&postcount=453)could be interesting for BD-RB. Cool, I'd asked laserfan3d for that -- and it should solve the DirectShowSourceMVC() need as now I can feed SBS or O/U video directly into X264.

[Adbear]

Yes, I'll do that.
Thank you

[Sharc]

.....and it should solve the DirectShowSourceMVC() need as now I can feed SBS or O/U video directly into X264.
Exactly, and get around the "magic folder" and licensing issues .... trying .....

Added:
hurray, it works!

[jdobbs]

Exactly, and get around the "magic folder" and licensing issues .... trying .....

Added:
hurray, it works!I love it when a plan comes together. :)

[DarWun]

When doing a movie only copy of Hugo 3D to BD-9 on a Windows 8.1 system, the reencode using FRIMEnoder has failed on two attempts. On the first, it failed on the first pass at around 99%, and on the second it failed on the first pass at around 83%. The log file simply says Failed video encode.


I completed a rebuild of both Dredd 3D and Hugo 3D to BD-25 without FRIMEncode failing. I'm going to go back and retry a rebuild of Hugo 3D to BD-9 this evening to see if the video encode fails like it did in my first attempt. I'll post back with my findings.

[HWK]

I am gone do some testing later today or tomorrow. Jdobbs any specify movie you want me to do.

[Limobar]

I did "Epic 3D". The encode went without errors.

The playback in both PowerDVD and TMT5 shows shacking and artifacts. It looks like there is a compatibility issue between the FRIM encoder and the decoders used by PowerDVD and TMT5.

[jdobbs]

I did "Epic 3D". The encode went without errors.

The playback in both PowerDVD and TMT5 shows shacking and artifacts. It looks like there is a compatibility issue between the FRIM encoder and the decoders used by PowerDVD and TMT5.I've tested on PowerDVD 11 and I'm not seeing any issues.

Have you tried playback on a standalone device? That the definitive test.

[jdobbs]

Exactly, and get around the "magic folder" and licensing issues .... trying .....

Added:
hurray, it works!Here's a working command line for half-SBS encoding using X264:

FRIMDecode.exe -i::mvc 00000.track_4113.264 00000.track_4114.mvc -sbs -o - | x264.exe - --demuxer raw --input-res 3840x1080 --fps 23.976 --crf 18 --video-filter resize:width=1920,height=1080,sar=1:1,method=bilinear --output out3d.264

Of course you could replace the CRF with a "--bitrate" option, and you could do two passes in two consecutive command lines. You could also use "bicubic", "spline", or "lanczos" for the resizing method.

[Limobar]

I've tested on PowerDVD 11 and I'm not seeing any issues.

Have you tried playback on a standalone device? That the definitive test.

I cannot test that, because my Blu-Ray player does not play 3D.

This is the first time I see this happening. Other 3D encodes, retail Blu-Rays, DVDFab re-encodes and 3DT re-encodes, play fine using PowerDVD and TMT5?

Did you mean that you also tried "Epic 3D"?

[jdobbs]

I am gone do some testing later today or tomorrow. Jdobbs any specify movie you want me to do.Not really. Just let me know if you find any issues.

[Sharc]

Here's a working command line for half-SBS encoding using X264:

FRIMDecode.exe -i::mvc 00000.track_4113.264 00000.track_4114.mvc -sbs -o - | x264.exe - --demuxer raw --input-res 3840x1080 --fps 23.976 --crf 18 --video-filter resize:width=1920,height=1080,sar=1:1,method=bilinear --output out3d.264

Of course you could replace the CRF with a "--bitrate" option, and you could do two passes in two consecutive command lines. You could also use "bicubic", "spline", or "lanczos" for the resizing method.

Or if one prefers OU instead of SBS:
FRIMDecode.exe -i::mvc 00098.track_4113.264 00098.track_4114.mvc -tab -o - | x264.exe - --demuxer raw --sar 1:1 --crf 18 --input-res 1920x2160 --sar 1:1 --video-filter resize:width=1920,height=1080,sar=1:1,method=bilinear --fps 23.976 --output "C:\temp\FRIMtox264-OU.h264"

[HWK]

Not really. Just let me know if you find any issues.

Ok, commencing test sequence. I will start with avatar and see how it comes out.

[Sharc]

Ok, commencing test sequence. While at it I was wondering would this be good time to get rid of ffdshow and use frimdecode to decode avc, mvc, mpeg2 and vc-1 stream or do you plan to phase out in stages if at all.
See jdobb's footnote here (http://forum.doom9.org/showpost.php?p=1661571&postcount=18755)

[HWK]

Thanks, after close examination I realized as long as we have Vc-1 ffdshow is going nowhere, unless jdobbs is also working on developing decoder for all supported formats.

[jdobbs]

Thanks, after close examination I realized as long as we have Vc-1 ffdshow is going nowhere, unless jdobbs is also working on developing decoder for all supported formats.I've found that the newest version of X264 includes LAVF filters that handle every format very well. The only thing holding it back in the past was it's VC-1 interlaced limitations, and those seem to have gone away.

One other limitation of feeding X264 directly is that, even though you can resize internally, there aren't any common releases that include the ability to pad -- so some of BD-RB's features (like resizing 4:3 into a 16:9 window) might still need AVISYNTH. I'm looking for a workaround. There are patches that filter, so I guess I could always start creating my own builds. I just hate to do that.

[HWK]

I've found that the newest version of X264 includes LAVF filters that handle every format very well. The only thing holding it back in the past was it's VC-1 interlaced limitations, and those seem to have gone away.

One other limitation of feeding X264 directly is that, even though you can resize internally, there aren't any common releases that include the ability to pad -- so some of BD-RB's features (like resizing 4:3 into a 16:9 window) might still need AVISYNTH. I'm looking for a workaround. There are patches that filter, so I guess I could always start creating my own builds. I just hate to do that.

Jdobbs, I was reading somewhere that x264 LAVF can decode and serve frame to other encoders like HC. If so you can create two instance of x264 one for decode and another one for encode and use avisynth between them to process.

[HWK]

Not really. Just let me know if you find any issues.

Ok, commencing test sequence. I will start with avatar and see how it comes out.

Jdobbs, Couple of things I noticed during encode

1. Max bitrate allowed is up to 60000, you have set 35000 isn't that low for both views combined.

2. Tsmuxer is extracting all subtitle from disc, even though option of having one was selected in BD-RB.

3. What does MKV have to do with this according VID_00001 file

#Created by BD Rebuilder - v0.46.03 (beta)
DirectshowSource("E:\BD_OUT\WORKFILES\00001.track_4113.mkv", fps=23.976, framecount=232608, ConvertFPS=true, audio=false)
ConvertToYV12().AssumeFPS(24000,1001)

[DarWun]

I have a question about the quality of the new 3D mode. Does it make a difference in quality to use the existing (x264) quality profiles, or is there just one quality?

Yes. Tweaking relates specifically to X264 settings, so it wouldn't apply.

I just want to make sure I'm not missing something. Are you saying that for a 3D rebuild using FRIMEncode, the encoder quality settings Good, Better, etc. don't matter? If this is the case then I am a bit confused as to why a 3D rebuild with the encoder quality set at Highest took 7hours, and one done with automatic settings took 3.5hours.

[HWK]

I just want to make sure I'm not missing something. Are you saying that for a 3D rebuild using FRIMEncode, the encoder quality settings Good, Better, etc. don't matter? If this is the case then I am a bit confused as to why a 3D rebuild with the encoder quality set at Highest took 7hours, and one done with automatic settings took 3.5hours.

No, it is tweak related to x264 which has no effect, an example can be given of tune film value which is specific to x264 encoder in this case. Quality wise it will make difference since program change internal value of encoder to balance between speed and quality. For example I am using Ultra High Quality in BD-RB and for that preset in frimencode is given value of (2)

Frim quality scale goes from 1-7, 1 highest quality and 7 optimized for speed and 4 is balanced. As a result when you change quality setting BD-RB automatically set scale in encoder to predetermined value.

[DarWun]

Thanks for the clarification HWK.

[jdobbs]

Jdobbs, Couple of things I noticed during encode

1. Max bitrate allowed is up to 60000, you have set 35000 isn't that low for both views combined.

2. Tsmuxer is extracting all subtitle from disc, even though option of having one was selected in BD-RB.

3. What does MKV have to do with this according VID_00001 file

#Created by BD Rebuilder - v0.46.03 (beta)
DirectshowSource("E:\BD_OUT\WORKFILES\00001.track_4113.mkv", fps=23.976, framecount=232608, ConvertFPS=true, audio=false)
ConvertToYV12().AssumeFPS(24000,1001)It was probably VC-1 interlaced or pulldown. DirectshowSource() can't read it properly from an M2TS (actually I think the issue is HAALI) so it has to be remuxed into an MKV first. There are a lot of things BD-RB has to do as workarounds for limitations in the tools.

[Limobar]

I did "Cloudy With A Chance Of Meatballs 2" and got the exact same artifacts I got with "Epic", using PowerDVD 12. It's the 3D part that has the artifacts. The 2D part is clean.

http://i39.tinypic.com/k31un6.jpg

[Acerjen]

- Updated code to fully support DTS Express
secondary streams without the need for
special processing.

Does this mean that DTS Express audio tracks should work or is this something entirely different? All of the titles I have come across that have DTS Express audio, use it for the PIP video. I ran a few titles through the newest version and the DTS Express track is not working. Basically, its the same as its been since DTS Express support was put in experimentally a while back. PIP video works great but the audio isn't there. I checked the M2TS file with tsMuxer and the DTS Express track is there but is not playing. Before I posted anything specific, I wanted to ask if maybe I am misunderstanding what the above statement is saying. Thank you for your time and a great program. Later.

Acerjen

[jdobbs]

Does this mean that DTS Express audio tracks should work or is this something entirely different? All of the titles I have come across that have DTS Express audio, use it for the PIP video. I ran a few titles through the newest version and the DTS Express track is not working. Basically, its the same as its been since DTS Express support was put in experimentally a while back. PIP video works great but the audio isn't there. I checked the M2TS file with tsMuxer and the DTS Express track is there but is not playing. Before I posted anything specific, I wanted to ask if maybe I am misunderstanding what the above statement is saying. Thank you for your time and a great program. Later.

AcerjenIt should definitely work. It's working on all my players.

[HWK]

It was probably VC-1 interlaced or pulldown. DirectshowSource() can't read it properly from an M2TS (actually I think the issue is HAALI) so it has to be remuxed into an MKV first. There are a lot of things BD-RB has to do as workarounds for limitations in the tools.

Avatar 3D main movie is not interlaced and vc-1. So I am not quite sure about this response being correct. FrimDecode is decoding this movie so I bit confused at this stage.

[jdobbs]

Avatar 3D main movie is not interlaced and vc-1. So I am not quite sure about this response being correct. FrimDecode is decoding this movie so I bit confused at this stage.If FRIM is being used, then that AVS file is doing nothing anyway. But I still don't see how it could be pointing to an MKV -- I'll go back and look.

[HWK]

Jdobbs, Can you also check why BD-RB is extracting all subtitle stream (6) in case of avatar. Even though I want English only in final output. This one doesn't include one with 80mb + size.

[HWK]

I did "Cloudy With A Chance Of Meatballs 2" and got the exact same artifacts I got with "Epic", using PowerDVD 12. It's the 3D part that has the artifacts. The 2D part is clean.

http://i39.tinypic.com/k31un6.jpg

Can you provide more info about GPU and system?

[DarWun]

I completed a rebuild of both Dredd 3D and Hugo 3D to BD-25 without FRIMEncode failing. I'm going to go back and retry a rebuild of Hugo 3D to BD-9 this evening to see if the video encode fails like it did in my first attempt. I'll post back with my findings.

Another update. After having success with a rebuild of Hugo 3D to BD-25, I retried a rebuild to BD-9. The video encode failed on three separate attempts. This may not have anything to do with the failures, but BD-Rebuilder Priority was set on idle and I was doing other CPU/GPU intensive things on the PC while the rebuild was happening (i.e. playing Civilization 5). The reason I mention this is that when I ran two BD-9 rebuilds of the same movie with different quality settings in batch mode overnight, they both completed successfully. I usually run rebuilds in the background while doing other things on the PC without an issue.

[HWK]

Hmm, interesting find. So it seems OS is having difficulty locating CPU time to applications or it would seem so with game. What is even more interesting is I am gamer as well and never came across such a thing.

[jdobbs]

Another update. After having success with a rebuild of Hugo 3D to BD-25, I retried a rebuild to BD-9. The video encode failed on three separate attempts. This may not have anything to do with the failures, but BD-Rebuilder Priority was set on idle and I was doing other CPU/GPU intensive things on the PC while the rebuild was happening (i.e. playing Civilization 5). The reason I mention this is that when I ran two BD-9 rebuilds of the same movie with different quality settings in batch mode overnight, they both completed successfully. I usually run rebuilds in the background while doing other things on the PC without an issue.Can you post your settings? I'm interested what you are using for frame serving.

I also noticed that your log post doesn't include the output showing whether you settings are correct. That makes me wonder why you decided to remove that part. Can you run INSPECT and post the results?

[Note] Actually I forgot this was a 3D encode... so obviously you're using FRIMDecode for frame serving. I may have to do some testing and see if FRIMDecode is vulnerable/affected by CPU usage.

[DarWun]

Can you post your settings? I'm interested what you are using for frame serving.

I also noticed that your log post doesn't include the output showing whether you settings are correct. That makes me wonder why you decided to remove that part. Can you run INSPECT and post the results?

Weird. I didn't edit the log files at all (other than to change the extensions so that I could attach them to my post). I'm not sure why the Inspect information isn't there. I'll run inspect when I get home tonight and post the results.

I may be wrong about this, but my recollection is that when doing a normal 2D rebuild in the past using DGDecNV, not all my CPU's cores were used. I'm pretty sure all six cores were running at 100% when doing the 3D rebuild. I'll check that tonight as well to make sure that is actually the case.

Edited to add: I looked back through the forum to see where the inspect information is supposed to be showing up in the log file. In the posts I found with logs for failed rebuilds, it looks like the inspect information is supposed to be tacked on after the encode fails. None of my failed encode log files I looked at last night had that information in them. The last line in all the logs was the same as it was in the log I attached to my original post: "Failed video encode, aborted".

[Limobar]

[screenshot that shows artifacts]

Can you provide more info about GPU and system?

i7 920@3.8Ghz
nVidia GTX 460
6 GB RAM
Windows 7 (64 bit)

Your request for more info got me thinking. I disabled hardware acceleration in TMT5 and then the artifacts are gone. I tried it also with PowerDVD 12, but that software appears to disallow disabling of hardware acceleration.

Blu-Ray players use hardware acceleration. Does that mean that FRIM encodes do not get decoded correctly?

I cannot test it myself, because I don't have a 3D compatible Blu-Ray player. I created a sample (130 MB). Please, try it and report back.

Here's the sample: https://www.hightail.com/download/elNLQmtjcklrUm52WnRVag

[DarWun]

I ran across another potential bug when trying to do multiple rebuilds using FRIMEncode with different quality settings in batch mode. The attached BDBATCH file shows that the encode quality settings for the two tasks were set at 0 (good) and 3 (high). The attached BATCHITEM file shows that the second high quality encode task was completed using an encode quality of 0 instead of 3. This is the first time I've tried batch mode using different quality settings. So I'm not sure if this is something new to this version of BD-Rebuilder or something that has carried over from a previous version.

[HWK]

i7 920@3.8Ghz
nVidia GTX 460
6 GB RAM
Windows 7 (64 bit)

Blu-Ray players use hardware acceleration. Does that mean that FRIM encodes do not get decoded correctly?



No, if it was the case encoder will crash on garbage input. Sound more like video card issue since GPU acceleration off result in good and clean playback.

Anyways I will try on software and hardware and see what is happening.

[Limobar]

...Sound more like video card issue since GPU acceleration off result in good and clean playback.

I highly doubt that. It's only with FRIM encodes that the artifacts show.

[HWK]

I highly doubt that. It's only with FRIM encodes that the artifacts show.

Hmm, Can you share more info about movie and setting you were using. If I have the movie I can test and see what is happening with this .

I will also try to run with another MVC encoder and see if there is something I can come up with regards to encoder or its setting.

[DarWun]

Weird. I didn't edit the log files at all (other than to change the extensions so that I could attach them to my post). I'm not sure why the Inspect information isn't there. I'll run inspect when I get home tonight and post the results.

Here are the results from INSPECT:

- Windows Version: 6.2 [9200]
- AVISYNTH Version: [2.5.8.0], Ok
- HAALI Splitter: [1.9.42.1], Ok
- FFDSHOW: [4504], 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 Rebuilder v0.46.0.3, Ok
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- WAVI: Ok
- TSMUXER: Ok

Here are the contents of the settings file from the BD-Rebuilder installation directory:

[Options]
VERSION=0.46.0.3
MODE=3
ENCODE_QUALITY=0
DTSX_ENABLE=1
MULTIPROCESS=1
DISABLE_VIDEO_SLEEP=1
FULL_3D=1
ONEPASS_ENCODING=0
AUTO_QUALITY=1
STATUS_LOG=1
TARGET_SIZE=8032
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
RESIZE_1440=0
RESIZE_720=0
DEINTERLACE=1
SD_TO_1080=0
CONVERT_WIDE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=1
AVCHD=0
REMOVE_WORKFILES=1
MOVIE_ONLY_LOOP=0
REMOVE_OUTPUT=1
USE_FILTERS=0
BDMV_CERT_ONLY=0
USE_LAVF=0
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
UNMASK_CHAPTER=0
COMPLETION_BEEP=0
DGDECNV=1
OUTPUT_SBS=0
NEROAAC=0
SUPTITLE=1
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=50000
[Paths]
WORKING_PATH=D:\TEMP\
DGIndexNV=D:\Program Files (x86)\DGDecNV\DGIndexNV.exe
DGDecNV=D:\Program Files (x86)\DGDecNV\DGDecodeNV.dll
DirectShowMVCSource=D:\Program Files (x86)\BD_Rebuilder\Tools\stereoplayer.exe\DirectShowMVCSource.dll
SupTitlePath=D:\Program Files (x86)\BD_Rebuilder\Tools\SupTitle\SupTitle.dll
SOURCE_PATH=I:\

[Limobar]

Hmm, Can you share more info about movie and setting you were using. If I have the movie I can test and see what is happening with this .

I will also try to run with another MVC encoder and see if there is something I can come up with regards to encoder or its setting.

The movie is: "Cloudy With A Chance Of Meatballs 2". I used the "Highest Quality" setting. The Movie "Epic" gives the same artifacts with hardware acceleration.


Log:
----------------------
[01/14/14] BD Rebuilder v0.46.03 (beta)
[10:59:08] Source: CLOUDY_2_00001
- Input BD size: 29.94 GB
- Approximate total content: [01:34:50.684]
- Target BD size: 23.68 GB
- Windows Version: 6.1 [7601]
- MOVIE-ONLY mode enabled
- Quality: Highest (Very Slow), ABR
- X264 Tweak(s) enabled
- MVC 3D Output Mode enabled
- Decoding/Frame serving: FRIMDecode
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[10:59:08] PHASE ONE, Encoding
- [10:59:08] Processing: VID_00344 (1 of 3)
- [10:59:08] Extracting A/V streams [VID_00344]
- [11:05:20] Reencoding video [VID_00344]
- [11:05:20] Reencoding: VID_00344, Pass 1 of 1
- Track 4352 (eng): Keeping original audio
- [12:11:11] Processing: VID_00345 (2 of 3)
- [12:11:11] Extracting A/V streams [VID_00345]
- [12:11:16] Reencoding video [VID_00345]
- [12:11:16] Reencoding: VID_00345, Pass 1 of 1
- [12:13:42] Processing: VID_00346 (3 of 3)
- [12:13:42] Extracting A/V streams [VID_00346]
- [12:22:06] Reencoding video [VID_00346]
- [12:22:06] Reencoding: VID_00346, Pass 1 of 1
[23:35:05]PHASE ONE complete
[23:35:05]PHASE TWO - Rebuild Started
- [23:35:05] Rebuilding BD file Structure
[23:46:12] - Encode and Rebuild complete
[23:46:12] JOB: CLOUDY_2 finished.

Setup info:

[Status]
LABEL=CLOUDY_2
VERSION=v0.46.03 (beta)
SOURCE_SIZE=32143816704
SOURCE_VIDEO_SIZE=32143816704
TARGET_SIZE=25427968000
REDUCTION=.791068721992673
RESIZE_1080=0
RESIZE_1440=0
AUDIO_TO_KEEP=all
KEEP_HD_AUDIO=-1
SUBS_TO_KEEP=all
BACKUP_MODE=1
MOVIEONLY_TYPE=0
USE_LAVF=-1
INSTANCES=1
DGDECNV=0
SSIF_MODE=-1
QUICK=0
ENCODE_STEP=0
COMPLETED=3
REBUILD_COMPLETE=1
[00344]
AUDIO=1111
PGS=1111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=2080530686
RATE=30866
NSIZE=0
FLINK=-1
MLINK=0
[00345]
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=74387293
RATE=28312
AUDIO=1111
NSIZE=0
FLINK=-1
MLINK=0
[00346]
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=23273050021
RATE=30089
AUDIO=1000
NSIZE=0
FLINK=0
MLINK=0

[DarWun]

Hmm, interesting find. So it seems OS is having difficulty locating CPU time to applications or it would seem so with game. What is even more interesting is I am gamer as well and never came across such a thing.

It's new to me as well. If I can find some time I'm going to play around a bit more tonight to see if I can reproduce the occurrence. I should point out that of the three rebuild failures that occurred last night, only two of them occurred while I was gaming. The third occurred while I was backing up my NAS to an external hard drive. I don't recall that being very CPU intensive. But then again don't usually pay much attention to CPU performance while completing backups (unless I'm bored ;-) ).