1/ Sometimes we can be in a situation where we must do a lot of preview.
when a preview is generated, the last preview is put at the bottom of the list instead of top.
after 6 previews (same problem with exports), they are rendered out of the window, at the end of the list (the list can only have 6 previews / export without having to scroll down).
to see the “new ones” , or be sure that it’s running, we must go down to the list if not we don’t know if a preview or export is generated.
the solution would be to make the most recent generated video to be at the top of the list.
2/ only way to empty a list full of preview or exports, is close the video source or remove them one by one. with one video it’s ok, but when batch processing will work, with like 100 videos to generate, it will maybe be a bit chaotic for the export list. but it’s the same with previews.
3/ found something weird, don’t know where i failed.
with some unusual size/resolution of video source, some have, after doing a custom height of 1080p, once generated, black bars at top and bottom while other videos are working ok.
example : a 812 x 796 video, i set custom height at 1080, it give a 836 x 1080 preview / export.
Crop to fill is turned off. result ? black bars at top and bottom.
I try again with an another video, 778x796, crop to fill turned off, custom weight 1080, it gives a 1056x1080, and give a result with no black bars anywhere.
I would never run sfc /scannow when other stuff is running. That’s something you ideally always want to run with the least amount of other processes running. You should even disable antivirus first.
In the modern era of OS’s it less necessary to stop running programs while performing system functions such as SFC. SFC is for the most part a “system” file checker. If a problem with a system file is found being that it is missing or corrupt those files can be delt with one by one while the OS is running. It’s much easier to repair/replace a single system file than say an OS update replacing many files. If SFC finds no problems there is no reason to believe the scan of that file would have an impact on a program running that just might use that file at the same exact time. If the file was found to be bad than that’s a different story but SFC should be smart enough along with the OS to wait for that file to be fully available and then replace or repair it.
One other indicator that SFC can be used while other programs are running is that when executed there is no warning to exit running program before continuing. Such a powerful program certainly after 24 years of being part of Windows would have such a warning much like the Format command has warnings. We are not in the days of Windows XP anymore.
Also for those who remember when SFC took hours sometimes to complete, while writing this ran I it on this computer. It completed in 57 seconds. That was on Gen3 NVMe and utilized only one core to 70 percent of my CPU. I never want to return to the ‘Good Old Days’ of computing.
No I haven’t tried any other file formats only because it’s the VOB file type that I’m primarily interested in to upscale to 4K lol.
I note that using just the resize filter, the encoder will actually run (but the resultant file isn’t correctly scaled to 4K) but other filters such as deinterlace and enhance will just flat out error.
I’ll keep an eye out for a new release and try it out again as and when
OK - I loaded up the latest beta, and ‘flew blind’ as all the familiar controls are absent. Took a UHD 10 bit HEVC at 23.976 and set it to process to a 10 bit HEVC frame multiplied to 59.94 FPS … with ‘improvements’ set to default. No preview of progress, no time markings or projections, just the 0.4 fps showing and a tiny bluish line coming across from the left botton screen. After 12 hours of no change, I bottled it out and closed (I had been seeing peaks of 70% on GPU-Z , and performance of half my RAM and 60% peak activity on one of the 12 processes on my Intel i7, so know that ‘something’ was happening. Having closed the application (I was rendering to an SSD drive as 10 bit HEVC 59.94P .mp4 with the sound left as ‘copy’.)
Thankfully, the nice render engine still leaves the file playable on mp4 despite closing mid process.
I played it on MPC-HC and checked for all features and Windows says HEVC (H265 unknown@ L5.1) and 5.1 sound, which plays rather nicely. This is a Dolby vision clip, and so comes out with the colour shift on this player only. I ‘think’ it is only using 1 CPU core seriously, but going well on my RTX3060 Ti graphics card, hence presumably the slow process (and being a Beta?). No progress indication is a mindbender to work with, but again, presumably this is a work in progress. The HEVC encoder works - yippee … but obviously the slow performance with the frame doubling and whatever default process enhancement is going on is a strain with one core only really doing much. The NICE thing is that a truncated process can still yield a playable mp4 file. Oh … and my signing in to my account just tells me that my licence expired sometime in 2020? It hasn’t and I suppose that is just to ensure that the TOPAZ Logo is splashed across the screen of the output - which kinda nukes any quality control assessment of the final output.
I observe on my PC that VEAI saved peridically every 40-50 minutes of processing. So far I can stop the process at any time and can use whatever has been saved. Unfortunatly I cannot resume processing from the last. I’ve not checked if it is possible to restart processing of the original from that last frame saved.
If you load the partial video in to VEAI you can read the number of frames in that video. Now you know how many frames the video completed you could start processing from the original file using the same settings as originally but move the beginning of the processing to that frame number plus one frame. After that processing is done then use some other software to join the two videos.
Just replace the .vob file names with whatever ones you have.
That loses the audio. I process that separately. I just use MKVToolNix to extract that, turn it to .wav, processes it however, then encode to .m4a.
By the way, with MKVToolNix, you only have to select the first .VOB file, and it will automatically load the other ones. You can use this as well for video instead of using ffmpeg, if you prefer.
Personally, I like to process DVD .VOB files without doing the stretching first; I think it gives better results than letting VEAI do the stretching first. I use .png (which you can only do .tif in VEAI 3.0), import that into Hybrid, then resize it to its final pixel size and aspect ratio using Spline144 in AviSynth. If you want to do this, you can just change the display width/height to 720x480 (or 720x576 for PAL) in MKVToolNix. Again, personally, I mux to mpg using ffmpeg, then use Hybrid to encode to h264 using a constant rate factor of 1.0, and checking both boxes under “pixel aspect ratio” on the “crop/resize” tab and setting all 4 boxes to 1, and setting “Square Pixel (1:1)” for “Convert Output to PAR”.
Yes, I didn’t have crop enabled (no need to crop, no black edges), and of course I didn’t use fill. The file is a bit troublesome, it is not very convenient to upload, but I have uploaded this file before, VOB file. The email is the email of the forum, and the file name starts with Part. If you keep it, I don’t need to upload it again. If not, please inform me again. I will try my best to upload it. In addition, this issue is unique to this version, the previous beta version did not cut the screen. There is also AN issue with COLOR conversion, THE color space cannot be converted in some H.265, 420, 4K videos, but in this version the GUI does not have the problem, this version seems to fix it. But the FFmpeg command line still prompts for color space problems.
VEAI 3.0 relies on FFMPEG for file input and output.
If an error occurs with a particular file, it may be because the file is corrupted or the encoder or authoring software is outputting a file that does not conform to the MPEG standard.
You should check the file information with ffprobe once or try a test encoding with ffmpeg to see if there is still something wrong. If the abnormality is still there, VEAI cannot fix it.
I have a fully paid up set of valid licences for several Topaz products and they validate my paid for products OK when I log in with the same exact details for my VEAI as with the Beta, - which doesn’t validate. I am running on Windows 10 64 bit. It’s a pain as an ex-BBC video man and previous Sony Vegas Beta tester, to have these sorts of things come up when trying to help test Beta versions of this excellent product which is moving into the real future world of video that requires HDR and 10 bit encoding output.
I tried with ProRes422 and no error.
H.264 only supports up to 4K, so if you choose H.264(INTEL), I think you will get an error.
H.265 supports up to 8K, so H.265(INTEL) may work.
p.s.
I can’t make any promises as I only have RYZEN and can’t try H.265(INTEL). Sorry.
I’ve just tried a non VOB file, this time used an H.264 1080p MP4 which is an export from Adobe Premiere Pro and the exact same error occurred as with the VOBs.
As I’m on Mac OS Monterey 12.5, could it be in relation to this more so that the source files with FFMPEG?
