logo Sign In

Intruder

User Group
Members
Join date
10-Jan-2014
Last activity
25-Oct-2021
Posts
116

Post History

Post
#766447
Topic
Converting DTS HD-Audio for use in Premiere Pro CC
Time

In marked contrast to the spam bot above me, I have found the solution. My files were too big, over the 4 GB limit of WAV files. I knew that there was a limit, I just thought that it will stand out much earlier, at the point of file creation.

Now I chopped the file down and had to fix them because of another problem with Premiere Pro:

http://mshg33.blogspot.de/2015/04/why-do-i-get-broken-wav-files-with.html

Post
#766227
Topic
Star Wars GOUT in HD using super resolution algorithm (* unfinished project *)
Time

Yes, even downsampling (1080p -> SR 4k -> Spline64 1080p) a Blu-Ray does not show any noticable difference. So it's not only because of YouTube.

I tried this today when experimenting for a project, but with AOTC:

http://screenshotcomparison.com/comparison/123910

Best results are at the weapon's scope. Overall it introduces banding at gradients through more random noise, take a look at the edges of the first soldier's hat. Although AOTC and that frame might not be the ideal test subject.

Post
#765420
Topic
StarWarsLegacy.com - The Official Thread
Time

mverta said:

Very rarely can I say with absolute certainty that a particular piece of damage is "original negative damage." Say it's one of those white spots we see in some shots, one that shows up on every print that's ever been struck (that we've SEEN).  Should that be preserved?  Even then, I can't say that white spot was on the original negative as it first came out of the camera after shooting.  And if it wasn't, then it's not original negative, it's damage/dirt/dust. Even if it happened on the way from the camera mag to the developer, it's not original negative.  It was shit floating in the air.  And finding some clear definition for where in the process shit on the negative is good shit and where it's bad shit becomes random and insane and arbitrary.  What, one hour after filming is good shit, but if it showed up two days later while striking IP's it's bad shit?  It's impossible to say, I mean literally impossible.  So in this case, I've decided to follow my own definition, which asks the question: Is it IN the scene, or ON the scene?  If it's on the scene (physically on the emulsion of the negative), then it goes.  Nuked from orbit; the only way to be sure.  If it's something that's IN the scene (a crewmember in the shot) it stays.

 Very well said, I like your philosophy on this.

By the way, will this be released to the public? The videos really got me interested.

Post
#764738
Topic
Star Wars GOUT in HD using super resolution algorithm (* unfinished project *)
Time

Again it is stunning to see the comparison with bicubic resize, haven't seen it for a while ;)

Your latest test 122645 has even more detail but also more noise, and take a look at the gun's "sights" - the bead - it gets a bit deformed. This has happened in other results aswell, but here it is stronger. I would like to see other frames of MagicUpSR3 refined + GrainPlate, could you please post more maybe?

Post
#764689
Topic
Star Wars GOUT in HD using super resolution algorithm (* unfinished project *)
Time

This is getting better and better, one might suspect you're using a real HD transfer, haha ;)

Regarding this comparison http://screenshotcomparison.com/comparison/122417 super resolution seems to have more detail which goes with more noise, but MU handles edges with aliasing and artifacts better (right edge of chinstrap seems to be a haloing artifacts, but I might be wrong).

Post
#763702
Topic
Star Wars GOUT in HD using super resolution algorithm (* unfinished project *)
Time

_,,,^..^,,,_ said:

SuperResolution V3 Vs MagicUpPlus + GrainPlate2
http://screenshotcomparison.com/comparison/121901

Spline64Resize + GrainPlate2 Vs MagicUpPlus + GrainPlate2
http://screenshotcomparison.com/comparison/121902

Spline64Resize + GrainPlate2 Vs SuperResolution V3
http://screenshotcomparison.com/comparison/121903

[...]

my thoughts: despite the fact SuperResolution V3 is (obviously) cleaner than "classic" upscale filters, it relies on artifacts... indeed, you could see that it distorts some shapes (eyes, last teeth etc); MagicUpPlus increments details while maintaining shapes... I added a grain plate to give the impression of further details.

 Yes, MagicUpPlus really is better at keeping the shapes close to the Spline64Resize which enhancing the detail greatly. But the picture seems to be brightened up more by the process.

Did you improve it with the method DrDre used, different color spaces and reversing?

Post
#761788
Topic
Converting DTS HD-Audio for use in Premiere Pro CC
Time

Hello all,

I have a *.mkv file with a 5.1 DTS-HD Master Audio Stream. I extracted it and converted it to a multi-channel wave file. The result is a very slow audio (approx. 3 times slower) and still it is shown as 20 minutes shorter than the original audio.

So far I tried extracting/converting with TSMuxer, Avidemux, MKVToolnix, VLC and foobar2000. I either get a "wrong file format"/"unsupported compression" error in Premiere Pro when converting to *.dts or *.ts or a corrupted file like described above when converting to wav/FLAC. Maybe my MKV is broken, but I don't know how to fix it.

Can somebody help?

Thanks in advance

Post
#761276
Topic
Star Wars GOUT in HD using super resolution algorithm (* unfinished project *)
Time

Wow, PaNup with MagicUp looks nice! But it also emphasizes the grain.

By the way, to simulate a scene change, I cut the clip so it starts from the given frame and used VideoEnhancer. Comparison with full 40-frame clip here:

http://screenshotcomparison.com/comparison/120395

Very subtle but you can see it better at her hairline. The most moving part, the mouth, has very few visible differences for me. But when zoomed in with Photoshop you can see it.

Note that real results depend on the algorithm on how well VideoEnhancer recognizes a scene change.