KVR Audio

D N A · Post by **D N A** » Wed Apr 20, 2011 7:05 am

vaisnava wrote:Wow, it produces NO sound in Jeskola Buzz or Reaper here.

I had similar feeling during testing beta version. Most probably it's because of protection = you don't have a license file inside your folder and the result is no sound.

ps. very nice, "catchy" YT audio demo by MASCHINENBAUERMUSIC

(pad at the end is marvellous

)

Elektronisch · Post by **Elektronisch** » Wed Apr 20, 2011 7:27 am

very nice update wich includes glide!

but seems there is a bug in gliding...

http://www.speedyshare.com/files/280593 ... liding.mp3

first melody goes without glide and later on with glide

antto · Post by **antto** » Wed Apr 20, 2011 8:04 am

themachinelt wrote:very nice update wich includes glide!

but seems there is a bug in gliding...

http://www.speedyshare.com/files/280593 ... liding.mp3

first melody goes without glide and later on with glide

it doesn't look like a bug
the oscillator retriggers, if there is a Retrigger option - disable it, should sound normal

adamszabo · Post by **adamszabo** » Wed Apr 20, 2011 8:19 am

themachinelt wrote:very nice update wich includes glide!

but seems there is a bug in gliding...

http://www.speedyshare.com/files/280593 ... liding.mp3

first melody goes without glide and later on with glide

Yes, initially I didnt want portamento for this reason coz the portamento in SM does this. The portamento only works correctly when you have notes overlapping each other, so maker all your notes a little bit longer and the pops will go away.

adamszabo · Post by **adamszabo** » Wed Apr 20, 2011 8:20 am

SoulTrain wrote:Missing plug-in message in Cubase 5 after updating from 1.0

Hmm, its propably because the plugin id was changed by accident and now cubase thinks its a different plugin. Please put your version 1.0 back, save your presets from the synth, not in .fxb format. Then replace the synth, load it in again and put back your preset.

Cyforce · Post by **Cyforce** » Wed Apr 20, 2011 9:08 am

Why not using the old plugin-ID in the 1.1 version? So the user must only replace the 1.0 ddl with the 1.1. ...

SoulTrain · Post by **SoulTrain** » Wed Apr 20, 2011 9:48 am

Yeah, I brought back an old dll, so now i have old and new dll in VST folder. Cubase see both of them at the same time =)
BUT indeed why not to use the same plugin ID

In my case the problem was not in used presets, but in automatizations. If you replace missing plug-in with a new one, you have to draw all needed automatizations one again and this is really annoyingly bad!

Elektronisch · Post by **Elektronisch** » Wed Apr 20, 2011 10:47 am

adamtrance wrote:
themachinelt wrote:very nice update wich includes glide!

but seems there is a bug in gliding...

http://www.speedyshare.com/files/280593 ... liding.mp3

first melody goes without glide and later on with glide
Yes, initially I didnt want portamento for this reason coz the portamento in SM does this. The portamento only works correctly when you have notes overlapping each other, so maker all your notes a little bit longer and the pops will go away.

Well thing is, if i make notes little longer, i miss a note on the same key, and there is not retrigger option

adamszabo · Post by **adamszabo** » Wed Apr 20, 2011 10:55 am

The plugin id was changed by mistake, and has now been corrected. I sent out emails, so please download the plugin again and see if it loads.

keel · Post by **keel** » Wed Apr 20, 2011 2:50 pm

Thank you Adam! I really hope keep improving this beauty!

Happy Frog · Post by **Happy Frog** » Wed Apr 20, 2011 2:58 pm

How many patches are there now, please.

SoulTrain · Post by **SoulTrain** » Wed Apr 20, 2011 2:58 pm

Thats okay now, thanks a lot =)
Please keep in mind (ID issue) in the future updates!
And thank you for this awesome plug-in!

Guenon · Post by **Guenon** » Wed Apr 20, 2011 3:46 pm

Even after using the fixed plugin with the correct id, I'm facing some big problems with project compatibility (using Live):

First, in an ongoing project where I have used instances of JP6K 1.0, the automation now controls wrong parameters. Filter cutoff automation is now hooked to pitch envelope decay.

Perhaps more seriously, it seems that the instrument has never saved its parameters with the project for total recall. Instead, it relies on the actual patch number in the patch bank.

For example, in my project I used a sound I made by customizing JPK6 1.0 patch number 5, "LEAD - Believe". Now, when I load the project with version 1.1, I get a totally different sound based on the current patch number 5, "BASS - Digital Bass"

You can imagine my *spit the coffee* reaction when I first listened to the project with JP6K 1.1, with all the wrong sounds and the pitch envelope wonking all over the place due to the automation

Luckily, replacing the plugin again with version 1.0 makes everything all right for now. In any case, it's unusable as far as project compatibility down the road is concerned: an instrument should NOT lose its automation targets or actual parameter settings inside a project when doing a mere point update, or when changing the contents of the patch bank.

Cyforce · Post by **Cyforce** » Wed Apr 20, 2011 4:14 pm

Usually if you add new features, and all existence value's still exist, something like that couldn't show up, except the new values(for the new features) has the same parameter name or midi cc number.

sirbellog · Post by **sirbellog** » Wed Apr 20, 2011 5:21 pm

Happy Frog wrote:How many patches are there now, please.

As a "non-tweaker", just "preset player" potential customer, I second this question !

JP6K 1.7 update (64 bit)