KVR Audio

sergiofrias · Post by **sergiofrias** » Mon Mar 28, 2016 2:15 pm

Thank you

PTV · Post by **PTV** » Mon Mar 28, 2016 5:10 pm

martin_l wrote:
docmun wrote:when loading the sound banks I get no sound, it used to work.
Can you please give me more information? Which computer, which host, which soundbank file?
Are you opening an old project or is it in a new project?

Thanks,
Martin

Same here. Ableton Live intro 9.18 on Win XP, default.PG8Xbank, all presets starts with ADSR & Volume on zero.

docmun · Post by **docmun** » Mon Mar 28, 2016 5:25 pm

Reaper, new project, loading the banks get no sound presets:
DrewDalePG-8X Bank.PG8Xbank for instance

bstageboss · Post by **bstageboss** » Mon Mar 28, 2016 5:43 pm

Same here, using REAPER. Saving to sysex in the old version, then importing into the new version works, though (although some of the longer patch names get truncated). I went with 32-patch banks at a time.

STV

martin_l · Post by **martin_l** » Mon Mar 28, 2016 5:55 pm

I just found the problem for the failure to load old banks:

A few pages back, PAK suggested to change the parameter resultion from 0-1 to 0-100. (see http://www.kvraudio.com/forum/viewtopic ... 0#p6385370)

I was under the impression that the WDL framework stores parameters by their normalized value (i.e. always in the range 0-1), but now figured out that this is not the case. This means that old banks are currently loaded with values corresponding to 0.01 times the original value.

I have to see whether either to revert back to the old range, or whether to modify my WDL package as to read and write normalized values.

Cheers,
Martin

martin_l · Post by **martin_l** » Mon Mar 28, 2016 6:04 pm

I just tried the WDL modification and it seems to work. I guess I will go for that.

Please, keep in mind that projects, saved with the current beta (2016_03_27), will load incorrectly with the next, corrected version. If you are working on a project, please do NOT use that version!

Sorry about the problems,
Martin

martin_l · Post by **martin_l** » Mon Mar 28, 2016 8:58 pm

Quick update:

I uploaded new versions (2016-03-28), which should fix the problem of loading old banks. Please, give it a try. I hope that it also loads previous projects correctly. Let me know of any problems.

About the aliasing problem: that does not look too promising at the moment. I tried updating the filter frequency at every sample frame, and even interpolate between them for the oversampling, but the problem remains (maybe marginally improved).

I will double check whether there is any other problem. If not, I guess, I will need to bite the bullet and completely change the filter code...

Cheers,
Martin

sprnva · Post by **sprnva** » Mon Mar 28, 2016 9:31 pm

I was just about to report high CPU usage with the 03-27 Mac build here. In Live 9.6 an old January build sits at @7% CPU usage when opened in a new project. The 03-27 one was eating 30%.

The new one you've just uploaded is @15%. So still higher than previous builds but much better than yesterdays release.

On further inspection the increased CPU usage is coming from displaying the GUI. When I close the GUI, CPU usage goes down to @7%.

martin_l · Post by **martin_l** » Mon Mar 28, 2016 9:37 pm

sprnva wrote:I was just about to report high CPU usage with the 03-27 Mac build here. In Live 9.6 an old January build sits at @7% CPU usage when opened in a new project. The 03-27 one was eating 30%.

The new one you've just uploaded is @15%. So still higher than previous builds but much better than yesterdays release.

Yesterday's Mac build was accidentally a debug build. Hence the huge CPU hit. Today's build is again a release build, but I increased the frequency with which the filter frequency is updated, in an attempt to reduce the aliasing. As it did not help anyway, I probably should take it out again for the next release (until I can find a proper fix).

Cheers,
Martin

PS. I just updated the beta's with the original frequency update interval. The CPU time should be lower again.

sprnva · Post by **sprnva** » Mon Mar 28, 2016 10:19 pm

I probably added this finding after you'd read my message, but the CPU hike seems to be related to drawing the UI. It's still the same with the latest build. Opening the UI increases CPU usage by 7% here. It drops back again when I close it.

I'm not playing any audio at this stage. Just dropping PG-8X into a new project and watching Live's CPU meter. It's not a major problem now, but just reporting it all the same.

martin_l · Post by **martin_l** » Mon Mar 28, 2016 10:56 pm

sprnva wrote:I probably added this finding after you'd read my message, but the CPU hike seems to be related to drawing the UI. It's still the same with the latest build. Opening the UI increases CPU usage by 7% here. It drops back again when I close it.

I'm not playing any audio at this stage. Just dropping PG-8X into a new project and watching Live's CPU meter. It's not a major problem now, but just reporting it all the same.

That's odd as I have not really changed anything to the GUI. Need to trace back all changes I made to see which one could possibly have this effect.

Martin

layzer · Post by **layzer** » Mon Mar 28, 2016 11:06 pm

just tried the latest x32 win build. it crashed EnergyXT2 (which rarely ever crashes on my laptop) i
was just playing a few chords. no details given. my be some other plugin but we'll see if anyone
else reports daw crashes.

martin_l · Post by **martin_l** » Tue Mar 29, 2016 7:10 am

layzer wrote:just tried the latest x32 win build. it crashed EnergyXT2 (which rarely ever crashes on my laptop) i
was just playing a few chords. no details given. my be some other plugin but we'll see if anyone
else reports daw crashes.

Hi Layzer,

what were the things you did before the crash? Did you use Midi Learn? Did you change any parameters just before the crash?

Please, let me know whether you manage to reproduce the crash.

Thanks,
Martin

docmun · Post by **docmun** » Tue Mar 29, 2016 8:15 pm

It is working alright now, on Reaper.

By the way: I really love this synth, it's sound is amazing!

thanks for it

ZonderP · Post by **ZonderP** » Wed Mar 30, 2016 10:10 pm

layzer wrote:just tried the latest x32 win build. it crashed EnergyXT2 (which rarely ever crashes on my laptop) i
was just playing a few chords. no details given. my be some other plugin but we'll see if anyone
else reports daw crashes.

Same for me...
Windows 7 64 bit, EnergyXT 2.7, PG-8X (2016-03-28b)
Finally managed to record some bars before the crash. Always crashes EnergyXT2 after playing those bars in a loop after some time. This happens reproducible with Juno-60 Bass preset in 'DrewDalePG8XBank2.PG8Xbank' after some time.
No fancy stuff like automation or MIDI Learn involved...

PG8X (inspired by the JX8P): new beta version uploaded