I have been trying to upscale quite a few clips with Starlight Mini in the Cloud, therefore using purchased credits, since as a Mac user, we do not yet have the luxury of processing it locally.
Sometimes, when lucky, I am able to have some success with very short clips (1 minute.)
It usually takes an immense amount of hours to do so, but as I try to process anything above 2’30" (and below the max allowed of 5’), it fails in most instances.
It is a good thing that the spent credits are added back to the account, but it is disheartening that after processing a 2’30" clip for a couple of days, the cloud rendering fails to finish the job.
the ideal solution would be to accelerate the release of Starlight on OSX, but in the meantime it would be nice to get an idea if the cloud rendering is ever going to work as intended.
As of now it is truly disfunctional.
Do you have the job ID numbers or the logs from the app to send to the support team to look at and see what is going on?
Unfortunately not anymore, but I will run a few more, and post the failed IDs (once they fail after a day or two of processing.)
Just for the record, when you first launched Mini, the success rate was quite good, and the processing time was more than acceptable for 5 min clips, now the success rate is negligible, and the processing time before failure is massive, even for short clips (1 to 2.5 mins clips.)
I have been thinking it is an overload issue, so I patiently waited, hoping for a Silicon Chip release, but it has been a while without that release, and therefore I have no choice and have to rely solely on the cloud, or build an expensive dedicated PC that would have no use other than for this task.
Additionally, rather than using the Mac’s TVAI, I am going to give it a go in your cloud browser version
Dear Kyle, I ran the same identical footage through your Web UX, and it worked fine, so the failure seems to be happening when I try to process it in the cloud using your latest version for Mac: 7.0.1
Hi again Kyle!
One portion also just failed in the web-based cloud: ID 01977e1b-289c-769f-bac5-efb7acd48fb2
Thank you, sending a message to the backend team to take a look and see what is going on.
