KVR Audio

Cyforce · Post by **Cyforce** » Wed Apr 20, 2011 5:44 pm

114 presets are now in.
included 32 by myself, demo-mp3 of them, or better a re-arranged demo comes tomorrow, or tonight...

Guenon · Post by **Guenon** » Wed Apr 20, 2011 5:50 pm

Cyforce wrote: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.

Yep. Also, the way the parameters saved within a project are tied to the actual number of a preset in the current patch bank is not the way it's supposed to be.

Oh well, I'm 100% sure Adam will fix these issues. A lovely instrument otherwise, of course

sirbellog · Post by **sirbellog** » Wed Apr 20, 2011 6:06 pm

Cyforce wrote:114 presets are now in.
included 32 by myself, demo-mp3 of them, or better a re-arranged demo comes tomorrow, or tonight...

114 ?
Well, it's a good start by now, even more for the asking price of this synth...
I might as well buy it very soon (this weekend probably, or even sooner)

Plus, you seem to like the synth and be inspired by it, so you're likely to release a bigger commercial soundset very soon ?
For non programers like me, a sytnh with a good potential in sound expansions indeed makes a better value !

Cyforce · Post by **Cyforce** » Wed Apr 20, 2011 6:30 pm

Better than 20 like at the start. But still remind, the synth sounds top, but it's not so extremly flexible like typicals(alà Dune, Sylenth & Co) so there is extrem much freedom for many variety sounds - just 2 supersaw oscs.
So commercial soundsets would be surely very close to the good(!) factory sounds.

Kriminal · Post by **Kriminal** » Wed Apr 20, 2011 6:36 pm

64bit version?

adamszabo · Post by **adamszabo** » Thu Apr 21, 2011 10:14 am

Guenon wrote: 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

Yeah I know

The problem is, when I add a new control in SM it doesn't put the new controls after the old ones, but puts it where it feels like it. So before we had these controls:

Depth Select
Detune Lower
Detune Upper
Filter Type
LFO Amp Waveform

And when I add new controls it seems to put them in random order, so now we got this list:

Analog
Depth Select
Detune Lower
Detune Upper
Filter Type
Glide Time

Now, when you load a patch, the host does not apply the values by name but buy order, so first control, second control etc. Then we see what happens, the values will be messed up:

Depth Select -> Analog
Detune Lower -> Depth Select
Detune Upper -> Detune Lower
Filter Type -> Detune Upper
LFO Amp Waveform -> Glide Time

If anyone knows a fix in SM for this then it would be great. I dont know if I can fix this now, because new patches are already made using this control list, and it would be a nightmare trying to fix over 100 presets again...

AdmiralQuality · Post by **AdmiralQuality** » Thu Apr 21, 2011 10:28 am

adamtrance wrote: Depth Select
Detune Lower
Detune Upper
Filter Type
LFO Amp Waveform

And when I add new controls it seems to put them in random order, so now we got this list:

Analog
Depth Select
Detune Lower
Detune Upper
Filter Type
Glide Time

They would appear to be sorted alphabetically.

adamszabo · Post by **adamszabo** » Thu Apr 21, 2011 11:11 am

AdmiralQuality wrote:
They would appear to be sorted alphabetically.

I thought that too, but its just a small portion of the list, and after that list comes
Cutoff
Resonance
Bass
Treble
etc...

So its not alphabetical. But I hope its not alphabetical because that would be a disaster still. Say if I add a new knob called Analog 2, it will come after Analog, and it will push down the list and the presets will be messed up again. So it seems the knobs should get somekind of ID or something so that I can put them in correct order, but I still havent figured it out.

Guenon · Post by **Guenon** » Thu Apr 21, 2011 12:35 pm

Yeah. Hmm. Does the order change when you rename a control, or when you change a control's internal parameter destination? If not, and if no other convenient solution can be found before, this (hacky) idea might be able to "future proof" the controls for now:

In the next update, include a nice number of empty internal controls (just call them Empty 01, Empty 02 etc, for example) which act like placeholders in the synth, for possible new automatable parameters you might want to include at a later stage. Then, if you include an automatable feature, just rename one and assign it accordingly. Does this make sense at all? (I haven't used SM so I don't know if this is actually workable.)

In any case, to put things in perspective, automation destinations are pretty quick to reassign inside a host. I mean, on my example instance, I didn't have to do anything else than go "oh my!" and choose filter cutoff instead of pitch envelope decay in Live again. Of course, when there are a lot of tracks and automation, remembering what went where might get challenging when loading a project after a long while...

However, the other issue (not saving all the parameters with the project and relying on the contents of the current local patch bank when loading an old project) is potentially something that could lead to (more) hair loss

Integratron · Post by **Integratron** » Thu Apr 21, 2011 12:39 pm

Very nice and well worth the asking price IMHO.

Cyforce · Post by **Cyforce** » Thu Apr 21, 2011 1:14 pm

Demo-track of my 32 factory patches for the JP6K:

Everytime by playing with the JP6K i am suprised how flexible he can sound, also through "only 2 supersaws"...

Perhaps i should also build a synth like that

D N A · Post by **D N A** » Thu Apr 21, 2011 1:54 pm

Cyforce wrote: Everytime by playing with the JP6K i am suprised how flexible he can sound, also through "only 2 supersaws"...

same here

rob_lee · Post by **rob_lee** » Thu Apr 21, 2011 2:00 pm

Cyforce wrote:Demo-track of my 32 factory patches for the JP6K:

Everytime by playing with the JP6K i am suprised how flexible he can sound, also through "only 2 supersaws"...

Perhaps i should also build a synth like that

Sounds pretty nice Martin.. good sounds in the demo.

Rob

jonnycake · Post by **jonnycake** » Fri Apr 22, 2011 2:08 pm

I find the CPU usage to be quite high om my quadcore system, when playing some chords its runs up to 40/50%, is this the case for everyone ?? I thought version 1.0 was was more cpu efficient

but since i don't have the v1.0 demo anymore, i cannot compare the two.

Which midi CC does it use: can't find this in the user manual

adamszabo · Post by **adamszabo** » Fri Apr 22, 2011 3:23 pm

It shouldn't use that much CPU, I dont know what you are doing

In version 1.1, I had to add a few more things to make new features work, but they added only a few more cycles, and shouldn't bring up the cpu to 40 or 50%. I am guessing you have very long release times and too many notes? That could be heavy on the cpu if you do that, but its like that with all synths.

JP6K 1.7 update (64 bit)