
- Time
- (Edited)
- Post link
.
.
What an awesome first post.
“It’s a lot of fun… it’s a lot of fun to watch Star Wars.” – Bill Moyers
What an awesome first post.
It’s edited. Was probably Markdown syndrome/syntax.
Here I was like a shnook expecting the string of thread subscription notifications I just got would signify an actual update.
Might as well be cause for asking for an update, though… Hey, Harmy, any update?
I did make some progress in the last couple of weeks but there’s still a lot to do.
A note to anyone intending to D/L the 19.7Gb MKV of 2.0 from a.b.test (posted almost a year ago):
I’ve downloaded this - a couple of times - and according to the PAR, all files check, no errors. However, when extracted, video freezes at 00:01:52. Tried running it through MeGUI, MKVMerge, and Meteorite to no avail. Clearly, the file was bad BEFORE it was RARed, so unfortunately, this D/L was a bust.
I got the 720p AVCHD of 1.0 (from a.b.starwars) as a “consolation prize”; that checked out okay and seems to play well.
Just a heads-up to anyone intending to D/L from Usenet…
That’s approximately the size of Harmy’s original file. Does the checksum match? I know people have remuxed his ESB 2.0 to fix the fact that it was a frame or so off sync, so that’s another reason the checksum might not match…
@towne: Check your PMs
😃
You probably don’t recognize me because of the red arm.
Episode 9 Rewrite, The Starlight Project (Released!) and ANH Technicolor Project (Released!)
Hi slark,
Have you had any trouble with the official links of the ESB 2.0 MKV or AVCHD as posted on tehparadox?
The NJVC Custom Bluray Set of Harmy’s Despecialized Editions is available on Mega.
Go to this thread
Hi slark,
Have you had any trouble with the official links of the ESB 2.0 MKV or AVCHD as posted on tehparadox?
Well, as I often the case, I posted just a little too soon!
Looks like third time was the charm.
I extracted from the RAR files (again, downloaded from Usenet, and yes, it passed CRC) but this time I immediately ran it through tsMuxer TWICE: first to change it to another format (M2TS), THEN to Blu-ray. THIS time it worked just fine.
Odd that the first two times I extracted it - to different drives - it yielded a conversion error in EXACTLY the same place (at 1 minute 52 seconds into the film).
I’ve had this experience before - where tsMuxer encounters an error in an MKV - but often, if you convert to an interim format, you can “filter out” the error.
Thanks for the responses, BTW!
That’s approximately the size of Harmy’s original file. Does the checksum match? I know people have remuxed his ESB 2.0 to fix the fact that it was a frame or so off sync, so that’s another reason the checksum might not match…
ESB DE is off sync?? I’ve never noticed. Where is the error?
Somewhere early. It’s only off by a frame, so it makes sense that you would have not noticed it. It can be remuxed with a sync offset to fix.
That’s it, I’m throwing my entire set in the trash.
That’s it, I’m throwing my entire set in the trash.
what about your dad’s set?
That’s it, I’m throwing my entire set in the trash.
what about your dad’s set?
Now there are two of them.
That’s it, I’m throwing my entire set in the trash.
what about your dad’s set?
Harmy promised to come over and throw out his set.
That’s it, I’m throwing my entire set in the trash.
Yeah, of all the nerve to call that an OUT.
I would put this in my sig if I weren’t so lazy.
My dads birthday is in a week. Can Harmy come throw away his set before then?
Somewhere early. It’s only off by a frame, so it makes sense that you would have not noticed it. It can be remuxed with a sync offset to fix.
Any instructions on how to do so? I mean obviously it’s so small that I never noticed it before and probably never could, but simply knowing it’s there now is going to bother my mildly OCD brain regardless.
Somewhere early. It’s only off by a frame, so it makes sense that you would have not noticed it. It can be remuxed with a sync offset to fix.
Any instructions on how to do so? I mean obviously it’s so small that I never noticed it before and probably never could, but simply knowing it’s there now is going to bother my mildly OCD brain regardless.
http://originaltrilogy.com/post/id/725222
For ESB, just add 42ms delay in Mkvmerge for all audio tracks.
Somewhere early. It’s only off by a frame, so it makes sense that you would have not noticed it. It can be remuxed with a sync offset to fix.
Actually the frame difference between PAL and NTSC GOUT is at around 1:44:24, so the reason nobody notices it is that it’s a one-frame difference, it affects only a small section of the film, and that section has very little dialogue (which is the easiest way to spot small sync problems). Muxing the audio one frame off would actually make sync worse for most of the film, and you’d be more likely to notice it.
Somewhere early. It’s only off by a frame, so it makes sense that you would have not noticed it. It can be remuxed with a sync offset to fix.
Actually the frame difference between PAL and NTSC GOUT is at around 1:44:24, so the reason nobody notices it is that it’s a one-frame difference, it affects only a small section of the film, and that section has very little dialogue (which is the easiest way to spot small sync problems). Muxing the audio one frame off would actually make sync worse for most of the film, and you’d be more likely to notice it.
Are you discussing SW or ESB? I was referring to ESB, and the time stamp you’ve stated sounds more like the SW imperfection as of 2.5 (fixed in 2.7), but I don’t recall the exact point off the top of my head.
My understanding (and seemingly everyone else’s at the time) was that ESB was off by a frame very early on.
I believe Darth Mallwalker said that one extra frame was somehow added to ESB 2.0, making all audio tracks play one frame too early. It’s not easy to notice this while watching…
The 2-frame difference at a reel change during the Luke and Vader duel was a discrepancy between the PAL and NTSC versions of the GOUT. ESB 2.0 deleted these two frames from the video in order to match the NTSC audio tracks, so there shouldn’t be any additional mismatch there.
Honestly since I can’t notice it and there seems to be a dispute as to the nature or even existence of it, I’m not gonna worry about it. Any changes I make might just mess it up more so I’ll leave it as it is. If there is a problem I’m sure it will be corrected in 2.5.