team negative1 - star wars 1977 - 35mm theatrical version (Released) — Page 155

SnooPac said:

Sorry don’t have time to read all these messages (will eventually) but I’ll try to quickly answer a few.

Chewtobacca said:

This happens every time someone extracts the ISO. Why extract it? Why do anything to it?

By “extracted”, its meant extracted from rar to iso. Iso not modified (intentionally).
And this is a rule on myspleen that the rars need to be extracted.

dahmage said:

Well, SnooPac do you mind if i replace your upload with the fixed file or do you want to fix it? good news is it should only require minor download to sync the changes.

Go ahead. I think it will just be 1 or 2 torrent segments that are bad. Would be nice if you have the ability to diff. I’m curious if its just a few bytes that are bad or something more significant. Even if its just 1%, 1% of that many GB could still be a lot. Probably best to keep file name the same so torrent clients just auto “overwrite” my file and complete the few missing bad bytes? Can also delete the first torrent.

Also I would have tried to confirm the hash after extracting, but I couldn’t find it. Sorry all, my bad.

Yeah, as a community we need to get in a better habit of sharing hashes/checksums for everything…

I will create a new torrent, keeping the exact same directory and file structure that you had. I will try to make it clear (at least for the time-being) that this is a updated/fixed torrent, and if you just point it at your existing download it will only need to change one piece (2mb). I will let you know when it is ready to go.

I did a binary diff: but i am not exactly sure what it means. Anyone who knows the UDF 2.5 spec better than me might be able to decipher it.

dahmage said:

Yep, the myspeen torrent probably modified your file.

Here is difference i have found so far:

a.b.starwars blocks 20004-20078:
CA 00 01 00 D2 2D 7E 00 40 00 00 00 10 1F E0 07 06 0C 0E 29 29 3C 50 00 01 00 00 00 00 00 00 00 00 00 00 00 7E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 2E 00 00 00 00 00 00 00 00 00 00 00 C0 51 2C 01 A0 00 00 00 00 2A 49 6D 67 42 75 72 6E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Ê…Ò-~.@…à…))<P…~…ÀQ,. …*ImgBurn…

myspleen blocks 20004-20078:
53 00 01 00 D0 B8 7E 00 40 00 00 00 10 1F E0 07 06 0D 09 32 06 07 4B 21 01 00 00 00 00 00 00 00 00 00 00 00 7E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 2E 00 00 00 00 00 00 00 00 00 00 00 C0 51 2C 01 A0 00 00 00 00 2A 49 6D 67 42 75 72 6E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 04

S…и~.@…à…2…K!..~…ÀQ,. …*ImgBurn…

^ Yep.

SnooPac said:

dahmage said:

Well, SnooPac do you mind if i replace your upload with the fixed file or do you want to fix it? good news is it should only require minor download to sync the changes.

Go ahead. I think it will just be 1 or 2 torrent segments that are bad. Would be nice if you have the ability to diff. I’m curious if its just a few bytes that are bad or something more significant. Even if its just 1%, 1% of that many GB could still be a lot. Probably best to keep file name the same so torrent clients just auto “overwrite” my file and complete the few missing bad bytes? Can also delete the first torrent.

Actually, why don’t you just edit your local file using a hex editor. See my previous post for the bytes to change. It is really very minor. Save it and run some checksums, it should match what Williarob posted at that point. THen you can re-upload the torrent. I think it will just be too confusing if i upload a new one, might be less so if you do?

I’m sure Team Blu will probably have the 5.1 in their version, as their goal (to my understanding) is more about having the best presentation of the original version on blu ray, rather than trying to accurately present exactly what was seen and heard on 35mm film in theaters.

towne32 said:

… Maybe people who have each version should compare checksums of the rars themselves.

The rar’s were fine I think. Pretty sure it came with an .sfv file and I checked it with that. So whatever the problem was must have come during (or after) extracting the iso from the rars.

pittrek said:

…
Jedit : Wait a moment, I have now realized I am helping seeding the myspleen torrent. I have a bad feeling that uTorrent has rewritten some of the bytes of the ISO to “comply” with the ISO shared on myspleen 😦

Sorry 😦

dahmage said:

Yep, the myspeen torrent probably modified your file.

Here is difference i have found so far:

a.b.starwars blocks 20004-20078:
CA 00 01 00 D2 2D 7E 00 40 00 00 00 10 1F E0 07 06 0C 0E 29 29 3C 50 00 01 00 00 00 00 00 00 00 00 00 00 00 7E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 2E 00 00 00 00 00 00 00 00 00 00 00 C0 51 2C 01 A0 00 00 00 00 2A 49 6D 67 42 75 72 6E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

Ê…Ò-~.@…à…))<P…~…ÀQ,. …*ImgBurn…

myspleen blocks 20004-20078:
53 00 01 00 D0 B8 7E 00 40 00 00 00 10 1F E0 07 06 0D 09 32 06 07 4B 21 01 00 00 00 00 00 00 00 00 00 00 00 7E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 02 00 00 00 2E 00 00 00 00 00 00 00 00 00 00 00 C0 51 2C 01 A0 00 00 00 00 2A 49 6D 67 42 75 72 6E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 04

S…и~.@…à…2…K!..~…ÀQ,. …*ImgBurn…

Man that’s annoying. Looks like by my quick count (I bolded diffs), there are just 11 bytes different. 11 bytes! That’s 2.7289303176173536412470897337513 x 10^-8% of the file corrupt. 0.0000000272893%! 😦

Chewtobacca said:

SnooPac said:
By “extracted”, its meant extracted from rar to iso. Iso not modified (intentionally).

Got it!

And this is a rule on myspleen that the rars need to be extracted.

Of course! That was never the issue.

Ok, glad we cleared that much up at least 😃.

dahmage said:

…
After looking at the binary diff, all the changes seem to be in the file header, it looks like the author or maybe an authoring date got changed? but How?

That’s the million dollar question. I’m guessing its something in my setup. Bad corrupt disk on my server? Buggy version of unrar? I can’t really explain it yet, but that sucks.

dahmage said:

…
Actually, why don’t you just edit your local file using a hex editor. See my previous post for the bytes to change. It is really very minor. Save it and run some checksums, it should match what Williarob posted at that point. THen you can re-upload the torrent. I think it will just be too confusing if i upload a new one, might be less so if you do?

Oh man. OK I can try. But I don’t know if I’ll be able to do it right. Can you please make your .torrent ready just in case I can’t get it right?
Alternatively you could…wait, I’ll take this to PM.

Darth Lucas said:

I’m sure Team Blu will probably have the 5.1 in their version, as their goal (to my understanding) is more about having the best presentation of the original version on blu ray, rather than trying to accurately present exactly what was seen and heard on 35mm film in theaters.

We will do the Original Trilogy up the absolute best we can with all the best resources available, we have assembled the best Team for this so stay tuned! we are just trying to clear our plates and I am going to need to do what Harmy did a while back, I need a PC rebuild very soon for all this stuff we have in store, so hopefully when ready I can get the same support Harmy did, he and I will spread the word when ready.

Exciting times are coming!

So, just to clarify, does the MKV version that’s up on the Spleen have a video glitch? I downloaded it, but haven’t had a chance to watch it yet. Hope I didn’t just waste a 30gb download. 😦

NP. dahmage did the work to fix. I just put it up there…

Haha nice observation Faithwyn.

FYI, it looks like we found out what caused those corrupt bytes (thanks again dahmage who actually seemed to find out what happened).
I haven’t tried to reproduce (I will soon), but pretty sure this is it.

I figured, after I got the RARs and extracted the ISO from them, the best way I could check the ISO was good was to mount it and browse the folders, check for BVMD and STREAM and all the m2ts files etc…
So I did a quick google search on how to mount ISO’s on Linux, and eventually I do the command:
mount -o loop Star_Wars_SSE_TN1_v1_6.iso …/tmp/iso
I go over to …/tmp/iso/, look around, all looks good, so I unmount and continue on.

Well, apparently the stupid mount edits the ISO file for some reason:
http://unix.stackexchange.com/questions/149459/mount-o-loop-changes-mounted-iso-image-file
If I had just run the command with a “ro,” in there before the “loop”, all would have been fine.

So if I didn’t try to verify that all was good, then all would have been good 😃.
Oh well. You live and learn I guess.

User. Error.

SnooPac said:

So if I didn’t try to verify that all was good, then all would have been good 😃.

Irony.

I fixed the issue with the stars on the 81 crawl, but as I was fixing it I noticed two more small issues. I have some appointments I need to get to today, but when I get back I’ll fix those issues and should get the file to Williarob later today

Can’t speak for Rob of course, but I would say not to worry about rushing it. If there are more errors to be spotted, then hopefully we can catch them.

Are you going to try to do anything about the static grain on Tatooine? I think it looks a lot better than some of the very early attempts, but I think a few people did notice it even in the last release. Anyway, the only problem that I thought was pretty big last time was the reappearing Star Wars logo. Presumably happened in the process of looping the starfield?

towne32 said:

Can’t speak for Rob of course, but I would say not to worry about rushing it. If there are more errors to be spotted, then hopefully we can catch them.

Are you going to try to do anything about the static grain on Tatooine? I think it looks a lot better than some of the very early attempts, but I think a few people did notice it even in the last release. Anyway, the only problem that I thought was pretty big last time was the reappearing Star Wars logo. Presumably happened in the process of looping the starfield?

Unfortunately I can’t think of much more that I can do. i added more grain on top of it, but it still only makes it less noticeable. The static grain is still there under it.

I’m not sure what you mean by the re-appearing Star Wars logo. I’ve looked through it and the logo fades out and then I can’t see any trace of it after that. What exactly are you referring to? Maybe it was an issue with the encoding?

RU.08 said:

SnooPac said:

Well, apparently the stupid mount edits the ISO file for some reason:
http://unix.stackexchange.com/questions/149459/mount-o-loop-changes-mounted-iso-image-file
If I had just run the command with a “ro,” in there before the “loop”, all would have been fine.

If that’s the case then the ISO definitely wasn’t corrupted - it’s just a slight different .iso file with all the same contents. So it did not cause the glitches Blackout had.

Ya I doubt very much that it would have caused any difference, but who knows. And in any case, its best that it was fixed and that there’s a consistent version out there.

clutchins said:

Welp, it’s down.

What is?
edit: if you are talking about the original torrent, yes it was taken down and there’s a new one instead that has the fully correct file (you don’t need to redownload the whole thing, just like <1%).

Stinky-Dinkins said:

Darth Lucas said:

I need a PC rebuild very soon for all this stuff we have in store, so hopefully when ready I can get the same support Harmy did.

I’m in, for absolute friggin’ sure.

No I didn’t say that.