Unifab 2.0.3.8 is a complete DISASTER!

[knighter]

The close status will be automatically updated if there is no contact on this ticket for a few days. You can reply to reopen it anytime you want

[raven-au]

Well I am impressed, 3.0.0.0 has managed to not solve the problem and has taken away even more functionality.

[Mandalorian1]

Well I am impressed, 3.0.0.0 has managed to not solve the problem and has taken away even more functionality.

Just loaded 3.0.0.0 and am running it now. Still stuck at zero progress (after nearly 30 mins.) when doing an upscale to 4K. The little blue circle spins, but nothing else (% or Time Remaining) advances. Functionality is now stripped down to the bare minimum. No more ability for user to adjust bitrates and other output options. This is even worse than 2.0.3.8. How is this a "Next-Level Experience". I guess you could say it is if you're in an elevator headed to the basement from the upper floor! I'd be ashamed to release this software to the users. It's an attractive interface, but void of functionality, user controls, and reliability.



I'm removing this "crappy-ware" and going back to 2.0.3.7. Even though HDR has issues in that version, I can at least do a decent upscale to 4K.

[knighter]

We've reported this problem to the develop department. Please allow some time. Have you also reported throguh ticket? You can supply your log to us here or through ticket.

[raven-au]

Yes, I see that same behaviour with the Enlarger module.

I do see this with the Denoise module too but I find that by fiddling with the settings I can get it to work most of the time.
I had no success doing this using the Enlarger module no matter what I did.

The HDR Upscaler seemed to work too but that was for a HDR10 conversion only since I can't upscale, didn't try Dolby Vision yet.

I hope that the observation about fiddling with the parameters helps to work out the cause of the problems.

I must say that I'm not happy with the removal of the fine grained quality control.
When I get artifacts (often in faces that are not close ups) I find that increasing the quality (bitrate) can help but with the latest update my only choice is to essentially "double" the size of the encode which is not ok with me. Either bring back the flexibility or fix the encoding of your application.

[Justin]

It's so slow this program

[Mandalorian1]

We've reported this problem to the develop department. Please allow some time. Have you also reported throguh ticket? You can supply your log to us here or through ticket.

YES and YES again. Nothing seems to get done. Your development team seems more interested in changing up the UI and removing functionality intead of fixing the many problems it has and leaving the pre-existing functionality and controls in place. I just got a survey about what NEW features to add. That's nice you want to add new features. I have a better suggestion, why not restore the functionality that was there pre-2038/pre-3000 and fix the issues that have been ongoing since pre-2037. Doesn't do any good to create a new UI and add new features if there is missing and broken functionality that remains and is NOT fixed.

Right now, as of 1/1/2025, version 2037 appears to be the most stable version, despite the issues with over compression of output in HDR and the flashing/flickering lighting. HDR has had issues since about 2036 (red hue was fixed; other problems noted were introduced or not addressed since). Also, 2037 at least has the user functionality and controls that your development team seemed to REMOVE in 3000. Those advance controls I speak of were the ability to control Video Codec, Frame Rate, Bit Rate, etc. Also, Audio Codec & Channel, Sample Rate, Bit Rate. Version 3000 seems to have taken away much or all of these advance user controls and tried making the software geared and "dumbed-down" to a novice level. Some of us more advanced users would like to have these features back. Please pay attention to what your users want and need and don't IGNORE US!

[Mandalorian1]

Did another trial run of Version 3.0.0.0. This time I tried using it with a smaller video (shorter duration of less than 5 minutes). This time I did find that the "% Completed" and "Time Remaining" did increment/decrement accordingly. After that, I tried it out with a full-length movie slightly over 2 hours duration. That's when it gets caught in what seems to be a "no progress" noted situation.

For this feature length movie, it has been roughly 30+ minutes where the Time Remaining and % Completed are stuck at ZERO progress. This gives the user the impression that nothing is happening or that the application is stuck in some kind of indefinite/infinite loop. My guess is that the application is probably doing some kind of analysis of the video prior to actually re-encoding it and during that period of time the progress remains at a stand-still. This would explain that when running the 4K Upscale on the shorter duration video, the analysis doesn't take long to complete before the processing engages and the progress (% and Time Remaining) reflects incrementing/decrementing as one would expect. If this is the cause of this issue, there should some kind of progress visual that lets the user know what is going on. Maybe there needs to be a separate step for any pre-analysis (before actually processing the video to upscale, etc.) with its own progress visual before moving it forward along the progress line to actual processing of the video.

[Mandalorian1]

Did some further testing and have determined that it isn't due to the size (duration) of the video source after all. Apparently, it is tied to the M2TS file. It doesn't like the M2TS file format of the source video file and gets hung up. If I convert it to an MKV format, it quickly jumps through its pre-processing/analysis phases and then starts processing with the process status visuals appropriately reflecting actual progress status. The work around is convert the M2TS file to MKV and process that instead. That is an obvious issue as, per the software you should be able to use a native M2TS file format for processing.

GOOD NEWS per latest 3.0.0.0 version also noted is that the HDR issues have been addressed (flickering and over-compressing output). The source video I've been using for testing now produces a video output that is somewhat larger in file size than the original source when doing HDR upconversion on it. That is the way it should be. Before, the HDR Upconvert output was nearly 50% smaller compared to the original source. It also produced noticeable adverse quality issues when viewing the output as a result of the file compression issue.

BAD NEWS is that the quality of the 4K Upscale is not has good as before. It is not as sharp. Quality has gone down there.

[knighter]

For this freeze probelm have you tried 3.0.0.1？

If still doesn't work, please send the UniFab_log for check.