Ericlingus
Prettiest Hair Around
- Oct 31, 2006
- 1,375
- 2
- 38
sounds great! It seems to really have that heavy girth that AxeFx and Kemper both have that I havent heard in any other amp modelers.
Thermionik Amp Modeler Plugin by Kazrog LLC
- Thread starter superfreak
- Start date
![[Prime]](/data/avatars/l/138/138439.jpg?1472440784){kind=avatar}
[Prime]
Member
- May 20, 2012
- 146
- 5
- 18
Obviously, you put this together rather quickly. It sounds pretty good to me. That said, the tone is a little fizzy and harsh for my taste. And no offense to anyone.... but I am not hearing the revolutionary, earth shattering ebola curing tones that were promised.
I want my magical pink unicorn...damnit!!!
Ericlingus
Prettiest Hair Around
- Oct 31, 2006
- 1,375
- 2
- 38
Exactly my thoughts - I don't know about the 2 other modellers, but this one does have the heavy girth, without the cluttered low mid issues. There's still attack there.
If it sounds pretty good but a little fizzy, then try it out and use a lowpass.
Or wait for your pink whatever you say it is.
Kazrog
Kazrog, Inc.
Ericlingus
Prettiest Hair Around
- Oct 31, 2006
- 1,375
- 2
- 38
well my first impressions of using it for about 30 minutes is that its the worst sounding garbage ever! I think it's the cause of Ebola!
actually it sounds great and am very excited about it. I love the serpent amp. It's awesome to use amp models that havent been available in the software realm before. All the amp models are great really. They really do feel like real amps when I play through it. Man between this and my new Laney IRT Studio I'm in tone heaven! Wish I could play Thermionik some more but it's 3:30 in the morning and I probably should actually sleep. Dammit I'm probably going to stay up all night in bed thinking about my new toys.
p.s. thanks again Kazrog for hooking me up with it before my check in cleared!
actually it sounds great and am very excited about it. I love the serpent amp. It's awesome to use amp models that havent been available in the software realm before. All the amp models are great really. They really do feel like real amps when I play through it. Man between this and my new Laney IRT Studio I'm in tone heaven! Wish I could play Thermionik some more but it's 3:30 in the morning and I probably should actually sleep. Dammit I'm probably going to stay up all night in bed thinking about my new toys.
p.s. thanks again Kazrog for hooking me up with it before my check in cleared!
HOFX
Member
- Apr 12, 2012
- 469
- 0
- 16
Just playing with it now, very easy to dial in a good organic tone. Sounds open and fluid, definitely not flat and static.
I'll have more time to play with it in 24 hours but for now and put it through it's paces in a mix, but for now I think it was definitely worth the upgrade from Recab 3.
I'll try and put a comparison together between it and S-Gear tomorrow night and post it.
Good work Shane, I hope this goes well for you!
I'll have more time to play with it in 24 hours but for now and put it through it's paces in a mix, but for now I think it was definitely worth the upgrade from Recab 3.
I'll try and put a comparison together between it and S-Gear tomorrow night and post it.
Good work Shane, I hope this goes well for you!
MrBongo
idiot at work
reaper can´t find it.
downloaded the .exe twice, installed in various folders, re-scanned ... -.-´
win7 64
reaper 4.73 x64
recabinet 4 x64 vst for windows
gotta go, more info later
downloaded the .exe twice, installed in various folders, re-scanned ... -.-´
win7 64
reaper 4.73 x64
recabinet 4 x64 vst for windows
gotta go, more info later
My experience: The 64bit Windows installer installs by default to c:\program files (x86)\, probably not your 64bit VST path.
Quality slider (oversampling) seems to be in the top right, under the 'glowing tube' graphic thing.
CPU usage seems to be extremely high. As in, putting TS-999 in front with x4 oversampling causes my CPU to spike (3.5ghz core i7). Rendering a portion seems to pretty much lock it at '1.0x' realtime speed... can't be right?
I'm running at 96k though, maybe that is untested and buggy (wouldn't be the first time).
Throwing the 'rose of sharyn' DIs on the track and playing around, I can't seem to have the poweramp enabled _at all_. I pick _one_ cab (oversize sm 57 off axis, close, no eq). The output in the middle recabinet section is at default, the output knob of the enabled cab is at default, the input knob all the way at the top is at default.
Default amp is 'damage - clean' with it's matching power amp, all knobs at noon. Put it on the DI tracks, and reaper auto-mutes the track because it's clipping at over +16 db.
Playing around, I have to have the 'level' of the poweramp at the absolute minimum or the output knob in the middle recabinet section all the way at minimum to let the plugin produce audio that is _barely_ not clipping.
Can't be right?
Also, there are random 'sine wave' kinda sounds coming through. Flipping back and forth between the cabs gets rid of it most of the times, it's kinda random.
So, seems very very buggy so far, but that all might be because of 96k.
Quality slider (oversampling) seems to be in the top right, under the 'glowing tube' graphic thing.
CPU usage seems to be extremely high. As in, putting TS-999 in front with x4 oversampling causes my CPU to spike (3.5ghz core i7). Rendering a portion seems to pretty much lock it at '1.0x' realtime speed... can't be right?
I'm running at 96k though, maybe that is untested and buggy (wouldn't be the first time).
Throwing the 'rose of sharyn' DIs on the track and playing around, I can't seem to have the poweramp enabled _at all_. I pick _one_ cab (oversize sm 57 off axis, close, no eq). The output in the middle recabinet section is at default, the output knob of the enabled cab is at default, the input knob all the way at the top is at default.
Default amp is 'damage - clean' with it's matching power amp, all knobs at noon. Put it on the DI tracks, and reaper auto-mutes the track because it's clipping at over +16 db.
Playing around, I have to have the 'level' of the poweramp at the absolute minimum or the output knob in the middle recabinet section all the way at minimum to let the plugin produce audio that is _barely_ not clipping.
Can't be right?
Also, there are random 'sine wave' kinda sounds coming through. Flipping back and forth between the cabs gets rid of it most of the times, it's kinda random.
So, seems very very buggy so far, but that all might be because of 96k.
HOFX
Member
- Apr 12, 2012
- 469
- 0
- 16
Try and re-install the Microsoft Visual C++ redistributable - I had the same problem until I got the latest.
I managed to get 'a good session' going by switching to 44.1K and keeping the oversampling low.
Once I tried rendering out some 20 seconds it rendered at 1.5x realtime (so I'm guessing the oversampling gets maxed out during offline render) and rendered OK. But _after_ the rendering the plugin got back to it's nasty state where everything is 20 times too loud and clipping and distorting. Disabling the poweramp section seems to be the only thing to get it back to working then.
So my _guess_ is that going over a certain samplerate (be at 44.1K but with lots of oversampling or using the plugin at 96K but with less oversampling) breaks the plugin from within
.
edit: Nevermind the whole 'bounce' portion of this. My Reaper seems to jump back to 96K after bouncing a portion, so that explains why the plugin goes back to being 'wrong' after a bounce: It just doesn't work in 96K so far it seems. Working fine in 44.1K for now.
Once I tried rendering out some 20 seconds it rendered at 1.5x realtime (so I'm guessing the oversampling gets maxed out during offline render) and rendered OK. But _after_ the rendering the plugin got back to it's nasty state where everything is 20 times too loud and clipping and distorting. Disabling the poweramp section seems to be the only thing to get it back to working then.
So my _guess_ is that going over a certain samplerate (be at 44.1K but with lots of oversampling or using the plugin at 96K but with less oversampling) breaks the plugin from within
.edit: Nevermind the whole 'bounce' portion of this. My Reaper seems to jump back to 96K after bouncing a portion, so that explains why the plugin goes back to being 'wrong' after a bounce: It just doesn't work in 96K so far it seems. Working fine in 44.1K for now.
Just to say, after playing through it for a bit now, it feels really nice.
I wouldn't be surprised if some people think it doesn't sound leaps and bounds better than the best amp sims out there, but that means it at least matches them.
I wouldn't be surprised if some like the 'polished' unreal sound of some other amps for ease of mixing.
But from the first 30 minutes to an hour, this feels so more 'untamed', 'raw'.. is that what real amps sound like when mic'd up? (Only in single floor apartment so micing up my own 2x12 never sounds as good as good IRs, I tried). But (even after trying Revalver4) this somehow 'clicks' in my hands when playing through it. I can imagine that a lot of people who've played through real amps all their life think this feeling was missing.
Comparing the PsychoB to X50v2 and you notice how similar they are in tone and timbre (not unlike some other 5150-II sims) but Recab4 has some more 'growl' in it it seems. Still, me - as someone who is clearly NOT an expert - enjoyed playing through it a lot, clearly more so compared to other sims (and I don't say that often).
I wouldn't be surprised if some people think it doesn't sound leaps and bounds better than the best amp sims out there, but that means it at least matches them
.I wouldn't be surprised if some like the 'polished' unreal sound of some other amps for ease of mixing.
But from the first 30 minutes to an hour, this feels so more 'untamed', 'raw'.. is that what real amps sound like when mic'd up? (Only in single floor apartment so micing up my own 2x12 never sounds as good as good IRs, I tried
). But (even after trying Revalver4) this somehow 'clicks' in my hands when playing through it. I can imagine that a lot of people who've played through real amps all their life think this feeling was missing.Comparing the PsychoB to X50v2 and you notice how similar they are in tone and timbre (not unlike some other 5150-II sims) but Recab4 has some more 'growl' in it it seems. Still, me - as someone who is clearly NOT an expert - enjoyed playing through it a lot, clearly more so compared to other sims (and I don't say that often).
MrBongo
idiot at work
that didn´t work :/
what else do i need to make it work? (i even needed java for some plugins)
Which visual c=+ redist did you try? There are multiple .
I'm on Reaper x64 4.731 under Windows 8.1 x64 and it is detected without problems (if in the right folder).
What kind of CPU do you have? There are problems (with multiple plugins around, commercial and free) that prevents them from working (being detected even I believe) on newer CPU's (as in, Intel Haswells.. i3/i5/i7 in the 4xxx serie).
Apparently there is a bug in the most recent Windows SDK (a piece of kit software developers use to make their product) that causes plugins to not work on recent Intel CPUs, while developers got it fixed by downgrading their Windows SDK to a previous version.
_IF_ this is the problem in your case, you can do nothing until there is a fixed version of the plugin. But I have no clue if this is a) still recent and still counts b) the actual problem you have
.I'm on Reaper x64 4.731 under Windows 8.1 x64 and it is detected without problems (if in the right folder).
What kind of CPU do you have? There are problems (with multiple plugins around, commercial and free) that prevents them from working (being detected even I believe) on newer CPU's (as in, Intel Haswells.. i3/i5/i7 in the 4xxx serie).
Apparently there is a bug in the most recent Windows SDK (a piece of kit software developers use to make their product) that causes plugins to not work on recent Intel CPUs, while developers got it fixed by downgrading their Windows SDK to a previous version.
_IF_ this is the problem in your case, you can do nothing until there is a fixed version of the plugin. But I have no clue if this is a) still recent and still counts b) the actual problem you have
He's Dead, Jim
Member
After connecting to my gaming TV screen to fix the resolution issue, can firmly say this plugin is by far the best VST amp modeler I've yet used. I've never owned an Axe or Kemper so I can't compare, but the way the amp controls react and the organic dirtiness of it- in a good, realistic way- are just amazing. It's hard to judge by just hearing samples because the quality is really displayed when you actually play around with it. I'm using Jeff's Rose of Sharyn DIs and it sounds like total sex. My only real complaint is the CPU usage; I've gotten it under control to around 7% by doubling my latency from 5 to 10 ms. I know I'm on a sorta oldish laptop, but there is room for improvement there over the long term vis a vis competing modelers. But it's not too big an issue in any event. Really, really well done, and congrats on the release Shane!
edit: And add numbers to the Thermionik knobs. I know the minimalism is nice, but numbers are ideal for remembering/making/sharing presets.
double edit: I'm also now starting to get the weird beeping thing the other user mentioned, but it doesn't happen when I load the plugin as part of a Reaper preset. Seems to be something with adding the plugin to a new track. It also creates a pretty loud pop any time I do that, even when record monitoring is off. Happens when you switch amps too.
edit: And add numbers to the Thermionik knobs. I know the minimalism is nice, but numbers are ideal for remembering/making/sharing presets.
double edit: I'm also now starting to get the weird beeping thing the other user mentioned, but it doesn't happen when I load the plugin as part of a Reaper preset. Seems to be something with adding the plugin to a new track. It also creates a pretty loud pop any time I do that, even when record monitoring is off. Happens when you switch amps too.
Over at KVR, they reported issues with detecting and it being fixed by installed the visual C _2012_ runtime (or the unrecommended, hacky way of doing things, make sure you get the correct (x86/x64) version of msvcr120.dll and put it in the correct place (x86/x64).
If on 32bit windows: Get the x86 version and make sure it is in c:\windows\system32
If on 64bit windows: Get the x64 version and make sure it is in c:\windows\system32. The 32bit version would've gone into c:\windows\syswow64
But in all honesty, http://www.microsoft.com/en-us/download/details.aspx?id=30679 should do the trick.
It could also be this one: http://www.microsoft.com/en-us/download/details.aspx?id=40784
Kazrog himself can tell you more if this is actually the case, but since this is launch day he's busy. The proper way to contact him if through the Recabinet support link on the website I assume.
Is the quality slider supposed to make much of a difference in cpu usage? In pro tools there is only a slight reduction when I turn it down.
Which visual c=+ redist did you try? There are multiple
I'm on Reaper x64 4.731 under Windows 8.1 x64 and it is detected without problems (if in the right folder).
What kind of CPU do you have? There are problems (with multiple plugins around, commercial and free) that prevents them from working (being detected even I believe) on newer CPU's (as in, Intel Haswells.. i3/i5/i7 in the 4xxx serie).
Apparently there is a bug in the most recent Windows SDK (a piece of kit software developers use to make their product) that causes plugins to not work on recent Intel CPUs, while developers got it fixed by downgrading their Windows SDK to a previous version.
_IF_ this is the problem in your case, you can do nothing until there is a fixed version of the plugin. But I have no clue if this is a) still recent and still counts b) the actual problem you have
He's using an older SDK, so it's not an issue with a newer CPU. I'm one of the people with the newer CPU that was having problems with some newer plugins and Thermionik works just fine for me.
You're the one who pointed me at it
(if you are 'Dominus' over at GAM ).But ok,then it should be a question of installing the right runtime and it should work OK for the user who had issues here.
Other users over at KVR got it fixed, and if it isn't the Windows-SDK-cpu-problem, it should be fixable over at your local end.
