BD Rebuilder Beta - Bug Reports Only

[kufo]

This seems to be solved in the redfox forum. To get a working copy you´ll ned the original disc or an untouched mounatable image.
Lok here for details: https://forum.redfox.bz/threads/mockingjay-2.68608/

Sorry for double post :mad: After first post a server error was shown.

[jdobbs]

Sorry for double post :mad: After first post a server error was shown.Fixed it. I got one of those earlier today also.

[wakko709]

------------------------------
[04/05/16] BD Rebuilder v0.50.14
[11:57:33] Source: PACIFIC_RIM
- Input BD size: 35.30 GB
- Approximate total content: [02:27:19.830]
- Target BD size: 22.95 GB
- Windows Version: 6.2 [9200]
- Auto Quality: Good (Very Fast), ABR
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[11:57:42] PHASE ONE, Encoding
- [11:57:42] Processing: VID_00001 (1 of 7)
- [11:57:42] Extracting A/V streams [VID_00001]
- Error in attempt to extract audio/subs.
-

[wakko709]

------------
[04/05/16] BD Rebuilder v0.50.14
[11:57:33] Source: PACIFIC_RIM
- Input BD size: 35.30 GB
- Approximate total content: [02:27:19.830]
- Target BD size: 22.95 GB
- Windows Version: 6.2 [9200]
- Auto Quality: Good (Very Fast), ABR
- Decoding/Frame serving: X264/LAVF
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[11:57:42] PHASE ONE, Encoding
- [11:57:42] Processing: VID_00001 (1 of 7)
- [11:57:42] Extracting A/V streams [VID_00001]
- Error in attempt to extract audio/subs.
-

[wakko709]

and theres another issue with mokeingjay2 won't work

[Ch3vr0n]

Then post the encode log for that one, no log no fix.

Verstuurd vanaf mijn Nexus 7 met Tapatalk

[jdobbs]

and theres another issue with mokeingjay2 won't workUninstall and reinstall BD-RB, AVISYNTH, and LAV filters (or FFDSHOW) and see if that fixes it.

[Lathe]

I was hoping for something like:
1. Create the mentioned script setting, save as (***.avs ?)
2. Add the ***.avs script in BDRB
3. Add the Blu-ray title
4. Do the necessary output settings in BDRB
5. Hit "Backup"

I'm a very much GUI person and not very good at command line...
Oh well, lots to learn. No easy way?

Well, what I do is just simply add specific 2nd pass 'tweaks' that I want BDRB to do. I don't myself create an entire command line for the encode.

I've found that BDRB does a fine job on encoding and adds all the necessary parameters for most stuff.

For example, here is what I usually add if I am doing a pretty heavily compressed Blu-ray (in other words, say if you are compressing from 35 Gigs to 23 to fit on a single layer Blu-ray):

TWEAK_PASS_TWO=--ref 4 --deblock -2:-2 --psy-rd 1.00:0.20 --me umh --subme 8 --trellis 2 --direct auto --qcomp 0.50

Now, most here will tell you that this probably isn't necessary, and they are probably right :) but, I just like to tweak the deblocking, Psychovisual / Trellis, and make sure the 'me' & 'subme' are a bit higher than BDRB normally sets them for 'High - Default' (the super slow setting IS indeed overkill though and sets the settings TOO high I feel) and alter the qcomp a tad (this was suggested by Selur who designed HYBRID - it basically takes a few more bits from the high motion scenes and assigns them to the more static scenes, no big deal...)

I use these tweaks if I feel that there is not going to be that much compression (like just 2 or 3 Gigs):

TWEAK_PASS_TWO=--deblock -2:-2 --qcomp 0.50

Just to make the picture a tad sharper and the 'moving bits around thing'

If you want to experiment where it's pretty easy, I would suggest adding tweaks to BDRB and let it do most of the work :)

I am definitely NOT an expert, but I just kind of fiddle around a little bit with this kind of stuff... I only mention these that I use because you said that you wanted to experiment around a little. Hope that helps somewhat.

[Sharc]

@Lathe
I am not sure whether it's a terribly good idea to change --deblock and --direct between passes. They should better be the same for pass1 and pass2, as the speed gain for pass1 is minimal with the lower settings. The other parameters are less critical and can be changed for pass2 (I am not sure about --qcomp though).

Anyway, the discussion has nothing to to with a BD-RB bug report.

Edit:
About changing --direct between passes, see here:
http://forum.doom9.org/showpost.php?p=1113961&postcount=30
So in best case, it has no effect at all.

Or the discussion here:
http://forum.doom9.org/showthread.php?t=135533

[varekai]

@Lathe
@Sharc
Thanks guys, appreciate the input, will try to learn more.
Now back on topic... but I never seems to find any bugs...:D

[Weirdo]

Hello, I interrupted a backup process about half-way, but seems BD-RB cannot resume this one, I get the "working path is not empty - delete all old files?" prompt. Haven't made any changes or used BD-RB in-between. Any suggestions on how I could resume this? Thank you.

Log in Working folder:

[04-06-16] BD Rebuilder v0.50.14
[22:50:47] Source: MY_SOURCE
- Input BD size: 28.30 GB
- Approximate total content: [05:17:45.337]
- Target BD size: 7.84 GB
- Windows Version: 6.2 [9200]
- Resize: 1080p to 720p enabled
- Auto Quality: High Quality (Default), Two Pass
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[22:50:47] PHASE ONE, Encoding
- [22:50:47] Processing: VID_00231 (1 of 22)
- [22:50:47] Extracting A/V streams [VID_00231]
- [22:50:57] Reencoding video [VID_00231]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 480 frames
- Convert: 1280x720, 23.976fps, 480 frames
- Bitrate: 8,536 Kbs
- [22:50:57] Reencoding: VID_00231, Pass 1 of 2
- [22:51:11] Reencoding: VID_00231, Pass 2 of 2
- [22:51:22] Video Encode complete
- [22:51:22] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [22:51:22] Multiplexing M2TS
- [22:51:26] Blanking: VID_00274 (2 of 22)
- [22:51:26] Processing: VID_00295 (3 of 22)
- [22:51:26] Extracting A/V streams [VID_00295]
- [22:52:13] Reencoding video [VID_00295]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 6,902 frames
- Convert: 1280x720, 23.976fps, 6,902 frames
- Bitrate: 8,468 Kbs
- [22:52:13] Reencoding: VID_00295, Pass 1 of 2
- [22:54:29] Reencoding: VID_00295, Pass 2 of 2
- [23:01:13] Video Encode complete
- [23:01:13] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [23:01:13] Multiplexing M2TS
- [23:01:24] Processing: VID_00304 (4 of 22)
- [23:01:24] Extracting A/V streams [VID_00304]
- [23:02:20] Reencoding video [VID_00304]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 7,191 frames
- Convert: 1280x720, 23.976fps, 7,191 frames
- Bitrate: 8,461 Kbs
- [23:02:20] Reencoding: VID_00304, Pass 1 of 2
- [23:04:51] Reencoding: VID_00304, Pass 2 of 2
- [23:11:16] Video Encode complete
- [23:11:16] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [23:11:16] Multiplexing M2TS
- [23:11:25] Processing: VID_00305 (5 of 22)
- [23:11:25] Extracting A/V streams [VID_00305]
- [23:11:46] Reencoding video [VID_00305]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 5,814 frames
- Convert: 1280x720, 23.976fps, 5,814 frames
- Bitrate: 4,172 Kbs
- [23:11:46] Reencoding: VID_00305, Pass 1 of 2
- [23:14:01] Reencoding: VID_00305, Pass 2 of 2
- [23:18:36] Video Encode complete
- [23:18:36] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [23:18:36] Multiplexing M2TS
- [23:18:42] Processing: VID_00306 (6 of 22)
- [23:18:42] Extracting A/V streams [VID_00306]
- [23:18:54] Reencoding video [VID_00306]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 3,442 frames
- Convert: 1280x720, 59.940fps, 6,884 frames
- Bitrate: 4,170 Kbs
- [23:18:54] Reencoding: VID_00306, Pass 1 of 2
- [23:21:19] Reencoding: VID_00306, Pass 2 of 2
- [23:25:18] Video Encode complete
- [23:25:18] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [23:25:18] Multiplexing M2TS
- [23:25:23] Processing: VID_00307 (7 of 22)
- [23:25:23] Extracting A/V streams [VID_00307]
- [23:25:41] Reencoding video [VID_00307]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 5,423 frames
- Convert: 1280x720, 23.976fps, 5,423 frames
- Bitrate: 4,172 Kbs
- [23:25:41] Reencoding: VID_00307, Pass 1 of 2
- [23:27:44] Reencoding: VID_00307, Pass 2 of 2
- [23:31:43] Video Encode complete
- [23:31:43] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [23:31:43] Multiplexing M2TS
- [23:31:48] Processing: VID_00308 (8 of 22)
- [23:31:48] Extracting A/V streams [VID_00308]
- [23:31:57] Reencoding video [VID_00308]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 2,239 frames
- Convert: 1280x720, 59.940fps, 4,478 frames
- Bitrate: 4,170 Kbs
- [23:31:57] Reencoding: VID_00308, Pass 1 of 2
- [23:33:23] Reencoding: VID_00308, Pass 2 of 2
- [23:35:41] Video Encode complete
- [23:35:41] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [23:35:41] Multiplexing M2TS
- [23:35:45] Processing: VID_00309 (9 of 22)
- [23:35:45] Extracting A/V streams [VID_00309]
- [23:38:20] Reencoding video [VID_00309]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 48,634 frames
- Convert: 1280x720, 23.976fps, 48,634 frames
- Bitrate: 4,171 Kbs
- [23:38:20] Reencoding: VID_00309, Pass 1 of 2
- [23:56:32] Reencoding: VID_00309, Pass 2 of 2
- [00:24:31] Video Encode complete
- [00:24:31] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [00:24:31] Multiplexing M2TS
- [00:24:51] Processing: VID_00310 (10 of 22)
- [00:24:51] Extracting A/V streams [VID_00310]
- [00:25:15] Reencoding video [VID_00310]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 9,330 frames
- Convert: 1280x720, 59.940fps, 18,660 frames
- Bitrate: 4,169 Kbs
- [00:25:15] Reencoding: VID_00310, Pass 1 of 2
- [00:29:57] Reencoding: VID_00310, Pass 2 of 2
- [00:36:42] Video Encode complete
- [00:36:42] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [00:36:42] Multiplexing M2TS
- [00:36:48] Processing: VID_00311 (11 of 22)
- [00:36:48] Extracting A/V streams [VID_00311]
- [00:37:10] Reencoding video [VID_00311]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 7,477 frames
- Convert: 1280x720, 23.976fps, 7,477 frames
- Bitrate: 4,170 Kbs
- [00:37:10] Reencoding: VID_00311, Pass 1 of 2
- [00:39:30] Reencoding: VID_00311, Pass 2 of 2
- [00:43:56] Video Encode complete
- [00:43:56] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [00:43:56] Multiplexing M2TS
- [00:44:02] Processing: VID_00312 (12 of 22)
- [00:44:02] Extracting A/V streams [VID_00312]
- [00:44:21] Reencoding video [VID_00312]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 5,898 frames
- Convert: 1280x720, 23.976fps, 5,898 frames
- Bitrate: 4,170 Kbs
- [00:44:22] Reencoding: VID_00312, Pass 1 of 2
- [00:46:14] Reencoding: VID_00312, Pass 2 of 2
- [00:49:40] Video Encode complete
- [00:49:40] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [00:49:40] Multiplexing M2TS
- [00:49:46] Processing: VID_00313 (13 of 22)
- [00:49:46] Extracting A/V streams [VID_00313]
- [00:49:57] Reencoding video [VID_00313]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 3,169 frames
- Convert: 1280x720, 59.940fps, 6,338 frames
- Bitrate: 4,169 Kbs
- [00:49:57] Reencoding: VID_00313, Pass 1 of 2
- [00:51:34] Reencoding: VID_00313, Pass 2 of 2
- [00:53:53] Video Encode complete
- [00:53:53] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [00:53:53] Multiplexing M2TS
- [00:53:57] Processing: VID_00314 (14 of 22)
- [00:53:57] Extracting A/V streams [VID_00314]
- [00:54:06] Reencoding video [VID_00314]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,531 frames
- Convert: 1280x720, 23.976fps, 1,531 frames
- Bitrate: 4,171 Kbs
- [00:54:06] Reencoding: VID_00314, Pass 1 of 2
- [00:54:37] Reencoding: VID_00314, Pass 2 of 2
- [00:55:22] Video Encode complete
- [00:55:22] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [00:55:22] Multiplexing M2TS
- [00:55:27] Processing: VID_00315 (15 of 22)
- [00:55:27] Extracting A/V streams [VID_00315]
- [00:55:40] Reencoding video [VID_00315]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 4,096 frames
- Convert: 1280x720, 59.940fps, 8,192 frames
- Bitrate: 4,170 Kbs
- [00:55:40] Reencoding: VID_00315, Pass 1 of 2
- [00:57:46] Reencoding: VID_00315, Pass 2 of 2
- [01:00:46] Video Encode complete
- [01:00:46] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [01:00:46] Multiplexing M2TS
- [01:00:51] Processing: VID_00316 (16 of 22)
- [01:00:51] Extracting A/V streams [VID_00316]
- [01:02:14] Reencoding video [VID_00316]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 30,649 frames
- Convert: 1280x720, 59.940fps, 61,298 frames
- Bitrate: 4,169 Kbs
- [01:02:14] Reencoding: VID_00316, Pass 1 of 2
- [01:17:49] Reencoding: VID_00316, Pass 2 of 2
- [01:45:04] Video Encode complete
- [01:45:04] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [01:45:04] Multiplexing M2TS
- [01:45:15] Processing: VID_00317 (17 of 22)
- [01:45:15] Extracting A/V streams [VID_00317]
- [01:45:23] Reencoding video [VID_00317]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 2,521 frames
- Convert: 1280x720, 59.940fps, 5,042 frames
- Bitrate: 4,173 Kbs
- [01:45:23] Reencoding: VID_00317, Pass 1 of 2
- [01:46:59] Reencoding: VID_00317, Pass 2 of 2
- [01:49:25] Video Encode complete
- [01:49:25] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [01:49:25] Multiplexing M2TS
- [01:49:29] Processing: VID_00318 (18 of 22)
- [01:49:29] Extracting A/V streams [VID_00318]
- [01:49:59] Reencoding video [VID_00318]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 9,776 frames
- Convert: 1280x720, 23.976fps, 9,776 frames
- Bitrate: 4,172 Kbs
- [01:49:59] Reencoding: VID_00318, Pass 1 of 2
- [01:53:38] Reencoding: VID_00318, Pass 2 of 2
- [02:01:31] Video Encode complete
- [02:01:31] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [02:01:31] Multiplexing M2TS
- [02:01:38] Processing: VID_00319 (19 of 22)
- [02:01:38] Extracting A/V streams [VID_00319]
- [02:02:58] Reencoding video [VID_00319]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 29,478 frames
- Convert: 1280x720, 59.940fps, 58,956 frames
- Bitrate: 4,172 Kbs
- [02:02:58] Reencoding: VID_00319, Pass 1 of 2
- [02:19:04] Reencoding: VID_00319, Pass 2 of 2
- [02:44:45] Video Encode complete
- [02:44:45] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [02:44:45] Multiplexing M2TS
- [02:44:57] Processing: VID_00320 (20 of 22)
- [02:44:57] Extracting A/V streams [VID_00320]
- [02:52:27] Reencoding video [VID_00320]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 153,101 frames
- Convert: 1280x720, 59.940fps, 306,202 frames
- Bitrate: 4,173 Kbs
- [02:52:27] Reencoding: VID_00320, Pass 1 of 2
[02:54:57]PHASE ONE aborted by user request
----------------------
[04-08-16] BD Rebuilder v0.50.14
[14:35:59] Source: MY_SOURCE
- Input BD size: 46.18 GB
- Approximate total content: [05:17:45.337]
- Target BD size: 7.84 GB
- Windows Version: 6.2 [9200]
- Resize: 1080p to 720p enabled
- Auto Quality: High Quality (Default), Two Pass
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[14:36:03] - Aborted per user request
----------------------
[04-08-16] BD Rebuilder v0.50.14
[14:38:55] Source: MY_SOURCE
- Input BD size: 46.18 GB
- Approximate total content: [05:17:45.337]
- Target BD size: 7.84 GB
- Windows Version: 6.2 [9200]
- Resize: 1080p to 720p enabled
- Auto Quality: High Quality (Default), Two Pass
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[14:39:01] - Aborted per user request

Inf file in Working folder:

[Status]
LABEL=MY_SOURCE
VERSION=v0.50.14
SOURCE_SIZE=30384267392
SOURCE_VIDEO_SIZE=30379051008
TARGET_SIZE=8422162432
REDUCTION=.277064153379363
RESIZE_1080=-1
RESIZE_1440=0
AUDIO_TO_KEEP=eng;
KEEP_HD_AUDIO=0
SUBS_TO_KEEP=ell;eng;fra;fre;ger;ita;rus;spa;
BACKUP_MODE=0
MOVIEONLY_TYPE=0
USE_LAVF=0
INSTANCES=1
DGDECNV=0
DGDECIM=0
FRIMSOURCE=0
FFMS2=0
SSIF_MODE=0
QUICK=0
ENCODE_STEP=1.5
COMPLETED=19
REBUILD_COMPLETE=0
[00231]
AUDIO=10
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=23540860
RATE=8536
SPLITS=1
NSTART=27000000
NEND=27900900
NSIZE=1579008
FLINK=0
MLINK=0
[00295]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=335846652
RATE=8468
SPLITS=1
NSTART=27000000
NEND=39954191
NSIZE=329367552
FLINK=-1
MLINK=0
[00304]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=349647053
RATE=8461
SPLITS=1
NSTART=27000000
NEND=40496608
NSIZE=342921216
FLINK=-1
MLINK=0
[00305]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=142833389
RATE=4172
SPLITS=1
NSTART=27000000
NEND=37912151
NSIZE=141576192
FLINK=0
MLINK=0
[00306]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=67619754
RATE=4170
SPLITS=1
NSTART=27000000
NEND=32168163
NSIZE=67952640
FLINK=0
MLINK=0
[00307]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=133218899
RATE=4172
SPLITS=1
NSTART=27000000
NEND=37178293
NSIZE=131328000
FLINK=0
MLINK=0
[00308]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=43988673
RATE=4170
SPLITS=1
NSTART=27000000
NEND=30361858
NSIZE=44752896
FLINK=0
MLINK=0
[00309]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=1194476070
RATE=4171
SPLITS=1
NSTART=27000000
NEND=118279938
NSIZE=1184335872
FLINK=0
MLINK=0
[00310]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=183259186
RATE=4169
SPLITS=1
NSTART=27000000
NEND=41008994
NSIZE=182691840
FLINK=0
MLINK=0
[00311]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=183613260
RATE=4170
SPLITS=1
NSTART=27000000
NEND=41033394
NSIZE=182145024
FLINK=0
MLINK=0
[00312]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=144848891
RATE=4170
SPLITS=1
NSTART=27000000
NEND=38069808
NSIZE=143671296
FLINK=0
MLINK=0
[00313]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=62238840
RATE=4169
SPLITS=1
NSTART=27000000
NEND=31758253
NSIZE=62588928
FLINK=0
MLINK=0
[00314]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=37606817
RATE=4171
SPLITS=1
NSTART=27000000
NEND=29873495
NSIZE=37502976
FLINK=0
MLINK=0
[00315]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=80477091
RATE=4170
SPLITS=1
NSTART=27000000
NEND=33150144
NSIZE=80289792
FLINK=0
MLINK=0
[00316]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=601940589
RATE=4169
SPLITS=1
NSTART=27000000
NEND=73019472
NSIZE=601024512
FLINK=0
MLINK=0
[00317]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=49558540
RATE=4173
SPLITS=1
NSTART=27000000
NEND=30785281
NSIZE=49846272
FLINK=0
MLINK=0
[00318]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=240174990
RATE=4172
SPLITS=1
NSTART=27000000
NEND=45348330
NSIZE=238147584
FLINK=0
MLINK=0
[00319]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=579405778
RATE=4172
SPLITS=1
NSTART=27000000
NEND=71261216
NSIZE=578433024
FLINK=0
MLINK=0
[00320]
AUDIO=1
PGS=
APULLDOWN=0
S1440=0
VIDEO2=0
V2MBRATE=0
M2TS_TARGET=3009672306
RATE=4173
SPLITS=1

[Weirdo]

Update: I reloaded the source path (even though it was already loaded at BD-RB startup), and after that BD-RB picked up the previous job and is now resuming. :)

The overall progress shows 116% and increasing - a bit alarming.

---------------------------------------

Some more info that wouldn't fit in the previous post:

[04-08-16] Checking System Settings
- BD-Rebuilder v0.50.14
- Windows Version: 6.2 [9200]
- Working Path Free Space: 46.60GB
- AVISYNTH Version: 2.6.0.6, Ok
- LAVFILTERS: Ok
- AnyDVD settings check: Ok.
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[04-08-16] Systems Settings Check complete

[wakko709]

Uninstall and reinstall BD-RB, AVISYNTH, and LAV filters (or FFDSHOW) and see if that fixes it.

it doesnt!

[jdobbs]

it doesnt!Then the best guess is that you either have a corrupt source or one that hasn't been decrypted correctly. That's pretty much the only thing that could cause an error in demuxing.

[AmigaFuture]

FYI: 59.94 fps video doesn't exist. 29.97 fps video does. FPS = frames per second, not fields per second.

For 720p (and 4k) it does... but then you wouldn't need to IVTC it.

What I know is, I became excited when Comcast announced the change to MPEG-4 from MPEG-2. With a very slow migration. Now, some of what I like is encoded with my TiVo device as MPEG-4. I understand 59.940 doesn't actually exist, which is why the render down. BD-RB went too low with 23.976, and another software I use sometimes allowed for 29.97. I was wondering if something might be broken or just not detecting correctly.

[MrVideo]

What I know is, I became excited when Comcast announced the change to MPEG-4 from MPEG-2. With a very slow migration. Now, some of what I like is encoded with my TiVo device as MPEG-4. I understand 59.940 doesn't actually exist, which is why the render down. BD-RB went too low with 23.976, and another software I use sometimes allowed for 29.97. I was wondering if something might be broken or just not detecting correctly.
The only difference between the the MPEG-2 days and the MPEG-4 days is that the video is now H.264. Any produced program that is 1080, will be 1080i @ 29.97 fps. Those programs will normally also be sourced from 23.976 video, meaning that it will be run thru 2:3 pulldown to get to the 29.97 frame rate. Stuff produced on video, like live sports, will be be 1080i as well, but with pure 29.97 frame source. When it comes to comes to produced programs aired via a 720p channel, the frame rate will indeed be 59.94. Again 2:3 pulldown will be used for 23.976 source material.

So, I'm confused by your render down statement. There is no 59.94 1080i source to render down, only 720p. For 1080i you either keep it at 1080i29.97 or you IVTC to 1080p23.976. Same goes for 720p. You either keep it at 720p59.94 or IVTC it to 720p23.976.

What do you mean that "BD-RB went too low with 23.976?" And why would the software "sometimes allowed for 29.97?" 29.97 is a valid frame rate for all 1080i source material.

There are some who prefer to take 1080i29.97 video (sports for example) and de-interlace it to 1080p29.97. IMHO, that ruins time spacial information. I don't care for sports, so I never deal with it.

So, if you think that you have 1080i59.94 source material coming from Comcast, you don't.

[AmigaFuture]

Then I'm curious why:

[04/08/16] BD Rebuilder v0.50.12
[19:20:52] Source: THE_STORY_OF_GOD_WITH_MORGAN_FREEMAN_-_''BEYOND_DEATH''_(RECORDED_APR_3,_2016,_NGCPHD)_00000
- Input BD size: 1.04 GB
- Approximate total content: [00:50:04.017]
- Windows Version: 6.1 [7601]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV Container, 1280x720, Intact Audio
- Decoding/Frame serving: DGDecNV
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[19:20:53] PHASE ONE, Encoding
- [19:20:53] Processing: VID_00000 (1 of 1)
- [19:20:53] Extracting A/V streams [VID_00000]
- [19:21:02] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1280x720
- Rate/Length: 59.940fps, 180,061 frames
- Inverse Telecining in effect (IVTC)
- Bitrate: 2,352 Kbs
- [19:21:02] Reencoding: VID_00000, Pass 1 of 2
- [19:40:19] Reencoding: VID_00000, Pass 2 of 2
- [19:59:29] Video Encode complete
- [19:59:29] Processing audio tracks
- Track 4352 (eng): Keeping original audio
[19:59:29]PHASE ONE complete
[19:59:29]PHASE TWO - Rebuild Started
- [19:59:29] Building ALTERNATE OUTPUT Structure
[19:59:49] - Encode and Rebuild complete
[19:59:49] JOB: THE_STORY_OF_GOD_WITH_MORGAN_FREEMAN_-_''BEYOND_DEATH''_(RECORDED_APR_3,_2016,_NGCPHD) finished.


Output is 23.976fps when it should be 29.97fps. Which is why the video is jerky.

Side note...to everyone.. Go to Target and comment about the 24.99$ version of Star Wars: The Force Awakens not being any different than the 19.99$ version other than the front cover. I got mine for "Noticing the Force" reduced rate of 14.99$. At eBay it's 16.99$ (by Target). In line I commented about the price difference and why and...interaction followed about "The Force" and a reduction.
Maybe you'll get the same reaction?? I love the Extras. Before I went shopping, I had a feeling.

[Sharc]

Then I'm curious why:

[04/08/16] BD Rebuilder v0.50.12
[19:20:52] Source: THE_STORY_OF_GOD_WITH_MORGAN_FREEMAN_-_''BEYOND_DEATH''_(RECORDED_APR_3,_2016,_NGCPHD)_00000
- Input BD size: 1.04 GB
- Approximate total content: [00:50:04.017]
- Windows Version: 6.1 [7601]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV Container, 1280x720, Intact Audio
- Decoding/Frame serving: DGDecNV
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[19:20:53] PHASE ONE, Encoding
- [19:20:53] Processing: VID_00000 (1 of 1)
- [19:20:53] Extracting A/V streams [VID_00000]
- [19:21:02] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1280x720
- Rate/Length: 59.940fps, 180,061 frames
- Inverse Telecining in effect (IVTC)
- Bitrate: 2,352 Kbs
- [19:21:02] Reencoding: VID_00000, Pass 1 of 2
- [19:40:19] Reencoding: VID_00000, Pass 2 of 2
- [19:59:29] Video Encode complete
- [19:59:29] Processing audio tracks
- Track 4352 (eng): Keeping original audio
[19:59:29]PHASE ONE complete
[19:59:29]PHASE TWO - Rebuild Started
- [19:59:29] Building ALTERNATE OUTPUT Structure
[19:59:49] - Encode and Rebuild complete
[19:59:49] JOB: THE_STORY_OF_GOD_WITH_MORGAN_FREEMAN_-_''BEYOND_DEATH''_(RECORDED_APR_3,_2016,_NGCPHD) finished.


Output is 23.976fps when it should be 29.97fps. Which is why the video is jerky.

Upload a 2s sample of your captured video source.

[AmigaFuture]

As requested. You didn't specify where, this is after the commercials at the start.

If you want during the episode I'll resend. :) But should show the same information.

[Sharc]

It would be better/faster to upload to a filehoster like mediafire or similar than attach it here.

[MrVideo]

Then I'm curious why:

- Inverse Telecining in effect (IVTC)

Why is this on? Did you do it, or is BDRB doing it?

If autodetection is occuring, it is very possible that there is enough 2:3 pulldown material in the show to make it "think" that it is 2:3 and therefore turn on IVTC. The portions with Morgan Freeman, or other pure video source material, are 29.97 and that doesn't work out when going to 23.976, as you've discovered.

If it is indeed a mixture of 2:3 material and pure video, a 2 second source isn't going to be enough to figure this out.

The fix might be as simple as forcing no IVTC.

[AmigaFuture]

Why is this on? Did you do it, or is BDRB doing it?

If autodetection is occuring, it is very possible that there is enough 2:3 pulldown material in the show to make it "think" that it is 2:3 and therefore turn on IVTC. The portions with Morgan Freeman, or other pure video source material, are 29.97 and that doesn't work out when going to 23.976, as you've discovered.

If it is indeed a mixture of 2:3 material and pure video, a 2 second source isn't going to be enough to figure this out.

The fix might be as simple as forcing no IVTC.

I agree.. 2 seconds isn't enough. Autodetection leaves the Video as it is. That's what software players show. I haven't used my Standalone yet, but usually MPC-HC is petty good at detecting what's happening. I've striving to be as good as JD, and others here...but not there, yet.

[Sharc]

..... but usually MPC-HC is petty good at detecting what's happening.....
You would actually have to inspect the stream by separating the fields and stepping through the fields using avisynth or VDub, for example. The field pattern will let you draw some conclusions.
Like MrVideo wrote, I suspect your clip is a mixture of pure video (or fake-interlaced progressive) and 3:2 pulldown (or telecined) movie. This is not unusual for mixtures of commercials with movies. So the sample clip for inspection should include such a transition.
If you are not sure what it is, don't IVTC.

Edit:
When you make a search for "IVTC" in the changes.txt of DB-RB you get an impression of the complexity of this topic .... :)

[AmigaFuture]

Indeed! I didn't think there's anything simple about IVTC. I thought that years ago, that it was simple...erm, nope! :) If I don't choose IVTC when the output is either as Full Backup or using Alternative MKV the video is 1280x720@59.94fps. This is what MPC-HC shows. I've tried different various of Deinterlace with and without IVTC. Nothing is causing BD-RB to produce 29.97 which would be smooth. For now, Handbrake does it by only changing the video frame rate to 29.97. I prefer not to transcode but...ehh...it works for now.

[Lathe]

@Lathe
I am not sure whether it's a terribly good idea to change --deblock and --direct between passes. They should better be the same for pass1 and pass2, as the speed gain for pass1 is minimal with the lower settings. The other parameters are less critical and can be changed for pass2 (I am not sure about --qcomp though).

Anyway, the discussion has nothing to to with a BD-RB bug report.

Edit:
About changing --direct between passes, see here:
http://forum.doom9.org/showpost.php?p=1113961&postcount=30
So in best case, it has no effect at all.

Or the discussion here:
http://forum.doom9.org/showthread.php?t=135533

Thank you VERY much for this Sharc! Like I said, I'm really not an expert, so I had no idea that different settings for both passes made any difference. I guess I just assumed that all important changes were done in the final pass, I guess not.

I will definitely check out the links you gave me. I can NEVER learn enough about x264 encoding :) Thanks!

***EDIT

Yes, that discussion was helpful. But, I have NO idea what BDRB does on it's first pass...???

[MrVideo]

Indeed! I didn't think there's anything simple about IVTC. I thought that years ago, that it was simple...erm, nope! :)
I've never found IVTC to be difficult. There are video sources I deal with I know are from 23.976 mastered sources (all drama TV shows, for example). For material that I do not know, I look thru the video to see if it is pure video, a combo, or pure 2:3 pulldown. If the source is not pure 2:3 pulldown, I leave it alone. I do not deinterlace 1080i material. I personally do not like deinterlacing.
If I don't choose IVTC when the output is either as Full Backup or using Alternative MKV the video is 1280x720@59.94fps. This is what MPC-HC shows. I've tried different various of Deinterlace with and without IVTC.
If your source is 720p59.94, and it does not have pure 2:3 pulldown material throughout, then it should be left alone, which means 720p59.94. What is wrong with that? You NEVER, I repeat NEVER, deinterlace and IVTC 2:3 pulldown material. If the deinterlacing is done first, then there will be nothing to IVTC. IVTC in reality is a deinterlacer for 1080i 2:3 video. Deinterlacing 720p accomplishes nothing, as there is no interlacing to remove.
Nothing is causing BD-RB to produce 29.97 which would be smooth. For now, Handbrake does it by only changing the video frame rate to 29.97. I prefer not to transcode but...ehh...it works for now.
To take 720p59.94 to 720p29.97 with pure source video would mean that a frame would have to be dropped, resulting in a spatial time issue, i.e., it would not be as smooth as the original video. Or worse yet, two consecutive frames are merged. Yuch! If the 720p59.94 video is converted to 29.97 and it has 2:3 pulldown, the result would be more jerky than it already is (the 2:3 pulldown portion).

I repeat the point of this posting.... there is nothing wrong with 720p59.94 staying 59.94 with pure video or a combo of pure video and 2:3 video.

I do not understand your need to force 720p29.97.

[Sharc]

Thank you VERY much for this Sharc! Like I said, I'm really not an expert, so I had no idea that different settings for both passes made any difference. I guess I just assumed that all important changes were done in the final pass, I guess not.

I will definitely check out the links you gave me. I can NEVER learn enough about x264 encoding :) Thanks!

***EDIT

Yes, that discussion was helpful. But, I have NO idea what BDRB does on it's first pass...???

x264 defines a number of standardized --presets. For 2-pass encodes, the first pass is run per default with a reduced set of parameters as "fast firstpass". In this case, Pass1 and Pass2 are aligned for maximum speed of Pass1 without compromising the final quality.
BD-RB follows the same strategy, but in addition it takes care of blu-ray compliant settings for BD output, and playback device compatibility for alternate outputs as much as possible.
So when you tweak anything with the passes you should know what you are doing, otherwise you risk to worsen the final result or produce playback issues.
The only tweak which I occasionally use is --tune-film, for both passes.

(Btw, this discussion is unrelated to a BD-RB bug report).

[Sharc]

I've never found IVTC to be difficult. There are video sources I deal with I know are from 23.976 mastered sources (all drama TV shows, for example). For material that I do not know, I look thru the video to see if it is pure video, a combo, or pure 2:3 pulldown. If the source is not pure 2:3 pulldown, I leave it alone. I do not deinterlace 1080i material. I personally do not like deinterlacing.

Agree, once you know what the source is it's not too difficult to deal with it. What I meant is that it is probably not so easy to do it in a fully automated process.
(Btw. I also prefer to encode interlaced sources as interlaced, unless there is a specific reason - like vertical resizing - for (bob-)deinterlacing, possibly followed by re-interlacing.)

[AmigaFuture]

I've never found IVTC to be difficult. There are video sources I deal with I know are from 23.976 mastered sources (all drama TV shows, for example). For material that I do not know, I look thru the video to see if it is pure video, a combo, or pure 2:3 pulldown. If the source is not pure 2:3 pulldown, I leave it alone. I do not deinterlace 1080i material. I personally do not like deinterlacing.

In the beginning with DVDs I didn't either. I don't use deinterlace unless I have to, I don't like the look of it. I also don't like the lines which is why I'm glad IVTC usually does very well without deinterlacing. I've done a lot of stepping through frames to know what 3:2 / 2:3 looks like and so on. I concur.

If your source is 720p59.94, and it does not have pure 2:3 pulldown material throughout, then it should be left alone, which means 720p59.94. What is wrong with that? You NEVER, I repeat NEVER, deinterlace and IVTC 2:3 pulldown material. If the deinterlacing is done first, then there will be nothing to IVTC. IVTC in reality is a deinterlacer for 1080i 2:3 video. Deinterlacing 720p accomplishes nothing, as there is no interlacing to remove.

This is why I've considered leaving this particular source alone. VideoReDo TV Suite shows that's it's progressive, totally, but because of the non-bias content of the series, as it seems so far, I want to make a Blu-ray of it once I have more episodes. Blu-ray doesn't have 59.94 720P video, right? I haven't done enough research.. I think JD has commented (??) and others (?) that that's outside the BD or AVCHD specs. I'm going to check around a bit more when I create more time to do so. I did expected that BD-RB would notice it and at lease change the frame rate to 29.97. Which is why I wondered if something is broken or ...?? :) I don't have anything against pure progressive, I love the look and flow.

To take 720p59.94 to 720p29.97 with pure source video would mean that a frame would have to be dropped, resulting in a spatial time issue, i.e., it would not be as smooth as the original video. Or worse yet, two consecutive frames are merged. Yuch! If the 720p59.94 video is converted to 29.97 and it has 2:3 pulldown, the result would be more jerky than it already is (the 2:3 pulldown portion).

I think I agree with you here. I'm not entirely sure I understand what you mean by spatial time..I have something like that with time not always feeling the "passage" of it, but I'm not sure it's related.. When I used HandBrake and got the video to 29.97 it looked like it flowed as it should. I didn't see any jerking or PAL vs NTSC distortions..type differences. I hope that makes sense. :) There's a "frame rate flicker" difference between NTSC and PAL (without going into a lot of details). I hope the relating is coming across here, is this sort of the spatial time you're meaning?

I repeat the point of this posting.... there is nothing wrong with 720p59.94 staying 59.94 with pure video or a combo of pure video and 2:3 video.

I do not understand your need to force 720p29.97.

I was thinking pure BD compatible. I'll burn a test soon. I also agree about the Comcast comment. I was hoping the video would become 23.976 or 29.97, but it was a very small hope AND wouldn't have to be rerendered. Haha, so much for that. I was thinking, "Awesome, just remove the commercials and burn!" Silly me..

[sneaker_ger]

Blu-ray doesn't have 59.94 720P video, right?
Wrong.
http://forum.doom9.org/showthread.php?t=154533
http://www.x264bluray.com/home/720p-encoding

[AmigaFuture]

Most simplest of terms..."Wrong.", haha. Ask inside, and get an answer in some way. Thanks. Some absorbing to do.

[jdobbs]

Most simplest of terms..."Wrong.", haha. Ask inside, and get an answer in some way. Thanks. Some absorbing to do.If the source was 1280x720@59.94fps and you selected 1280x720 as the output in an ALTERNATE format, the frame rate should have remained unchanged. BD-RB shouldn't use inverse telecining unless one of two things exist:

1. The source is flagged as telecined (which would imply a 29.97 source to BD-RB) -- and you have iVTC selected from the SETUP menu.

2. On a 720 source, the setting "IVTC_720h" has been set to "1" in BD-RB's INI file. This setting is meant for hard telecined 720 sources -- and shouldn't normally be set. It's meant for very specific conditions (a 29.97fps telecined original source that was converted to 29.97fps via hard encoding) .

If neither of those conditions exist and you got 23.976 as output -- there must be something wrong with BD-RB's logic. I'll have to look around for (or create) a 1280x720/59.94 source and test it.

[Edit] I just looked at the code -- and even #2 above requires a rate of 29.97fps for inverse telecining. So I have no idea how it is even possible for a 59.94fps source to be output to 23.976fps or for the iVTC flag to be set??? Again, I'll have to do some testing to see.

[Sharc]

His attachment (2s clip) is still pending approval.......

[AmigaFuture]

Shazbot, I forgot all about the IVTC_720h... I made a note of it somewhere.

I did use the IVTC via IVTC_SELECTION=1, otherwise BD-RB doesn't activate it with this source. That's why I initially wondered if something is broken. I don't understand why with HandBrake changing the frame rate to 29.97 and "constant frame rate" will create a smooth video (aren't any repeated frames that I can see doing a "step by step" check. I was attempting to get a smaller file size but from MrVideo's comments and the info from sneaker_ger looks like it is video and pure progressive so there isn't a need. Other than smaller file size. Hmm.. I could make a 1 minute sample available with a link? I don't want to reinvent the Wheel, but I would like an answer to the 29.97 smooth video with HandBrake 0.10.5.0 output but not with BD-RB. I'm not in any hurry. :) I appreciate the help, everyone.

[jdobbs]

His attachment (2s clip) is still pending approval.......I looked at it -- it's 2s of black. I don't believe it has enough information to even use as a check. Also, BD-RB makes decisions based upon information contained in the CLPI and MPLS files as well as the video itself -- so it wouldn't contain all the information I'd need.

I approved the attachment, though, in case anyone else has anything they want to check.

[Sharc]

Shazbot, I forgot all about the IVTC_720h... I made a note of it somewhere.

I did use the IVTC via IVTC_SELECTION=1, otherwise BD-RB doesn't activate it with this source. That's why I initially wondered if something is broken. I don't understand why with HandBrake changing the frame rate to 29.97 and "constant frame rate" will create a smooth video (aren't any repeated frames that I can see doing a "step by step" check. I was attempting to get a smaller file size but from MrVideo's comments and the info from sneaker_ger looks like it is video and pure progressive so there isn't a need. Other than smaller file size. Hmm.. I could make a 1 minute sample available with a link? I don't want to reinvent the Wheel, but I would like an answer to the 29.97 smooth video with HandBrake 0.10.5.0 output but not with BD-RB. I'm not in any hurry. :) I appreciate the help, everyone.

I guess handbrake simply drops every second frame of the 720p 59.97 source which would still result in judder-free playback at half temporal resolution (assuming your source is true progressive i.e. not telecined or pulldown)

[jdobbs]

His attachment (2s clip) is still pending approval.......To add: I just imported the 2 second .ts file that was posted. I ran it through BD-RB and output to an MKV. The output remained 59.94fps. Here's the log:[04/10/16] BD Rebuilder v0.50.16
[16:24:01] Source: 2_SECOND_00000
- Input BD size: 0.00 GB
- Approximate total content: [00:00:00.033]
- Windows Version: 6.1 [7601]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: MKV Container, NO_RESIZE, Auto-AAC
- Quality: High Quality (Default)
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=1 DTS=1 HD=0 Kbs=640
[16:24:05] PHASE ONE, Encoding
- [16:24:05] Processing: VID_00000 (1 of 1)
- [16:24:05] Extracting A/V streams [VID_00000]
- [16:24:09] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1280x720
- Rate/Length: 59.940fps, 2 frames
- [16:24:09] Reencoding: VID_00000, Pass 1 of 1
- [16:24:09] Video Encode complete
- [16:24:09] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AAC...
[16:24:10]PHASE ONE complete
[16:24:10]PHASE TWO - Rebuild Started
- [16:24:10] Building ALTERNATE OUTPUT Structure
[16:24:10] - Encode and Rebuild complete
[16:24:10] JOB: 2_SECOND finished.

Notice that no inverse telecining was performed. It also looks like it isn't really 2 seconds -- but is 2 frames.

[AmigaFuture]

Right....that's what I noticed when IVTC wasn't enabled through IVTC_SELECTION=1.

[MrVideo]

If the source was 1280x720@59.94fps and you selected 1280x720 as the output in an ALTERNATE format, the frame rate should have remained unchanged. BD-RB shouldn't use inverse telecining unless one of two things exist:

1. The source is flagged as telecined (which would imply a 29.97 source to BD-RB) -- and you have iVTC selected from the SETUP menu.
Bad logic. More in a moment.
2. On a 720 source, the setting "IVTC_720h" has been set to "1" in BD-RB's INI file. This setting is meant for hard telecined 720 sources -- and shouldn't normally be set. It's meant for very specific conditions (a 29.97fps telecined original source that was converted to 29.97fps via hard encoding) .
Again, bad logic.
If neither of those conditions exist and you got 23.976 as output -- there must be something wrong with BD-RB's logic. I'll have to look around for (or create) a 1280x720/59.94 source and test it.

[Edit] I just looked at the code -- and even #2 above requires a rate of 29.97fps for inverse telecining. So I have no idea how it is even possible for a 59.94fps source to be output to 23.976fps or for the iVTC flag to be set??? Again, I'll have to do some testing to see.
720p59.94 video can indeed have 2:3 pulldown video directly from the 23.976 video master. U.S. OTA networks Fox and ABC get their dramas from the production companies. "Cable" channels that are 720p also get their dramas the same way. All production in the U.S., and world wide, is done in 1080p23.976 or 1080p25 or 1080i50. Some are now starting to produce in 4K (Daredevil from Netflix). Fox/ABC either get a 1080p23.976 master from the production company and convert it to 720p59.94 with 2:3 pulldown, or they get it already converted to 720p59.94. I have no idea if an IVTC flag even exists in the OTA video. What is worse is that ABC tends to speed up the video so that they can get another 30-60 seconds of promo/commercial time into the broadcast, which totally messes with the 2:3 pulldown.

Take a look at the following: https://en.wikipedia.org/wiki/Three-two_pull_down?sa=X&ved=0ahUKEwis5oPegYXMAhVMeT4KHYh8B_EQ9QEIGTAA

Replace 1080i fields with 720p frames. The first frame of 1080p23.976 is transferred to two frames of 720p59.94 and the next 1080p23.976 frame is transferred to three frames of 720p59.94. No 29.97 involved at all.

Here is my AVS script for dealing with 720p 2:3 pulldown video:
LoadPlugin("C:\Program Files (x86)\DGAVCDecNV\DGDecodeNV.dll")
dgsource("=DRIVE=\=FILENAME=")
v1=last
v2=v1.crop(0,0,-0,-320)
v2.TDecimate(clip2=v1,cycle=5,cycleR=3)
The "=DRIVE=\=FILENAME=" is replaced in the script with the appropriate information for the job. The cropping is done to eliminate the bottom portion of the video from interfering with frame detection because of snipes and/or animated bugs.

So, forget the idea that 29.97 is involved with 720p 2:3 pulldown.

[MrVideo]

VideoReDo TV Suite shows that's it's progressive.
Correct. But that has nothing to do with it possibly having 2:3 pulldown content.
I'm not entirely sure I understand what you mean by spatial time.
The time between images makes up spatial time. In other words, the sampling of space and time. The more images captured per second provides smoother motion. So, motion captured at 59.94 fps will have more spatial info that if it were captured at 29.97 fps.
I was thinking pure BD compatible. I'll burn a test soon. I also agree about the Comcast comment. I was hoping the video would become 23.976 or 29.97, but it was a very small hope AND wouldn't have to be rerendered. Haha, so much for that. I was thinking, "Awesome, just remove the commercials and burn!" Silly me..
Actually you can just edit out the commercials and burn to Blu-ray, since 720p59.94 is part of the Blu-ray spec. 720p29.97 is NOT part of the Blu-ray spec.

[Lathe]

x264 defines a number of standardized --presets. For 2-pass encodes, the first pass is run per default with a reduced set of parameters as "fast firstpass". In this case, Pass1 and Pass2 are aligned for maximum speed of Pass1 without compromising the final quality.
BD-RB follows the same strategy, but in addition it takes care of blu-ray compliant settings for BD output, and playback device compatibility for alternate outputs as much as possible.
So when you tweak anything with the passes you should know what you are doing, otherwise you risk to worsen the final result or produce playback issues.
The only tweak which I occasionally use is --tune-film, for both passes.

(Btw, this discussion is unrelated to a BD-RB bug report).

Thanks Sharc! This gives me a nice starting point to do some research about what is done on the 'fast first pass' and about coordinating the 2 passes correctly. I was not aware of the relationship between the two. And yeah, --tune-film does include the deblock -1.-1, but as you say on BOTH passes.

And, YES, I think that I have taken MORE than enough time here on this already, sorry! :rolleyes:

[jdobbs]

Correct. But that has nothing to do with it possibly having 2:3 pulldown content.

The time between images makes up spatial time. In other words, the sampling of space and time. The more images captured per second provides smoother motion. So, motion captured at 59.94 fps will have more spatial info that if it were captured at 29.97 fps.

Actually you can just edit out the commercials and burn to Blu-ray, since 720p59.94 is part of the Blu-ray spec. 720p29.97 is NOT part of the Blu-ray spec.It really doesn't matter -- as BD-RB doesn't iVTC anything unless it is a 29.97fps source. A 59.94 source will stay 59.94fps. I went through the code and I can see no way that iVTC will ever be accomplished on a 59.94fps source. I also ran a 1280x720/59.94fps source through it and couldn't make it happen. So I'm confused as to how that log could have possibly occurred.

You could use pulldown flags to turn almost any frame rate into almost any other higher frame rate -- but my intent is to find the progressive source in a 29.97fps telecined stream in order to give better picture quality with less wasted bandwidth.

[MrVideo]

It really doesn't matter -- as BD-RB doesn't iVTC anything unless it is a 29.97fps source. A 59.94 source will stay 59.94fps.
That is unfortunate, because you could possibly be keeping 2:3 video from being IVTC'd to 720p23.976, which will ultimately consume less space.

[AmigaFuture]

My guess of back a few versions, then, is that when BD-RB had some challenges with a 720p 59.94, The Mentalist, that it did not have 2:3 in the progressive video? Because going back to my source archives and current BD-RB version, it rerenders from 59.94 to 23.976 fine with iVTC active via right-click access and nothing else. I'm curious.

@ MrVideo

"The time between images makes up spatial time. In other words, the sampling of space and time." -- Thanks, that IS what I was wondering about.

[MrVideo]

My guess of back a few versions, then, is that when BD-RB had some challenges with a 720p 59.94, The Mentalist, that it did not have 2:3 in the progressive video? Because going back to my source archives and current BD-RB version, it rerenders from 59.94 to 23.976 fine with iVTC active via right-click access and nothing else. I'm curious.

It should have been 2:3 pulldown, as the show is produced like any other: 1080p23.976. A side note to this is that many shows are shot and edited as 1080p23.98 psf (progressive segmented frame).

I don't watch The Mentalist, but it airs on a network that is 1080i.

To add a wrinkle to all of this, GDMX, the satellite feed arm of Warner Bros., sometimes feeds shows to Canada using duplicate frame mode instead of 2:3 pulldown for the 1080i videos they feed. What that means is that every fourth video frame from the original source is duplicated, resulting is a different jerky motion because of a frame being shown twice.

The AVS Decimate function handles IVTCing this just fine. But I prefer to use SelectEvery instead. But to do that, the location of the repeat frame must be known and hap hazard editing of the video will result in that pattern being upset.

Now, as for the original video that brought this conversation about, it was uploaded to my server and I took a look at it. The whole thing was shot 1080p29.97, i.e., pure video. Interesting that it wasn't shot interlaced. When converted to 720p for airing on the NatGeo channel, each source frame was duplicated for the 59.94 frame rate. So, it has to be left alone for Blu-ray inclusion. But, it can be converted to 720p29.97 by dropping every other frame, with no loss of spatial info.

Come to think of it, it could easily have been shot 1080i. When converted to 720p59.94, deinterlacing would have been done to create 1080p29.97 and then converted to 720p59.94. That means spatial info would have been lost doing that. Some vertical resolution might have been compromised as well. But the downconversion from 1080 to 720 already messes with vertical resolution.

[Sharc]

Replace 1080i fields with 720p frames. The first frame of 1080p23.976 is transferred to two frames of 720p59.94 and the next 1080p23.976 frame is transferred to three frames of 720p59.94. No 29.97 involved at all.

This "shortcut" method for converting 1080p23.976 to 720p59.97 produces the worst judder, right? (one repetition every 5 pictures; progressive picture sequence like a a b b b c c d d d e e f f f ........).
I think manual frame inspection is required to identify this case, or is the stream somehow flagged to help an automated detection for IVTC?

P.S.
I think we still don't really know what the OP's stream actually is .....

Edit:
Sorry, I missed that you got the stream and analyzed it.
But, it can be converted to 720p29.97 by dropping every other frame, with no loss of spatial info
..and this is probably what handbrake did (referring to the OP's question).

[MrVideo]

This "shortcut" method for converting 1080p23.976 to 720p59.97 produces the worst judder, right? (one repetition every 5 pictures; progressive picture sequence like a a b b b c c d d d e e f f f ........).
I've not really noticed an issue. But, I watch very little 720p. I get all of my material as either 1080i, which I then convert to 1080p23.986, or already as 1080p23.986. If I do have to view 720p video, it too is already 720p23.976. What is worse for judder is 1080 with the fifth frame a repeat of the previous. At least with the 720p repeat frames, there are 12 a second, vs the 6 for 1080.
I think manual frame inspection is required to identify this case, or is the stream somehow flagged to help an automated detection for IVTC?
There is no reason to flag 720p59.94 with 2:3 pulldown, because it is not meant for IVTC, only viewing. You can count on any drama that airs to have 2:3 pulldown, be it 720p or 1080i. But, a visual inspection is pretty much needed to verify video that you do not know.

[Sharc]

There is no reason to flag 720p59.94 with 2:3 pulldown, because it is not meant for IVTC, only viewing.
Ah yes, good point. Thanks.

[Lathe]

I tried importing the BDMV structure that was ripped to my HDD so that BDMV could sort out all the bloody little separate parts and regroup them into some semblance of order (like you suggested I do with the TNG discs, which worked perfectly!)

However, when I go to import the BDMV folder, BDRB tells me that it is not a Blu-ray format...??? I can just 'browse' to the BDMV folder and it accepts that all right, but then everything is STILL in a million little parts, so I can't bloody identify what is the main film and what are XTras. The Blu-ray is 'THE HEAT' which contains the Theatrical and Unrated versions. I really just want to extract the Theatrical version, primarily because it has all these great commentaries on it (including one by the MST3K group!) But, the way it is now, I can't tell heads or tails of which part is which. And, even if I set it for 'Movie Only', it still maddeningly wants to encode every little part as a separate file.

Is there ANY way at all to get BDMV (or anything else for that matter) to decode the damn thing and just create a simple SINGLE movie file (for that matter, later I DO want to do a separate encode for just the Xtras, but I can't tell what the hell is what.

What should I do...?

[Lathe]

Sorry, never mind...

I've only done this a few times and I forgot when importing a Blu-ray, you DON'T click on the BDMV folder like you do when you use the 'browse' function. You select the folder above it CONTAINING the BDMV & CERTIFICATE folders....

DOHHHHHHHHHH...!

Well, I guess my standing on this board has probably skyrocketed now... :o