XILS Roland Vocoder VP-330 Plus - NEW SYNTH

[electro]

Because it's a pre-release version ? Just a guess ...

You should never have two different revisions with the same Version #.

[dusted william]

Because it's a pre-release version ? Just a guess ...

You should never have two different revisions with the same Version #.

agreed.

dw

[sqigls]

not sure if anyone's picked this up... in Cubase, in the effects plugin list there is a VST3 version called "kInstrument - XILS V+"

[Alex Cremers]

Yesterday I played with the demo, sound is impressive, the looks are gorgeous, but it's probably the most CPU hungry VSTI that I've ever encountered.



Alex

[paulbreeze]

You should never have two different revisions with the same Version #.

Yeah, it's a bit problematic. From a coders POV, why not; but introduce the build number as a forth number...

[paulbreeze]

but it's probably the most CPU hungry VSTI that I've ever encountered.

And you also tried LuSH101, Diva, ... ?

[Crackbaby]

When you say CPU hungry, what is your unison at?

[vic_france]

not sure if anyone's picked this up... in Cubase, in the effects plugin list there is a VST3 version called "kInstrument - XILS V+"

Yes, I noticed this (only happens if you had first installed version 1.0.0.. it's a "left-over" , it is the VST3 plugins cache in Cubase that causes this.)
The "sledgehammer" fix would be to trash Cubase Preferences (or, at least, the file mentioned below), but if you don't mind "rolling up your sleeves" as regards editing .xml files in there, open the file "Cubase Module Cache.xml", and delete the paragraphs that contain "V+".
When you relaunch Cubase, the VST3 versions will have the correct name.. but be aware that the FX version is now found inside the "Other" plugins category subfolder.

[aMUSEd]

not sure if anyone's picked this up... in Cubase, in the effects plugin list there is a VST3 version called "kInstrument - XILS V+"

Yes, I noticed this (only happens if you had first installed version 1.0.0.. it's a "left-over" , it is the VST3 plugins cache in Cubase that causes this.)
The "sledgehammer" fix would be to trash Cubase Preferences (or, at least, the file mentioned below), but if you don't mind "rolling up your sleeves" as regards editing .xml files in there, open the file "Cubase Module Cache.xml", and delete the paragraphs that contain "V+".
When you relaunch Cubase, the VST3 versions will have the correct name.. but be aware that the FX version is now found inside the "Other" plugins category subfolder.

Simpler method - locate your VST3 folder and move out the XILSV plugin, open Cubase and allow it to scan for plugins. Then close it, move the plugin back, reopen Cubase and scan again.

[xavier]

Hi

I'm currently doing some tutorial videos explaining how to use the XILS V+ vocoder (including Sidechain) on various music application.

For the moment, Protools (using AAX), Cubase (using VST3), Reaper (using VST24) and LIVE (AU) are done. I plan to also do Logic (using AU), DP and some other a little later (feel free to post your wishes)

Here are the firsts (sorry if there are some English clumsy sentences or misspellings, it was done quite quickly ).

In these tutorials, I'm using two audio contents to also explain how to feed the XILS V+ with external synth.
As I also want to use these contents for the Vocoder modulator, the result is obviously not very good (using a audio content as a carrier can't produce good vocoding results), anyway it was not the purpose !

Protools (AAX plug-in)





Cubase (VST3 plug-in)




Reaper (VST2.4 plug-in)




Ableton LIVE (AudioUnit or VST2.4 plug-in)





Best regards
Xavier

[xavier]

Thanks Vic and aMUSEd,

Yes, on the V1.0.1 version, I fixed this typo (kInstruments instead of Intruments) in the VST3 plug-in.

So Cubase needs a rescan

The 1.0.1 won't change any more, I'm now working on the 1.0.2 !


Best
Xavier

[sqigls]

not sure if anyone's picked this up... in Cubase, in the effects plugin list there is a VST3 version called "kInstrument - XILS V+"

Yes, I noticed this (only happens if you had first installed version 1.0.0.. it's a "left-over" , it is the VST3 plugins cache in Cubase that causes this.)
The "sledgehammer" fix would be to trash Cubase Preferences (or, at least, the file mentioned below), but if you don't mind "rolling up your sleeves" as regards editing .xml files in there, open the file "Cubase Module Cache.xml", and delete the paragraphs that contain "V+".
When you relaunch Cubase, the VST3 versions will have the correct name.. but be aware that the FX version is now found inside the "Other" plugins category subfolder.

I've tried a few things to no avail, do you know where the blacklist and other files are located on OS X??

[vic_france]

I've tried a few things to no avail, do you know where the blacklist and other files are located on OS X??

If the problem is with the VST3 version, then there is no blacklist as such (the blacklists are only for VST2.x)
The file you need to delete/edit for VST3 is the one I mentioned.. Cubase Module Cache.xml.
It is inside the Cubase 7 (I presume?) Preferences folder, which in turn is inside your User account/Library/Preferences folder.
If your User account Library folder is not visible (i.e. on OSX 10.7 and later), you can get it to show by one of the following methods..

Hold the Option key while clicking the Go menu in the Finder to see the User Library item in the menu, or paste the following command into the Terminal to make it become permanently visible again:

chflags nohidden ~/Library

You'll also find the VST2.x cache and blacklist files there.

Anyways, the fix I described does work.. I used it myself .

Btw, just to be clear.. you have updated XILS V+ to v1.0.1? (v1.0.0 will always come up with that strange VST3 name)

[KBSoundSmith]

Hmm so after all this i myself am unable in any scenario to use the vocoder with an external carrier.

After i thought pages ago i had it, i today settled to compare all vocoders (TBH to see whether i wanted to buy this, as the strings are after all that, covered for me well and truly by loomer.. this sounds great but it's *very* european sounding.. we call that woggy in australia (and yes i am a greek myself) but i don't think they'll fit my music.)

So it comes down to the vocoder.. and...i can't test it.. in the front line : Waves Morphoder, Logic Evoc20, Antares Articulator, Orange Vocoder V3 - Carrier - Fab Filter Twin 2 lush pad.

All are working.. so far they are all on par.. they sound completely different to eachother but all are clearly intelligible.. so i really want to see if Xils can add something to that table. I know it can with it's own internal synth of course, but i still want to see how it vocodes using an internal carrier. I need help setting up, please.

The vocal is a stereo audio file (yes i know, stereo is stupid but for some reason all sample houses provide stereo vocals), and twin is on an instrument track in logic playing a 3 note pad sequence in key with the vocal, looping every 4 bars. I have outputed it to a bus in case it needs to be sidechained, as instruments can be sidechained into anything via busses in logic

but i can't get it to work.

Also i guess my patches question was overlooked.. wanted to know if that's it and covers the whole "synth" or if there is much more that can be gotten out of it.

I am having crazy problems with polyphony and i am only using a qwerty keyboard! doing a 3 note chord progression on almost any long attack patch causes cutting very fast

have you tried...
http://www.meldaproduction.com/plugins/ ... d=MVocoder
?

Thanks for this suggestion, seems to be what I was looking for. You have to treat it as an off-line process, CPU hit can be unforgiving, but if you spend the time to dig deep and tweak, you can really get the sound you want.

[Notron User]

Nope i can't even get the vocoder to work the normal way..

plug xils 5 as an "au effect instrument" on an instrument track.. sidechain vocal into it.. none of the vocoder presets do anything.. you can see the keys being pressed though.. this is going on days now and i am pretty frustrated.

I have never even needed a manual for any of the other vocoders.. they just work!

So, did you get it working yet?

Plug xils v+ into the external carrier's track
sidechain vocal into it
turn on a red vocoder switch (upper or lower)
trip the side chain selector switch down to synth:Input, Mic: side
and turn up ext synth slider by mix/ext int to taste.

It works on both audio and instrument tracks for me.