Two problems when i use Topaz Video AI recently

  1. TopazVideoAI v5.5.0 and TopazVideoAI v5.4.0 both have same problem, that is the frame rate of the output video file is not the same with i selected in Video AI.

for example, when I import a 1280×720p 25fps video into TopazVideoAI v5.5.0, select the preset “Upscale to FHD”, frame rate select the default “25 FPS (Original)”, output to 1920×1080 25fps video, tried for four times, but the output files are always not 25fps, they are 24.909fps, 24.93fps, 24.955fps, 24.929fps.

only when I rollback to TopazVideoAI v5.3.5, it output the correct 25fps file.

  1. Hard disk space issues

I want to use Video AI to export a video file as ProRes 422 HQ, The output file directory I chose is D:\k2\temp.

I mounted a 24TB hard drive as a folder “k2” in the root directory of drive D.

so K2 is a 24TB hard drive, at least 7TB of free space, but an error occurred midway, display this:

  • No space left on device.
  • Free space in C:/ : 352.422 / 953.268 (GB)
  • Free space in D:/ : 147.466 / 953.867 (GB)
  • Free space in E:/ : 128.655 / 476.938 (GB)
  • Free space in F:/ : 1216.620 / 1907.712 (GB)
  • Free space in G:/ : 51.480 / 2794.394 (GB)
  • Free space in H:/ : 179.833 / 7451.910 (GB)
  • Free space in M:/ : 16.390 / 7451.910 (GB)
  • Free space in O:/ : 15.026 / 4657.400 (GB)
  • Free space in P:/ : 6.508 / 2794.394 (GB)
  • Free space in Q:/ : 13.208 / 2794.394 (GB)
  • Free space in W:/ : 8.959 / 2794.394 (GB)
  • Free space in X:/ : 42.489 / 2794.394 (GB)
  • Note: some space gets freed up when the unfinished files are deleted when a process fails.
  • Free space in C:/ : 352.421 / 953.268 (GB)

According to the Video AI error message, Video AI only detects hard disks with hard disk drive letters. my output file location is not detected at all, that is, the D:\k2 with plenty of space.

please fix, or i can’t output large files, thanks.

my system is win10 x64.
logsForSupport.zip (392.7 KB)

The team is looking into what is causing the frame rates to come out incorrectly when working with ProRes and they are hoping to have a resolution for a patch shortly.

The app will write the temporary file to the workspaces folder location before final assembly and transfer to the final location. The D drive file path looks to be less than what the file is going to take and as you said the 24TB drive is not being seen correctly since it is not mounted with a letter.

Can you try mounting the drive and assigning it a letter and then set that as the file path?

thank you for reply. The frame rates problem not only affects ProRes, but also H264, because I tried output H264 file and ProRes file for many times, both have this rate problem, and i also tried this three version, VideoAI v5.5.0, VideoAI v5.4.0, VideoAI v5.3.5, only v5.3.5 is OK, seems not have this issue.

and you said, Can you try mounting the drive and assigning it a letter and then set that as the file path?
yeah, i think if i assign letter to the 24GB drive, it may be works. i don’t know when the output file is large enough, as you said will the temporary file occupy the C drive space?

And i need mount a hard drive as a folder this way more, because the windows letters are not enough, my most hard drives need to work as folders mounted this way. D:\A to D:\Z are already used up, D:\A2 to D:\K2 are in use.

I hope that the ideal way is that no matter how much space my C drive has, and no matter whether the hard disk where the output file is located is assigned by a drive letter or mounted as a folder, as enough space as it is , I can output.

My F drive is also an SSD, and it has the most available space on my computer, with about 1TB of available space. Can I set the cache files of Video AI on the F drive? In other words, can I continue to use the available space of the F drive as a cache file when the available space of the C drive is not enough?

also v5.3.6 is ok, is the last version where the framerate problem does not exist.

OK, and the disk space issue is also important for me, please help with research.

Windows or iOS?

win10 x64

Sorry I’m not sure of your description. Relevant is only the free space on the partition where TVAI is installed, because by default TVAIs Cache folder is there. But you can change the location of the Cache folder into TVAI, I you like. Second, for sure the location where you export you’re encodes is relevant.

You have 350 GB free space left on the C: Partition (windows is there?) and then you have “only” 147GB left on the D: partition, where you export? You’re talking about a 24Tb HD, so where is the rest and the many drive letters. I don’t know where they point to.

Windows Disk Management gives you a good overview. Could it be you have unassignet space left on you’re 24TB HD?

Just a sample picture of the Windows “Disk Management”
grafik

Snipaste_2024-12-06_07-33-39

yes, my windows 10 x64 is on the C: Partition, and TVAI is on the C: Partition too, and my export file is, for example, D:\K2\temp

my D: partition is 147GB left, but my D:\K2 is a 24TB HD, because I mounted a 24TB hard drive as a folder “k2” in the root directory of drive D. So K2 is a 24TB hard drive

TopazVideoAI v5.5.1 is out now, has this version completely fixed the framerate issue?

grafik
showed Volume has no drive letter and I wondering about D: drive you talking about that should be on this volume. Is this volume otherweise segemented or so, are you sure D: is on this volume?

Try assign a letter to this 24TB Volume in Windows Disk Managemet and access it over this one

  • No variable framerate is not fixed yet

yes, assign a letter is works. but now TopazVideoAI can only recognize D:\ , and free space in D:\ , TopazVideoAI can’t recognize D:\K2 is my 24TB hard disk, and D:\K2 's free space.

If you have not assigned a drive letter to the 24TB volume in the “Windows Disk Management”, so then you can’t access this volume in Windows File Explorer in normal way.

yes it seems you have access to the 24TB HD, but doing some other unusual way. I don’t know what “K2” is, in you’re screenshot “K2” seems like a file without an extension and it does not look like a folder. As it is, TVAI can’t use this, or has problems with it.

D: what TVAI can see is something else not you’re 24TB Disk because no Windows drive letter is assigned. I recommend assign a drive letter to the 24TB Volume in “Windows Disk Management” then TVAI can see it and use it.

D:\K2 is indeed a folder, and it is indeed a 24TB hard drive, because I use it by mounting the hard drive as a folder.

I don’t know why the hard disk mounted on my computer is displayed as such an icon. It should be a folder icon.

As you said, it is indeed possible to assign a drive letter to this 24TB hard drive, but this will occupy a drive letter of mine. My system drive letter is not enough, and I need to set or change it every time I use it. So it is best to directly support hard disks mounted as folders.

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.