thanx with your tip now i have 0,7-0,8 fps 
2 Likes
The King Turd Beavis and Butthead collection deserves a Starlight remastering!
5 Likes
Haha…that’s the goal!!! Beavis and Butthead Forever!!!
6 Likes
No matter what I do, 7.0.0.4.b errors everytime I try to export. My source video is 720x 576 PAL mp4 - used same settings as 7.0.0.3.b. Done clean install - restarted multiple times - logs attached
logsForSupport.zip (14.3 MB)
I finally got the memory percentage to stick. I created a new project and I typed in the actual number instead of using the slider. Not sure which thing fixed the bug, but at least it’s working now!
1 Like
With a 4090 and testing Starlight mini I seem to error everytime I export as TIFF @ 16bit - 8 bit seems to work fine. This was after selecting the 2x then down to 1x fix. Tried it also at 2x and 3x and no go.
logsForSupport.zip (4.3 MB)
Without closing programs (I have a ton running right now tbh), and limiting VRAM usage on 4090 to 75% for now (because of above feedback from others) – This is already the fastest starlight mini version i have ran
Hello.
I scale a lot from 160p with the old model Artemis 1.0.1 because the newer models have rather disappointed me and even Starlight Full has problems.
Now I’ve tried Starlight Mini with an RTX3090 and I’m really impressed and the model is on the right track!
I think Starlight Mini is better than the Full version for the following reasons.
Pros by Starlight Mini:
- The faces and eyes are more natural
- Eye blinks are easy to see.
- Static backgrounds are very stable and do not change.
- Text and lines are usually nice and clean
- Scene changes are good
Cons by Starlight Mini:
- The image is blurrier, but I think you can sharpen it up with a second pass using a different model.
Cons by Starlight FULL:
- The static backgrounds are not stable and change or morph in a short time!
- The faces look artificial and the eyes sometimes look strange or have errors.
- Eye blinks disappear more often and the eyes are usually open.
- Text or straight outlines are not nice
- Scene changes are sometimes not clean and fluctuate in brightness
Starlight Mini has positively surprised me and I hope it gets even better!
9 Likes
It took me a minute to realize it, but the 2x 3x 4x scaling is completely messed up ..
“480p” 1x tries to scale to 720p
2x is not “2x”
And the RAM slider does nothing for me, it’s only using half my 24GB of VRAM no matter what i do.
And when i corrected it, this is still slower, and lower quality than the first beta (for me)
not sure at which point but I had memory leak after using 7.0.0.4.b and had to restart my windows 10. Seems to be working fine after that. Even Starlight mini on RTX 3090 24GB VRAM and 64GB DDR4. I changed VRAM limit to 95% just to have a little extra if needed. I was checking VRAM and RAM usage using GPU-Z. for some reason when loading Starlight mini it occupied 24.5GB VRAM (100%) plus it was swapping to CPU I presume, after couple of minutes it went down to 17GB VRAM and of course speed of processing increased. Still a lot slower compared to other models. Inability to use other than 2x or 4x upscale is somewhat limiting at the moment. Have to prepare the source material beforehand.
I have now tested this version (BETA4) .
The problems with the VRAM are solved for me, no crashes ors so.
The speed is the same as in Beta1: 320x240 => 1280x960 0.7 FPS (RTX 4090)
Only for settings (use 100%) are used> 30GB VRAM => lower speed.
In other settings (80%, 75%, 50%, 25%), approx. 11GB are used => faster speed.
The quality at 100% VRAM is a little better / different.
If you export as individual images, you can observe:
With 100% VRAM: 24 pictures are always “spit out” (=> greater time stability).
With the other attitude: always 8 pictures at the same time.
The difference is noticeable that in the latter settings sometimes objects slowly “morph”. (Although the maximum setting, but not quite as much).
A restart from the program is necessary so that the settings are taken over.
The VRAM settings for Starlight should take place elsewhere with a different name, for example as a model parameter directly below the model selection. You shouldn’t be called “Max VRAM”, but for example "Normal Quality [Faster]/ Max Quality [Slower])
Which is still a little problem (for all beta versions):
The first frame is lost (this can also be seen in the preview in export). This can later lead to Audio-Sync-problems if, for example, you are have split a longer clip into parts and thereby lost many frames.
Here is an example from a short clip.
160x120 => 1280x960
(Old Camera, 160x120 with 15fps, compressed with Motionjpeg [that was progressive a long time ago!])
I edited the clip twice, once with settings “75% VRAM” and once with "100%. (Speed: 0.7 fps / 0.3 fps).
You can see small differences to illustrate this, I created a difference.
Also interesting:
I resized down the output again to (1280x960 => 640x480) and then scaled up again with Starlight, which increases the quality again.
Tests:
Original:
2x Starlight (160x120 => Starlight 1280x960 => 640x480 => starlight 1280x960)
Settings to 75% VRAM (0.7fps):
Settings to 100% VRAM: (0.4 fps):
Here is the difference between the Frames:
Here a small part cropped:
Settings 75% VRAM:
Settings 100% VRAM:
2x Starlight:
6 Likes
This beta version still renders video I did NOT ask it to render and makes playback of video (that I DID ask it to render) terrible.
How do I get the program to stop this behavior?
1 Like
Great observations. I did notice the output looks a little soft with mini. If it can be sharpened up slightly, it will look really nice. The fastest speed I’ve gotten so far is .9fps.
I hope with optimizations, this model can be sped up to 3-5 fps without quality or temporal consistency loss. It would save a ton of time. But again, I prefer quality first, so if it has to be slow for maximum quality, that’s what I will do.
1 Like
I did RheaXL on a Starlight mini upscale and was suprised in a positiv way. Starlight usually delivers (too) soft results and RheaXL 1x makes it harder/sharper less blury overall by keeping details. Doing 1x RheaXL exist no problem with disorted faces. Unfortunately 1x RheaXL can produce jagged contours but the effect seems to be reduced when footage is Starlight. Just give it a try, it looks promising but I can’t draw a final conclusion yet and am still testing what works together and what doesn’t
1 Like
the original is dvd interlaced?can you please share your settings?
I have no settings to share because I did not set any. Do Starlight mini upscale, import the encode into TVAI and do RheaXL 1x original size in auto mode, without user settings.
ups sorry wrong response, you asked daniel
I dont know if the response was to me.
My sample images are from 320x160p progressive mjpeg videos upscaled to 1440x720p with Starlight mini und Full
This is actually really nice. A rhea or iris upscale seem to work pretty good after a starlight export. Rhea is terrible with teeth though. It makes them look jagged and weird like a vampire. But in general, using iris or rhea really sharpens up the image and since there are decent details, it’s easier for topaz to upscale it properly.
I hope we can get to a point where a two step process is not needed though.
Seems similar to what happened here.
All system RAM was occupied and GPU used to 99% even though TVAI was quit.
I could cure this by killing an ffmeg task and atask called „runner“ in the task manager. No restart needed.
1 Like
I just did a test with first doing a starlight mini turn and after that applying Iris 2x. Additional sharpness due to thus but also a little bit more „plastic“ look.
Edit: seems I was too slow…
