BD Rebuilder Beta - Bug Reports Only

[Lathe]

I think he's talking about changing the framerate but staying temporally accurate. You can change the frame rate without reencoding by only changing the internal flags (that indicate framerate) -- but (unless it is using pulldown flags and you're doing iVTC) the video will speed up or slow down and not be accurate temporally.

Hmmm... I don't quite understand the 'accurate temporarally' part. All I know is that with TSMuxer if I take a file and use the drop-down box by the video file where it says 'change the fps to' and I change that, then the 'speed' of the video file WILL indeed either slow down or speed up with reference to the audio track. I think I DO understand that what it is doing is changing the 'headers', right? In other words, it's merely telling the player to render it at such 'n' such frame rate which will either speed it up or slow it down.

So, are what you are saying is that the ACTUAL frame rate doesn't change, but you can kind of 'fool' the player into playing it faster or slower...?

I THINK you can do something similar to that with MKVMerge with the aspect ratio, right? Can't you change the 'headers' or whatever they are in the file when you remux it that will cause the player to play it in a different AR then the ACTUAL file is in? That would be GREAT if I can figure out how to do that, and I have a strong suspicion that SOMEHOW if I could do that then my OPPO would play the 1440x1080 HD 4x3 files correctly instead of stretching them across the screen. But, I've never quite figured out the secret to that. Especially when I have to render a film in a BDMV format in order for my OPPO to recognize and play the HD audio.

Also too... Isn't FLAC a good example of what you were talking about where the size is compressed but none of the original information is lost? And, it seems that I remember that AVI files can be rendered lossless, right? You get a HUGE file, but that is truly lossless, right?

[MrVideo]

Hmmm... I don't quite understand the 'accurate temporarally' part.
In short, space and time. Temporally accurate means something that originally took 10 seconds, plays back taking 10 seconds. That is the time portion. Spatial accuracy is what I was referring to regarding 59.94 fps vs. 29.97 fps. If the 59.94 fps video contains 59.94 unique images, that is its spatial accuracy. If you convert to 29.97 fps, you cut the spatial accuracy in half. While the time it takes hasn't changed, the number of images that show what happens during that time is reduced.
So, are what you are saying is that the ACTUAL frame rate doesn't change, but you can kind of 'fool' the player into playing it faster or slower...?
In a nutshell, yes. That is how slo-mo works. The recording is done at a much higher frame rate and then that file is told to play back at a different frame rate.
I THINK you can do something similar to that with MKVMerge with the aspect ratio, right? Can't you change the 'headers' or whatever they are in the file when you remux it that will cause the player to play it in a different AR then the ACTUAL file is in? That would be GREAT if I can figure out how to do that, and I have a strong suspicion that SOMEHOW if I could do that then my OPPO would play the 1440x1080 HD 4x3 files correctly instead of stretching them across the screen. But, I've never quite figured out the secret to that.
Have you tried playing with the three aspect ratio settings in mkvmerge:
--aspect-ratio <TID:f|a/b>
--aspect-ratio-factor <TID:f|a/b>
--display-dimensions <TID:width>x<height>
Run mkvmerge without any options to get the help output. You should be able to google it as well. There is a really detailed help for this program. I have a printout around here somewhere.

Oh, and you can ask in the Doom9 mkvmerge thread.
Also too... Isn't FLAC a good example of what you were talking about where the size is compressed but none of the original information is lost?
Yes
And, it seems that I remember that AVI files can be rendered lossless, right? You get a HUGE file, but that is truly lossless, right?
AVI is a wrapper. It is the content that could be lossless. As for AVI wrappers containing lossless codecs, I do not know.

[Lathe]

In short, space and time. Temporally accurate means something that originally took 10 seconds, plays back taking 10 seconds. That is the time portion. Spatial accuracy is what I was referring to regarding 59.94 fps vs. 29.97 fps. If the 59.94 fps video contains 59.94 unique images, that is its spatial accuracy. If you convert to 29.97 fps, you cut the spatial accuracy in half. While the time it takes hasn't changed, the number of images that show what happens during that time is reduced.

In a nutshell, yes. That is how slo-mo works. The recording is done at a much higher frame rate and then that file is told to play back at a different frame rate.

Have you tried playing with the three aspect ratio settings in mkvmerge:
--aspect-ratio <TID:f|a/b>
--aspect-ratio-factor <TID:f|a/b>
--display-dimensions <TID:width>x<height>
Run mkvmerge without any options to get the help output. You should be able to google it as well. There is a really detailed help for this program. I have a printout around here somewhere.

Oh, and you can ask in the Doom9 mkvmerge thread.

Yes

AVI is a wrapper. It is the content that could be lossless. As for AVI wrappers containing lossless codecs, I do not know.

Thanks for the cmd line stuff for MKVMerge; I know it has a LOT of options, but I've never really gone through them. I'll check those out concerning the aspect ratio.

Yeah, I understood about the 59.xx Again, I don't remember WHY something rendered a file to 59.xx; it was to correct SOMETHING else, but I don't remember. But, the resulting file played just fine at 59.xx I would THINK that you would NOT want to convert it to half the frame rate and lose half the information (or do a 'blend' either...)

[AmigaFuture]

Also too... Isn't FLAC a good example of what you were talking about where the size is compressed but none of the original information is lost? And, it seems that I remember that AVI files can be rendered lossless, right? You get a HUGE file, but that is truly lossless, right?

Correct, but depends on codec even for AVI. I use FLAC and sometimes APE for my CD backups as well as other sound samples instead of keeping them in "wave".

[Lathe]

Hey, are all you guys all right...???

Has JD introduced an insidious virus into his program that has sucked you all into his Evil world?

:eek:

[AmigaFuture]

Evil is a mental illusion. But he has created a virus that I'm enjoying using. It is propagating my BDs. Haha. Other than that, shhhhhhh....let people sleep for a bit.

[jdobbs]

Has anyone else noticed some weird behavior with DGIndexNV? It seems to be crashing (or at least not running) when BD-RB tries to run it. The result is failed encodes -- and when I investigate there is no .DGI file. The issue appears to be at least partially random, as sometimes it will be ok if I re-run the job. I think it may have started about the same time that I upgraded Windows 10 to version 1703, but I'm not positive that there's a link.

Hey, are all you guys all right...???

Has JD introduced an insidious virus into his program that has sucked you all into his Evil world?It has been unusually quiet here, hasn't it? I guess it's because it has been so long since I've released a new version. I got a little busy with another project and haven't been giving BD-RB the attention it needs.

[gonca]

DGIndexNV is working fine on my system with the Anniversary Update version

[jdobbs]

DGIndexNV is working fine on my system with the Anniversary Update versionGood to know. So I guess it must be something other than the update then. Maybe it's one of the changes I put in for the next release... I'm going to look at it today.

[Ch3vr0n]

@jdobbs No. It's still possible it's that update. Several users on the redfox forums reported issues with anydvd that were fixed after a reinstall of it. You're mixing up the Anniversary update (build 1607) with the Creators Update (build 1701, that you're using). 2 different builds. I can't test that yet as CU has yet to be pushed to my system and i'm not going to do it manually.

[videoh]

Good to know. So I guess it must be something other than the update then. Maybe it's one of the changes I put in for the next release... I'm going to look at it today. All working fine for me too with Creators Update (1703 build 15063.296). Make sure you have the latest DGDecNV version, which you can download from DG site. If you still encounter issues, I can give you a debug build. One thing to remember, a recent change requires you to have a copy of the license.txt file together with DGDecodeNV.dll if it is not in the same directory as DGIndexNV.exe.

I'll do some testing with BDRB today.

[jdobbs]

@jdobbs No. It's still possible it's that update. Several users on the redfox forums reported issues with anydvd that were fixed after a reinstall of it. You're mixing up the Anniversary update (build 1607) with the Creators Update (build 1701, that you're using). 2 different builds. I can't test that yet as CU has yet to be pushed to my system and i'm not going to do it manually.Yeah, you're right, I was thinking "Anniversary" was 1703.

[jdobbs]

All working fine for me too with Creators Update (1703 build 15063.296). Make sure you have the latest DGDecNV version, which you can download from DG site. If you still encounter issues, I can give you a debug build. One thing to remember, a recent change requires you to have a copy of the license.txt file together with DGDecodeNV.dll if it is not in the same directory as DGIndexNV.exe.

I'll do some testing with BDRB today.I thought I was using the latest... but it turns out I was using v2051. I just updated to v2053 and it seems to be working on a job that I'd had problems with consistently. I'll let you know if I find anything else -- but right now it seems to be working.

Thanks

[videoh]

Good to hear. Those earlier versions had a race issue that can account for the things you saw.

[AmigaFuture]

I also won't go Windows 10, I just..do....not...like....the Metro GUI at all and all the hidden snooping. Maybe if StarDock gets a Win7 Skin made, which I also haven't checked for in a while. Anyway, DGIndexNV 2051 is doing well with Windows 7 Pro 64-bit. I'll check for a new version...maybe some cool new updates?

Edit: OOhh, some nice updates for DGIndexNV. Computers: Not always possible to keep with updates, past age 25. Especially when nature and face to face connections are also more cool. :D

[gonca]

maybe some cool new updates?
You could say that

[Lathe]

It has been unusually quiet here, hasn't it? I guess it's because it has been so long since I've released a new version. I got a little busy with another project and haven't been giving BD-RB the attention it needs.

No, no, not at all Boss... Just thought I'd shake up the crickets a bit...

[Jake802]

Does BD shrink a 3D Blu-Ray and still leave it 3D?

[jdobbs]

Does BD shrink a 3D Blu-Ray and still leave it 3D?Yes, it does.

[Lathe]

Does BD shrink a 3D Blu-Ray and still leave it 3D?

Only if you send J Dobbs your youngest child. Then he sends you a special key to unlock this ability.

A steep price, but it does a beautiful job...

[jdobbs]

"Your children... we want to buy your children." - John Belushi, The Blues Brothers

[varekai]

“A child of five could understand this. Send someone to fetch a child of five.”
― Groucho Marx

[AmigaFuture]

Not sure what's happening. Downloaded DGIndexNV.exe 2052, make a new directory as I do for each new version. Setup BD-RB as per usual. Ran the first run..and failed. Used 2053 next...failed.

Switched back to DGIndexNV.exe 2051 and all is well again. Anyone come across this? If I run DGIndexNV.exe from it's directory and have it read the file, it does fine. License is in the text file as per normal. Hmm.. Bug with BD-RB?

[06/03/17] BD Rebuilder v0.50.23
[02:17:51] Source: MONTY_PYTHON_D1
- Input BD size: 42.66 GB
- Approximate total content: [03:39:39.432]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- MOVIE and MENUS mode enabled
- Quality: Highest (Very Slow), Two Pass
- Decoding/Frame serving: DGDecNV [3-way]
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[02:17:54] PHASE ONE, Encoding
- [02:17:54] Blanking: VID_00007 (1 of 7)
- [02:17:54] Blanking: VID_00005 (2 of 7)
- [02:17:54] Blanking: VID_00006 (3 of 7)
- [02:17:54] Processing: VID_00000 (4 of 7)
- [02:17:54] Extracting A/V streams [VID_00000]
- [02:19:05] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 92,396 frames
- Inverse Telecining in effect (IVTC)
- Bitrate: 12,546 Kbs
- [02:19:06] Reencoding: VID_00000, Pass 1 of 2
- Encode failed. Aborting.
- BD-Rebuilder v0.50.23
- Windows Version: 6.1 [7601]
- Working Path Free Space: 358.51GB
- AVISYNTH Version: 2.5.8.0, Ok
- LAVFILTERS: Ok
- AnyDVD settings check: Ok.
- X264: Ok
- AFTEN: Ok
- FAAC: Ok
- MP4BOX: Ok
- WAVI: Ok
- TSMUXER: Ok
- FRIMEncode: Ok
- FRIMDecode: Ok
[02:19:06] - Failed video encode, aborted
----------------------
[06/03/17] BD Rebuilder v0.50.23
[02:20:15] Source: MONTY_PYTHON_D1
- Input BD size: 42.66 GB
- Approximate total content: [03:39:39.432]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- MOVIE and MENUS mode enabled
- Quality: Highest (Very Slow), Two Pass
- Decoding/Frame serving: DGDecNV [3-way]
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[02:20:19] PHASE ONE, Encoding
- [02:20:19] Blanking: VID_00007 (1 of 7)
- [02:20:19] Blanking: VID_00005 (2 of 7)
- [02:20:19] Blanking: VID_00006 (3 of 7)
- [02:20:19] Processing: VID_00000 (4 of 7)
- [02:20:19] Extracting A/V streams [VID_00000]
- [02:21:37] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 92,396 frames
- Inverse Telecining in effect (IVTC)
- Bitrate: 12,296 Kbs
- [02:21:37] Reencoding: VID_00000, Pass 1 of 2

It's doing fine...

[videoh]

Later versions of DGDecNV no longer support Avsynth 2.5.8.

[AmigaFuture]

OOpps...I forgot about that though I read it. Heh!

[Jake802]

LMAO! Thanks JDobbs. I thought I read it did but I was not sure.

[AmigaFuture]

I removed AviSynth 2.5.8 and installed 2.6.0 and then 2.6.1 but still encountering this error. Went back to AviSynth 2.6.0. I'm still checking into this, but anyone have any suggestions?

[06/05/17] BD Rebuilder v0.50.23
[06:40:52] Source: MONTY_PYTHON_D2
- Input BD size: 42.62 GB
- Approximate total content: [04:05:23.675]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- MOVIE and MENUS mode enabled
- Quality: High-Speed Option (BD-25+), Two Pass
- Decoding/Frame serving: DGDecNV [3-way]
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
- Resuming from previously started job.
[06:40:54] PHASE ONE, Encoding
- [06:40:54] Processing: VID_00000 (1 of 39)
- [06:40:54] Multiplexing M2TS
- [06:40:55] CreateBDFiles() 00063 2004
[06:40:58]PHASE ONE aborted by user request
----------------------
[06/05/17] BD Rebuilder v0.50.23
[07:11:20] Source: MONTY_PYTHON_D2
- Input BD size: 42.62 GB
- Approximate total content: [04:05:23.675]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- MOVIE and MENUS mode enabled
- Quality: High-Speed Option (BD-25+), Two Pass
- Decoding/Frame serving: DGDecNV [3-way]
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[07:11:21] PHASE ONE, Encoding
- [07:11:21] Processing: VID_00000 (1 of 39)
- [07:11:21] Extracting A/V streams [VID_00000]
- [07:13:08] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 97,163 frames
- Inverse Telecining in effect (IVTC)
- Bitrate: 11,983 Kbs
- [07:13:08] Reencoding: VID_00000, Pass 1 of 2
- [07:13:09] Reencoding: VID_00000, Pass 2 of 2
- [07:46:20] Video Encode complete
- [07:46:20] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [07:46:25] Multiplexing M2TS
- [07:46:25] CreateBDFiles() 00063 2004
[07:59:06]PHASE ONE aborted by user request
----------------------
[06/05/17] BD Rebuilder v0.50.23
[08:43:23] Source: MONTY_PYTHON_D2
- Input BD size: 42.62 GB
- Approximate total content: [04:05:23.675]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- MOVIE and MENUS mode enabled
- Quality: High-Speed Option (BD-25+), Two Pass
- Decoding/Frame serving: DGDecNV [3-way]
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[08:43:26] PHASE ONE, Encoding
- [08:43:26] Processing: VID_00000 (1 of 39)
- [08:43:26] Extracting A/V streams [VID_00000]
- [08:45:13] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 97,163 frames
- Inverse Telecining in effect (IVTC)
- Bitrate: 11,983 Kbs
- [08:45:13] Reencoding: VID_00000, Pass 1 of 2
- [08:45:14] Reencoding: VID_00000, Pass 2 of 2
- [09:17:55] Video Encode complete
- [09:17:55] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [09:18:02] Multiplexing M2TS
- [09:18:02] CreateBDFiles() 00063 2004
[09:29:22]PHASE ONE aborted by user request

[06/05/17] BD Rebuilder v0.50.23
[09:34:53] Source: MONTY_PYTHON_D2
- Input BD size: 42.62 GB
- Approximate total content: [04:05:23.675]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- MOVIE and MENUS mode enabled
- Quality: High-Speed Option (BD-25+), Two Pass
- Decoding/Frame serving: DGDecNV [3-way]
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
- Resuming from previously started job.
[09:34:54] PHASE ONE, Encoding
- [09:34:54] Processing: VID_00000 (1 of 39)
- [09:34:54] Multiplexing M2TS
- [09:36:29] Processing: VID_00001 (2 of 39)
- [09:36:29] Extracting A/V streams [VID_00001]
- [09:38:08] Reencoding video [VID_00001]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 90,158 frames
- Inverse Telecining in effect (IVTC)
- Bitrate: 11,996 Kbs
- [09:38:08] Reencoding: VID_00001, Pass 1 of 2
- [09:38:08] Reencoding: VID_00001, Pass 2 of 2
- [10:07:00] Video Encode complete
- [10:07:00] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [10:07:05] Multiplexing M2TS
- [10:07:05] CreateBDFiles() 00063 2004
[10:09:16]PHASE ONE aborted by user request
[06/05/17] Checking System Settings
- BD-Rebuilder v0.50.23
- Windows Version: 6.1 [7601]
- Working Path Free Space: 257.73GB
- 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
[06/05/17] Systems Settings Check complete

[jdobbs]

Error 63 is a "bad record number" when reading from a file. Best guess would be a corrupt file.

[AmigaFuture]

During multiplexing? That should happen during extraction and rerendering, only, right?

[jdobbs]

During multiplexing? That should happen during extraction and rerendering, only, right?Not necessarily. I looked at that section of code, indicated by the "2004" in the error message, SUP and IGS files can be manipulated directly (e.g. resizing or making empty). It really only involves a couple of subroutine calls -- and that seems to be the only possibility.

[ggtop]

During multiplexing? That should happen during extraction and rerendering, only, right?

Maybe you came across a regression issue

From the changelog:
April 11th, 2012 - v0.40.9
- Corrected the type of DGDecNV field operation used when IVTC is enabled. This should correct audio sync issues with IVTC/DGDecNV/MPEG-2 pulldown combinations.
- Modified processing so that MULTIPROCESS is not used when the source that are to be processed for inverse telecining.

From your log:
Decoding/Frame serving: DGDecNV [3-way]
...
Inverse Telecining in effect (IVTC)

Does deactivating MULTIPROCESS make any difference?

ggtop

[AmigaFuture]

Checking....nope. I also got around to re-ripping it and...still the same.

[videoh]

Maybe you came across a regression issue...DGDecNV... Or not. No indication of a DG problem. DG has nothing to do with multiplexing. If the poster doubts it, test DG stuff manually, outside of BDRB.

[AmigaFuture]

I also did that before I re-ripped it. Scanned through fine. I had DGIndexNV.exe 2053 save the video and demux audio. Everything went fine.

[videoh]

Do you and of course all others reading this have any experience if DecIM should be avoided in HW mode? I saw my framerates jumping from 80 to 120 fps Only if you want to give up 40fps. Don't worry, be happy.

[videoh]

I also did that before I re-ripped it. Scanned through fine. I had DGIndexNV.exe 2053 save the video and demux audio. Everything went fine. Maybe jdobbs can try to recreate the 63 error. He's usually very kind and diligent about getting disks to try to fix things. A great developer, one for the ages. One special guy.

[AmigaFuture]

I agree. I've changed IVTC_1080i to "0" and see if that's the cause and so far, it's going well.

[videoh]

IVTC? What's being used? TFM/TDecimate? DG fieldop=1? DGTelecide/DGDecimate (CUDA filters)?

Can you give us a sample? Seems maybe strange to be doing IVTC on 1080i.

[AmigaFuture]

I had BD-RB use the hidden option IVTC_1080i=1. I've changed it to 0 now it's going through all using High Speed to test. I wasn't using anything else other than IVTC active in Setup.

[jdobbs]

I had BD-RB use the hidden option IVTC_1080i=1. I've changed it to 0 now it's going through all using High Speed to test. I wasn't using anything else other than IVTC active in Setup.That's confusing. What does that have to do with a failure during multiplexing?

[AmigaFuture]

I don't know yet. If I have BD-RB use IVTC_1080i=1 or disable that and use Inverse Tel with Right Click, it gives an error during multiplexing. I haven't modified the Config much, but I'll try an almost clear Config and see.

What the above meant is that I'm not using added AviSynth scripting stuff as was asked about.

[MrVideo]

Seems maybe strange to be doing IVTC on 1080i.
IVTC is done on 1080i video. That is how 23.976p is converted to 1080i29.97, via 2:3 pulldown on the video fields. If the video is 1080p, then IVTC can't be used, as it cannot contain 2:3 pulldown.

IVTC is done on progressive video when it is 720p59.94.

Too me it would seem correct to use IVTC_1080i=1 when the source is 1080i with 2:3 pulldown at 29.97 frames/sec. I have no idea what setting the option to 0 would do.

[videoh]

1080i refers to pure interlaced, which should not be IVTC'ed. Not worth quibbling about unless your goal is pedantry.

[jdobbs]

IVTC is done on 1080i video. That is how 23.976p is converted to 1080i29.97, via 2:3 pulldown on the video fields. If the video is 1080p, then IVTC can't be used, as it cannot contain 2:3 pulldown.

IVTC is done on progressive video when it is 720p59.94.

Too me it would seem correct to use IVTC_1080i=1 when the source is 1080i with 2:3 pulldown at 29.97 frames/sec. I have no idea what setting the option to 0 would do.It defaults to 0. It's just there for the rare instances where you might need it. An example might be a film recorded from a cable box that has it's output set to 1080i.

[AmigaFuture]

Part 1 of 2.

Config:

[Options]
VERSION=0.50.0.23
ENCODER=0
ENABLE_TEST=1
MULTIPROCESS=3 (This doesn't make any difference...)
IVTC_SELECTION=1
FORCE_ENCODE=0
FORCE_NOENCODE=0
IMPORT_VFR_SCAN=1
IMPORT_VFR_FILM=0
MODE=1
ENCODE_QUALITY=5
ONEPASS_ENCODING=0
AUTO_QUALITY=0
QUICK_EXTRAS=0
ENABLE_BLANKING=1
TARGET_SIZE=23500
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
RESIZE_1440=0
RESIZE_720=0
DEINTERLACE=0
SD_TO_1080=0
IGNORE_3D=0
CONVERT_WIDE=0
DTS_REENCODE=1
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=0
AUDIO_DRC=0
DECODER=3
AVCHD=1
REMOVE_WORKFILES=0
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=0
IVTC_PULLDOWN=1
ASSUME_DVD_PAL=0
FRIMSOURCE=0
COMPLETION_BEEP=1
OUTPUT_SBS=0
NEROAAC=0
SUPTITLE=0
PGSTOSRT=0
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=1
CUSTOM_TARGET_SIZE=23500
MOVIEONLY_TYPE=34
ALTCRF=23
ALT_TARGET=624
ALT_CRF_TARGET=624
ALTMETHOD=2
ALTAUTOCROP=0
[Paths]
SOURCE_PATH=P:\MONTY PYTHON- ALMOST THE TRUTH\MONTY PYTHON D2\
WORKING_PATH=G:\OUTPUT\
DGIndexNV=C:\Users\User\Desktop\BD_Rebuilder\nVidia\2053\DGIndexNV.exe
DGDecNV=C:\Users\User\Desktop\BD_Rebuilder\nVidia\2053\DGDecodeNV.dll


IVTC_1080i=1 being used.
----------------------
[06/08/17] BD Rebuilder v0.50.23
[07:19:42] Source: MONTY_PYTHON_D2
- Input BD size: 42.62 GB
- Approximate total content: [04:05:23.675]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- MOVIE and MENUS mode enabled
- Quality: High-Speed Option (BD-25+), Two Pass
- Decoding/Frame serving: DGDecNV [3-way]
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[07:19:44] PHASE ONE, Encoding
- [07:19:44] Processing: VID_00000 (1 of 39)
- [07:19:44] Extracting A/V streams [VID_00000]
- [07:20:59] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 97,163 frames
- Inverse Telecining in effect (IVTC)
- Bitrate: 11,287 Kbs
- [07:20:59] Reencoding: VID_00000, Pass 1 of 2
- [07:20:59] Reencoding: VID_00000, Pass 2 of 2
- [07:55:26] Video Encode complete
- [07:55:26] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- Track 4353 (eng): Keeping original audio
- [07:55:33] Multiplexing M2TS
- [07:55:33] CreateBDFiles() 00063 2004
[07:55:42]PHASE ONE aborted by user request

[AmigaFuture]

Part 2 of 2.

Now IVTC_1080i=1 is removed and not just switched to 0...
----------------------
[06/08/17] BD Rebuilder v0.50.23
[07:57:19] Source: MONTY_PYTHON_D2
- Input BD size: 42.62 GB
- Approximate total content: [04:05:23.675]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- MOVIE and MENUS mode enabled
- Quality: High-Speed Option (BD-25+), Two Pass
- Decoding/Frame serving: DGDecNV [3-way]
- Audio Settings: AC3=0 DTS=1 HD=0 Kbs=640
[07:57:21] PHASE ONE, Encoding
- [07:57:21] Processing: VID_00000 (1 of 39)
- [07:57:21] Extracting A/V streams [VID_00000]

[......]

- [09:31:38] Reencoding video [VID_00082]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 98 frames
- Bitrate: 1,610 Kbs
- [09:31:38] Reencoding: VID_00082, Pass 1 of 2
- [09:31:38] Reencoding: VID_00082, Pass 2 of 2
- [09:31:40] Video Encode complete
- [09:31:40] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [09:31:40] Multiplexing M2TS
- [09:31:43] Processing: VID_00083 (39 of 39)
- [09:31:43] Extracting A/V streams [VID_00083]
- [09:31:48] Reencoding video [VID_00083]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 29.970fps, 98 frames
- Bitrate: 1,895 Kbs
- [09:31:48] Reencoding: VID_00083, Pass 1 of 2
- [09:31:48] Reencoding: VID_00083, Pass 2 of 2
- [09:31:50] Video Encode complete
- [09:31:50] Processing audio tracks
- Track 4352 (eng): Reencoding audio to AC3...
- [09:31:50] Multiplexing M2TS
[09:31:54]PHASE ONE complete
[09:31:54]PHASE TWO - Rebuild Started
- [09:31:54] Rebuilding BD file Structure
[09:31:56] - Encode and Rebuild complete
[09:31:56] JOB: MONTY_PYTHON_D2 finished.
[06/08/17] Checking System Settings
- BD-Rebuilder v0.50.23
- Windows Version: 6.1 [7601]
- Working Path Free Space: 320.58GB
- 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
[06/08/17] Systems Settings Check complete


BD-RB identifies all the 1080 videos for this BD as 1080i. I've re-ripped the BD a few times now, same error. I'm enabling Interlace now to see if that's playing a role.

[MrVideo]

1080i refers to pure interlaced, which should not be IVTC'ed.
I do it every day. The material I capture is 1080i, with 2:3 telecined video.

That is why 2:3 telecine exists, i.e., to be able to put 23.976p video onto 1080i29.97 video.

To get back to 1080p23.976, it requires doing IVTC of the 1080i video.

[MrVideo]

It defaults to 0. It's just there for the rare instances where you might need it. An example might be a film recorded from a cable box that has it's output set to 1080i.
Or you captured any 1080i video from DBS/cable that has 2:3 pulldown. It doesn't have to be a movie, it could be a drama.

I do not know of any Blu-ray that is released where the source is 23.976/24p and it is converted to 1080i29.97. When it is other than Blu-ray, there are lots of 1080i sources. Prime examples in the U.S. are the OTA networks: CBS, The CW and NBC.

[MrVideo]

BD-RB identifies all the 1080 videos for this BD as 1080i.
What does mediainfo say about the M2TS files?

Please supply the UPC of the Blu-ray.

[videoh]

2:3 telecine exists MrVideo thinks we don't know about hard telecine. Pedantry!