Window size as VST plug in Sonar

This has to be a problem with a simple solution or I imagine there would be a lot more complaints. I've installed the patches on both the Reaktor and Sonar side, and still:

When I add Reaktor 4 as a VST plugin in Sonar 3.1.1 and open the window, there is a window within the window that cannot be resized. Therefore the instrument panel within cannot be seen in full - and there aren't even scrollbars. I can sometimes shift the panel over enough to get the job done, but usually I'm looking at half of Reaktor, and the situation is basically hopeless. Any recommendations? I'm at wit's end.

Thanks.

 

Two obvious solutions;
1)Rescan with the adapter and change the default GUI settings in Reaktor's properties in the adapter (the first screen that comes up after the scan)
2)use the DXi version
ew

 

Thanks ewistrand. I would definitely prefer to use DXi if possible (presumably more efficient) but I didn't notice it in the plugin menu. I might have missed a step in my initial Reaktor setup. I'll check that out tonight, and failing that I'll look more closely at the VST registration for UI options.

 

The DXi version's the real answer- using that and Sonar's echo DXi to armed MIDI track(s) function, you can automate by moving Reaktor's
knobs, record Reaktor's sequencers for use with other instruments and the like.
If you didn't install the DXi version to begin with, just run the latest update and choose to install only the DXt plugin.
ew

 

sonar has a vst adapter that converts VST to dxi. you may have it already or, you may have to buy it from cakewalk. check your sonar files under program files.

run it for reaktor if you have it . you should have no problems after that. it is very straight forward.

reaktor will appear in both the vst & dxi menus.

 

He's aware of this; the Cakewalk adapter's what's giving him the trouble as he stated in the original post. The adapter does do funky things with Reaktor unless you expand the window in the properties; I've run into it using the VST version in my older version of SoundForge (I have to use the VST version, because the DX version's registered as a DX synth and not a DX effect).
ew

 

actually, he implied that he opened the plugin w/in sonar and had problems.

if that is the case he needs to run the adapter again. it runs fine as a vst or a dxi in sonar if installed correctly.

he didn't say that he used the new vst/dxi adapter to reinstall & have sonar recognize it as a dxi.

i made a constructive suggestion. you assumed he ran the new vst/dxi adapter to try and resolve the problem.

you are a moderator - try to be moderately pleasant in your responses.

darc - try running the adapter again - install it as a vst & a dxi. both vst & dxi reaktor run fine and are scalable for me.

good luck & good music to both of you.

 

Baldo, I don't think ewi meant to be unpleasant, I think it's just a side-effect of brevity. If it de-ruffles any feathers, I appreciate the help from both of you.

As it happens I was aware of the VST wrapper. (It is actually included by default in Sonar 3, and I installed the VST wrapper patch last night hoping that that might improve matters.) But I've been plowing through the VST plugin registration with all defaults, not considering that there might be something to remedy my problem there.

And all of that said, I will steer clear of VST altogether in this instance if I can. I thought I remembered using Reaktor as true DXi way back when, but when it didn't jump right out at me I assumed I was remembering another plugin.

Thanks, all!

 

i hope the reaktor dxi works for you.

i've had a couple of failed installs with the vst/dxi wrapper - that's why i suggested the reinstall.

sorry i couldn't be more helpful.

i have a question for you or for ewistrand - is there supposed to be any advantage using a vst vs dxi version of reaktor (or any softsynth) in sonar?

have you been using reaktor in sonar for awhile?

NI's other ssynths have really been a plus for me.

no feathers ruffled here but, thx for the comments. i'm kinda' like a duck - most stuff washes off my back.

hope the dxi works as expected for you.

good luck & great music.

 

The main advantage of using the true DXi versus the wrapped version is the DXi2 implementation, which allows you to use the GUI's knobs to record automation and be able to record MIDI out ebvents from the plugin without resorting to loopback devices such as Hubi's or MIDIYoke.
I've been using them together for almost four years- the first version of Sonar and Reaktor 3 (the first DXi version). Sonar 2 brought DXi2 implementation to the ballgame, and Reaktor 4 was the first native (non-wrapped) DXi that NI released- the rest had wrappers as part of the internal code.
No feathers ruffled here either, so everybodt have a good night.
ew

 

thx 4 the explanation ewistrand - any advantage of vst over dxi?

 

reaktor fx

I am having a related problem with reaktor in sonar 3. The reaktor fx as opposed to reaktor itself is not available in dxi so i must use vsti when using reaktor as an audio effect. I am experiencing the same problem with the window cutting off half of reaktor when i open the project. I will try to adjust the reaktor window in properties and see what happens.

jim

 

I have figured out a work around. If you close and re-open the reaktor fx window several times you get the scroll bar reappear and you can access the entire window.

jim

 

Baldo, to my knowledge there is no *technical* benefit to using VST over DXi. In Sonar in particular DXi should be superior because it is the technology that is native to the host - so the automation interfaces are more robust, and one less layer of software is loaded into memory and eating up CPU cycles. The *practical* benefit of VST is that it is much more established and universal between platforms, so there are far more plugins available in the VST format. This is why Cakewalk made the VST wrapper available for Sonar users in the first place.

So anyway, last night I tested Reaktor DXi noting that I missed it because it was tucked away with the synths and I was trying to route an effect. I'm not sure whether you can simply select the DXi synth and then change its input to use it as an effect (happened to test a synth last night) but I'm hoping so. Otherwise, bummer.

DXi improves matters - the window assumes the correct size when an ensemble is loaded - but its still not 100%. It has a tacked on "window in a window" feel; the window within does not resize dynamically with the window without. You definitely would not want to be developing new ensembles inside a plugin instance.

But this should be sufficient to get me limping along again. Thanks again!

 

darc - have you had any problems loading any ensembles from the user library into sonar? i tried to load one yesterday and the gui was not there.

is there a trick to loading some ensembles in sonar?

 

You don't have to change anything on the DX plug- just insert it as an effect in the fx bin where you want it to be.
Any DX plugin that allows MIDI control (even tempo) is classified as a DX synth; that's why there's no separate DX listing for ReaktorFX.
baldo- try right clicking in the space where the GUI soulld be and choose show panel...
ew

 

ew - that did the trick - thx a ton.

you have nice website. what do you use to do the fractal pics?

a suggestion to darc - have you tried going to 'menu' then 'view' in the reaktor dxi and choosing 'auto optimize window size'? it worked for me when i had that problem.

thx again to both of you.

 

Thanks, I'm glad you like it.
My main one these days is UltraFractal- it's around $50, and worth every penny
www.ultrafractal.com
I'm also a fan of Stephen Ferguson's Sterling; I can't remember the URL right off hand, but the link to it's on my web page.
ew

 

ew - thx. my son is more into graphics. he is a big fan of digital blasphemy site. i will check out the sites.

one more question for you - & again thx for the time u take on these.

when i opened the ensemble and had the gui - the controls would not work - it wa as though i was building the ensemble gui. ie: there was no functionality to the control surface. is this what you werediscussing earlier.

can i do something to make the control surface active? do i have to make the adjustment in stand alone reaktor & then use the dxi in sonar?

 

That's weird... which ensembles are giving you this problem?
To record your control movements as automation, you'll have to use MIDI learn and activate MIDI in in the control's properties.
If you aren't automating, everything should work- you just can't record the changes.
ew