Quote:
|
Some software sees the "internally 29.97" and is "NTSC stupid", meaning it only shows 29.97 for anything NTSC --- even when it's 23.976, which is valid NTSC, too.
|
If Architect forces a re-encode under 23.976, won't it affect the video quality? Or are you saying, since it's valid NTSC, it's within range and won't be noticable? I always thought it had to be perfect all the way through.
Quote:
|
Did anything re-encode between the 23.976 source and the supposed 29.97 files? I haven't used DGIndex in probably 5-6 now, no need for it (not for me, anyway).
|
Nothing does or wants to re-encode at any stage until Architect. I really only use DGIndex to quickly ID VOBs and check parameters. Which is why this progressive/interlaced thing is so weird. Do you think it's anything to worry about?
Quote:
|
What does Gspot think? What about Restream?
|
You got me
Quote:
|
I hate learning new methods too --- but I think your older method is actually more complex. Redoing the audio repair work would not be fun. (Did you take notes? I started doing that, for such very reasons! Yuck.)
|
Well, I haven't really taken written notes. But I've learned what sounds good and what doesn't, and recently solved a very irritating noise problem with some good sound proofing in my workstation. So I'm very happy about that!
This method might be more complex (it's certainly more time consuming), but nothing else satisfies my sensitive ears. Muxing/demuxing always appears to result in audio loss
