Chewtobacca

hairy_hen said:Speaking of the '93 versions, there is no real reason to avoid them, because unlike the first movie there aren't any sound effects additions.  ESB is missing the snowspeeder crash sound for some reason...

In that case, it would be good to have 2.0 PCM of the '93 mix with the sound of the snowspeeder crash restored.

Teeceezy, if you have GOUT-synced PCM of the ESB 80 stereo, I would appreciate a PM.

What's the restoration program?  I don't know what it is, despite being given the ending.

Great to see you back again, Possessed!  I look forward to seeing what you come up with.  :)

The size of the MKV is 19,213,754,660 B.

That's the size of my MKV, which came from myspleen.

Kk650, you might find NeverarGreat's thread interesting.  What program are you using, by the way?

I think he's more concerned that he's been providing people with the unfixed version.

Nearsighted Scrappile, the myspleen version is fine, and there are no duplicates.  There were checksums posted a few pages back.

msycamore said:Yeah, I'm sorry to say it but I ran out of steam, with a better capture...

That's understandable, given how busy you've been with THX-1138.

msycamore said:I only made a recalibrated and aspect ratio corrected version.

I'm sure it will look absolutely fine.  Your first version was very good, so any improvement will be welcome. :)

The password is usually Harmy, so try that.

kk650 said:technically no audio quality loss should have occured along the way from either of the two sources to the final output mix, apart from the downmixing of the dolby digital 5.1 audio of course.

That's true, but it would, of course, be better to use a lossless source.  I can help you out with a downmix of the BD audio at some point if you're interested.

Sorry.  I misread (actually misquoted) your last statement.  The answer should have been yes. (I meant the "no" to apply to the part about the frame-rate's still being 47.952.)

jdryyz said:

It's normal with VLC playing back a Blu-Ray?? 

Yes.

jdryyz said:

Also, will my actual Blu-Ray player (set top box) still report the 23.9/24 Hz playback with the disc I create?

Yes.

kk650 said:  Audio Track: Uncompressed PCM track based of Belbucus's 1993 PCM audio mix

Is your PCM a combination of Belbucus' PCM and a downmix of the DTS-HD MA from the BD?

jdryyz said:Somehow my frame rate changed from 23.9x to something like 47.9x.

That's normal when VLC plays 23.976fps content.  The frame-rate of the file itself has not really been changed.

hairy_hen said:I'm able to encode TrueHD, but for whatever reason this format isn't commonly used and may cause compatibility problems of its own.

Wow!  I didn't realize that you had Dolby Media Encoder.  That must have set you back a bit.

Dolby TrueHD is only optional for BD, so this is the probable explanation for the compatibility problems – not that I've ever experienced any.  While it's not used as much as DTS-HD MA these days, it's common enough on BDs.

dark_jedi said:I think a few of us in this thread have learned some very important things about our fellow members.

I think most of already know what we need to know about our fellow members.

This is indeed good news.  I had thought the second version abandoned.

TV's Frink said:There's a million better ways to show enthusiasm than "don't die before you're done."

I agree, Frink, and I would have no more written that than you would have; but I understood what he must have meant straight away and took it in exactly the same way that Bester did.

Dolby Digital is lossy.  Dolby TrueHD is lossless, but there is no free encoder available, and the commercial ones are very expensive.   Price rather than difficulty would be the stumbling block.

You should decode your HDTV cap and use AviSynth to change the frame-rate.  Then render a lossless intermediate, apply your color grading, and re-encode.

While the JSC does not have a shrinking ratio, the height of the active image area does vary considerably, sometimes from shot to shot.  I noticed that when looking at Arnie.d's capture.

NeonBible said:But is there an exact science to getting the right sync?

If you don't have a track to use as a guide, you'll have to make your best guess or wait for DoomBot to make changes if it is indeed out of sync.  (I'm not the best person to ask because I sync using the method that zeropc explained above.)  250ms is between five and six frames, which is usually quite noticeable.

Converting w64 to wav is easy.

eac3to input.w64 output.wav

Other people upload as flac, which requires a similar, one-step conversion before you can author a disc.  I think what DoomBot did was fine.

EDIT:  NeonBible, if you're worried about the delay, you can use Eac3to to add that too.

I have made progress of sorts in that I have rendered very short clips successfully.  This demonstrates that there is nothing inherently wrong with my source files or script.  Unfortunately, the clips have to be very short – around four thousand frames – and the length after which livelock occurs does not seem to be predictable, so I cannot simply break the film into manageable chunks.

Would someone be kind enough to try to render a film of any length using ColourLikeFBF() and report any problems?

hairy_hen said:By the way, the DTS is not an encode of the same mono mix file that's been out there for the past few years.

Thanks for confirming that.