TAL-U-NO-LX. Uber accurate Juno 60 emulation.

[DuX]

The thing is, Astral, VST standard is complicated and sometimes it doesn't work as expected. The issue could be with a plugin or with the DAW itself, both. However, it usually is with the plugin not conforming to VST2 standards, so it's best to ask the developer first about it.

Having Cubase and Reaper, both, is in my view a pretty good setup. However, I'm a former Cubase user [since 1992, I think], and a Reaper fanboy since 2008 so I might not be the most unbiased source of info. My clients mostly use Cubase, Pro-Fools, and Reaper, though.

However, Reaper developers take care of such issues quite promptly, unlike Steinberg, and that's what I really like about Reaper.

P.S. and what chk071 said, yes! delete every other instance of U-NO plugin and rescan with Cubase. Go to "plugin preferences" and rescan. Restart it and see if it works. It should.

[AstralExistence]

didn't work. it wont replace v1 with v2. all it sees is v1. from what your telling me, it seems reaper simple replaces v1 with v2. the reason i dont understand this problem is ive never encountered it before in other daws. i can manually replace it though. but that doesn't solve the compatibility problem.

[chk071]

didn't work. it wont replace v1 with v2. all it sees is v1. from what your telling me, it seems reaper simple replaces v1 with v2. the reason i dont understand this problem is ive never encountered it before in other daws.

So, as far as i understood, v1 and v2 dll's have a different name, and you have both installed? (Really hard to figure out, please post if you have both installed or not...) Then it is the plugin programmers job to solve the issue.

Edit: Btw, if you delete both the vstpluginlist.xml (i think it is called like that) and the vstblacklist.xml, it should erase all the plugin information, reload it, create both files new, so it is virtually impossible that it still sees your v1 if you don't have it installed anymore.

[AstralExistence]

didn't work. it wont replace v1 with v2. all it sees is v1. from what your telling me, it seems reaper simple replaces v1 with v2. the reason i dont understand this problem is ive never encountered it before in other daws.

So, as far as i understood, v1 and v2 dll's have a different name, and you have both installed? (Really hard to figure out, please post if you have both installed or not...) Then it is the plugin programmers job to solve the issue.

Edit: Btw, if you delete both the vstpluginlist.xml (i think it is called like that) and the vstblacklist.xml, it should erase all the plugin information, reload it, create both files new, so it is virtually impossible that it still sees your v1 if you don't have it installed anymore.

ok, maybe im not clear, i only have v2 installed, before i installed v2, i had v1, i wrote my projects with v1, v2 is released, i completely uninstall v1, then install v2, after installing v2, i open my old songs that used v1, assuming that i could simple remove v1, install v2, and cubase would recognize v1 as an updated v2, it does not, it gives a message that all tracks using v1 cant find tal v1, because cubase cant find v1, all tracks go silent, due to having no v1 plugin.

after doing what was recommended, old v1 projects cant find v1, which i assume other daws simply update v1 plug with v2, and compatibility works. that seems to be the issue. cubase doesn't automatically replace v1 with v2 dll. and thus since cubase cant replace it automatically, old v1 projects go silent. its possible to manualy replace v1, dll/patches with v2, and load old v1 patches, i just assumed, and it seems that most daws do this automatically.

[braj]

I have both V1 and V2 installed after updating in Reaper Win64.

[Ingonator]

I have both V1 and V2 installed after updating in Reaper Win64.

Same here in Ableton Live 8.3.4 (on Windoows 7 32-bit). V2 also recognized my presets for V1 so it seems to use the same presets folder.
So the best solution to keep compatible with V1 is installing both. This way it is also more easy to check the differences of both plugin versions.

UPDATE:
From the official announcement of V2:
http://www.kvraudio.com/news/togu-audio ... rice-20103

"This new version includes an improved filter that is more accurate and warmer, especially at extreme values with a lot resonance. Old presets are compatible with this version. Version 2.0 can run parallel to the old plugin. The chorus was calibrated too. This version includes some more non-linear components and needs a bit more CPU."

So the observed "problem" is not a bug, it's a feature...


Ingo

[chk071]

ok, maybe im not clear, i only have v2 installed, before i installed v2, i had v1, i wrote my projects with v1, v2 is released, i completely uninstall v1, then install v2, after installing v2, i open my old songs that used v1, assuming that i could simple remove v1, install v2, and cubase would recognize v1 as an updated v2, it does not, it gives a message that all tracks using v1 cant find tal v1, because cubase cant find v1, all tracks go silent, due to having no v1 plugin.

after doing what was recommended, old v1 projects cant find v1, which i assume other daws simply update v1 plug with v2, and compatibility works. that seems to be the issue. cubase doesn't automatically replace v1 with v2 dll. and thus since cubase cant replace it automatically, old v1 projects go silent. its possible to manualy replace v1, dll/patches with v2, and load old v1 patches, i just assumed, and it seems that most daws do this automatically.

Ok, got it now. Nothing wrong on your side then, that's for sure. I could only think of that Cubase might have saved some other plugin configuration files then somewhere which causes it to think it is still the v1 one.

[Captain]

I just installed v2 AU on my Mac, and noticed a strange problem: start Logic, open a new project, and open an instance of v1. Works fine. However, if I then open v2 on another track, its GUI is missing, and I only get generic sliders (I think it's some standard AU interface). It also works the other way - whichever version opens first, "steals" the GUI, and doesn't let the other use it. Restarting Logic resets the situation.

Maybe the two versions share some resources? This isn't big problem since I didn't plan to use both versions in the same project, but it's curious anyway. (OS X 10.6.8 & Logic 9.1.7)

[baconpriest]

Had the same problem, in Live. Tried to open both, just to compare, but V1 one wouldn't show the gui at all.
As you say, though, not really a serious problem.

[waltercruz]

Had the same problem, in Live.

Had the same problem in Live, Mac OS X.

[Ingonator]

Had the same problem, in Live.

Had the same problem in Live, Mac OS X.

No problem in Live and Windows 7 32-bit. I just left the installation of V1 like it is and then installed V2.


Ingo

[electro]

Hard to believe there is an improved version. Version 1.x was already incredibly close to the real thing.

[Sendy]

I'm liking the new resonance sound.

[fluffy_little_something]

Oops, deleted, I didn't read the previous posts as I had not gotten any new post notification for this thread in days, odd

Anyway, great to see that it is still being improved, not a closed project

[lionscub68]

I'm gonna wait 'til the dust settles. When you guys show a solid version here, I'll jump up to v2.