They said it can process 1.5 sec IRs so i tried impulse reverb on clean profiles yesterday.
It does not work even if they are shorter than 1.5sec. Where is the mistake?
CAB Maker 1.5 sec IRs
-
mba -
January 16, 2013 at 10:00 AM -
Closed -
Thread is marked as Resolved.
-
Perhaps the cab maker can process longer IRs but i am sure they will truncated. Look at athe filesize of the resulting KPA cabs. I am pretty sure you cannot use them for reverb, just as an EQ curve for the cab.
-
Im just guessing, but most likely it is just an approximation of several internal KPA cab parameters + some reverb tail. You cant expect too much from it. But of course it is nice to have.
-
Perhaps the cab maker can process longer IRs but i am sure they will truncated. Look at athe filesize of the resulting KPA cabs. I am pretty sure you cannot use them for reverb, just as an EQ curve for the cab.
Probably. But what is the reason of this? A futur support for longer IRs? (which means convolution reverb...) -
Probably. But what is the reason of this? A futur support for longer IRs? (which means convolution reverb...)Because there won´t be any convolution reverb on the KPA in the near future. At least that´s what CK says.
-
In this case it makes not sense to say that it can process 1.5 sec IR.
-
Longer IR taken in account is, better low frequency response is...
-
In this case it makes not sense to say that it can process 1.5 sec IR.
Why not? This way you don´t have to process longer IRs. It will just use the first part of that IR though. Anyway, since the results so far were not that overwhelming, i probabaly won´t put any more time into this. There are still enough speakers to capture into KPA cabs
-
Hey guys,
I have to admit, the 1.5 sec statement might be a bit misleading here. In fact, it just means that CabMaker analyzes this first portion of the file and ignores the rest if the file is longer (which is usually not the case with Cab IRs).
As CabMaker takes WAV files as its input, you can feed it with almost everything, but it will always make a Cab out of it, nothing more. A reverb tail doesn't fit into a Cab model, so what remains is something like the overall color of the tail, not its temporal behaviour. I think you wouldn't expect the profiler to fully capture a reverb device just by profiling it either.
-
Ok so it's wrong, you should perhaps remove this statement.
