BD Rebuilder Beta - Bug Reports Only

[HWK]

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


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

Setup info:

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

Thank you, I will add to do list and will also check out your sample.

[HWK]

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

Are you doing compression or similar before sending to NAS which may cause cpu to be high side.

[HWK]

@ Limobar

I just downloaded your sample and I am experience the same thing when playing with TMT 5. Acceleration on causing artifact in video and with off video is doing zigzag(not in focus) seem to be related to tsmuxer(I had with other situation as well)

[Limobar]

...video is doing zigzag(not in focus) seem to be related to tsmuxer(I had with other situation as well)

Left and right mixed up, probably.

[HWK]

Left and right mixed up, probably.

Not quite, even static background is moving. Best I can describe is going between point a and b which are very close and it is doing rapidly.

Hardware acceleration does not cause this problem.

[DarWun]

Are you doing compression or similar before sending to NAS which may cause cpu to be high side.

No compression.

[HWK]

@ Limobar

I finish analyzing sample you have provided and I can confirm FRIMEncode is at fault over here. I ran five different test to make sure it is not random occurrence and for all test FRIMDecode was used. Part of test was to use pipe between two processes, create yuv files and check number of frames are equal in both view.

I can upload sample which I fixed with another encoder so you can test as well, for my test TMT 5 with hardware acceleration turned on.

System Info
Intel core i7 3930K
nVidia GTX 580
32GB Ram
Windows 7 (64 bit)

I am also gone test with different version of FRIMEncode to see if I find one where problem does not occur.

I forgot to add all test were done outside of BD-RB environment with FRIM tools.

[DarWun]

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

I had two rebuilds running through the day while I was at work to evaluate the impact of the encoder quality settings. They both completed fine. I started a rebuild when I got home from work. It ran unattended for about 30minutes. Ten minutes after I loaded Civilization 5, the video encode failed. I can now confirm without any doubt that the log file does not summarize inspect results after the failure.

[HWK]

Do you have other game which you can use and test to see if this happens again. A game which is not much demanding would be best candidate.

[DarWun]

Do you have other game which you can use and test to see if this happens again. A game which is not much demanding would be best candidate.

I do. I'm heading out of town for a few days so I won't be able to get back to it until the weekend though.

[jdobbs]

I highly doubt that. It's only with FRIM encodes that the artifacts show. This doesn't make sense. If the issue was in the encode it would always be there. How could it correct itself when you change playback settings? It has to be a result of the playback device.

[HWK]

This doesn't make sense. If the issue was in the encode it would always be there. How could it correct itself when you change playback settings? It has to be a result of the playback device.

Jdobbs, I decided to do cloudy with chance of meat ball 2 as well and with frimencode and I can repeat this each time I encode; but like you mention how it can change with playback is still mystery.

I am gone play on hardware player and see what is happening, when I played on software player my result is identical limobar.

[jdobbs]

Jdobbs, I decided to do cloudy with chance of meat ball 2 as well and with frimencode and I can repeat this each time I encode; but like you mention how it can change with playback is still mystery.

I am gone play on hardware player and see what is happening, when I played on software player my result is identical limobar.Like I said, though, if the problem is in the encode it would have to always be there. That, to me, says it is absolutely a problem in the playback mechanism.

This is why I hesitate to accept bug reports from software players -- you never know whether the issue is in the player (and it usually is).

[HWK]

True, hardware player would be big help. I am gone run some test and hopefully have meaningful report.

Just quick question can you test sample as well. It is only 29 second and it would add weight to report.

[jdobbs]

True, hardware player would be big help. I am gone run some test and hopefully have meaningful report.

Just quick question can you test sample as well. It is only 29 second and it would add weight to report.I'll pick up "Cloudy with a Chance of Meatballs 2" at some point and run a backup.

[HWK]

I'll pick up "Cloudy with a Chance of Meatballs 2" at some point and run a backup.

I will do the same, in fact I already ordered it and hopefully I will have it soon.

[jdobbs]

It looks like it isn't going to be released in 3D here until January 28th.

[J666RST]

Hi jdobbs, HWK & Limobar, played the iso sample on my Panasonic DMP-BDT210 3D player and sample played fine in 3D

Hope that helps

Lee

[HWK]

Thank you, marvelous to hear such a news. I am doing backup as well and will also test for sure (extra test doesn't hurt)

[AmigaFuture]

No, need to assume. You can be assured no XP support and no it is not Jdobbs fault. Program he uses require win 7 at minimum to work.

I'm glad WinDoze 8 isn't required. I'm staying with XP, Doze 7 and Mac OS X Mavericks. I do not like the functionality/bland look of 8 at all.

I'm loving the DTS Express support. Thus far, Karate Kid is doing well with PowerDVD 12 and LG Player. I have some others to try soon. Yay!

[Limobar]

This doesn't make sense. If the issue was in the encode it would always be there. How could it correct itself when you change playback settings? It has to be a result of the playback device.

The explanation is not so hard to imagine. There is a difference in encoder settings used that the hardware accelerated- and the software decoders within TMT 5 allow.

That it's the hardware accelerated decoding that gives artifacts and not the software decoding, is odd. I would think that HW decoding has strict rules and that software decoding can be more forgiving when it comes to used encoder settings.

Knowing that HW decoding goes wrong, there's no reason to exclude the FRIM encoder as the reason for the artifacts, at this point.

[jdobbs]

The explanation is not so hard to imagine. There is a difference in encoder settings used that the hardware accelerated- and the software decoders within TMT 5 allow.

That it's the hardware accelerated decoding that gives artifacts and not the software decoding, is odd. I would think that HW decoding has strict rules and that software decoding can be more forgiving when it comes to used encoder settings.

Knowing that HW decoding goes wrong, there's no reason to exclude the FRIM encoder as the reason for the artifacts, at this point.I disagree completely. The encoded stream is the encoded stream. It isn't variable, or changing. If it can be decoded correctly -- then the stream is fine. The only variable is the player. In other words, since the blocks you see aren't in the encoded stream (obviously because they aren't always there) -- they have to be created by the decoder.

I've seen hardware acceleration cause problems in all kinds of scenarios. That's why it's an option that can be disabled. This scenario is no different.

I have no vested interest in whether FRIMEncode works or doesn't work -- I'm just using logic here, and everything points to the decoder.

[Limobar]

You can disagree with me, but what I'm saying is logical.

You can create an encode that gets decoded fine by more forgiving decoders, but if that encode doesn't meet the required standard it is supposed to meet, the encode is still to blame and not the decoder that only allows that required standard.

[jdobbs]

You can disagree with me, but what I'm saying is logical.

The bottom line is that the ONLY good test is using a standalone player, and having done a large number of 3D discs with FRIMEncoder I have not encountered a single one that has playback issues (on two different brands of players).

While anything is possible in a quantum world, the probabilities point heavily toward the decoder.

[HWK]

The bottom line is that the ONLY good test is using a standalone player, and having done a large number of 3D discs with FRIMEncoder I have not encountered a single one that has playback issues (on two different players).

I finish test and OPPO player provide exceptional playback of video and 3D experience, Ps3 also play without any issue. Although subtitle depth is lost when BD-RB mux assets after encode. Another thing I notice is on TMT5 frequency of problem occurring has gone down significantly.

FRIM Version 1.20

[jdobbs]

I finish test and OPPO player provide exceptional playback of video and 3D experience, Ps3 also play without any issue. Although subtitle depth is lost when BD-RB mux assets after encode.Same with my Samsung and Sony players.

I'll check on the subtitle depth issue.

[HWK]

Same with my Samsung and Sony players.

I'll check on the subtitle depth issue.

I am quite happy with compression of FRIM, I am gone do movie with longest run time I have and see how it goes.

[jdobbs]

I am quite happy with compression of FRIM, I am gone do movie with longest run time I have and see how it goes. I ran a group of PSNR tests with 2D encodes from FRIM and X264 at different settings. X264 did better overall, but it really wasn't as great a difference as I would have thought, and I think it was mainly due to it's two pass ability. I may do another comparison using ABR on both.

[HWK]

You really can't compare them even with ABR, unless disable advance options such as lookahead and MB Tree etc.

[HWK]

Jdobbs, I notice something interesting I was extracting main movie from cloudy with chance of meat balls 2 and I used mpls, but when I finish tsmuxer only extracted mvc stream from first segment which is 7 min 34 sec.

I am wondering if it has to do something with faulty playback of 3D in software when mux is done.

I am gone send this info to Roman as well.

[HWK]

I'll check on the subtitle depth issue.

Are you experiencing this problem with every movie?

[jdobbs]

Are you experiencing this problem with every movie?Honestly I haven't given enough thought or attention to the subtitles.

[AmigaFuture]

While anything is possible in a quantum world, the probabilities point heavily toward the decoder.

Which is why quantum mechanics and physics is a rediscovery of the massive Law of Attraction. Ah, the Teenage years of Science we're in...

Anyway... After editing a TiVo file and exporting to MPG... I'm not able to reproduce a Progressive file with BD-RB as HandBrake does. If I drag an MPG file to HandBrake and select the Filters tab then select "Detelecine: Default" which is usually "Off", and change Video Framerate to 23.976 and switch from Peekframe Rate to Constant Framerate. The desired Progressive MKV is obtained.

I have the following in BD-RB.
SD_PROGRESSIVE=1
IVTC_TELECIDE=0
IVTC_SELECTION=1
IVTC_480i=0

IVTS for 3:2 pulldown is disabled.

I've tried different combinations with BD-RB. It's not producing the same effect HangBrake is. Is this a bug? Seems like like BD-RB (or I) am missing something. If I use Media Player Classic - Home Cinema to "step" through the frames once passed I'm able to see repeated frames after using BD-RB (44.03).

Wanting 1080i to 1280x720. Anyone have any ideas I may entertain?

[Sharc]

I ran a group of PSNR tests with 2D encodes from FRIM and X264 at different settings. X264 did better overall, but it really wasn't as great a difference as I would have thought, and I think it was mainly due to it's two pass ability. I may do another comparison using ABR on both.
Hmmm..., I would have to disagree at some point.
x264 is really stronger at low bitrates IMHO, like those you get for BD5/9.
In flat scenes with flat backgrounds the Intel Encoder tends to produce visible blocks and gop pulsing. Similar can happen at scene transitions. Such occasional transient effects may barely deteriorate the PSNR values, they are however clearly visible even by "uneducated" viewers at normal viewing distance (and unfortunately one tends to remember these occasional "ooops".... )
In motion and panning scenes details get suppressed (blurred), but this is less of a problem because it is usually not noticeable when watching the movie.
I trust it may be different at BD25+ bitrates, but I didn't try as I still do all my backups on BD5/9.
Not a big issue, it is really great to finally have a free and good quality MVC suite with FRIM/Intel, even though there seems to be some room for improvement.

[jdobbs]

Hmmm..., I would have to disagree at some point.
x264 is really stronger at low bitrates IMHO, like those you get for BD5/9.
In flat scenes with flat backgrounds the Intel Encoder tends to produce visible blocks and gop pulsing. Similar can happen at scene transitions. Such occasional transient effects may barely deteriorate the PSNR values, they are however clearly visible even by "uneducated" viewers at normal viewing distance (and unfortunately one tends to remember these occasional "ooops".... )
In motion and panning scenes details get suppressed (blurred), but this is less of a problem because it is usually not noticeable when watching the movie.
I trust it may be different at BD25+ bitrates, but I didn't try as I still do all my backups on BD5/9.
Not a big issue, it is really great to finally have a free and good quality MVC suite with FRIM/Intel, even though there seems to be some room for improvement. You're right. I was testing at a given bitrate (generally aimed at BD-25) and didn't do anything exhaustive. It's very likely that X264 would do considerably better at lower bitrates. I don't want to give the wrong impression. I still believe X264 is the best h.264 encoder around. But no matter how much we like it -- it still doesn't do MVC.

[Acerjen]

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

Thanks for your response. One of the movies I am having trouble with is Battle: Los Angeles. Everything works except the DTS Express track. When I choose the bonus material that uses it, the movie begins playing and occasionally a PiP video will pop up. The PiP video plays fine, but the audio that plays is the main DTS-HD track. I used tsMuxer and verified that the DTS Express track is there, but it is not playing. I believe I have provided everything below that is usually requested when reporting a problem. The text in these files would have spanned across 3-4 posts. So, I decided to attach them instead. If anything else is needed, please ask. Thanks for your help. Later.

Acerjen

[Yordan5]

Could someone confirm if using the Quality settings would make any difference at all to the final movie (3D iso) even though when using the Best setting it takes much longer to process the iso.

[jdobbs]

Could someone confirm if using the Quality settings would make any difference at all to the final movie (3D iso) even though when using the Best setting it takes much longer to process the iso.The BD-RB quality setting is applied to FRIMEncode. In my PSNR tests I can confirm that the higher quality settings resulted in better PSNR results than lower settings. So the answer should be "yes", using a higher quality setting would make a difference -- remember, though, that different sources may have different degrees of results.

[colinhunt]

Running my first test with the new BD-RB, doing a movie-only 3D backup. I'm a bit puzzled as to why BD-RB began re-encoding the movie, because the ISO image is 24.3GB and the movie itself is only 22936MB (including two 5.1 channel DTS-HD MA tracks, one of which is disabled, saving approx. 1GB). I expected a quick 1:1 copy instead of a re-encode as I'm using a Custom output size of 24350MB.

[jdobbs]

Running my first test with the new BD-RB, doing a movie-only 3D backup. I'm a bit puzzled as to why BD-RB began re-encoding the movie, because the ISO image is 24.3GB and the movie itself is only 22936MB (including two 5.1 channel DTS-HD MA tracks, one of which is disabled, saving approx. 1GB). I expected a quick 1:1 copy instead of a re-encode as I'm using a Custom output size of 24350MB. Currently BD-RB always reencodes for 3D. I'm working on "keep original" for 3D for the next release.

[colinhunt]

Currently BD-RB always reencodes for 3D. I'm working on "keep original" for 3D for the next release.
Ah, well that explains it perfectly :)

[colinhunt]

First movie-only 3D backup result: image is extremely corrupted.

Log:

[01.18.14] BD Rebuilder v0.46.03 (beta)
[20:08:32] Source: OUT_OF_INFERNO_3D_00001
- Input BD size: 27,36 GB
- Approximate total content: [01:47:19.516]
- Target BD size: 23,68 GB
- Windows Version: 6.1 [7601]
- MOVIE-ONLY mode enabled
- Quality: Ultra High Quality (Extremely Slow), ABR
- Output folder: T:\_ENCODES\
- X264 Tweak(s) enabled
- MVC 3D Output Mode enabled
- Decoding/Frame serving: FRIMDecode
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
- Subtitle [3] is defaulted ON.
[20:08:35] PHASE ONE, Encoding
- [20:08:35] Processing: VID_00000 (1 of 1)
- [20:08:35] Extracting A/V streams [VID_00000]
- [20:24:43] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 154*394 frames
- Bitrate: 26*950 Kbs
- Using FRIMEncoder for MVC reencoding
- [20:24:43] Reencoding: VID_00000, Pass 1 of 1
- [06:53:07] Video Encode complete
- [06:53:07] Processing audio tracks
- Track 4352 (zho): Keeping original audio
[06:53:07]PHASE ONE complete
[06:53:07]PHASE TWO - Rebuild Started
- [06:53:07] Rebuilding BD file Structure
[06:57:31] - Encode and Rebuild complete
[06:57:31] JOB: OUT_OF_INFERNO_3D finished.


Similar image corruption took place several times when I was testing the command line versions of FRIMdecoder/encoder/transcode. It happened when decoding was done in hardware instead of software. I ran this backup job on a Core i7-3930K which supports HW acceleration for both decode and encode.

[jdobbs]

First movie-only 3D backup result: image is extremely corrupted.

Log:

[01.18.14] BD Rebuilder v0.46.03 (beta)
[20:08:32] Source: OUT_OF_INFERNO_3D_00001
- Input BD size: 27,36 GB
- Approximate total content: [01:47:19.516]
- Target BD size: 23,68 GB
- Windows Version: 6.1 [7601]
- MOVIE-ONLY mode enabled
- Quality: Ultra High Quality (Extremely Slow), ABR
- Output folder: T:\_ENCODES\
- X264 Tweak(s) enabled
- MVC 3D Output Mode enabled
- Decoding/Frame serving: FRIMDecode
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
- Subtitle [3] is defaulted ON.
[20:08:35] PHASE ONE, Encoding
- [20:08:35] Processing: VID_00000 (1 of 1)
- [20:08:35] Extracting A/V streams [VID_00000]
- [20:24:43] Reencoding video [VID_00000]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23,976fps, 154*394 frames
- Bitrate: 26*950 Kbs
- Using FRIMEncoder for MVC reencoding
- [20:24:43] Reencoding: VID_00000, Pass 1 of 1
- [06:53:07] Video Encode complete
- [06:53:07] Processing audio tracks
- Track 4352 (zho): Keeping original audio
[06:53:07]PHASE ONE complete
[06:53:07]PHASE TWO - Rebuild Started
- [06:53:07] Rebuilding BD file Structure
[06:57:31] - Encode and Rebuild complete
[06:57:31] JOB: OUT_OF_INFERNO_3D finished.


Similar image corruption took place several times when I was testing the command line versions of FRIMdecoder/encoder/transcode. It happened when decoding was done in hardware instead of software. I ran this backup job on a Core i7-3930K which supports HW acceleration for both decode and encode.By default hw/sw is auto detected. I'll force sw on the next release.

[colinhunt]

By default hw/sw is auto detected. I'll force sw on the next release.
Could you instead make two toggles or hidden options, one each for decoding and encoding? HW encoding works fine on my system, it's the HW decoding that causes issues.

[jdobbs]

Could you instead make two toggles or hidden options, one each for decoding and encoding? HW encoding works fine on my system, it's the HW decoding that causes issues.Understood

[HWK]

I ran this backup job on a Core i7-3930K which supports HW acceleration for both decode and encode.

Strange, I have same processor but mine never in hardware acceleration. No I didn't use -sw option. Perhaps it has to do with motherboard one is using.

[update]

It is indeed related to motherboard and one I am using does not have GPU built in which also explain why I can't turn it on.

[jdobbs]

Strange, I have same processor but mine never in hardware acceleration. No I didn't use -sw option. Perhaps it has to do with motherboard one is using.Mine are all AMD processors, so I guess I never have to worry about it. I've added a couple of hidden options to force SW decoding/encoding for the next release.

[slvrsrfr]

Imported The Simpsons Season 3 from 4 DVDs to BD. The sound lags behind the video on all 24 episodes. The lag discrepancy grows longer as the further the episode is...here's the log and my settings. Plz. let me know if you want any other info:
==========================
[12:54:00] BD Rebuilder v0.46.03 (beta)
[12:54:00] BEGIN - BATCH SEQUENCE
==========================
-----------------------
[12:54:00] PROCESSING BATCH FILE [1]
----------------------
[01/15/14] BD Rebuilder v0.46.03 (beta)
[12:54:02] Source: SIMPSONS_S3
- Input BD size: 27.64 GB
- Approximate total content: [09:12:09.203]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- Quality: Highest (Very Slow), Two Pass
- Decoding/Frame serving: DirectShow
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=448
[12:54:03] PHASE ONE, Encoding
- [12:54:03] Processing: VID_00001 (1 of 24)
- [12:54:03] Extracting A/V streams [VID_00001]
- [12:55:23] Reencoding video [VID_00001]
- Source Video: MPEG-2, 720x480, Hybrid
- Rate/Length: 29.970fps, 41,479 frames
- Bitrate: 5,169 Kbs
- [12:55:24] Reencoding: VID_00001, Pass 1 of 2
- [13:05:15] Reencoding: VID_00001, Pass 2 of 2
- [13:52:56] Video Encode complete
- [13:52:56] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [13:52:56] Multiplexing M2TS
- [13:54:07] Processing: VID_00002 (2 of 24)
- [13:54:07] Extracting A/V streams [VID_00002]
- [13:56:02] Reencoding video [VID_00002]
- Source Video: MPEG-2, 720x480, Hybrid
- Rate/Length: 29.970fps, 41,421 frames
- Bitrate: 5,129 Kbs
- [13:56:02] Reencoding: VID_00002, Pass 1 of 2
- [14:06:14] Reencoding: VID_00002, Pass 2 of 2
- [14:57:53] Video Encode complete
- [14:57:53] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [14:57:53] Multiplexing M2TS
- [14:58:39] Processing: VID_00003 (3 of 24)
- [14:58:39] Extracting A/V streams [VID_00003]
- [14:59:59] Reencoding video [VID_00003]
- Source Video: MPEG-2, 720x480, Hybrid
- Rate/Length: 29.970fps, 41,301 frames
- Bitrate: 4,905 Kbs
- [14:59:59] Reencoding: VID_00003, Pass 1 of 2
- [15:09:23] Reencoding: VID_00003, Pass 2 of 2
- [15:55:03] Video Encode complete
- [15:55:03] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [15:55:03] Multiplexing M2TS
- [15:55:47] Processing: VID_00004 (4 of 24)
- [15:55:47] Extracting A/V streams [VID_00004]
- [15:57:38] Reencoding video [VID_00004]
- Source Video: MPEG-2, 720x480, Hybrid
- Rate/Length: 29.970fps, 41,391 frames
- Bitrate: 5,072 Kbs
- [15:57:39] Reencoding: VID_00004, Pass 1 of 2
- [16:07:24] Reencoding: VID_00004, Pass 2 of 2
- [16:54:03] Video Encode complete
- [16:54:03] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [16:54:03] Multiplexing M2TS
- [16:54:49] Processing: VID_00005 (5 of 24)
- [16:54:49] Extracting A/V streams [VID_00005]
- [16:56:06] Reencoding video [VID_00005]
- Source Video: MPEG-2, 720x480, Hybrid
- Rate/Length: 29.970fps, 41,479 frames
- Bitrate: 4,897 Kbs
- [16:56:07] Reencoding: VID_00005, Pass 1 of 2
- [17:05:43] Reencoding: VID_00005, Pass 2 of 2
- [17:52:18] Video Encode complete
- [17:52:18] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [17:52:18] Multiplexing M2TS
- [17:53:29] Processing: VID_00006 (6 of 24)
- [17:53:29] Extracting A/V streams [VID_00006]
- [17:55:45] Reencoding video [VID_00006]
- Source Video: MPEG-2, 720x480, Hybrid
- Rate/Length: 29.970fps, 41,479 frames
- Bitrate: 5,040 Kbs
- [17:55:46] Reencoding: VID_00006, Pass 1 of 2
- [18:06:31] Reencoding: VID_00006, Pass 2 of 2
- [18:58:13] Video Encode complete
- [18:58:13] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [18:58:13] Multiplexing M2TS
- [18:59:29] Processing: VID_00007 (7 of 24)
- [18:59:29] Extracting A/V streams [VID_00007]
- [19:03:00] Reencoding video [VID_00007]
- Source Video: MPEG-2, 720x480, Hybrid
- Rate/Length: 29.970fps, 41,361 frames
- Bitrate: 5,527 Kbs
- [19:03:01] Reencoding: VID_00007, Pass 1 of 2
- [19:14:02] Reencoding: VID_00007, Pass 2 of 2
- [20:06:55] Video Encode complete
- [20:06:55] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [20:06:55] Multiplexing M2TS
- [20:08:21] Processing: VID_00008 (8 of 24)
- [20:08:22] Extracting A/V streams [VID_00008]
- [20:10:09] Reencoding video [VID_00008]
- Source Video: MPEG-2, 720x480, Hybrid
- Rate/Length: 29.970fps, 41,479 frames
- Bitrate: 5,217 Kbs
- [20:10:09] Reencoding: VID_00008, Pass 1 of 2
- [20:20:43] Reencoding: VID_00008, Pass 2 of 2
- [21:11:53] Video Encode complete
- [21:11:53] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [21:11:54] Multiplexing M2TS
- [21:13:06] Processing: VID_00009 (9 of 24)
- [21:13:06] Extracting A/V streams [VID_00009]
- [21:14:59] Reencoding video [VID_00009]
- Source Video: MPEG-2, 720x480, Hybrid
- Rate/Length: 29.970fps, 41,271 frames
- Bitrate: 5,071 Kbs
- [21:15:00] Reencoding: VID_00009, Pass 1 of 2
- [21:26:54] Reencoding: VID_00009, Pass 2 of 2
- [22:22:04] Video Encode complete
- [22:22:04] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [22:22:04] Multiplexing M2TS
- [22:23:07] Processing: VID_00010 (10 of 24)
- [22:23:07] Extracting A/V streams [VID_00010]
- [22:24:54] Reencoding video [VID_00010]
- Source Video: MPEG-2, 720x480, Hybrid
- Rate/Length: 29.970fps, 41,361 frames
- Bitrate: 4,945 Kbs
- [22:24:55] Reencoding: VID_00010, Pass 1 of 2
- [22:34:35] Reencoding: VID_00010, Pass 2 of 2
- [23:20:23] Video Encode complete
- [23:20:23] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [23:20:23] Multiplexing M2TS
- [23:21:08] Processing: VID_00011 (11 of 24)
- [23:21:08] Extracting A/V streams [VID_00011]
- [23:22:30] Reencoding video [VID_00011]
- Source Video: MPEG-2, 720x480, Hybrid
- Rate/Length: 29.970fps, 41,361 frames
- Bitrate: 3,758 Kbs
- [23:22:31] Reencoding: VID_00011, Pass 1 of 2
- [23:31:38] Reencoding: VID_00011, Pass 2 of 2
- [00:14:14] Video Encode complete
- [00:14:14] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [00:14:15] Multiplexing M2TS
- [00:14:51] Processing: VID_00012 (12 of 24)
- [00:14:51] Extracting A/V streams [VID_00012]
- [00:16:40] Reencoding video [VID_00012]
- Source Video: MPEG-2, 720x480, Hybrid
- Rate/Length: 29.970fps, 41,421 frames
- Bitrate: 5,035 Kbs
- [00:16:40] Reencoding: VID_00012, Pass 1 of 2
- [00:26:20] Reencoding: VID_00012, Pass 2 of 2
- [01:13:14] Video Encode complete
- [01:13:14] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [01:13:15] Multiplexing M2TS
- [01:14:00] Processing: VID_00013 (13 of 24)
- [01:14:00] Extracting A/V streams [VID_00013]
- [01:15:22] Reencoding video [VID_00013]
- Source Video: MPEG-2, 720x480, Hybrid
- Rate/Length: 29.970fps, 41,449 frames
- Bitrate: 5,265 Kbs
- [01:15:22] Reencoding: VID_00013, Pass 1 of 2
- [01:25:18] Reencoding: VID_00013, Pass 2 of 2
- [02:13:08] Video Encode complete
- [02:13:08] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [02:13:08] Multiplexing M2TS
- [02:13:55] Processing: VID_00014 (14 of 24)
- [02:13:55] Extracting A/V streams [VID_00014]
- [02:15:48] Reencoding video [VID_00014]
- Source Video: MPEG-2, 720x480, Hybrid
- Rate/Length: 29.970fps, 41,479 frames
- Bitrate: 5,257 Kbs
- [02:15:48] Reencoding: VID_00014, Pass 1 of 2
- [02:25:32] Reencoding: VID_00014, Pass 2 of 2
- [03:10:18] Video Encode complete
- [03:10:18] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [03:10:19] Multiplexing M2TS
- [03:11:05] Processing: VID_00015 (15 of 24)
- [03:11:06] Extracting A/V streams [VID_00015]
- [03:12:58] Reencoding video [VID_00015]
- Source Video: MPEG-2, 720x480
- Rate/Length: 29.970fps, 41,415 frames
- Bitrate: 5,266 Kbs
- [03:12:59] Reencoding: VID_00015, Pass 1 of 2
- [03:22:57] Reencoding: VID_00015, Pass 2 of 2
- [04:10:37] Video Encode complete
- [04:10:37] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [04:10:37] Multiplexing M2TS
- [04:11:24] Processing: VID_00016 (16 of 24)
- [04:11:24] Extracting A/V streams [VID_00016]
- [04:12:47] Reencoding video [VID_00016]
- Source Video: MPEG-2, 720x480, Hybrid
- Rate/Length: 29.970fps, 41,421 frames
- Bitrate: 5,448 Kbs
- [04:12:47] Reencoding: VID_00016, Pass 1 of 2
- [04:22:40] Reencoding: VID_00016, Pass 2 of 2
- [05:09:42] Video Encode complete
- [05:09:42] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [05:09:42] Multiplexing M2TS
- [05:10:30] Processing: VID_00017 (17 of 24)
- [05:10:30] Extracting A/V streams [VID_00017]
- [05:12:24] Reencoding video [VID_00017]
- Source Video: MPEG-2, 720x480, Hybrid
- Rate/Length: 29.970fps, 41,421 frames
- Bitrate: 5,291 Kbs
- [05:12:25] Reencoding: VID_00017, Pass 1 of 2
- [05:22:21] Reencoding: VID_00017, Pass 2 of 2
- [06:10:13] Video Encode complete
- [06:10:13] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [06:10:13] Multiplexing M2TS
- [06:11:00] Processing: VID_00018 (18 of 24)
- [06:11:00] Extracting A/V streams [VID_00018]
- [06:12:23] Reencoding video [VID_00018]
- Source Video: MPEG-2, 720x480, Hybrid
- Rate/Length: 29.970fps, 41,449 frames
- Bitrate: 5,459 Kbs
- [06:12:24] Reencoding: VID_00018, Pass 1 of 2
- [06:22:23] Reencoding: VID_00018, Pass 2 of 2
- [07:11:39] Video Encode complete
- [07:11:39] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [07:11:39] Multiplexing M2TS
- [07:12:27] Processing: VID_00019 (19 of 24)
- [07:12:27] Extracting A/V streams [VID_00019]
- [07:14:19] Reencoding video [VID_00019]
- Source Video: MPEG-2, 720x480, Hybrid
- Rate/Length: 29.970fps, 41,001 frames
- Bitrate: 5,278 Kbs
- [07:14:20] Reencoding: VID_00019, Pass 1 of 2
- [07:24:21] Reencoding: VID_00019, Pass 2 of 2
- [08:12:46] Video Encode complete
- [08:12:46] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [08:12:46] Multiplexing M2TS
- [08:13:33] Processing: VID_00020 (20 of 24)
- [08:13:33] Extracting A/V streams [VID_00020]
- [08:14:57] Reencoding video [VID_00020]
- Source Video: MPEG-2, 720x480, Hybrid
- Rate/Length: 29.970fps, 41,361 frames
- Bitrate: 5,477 Kbs
- [08:14:58] Reencoding: VID_00020, Pass 1 of 2
- [08:24:46] Reencoding: VID_00020, Pass 2 of 2
- [09:12:52] Video Encode complete
- [09:12:53] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [09:12:53] Multiplexing M2TS
- [09:13:41] Processing: VID_00021 (21 of 24)
- [09:13:41] Extracting A/V streams [VID_00021]
- [09:15:04] Reencoding video [VID_00021]
- Source Video: MPEG-2, 720x480, Hybrid
- Rate/Length: 29.970fps, 41,391 frames
- Bitrate: 5,273 Kbs
- [09:15:04] Reencoding: VID_00021, Pass 1 of 2
- [09:24:57] Reencoding: VID_00021, Pass 2 of 2
- [10:13:17] Video Encode complete
- [10:13:17] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [10:13:17] Multiplexing M2TS
- [10:14:04] Processing: VID_00022 (22 of 24)
- [10:14:04] Extracting A/V streams [VID_00022]
- [10:15:33] Reencoding video [VID_00022]
- Source Video: MPEG-2, 720x480, Hybrid
- Rate/Length: 29.970fps, 41,301 frames
- Bitrate: 4,108 Kbs
- [10:15:33] Reencoding: VID_00022, Pass 1 of 2
- [10:24:45] Reencoding: VID_00022, Pass 2 of 2
- [11:08:00] Video Encode complete
- [11:08:00] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [11:08:01] Multiplexing M2TS
- [11:08:40] Processing: VID_00023 (23 of 24)
- [11:08:40] Extracting A/V streams [VID_00023]
- [11:09:54] Reencoding video [VID_00023]
- Source Video: MPEG-2, 720x480, Hybrid
- Rate/Length: 29.970fps, 41,449 frames
- Bitrate: 4,344 Kbs
- [11:09:55] Reencoding: VID_00023, Pass 1 of 2
- [11:19:18] Reencoding: VID_00023, Pass 2 of 2
- [12:03:47] Video Encode complete
- [12:03:48] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [12:03:48] Multiplexing M2TS
- [12:04:28] Processing: VID_00024 (24 of 24)
- [12:04:28] Extracting A/V streams [VID_00024]
- [12:05:36] Reencoding video [VID_00024]
- Source Video: MPEG-2, 720x480, Hybrid
- Rate/Length: 29.970fps, 40,911 frames
- Bitrate: 4,078 Kbs
- [12:05:37] Reencoding: VID_00024, Pass 1 of 2
- [12:14:34] Reencoding: VID_00024, Pass 2 of 2
- [12:56:08] Video Encode complete
- [12:56:08] Processing audio tracks
- Track 4352 (eng): Keeping original audio
- [12:56:08] Multiplexing M2TS
[12:56:47]PHASE ONE complete
[12:56:47]PHASE TWO - Rebuild Started
- [12:56:47] Rebuilding BD file Structure
[12:57:02] - Encode and Rebuild complete
[12:57:02] Writing BD structure to ISO file
- ImgBurn completed successfully
- SIMPSONS_S3 folder removed.
- WORKFILES folder removed.
[13:25:04] JOB: SIMPSONS_S3 finished.
==========================
[13:25:04] END - BATCH SEQUENCE
==========================
[Options]
VERSION=0.46.0.3
MODE=0
ENCODE_QUALITY=3
ONEPASS_ENCODING=0
AUTO_QUALITY=0
TARGET_SIZE=23500
AUTO_BURN=2
PRIORITY_CLASS=0
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
RESIZE_1440=0
RESIZE_720=0
DEINTERLACE=1
SD_TO_1080=0
CONVERT_WIDE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=0
AC3_192=0
KEEP_HD_AUDIO=1
AVCHD=1
REMOVE_WORKFILES=1
MOVIE_ONLY_LOOP=0
REMOVE_OUTPUT=1
USE_FILTERS=0
BDMV_CERT_ONLY=0
USE_LAVF=0
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
UNMASK_CHAPTER=1
COMPLETION_BEEP=0
DGDECNV=0
OUTPUT_3D=0
NEROAAC=0
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=1
CUSTOM_TARGET_SIZE=23500
ENABLE_TEST=1
QUICK_EXTRAS=0
ENABLE_BLANKING=1
IMPORT_THRESHOLD=21
[Paths]
SOURCE_PATH=E:\BDS\SIMP_S3\IMPORTS\SIMPSONS_S3\
WORKING_PATH=F:\BDS\SIMP_S3\

[jdobbs]

@slvrsrfr

Could you post the content of one of the .AVS files so I can look at it? I'm guessing it has something to do with the fact that these are hybrid files. That means that parts of them are telecined and other parts aren't.

[slvrsrfr]

You bet - I appreciate your alacrity! :)

So, the season 3 files were wiped, but I had the same behavior on season 8. There were 2 acs files per episode, let me know if you want anything else!

VID_00001.AVS contents:
#Created by BD Rebuilder - v0.46.03 (beta)
DirectshowSource("F:\BDS\SIMP_S8\IMPORTS\SIMPSONS_S7\BDMV\STREAM\00001.m2ts", fps=29.97, framecount=41999, ConvertFPS=true, audio=false)
ConvertToYV12()
LoadPlugin("C:\Temp\Software\BD_Rebuilder\tools\decomb521.dll")
FieldDeinterlace(blend=true)
ConvertToYV12().AssumeFPS(30000,1001)

AUD_00001_4352.AVS contents:
#Created by BD Rebuilder - v0.46.03 (beta)
LoadPlugin("C:\Temp\Software\BD_Rebuilder\tools\nicaudio.dll")
audio=NicAC3Source("00001.track_4352.ac3")
audio = (AudioChannels(audio) > 6) ? GetChannel(audio,1,2,3,4,7,8) : audio
ConvertAudioTo16bit(ResampleAudio(audio, 48000))