KVR Audio

Cordelia · Post by **Cordelia** » Fri Jun 20, 2008 11:25 pm

Agitator wrote:
Cordelia wrote:
Agitator wrote:i think this way of copy protection is ok, because if i want to use the UVI-W, i also want to use/buy additional soundsets. i don't have iLok at the moment, but i will get it soon and i think it is a good, safe and professional way of copy protection and many big devs, like Waves or Nomad Factory, use it!
Go for it. Have fun. If the Big Devs use it, then it must be good.
this is not what i mean, but if i don't want pace on my computer, i don't install software which use it!

nobody forces the users to download, install und use UVI-W!

right or wrong?

Right. Exactly. We have a choice. Which is why, before I downloaded 500 MBs of "free" software, I would have liked to have been informed that the "free" software will install Pace drivers on my computer.

I do think it is dishonest to describe the UVI Worstation as having "copy protection- none" when the installer will load Pace drivers into your system, not to protect the software, which is "free", but to protect sound sets that you may or may not purchase in the future.

Whatever, this thing appears to be pretty buggy anyway. More UVI engine fun.

otristan · Post by **otristan** » Fri Jun 20, 2008 11:28 pm

1-2-Many wrote: And too if you add the internet snoop thing (RSS feed).

Just a comment on this before sleeping

This is just an RSS feed, nothing more, nothing less.
There is no data send to our website about you, your computer or anything else. Those are just informations from our website to your computer and absolutely not the other way.
I'm very strict regarding privacy issue and dislike a lot big corporation watching consumer habits, so be assure I will never let this kind of things happens.

shogger · Post by **shogger** » Fri Jun 20, 2008 11:33 pm

otristan wrote:Regarding the crash, are you using a recent downloaded version ?
We have an issue on VST PC version which leaded to automatic crash.
Please try downloading the latest version.

It is a good idea to name new versions as being new versions.

Shogger

P.S. works here now and I just had a crash switching sample rate in Reaper.

b-real · Post by **b-real** » Fri Jun 20, 2008 11:46 pm

Looks nice but works like crap

shogger · Post by **shogger** » Fri Jun 20, 2008 11:49 pm

Oh no,

your internal beta test seems to have been very sparse. Good beta testers would have told you that copying a track doesn't copy any uvi ws settings.
And they would have tried to save and reload a song to find out that the formerly saved multi programs aren't loaded when loading the song.

Shogger

P.S. There might be a trick but your browser doesn't seem to sort the content of the HD partitions in any way. Simply unusable.

Gothboy · Post by **Gothboy** » Sat Jun 21, 2008 12:26 am

[quote="otristan]Regarding the crash, are you using a recent downloaded version?[/quote]

I downloaded the UVI Workstation beta the day before yesterday. Has it been updated since?

topaz · Post by **topaz** » Sat Jun 21, 2008 12:34 am

a great example of why having in house, trusted beta testers works.

sure release an RC a week or so before but to release at this stage,

seems like a nice idea backfired.

1-2-Many · Post by **1-2-Many** » Sat Jun 21, 2008 12:39 am

shogger wrote:Oh no,

your internal beta test seems to have been very sparse. Good beta testers would have told you that copying a track doesn't copy any uvi ws settings.
And they would have tried to save and reload a song to find out that the formerly saved multi programs aren't loaded when loading the song.

Shogger

P.S. There might be a trick but your browser doesn't seem to sort the content of the HD partitions in any way. Simply unusable.

I was going to suggest earlier, when seemingly simple things started popping up, that they flog their internal testers.

It did turn out that the major PC VST issue was a corrupted dll in the download. However, there have been quite a few other things arise, like those you point out, which make me wonder if those 'testers' have been kicked in the shins yet, and how hard.

topaz · Post by **topaz** » Sat Jun 21, 2008 12:46 am

no time to read the whole thread, where does it say they used a decent internal beta team ?

shogger wrote:Oh no,

your internal beta test seems to have been very sparse. Good beta testers would have told you that copying a track doesn't copy any uvi ws settings.
And they would have tried to save and reload a song to find out that the formerly saved multi programs aren't loaded when loading the song.

Shogger

P.S. There might be a trick but your browser doesn't seem to sort the content of the HD partitions in any way. Simply unusable.

JavaJ · Post by **JavaJ** » Sat Jun 21, 2008 1:01 am

so do we have to constantly go to the website and check for updates? Couldn't you put a check for updates button on the interface that makes way more sense.

1-2-Many · Post by **1-2-Many** » Sat Jun 21, 2008 1:02 am

topaz wrote:no time to read the whole thread, where does it say they used a decent internal beta team ?

Page 4 ...

otristan wrote:
MacQ wrote: ....Usually when a "public beta" is announced, that's after the "internal beta". But then, what do I know?
...Regarding the internal beta, there was a pretty one.
The VST PC issue should be a stupid thing and will be fixed as soon as possible (hopefully today)

So I guess she was a hot leggy blonde with ample breasts

topaz · Post by **topaz** » Sat Jun 21, 2008 1:07 am

so it isn't really stated there was a "team" as such.

Bass108 · Post by **Bass108** » Sat Jun 21, 2008 1:16 am

Regarding automation, unfortunately, you can't have in most host dynamic automation list and given that you can have an undefined number of parts, you can't list at the plugin launching the number of automation.
Still, We assign by default for each part the MIDI CC 7, 10 and 11 for pan, volume and expression.(MIDI Standard CC), so you should have control on those very easily in most host.
So there is no quick fix regarding this issue.

I can understand that, but maybe you can look for ideas like NI's battery where it is possible to assign parameters to midi cc's that will come up in the automation window. The only way for me to get things done in plugsound is to create a seperate instrument in the environment and have it send midi cc's to a parameter I right click and assign. If you start to multiply the amount of automation it can get confusing where everything is because all that I immediately see are cc values. Please keep in mind that this is a limitation at least for logic users of a very powerful sampler. If you can just give us the 128 cc's to come up in the automation pane and then have some kinda window where I can see what is being assigned to what then I would have no complaints.

Regarding Mute/Solo, I'm not a huge fan of the dragging behaviour as it may lead to weird results if you're not used to this kind of behaviour, which is afaik no very common. Feel free to give example where it's used.
Regarding responsivness, I think it depends on your host latency.
We apply a lowpass filter on incomming MIDI CC, but it's more to avoid zipper noise and it should still let you have a very quick modification rate.

this is something I am not too particular about. i was just suggesting to mimic the mute and solos track behavior in logic and I'm pretty sure dp too. but i'm all for clicking as opposed to weird behavior...but I have never experienced anything weird before with dragging.

and i guess i don't mind clicking two buttons for patches. the window not collapsing is sooooo helpful.

thanks

~jay

spidermix · Post by **spidermix** » Sat Jun 21, 2008 1:22 am

You guys sound like a bunch of bitchy old women.

Goodness gracious. Bitching hoes. Anyway, yeah...it was a little bit embarrassing that the UVI plugin crashed like it did, but it didn't cost your ass anything other than the time it took to download and run the thing. I don't know about you, but I'd rather have these issues ironed out BEFORE I pay my hard earned cash for it.

I've had issues with UVI, some that we still have to work out...but I'm glad that they are back in some form or other. It's too bad that they went underground leaving their customers with a stranded feeling, but you guys seem to want to hammer them back there again.

Use this beta test to do what it's supposed to do...uncover problems with the software. I'm not a programmer, so I'm not going to say what they should have done before they released it...but I'm willing to give these guys another chance. The Plugsound library is one of the best recorded libraries in it's class and the UVI engine sounds worlds better than the Sampletank/Sonik Synth 2 engine (trust me, I have them both).

So here's a virtual beer to all those who can kick back and be productive, and a virtual bitch slap for the rest of you.

spidermix

shogger · Post by **shogger** » Sat Jun 21, 2008 1:34 am

spidermix wrote:So here's a virtual beer to all those who can kick back and be productive, and a virtual bitch slap for the rest of you.

spidermix

Ah yes,

usually there is some way of compensation for a beta tester. Bugs as weighty as the ones already meantioned tell me that this product would need some serious beta testing which is real work. After that there could be a public beta test to iron out the last incompatibilities. Just to clarify that as you might not know what we're talking about here.
So relax with your bitch slapping.

Shogger

UVI Workstation (release)