Tuesday, 31 March 2020

Deep Space Nine Upscale Project Update: ‘Sacrifice of Angels’

It’s been almost exactly a month since I published my last Deep Space Nine report, where I showed how different AI software could upscale the show to something approaching HD quality. Despite the ongoing pandemic, I’ve kept the Cascade Lake testbed and RTX 2080 crunching busily away, testing various permutations. Some folks have contacted me to express interest in working together, and I’ve learned some interesting things along the way.

I haven’t been able to find my DVDs, so I bought Season 6 brand-new and started working with that source. I chose Season 6 because it has some of the best space-combat scenes, including the largest battle ever staged in the Star Trek universe in the episode “Sacrifice of Angels.” SoA was the obvious episode to work with and the Defiant image above is from an upscaled encode. Here’s the full shot.

I had hoped that the DVD source would offer a better upscaling alternative than using already-encoded MKVs. I still believe it does, but guys, I have to tell you — the baseline DS9 source sucks.

I watched this show when it was broadcast on cable, on a new 24-inch TV my parents had just bought. It’s one of my all-time favorite shows, and watching it on DVD looks nothing like watching it on TV did 25 years ago. Obviously the base resolution is low, but that’s not the problem. The video is noisy, it’s much darker than I remember, there’s a clearly visible 3:2 pulldown/telecine effect, and distant vessels are often heavily aliased (meaning they crawl with jagged lines). The credits are particularly bad as far as image quality. If the rest of the show looked as bad as the credits, I’d never want to watch it. I may upload a few videos just to show how rough they are.

Click to enlarge

This is what 3:2 pulldown looks like. You’re literally seeing half a frame of information, which is why every other line is blank. There are a number of these moments in any given episode, and while they don’t prevent anyone from enjoying the show, they can be annoying.

NanaVisitor

Nana Visitor’s reaction to the DVD source quality… or a very lucky pause on my part. You be the judge.

What I’ve Been Working On (and Learned)

Here’s the honest truth: You can get a pretty good looking video if you just rip the DVD without deinterlacing or detelecine via Handbrake (use the H.264 Production Max preset) and then upscale it. While the half-frame transitions are noticeable and annoying, upscaling this way actually cleans up some areas that are otherwise quite jagged and “crawly” at specific points in the show. If you want a one-and-done solution and you aren’t bothered by the occasional half-frame, it’s a great option and I recommend it. The result is 70-80 percent of what I think is likely possible, best-case. If you rip the DVD using Handbrake’s detelecine option, it will solve the half-frame flicker, but at the cost of introducing additional aliasing that wasn’t present before. In my opinion, the telecined upscaled DVD looks better, on the whole, than the detelecined Handbrake output post-upscale.

My long-term goal with this project is to create a guide using as much free software as is possible (Topaz VEAI is obviously a paid purchase). I’m working with a reader who has done some incredible color balance changes, and I’m excited about what that might mean for the project.

What I’ve done for the past month? About 600GB of renders at 3-8GB each. I’ve been examining color grading with DaVinci Resolve, rescaling in that same application, various AviSynth filters for antialiasing, detelecine, and deinterlacing using algorithms like QTGMC. The truth is, I could accelerate the process if I focused on smaller clips, but I prefer to upscale the entire episode. That way, I can check any trouble spot or problem area in one area of an encode against all the previous settings I’ve tested, to see how that particular area was handled.

Another thing I’ve learned? The best version of Deep Space Nine would be constructed clip by clip, using optimized video processing settings for each. I have no intention of slicing and dicing episodes up by hand, but if there was an episode you truly loved, you could achieve some truly impressive results that way.

I want to show you a short clip from “Sacrifice of Angels.” First, the DVD source and second, the upscaled output with QTGMC applied. QTGMC is a deinterlacing filter, not a detelecine filter, and it works by creating additional frames. The final output does not have the hypersmooth look of interpolated sports video, but I’ve had trouble matching audio to the clip. There’s a lot of hands-on learning involved in this kind of project because ultimately, each video benefits from a different set of filters. For best quality, change both videos to top available playback source.

This is the original DVD source. Note how the nacelles on the Miranda-class starship (the two ships in the opening frames) shimmer. This is telecined output, which means they look much better in this video than they do if I detelecine the source using Handbrake. There’s a lot of noise in certain frames and some visible compression artifacts in others.

This is the upscaled video after I applied QTGMC deinterlacing to it via a buggy and difficult-to-parse application named StaxRip. It’s been incredibly useful to me in certain respects, but if I’m being honest, I’m trying to find an alternative because this app is rather ornery and difficult to use. It also only seems to output H.265. Figuring out how to use applications like AviSynth (current user level: Bad) is part of the experience. One of our readers, Shortstick, has contacted me to show off some of his own color grading work on DS9, with impressive results:

We are looking into how to combine efforts and further improve the show.

Why I’m Doing This

If you watched Deep Space Nine on TV growing up as I did, I have news for you: You never actually saw the work that VFX designers put into those battle scenes. Watching “Sacrifice of Angels” in upscale on a much larger display, I was struck by how incredible the shots were. The space battle in Insurrection may have had more expensive special effects and a few more years of CGI advances, but it didn’t involve half as many ships or as many complex maneuvers.

Until I started working on this episode, I never thought about how space combat evolved from Star Trek: The Next Generation to DS9. On TNG, battle is almost stately, with large ships firing at each other from static positions. The exception to this is stern chases, where the Enterprise is pursued by an opponent.

DS9 changed all that. The decision to introduce the Defiant and to make it a small ship completely changed the rhythm and flow of space combat. The Defiant wasn’t made for stately, sweeping broadsides — it’s an antimatter-powered flying gun that can absorb significant amounts of damage while it blows your ass into next week. Above all, the Defiant is fast, and Jadzia Dax is one hell of a pilot.

The entire battle “language” of Star Trek changed dramatically between TNG and DS9, largely on the backs of the VFX artists who were tasked with doing the work. DS9 didn’t just add more ships; it showed those ships doing more things, with background battles often as dramatic as the foreground shots. True, some people disliked the look and preferred the idea of a more spread-out fleet engagement, but I’m not one of them. I’m watching a show in which aliens with no concept of time live inside a stable wormhole. I don’t need the starships to stay far away from each other to enjoy the battle scenes.

Speaking of wormholes…

Watching this episode in standard DVD quality is like looking at a da Vinci painting with 500 years of grime on it. You can recognize the mastery of the work, but there’s a lot of schmutz between you and it. Thanks to advances in AI processing, we’re finally seeing consumer tools that can wipe the grime away — and not just for DS9, but for any number of additional shows. The artists that worked on these episodes deserve to have their work seen in something approaching the way it could have looked.

I’m never going to be able to make these old DVDs look as good as what Paramount could do. Heck, I’m never going to improve them as much as a professional video editor could do. But Paramount has no plans to upgrade DS9 itself, and that means the only way to restore the TV show to some semblance of how it could look is with a lot of elbow grease, filter testing, and one exhausted RTX 2080. I think the work deserves to be done, even if Paramount disagrees.

Interested in helping? Give me an email or sound off below. Got ideas or tips for using AviSynth? Get in touch.

Now Read:



from ExtremeTechExtremeTech https://www.extremetech.com/extreme/308505-star-trek-deep-space-9-upscale-project-update

Coronavirus: Paramedic protective kit 'only fit for making sandwiches'

A London paramedic says he does not feel protected while treating patients with suspected coronavirus.

from BBC News - London https://www.bbc.co.uk/news/uk-52091420

Coronavirus: How to help film the news

Ellie Crisell explains how you can help the BBC report during the coronavirus outbreak.

from BBC News - London https://www.bbc.co.uk/news/uk-england-52090705

Daniel Levy: Tottenham chairman issues warning as non-playing staff take pay cut

Tottenham's non-playing staff will take a 20% pay cut during the coronavirus pandemic, the club announces.

from BBC News - London https://www.bbc.co.uk/sport/football/52105337

Samsung Galaxy Chromebook Goes on Sale April 6 for $1,000

Google has essentially owned the premium Chromebook market ever since it launched the first Chromebook Pixel way back in 2013. Now, Samsung is about to dive in with its Galaxy Chromebook, which it unveiled at CES 2020. Samsung has finally announced a release date for the laptop, which starts at $1,000. You’ll be able to get the Galaxy Chromebook at Best Buy starting on April 6th

Many Chromebook aficionados were expecting Google to refresh the Pixelbook in 2019, but the company instead announced the less expensive Pixelbook Go. Samsung worked closely with Google on the Galaxy Chromebook, and many think of it as the true successor to the 2017 Pixelbook. Not only does it have impressive specs, but the design is also reminiscent of the Pixelbook. It’ll come in an understated gray color or the lovely “Fiesta Red” seen above.

The centerpiece of Samsung’s new Chromebook is the 13.3-inch 4K OLED screen. Yes, $1,000 is objectively a lot of money to spend on a Chromebook, but this will be one of the least-expensive, high-resolution OLED laptops available. It will also have 256GB of storage, 8GB of RAM, and a 10th generation Intel Core i5 CPU. At CES, Samsung said it would have a version with 16GB of RAM and 1TB of storage, but there’s no sign of that variant yet. Like other Samsung notebooks, the Galaxy Chromebook comes with a fingerprint sensor and a built-in stylus. 

The stylus docks inside the Galaxy Chromebook when not in use.

Google has worked to improve the value proposition of Chromebooks over the years with support for Android and Linux applications. The former is included on every Chromebook out of the box, but Linux support is still in beta and requires you to jump through some hoops. Still, the additional software capabilities help to justify the powerful hardware on a device like the Galaxy Chromebook. 

The Samsung Galaxy Chromebook is going to be a tough sell when other Chromebooks offer almost the same experience for much less. The Asus Chromebook Flip C434 is under $600, and the Google Pixelbook Go is $649. Samsung is probably hoping that 2017 Pixelbook owners will want an upgrade, but Google didn’t sell many of those until the prices dropped. Nevertheless, you can pick up a Galaxy Chromebook next week at Best Buy. There are no pre-orders available at this time.

Now read:



from ExtremeTechExtremeTech https://www.extremetech.com/computing/308443-samsung-galaxy-chromebook-goes-on-sale-april-6-for-1000

Crippled No Longer: MATLAB 2020a Runs AMD CPUs at Full Speed

A few months ago, we covered how Mathwork’s Matlab software didn’t run workloads on AMD CPUs at full speed. These products use the Intel Math Kernel Library, which will only run fully optimized code on Intel CPUs. AMD CPUs were shunted into using a different and much slower code path. Despite widespread speculation from the community that MathWorks might either be unable or unwilling to patch the issue, the company has surprised us all and fixed it.

According to NedFlanders1976 (the same individual who made the original Reddit report), MathWorks has incorporated a permanent path fix into Matlab 2020a, the latest version of its application. Essentially, Matlab now always starts in a mode that allows it to run AVX2 code on AMD CPUs. Previously, you could only force this capability by creating a System Environment Variable or a special batch file to launch the program.

Kudos to Matlab

I’d like to acknowledge and thank MathWorks for being willing to resolve this issue and for doing so quickly. I’ve had a number of conversations on this topic with my colleague David Cardinal, who has more experience than I do with the software development side of things. One of the points he made in our discussions is that these sorts of situations play out very differently from the software developer’s perspective.

Matlab performance from our 3970X review. Top scores are from a non-optimized run, bottom scores use AVX2.

Individual developers may not be aware that the Intel MKL doesn’t execute AVX2 code on non-Intel CPUs. Even if developers do know, many applications have user bases that are almost entirely Intel-based. If 90-99 percent of your customers own Intel hardware to begin with, the AVX2 codepath issue isn’t going to look very pressing. Working with Intel to maximize performance on an application with a user base that has chosen to buy Intel processors doesn’t necessarily look unfair from the software developer’s perspective. The low performance of AMD’s Bulldozer-derived CPUs made these questions moot until the launch of Ryzen, and just because AMD launched Ryzen in 2017 doesn’t mean everyone running Matlab instantly ran out and bought one.

Given that developers may not be aware of the impact of these issues, I think it’s only fair to judge them by how they address the problem rather than by assuming immediate bad faith just because the issue exists. Evaluated by these criteria, MathWorks’ response is excellent — the company fixed the issue in the next major application update. While NedFlanders1976 notes that “If you use other software including the MKL, e.g. Anaconda, SymPy, etc. along with Matlab, you actually might want to keep that system-wide variable as the new fix only applies to Matlab,” but he states that Matlab itself has been updated appropriately. MathWorks also confirmed the update to ExtremeTech in a separate discussion, even though the fix is not listed in the Matlab 2020a release notes.

There aren’t that many applications that rely on Intel’s compiler or libraries in this manner, but it’s encouraging to see MathWorks react this quickly to guarantee best performance on both Intel and AMD hardware. There’s nothing wrong with using an Intel-optimized library, but if companies are going to do so, they ought to inform their users that they do so, allowing customers to buy the best hardware for the task. Ideally, they would also work with other CPU vendors to offer optimized code paths for their architectures or take action to allow AVX2 code to run unimpeded on CPUs that support it. MathWorks has opted for this last approach and we hope other vendors in similar situations either follow its example or release alternately-optimized code paths that don’t rely on the Intel MKL when running on an AMD CPU if a different library would produce faster results.

Now Read:



from ExtremeTechExtremeTech https://www.extremetech.com/computing/308501-crippled-no-longer-matlab-2020a-runs-amd-cpus-at-full-speed

Wimbledon cancellation seems inevitable as emergency meetings held

A series of emergency meetings is under way to decide whether Wimbledon can go ahead this year - with cancellation looking inevitable.

from BBC News - London https://www.bbc.co.uk/sport/tennis/52103050