The problem is they’ll put out a beta version, then sometimes literally a week or less later release it as a public version. a week for a beta test is useless, especially when 99% of beta testers aren’t in it to do free labor, we just want a new toy to play with.
IMO they need two things:
much longer beta tests
most importantly, they need to stop adding new features and focus all their efforts into perfecting and optimizing the current ones. This type of Homer’s Makeup Shotgun update policy has been going for 2+ years now and it’s really frustrating.
1109 fps is huge ^^ and please let us tune HEVC … Main @ 6.2 => You need a Cray to display this correctly
“Low”, “Medium” and “High” is for general users. Considering licence price, we should get tunable things (like VSDC )
Agreed. A “release” version should be a stable build based on an already nearly stable beta that has had some period of intensive bugfixing with no new features being added. Buggy functions disabled if necessary. Nothing labeled “experimental.”
Releases with new features should probably happen no more often than quarterly. Anything in between should be bugfixes only.
The current scheme is really a lot of alphas and betas, with nothing that can justifiably be called a release.
I don’t know clearly where to take data, but JWST is all but noisy, artifacts are only to its structure with 18 separate pannels. Also NASA/ESA delivers RAW data, untouched, scientists do their owns tuning. Allmost all Hubble shots are computer enhanced whish is easy because taken in visible spectrum.
Also near infarred is all but accurate wave length for detailed image, but it vastly compensate it with its 6.5m main mirror and its berylium coating.
Try to compare Orion nebula from Hubble / JWST, there is a world between them
Voyager 1 is still able to send data with 8Ko of memory and a CPU that is just able to run a car button of now, but those data are however priceless
These really should be getting worked out in the betas. Isn’t that why you opened them up to everyone, to get more beta testing input you could resolve before putting up releases?
The only way to know that would be if people running this release version who had also tested the betas could report on how the release compares with its betas.