To be fair, the only Kubrick on DVD that is master supervised are the original R1 box set LD ports (complete with original mixes), and the R2 EWS Snapcase open matte uncensored. The rest are just revisions on a master work.

@Moshrom Yeah, it's the pre-SE MGM R1 DVD, the one with the very wide AR (2.69:1 according to dvdcompare.net). It sounds all right, from what I remember, but it's been a while since I listened to it. I'll fish it out at the weekend.

According to DVDbeaver, the 2.69 AR was meant for director John Sturges to mess around with to frame a 2.35 image in post.

What is wrong with Criterion's Barry Lyndon mono audio? I was thinking of buying that...

The 2.69 AR was awesome, it gave an epic feel to the film!

^^^ Regarding the 2.69:1, I know the story behind it, but it still looks awesome, and I value the old R1 DVD for it.

@titanic Read the comments on Moshrom's blog. It's the best that's available. I bought the Criterion BD partly because of it. It's just that it should sound better. https://blah-ray.blogspot.com/search/lab...%281975%29

Even Criterion isn't perfect.

@Chewtobacca Thanks.

Criterion post LD have never been perfect

Was DTS-ES a Theatrical sound format like Dolby Digital EX was? Or was it home video only?

DTS-ES was theatrical but matrixed the same as Dolby EX

ES was and still is on home releases

Hi, I have a CD DTS theater which is in DTS-ES : Corpse Bride in French. ES was therefore for home video, and theaters.

I have a question: What should I update on EAC3to so that it correctly detects the bit depth (on AC3 and DTS)? Libav?

There's nothing to update: lossy tracks don't have bit-depth. because they are encoded in the frequency domain. This is why eac3to decodes them to 24bit. You might have better luck with technical questions if you post a thread, rather than using the shoutbox.

Thank you, but I just read a recent thread (here or on videohelp, or OT, I don't remember) where the person advised to update (libav I think) so that EAC3to decodes in 24 bits only if necessary, because it tends to decode in 24 bits even when it is not necessary.

I'm desperately looking for this thread, it was a recent discussion, on videohelp, doom9, OT, fanres, I forgot ...

This message that I read questioned all of my beliefs about EAC3to I also thought that we should always decode lossy formats in 24 bits, but maybe the person was wrong, and that libav / FFmpeg is already updated on EAC3to

I'd like to read that thread. There was even an attempt made to get the dev of MediaInfo to remove that field from its output (for lossy tracks) to stop people asking about it over and over again.