Thermionik Amp Modeler Plugin by Kazrog LLC

dipje said:
You're the one who pointed me at it :p (if you are 'Dominus' over at GAM :p).

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.
Click to expand...

I am, and it's X50 that's using the newer SDK, so I haven't updated X50 yet. I E-Mailed Kazrog a few times before the release warning him about the SDK. Emissary and AXP Flextron were the first plugins that I found the issues with and they worked with me to find and fix the problem. There's a few people on other forums that are upgrading computers and just now finding the issues themselves. It's not a good time to be an early adopter. Intel or Microsoft screwed up something along the way, and very few people are going to see it, and I'm one of them. :mad:

(The only common thread is a newer CPU/chipset, and a 64 bit VST compiled with the latest Microsoft SDK. The 32 bit versions would work fine.)
 
dipje said:
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 :p.

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.
Click to expand...

At 96k, you will probably need to disable oversampling in the plugin. To be fair, 96k was not tested and is considered an edge case, but I will be doing some testing in 96k down the road.
 
@Kazrog, Congrats on your launch! I haven't had some time with it yet.

Off the top of my head, I was thinking that when you said the knobs are 1:1 mapped to the amps, I was (may I add hopefully) expecting the interface to look different too, for each amp. It's just a UX thing. Nothing major; one of those "nice touch" things.
 
dominus_malas said:
I am, and it's X50 that's using the newer SDK, so I haven't updated X50 yet. I E-Mailed Kazrog a few times before the release warning him about the SDK. Emissary and AXP Flextron were the first plugins that I found the issues with and they worked with me to find and fix the problem. There's a few people on other forums that are upgrading computers and just now finding the issues themselves. It's not a good time to be an early adopter. Intel or Microsoft screwed up something along the way, and very few people are going to see it, and I'm one of them. :mad:

(The only common thread is a newer CPU/chipset, and a 64 bit VST compiled with the latest Microsoft SDK. The 32 bit versions would work fine.)
Click to expand...

I'll have to look into this now. There simply wasn't time during development. I think I am using the VC2012 SDK, though, but I'll have to double check my settings.

I'll follow up with you via email. Thanks!
 
v1gnesh said:
@Kazrog, Congrats on your launch! I haven't had some time with it yet.

Off the top of my head, I was thinking that when you said the knobs are 1:1 mapped to the amps, I was (may I add hopefully) expecting the interface to look different too, for each amp. It's just a UX thing. Nothing major; one of those "nice touch" things.
Click to expand...

Thanks!

I know, a lot of other modelers do this. With the sheer number of amps that will be added over the course of the next year alone, it's ridiculously impractical to have different UI designs for each amp. The focus is the sound, not the graphics, although I did put a lot of time into making the one UI design look nice.
 
Kazrog said:
Thanks!

I know, a lot of other modelers do this. With the sheer number of amps that will be added over the course of the next year alone, it's ridiculously impractical to have different UI designs for each amp. The focus is the sound, not the graphics, although I did put a lot of time into making the one UI design look nice.
Click to expand...

I may be completely wrong... A kickass software with great presentation is bound to sell and keep you happy :)
 
installed the Visual Studio 2013 (claimed to be the latest visual c++ thingy), and dotnet 4.5 .
still doesn´t appear :(


i5-2400, and if it matters in any way, a GF 610 gpu.
 
Great tones and playing!!! I'm loving the rawness and immediacy of this.
Click to expand...

Thanks Shane, I'm glad you liked it.

The thing here is that I've been using the same IR with the previous modeller
and when I put Thermionik on, I disabled about 6 plugins that I was using
trying achieve the sound that Thermionik has as standard.


You came up with a really unique piece of software and just by
disabling the power amp you can tell what a huge difference it makes to the
sound.
 
akarawd said:
Thanks Shane, I'm glad you liked it.

The thing here is that I've been using the same IR with the previous modeller
and when I put Thermionik on, I disabled about 6 plugins that I was using
trying achieve the sound that Thermionik has as standard.


You came up with a really unique piece of software and just by
disabling the power amp you can tell what a huge difference it makes to the
sound.
Click to expand...

That's exactly how I shape guitar sounds. Multiple plugins, using bits and pieces from different manufacturers. I'm really happy with the way Thermionik fit right into my workflow, and I literally only had 5 minutes to play with it.
 
Kazrog said:
I'll have to look into this now. There simply wasn't time during development. I think I am using the VC2012 SDK, though, but I'll have to double check my settings.

I'll follow up with you via email. Thanks!
Click to expand...

Yup, you were using the old one, x64 works fine for me. If you want to put together an x64 build with the 2013 SDK and send it to me, I can confirm that it's broken.

That and we can work out some scheduling for you to model my amps. Thermionik sounds good enough for me to sell my amps off after they're modeled. :devil:
 
i have no idea why ... and i´m really sorry for causing any trouble in here ... but:

after installing all the shit like 5 or 6 times, including vc++ 2012 and even 2013, it finally started working.

:kickass:
 
@Kazrog: It seems really 'broken' in 96k. No stutters or cpu-hangs or stuff like that, but >20x the volume + distortion, beeping, buzzing that all change pitch when flicking random switches. Seems like a bug than cpu power to be honest (or the plugin looses 'sync' somewhere or something? Don't know how your stuff works - don't wanna know :p).

@Dominus: Early adopters like the latest updates of software stuff? Or early adopters for hardware? Cause Intel's haswell line has been out since november last year or something, wouldn't call that an early adopter. Any ready-made PC bought in the last year probably has a chip like that, and it's the go-to cpu line for homemade-builds (or you go AMD)... But in the audio world people are... how to say it nicely... 'slow' to catch up in the tech world :).
Just wanna state that if the problem is really latest Windows SDK + Intel 4xxx line (or even the 3xxx with it), I would blame Microsoft, cause the intel chip design has been around for almost a year and is considered 'mainstream'.
I think it's insane a bug like that can creep up into the Windows SDK or compiler suite and there is no clear statement from MS about it (I couldn't find it for what it's worth).
 
@MrBongo: the Visual Studio C++ redistributables (or Microsoft runtimes or how you would call them) are _not_ all inclusive. So installing 2013 does not automatically install 2012 or 2010 :). (DotNet kinda the same, installing 1.0 is not the same as 2.0.. from from 2.0 to 3.5 to 4.5 they _arE_ inclusive. Really confusing stuff, and mostly this is why they are included in the installers for software, cause it's too much work and understanding for regular users to know this stuff. I guess Kazrog had his mind on different things this weekend :p).

4.0.0 from Recabinet needs the 2012 one (there seems to be only one installer for x86 or x64 for this, so just the microsoft link for 'visual c++ redistributable 2012 update 4'. Installing the separate DLL's may work, but it's really not recommended
 
@Kazrog: Reported the 'level' control in the poweramp section still working even though poweramp section is bypassed. Once again her for good meassure :p.

You can add to it: The treble control still working even when the preamp section is bypassed :p. Was trying to try Studio Devil amp-modeler preamp only jcm-style stuff into your Serpent-poweramp + IR. Got weird results because the treble was still cranked in your bypassed preamp :p.
 
You must log in or register to reply here.

Similar threads

Kazrog
New Kazrog/Thermionik amp and pedal emulations
Replies
17
Views
4K
Backline
guy in latvia
G
guitarjon
Thermionik review and demo (in 9 styles)
Replies
9
Views
4K
Backline
nezvers
nezvers
Dans
Does any 'Amp Modeler + Plug-in' Hybrid Digital Solution Exist?
Replies
1
Views
715
Backline
deLuther
deLuther
Ericlingus
What do you use for your go to guitar sound?
Replies
24
Views
3K
Backline
texisthebest
T
X
Recabinet 5 (originally 4.1) released
Replies
60
Views
13K
Backline
Artean
Artean
Top Bottom
Back