That’s always great to hear! Keep in mind that my Vietnamese subs are based on those fansubs you found (just re-timed), so I can’t speak for the quality of the translation. If you see any room for improvement, feel free to drop me a line!
FWIW there were never any official MP4 encodes, but there are re-encodes made by random internet people all over the place, mostly because people really were put off by the file sizes of the official downloads. i.e. if you’re going into this from a film preservation/I want something with better quality than the official releases that I can keep forever, big file sizes aren’t a concern. But if all you want to do it watch a movie once on your phone and be done with it, well, something smaller is probably good enough. Different strokes and all that.
But those MP4s you found might not be a “matched set”, they may be re-encodes made by three entirely different people using entirely different quality/speed trade-offs, they may have made different and possibly bad audio choices, etc. Heck, someone could have spliced Jedi Rocks back into ROTJ for all we know, people do all sorts of weird things. That’s the downside of unofficial sources.
I can verify, the Japanese dub in my collection is the “home video” dub, taken straight from the GOUT – this is just mislabeled here. Harmy uses my collection for a lot of his dubs, but he may be open to supplementing from other sources.
I generally don’t include more than one dub per language in my own collection, for space reasons. I opted for the home video dub because it’s a trilogy-complete, voice-matched set.
PM sent.
Keep in mind, Despecialized ROTJ 3.0 has a bug where one of Jabba’s subtitles is missing. If you’re using Project Threepio’s “native” English subtitles, this presents a problem, as they do not subtitle things that are already supposed to have onscreen subtitles. This is not a problem for “full” subtitles, which subtitle everything.
You may want to contact the Krieg der Sterne team. It’s the most active of these projects, and they may have some subtitle-free video that you can use for your version, plus perhaps their method of creating the German crawl could maybe be re-used for Spanish.
Good luck!
Hi
Yeah, maybe they can share with me their method of making their German version. I tried my best to replicate the original Spanish titles searching the fonts used in this forum. I applied some film grain and image gentle unfocus to obtain that 70s movie feel.
https://drive.google.com/file/d/15cX5UoSc_ATx_ZTAqqMBfIcAsUCOv33E/view?usp=sharing
https://drive.google.com/file/d/1U0TtppIsxkdIiUsiqz-GRjXFScj2RZNN/view?usp=sharing
I’am using 4K77 v.1.0 with Dr. Dre color correction as a source for this recreation. Don’t misunderstand me, I love and appreciate the Harmy’s Despecialized Edition, but i personally enjoy more the feel and looks of the 4K77.
This is my recreation of the prologue, using the 4K77 background and resolution.
https://drive.google.com/file/d/1YMR2fKh2m1IcHR5lCqvIYF90-ITOpItV/view?usp=sharingFunnily, where i’am having more difficulties it’s the LA GUERRA DE LAS GALAXIAS title. I tried to made the title manually using some Star Wars fonts, but it doesn’t look plausible for a 1977 film. I think i’m going to ask to Laserschwert, main responsible of the Krieg Der Sterne (German Star Wars) trilogy if he can help me in this part.
Also, i don’t have any trust information about the Spanish Greedo subtitles used theatrically since the 1984 CBS FOX/1991 Planeta DeAgostini VHS release subtitles were digitally added. I don’t have the 1993 THX Laserdisc master, but they didn’t used the Spanish version of the film. I revised my Spanish 1997 Special Edition VHS tape release and nothing…
I hope if there is some user in this forum from Spain or Latin America Spanish-speaking countries who did watch the movie in theaters in 1977 or a 80s re-release of the film and they can read this thread…
From what I can tell from the other European film sources we have, the subtitle fonts used in ROTJ were largely standardized and more-or-less the same as the English theatrical font, but the Star Wars subtitle font varied wildly – not the same for two countries so far. Also, the actual text of the subtitles frequently changed between the theatrical run and the first home video release (the theatrical translation was rushed and often less than ideal). That’s all I have, sorry!
PM sent.
You may want to contact the Krieg der Sterne team. It’s the most active of these projects, and they may have some subtitle-free video that you can use for your version, plus perhaps their method of creating the German crawl could maybe be re-used for Spanish.
Good luck!
Sorry, I’m a disc person who’s just recently branched out to MKV. MP4 is one step beyond for me, but I’ll gladly open up the discussion to anyone who does know.
“Romani ite domum”
Hahaha
Great choice for a name.
Did you have to write it a hundred times too?I must have seen this movie at least a hundred times. Almost as many times that I have seen Star Wars.
Many of my codenames are plays on words, plays on numbers, references to pop culture and current events, or all three. And I’m a big Python fan. When I’m secretly worried that my machine translation is going to come up with bad translations, that anxiety comes out in the codename 😉
Speaking of which, version 14.0 was a bit rushed, to make it out in time for Despecialized ROTJ 3.0. I had plans for a lot more machine-translated languages, but those had to be deferred, and will show up in a future release.
The bigger news is that while I was initially conservative with machine translation, I am at least initially getting good results with languages that I considered longshots. Specifically, Georgian. Georgian isn’t really even somewhat related to any other major language, so I picked Russian as the starting language – simply because some Russian colloquialisms and other terms may have worked their way into the language, and “problematic machine translations from Russian” may be the sort of strangeness that Georgian speakers may already know how to accommodate.
How do I measure if the translation is any good? Well, if the translation round-trips from Russian to Georgian, and then back again to English, and it’s still intelligible, I figure it’s probably okay. In this case, it’s not just intelligible, but usually pretty solid (and sometimes merely intelligible too). So assuming this keeps up, I may be able to add some very interesting languages.
Sadly, it appears that it may be more the quality of the machine translator for that particular language than any proximity to an existing translation, so I just won’t know until I try, and I may not be able to predict which languages will work. For example, Faroese is very close to Icelandic, and that attempt failed badly in the early stages.
PM’s sent.
PM sent.
More possible fixes:
I’m still noticing a grading shift mid-wipe at 1:21:38, but I’m not sure if it’s theatrical or not.
Okay, I know the Boba Fett flyby is supposed to look janky when you watch it frame-by-frame, but could you check against 4K83 to see if it looks different there? Something about the current flyby looks like very low res video scaled way too large, and I recall this was your only GOUT-sourced despecialization in 2.5.
On the bug report front –
The 1080p encode seems to be missing a framerate in the H264 file. This works fine in the MKV, but if you try to demux/remux, you may have to manually set the framerate or you could get issues.
The 2160p encode has no black bars – not a problem for most people, but it does cause problems when using PGS subtitles. PGS subtitles generally need a 16x9 frame or weird and bad stuff can happen during playback.
issue
please help!!!
Google restricts the volume of downloads, so we’re a little stuck, at least until someone who’s downloaded it makes it available via torrent, etc. So please share everyone!
Project files have been updated to version 14.0 (codename: “Romani ite domum”), and the first post has been updated. Please PM me for temporary download links until the files are available at some more permanent locations.
Rough summary of changes from 13.0 to 14.0:
PM sent.
PM sent.
PM sent.
PM sent.
PM sent.
PM sent.
PM sent.
Wow Harmy, thanks for the update! I’d been pessimistic that Darth Real Life* had claimed another victim.
* Shamelessly stolen from hairy_hen.
Well, that appears to have been much ado about nothing. The text weight is great, but the kerning isn’t. I’d rather have slightly-too-light fonts than bad kerning 😕
It’s been a while since I’ve posted one of my technical progress reports, so here goes.
This project has been through a few text renderers in its day. First, we had an entirely manual Windows-only renderer (easySUP), then a scriptable and mostly-but-not-quite cross-platform one (Pango). Currently, the project is using Chrome – or to be more accurate, Chromium, the open-source project behind Chrome and other Chrome-like web browsers. This has solved a lot of problems. It’s scriptable, it’s truly cross-platform, and it easily deals with the complicated technical requirements behind rendering some of our non-Latin scripts.
But there’s always something, and I’ll just come out and say it. I hate the way Chrome renders text on Windows. Firefox does way better at this. I hated Chrome’s text rendering even as I moved the project to Chrome, hoping it would someday get better. There are lots of bugs filed on this, all lumped under a single uber-bug here. The gist is this: Chrome’s text is too light, too thin, too spindly. Bold text looks more like semibold, semibold looks more like medium, medium looks more like regular, and so on. That doesn’t mean that text is bad or unreadable or even unpleasant (some people prefer it this way, and that’s okay), but it does mean that the appearance of the text differs from the intent of the person who chose that font and weight. And for subtitles, that’s important.
With subtitles, you want your text a little on the thick side, so they don’t get lost against a busy, moving background. Some people use bold subtitles, but that’s a little hardcore for my tastes – I prefer to ease it back one step. In my opinion, semibold is the ideal font weight for subtitles. Thick enough to really stand out, but not so thick it draws too much attention to itself. But, for the past few releases, Project Threepio’s subtitles have been a touch lighter than that, and I just tolerated it because Chrome solved so many other problems for me. And the difference is honestly subtle – most people couldn’t distinguish Medium from SemiBold, and I knew this was the sort of thing that was likely bothering only me. I could have switched everything to Bold, but the result was still slightly thicker than SemiBold on Windows, and it’d screw up non-Windows platforms, where Bold is Bold and SemiBold is SemiBold.
But if you follow that link to the Chromium bug report, you’ll see that progress has been glacial. This does not seem to be a Chromium project priority. Edge implemented a fix called enhanced-text-contrast and it works as advertised. But not only is that fix unavailable on other Chromium-based browsers, it’s still experimental on Edge and turned off by default. The default state is very important to me, because when running in headless scripted mode, you can’t always configure esoteric options – you mostly just run with the defaults.
So, while researching my options, I stumbled across an old fork of Chromium, called GDIChromium. The reasons for creating this fork were somewhat different than what I was looking for, but the resulting text is definitely what I wanted. The fork is old and doesn’t look maintained, so I would definitely not recommend it for day-to-day browsing, but it’s new enough that the headless scripting works. I’ve tried it out, and things look very good. Ideally Chromium will get around to fixing its text rendering on Windows, but until then, I think I’ve found a fine stopgap solution.
So, to make a long story short, I’m re-working the subtitle rendering script yet again, and the next release will likely have very slightly, perhaps imperceptibly to most, thicker subtitles.