The first color feature length film was the 1914 British silent film, “The World, the Flesh and the Devil.”
The first color feature length live action film with sound was the 1929 “On With the Show!” (it was also the first color feature length musical).
Both of the above are lost films.
Snow White in 1937 was the first color feature length animated film with sound. It’s also probably the earliest feature length color film with sound that is widely available to view, since pretty much all earlier ones are either lost, incomplete or locked up in some archive.
I spoke too soon. Topaz has sabotaged this method now too:
Stream #0: not enough frames to estimate rate; consider increasing probesize
Could not find codec parameters for stream 0 (Video: none (P010 / 0x30313050), none, 1920x1080, 1193207 kb/s): unknown codec
Consider increasing the value for the 'analyzeduration' (0) and 'probesize' (5000000) options
2024-10-31 18-17-51.963 Thread: 60028 Critical Unable to decode video stream information in file "C:/Volumes/alient.vpy/alient.avi"
Lovely. The entire world can read the mounted avi files with AVFS, except, of course, Topaz. Would be so nice if TVEAI actually fixed their cropping, so I wouldn’t have to resort to trick like this. Very disappointed (once again).
Well, if you had super-high throughput with Rhea before, then obviously Topaz messed up somehow. Unless they suddenly threw support of all GPUs overboard that are not nVidia 3x or 4x series. I tend to be cynical, but that seems hard to imagine, even for me.
N.B. If I may ask. what kind of fps throughput were you getting with Rhea before? Can’t be much higher than my 4.8 fps. Mind you, I ran this on 5.4.07a Alpha; might be worth a shot too?
Thanks for the insight! I’ll check out the 5.4.07a Alpha as you suggested. I didn’t realize that was a thing.
I’m relatively new to Topaz, so I wasn’t tracking fps specifically before the update; sorry I can’t give you any info there. Right now I’m getting 0.1 FPS!!!
ChatGPT wonders whether the update is less optimized for non-NVIDIA GPUs, or if there is something else I might be missing in settings that could improve performance? (It’s more au fait with this stuff than me).
My calculator said your fps should be at 0.005556 right now (7200s / 40s) ; so yeah, that can’t be right. My RTX 4090 used about 7G of memory, and 100% 3D calculations (according to Task Manager). GPU-Z pegged it at ~100% load too. Not sure what an M1 does compared to that, but it can’t be 50x slower.
Okay. I’ve gotten to the bottom of it. The edit assistant had exported the clip we needed to upscale from premiere in 4k (it’s supposed to be 640x360). I think that confused everything.
It just finished exporting from Topaz and looked like shit which is when it all clicked!
Will try updating my software now I realize it was user error.
ok this is what Copilot will tell you forget rheia with digitized VHS 95 sources
Always deinterlace with video proc pro or handbrake old vhs stuff first then use first artemis lq v13 and Iris v1 LQ save to mov extension and h265 all the time
This will give you a good result NO artifacts next step
use Proteus v3 rase the slider to 70 percent do NOT use Proteus v4 it will create artifacts and deblur artemis v2
next use colourdirector 365 for professionally enhancing colours HDR
0.1 fps is a bug I hoped was fixed but doesen’t seems to be when you have it. I had this before several times, then when I restart the task it runs at normal speed.
That means I tried to solve my FFV1 issues parsing logs for days with different scenarios to definitely quit it for ProRes
The bad thing is that “regular” ffmpeg perfectly encodes stuff with at most some warnings because of super high rate, but output is top level quality. (FFV1 level3 4K 4:2:2 10b)
Can you add the option to change order that adjustments are rendered?
I have no idea if deblur is processed before or after upscaling.
I have no idea if frame interpolation gets processed before or after upscaling.
Having the ability to sort the order that these are done would be great. I have found that the order that these are processed can drastically change the results in some cases so having that ability would be a huge improvement. I usally have to do each seperatly to get the best results. It would be a big time saver if it was possible to do this. Thanks
It is absolutely not the source file. In fact, if I convert the same 4:3 file with an old version 2.6. 4 (which I am still very happy with) I get a perfect HD file with 16:9 format.
DAR = display aspect ratio
SAR = storage aspect ratio
It’s this, means Topaz doing something wrong and with source file is everything ok.
Source is 720x576 anamorph, means the content is compressed in width which is normal for 16:9 anamorph DVDs. Topaz reads out correctly the video container flag 16:9, this must be streched to 16:9 to get correct aspect ratio, then Topaz expands the width of the video until it is native 16:9
So everything is correct up to that point. But then TVAI does a additional unnecessary fault step. Because source is 5:4 not 4:3, Topas flags the video not as 16:9, TVAI says players “you must play this with aspect 1.942 instead 16:9 (1.777)”
You can easy correct this by Muxing the file for example with MKV Toolnix and set flag it must be played as 16:9
BUT if it’s the case the Topaz encoded video itself is at wrong size, then we have a problem! I can check this tonight.
I have a serious issue with the latest versions of Video AI. In the preview window I often can not see if there are black bars in a video so that a cropping is needed. Often when 50 % completed I check the file and realize in the external player that I had to crop.