The Krum-B demo runs for 20 minutes per session, disables all saving and project recall, and resets the moment you reload it.
That last clause matters more than the first two. Most trials give you full function on a countdown, and this one gives you a crippled build with no countdown at all.
Knowing what the trial build actually withholds changes how you spend the time. You are not racing an expiry date, you are working inside a window that reopens as often as you want it to.
That design rewards planning. You wait until you have a real project, then start the clock and use it hard.
A per-session limit inverts the incentive. There is no clock to waste, so you can open it on a Tuesday for ten minutes, close it, and come back on Saturday without spending anything you cannot get back.
Twenty minutes is also shorter than it reads. Loading the project, finding the right passage, and dialing in a rough setting eats the first five, which leaves you fifteen for the part that matters.
What you lose is continuity. You cannot leave the plugin sitting in a mix for a week and form a slow opinion, which is how most people actually decide whether they like a compressor.
Before any of this applies, check the format. This is a VST3 for Windows, so Logic runs Audio Units only and cannot load it, Pro Tools wants AAX and cannot load it, and Mac users have nothing to evaluate until the promised build arrives.
So build your evaluation around printing audio instead. Set the plugin up, get it where you want it, and bounce the processed bass to a file before the session ends.
Then bounce the same passage with the plugin bypassed. Two files, same length, same start point, and now you own a comparison that outlives the window.
Do that two or three times across different settings and you have something the demo cannot take away from you. The files sit in your project folder and you can open them next week with no plugin loaded at all.
Name those files properly while you are at it. A folder of bounces called bass_1 and bass_2 is worth nothing in a week, because the settings are the one thing you cannot recover.
Take screenshots of the interface while you are in there. Since the free evaluation build of a paid compressor will not recall your settings, a picture of the knob positions is the only record you get of how you arrived at a sound you liked.
There is one thing this demo does not cripple, which is the analysis. The spectrum display runs live in the evaluation build, so even a session you never intend to buy from will show you where your bass energy actually sits.
The ear reliably prefers the louder of two otherwise identical things. Any compressor auditioned with its output nudged up will sound better than the bypassed signal, and it will sound better whether or not it is any good.
So match levels before you form an opinion, not after. Trim the output until the bypassed and processed versions read the same on a meter, then switch between them
This is where printed files pay off again. Two bounced stems can be gain-matched precisely in your DAW, which is far more reliable than adjusting a knob by ear while a 20-minute timer runs down.
One practical note about the purchase itself. Copy protection is handled with a key file rather than an online account, so the license lives as a file on your drive and belongs in whatever backup you already trust with your samples.
Twenty minutes is enough to answer whether the crossover lands where you need it and whether the timing controls behave. It is not enough to learn a compressor, and no honest evaluation method pretends otherwise.
That last clause matters more than the first two. Most trials give you full function on a countdown, and this one gives you a crippled build with no countdown at all.
Knowing what the trial build actually withholds changes how you spend the time. You are not racing an expiry date, you are working inside a window that reopens as often as you want it to.
The session clock resets, which changes everything
Compare it against the model most people know. A UAD plugin demo runs 14 days fully functional, activates once per device, and after that you get two courtesy resets before the only remaining option is buying it.That design rewards planning. You wait until you have a real project, then start the clock and use it hard.
A per-session limit inverts the incentive. There is no clock to waste, so you can open it on a Tuesday for ten minutes, close it, and come back on Saturday without spending anything you cannot get back.
Twenty minutes is also shorter than it reads. Loading the project, finding the right passage, and dialing in a rough setting eats the first five, which leaves you fifteen for the part that matters.
What you lose is continuity. You cannot leave the plugin sitting in a mix for a week and form a slow opinion, which is how most people actually decide whether they like a compressor.
Before any of this applies, check the format. This is a VST3 for Windows, so Logic runs Audio Units only and cannot load it, Pro Tools wants AAX and cannot load it, and Mac users have nothing to evaluate until the promised build arrives.
Disabled recall forces you to print your test
No saving means no returning. Close the project and every setting you found is gone, which rules out the normal method of leaving something enabled and checking it with fresh ears tomorrow.So build your evaluation around printing audio instead. Set the plugin up, get it where you want it, and bounce the processed bass to a file before the session ends.
Then bounce the same passage with the plugin bypassed. Two files, same length, same start point, and now you own a comparison that outlives the window.
Do that two or three times across different settings and you have something the demo cannot take away from you. The files sit in your project folder and you can open them next week with no plugin loaded at all.
Name those files properly while you are at it. A folder of bounces called bass_1 and bass_2 is worth nothing in a week, because the settings are the one thing you cannot recover.
Take screenshots of the interface while you are in there. Since the free evaluation build of a paid compressor will not recall your settings, a picture of the knob positions is the only record you get of how you arrived at a sound you liked.
There is one thing this demo does not cripple, which is the analysis. The spectrum display runs live in the evaluation build, so even a session you never intend to buy from will show you where your bass energy actually sits.
Level matching decides more than the plugin does
The output control spans minus 24 to plus 24 dB. That is 48 dB of makeup gain sitting between you and an honest judgment.The ear reliably prefers the louder of two otherwise identical things. Any compressor auditioned with its output nudged up will sound better than the bypassed signal, and it will sound better whether or not it is any good.
So match levels before you form an opinion, not after. Trim the output until the bypassed and processed versions read the same on a meter, then switch between them
This is where printed files pay off again. Two bounced stems can be gain-matched precisely in your DAW, which is far more reliable than adjusting a knob by ear while a 20-minute timer runs down.
One practical note about the purchase itself. Copy protection is handled with a key file rather than an online account, so the license lives as a file on your drive and belongs in whatever backup you already trust with your samples.
Twenty minutes is enough to answer whether the crossover lands where you need it and whether the timing controls behave. It is not enough to learn a compressor, and no honest evaluation method pretends otherwise.
