BD Rebuilder Beta - Bug Reports Only

[jdobbs]

@steveg32

I picked up SKYLINE (since that's one of the discs you reported as having sync issues). I've loaded your INI into my system and will run it today. I'll report the results. Well "Skyline" completed -- and it is 100% in-sync, and I encoded it with the exact same settings as you. This seems to be the pattern for this. Other's report sync problems, and when I run the exact same movie it works fine for me. It's really frustrating because there are several people who have reported sync issues on DVD output -- and I can't find a single disc with issues. Are you using the exact versions of FFDSHOW, HAALI, and AVISYNTH that are recommended in the first post of this thread?

I see that you're using Windows XP and I'm using Windows 7 -- but I can't see why that would matter.

What codec do you have selected for AVC in FFDSHOW? I'm using "ffmpeg-mt"... although I don't think it makes a difference either.

Are you using an original commercial disc as the source? What did you use to rip it? I used AnyDVD HD (v6.8.0.0).

What are you using for playback? Is it a standalone player?

How far off is the sync? A half second is a long time -- is it close?

Just a note: The output was undersized by quite a bit -- but that is normal because the resulting bitrate would have been too high if it tried to fill the disc (over 11Mbs, way too high for DVD, it's because the movie isn't very long).

[steveg32]

@jdobbs

Well "Skyline" completed -- and it is 100% in-sync, and I encoded it with the exact same settings as you. This seems to be the pattern for this. Other's report sync problems, and when I run the exact same movie it works fine for me. It's really frustrating because there are several people who have reported sync issues on DVD output -- and I can't find a single disc with issues. Are you using the exact versions of FFDSHOW, HAALI, and AVISYNTH that are recommended in the first post of this thread?

I see that you're using Windows XP and I'm using Windows 7 -- but I can't see why that would matter.

What codec do you have selected for AVC in FFDSHOW? I'm using "ffmpeg-mt"... although I don't think it makes a difference either.

Are you using an original commercial disc as the source? What did you use to rip it? I used AnyDVD HD (v6.8.0.0).

What are you using for playback? Is it a standalone player?

How far off is the sync? A half second is a long time -- is it close?

Just a note: The output was undersized by quite a bit -- but that is normal because the resulting bitrate would have been too high if it tried to fill the disc (over 11Mbs, way too high for DVD, it's because the movie isn't very long).

Yes, I am using the exact versions of FFDSHOW, HAALI, and AVISYNTH that are recommended in the first post of this thread. I always uninstall and default reinstall all 3 with each new version of BD-Rebuilder, then run Inspect.exe to make sure all is OK.

H.264/AVC is enabled (libavcodec) in FFDSHOW (I think this answers your question "What codec do you have selected for AVC in FFDSHOW? I'm using "ffmpeg-mt"...").

I used an original commercial disc as the source. I also used AnyDVD HD (v6.8.0.0) to rip it.

I use CyberLink PowerDVD Ultra version 7.3 for PC playback. My Blu-ray standalone is a Pioneer BDP-121 Blu-ray Disc Player. My DVD standalones are JVC DR-MV79B 1080p HD-Upconverting DVD-VCR Combo Recorder; and a LiteOn LVW-5045 HDD & DVD Recorder.

The sync is at least a half second long (very noticeable). Note: In all three attempts for Jackass 3 (1x @ DVD-5 Theatrical, 1x @ DVD-5 Director's Cut, & 1x @ DVD-9 Director's Cut), the movie starts out of sync then goes completely in sync till the end (at running time ?, Chapter ? - damn I already trashed it & overwrote the DVD - sorry). Skyline was out of sync from start to end. :confused: Btw, my Skyline B-r to BD-25 backup had no sync issues so I doubt it was a bad rip.

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

Fyi, I'm not sure if BD-Reb's DVD Output auto overides Target Size in Settings, but if I do not select DVD-5 in Settings>Output Options>Target Size BD-5 (DVD-5), BD-Reb creates a DVD size that ImgBurn says is too big to burn to DVD-5 (it's close but still too large). Found this out when I left Target Size at BD-25. Didn't try DVD-9 so I don't know if results would be same with ImgBurn.

Also fyi, all titles I've listed with these issues have had no sync issues when I convert B-r to DVD using AVS Video Converter 7.0

Mahalo for all you do jdobbs. Go Silverswords! :)

[HatchetMan]

I have updated the first post of this thread with an updated version of BD-RB (v0.38.02).
A flawless full backup of HP5 to BD25, thanks!

[jdobbs]

Fyi, I'm not sure if BD-Reb's DVD Output auto overides Target Size in Settings, but if I do not select DVD-5 in Settings>Output Options>Target Size BD-5 (DVD-5), BD-Reb creates a DVD size that ImgBurn says is too big to burn to DVD-5 (it's close but still too large). Found this out when I left Target Size at BD-25. Didn't try DVD-9 so I don't know if results would be same with ImgBurn. The sizes selected for BD output are ignored. It's only the size you select from the ALTERNATE output list that matter for DVD output. However, even if you select DVD-9 you will only get a little less than 5GB for output. That's because the movie is only an hour and a half -- and you are maxing the bitrate.

In the INI you posted you have ALTERNATE/DVD selected for DVD-9 sizing. That's why it won't fit on a DVD-5.

[steveg32]

The sizes selected for BD output are ignored. It's only the size you select from the ALTERNATE output list that matter for DVD output. However, even if you select DVD-9 you will only get a little less than 5GB for output. That's because the movie is only an hour and a half -- and you are maxing the bitrate.

In the INI you posted you have ALTERNATE/DVD selected for DVD-9 sizing. That's why it won't fit on a DVD-5.

@jdobbs

Re: The sizes selected for BD output are ignored.

Yes, I realize DVD-9 sizing won't fit on a DVD-5 (I believe I previously mentioned I did not try burning my DVD-9 output with ImgBurn). I only played it back with PowerDVD and saw the same sync issues as my DVD-5 size playbacks.

Nonetheless, I am doing Jackass 3 again set for DVD-5 sizing. I purposely selected Target Size to BD-25 in Output Options to show how BD-Reb creates a DVD-5 size that ImgBurn says is too big to burn to a DVD-5. I will post results & screen shots when complete. Til then Aloha jdobbs.

[omegaman7]

I hate doing this, but I gotta ask. I usually use virtualdub Mod, for finding exact frames of Dvd/avi files. It apparently doesn't like M2TS files. Unless my version is severely outdated. Probably...
TMT3 can still Blu ray frames, but finding the exact frame every time would be challenging to say the least. Is there a program that I could use to accomplish this? I'm experiencing pixelation(darker scenery), in some of the outputs, and in order to post comparisons of my findings, I'm gonna need to find a program that can do this. I will of course continue my search for one, but I always welcome opinions/suggestions.

[PurpleMan]

I hate doing this, but I gotta ask. I usually use virtualdub Mod, for finding exact frames of Dvd/avi files. It apparently doesn't like M2TS files. Unless my version is severely outdated. Probably...
TMT3 can still Blu ray frames, but finding the exact frame every time would be challenging to say the least. Is there a program that I could use to accomplish this? I'm experiencing pixelation(darker scenery), in some of the outputs, and in order to post comparisons of my findings, I'm gonna need to find a program that can do this. I will of course continue my search for one, but I always welcome opinions/suggestions.

Just create an avisynth script and load into virtualdub. Install avisynth 2.5 or later, create a text file named "whatever.avs", and type the following lines:

DirectShowSource("c:\path\filename.mt2s")
converttorgb()

save the file and load the .avs into virtualdub.

[jdobbs]

@jdobbs

Re: The sizes selected for BD output are ignored.

Yes, I realize DVD-9 sizing won't fit on a DVD-5 (I believe I previously mentioned I did not try burning my DVD-9 output with ImgBurn). I only played it back with PowerDVD and saw the same sync issues as my DVD-5 size playbacks.

Nonetheless, I am doing Jackass 3 again set for DVD-5 sizing. I purposely selected Target Size to BD-25 in Output Options to show how BD-Reb creates a DVD-5 size that ImgBurn says is too big to burn to a DVD-5. I will post results & screen shots when complete. Til then Aloha jdobbs. ??? So if you understand that sizes selected for BD output are ignored... why are you telling me that you are selecting "Target Size to BD-25 to show..." -- either you don't understand what I'm saying or I don't understand what you're saying.

[thegame]

Hi jdobbs, sorry up front for posting this question in this thread, but I didn't know where else to post it, and didn't want to start a new thread for such a simple question, first right up front I want to tell you this program is GREAT(I know I have said this before) I have had no issues whatsoever with any version you post(knocks on wood) but last night I did a project and noticed in the settings this,

"use open GOPs for encoding"

I am curious, what is the difference between encoding with open GOPS vs non open GOPs? does it affect quality?

Thanks for your time and GREAT software.

[jdobbs]

Hi jdobbs, sorry up front for posting this question in this thread, but I didn't know where else to post it, and didn't want to start a new thread for such a simple question, first right up front I want to tell you this program is GREAT(I know I have said this before) I have had no issues whatsoever with any version you post(knocks on wood) but last night I did a project and noticed in the settings this,

"use open GOPs for encoding"

I am curious, what is the difference between encoding with open GOPS vs non open GOPs? does it affect quality?

Thanks for your time and GREAT software. A closed GOP means that all dependencies/references are limited to a specific group of pictures. In BD-RB that would be either 24 frames or 48 frames depending upon bitrate. With open GOP the references can go across groups.

The upside to open GOPs is slightly better compression. The downside is dependencies outside of groups. I'd say that closed GOPs may have a bit of an advantage for broadcasting where there is a higher probability of data being lost -- but probably not so much for BD. So, generally it is probably better to use open GOPs. But don't expect to notice a huge difference in most cases.

[thegame]

A closed GOP means that all dependencies/references are limited to a specific group of pictures. In BD-RB that would be either 24 frames or 48 frames depending upon bitrate. With open GOP the references can go across groups.

The upside to open GOPs is slightly better compression. The downside is dependencies outside of groups. I'd say that closed GOPs may have a bit of an advantage for broadcasting where there is a higher probability of data being lost -- but probably not so much for BD. So, generally it is probably better to use open GOPs. But don't expect to notice a huge difference in most cases.

Thank you for the fast response, and explanation, I was also curious about that because I do a lot of x264 encoding and was having issues with chapter points(actually still am) and someone had mentioned that open GOPs vs non open might be the issue, I have been using the default setting of open and my chapter points don't all line up on my forced I-Frame, so back to BD-RB, so should that be ticked then and not the default un ticked? or just leave it alone?

Thanks again

[jdobbs]

Thank you for the fast response, and explanation, I was also curious about that because I do a lot of x264 encoding and was having issues with chapter points(actually still am) and someone had mentioned that open GOPs vs non open might be the issue, I have been using the default setting of open and my chapter points don't all line up on my forced I-Frame, so back to BD-RB, so should that be ticked then and not the default un ticked? or just leave it alone?

Thanks again It shouldn't be an issue if chapter points are set within X264 (which BD-RB does). I would think specifying a chapter point would force a closed GOP there. I tick it -- but as I said, don't expect a huge difference.

[Added] Well, that assumption isn't entirely correct. Here are the rules from wth X264 Wiki:qpfile
Manual override to standard ratecontrol. Specify a file that gives the quantizer and frametype for
specifiedframes. The format is 'framenum frametype quantizer'. For example:

0 I 18 < IDR (key) I-frame
1 P 18 < P-frame
2 B 18 < Referenced B-frame
3 i 18 < Non-IDR (non-key) I-frame
4 b 18 < Non-referenced B-frame
5 K 18 < Keyframe*

You don't need to specify every frame

Using -1 as the desired quantizer allows x264 to choose the optimal quantizer value, useful when
only needing toset the frametype . Having a large number of specified frame types and quantizers
while still letting x264 choose intermittently decreases x264's performance. 'Keyframe' is a generic
keyframe/seekpoint type that equates to a IDR I-Frame if --open-gop is none, otherwise it
equates to a Non-IDR I-Frame flagged with the Recovery Point SEI

[omegaman7]

@Purpleman, thanks! I'm very green when it comes to scripting. Which isn't good, considering I want to program one day. Gotta start somewhere I suppose ;) It works perfectly. You have yourself a wonderful day. You just made mine! :D

See, I'd like to compare the speed settings. It's possible, that setting the speeds higher/faster produces a less than desirable output quality. Of course this is logically true, but I was informed a while back, that the difference should be negligible...

[steveg32]

??? So if you understand that sizes selected for BD output are ignored... why are you telling me that you are selecting "Target Size to BD-25 to show..." -- either you don't understand what I'm saying or I don't understand what you're saying.

@jdobbs

My understanding is if BD output is ignored then it should not matter what Target Size is ticked in Settings>Output Options. So, if I tick Alternate Output to be "DVD-5, 720X480/576, AC Audio", my resulting DVD-5 size should be 4686086144 or approximately 4.36 GB, even if BD-25 is ticked in Settings>Output Options? If your answer to this is yes then why, in my described scenario, is my resulting DVD-5 size 4.41 GB (which ImgBurn states is too large to write to a DVD-5)?

Let me start over by asking 1 simple question:

If I select Movie-only Alternate Output to be "DVD-5, 720X480/576, AC Audio", should I also select "Target Size BD-5 (DVD-5)" in Settings>Output Options?

Mahalo for your patience & understanding in this matter.

[omegaman7]

Well, I'm afraid that won't work. I copied frame 42702 from Chronicles of narnia VOTDT, and the aspect ratio is wrong, and the numbered frames are erratic. What I mean by that is, If I grab 42702 at one moment, close the program and load it again, it'll be a different frame next time. So much for that. THanks anyway ;)

I'm an idiot. The aspect ratio is fine. I wasn't acknowledging my PC's Native 1920 x 1200 resolution. THe bars on top and bottom are normal on my screen. I suppose It's normal for most screens though. Even 16:9 screens. I wish they'd just pick a ratio... It's not right when a 16:9 tv has bars on top and bottom. In my opinion anyway. The frame numbers seem to vary though.

[jdobbs]

@jdobbs

My understanding is if BD output is ignored then it should not matter what Target Size is ticked in Settings>Output Options. So, if I tick Alternate Output to be "DVD-5, 720X480/576, AC Audio", my resulting DVD-5 size should be 4686086144 or approximately 4.36 GB, even if BD-25 is ticked in Settings>Output Options? If your answer to this is yes then why, in my described scenario, is my resulting DVD-5 size 4.41 GB (which ImgBurn states is too large to write to a DVD-5)?

Let me start over by asking 1 simple question:

If I select Movie-only Alternate Output to be "DVD-5, 720X480/576, AC Audio", should I also select "Target Size BD-5 (DVD-5)" in Settings>Output Options?

Mahalo for your patience & understanding in this matter. If you select "DVD-5, 720X480/576, AC Audio" -- it really doesn't matter what you select under Settings/Output Options. That setting is for normal processing -- ALTERNATE output is processed differently. In fact it is an entirely different set of routines.

The only exception to that rule is a check BD-RB does that warns when output won't fit -- I've been meaning to disable that for ALTERNATE output, but I keep forgetting.

Output from "DVD-5, 720X480/576, AC Audio" is targeted at between 4.20 - 4.30GB (I purposely avoid outer edges due to a tendency for a lot of discs to be weak there). I've never seen one oversize. I can say, though, that the ouput from the settings you posted (that I used for testing) were about 4.50GB -- but that was because "DVD-9, 720X480/576, AC Audio" was selected and the movie was too short to allow that high a bitrate.

[steveg32]

If you select "DVD-5, 720X480/576, AC Audio" -- it really doesn't matter what you select under Settings/Output Options. That setting is for normal processing -- ALTERNATE output is processed differently. In fact it is an entirely different set of routines.

The only exception to that rule is a check BD-RB does that warns when output won't fit -- I've been meaning to disable that for ALTERNATE output, but I keep forgetting.

Output from "DVD-5, 720X480/576, AC Audio" is targeted at between 4.20 - 4.30GB (I purposely avoid outer edges due to a tendency for a lot of discs to be weak there). I've never seen one oversize. I can say, though, that the ouput from the settings you posted (that I used for testing) were about 4.50GB -- but that was because "DVD-9, 720X480/576, AC Audio" was selected and the movie was too short to allow that high a bitrate.

@jdobbs

Storage Media "safe size" limits:

74 min Cd-Rom (650mb) = 681574400
80 (703mb) = 737148928
120 Dvd-R (4464mb)= 4680843264

..std dvdrom media stating "4.7 gig" is misleading as the lead in and lead out space required gobbles some of this
..so the 'common consensus' out there is make max write space limit the 4464 megabytes for Std Dvd Media.

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

"BD-Reb" default target size for "DVD-5 MOVIE-ONLY/ALTERNATE OUTPUT" mode is 4686086144.

Q: 4686086144 bytes = ? megabytes
A: 4469 megabytes (4.3642578125 gigabytes)

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

If you change the default DVD-5 Target Size to 4680843264 (4464 MB), voila, no more oversize burning issues with ImgBurn or any other DVD burning software. Especially when burning to DVD+RW discs.

Please see my next post and screen shots. Mahalo for all you do jdobbs.

[omegaman7]

A dvd-r can handle closer to 4481Mb. Taiyo Yuden anyway. I trust them on the outer edge. THat really is pushing it though. I agree with Jdobbs on this one. I've experimented quite a bit on this. Dvd +R's hold even less. 4470 - 4472 I believe. The difference in video quality really is negligible when talking 30Mb...

I'll be re-encoding Chronicles of narnia at the slowest setting, to see if the difference is apparent. If it is, I'll no longer be using the faster/fastest settings. Pinpointing the exact frame is apparently gonna be slightly challenging :(

[steveg32]

??? So if you understand that sizes selected for BD output are ignored... why are you telling me that you are selecting "Target Size to BD-25 to show..." -- either you don't understand what I'm saying or I don't understand what you're saying.

@jdobbs

Here's the DVD-5, 720X480/576, AC3 Audio redo I did for Jackass 3:

Note: Sync issues start at beginning of movie and occurs until approx running time 00:30:15. Then I noticed a glitch at approx 00:30:16 (in Chapter 16 of 49). Following the glitch the sync issues end and the rest of the movie is in complete sync from 00:30:20 through the end of the movie (01:39:38).

Here's the INI:

[Options]
VERSION=0.38.0.2
MODE=1
ENCODE_QUALITY=0
ONEPASS_ENCODING=2
AUTO_QUALITY=1
MINIMIZE_TO_TRAY=1
AUDIO_TO_KEEP=eng;
SUBS_TO_KEEP=eng;
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
DEINTERLACE=1
SD_TO_1080=0
CONVERT_WIDE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=1
AVCHD=0
REMOVE_WORKFILES=1
MOVIE_ONLY_LOOP=1
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=0
USE_LAVF=0
IVTC_PULLDOWN=1
ASSUME_DVD_PAL=0
AUTO_BLANK=0
AUDIO_TRACK_LIMIT=1
SUBTITLE_TRACK_LIMIT=1
CUSTOM_TARGET_SIZE=23500
MOVIEONLY_TYPE=1
ALTCRF=20
ALT_TARGET=1000
ALTMETHOD=0
TARGET_SIZE=23500
ENCODER=0
[Paths]
WORKING_PATH=H:\BD-REBUILDER\DVD-5, 720X480_576, AC3 AUDIO\
SOURCE_PATH=H:\ANYDVD HD BLU-RAY RIPS\JACKASS_3\

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

Here's the INF:

[Status]
LABEL=JACKASS_3
VERSION=v0.38.02 (beta)
SOURCE_SIZE=24442490880
SOURCE_VIDEO_SIZE=24442490880
TARGET_SIZE=24641536000
REDUCTION=1.00814340571823
RESIZE_1080=0
AUDIO_TO_KEEP=eng;
KEEP_HD_AUDIO=-1
SUBS_TO_KEEP=eng;
BACKUP_MODE=1
MOVIEONLY_TYPE=1
USE_LAVF=0
QUICK=0
ENCODE_STEP=0
COMPLETED=15
REBUILD_COMPLETE=1
[00246]
AUDIO=0001
PGS=10000
M2TS_TARGET=7495213615
NSIZE=0
FLINK=-1
MLINK=0
[00261]
M2TS_TARGET=922316302
AUDIO=0001
NSIZE=0
FLINK=-1
MLINK=0
[00248]
M2TS_TARGET=4243482514
AUDIO=0001
NSIZE=0
FLINK=-1
MLINK=0
[00262]
M2TS_TARGET=354651752
AUDIO=0001
NSIZE=0
FLINK=-1
MLINK=0
[00250]
M2TS_TARGET=2078321085
AUDIO=0001
NSIZE=0
FLINK=-1
MLINK=0
[00263]
M2TS_TARGET=362078398
AUDIO=0001
NSIZE=0
FLINK=-1
MLINK=0
[00252]
M2TS_TARGET=662241241
AUDIO=0001
NSIZE=0
FLINK=-1
MLINK=0
[00264]
M2TS_TARGET=241418634
AUDIO=0001
NSIZE=0
FLINK=-1
MLINK=0
[00254]
M2TS_TARGET=585137917
AUDIO=0001
NSIZE=0
FLINK=-1
MLINK=0
[00265]
M2TS_TARGET=171946358
AUDIO=0001
NSIZE=0
FLINK=-1
MLINK=0
[00256]
M2TS_TARGET=598046282
AUDIO=0001
NSIZE=0
FLINK=-1
MLINK=0
[00266]
M2TS_TARGET=505265861
AUDIO=0001
NSIZE=0
FLINK=-1
MLINK=0
[00258]
M2TS_TARGET=4121063644
AUDIO=0001
NSIZE=0
FLINK=-1
MLINK=0
[00267]
M2TS_TARGET=182996513
AUDIO=0001
NSIZE=0
FLINK=-1
MLINK=0
[00260]
M2TS_TARGET=2117355882
AUDIO=0001
NSIZE=0
FLINK=0
MLINK=0

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

Here's the LOG:

[20:37:57] BD Rebuilder v0.38.02 (beta)
- Source: JACKASS_3
- Input BD size: 22.76 GB
- Approximate total content: [01:39:44.561]
- Windows Version: 5.1 [2600]
- MOVIE-ONLY/ALTERNATE OUTPUT mode enabled
- Mode: DVD-5, 720x480/576, AC3 Audio
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[20:37:57] PHASE ONE, Encoding
- [20:37:57] Extracting A/V streams [VID_00246]
- [20:59:01] Reencoding: VID_00246 (1 of 15)
- [20:59:01] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 43,582 frames
- Bitrate: 5,594 Kbs
- [20:59:01] Reencoding: VID_00246
- [22:16:53] Video Encode complete
- [22:16:53] Reencoding audio tracks (if req'd)
- [22:22:32] Multiplexing M2TS
- [22:22:33] Extracting A/V streams [VID_00261]
- [22:23:33] Reencoding: VID_00261 (2 of 15)
- [22:23:33] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 5,511 frames
- Bitrate: 5,432 Kbs
- [22:23:33] Reencoding: VID_00261
- [22:33:44] Video Encode complete
- [22:33:44] Multiplexing M2TS
- [22:33:44] Extracting A/V streams [VID_00248]
- [22:38:01] Reencoding: VID_00248 (3 of 15)
- [22:38:01] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 24,621 frames
- Bitrate: 5,607 Kbs
- [22:38:01] Reencoding: VID_00248
- [23:23:20] Video Encode complete
- [23:23:20] Multiplexing M2TS
- [23:23:20] Extracting A/V streams [VID_00262]
- [23:23:44] Reencoding: VID_00262 (4 of 15)
- [23:23:44] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 2,105 frames
- Bitrate: 5,471 Kbs
- [23:23:44] Reencoding: VID_00262
- [23:27:38] Video Encode complete
- [23:27:38] Multiplexing M2TS
- [23:27:38] Extracting A/V streams [VID_00250]
- [23:29:44] Reencoding: VID_00250 (5 of 15)
- [23:29:44] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 12,167 frames
- Bitrate: 5,553 Kbs
- [23:29:44] Reencoding: VID_00250
- [23:53:34] Video Encode complete
- [23:53:34] Multiplexing M2TS
- [23:53:34] Extracting A/V streams [VID_00263]
- [23:53:57] Reencoding: VID_00263 (6 of 15)
- [23:53:57] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 2,131 frames
- Bitrate: 5,522 Kbs
- [23:53:57] Reencoding: VID_00263
- [23:57:50] Video Encode complete
- [23:57:50] Multiplexing M2TS
- [23:57:50] Extracting A/V streams [VID_00252]
- [23:58:29] Reencoding: VID_00252 (7 of 15)
- [23:58:29] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 3,873 frames
- Bitrate: 5,559 Kbs
- [23:58:29] Reencoding: VID_00252
- [00:05:47] Video Encode complete
- [00:05:47] Multiplexing M2TS
- [00:05:47] Extracting A/V streams [VID_00264]
- [00:06:02] Reencoding: VID_00264 (8 of 15)
- [00:06:02] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,424 frames
- Bitrate: 5,508 Kbs
- [00:06:02] Reencoding: VID_00264
- [00:08:30] Video Encode complete
- [00:08:30] Multiplexing M2TS
- [00:08:30] Extracting A/V streams [VID_00254]
- [00:09:06] Reencoding: VID_00254 (9 of 15)
- [00:09:06] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 3,390 frames
- Bitrate: 5,616 Kbs
- [00:09:06] Reencoding: VID_00254
- [00:15:26] Video Encode complete
- [00:15:26] Multiplexing M2TS
- [00:15:26] Extracting A/V streams [VID_00265]
- [00:15:38] Reencoding: VID_00265 (10 of 15)
- [00:15:38] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,009 frames
- Bitrate: 5,539 Kbs
- [00:15:38] Reencoding: VID_00265
- [00:17:31] Video Encode complete
- [00:17:31] Multiplexing M2TS
- [00:17:31] Extracting A/V streams [VID_00256]
- [00:18:07] Reencoding: VID_00256 (11 of 15)
- [00:18:07] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 3,498 frames
- Bitrate: 5,559 Kbs
- [00:18:07] Reencoding: VID_00256
- [00:24:32] Video Encode complete
- [00:24:32] Multiplexing M2TS
- [00:24:32] Extracting A/V streams [VID_00266]
- [00:25:03] Reencoding: VID_00266 (12 of 15)
- [00:25:03] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 2,980 frames
- Bitrate: 5,509 Kbs
- [00:25:03] Reencoding: VID_00266
- [00:30:08] Video Encode complete
- [00:30:08] Multiplexing M2TS
- [00:30:08] Extracting A/V streams [VID_00258]
- [00:34:50] Reencoding: VID_00258 (13 of 15)
- [00:34:50] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 23,914 frames
- Bitrate: 5,606 Kbs
- [00:34:50] Reencoding: VID_00258
- [01:18:28] Video Encode complete
- [01:18:28] Multiplexing M2TS
- [01:18:28] Extracting A/V streams [VID_00267]
- [01:18:39] Reencoding: VID_00267 (14 of 15)
- [01:18:39] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 1,050 frames
- Bitrate: 5,675 Kbs
- [01:18:39] Reencoding: VID_00267
- [01:20:26] Video Encode complete
- [01:20:26] Multiplexing M2TS
- [01:20:26] Extracting A/V streams [VID_00260]
- [01:22:37] Reencoding: VID_00260 (15 of 15)
- [01:22:37] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 12,231 frames
- Bitrate: 5,634 Kbs
- [01:22:37] Reencoding: VID_00260
- [01:43:35] Video Encode complete
- [01:43:35] Multiplexing M2TS
[01:43:35]PHASE ONE complete
[01:43:35]PHASE TWO - Rebuild Started
- [01:43:35] Rebuilding stream 00246 [1 of 15]
- [01:43:35] Rebuilding stream 00261 [2 of 15]
- [01:43:35] Rebuilding stream 00248 [3 of 15]
- [01:43:35] Rebuilding stream 00262 [4 of 15]
- [01:43:35] Rebuilding stream 00250 [5 of 15]
- [01:43:35] Rebuilding stream 00263 [6 of 15]
- [01:43:35] Rebuilding stream 00252 [7 of 15]
- [01:43:35] Rebuilding stream 00264 [8 of 15]
- [01:43:35] Rebuilding stream 00254 [9 of 15]
- [01:43:35] Rebuilding stream 00265 [10 of 15]
- [01:43:35] Rebuilding stream 00256 [11 of 15]
- [01:43:35] Rebuilding stream 00266 [12 of 15]
- [01:43:35] Rebuilding stream 00258 [13 of 15]
- [01:43:35] Rebuilding stream 00267 [14 of 15]
- [01:43:35] Rebuilding stream 00260 [15 of 15]
- [01:43:35] Building ALTERNATE OUTPUT Structure
- [01:47:59] Converting 1 subtitles to DVD format.
- [01:48:39] Starting MPLEX.
- [01:55:40] Multiplexing 1 subtitles into stream.
- [02:01:16] Building DVD File Structure.
[02:08:11] - Encode and Rebuild complete
- WORKFILES folder removed.
[02:08:11]JOB: JACKASS_3 finished.

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

Mahalo for all you do jdobbs.

Here's the screen shots (in particular see # 11):

[jdobbs]

@steveg32

Something is causing an oversize and sync issues in your case -- I'll pick up "Jackass 3" and see what I can find.

[Edit] When I read back my original comment I sounded like an arrogant prick. It doesn't really bother me to be one -- but I don't lke to sound like it. So I've edited it. :)

[omegaman7]

It would appear that this particular scene has some slight artifacting to the left of the Rat on even the original/source video as well(Dark scenery). However smoother. The difference in all 3 appears to be minor. I do find there to be a fairly substantial difference between Faster and slowest settings. I'll likely be choosing Slowest output option from now on. Unless something doesn't require much compression ;) It would appear that the Jpg container introduced some moderate artifacting. use your imagination :p

Rather strange about the frame numbers. Not sure how that could happen :confused:

Here's the Original capture. Frame number 42673.
http://img820.imageshack.us/img820/5398/42673original.th.jpg (http://img820.imageshack.us/i/42673original.jpg/)
Here's a capture of the "Slowest" output speed. Frame number 42702.
http://img28.imageshack.us/img28/9953/42702slowest.th.jpg (http://img28.imageshack.us/i/42702slowest.jpg/)
Here's a capture of the "Faster" output speed. Frame number 42702.
http://img6.imageshack.us/img6/5051/42702faster.th.jpg (http://img6.imageshack.us/i/42702faster.jpg/)

[jdobbs]

If you have blocking, it wouldn't be unusual for it to be slightly amplified in the reencode. That's because the encoder doesn't know it isn't supposed to be there -- and tries its best to reproduce it. But, honestly I don't really see it in your pictures (at least not on this computer).

I'd recommend in the future that you use PNG... JPG always introduces it's own version of the picture that can distort comparisons. PNG is lossless.

[omegaman7]

LOL, I realize PNG is lossless, but it would also eat bandwidth. The encoder does do a pretty good job reproducing it. It's just something I'll/we'll have to deal with. I really do need a new monitor :(
Any thoughts on how the frames from the output could be off numerically from the original?

[jdobbs]

LOL, I realize PNG is lossless, but it would also eat bandwidth. The encoder does do a pretty good job reproducing it. It's just something I'll/we'll have to deal with. I really do need a new monitor :(
Any thoughts on how the frames from the output could be off numerically from the original? Hmmm... the frame number mismatch is interesting. It's very, very close to the difference you'd expect between a 24fps source and a 23.976fps source for the same point in time -- close enough that I have to wonder about it. What disc is this?

[omegaman7]

Chronicles of narnia: Voyage of the dawn treader. region 1/A.

[jdobbs]

Chronicles of narnia: Voyage of the dawn treader. region 1/A. Hmmm... I think I still have that one on my hard drive. I think I may play with it a little and see what's up. You never know when some seemingly unimportant little glitch will turn up something unexpected.

[jdobbs]

@steveg32

Just loaded your settings into BD-Rebuilder (from your post) and ran "Jackass 3" -- it created a perfectly synched DVD that was 4.28GB.

I don't know what to say. But I'm using the exact same BD-RB and the exact same source disc you are and it works 100% correctly. That seems to just leave your computer, your settings, or your playback method. Something is different. Have you burned it to a blank DVD and played it back on a standalone player?

Frankly I'm not sure what else I can do?

[[SLiM]D12]

Just did an encode, Stand By Me R1 using BD-25 as size setting and it came out as 11GB. Not sure what went wrong. I've literally done HUNDREDS of backups and this being the first issue. Not sure what i need to provide, but plz let me know.

Thx
[SLiM]

[jdobbs]

D12;1502388']Just did an encode, Stand By Me R1 using BD-25 as size setting and it came out as 11GB. Not sure what went wrong. I've literally done HUNDREDS of backups and this being the first issue. Not sure what i need to provide, but plz let me know.

Thx
[SLiM] The most likely reason is that the original was 11GB (after removing unwanted audio) and BD-RB kept it intact (because it would fit as-is). It's never a good idea to reencode when it isn't necessary.

[1Bullet]

Prince of Persia, I have been reading all the posts on this movie in searches.
Looks more like the issues are with the film.
The movie is one hell of a test for BD Rebuilder.
Using windows 7 64bit ultimate.
I ripped the my Disc with DVDFab 8 however when I tried to do a movie only BD RB 0.38.32 was still scanning file 15 minutes later. It did the same thing with BD RB 0.37.07 as well.
I shut down BD rebuilder in task manager and restarted it again. Because BD rebuilder was trying to re open at the last file (prince of persia) it hung on opening. I moved the file to another location and then I could get BD RB opened.
Doing full back up will open after about a 5 minute scan with well over 250 files.
I did a movie only with DVDfab and the main movie was 139 video files. BD reduilder had issues opening the main movie that I had just ripped with DVDfab( I was just testing as main movie under 25 GB).
This is not an issue with my system as in my last post. Turn out to be either Power Dvd 11 or Total Media 5 had updated my Avisynth to 2.5.8.0 causing X264 to freeze.
Just a suggestion, maybe BD rebuilder should not remember last file opened.

[omegaman7]

Well...You can intervene this. Simply open the BDREBUILDER.INI file as TXT, delete the source directory and start fresh. ;) I had to do this once. Forget what the circumstances were :p

[steveg32]

@steveg32

Just loaded your settings into BD-Rebuilder (from your post) and ran "Jackass 3" -- it created a perfectly synched DVD that was 4.28GB.

I don't know what to say. But I'm using the exact same BD-RB and the exact same source disc you are and it works 100% correctly. That seems to just leave your computer, your settings, or your playback method. Something is different. Have you burned it to a blank DVD and played it back on a standalone player?

Frankly I'm not sure what else I can do?

@jdobbs

Yes I did burn to blank DVDs and the sync issues appeared on all my previously listed standalones. Oh well, can't win them all. Guess I'll continue to convert B-r to DVD using "AVS Converter 7.0". For some reason that program has never given me sync issues when converting B-r to DVD :confused: Only drawback is that it converts any HD, DTS, 7.1, 5.1 type audio to 2 Channel Stereo. :mad:

No pilikia jdobbs. Mahalo for all your kokua. I really appreciate it. U still da man in my book! My B-r backups are always flawless thanks to you. Aloha, brah :)

[omegaman7]

I've converted at least 6 Bd's to Dvd. I had no sync issues. I'm as curious as you are though. It's highly rare that I see the need to convert to dvd though. I love HD :D I do however understand the need to do it ;)

[[SLiM]D12]

The most likely reason is that the original was 11GB (after removing unwanted audio) and BD-RB kept it intact (because it would fit as-is). It's never a good idea to reencode when it isn't necessary.

I'm not sure i understand. The original BD was 29 GB in size, and i didn't do anything different in BD-RB, it just came out that much smaller.....

[RobertM]

If you are saying that the entire disc was originally 29GB then that can contain all kinds of stuff, including the "extras", such as outtakes, previews and directorial comments.

It you are saying that only the original m2ts stream (usually the biggest file in the "stream" folder) is 29GB, then that can include multiple audio and subtitle streams.

Either way, the most likely reason is that the original video content on the disc is ACTUALLY only 11GB (or a little less) once all of the other stuff is removed.

You can test this by looking at the BD-Rebuilder log file. When it gets to the stage where it wants to re-encode the video, does it ACTUALLY do any re-encoding, or does it just keep the original? The log file will say what it has done. If it just keeps the original then you can be assured that your rebuild contains the exact same video data that was on the original disc.

Regards,
Bob

[jdobbs]

D12;1502456']I'm not sure i understand. The original BD was 29 GB in size, and i didn't do anything different in BD-RB, it just came out that much smaller..... You need to post your log -- then I can tell you for sure.

[jdobbs]

@jdobbs

Yes I did burn to blank DVDs and the sync issues appeared on all my previously listed standalones. Oh well, can't win them all. Guess I'll continue to convert B-r to DVD using "AVS Converter 7.0". For some reason that program has never given me sync issues when converting B-r to DVD :confused: Only drawback is that it converts any HD, DTS, 7.1, 5.1 type audio to 2 Channel Stereo. :mad:

No pilikia jdobbs. Mahalo for all your kokua. I really appreciate it. U still da man in my book! My B-r backups are always flawless thanks to you. Aloha, brah :) I really wish I could figure out why it isn't working for you. I've gotten a couple of other similar reports -- while it seems to be working correctly for the majority of users.

There has to be some common thread... but findng it has become a pain in the okole... :)

[jdobbs]

@steveg32

Something is causing an oversize and sync issues in your case -- I'll pick up "Jackass 3" and see what I can find.

[Edit] When I read back my original comment I sounded like an arrogant prick. It doesn't really bother me to be one -- but I don't lke to sound like it. So I've edited it. :) I was just reviewing the two INF files and noticed that they aren't matching. Did you choose an alternate playlist when you did Jackass?

[KillingTime]

I got a couple of donations on Sunday so I've ordered Heartbreak Ridge (couldn't find it locally). I should be able to test it in a couple days. Can you post your .INI file? I have to make sure I'm using the same setup as you so I can repeat your issue.

I appreciate your offer -- but honestly I'd rather work with donations and make my own choices as to when, where, and what discs I test. Thanks, though. :)

OK.

The ini file was posted with the original report here:

http://forum.doom9.org/showthread.php?t=143716&page=591

I've linked to it rater than reposting to avoid duplication.

Also, I've just noticed that errors in raw source material caused by optical read errors can force the audio to jump out of sync with the video. This is not the fault of BDRebuilder as you don't write the mpeg encoding engine, and I'm not sure if there's anything you can do to detect this, but the log file on a recent rebuild of 'Flags of Our Fathers
' reported success when there were obviously probs. The source video jumped once or twice, and BDRebuilder video output went white for a few seconds in the same place. The audio was out of sync from that point forward. The obvious solution is to clean the disc and try again. This could be what has happened with Heartbreak Ridge, but if it is, I can't see where the problem is on the source material, and cleaning the disc has not changed anything.

Thanks.

[jdobbs]

OK.

The ini file was posted with the original report here:

http://forum.doom9.org/showthread.php?t=143716&page=591

I've linked to it rater than reposting to avoid duplication.

Also, I've just noticed that errors in raw source material caused by optical read errors can force the audio to jump out of sync with the video. This is not the fault of BDRebuilder as you don't write the mpeg encoding engine, and I'm not sure if there's anything you can do to detect this, but the log file on a recent rebuild of 'Flags of Our Fathers
' reported success when there were obviously probs. The source video jumped once or twice, and BDRebuilder video output went white for a few seconds in the same place. The audio was out of sync from that point forward. The obvious solution is to clean the disc and try again. This could be what has happened with Heartbreak Ridge, but if it is, I can't see where the problem is on the source material, and cleaning the disc has not changed anything.

Thanks. Heartbreak Ridge got delivered yesterday (I ordered it online), but I haven't run it yet. There shouldn't be errors reading -- as the reading software should pick that up via CRC errors. I've never had any issues of that type with AnyDVD HD.

Also, the post in your link doesn't contain the INI file. That is the LOG and the INF file. The INI is called BDREBUILDER.INI and is located in the installation folder. It contains all the saved settings.

[Sharc]

I ran some tests and have found this issue. It appears that the "End of Display" segment on the clearing portion of the subtitle display in the example you gave me isn't using the same time as the "Window Defiinition Segment" for that action. I think it is something peculiar to the way TSMUXER writes it (when it does the resizing) -- as I'd never seen that before in my testing.

Anyway, I've fixed it for the next release.
Will the fix be applied to the 720p downsized sup, or would I have to redo everything from scratch starting from the original 1080p disc?

[omegaman7]

I've ripped lots of discs. BD and DVD. I've had 2 lite-on drives that will ignore read errors. My current iHES108 drive is one of them. The other was an iHAP424.

@killingtime, is this disc translucent? I've also had trouble in the past, with discs like that. Really rather an ignorant design. The technology employs a light/eye/beam, and then they make a disc, that light can travel through. Genius... :rolleyes:

[jdobbs]

Will the fix be applied to the 720p downsized sup, or would I have to redo everything from scratch starting from the original 1080p disc? The fix will take care of it from the 720 downsized SUP, so you don't have to redo anything. BD-RB just takes the timing from the clearing Windows-Definition-Segment instead. But just as an FYI, as of a couple versions ago BD-RB doesn't use TSMUXER for resizing SUPs anymore (because it has a tendency to fail sometimes). BD-RB does the resize itself. So that oddity in the timestamp of the End-of-Display-Segment is gone from that point on.

[A.Fenderson]

Also, I've just noticed that errors in raw source material caused by optical read errors can force the audio to jump out of sync with the video
...
The source video jumped once or twice, and BDRebuilder video output went white for a few seconds in the same place. The audio was out of sync from that point forward. The obvious solution is to clean the disc and try again. This could be what has happened with Heartbreak Ridge, but if it is, I can't see where the problem is on the source material, and cleaning the disc has not changed anything.

I've had this happen as well, and while the issue is very manifest on playback of the rebuild, it can be very difficult to see any visible artifacts during playback of the rip it's based on: I only saw them once I identified the exact moment the rebuild messed up, then went back frame-by-frame, examining each in detail: I eventually found very small areas of flat-colored macroblocks on just a couple of frames. In my case, cleaning and reripping worked eventually, but I actually ended up ripping with a newer BD drive just to be sure. Never did AnyDVD-HD (ripping program) or BD-RB report an error while ripping/rebuilding the corrupted file.

I don't know if it's feasible, and somehow doubt it is, but some check on the integrity of the original video stream may help eliminate this problem with bad rips.

[jdobbs]

I've had this happen as well, and while the issue is very manifest on playback of the rebuild, it can be very difficult to see any visible artifacts during playback of the rip it's based on: I only saw them once I identified the exact moment the rebuild messed up, then went back frame-by-frame, examining each in detail: I eventually found very small areas of flat-colored macroblocks on just a couple of frames. In my case, cleaning and reripping worked eventually, but I actually ended up ripping with a newer BD drive just to be sure. Never did AnyDVD-HD (ripping program) or BD-RB report an error while ripping/rebuilding the corrupted file.

I don't know if it's feasible, and somehow doubt it is, but some check on the integrity of the original video stream may help eliminate this problem with bad rips. That would be virtually impossible. A frame-by-frame examination would take as long as an encode. Interesting, though, that in a couple thousand encodes I've never seen it. I guess I've been lucky with my drives.

[omegaman7]

That would be virtually impossible. A frame-by-frame examination would take as long as an encode. Interesting, though, that in a couple thousand encodes I've never seen it. I guess I've been lucky with my drives.
A cool computer case helps ;) Most cases have pretty dire cooling...

[[SLiM]D12]

Re-encoded again using custom size, was 7GB this time.........here's the log:


[12:13:28] BD Rebuilder v0.37.08 (beta)
- Source: STAND_BY_ME
- Input BD size: 29.25 GB
- Approximate total content: [02:42:11.511]
- Target BD size: 22.95 GB
- Windows Version: 6.1 [7601]
- Quality: High Quality (Default), Two Pass
- Audio Settings: AC3=0 DTS=0 HD=1 Kbs=640
[12:13:28] PHASE ONE, Encoding
- [12:13:28] Extracting A/V streams [VID_00021]
- [12:13:29] Reencoding: VID_00021 (1 of 14)
- [12:13:29] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 24 frames
- [12:13:29] Reencoding: VID_00021, Pass 1 of 1
- [12:13:30] Video Encode complete
- [12:13:30] Reencoding audio tracks (if req'd)
- [12:13:30] Multiplexing M2TS
- [12:13:30] Extracting A/V streams [VID_00081]
- [12:13:35] Reencoding: VID_00081 (2 of 14)
- [12:13:35] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 1,440 frames
- [12:13:35] Reencoding: VID_00081, Pass 1 of 1
- [12:13:50] Video Encode complete
- [12:13:50] Reencoding audio tracks (if req'd)
- [12:13:50] Multiplexing M2TS
- [12:13:50] Extracting A/V streams [VID_00101]
- [12:13:55] Reencoding: VID_00101 (3 of 14)
- [12:13:55] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 1,012 frames
- [12:13:55] Reencoding: VID_00101, Pass 1 of 1
- [12:14:10] Video Encode complete
- [12:14:10] Reencoding audio tracks (if req'd)
- [12:14:10] Multiplexing M2TS
- [12:14:11] Extracting A/V streams [VID_00104]
- [12:14:16] Reencoding: VID_00104 (4 of 14)
- [12:14:16] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 1,012 frames
- [12:14:16] Reencoding: VID_00104, Pass 1 of 1
- [12:14:31] Video Encode complete
- [12:14:31] Reencoding audio tracks (if req'd)
- [12:14:31] Multiplexing M2TS
- [12:14:32] Extracting A/V streams [VID_00107]
- [12:14:40] Reencoding: VID_00107 (5 of 14)
- [12:14:40] Collecting video information
- Source Video: MPEG-2, 720x480
- Rate/Length: 29.970fps, 6,040 frames
- [12:14:40] Reencoding: VID_00107, Pass 1 of 1
- [12:15:01] Video Encode complete
- [12:15:01] Reencoding audio tracks (if req'd)
- [12:15:01] Multiplexing M2TS
- [12:15:03] Extracting A/V streams [VID_00108]
- [12:15:10] Reencoding: VID_00108 (6 of 14)
- [12:15:10] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 1,451 frames
- [12:15:10] Reencoding: VID_00108, Pass 1 of 1
- [12:15:30] Video Encode complete
- [12:15:30] Reencoding audio tracks (if req'd)
- [12:15:30] Multiplexing M2TS
- [12:15:31] Extracting A/V streams [VID_00022]
- [12:15:38] Reencoding: VID_00022 (7 of 14)
- [12:15:38] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 1,555 frames
- [12:15:38] Reencoding: VID_00022, Pass 1 of 1
- [12:16:01] Video Encode complete
- [12:16:01] Reencoding audio tracks (if req'd)
- [12:16:01] Multiplexing M2TS
- [12:16:03] Extracting A/V streams [VID_00109]
- [12:16:14] Reencoding: VID_00109 (8 of 14)
- [12:16:14] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 3,151 frames
- [12:16:14] Reencoding: VID_00109, Pass 1 of 1
- [12:16:55] Video Encode complete
- [12:16:55] Reencoding audio tracks (if req'd)
- [12:16:55] Multiplexing M2TS
- [12:16:57] Extracting A/V streams [VID_00113]
- [12:17:10] Reencoding: VID_00113 (9 of 14)
- [12:17:10] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 3,797 frames
- [12:17:10] Reencoding: VID_00113, Pass 1 of 1
- [12:18:05] Video Encode complete
- [12:18:05] Reencoding audio tracks (if req'd)
- [12:18:05] Multiplexing M2TS
- [12:18:08] Extracting A/V streams [VID_00110]
- [12:18:21] Reencoding: VID_00110 (10 of 14)
- [12:18:21] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 3,771 frames
- [12:18:21] Reencoding: VID_00110, Pass 1 of 1
- [12:19:14] Video Encode complete
- [12:19:14] Reencoding audio tracks (if req'd)
- [12:19:14] Multiplexing M2TS
- [12:19:17] Extracting A/V streams [VID_00111]
- [12:19:33] Reencoding: VID_00111 (11 of 14)
- [12:19:33] Collecting video information
- Source Video: MPEG-2, 1920x1080
- Rate/Length: 23.976fps, 4,559 frames
- [12:19:33] Reencoding: VID_00111, Pass 1 of 1
- [12:20:53] Video Encode complete
- [12:20:53] Reencoding audio tracks (if req'd)
- [12:20:53] Multiplexing M2TS
- [12:20:57] Extracting A/V streams [VID_00105]
- [12:21:28] Reencoding: VID_00105 (12 of 14)
- [12:21:28] Reencoding secondary video [TRK_02]
- [12:21:38] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 5,712 frames
- [12:21:38] Reencoding: VID_00105, Pass 1 of 1
- [12:23:52] Video Encode complete
- [12:23:52] Reencoding audio tracks (if req'd)
- [12:23:52] Multiplexing M2TS
- [12:24:03] Extracting A/V streams [VID_00106]
- [12:25:38] Reencoding: VID_00106 (13 of 14)
- [12:25:38] Collecting video information
- Source Video: MPEG-2, 720x480
- Rate/Length: 29.970fps, 66,135 frames
- [12:25:39] Reencoding: VID_00106, Pass 1 of 1
- [12:29:14] Video Encode complete
- [12:29:14] Reencoding audio tracks (if req'd)
- [12:29:14] Multiplexing M2TS
- [12:29:27] Extracting A/V streams [VID_00011]
- [12:45:31] Reencoding: VID_00011 (14 of 14)
- [12:45:31] Reencoding secondary video [TRK_02]
- [12:51:52] Collecting video information
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 127,656 frames
- Bitrate: 23,952 Kbs
- [12:51:52] Reencoding: VID_00011, Pass 1 of 2
- [14:04:07] Reencoding: VID_00011, Pass 2 of 2
- [18:30:54] Video Encode complete
- [18:30:54] Reencoding audio tracks (if req'd)
- [18:30:54] Multiplexing M2TS
[18:43:43]PHASE ONE complete
[18:43:43]PHASE TWO - Rebuild Started
- [18:43:43] Rebuilding BD file Structure
[18:44:07] - Encode and Rebuild complete
[18:44:07] Writing BD structure to ISO file
- ImgBurn completed successfully
- WORKFILES folder removed.
[18:48:43]JOB: STAND_BY_ME finished.

[A.Fenderson]

That would be virtually impossible. A frame-by-frame examination would take as long as an encode. Interesting, though, that in a couple thousand encodes I've never seen it. I guess I've been lucky with my drives.

Yeah, I didn't think it would be feasible, but thought I'd ask. I generally rip with my LiteOn (which was the cheapest BD-ROM drive I could get at the time I bought it), to save wear and tear on my nice Pioneer BD writer--I've had 2 bad rips with the LiteOn using AnyDVD-HD (always up-to-date), but reripping with the Pioneer, so far, hasn't given any issues. I hate to add the extra wear to my Pioneer, but I may have to start ripping with it to avoid these random and virtually undetectable bad rips.

[omegaman7]

Yeah, I didn't think it would be feasible, but thought I'd ask. I generally rip with my LiteOn (which was the cheapest BD-ROM drive I could get at the time I bought it), to save wear and tear on my nice Pioneer BD writer--I've had 2 bad rips with the LiteOn using AnyDVD-HD (always up-to-date), but reripping with the Pioneer, so far, hasn't given any issues. I hate to add the extra wear to my Pioneer, but I may have to start ripping with it to avoid these random and virtually undetectable bad rips.

I hear you. I really do LOL! My lite-on is guilty of a few bad rips. My LG hasn't done it yet. I don't expect it to for a while yet either. *touch wood*

[steveg32]

I was just reviewing the two INF files and noticed that they aren't matching. Did you choose an alternate playlist when you did Jackass?

@ jdobbs

Yes, I chose the Theatrical version:
Playlist 00001 -- Playlength: 01:34:00 - [048 Chapters].

And the Director's Cut version:
Playlist 00007 -- Playlength: 01:39:44 - [049 Chapters].

Both had the same sync issues.