Resource monitoring: pausing video creation
Resource monitoring is measuring the processor, memory, disk and temperature. The app does it during video creation. Based on these measurements, four readings are shown at the bottom of the window. The app also uses them to pause the work when resources run short. The thresholds for coloring the readings and the thresholds for pausing are different numbers, and below they are split into separate tables.
When the readings at the bottom of the window are visible
The four readings sit in the footer of the tab, next to the "Start" button. There are two conditions for them to show. The first is that the app is creating videos right now. The second is that monitoring is not turned off in the global settings. At other times there are no readings, and that is normal.
| Reading | What it shows |
|---|---|
| "CPU" | Processor load in percent |
| "CPU temp" | Processor temperature in degrees |
| "RAM" | Used memory in percent |
| "Disk" | Used disk space in percent |
An amber reading means the value is outside the normal range. This is a warning, not a breakdown. The "CPU" reading has no amber state at all. It stays green even at full processor load.
Thresholds at which the work pauses
The device is checked before each new task is handed out. If a value is past its threshold, the new task does not start. The ring at the "Start" button turns amber. The reason is shown in the status line next to the button.
| Value | Pause threshold | Resume threshold | What is paused |
|---|---|---|---|
| Disk space | 99 % used or more | less than 99 % used | New threads on the device and downloading finished videos from the cloud |
| Memory | 95 % used or more | less than 95 % used | New threads on the device |
| A thread ran out of memory | a thread failed for lack of memory | 85 % used or less, and no threads on the device | New threads on the device |
| Processor temperature | 85 °C and above | 65 °C and below | New threads on the device |
The disk differs from the other two reasons. It pauses both halves of the work at once. Memory and temperature pause only the threads on the device. The cloud keeps creating videos from the queue in the meantime. Threads that have already started finish their video in any case.
Thresholds at which a reading only changes color
These numbers are different. They do not pause the work. A reading turns amber before the pause, and this gives you time to free up resources yourself.
| Value | The reading turns amber | The pause comes |
|---|---|---|
| Disk space | 96 % used or more | 99 % used or more |
| Memory | 91 % used or more | 95 % used or more |
| Processor temperature | 85 °C and above | 85 °C and above |
| Processor load | never | there is no pause for this value |
What the details panel shows
The panel opens when you click any of the four readings. It has three groups: "CPU:", "RAM:" and "Disk:". Before the first measurement each row shows "Waiting for the first video...", and the temperature shows a dash.
| Panel row | What it shows |
|---|---|
| "Total load" in the "CPU:" group | Processor load from all programs together |
| "VUB load" | The share of the processor taken by Video Unique Booster |
| "Other apps load" | The processor share of the other programs |
| "CPU temperature" | Degrees, or a dash if readings are unavailable |
| "Total load" in the "RAM:" group | Used memory in percent and in gigabytes |
| "Drive 'C' used" in the "Disk:" group | Used space in percent and in gigabytes |
Next to each row there is an icon. The icon thresholds are yet another pair of numbers, and they give different advice.
| Panel row | ✅ icon at | ⚠️ icon at |
|---|---|---|
| Total processor load | 85 % and above | below 85 % |
| Video Unique Booster load | 50 % and above | below 50 % |
| Other apps load | 50 % and below | above 50 % |
| Processor temperature | below 85 °C | 85 °C and above |
| Memory in the "RAM:" group | 90 % used or less | more than 90 % used |
| Disk in the "Disk:" group | 95 % used or less | more than 95 % used |
For the first two rows the ⚠️ icon means the processor is not fully loaded. The advice in this case is to add threads, not to remove them.
The exact icon tooltips:
| Value | Tooltip at ✅ | Tooltip at ⚠️ |
|---|---|---|
| Total processor load | "the CPU is used in full." | "It looks like Video Unique Booster is using only part of the processor resources. You can probably speed video creation up by adding more threads in the "Export" section. Please restart video creation to apply the new settings." |
| Video Unique Booster load | "VUB gets enough CPU to work." | "It looks like Video Unique Booster is using only part of the processor resources. Because of that, video creation may be slower than your device could manage. Close other apps if you can, or raise the number of threads in the "Export" section. Please restart video creation to apply the new settings." |
| Other apps load | "Other apps have little effect on how Video Unique Booster works." | "It looks like other processes are putting a heavy load on the processor. Because of that Video Unique Booster may not have enough resources to create videos. Close the processes with the heaviest CPU impact if you can. The Task Manager of your operating system will help with this." |
| Processor temperature | "The CPU temperature is normal." | "The processor is hot - throttling or overheating is possible." |
| Memory | "There is enough memory to work." | "More than 95% of the memory is taken. Please consider closing other apps to avoid possible errors during video creation." |
| Disk | "There is enough disk space to create new videos." | "More than 95% of the disk space is taken. Please free up disk space to avoid possible errors during video creation." |
What the status line shows during a pause
| Status line | Reason | What to do |
|---|---|---|
| "Waiting for disk space" | 99 % of the disk or more is used | Free up space or choose another save folder |
| "Paused, CPU overheated - waiting for it to cool to 65°C" | 85 °C and above | Wait for it to cool down, check the device cooling |
| "Paused, memory N% used - waiting for it to free up" | 95 % of memory or more is used | Close other programs, reduce the number of threads |
| "Paused, not enough memory - waiting for it to free up" | A thread ran out of memory at start | Close other programs, reduce the number of threads |
With the "Endless" export type there are no separate lines about overheating and memory. The status line stays the same: "Running. N/M files in the folder". New threads still do not start.
How the work resumes
You do not need to click anything. The measurement repeats, and the pause lifts by itself.
- Disk: as soon as less than 99 % is used.
- Memory: as soon as less than 95 % is used.
- Temperature: as soon as the processor has cooled down to 65 °C.
- After a real memory shortage there are two conditions: 85 % or less is used and there are no threads on the device.
A failure counts as a memory shortage by any of three signs. The first is that the video processing module itself reported a lack of memory. The second is that the thread exit code points to a lack of memory. The third is that 95 % of memory or more is used at the moment of the failure. In the first two cases the usage percentage does not matter.
The status line returns to "Running". The ring at the "Start" button becomes normal again.
The fourth case is worth explaining separately. It kicks in when a thread really ran out of memory at start. On a device where more than 85 % is used at idle, new threads will not start at all. The cloud works through the queue in the meantime. If the project has no cloud threads, the work stands still until memory frees up.
Three desktop notifications
At each pause Windows shows a notification. The disk notification is shown once for the whole run. The overheating and memory notifications are shown once per episode, and there can be many episodes.
| Notification title | Text | When |
|---|---|---|
Disk {letter} is out of space | {N}% of the disk is used. Video creation is paused. | 99 % of the disk is used |
CPU overheating | CPU temperature {N}°C. Starting new threads is paused. | 85 °C and above |
High memory usage | Memory is {N}% used. Starting new threads is paused. | 95 % of memory is used |
Clicking a notification opens a window with details:
| Window title | Text |
|---|---|
Not enough disk space | Disk {letter} is already {N}% full out of the 99% allowed (set by the system). Video creation is paused until disk space is freed. |
High CPU temperature | CPU temperature has reached {N}°C (threshold 85°C). Starting new local threads is paused until the CPU cools to 65°C. Threads already running continue. |
Not enough memory | Memory is {N}% used (threshold 95%). Starting new local threads is paused until memory frees up. Threads already running continue. |
The right to a second memory notification comes back only at 65 % used memory. The pause may repeat before that number. Then there will be no second notification, although the pause really did repeat.
How to turn off monitoring and notifications
All five settings are in the "Global settings" window. By default all five are off, which means monitoring and notifications work. After a change, click "Save".
| Setting | What it turns off |
|---|---|
| "Disable notifications when the disk is full" | Only the notification. The disk pause stays |
| "Disable notifications on processor overheating" | Only the notification. The temperature pause stays |
| "Disable notifications on high memory usage" | Only the notification. The memory pause stays |
| "Disable device resource monitoring" | Measurements, pauses, notifications and all four readings |
| "Log device state to a file during video creation" | Turns nothing off. Turns on writing the logs\resource_monitor.txt file |
The "Disable device resource monitoring" setting takes effect from the next start of video creation. Writing to the file, on the contrary, turns on right away, no restart is needed. Both live in the expert group of the window. Everything else about this window is on the Global settings page.
There are two things the "Disable device resource monitoring" setting does NOT turn off:
- counting files in the save folder, otherwise the "Endless" export type would never stop;
- the disk check in the "Check before start" sheet, because the sheet measures the disk itself.
Thresholds checked before the start
The "Check before start" sheet measures the device separately, with its own numbers. Some findings refuse the start, some only warn.
| What is checked | Number | Outcome |
|---|---|---|
| Disk space | 95 % used or more | The "Low disk space" warning |
| Disk space | 99 % used or more | The start is refused, the "Start now" button is inactive |
| Memory reserve for the system | 2 GiB or 30 % of all memory, whichever is more | The "More local threads than recommended" warning with the "Set N" button |
| Core reserve for the system | 1 logical core | The upper limit of the safe number of threads |
| Memory usage forecast | above 90 % of the reserve | The "The system may fail: too many local threads" warning |
The whole sheet is covered on the Check before start page.
Why there is a dash instead of the temperature
The processor temperature is read by a separate helper process. A dash instead of a number means it could not be read. This is not a breakdown, and video creation works as usual.
There are three possible reasons:
- The app has no administrator rights. Then there are no numbers from the hardware.
- The helper failed to start three times in a row. After the third failure the temperature is not shown until the app restarts.
- The device hardware does not report the temperature at all.
While there is no temperature, the thermal pause does not change its state. If a pause was already on, it holds. It lifts when the readings come back and the temperature is at 65 °C or below.
The app does not tell apart running on battery, a lowered processor frequency or power saving mode in any way. All these states look the same to it.
Device state file
The "Log device state to a file during video creation" setting turns on writing the logs\resource_monitor.txt file. The file is in the same place as logs\app.log. One line is one measurement:
2026-09-06 14:55:03 | ЦП: 91% (VUB 78%, прочее 13%) | Темп. ЦП: 74°C | ОЗУ: 58% (18.6/31.9 ГБ, VUB 3.4 ГБ)
- A line is written no more often than once every 0.5 seconds.
- An unavailable value is written as
н/д. - The file size is up to 5 MB. After that the app saves it as a backup. There are three backup files.
- There is no disk and no file count in this log on purpose. There is one log for the app, while projects have different folders.
- Writing happens only during video creation.
- Each line is saved to the disk right away. So the records stay in place even if the computer shuts down suddenly.
The file is written even with monitoring off. Only all device values in it will be н/д. The other app files are described on the Where your files are page.
What to do if pauses keep repeating
Frequent pauses mean the device lacks spare resources. Please work through the cause in order:
- Open the details panel and see which value is at its threshold.
- Close programs that load the processor and memory. This means a video editor, a game, a browser with dozens of tabs.
- Reduce "Number of local threads" in the "Export" section. Each thread takes its own memory.
- Turn on "Limit logical processors per thread" in the "Performance" section. This cuts both the processor load and the memory use roughly in half.
- Free up space on the save disk or choose another folder.
- If it overheats, check the device cooling: dust in the heatsink, old thermal paste, blocked air vents.
- Move the work to the cloud. Then the cloud creates the videos, not your processor. It is not freed completely: the app does the uploading, downloading of finished copies, checksum calculation and similarity check on your device.
Threads and the number of copies are covered on the Export page. What slows down video creation is on the Performance page. The difference between the device and the cloud is covered on the Video creation on the device and in the cloud page.
What monitoring does not do
- It does not speed up video creation. It only pauses the work at a threshold.
- It does not limit the number of threads. The "Number of local threads" field accepts up to 99,999,999.
- It does not check the space on the disk with projects. That is a separate check with its own threshold: the "Low disk space" warning appears when less than 200 MB is free.
- It does not stop threads that have already started.
- It does not replace the check before start. Their thresholds are different.
Frequently asked questions
Why is the "CPU" reading green when the processor is fully loaded?
This reading has no amber state at all. Full processor load during video creation is normal. Look at the details panel: there the ⚠️ icon at the total load means the opposite. It appears when the processor is NOT fully loaded.
Why did a reading turn amber, but there is no pause?
Coloring thresholds and pause thresholds are different numbers. The "Disk" reading turns amber at 96 %, and the pause comes at 99 %. The "RAM" reading turns amber at 91 %, and the pause comes at 95 %.
Memory freed up, the pause repeated, but there was no notification. Why?
The right to a repeated memory notification comes back at 65 % used memory. If memory freed up only to 90 %, there will be no second notification. The pause itself works as usual.
Can I turn off only the pauses and keep the readings?
No. The "Disable device resource monitoring" setting removes the measurements, the pauses, the notifications and the readings. Only the three notifications can be turned off separately.
Why does the cloud keep working during a pause?
A memory or temperature pause affects only the threads on the device. It does not hold back new cloud tasks: the cloud looks at free disk space and at how busy the device threads are, and does not take temperature and memory into account. A disk pause is a different case. It also pauses downloading finished videos from the cloud.
The window stopped responding. Is that monitoring too?
No, that is a separate topic. Please open the Not responding and slow page.