After a few days with the demo, and with the presets bank growing quickly (which is promising for the future) I'll say that purchasing JP6K was for me the only thing left to do...
JP6K 1.7 update (64 bit)
-
- KVRist
- 268 posts since 24 Jul, 2001
Just ordered it !
After a few days with the demo, and with the presets bank growing quickly (which is promising for the future) I'll say that purchasing JP6K was for me the only thing left to do...
After a few days with the demo, and with the presets bank growing quickly (which is promising for the future) I'll say that purchasing JP6K was for me the only thing left to do...
-
- KVRAF
- 2844 posts since 1 Jan, 2003
Good thinking!sirbellog wrote:Just ordered it !
After a few days with the demo, and with the presets bank growing quickly (which is promising for the future) I'll say that purchasing JP6K was for me the only thing left to do...
The new presets are stellar. Even the FX presets, which I usually never consider, are interesting and inspiring.
The new features have all been working well so far! I haven't included the JP6K in a project yet- I'll wait a bit and see if the parameter list remains stable.
I'll also check out the cpu today. I didn't notice if the JP6K used a lot of cycles.
Overall, so far, fantastic update. Thank you, Adam!
-
- KVRer
- 5 posts since 2 Oct, 2009
The padsounds do indeed have a long release, but when playing a pad sound on sylenth1 my cpu doesn't go beyond 28%adamtrance wrote:It shouldn't use that much CPU, I dont know what you are doingIn 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.
Maybe it's because of the polyphony limit you can set per patch in sylenth1 and other synths ??Hmmm, when comparing abletons live cpu meter with windows xp own cpu meter and they don't match at all
Ableton indicates 35% while winxp indicates 10% weird!For the record: I do love the sound of the synth
-
- KVRian
- 584 posts since 12 Jul, 2007 from Sweden
I love the 1.1 update. Especially the stereo-spread functionality of the two oscs.
-
- KVRer
- 5 posts since 2 Oct, 2009
hey,
perhaps it's nice to also include the jp8000 square as a hypersquare like in the virus ti. And maybe a modulation matrix and polyphony limiter like sylenth1. just my 10 cents
perhaps it's nice to also include the jp8000 square as a hypersquare like in the virus ti. And maybe a modulation matrix and polyphony limiter like sylenth1. just my 10 cents
-
- KVRAF
- 1950 posts since 17 Jun, 2005
Adam, has there been progress with the project compatibility tweaking? (Automation targets remaining the same between versions, parameter positions being saved with the project instead of being read from the local patch set, etc?)
-
- KVRian
- Topic Starter
- 1238 posts since 29 Sep, 2004
Unfortunately no, because the new 114 presets use the "new" control list and if I were to somehow put the list back to the old one the new presets would be all broken again.Guenon wrote:Adam, has there been progress with the project compatibility tweaking? (Automation targets remaining the same between versions, parameter positions being saved with the project instead of being read from the local patch set, etc?)
-
- KVRAF
- 1950 posts since 17 Jun, 2005
Yeah, I totally understand, and I didn't really mean you to go back to the old control list and fix the transition from 1.0 to 1.1 in this regard.adamtrance wrote:Unfortunately no, because the new 114 presets use the "new" control list and if I were to somehow put the list back to the old one the new presets would be all broken again.Guenon wrote:Adam, has there been progress with the project compatibility tweaking? (Automation targets remaining the same between versions, parameter positions being saved with the project instead of being read from the local patch set, etc?)
I was asking more from the point of view of future versions, like, has there been progress so that one can use (for example) the version coming after 1.1 and be confident that it won't randomly change its settings inside the projects it has been used in, even if there are changes in the local patch bank or further updates to the instrument after that version?
-
- KVRian
- Topic Starter
- 1238 posts since 29 Sep, 2004
Ah yeh, I think I know how to prevent this from happening in the future. Its my first synth ever so I need to learn from mistakes just like everybody else 
-
- KVRAF
- 1950 posts since 17 Jun, 2005
Sure, no worriesadamtrance wrote:Ah yeh, I think I know how to prevent this from happening in the future. Its my first synth ever so I need to learn from mistakes just like everybody else
. In any case, it's good to know that forgetting the parameters is not likely to remain a persistent "feature" in JP6K, hehe.-
- KVRAF
- 2323 posts since 2 Feb, 2009 from Germany
-
- KVRian
- 979 posts since 7 Jan, 2011 from UK
Great Synth Adam-I have a real jp8000 and yours sounds every bit as good as it at the supersaw sounds.
One of the best gui's I have seen too.Good work
One of the best gui's I have seen too.Good work
Synth Magic synths for Konatkt - ARP Quadra, Polymoog and many more. www.synthmagic.co.uk
-
- KVRian
- Topic Starter
- 1238 posts since 29 Sep, 2004
The only parameter issues I can do is to is to add midi cc to all the controls. As I mentioned before if I fix the controls then all the patches will be messed up again So its better if its left alone.
So its better if its left alone.