View Full Version : BD Rebuilder Beta - Bug Reports Only
jdobbs
1st February 2013, 23:37
I have really never done this before, but I needed to take my laptop somewhere while it was in the middle of a BDRB job. The resumed video has a couple of unplayable areas in it with bad breakups. I reran the job from scratch and they are gone. Is that an issue with resuming jobs, or a bug with that function? It should have no issues. All it does is pick up at the beginning of whichever pass you were on when you dropped out. I've done it hundreds of times. Just make sure you abort the job (don't just turn the computer off) so BD-RB can cleanly stop the processes.
RobertM
2nd February 2013, 00:13
I had an odd one the other day; not a rebuild failure, but truly an oddity. I was Backing up a BluRay of "W". The source folder was called "W" but the resulting rebuild ended up in a newly-created folder called "WD-2TB". The source folder ("W") was on a HDD with a volume label "WD-2TB" (Western Digital 2 Terra Bytes), so, it would seem pretty obvious that the new folder name was just copied from the volume label instead of the folder name.
Not sure if this is a BD-RB issue or a Win7-64 issue, or what. It's a pretty far-out edge case (not likely to happen very often), but I thought I'd report it just to get it in the record.
gonca
2nd February 2013, 00:43
@RobertM
This seems to occur with input names that are short. Maybe 3 or 4 characters or less. I usually get INPUT, which happens to be the name of my source drive.
Just tested and it seems the number of characters is 2 or less for this to happen.
jdobbs
2nd February 2013, 00:57
I had an odd one the other day; not a rebuild failure, but truly an oddity. I was Backing up a BluRay of "W". The source folder was called "W" but the resulting rebuild ended up in a newly-created folder called "WD-2TB". The source folder ("W") was on a HDD with a volume label "WD-2TB" (Western Digital 2 Terra Bytes), so, it would seem pretty obvious that the new folder name was just copied from the volume label instead of the folder name.
Not sure if this is a BD-RB issue or a Win7-64 issue, or what. It's a pretty far-out edge case (not likely to happen very often), but I thought I'd report it just to get it in the record.If the BDMV file is in the root of a drive, then the Volume Label is used. I think your case was because the folder only had one letter. BD-RB interpreted that to be a drive. Was the "W" drive in the root? I'll look at the code -- but I think any path that is shorter than 3 char.
RobertM
2nd February 2013, 02:06
Was the "W" drive in the root?
No, it was "E:/Bluray/W".
Regards,
Bob
jdobbs
2nd February 2013, 14:10
No, it was "E:/Bluray/W".
Regards,
BobHmm... I'll check it out, but I sure can't imagine how that could happen.
lauguru
4th February 2013, 09:49
bug
not play the movie, or the theatrical version and extended version, the extras on hand, if.
[Status]
LABEL=THE.MAN.WITH.THE.IRON.FISTS.2012.1080P.BLURAY.AVC.DTS-HD.MA.5.1-PUBLICHD
VERSION=v0.42.08 (beta)
SOURCE_SIZE=44452706845
SOURCE_VIDEO_SIZE=43688785920
TARGET_SIZE=25583157248
REDUCTION=.568091692189555
RESIZE_1080=0
AUDIO_TO_KEEP=all
KEEP_HD_AUDIO=-1
SUBS_TO_KEEP=all
BACKUP_MODE=0
MOVIEONLY_TYPE=0
USE_LAVF=-1
INSTANCES=5
DGDECNV=0
QUICK=0
ENCODE_STEP=0
COMPLETED=92
REBUILD_COMPLETE=1
[00031]
AUDIO=
PGS=
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=268757
RATE=500
SPLITS=1
NSTART=27000000
NEND=27001877
NSIZE=12288
FLINK=0
MLINK=0
[00032]
AUDIO=
PGS=
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=268757
RATE=500
SPLITS=1
NSTART=27000000
NEND=27001877
NSIZE=12288
FLINK=0
MLINK=0
[00033]
AUDIO=
PGS=
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=268757
RATE=500
SPLITS=1
NSTART=27000000
NEND=27001877
NSIZE=12288
FLINK=0
MLINK=0
[00105]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=46540398
RATE=8553
SPLITS=1
NSTART=27000000
NEND=28704960
NSIZE=45053952
FLINK=0
MLINK=0
[00107]
AUDIO=
PGS=
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=289699
RATE=500
SPLITS=1
NSTART=27000000
NEND=27001877
NSIZE=12288
FLINK=0
MLINK=0
[00108]
AUDIO=
PGS=
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=286209
RATE=500
SPLITS=1
NSTART=27000000
NEND=27001877
NSIZE=12288
FLINK=0
MLINK=0
[00109]
AUDIO=
PGS=
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=300171
RATE=500
SPLITS=1
NSTART=27000000
NEND=27001877
NSIZE=12288
FLINK=0
MLINK=0
[00112]
AUDIO=
PGS=
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=132634
RATE=500
SPLITS=1
NSTART=27000000
NEND=27001877
NSIZE=12288
FLINK=0
MLINK=0
[00119]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=2753890
RATE=6530
SPLITS=1
NSTART=27000000
NEND=27133920
NSIZE=2752512
FLINK=0
MLINK=0
[00120]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=2760871
RATE=6461
SPLITS=1
NSTART=27000000
NEND=27133920
NSIZE=546816
FLINK=0
MLINK=0
[00121]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=4090696
RATE=9815
SPLITS=1
NSTART=27000000
NEND=27133920
NSIZE=3883008
FLINK=0
MLINK=0
[00122]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=2757381
RATE=6524
SPLITS=1
NSTART=27000000
NEND=27133920
NSIZE=2752512
FLINK=0
MLINK=0
[00123]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=2760871
RATE=6542
SPLITS=1
NSTART=27000000
NEND=27133920
NSIZE=2807808
FLINK=0
MLINK=0
[00124]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=1137779059
RATE=9852
SPLITS=1
NSTART=27000000
NEND=64679040
NSIZE=1111990272
FLINK=0
MLINK=0
[00125]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=250268950
RATE=9869
SPLITS=1
NSTART=27000000
NEND=35298720
NSIZE=244224000
FLINK=0
MLINK=0
[00126]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=117108403
RATE=9868
SPLITS=1
NSTART=27000000
NEND=30882240
NSIZE=111550464
FLINK=0
MLINK=0
[00127]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=290753582
RATE=9847
SPLITS=1
NSTART=27000000
NEND=36617760
NSIZE=284461056
FLINK=0
MLINK=0
[00128]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=144008572
RATE=9863
SPLITS=1
NSTART=27000000
NEND=31772160
NSIZE=141072384
FLINK=0
MLINK=0
[00130]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=5451935
RATE=9803
SPLITS=1
NSTART=27000000
NEND=27180000
NSIZE=6586368
FLINK=0
MLINK=0
[00131]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=198789699
RATE=9607
SPLITS=1
NSTART=27000000
NEND=33622560
NSIZE=193800192
FLINK=0
MLINK=0
[00132]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=4069754
RATE=9869
SPLITS=1
NSTART=27000000
NEND=27133920
NSIZE=4399104
FLINK=0
MLINK=0
[00133]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=4066264
RATE=9860
SPLITS=1
NSTART=27000000
NEND=27133920
NSIZE=4331520
FLINK=0
MLINK=0
[00134]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=4069754
RATE=9869
SPLITS=1
NSTART=27000000
NEND=27133920
NSIZE=4411392
FLINK=0
MLINK=0
[00135]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=4066264
RATE=9860
SPLITS=1
NSTART=27000000
NEND=27133920
NSIZE=4362240
FLINK=0
MLINK=0
[00136]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=4076735
RATE=9886
SPLITS=1
NSTART=27000000
NEND=27133920
NSIZE=4478976
FLINK=0
MLINK=0
[00137]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=83936066
RATE=9759
SPLITS=1
NSTART=27000000
NEND=29748960
NSIZE=82176000
FLINK=0
MLINK=0
[00138]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=83503262
RATE=9756
SPLITS=1
NSTART=27000000
NEND=29734560
NSIZE=81211392
FLINK=0
MLINK=0
[00139]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=91750971
RATE=9765
SPLITS=1
NSTART=27000000
NEND=30006720
NSIZE=90513408
FLINK=0
MLINK=0
[00140]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=79869802
RATE=9754
SPLITS=1
NSTART=27000000
NEND=29613600
NSIZE=78127104
FLINK=0
MLINK=0
[00141]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=79901215
RATE=9747
SPLITS=1
NSTART=27000000
NEND=29613600
NSIZE=78759936
FLINK=0
MLINK=0
[00143]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=549622768
RATE=15026
SPLITS=1
NSTART=27000000
NEND=35393280
NSIZE=530122752
FLINK=-1
MLINK=0
[00144]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=432744728
RATE=14348
SPLITS=1
NSTART=27000000
NEND=33739680
NSIZE=417122304
FLINK=-1
MLINK=0
[00145]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=256886664
RATE=15010
SPLITS=1
NSTART=27000000
NEND=31127040
NSIZE=248592384
FLINK=-1
MLINK=0
[00146]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=48948744
RATE=14420
SPLITS=1
NSTART=27000000
NEND=27763680
NSIZE=47468544
FLINK=-1
MLINK=0
[00147]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=113953122
RATE=14974
SPLITS=1
NSTART=27000000
NEND=28825920
NSIZE=109971456
FLINK=-1
MLINK=0
[00148]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=59817710
RATE=14705
SPLITS=1
NSTART=27000000
NEND=27947520
NSIZE=58472448
FLINK=-1
MLINK=0
[00149]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=195260950
RATE=14635
SPLITS=1
NSTART=27000000
NEND=30085440
NSIZE=188319744
FLINK=-1
MLINK=0
[00150]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=340306157
RATE=14855
SPLITS=1
NSTART=27000000
NEND=32339520
NSIZE=329091072
FLINK=-1
MLINK=0
[00151]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=281783369
RATE=14674
SPLITS=1
NSTART=27000000
NEND=31468800
NSIZE=272007168
FLINK=-1
MLINK=0
[00152]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=165460296
RATE=14302
SPLITS=1
NSTART=27000000
NEND=29567520
NSIZE=159141888
FLINK=-1
MLINK=0
[00153]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=1075476215
RATE=14702
SPLITS=1
NSTART=27000000
NEND=44043840
NSIZE=1039337472
FLINK=-1
MLINK=0
[00154]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=18572181
RATE=16043
SPLITS=1
NSTART=27000000
NEND=27314880
NSIZE=17952768
FLINK=0
MLINK=0
[00155]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=2349902686
RATE=14771
SPLITS=1
NSTART=27000000
NEND=64321440
NSIZE=2271006720
FLINK=-1
MLINK=0
[00156]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=222192532
RATE=14820
SPLITS=1
NSTART=27000000
NEND=30533760
NSIZE=214904832
FLINK=-1
MLINK=0
[00157]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=330226011
RATE=15021
SPLITS=1
NSTART=27000000
NEND=32106720
NSIZE=318547968
FLINK=-1
MLINK=0
[00158]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=618208250
RATE=14779
SPLITS=1
NSTART=27000000
NEND=36819360
NSIZE=597331968
FLINK=-1
MLINK=0
[00159]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=788404958
RATE=14590
SPLITS=1
NSTART=27000000
NEND=39406080
NSIZE=760823808
FLINK=-1
MLINK=0
[00160]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=1599755513
RATE=14669
SPLITS=1
NSTART=27000000
NEND=52262400
NSIZE=1544669184
FLINK=-1
MLINK=0
[00161]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=1822719413
RATE=14719
SPLITS=1
NSTART=27000000
NEND=55901760
NSIZE=1764311040
FLINK=-1
MLINK=0
[00162]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=213494566
RATE=14810
SPLITS=1
NSTART=27000000
NEND=30366720
NSIZE=205799424
FLINK=-1
MLINK=0
[00163]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=1624969840
RATE=14806
SPLITS=1
NSTART=27000000
NEND=52812480
NSIZE=1570787328
FLINK=-1
MLINK=0
[00164]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=1303532544
RATE=14598
SPLITS=1
NSTART=27000000
NEND=47329920
NSIZE=1257756672
FLINK=-1
MLINK=0
[00165]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=1898484557
RATE=14485
SPLITS=1
NSTART=27000000
NEND=56740800
NSIZE=1830365184
FLINK=-1
MLINK=0
[00166]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=768862459
RATE=14399
SPLITS=1
NSTART=27000000
NEND=39015360
NSIZE=740474880
FLINK=-1
MLINK=0
[00167]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=588023657
RATE=14329
SPLITS=1
NSTART=27000000
NEND=36132480
NSIZE=567060480
FLINK=-1
MLINK=0
[00168]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=420661118
RATE=14940
SPLITS=1
NSTART=27000000
NEND=33735840
NSIZE=407832576
FLINK=-1
MLINK=0
[00169]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=263881336
RATE=14705
SPLITS=1
NSTART=27000000
NEND=31177920
NSIZE=255123456
FLINK=-1
MLINK=0
[00170]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=255563819
RATE=14956
SPLITS=1
NSTART=27000000
NEND=31098720
NSIZE=246982656
FLINK=-1
MLINK=0
[00171]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=124856992
RATE=14839
SPLITS=1
NSTART=27000000
NEND=28992960
NSIZE=121387008
FLINK=-1
MLINK=0
[00172]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=344218845
RATE=14678
SPLITS=1
NSTART=27000000
NEND=32446560
NSIZE=332974080
FLINK=-1
MLINK=0
[00173]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=806293030
RATE=14974
SPLITS=1
NSTART=27000000
NEND=39644160
NSIZE=779808768
FLINK=-1
MLINK=0
[00174]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=516007155
RATE=14750
SPLITS=1
NSTART=27000000
NEND=35188800
NSIZE=498708480
FLINK=-1
MLINK=0
[00175]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=444988895
RATE=14301
SPLITS=1
NSTART=27000000
NEND=33908640
NSIZE=428685312
FLINK=-1
MLINK=0
[00176]
AUDIO=1111
PGS=111111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=1089350378
RATE=14580
SPLITS=1
NSTART=27000000
NEND=44143200
NSIZE=1052037120
FLINK=0
MLINK=0
[00177]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=158465624
RATE=9783
SPLITS=1
NSTART=27000000
NEND=32204160
NSIZE=154970112
FLINK=0
MLINK=0
[00178]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=8122057
RATE=9848
SPLITS=1
NSTART=27000000
NEND=27269280
NSIZE=10917888
FLINK=0
MLINK=0
[00179]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=4998189
RATE=6541
SPLITS=1
NSTART=27000000
NEND=27247680
NSIZE=1124352
FLINK=0
MLINK=0
[00180]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=5225062
RATE=6542
SPLITS=1
NSTART=27000000
NEND=27257760
NSIZE=1136640
FLINK=0
MLINK=0
[00181]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=5263456
RATE=6542
SPLITS=1
NSTART=27000000
NEND=27260640
NSIZE=1136640
FLINK=0
MLINK=0
[00182]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=5867287
RATE=6539
SPLITS=1
NSTART=27000000
NEND=27290880
NSIZE=1161216
FLINK=0
MLINK=0
[00183]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=6355937
RATE=6537
SPLITS=1
NSTART=27000000
NEND=27313920
NSIZE=1185792
FLINK=0
MLINK=0
[00184]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=8076682
RATE=9861
SPLITS=1
NSTART=27000000
NEND=27267840
NSIZE=10973184
FLINK=0
MLINK=0
[00185]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=8533919
RATE=9868
SPLITS=1
NSTART=27000000
NEND=27282240
NSIZE=11298816
FLINK=0
MLINK=0
[00186]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=8467602
RATE=9856
SPLITS=1
NSTART=27000000
NEND=27280800
NSIZE=11249664
FLINK=0
MLINK=0
[00187]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=8076682
RATE=9861
SPLITS=1
NSTART=27000000
NEND=27267840
NSIZE=10973184
FLINK=0
MLINK=0
[00188]
AUDIO=1
PGS=111
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=11402991
RATE=11894
SPLITS=1
NSTART=27000000
NEND=27313920
NSIZE=13977600
FLINK=0
MLINK=0
[Options]
VERSION=0.42.0.8
MODE=0
MIN_M2TS_SIZE=1
MIN_PLAYLIST_MINS=1
WEIGHTP =1
DTSX_ENABLE=1
AUTO_BIAS=4
BLANK_THRESHOLD=1
ENABLE_TEST=1
ENCODE_QUALITY=3
ONEPASS_ENCODING=0
MULTIPROCESS=5
AUTO_QUALITY=0
AUDIO_TO_KEEP=all
SUBS_TO_KEEP=all
SD_CONVERT=0
OPEN_GOP=1
RESIZE_1080=0
DEINTERLACE=1
DEINTERLACER_TYPE=3
SD_TO_1080=0
CONVERT_WIDE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=1
AVCHD=1
REMOVE_WORKFILES=0
MOVIE_ONLY_LOOP=1
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=0
USE_LAVF=1
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
UNMASK_CHAPTER=0
COMPLETION_BEEP=0
DGDECNV=0
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=0
CUSTOM_TARGET_SIZE=24398
ENABLE_BLANKING=1
TARGET_SIZE=24398
[Paths]
SOURCE_PATH=D:\THE.MAN.WITH.THE.IRON.FISTS.2012.1080P.BLURAY.AVC.DTS-HD.MA.5.1-PUBLICHD\
WORKING_PATH=I:\REBUILDERDISCONUEVO\
Ch3vr0n
4th February 2013, 12:15
[QUOTE=lauguru;1614309]bug
not play the movie, or the theatrical version and extended version, the extras on hand, if.
[CODE][Status]
LABEL=THE.MAN.WITH.THE.IRON.FISTS.2012.1080P.BLURAY.AVC.DTS-HD.MA.5.1-PUBLICHD/QUOTE]
Come back when u decide to use the original retail store disc (pirate). No retail disc uses a name like that.
Verstuurd van mijn HTC Sensation XE with Beats Audio Z715e met Tapatalk
jdobbs
4th February 2013, 13:42
@lauguru
You need to use an original source BD. I have no idea what has happened to that source before it reaches BD-RB -- but I would guarantee that it was preprocessed.
lauguru
4th February 2013, 14:15
@lauguru
You need to use an original source BD. I have no idea what has happened to that source before it reaches BD-RB -- but I would guarantee that it was preprocessed.
ok thanks
Video Dude
5th February 2013, 02:01
You need to use an original source BD.
Is it ok to use BD Rebuilder a second time on files already processed by BD Rebuilder?
For example, I used BD-RB to make movie only no compression copies stored on hard disks, some larger than the BD25 size. If I now want to burn to BD25 disc, can I use BD-RB on the movie only output files to compress it to fit on the disc? This would save time by not having to rip the original disc again.
Ch3vr0n
5th February 2013, 02:38
Sure you can, however if something goes wrong (though unlikely) you can't issue a bug report since the source for the report will have been preprocessed (by BDRB, by who doesn't matter. Preprocessed is preprocessed)
RobertM
5th February 2013, 03:14
Preprocessed is preprocessed)
Actually, I'd be rather surprised if JDobbs wouldn't want to hear that BD-RB created a file that couldn't be properly processed a second time by BD-RB.
jdobbs
5th February 2013, 03:40
Actually, I'd be rather surprised if JDobbs wouldn't want to hear that BD-RB created a file that couldn't be properly processed a second time by BD-RB. If the source was created by BD-RB and it choked the second time through, I'd have to accept it -- I'd just want to know the entire sequence of events so I can recreate it (end-to-end). That way I'd actually be starting with a "non-preprocessed" source.
Nico8583
8th February 2013, 19:23
Hi :)
Have you test BD-RB with AviSynth 2.6.0 alpha 4 ?
I use another soft and I must install 2.6.0 alpha 4 with. But on the same OS I have already AviSynth 2.5.8 for BD-RB...
Thanks !
jdobbs
8th February 2013, 21:22
I haven't tested it, but it will probably work. Just remember that if you use it I won't accept any bug reports. It's an Alpha -- and testing a beta on an alpha is pretty much a recipe for failure.
Nico8583
8th February 2013, 22:29
Thanks ;)
Do you know if a rollback from 2.6.0 a4 to 2.5.8 is possible without problem in case of bug with BD-RB ?
Does AviSynth version could influence encoding quality or another point ?
jdobbs
8th February 2013, 22:58
Thanks ;)
Do you know if a rollback from 2.6.0 a4 to 2.5.8 is possible without problem in case of bug with BD-RB ?
Does AviSynth version could influence encoding quality or another point ?
It's unpredictable. It could cause anything from a small glitch to a complete crash. AVISYNTH is used extensively.
I wouldn't suggest using an Alpha version of AVISYNTH with BD-RB.
Nico8583
9th February 2013, 10:24
Thanks :) I'll install AviSynth Alpha to my second PC so no problem.
I had report a bug 2 months ago on angle selection, do you find anything for this problem ?
It was on Ice Age 4, movie got 5 angles but BD-RB find only 2 angles.
http://img545.imageshack.us/img545/3196/iceage4.png
Thanks ;)
gamete
9th February 2013, 10:35
What is the maximum dimension to set output in bd rebuilder to fill almost the disc?
i try 24500mb but it 's too
sorry for my bad english
omegaman7
9th February 2013, 10:41
What is the maximum dimension to set output in bd rebuilder to fill almost the disc?
i try 24500mb but it 's too
sorry for my bad english
I generally stick with 23500. But that is by NO means a good standard. Depending on the source disc, and it's quirks, you might need to adjust higher OR lower.
I would stick with 23,000 frankly. You really don't wanna utilize the very edge of the disc anyhow. That's typically where the worst burn errors occur.
colinhunt
9th February 2013, 14:23
You really don't wanna utilize the very edge of the disc anyhow. That's typically where the worst burn errors occur.
Not an issue when using high quality media and a good writer, like the latest 2-3 generations of Pioneer drives. I usually adjust output size so it leaves less than 100MB of space on a BD-R.
colinhunt
9th February 2013, 14:26
Bumped into another weird issue. This time the culprit is Space Adventure Cobra, a Japanese SciFi animation from early 80s. It's a collection of tv show episodes but they've all been authored into a single 47GB .m2ts instead of each episode in its own .m2ts. The problem is that in the output some of the episodes are missing English subtitles. Yes, some, but not all.
jdobbs
9th February 2013, 15:46
Not an issue when using high quality media and a good writer, like the latest 2-3 generations of Pioneer drives. I usually adjust output size so it leaves less than 100MB of space on a BD-R. I would disagree. It is much more cost efficient to simply not write to the outer edge. The space lost isn't enough to make a noticable difference in quality -- and you can rest assured that you're not having issues half-way through your movie when you watch it next year.
But... to each his/her own.
Rich86
9th February 2013, 18:42
I am running into an audio/video sync issue with the Alex Cross BD. After processing the source files to a movie only BD, the audio is significantly out of sync. The original BD and rip of the BD seems fine. Has anyone else run into this recently? I am running version BD-RB 42.08 and "Inspect" says everything is OK. This is one of those screwy Summitt titles with 1 correct playlist & a bunch of phony ones with the correct main movie playlist including 12 M2TS files. Any ideas or suggestions are welcome.
RobertM
9th February 2013, 19:22
and you can rest assured that you're not having issues half-way through your movie when you watch it next year.
Just out of curiosity, with a 'movie only' rebuild wouldn't any potential problems caused by outer edge writing happen at the end of the film, during the credits?
omegaman7
9th February 2013, 19:23
Just out of curiosity, with a 'movie only' rebuild wouldn't any potential problems caused by outer edge writing happen at the end of the film, during the credits?
Should be. But should you ever need to run another copy down the road, a read error might prevent you from copying the disc.
setarip_old
9th February 2013, 19:26
@Rich86
Hi!
See my post #16521 in this thread (and my related postings prior to that in this thread) regarding the "Ted" Blu-ray.
Also, a similar problem was noted regarding this year's (not Ahnold) "Total Recall".
There would see to be bad pressings occurring with greater frequency than in past years.
omegaman7
9th February 2013, 19:33
@Rich86
Hi!
See my post #16521 in this thread (and my related postings prior to that in this thread) regarding the "Ted" Blu-ray.
Also, a similar problem was noted regarding this year's (not Ahnold) "Total Recall".
There would see to be bad pressings occurring with greater frequency than in past years.
Thanks for the reminder! I generally look at my readers with one raised brow. Especially if google can't find others having the same issue. ;)
Rich86
9th February 2013, 19:37
@Rich86
Hi!
See my post #16521 in this thread (and my related postings prior to that in this thread) regarding the "Ted" Blu-ray.
Also, a similar problem was noted regarding this year's (not Ahnold) "Total Recall".
There would see to be bad pressings occurring with greater frequency than in past years.
I have a problem blaming the pressing since the original disc and the rip of that disc to my hard disc play fine. The problem appears only with the movie only version after processing by BD-RB.
omegaman7
9th February 2013, 19:41
I have a problem blaming the pressing since the original disc and the rip of that disc to my hard disc play fine. The problem appears only with the movie only version after processing by BD-RB.
I've had a similar instance. Reripping via another drive, fixed the problem. Needless to say, I no longer use the drive that introduced a read error. BD-RB was likely NOT the problem. It's the helper apps. E.g. TSmuxer. TSmuxer is clearly a finicky little helper app :p
Just an observation.... I mean no disrespect.
Rich86
9th February 2013, 19:43
I've had a similar instance. Reripping via another drive, fixed the problem. Needless to say, I no longer use the drive that introduced a read error. BD-RB was likely NOT the problem. It's the helper apps. E.g. TSmuxer. TSmuxer is clearly a finicky little helper app :p
Interesting. I will do a bit more experimenting with a different computer with a BD drive and report back.
jdobbs
9th February 2013, 20:23
Just out of curiosity, with a 'movie only' rebuild wouldn't any potential problems caused by outer edge writing happen at the end of the film, during the credits?
On a single layer disc that would be true.
omegaman7
9th February 2013, 20:26
On a single layer disc that would be true.
That's a very good point! :o
jdobbs
9th February 2013, 20:29
That's a very good point! :o I can't remember which direction the second layer is read, though... I know the first layer is read from center to the edge.
omegaman7
9th February 2013, 20:34
I would assume it starts in the center, moves outward, and then back inward. In order to be seamless. But then, buffering would eliminate the need for that.
colinhunt
9th February 2013, 22:52
But... to each his/her own.
Indeed. I prefer to do full discs to maximize bitrates. Like for example, an average bitrate of 21 Mbps instead of 20 Mbps. It's also why I use the slowest encoding preset; for best quality. Aaand I also make sure I use high quality media and burners by measuring PIE, PIF and Jitter values of a couple of discs from each cakebox. :D
setarip_old
10th February 2013, 01:38
@Rich86
To add some confusion to the topic:
1) My full disc rip was errorless. The question still remains, although BD-RB creates a perfectly synched FULL DISC COPY, why doesn't BD-RB create a properly synched MOVIE-ONLY either from the original rip of the commercial Blu-ray disc or the BD-RB created FULL DISC COPY ?
2) When my BD-RB "movie only" version proved to be out of synch, I ripped a "movie only" directly from the UNCOMPRESSED full disc (Excluding BD-RB from the equation). To my total surprise, this FULL "movie only" version was also out of synch!
BTW, if I remember correctly, the out of synch effect increased as the movie progressed...
jdobbs
10th February 2013, 02:11
@Rich86
To add some confusion to the topic:
1) My full disc rip was errorless. The question still remains, although BD-RB creates a perfectly synched FULL DISC COPY, why doesn't BD-RB create a properly synched MOVIE-ONLY either from the original rip of the commercial Blu-ray disc or the BD-RB created FULL DISC COPY ?
2) When my BD-RB "movie only" version proved to be out of synch, I ripped a "movie only" directly from the UNCOMPRESSED full disc (Excluding BD-RB from the equation). To my total surprise, this FULL "movie only" version was also out of synch!
BTW, if I remember correctly, the out of synch effect increased as the movie progressed... I'll test "Alex Cross" tomorrow -- if it is out of synch, I'll find and fix the problem.
Rich86
10th February 2013, 03:06
I'll test "Alex Cross" tomorrow -- if it is out of synch, I'll find and fix the problem.
Here's a bit more info, in case it is helpful:
I updated the firmware in my BD drive. I doubt this update has anything to do with reading a BD, but what the heck . . . then I reripped the Alex Cross title.
I ran Alex Cross through multi AVCHD set for movie only, no menus, & set so no additional compression would occur. The resulting output copy plays fine - no problems with AV synch.
I reran Alex Cross through BD-RB for movie only, with output custom size set so no re-compression would take place - and the output copy has the AV synch problem introduced into it. imho there is something about this title that BD-RB doesn't handle correctly.
Please note that as best I can tell, playlist #814 is the correct one for the movie & the one I have been testing with.
MikeyBK
10th February 2013, 05:14
Regarding the Alex Cross audio sync issue, here's what I did and posted in another forum to get a clean copy of that playlist 814...
If you still wanted to process playlist 814 thru BDRebuilder and get a copy that doesn't have the audio sync issue then you'll need to run all the original m2ts files for that playlist thru TSMuxer and 'join' them together outputting to a single m2ts bluray structure files, it'll output to about 26 Gigs, then run that newly muxed bluray files thru BDRebuilder and you'll get a clean copy without the audio sync problem.
jdobbs
10th February 2013, 05:24
That's good info to know -- but since this is a bug thread, the important thing is that I figure out what is causing the sync issue.
Interesting that TSMuxer handles it correctly when it joins them... especially since that's what BD-RB uses to do the same.
MikeyBK
10th February 2013, 05:29
yeah, perhaps it will get you to find the bug quicker knowing that TSMuxer joining the files processes thru BDRebuilder without any issues...
or whether it's even a bug in Rebuilder at all...because Rebuilder has worked fine for ages...
Yordan5
10th February 2013, 10:15
Regarding the Alex Cross audio sync issue, here's what I did and posted in another forum to get a clean copy of that playlist 814...
If you still wanted to process playlist 814 thru BDRebuilder and get a copy that doesn't have the audio sync issue then you'll need to run all the original m2ts files for that playlist thru TSMuxer and 'join' them together outputting to a single m2ts bluray structure files, it'll output to about 26 Gigs, then run that newly muxed bluray files thru BDRebuilder and you'll get a clean copy without the audio sync problem.
I have done about 300 movies with BD-RB. Every single one of them was pre-processed with TSMuxer (to insert Bulgarian subtitles) to Main Movie only from the original Full Disk rip (using AnyDVD HD as the ripper). I have not yet experienced a single issue following this procedure. Each BD-RB job was completed perfectly.
Nico8583
10th February 2013, 13:47
Thanks :) I'll install AviSynth Alpha to my second PC so no problem.
I had report a bug 2 months ago on angle selection, do you find anything for this problem ?
It was on Ice Age 4, movie got 5 angles but BD-RB find only 2 angles.
http://img545.imageshack.us/img545/3196/iceage4.png
Thanks ;)
I hope you have seen my post :)
Yordan5
10th February 2013, 14:09
How come when BD-RB starts Rebuilding BD file Structure (which is the last process of the job) my PC becomes unresponsive or slow and until this process finishes not much else can be run. CPU usage during this stage is minimal and I have always wondered what causes this unresponsiveness. My PC is core i5 3570K with 8Gb RAM and Windows 7 64 bit running from an SSD.
jdobbs
10th February 2013, 15:14
How come when BD-RB starts Rebuilding BD file Structure (which is the last process of the job) my PC becomes unresponsive or slow and until this process finishes not much else can be run. CPU usage during this stage is minimal and I have always wondered what causes this unresponsiveness. My PC is core i5 3570K with 8Gb RAM and Windows 7 64 bit running from an SSD. That task is barely using the CPU -- but it is reading/writing extensively to the hard drive. That's why the computer is responding so slowly. Rebuilding generally only takes a few minutes (depending upon the complexity).
Rich86
10th February 2013, 16:38
I stumbled upon another issue today.
"Seven Psychopaths" blu-ray - processing through BD-RB in movie only mode to fit on a 25gb output.
This title has forced subtitles (see chapter 4). They work fine with the ripped files.
Once processed through BD-RB, the forced subtitles do not work. If I turn english subtitles #2 on, the english subtitles for vietnamese dialog shows up.
If I then turn english subtitles #2 off and back up to the beginning of the chapter, the forced subtitles now work.
The source has 3 subtitle tracks (english 1 & 2 & spanish is #3). I specified to not include the spanish subtitles when I ran it thru BD-RB - just the 1st 2 english subtitles were carried forward.
Yordan5
10th February 2013, 17:54
That task is barely using the CPU -- but it is reading/writing extensively to the hard drive. That's why the computer is responding so slowly. Rebuilding generally only takes a few minutes (depending upon the complexity).
Thank you for enlightening me. Now it makes sense. I must say that with each PC upgrade (faster machines) I've had this has been less of an issue.
omegaman7
10th February 2013, 18:11
Thank you for enlightening me. Now it makes sense. I must say that with each PC upgrade (faster machines) I've had this has been less of an issue.
At any given time, I usually have 6 - 8 Hard drives connected to my machine. Food for thought ;)
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.