Hi Seth,

I'm sincerely curious... is the native support leveraging FXpansion licensed technology? Similar in fashion to the way Radius algorithms are built in to AudioSnap?


best regards,
mike

mike_mccue


Hi Seth,

I'm sincerely curious... is the native support leveraging FXpansion licensed technology? Similar in fashion to the way Radius algorithms are built in to AudioSnap?


best regards,
mike

No, because their technology was a wrapper. We don't wrap DX plugins to VST plugins anymore. Its all native now, written in via the VST spec.

Seth Perlstein [Cakewalk
]

No, VST support has not changed in X1. It's been the same since it became native way back in SONAR 4 or SONAR 5 (2004 or 2005).

From then through 8.5 the VST Settings was in one of the Options menus, still within the App. That Option menu simply moved to the new Unified Preferences menu in X1. The menu itself stayed the same as did its functionality.

When I said I wonder if you have an older version of SONAR installed and are using the old wrapper, I mean WAY older, like SONAR 2 or 3.

Once we made VST native to SONAR in 4 or 5 there was no reason to use the wrapper and all of the VST settings, file locations, etc. were done inside SONAR. This is still true today in X1.

Right now I have 8 and 8.5 on my machines. Both have a separate app and what seems to be a separate app that opens in Sonar. At least through 8.5 VST choosing folders and scanning is dealt with differently than other apps in what seems to be a separate app. Why does it seem that way if it is indeed native?

10Ten

Seth Perlstein [Cakewalk
]

No, VST support has not changed in X1. It's been the same since it became native way back in SONAR 4 or SONAR 5 (2004 or 2005).

From then through 8.5 the VST Settings was in one of the Options menus, still within the App. That Option menu simply moved to the new Unified Preferences menu in X1. The menu itself stayed the same as did its functionality.

When I said I wonder if you have an older version of SONAR installed and are using the old wrapper, I mean WAY older, like SONAR 2 or 3.

Once we made VST native to SONAR in 4 or 5 there was no reason to use the wrapper and all of the VST settings, file locations, etc. were done inside SONAR. This is still true today in X1.

  It looks like he same old Cakewalk Plugin Manager we got with 4 or 5 to me. How is it not that?

Now we're talking about two separate things. The Plugin Manager and the VST Setting page in Preferences are two separate things, although you can scan for VST plugins in both.

Also, the Plugin Manager is not a separate app but a feature of SONAR that is accessed within the app.

However, the plugin manager is primarily designed as the window for creating and managing plugin layouts, importing and exporting plugin presets, and showing or excluding certain plugins from SONAR.

As an ease of use addition you can scan VST plugins and access the scan path directories from this window, but that is not its primary function.

Additionally, the Plugin Manager can be floated like many other windows in SONAR, but it still is only accessible from within SONAR as it is a part of SONAR and is not an outside application.

Having said all that, the Plugin Manager has nothing to do with native VST support in SONAR since the Plugin Manager can deal with DX, DXi, VST, and VSTi at the same time.

With or without the Plugin Manager, SONAR has native VST support.

With or without the Plugin Manager, SONAR has native VST support.

Indeed, every other VST capable app. has to scan the VST's that are available to it in order to maintain current details of those plugins.

Sonar like Soundforge for example have separate scanners with others it is integrated into the app. itself but the scanning still needs to be carried out on a designated folder (or folders), most apps. too you can elect to scan at every boot time in exactly the same way as Sonar or choose to do it manually to suit.

Sonar has certainly been VST compliant since I joined the fold since V7

The plugin manager is a separate app. Its an EXE file in the Sonar shared utilities directory. It is not the native support for VST. It is a manager for all plugins. Even Cubase has a plugin manager. It can invoke a scan for VSTs but it itself in not the scanner nor is it offer native support. It simply manages plugins. And it has been improved in X1.

TomFerraro


This is how a lot software companys solicite input, and build loyalty. 

This is a great idea, and one that I'm sure many who participate in this user community would appreciate, having for cake.

It would be interestig to see how many of the suggestions get implemented per release, it's probally less then you'd expect.

Which brings up the question, if only 4 or 5 feature suggestions out of hundreds get implemented how will the community handle that?

Also this is quite an undertaking to put into place and maintain, will that diversion pay off, will it make us more loyal, will it make a bertter cake?  I think so.

I work for a company called National Instruments (NI), not Native Instruments ;-)  We have a graphical programming lauguage we develop and sell called LabVIEW. 
 
We do have one of these suggestions boards, and it's worked rather well for us.
http://forums.ni.com/t5/LabVIEW-Idea-Exchange/idb-p/labviewideas

Peace all

Tom

Hey Tom,
 
You get to be involved w/any of the FLL NXT sponsorship stuff by NI...My daughter just did her 1st. yr. in the FLL NXT competition & it was great.  Pass the word that NI's participation is well received.
 
have a good one
3Eo