KVR Audio

alvakorn · Post by **alvakorn** » Thu Jan 21, 2016 9:21 pm

Big Busker wrote:OK, now I need someone to point me to the 'legacy' 'fan dedication' JX8P factory patch downloads!

edit: Found some! Link to zipfiles of the sysex factory patches, and some fan patches also.
http://www.synthzone.com/midi/roland/jx8p/syx.zip

I went on a big internet hunt for any JX-8P syx patches that existed a couple years back. What I found was the group listed above were pretty much the only ones from back in the day.... Now that Martins great plugin exists hopefully many new syx banks will be created.

layzer · Post by **layzer** » Thu Jan 21, 2016 10:14 pm

alvakorn wrote:
Big Busker wrote:OK, now I need someone to point me to the 'legacy' 'fan dedication' JX8P factory patch downloads!

edit: Found some! Link to zipfiles of the sysex factory patches, and some fan patches also.
http://www.synthzone.com/midi/roland/jx8p/syx.zip
I went on a big internet hunt for any JX-8P syx patches that existed a couple years back. What I found was the group listed above were pretty much the only ones from back in the day.... Now that Martins great plugin exists hopefully many new syx banks will be created.

Martin is a great guy for giving this fine software synthesizer away for free. I know he takes donations, but really, he should get a monthly sum by all his synth's users to help keep him alive so that he can bring forth new synths well into future.

electro · Post by **electro** » Sun Jan 31, 2016 1:42 am

what is left to take this synth out of beta?

Mutant · Post by **Mutant** » Sun Jan 31, 2016 3:22 am

I think the only thing left to fix is the DC offset.

martin_l · Post by **martin_l** » Sun Jan 31, 2016 11:45 am

electro wrote:what is left to take this synth out of beta?

I hope I should be nearly there.

I fixed the main part of the DC offset problem, but currently I am hunting another strange bug. I still get DC jumps when the synth is internally switching the oversampling. The oversampling is determined by the highest oscillator frequency. I kind of know where the bug is: it has to be in the internal variables of the high pass filter, but have not yet managed to fix it. The code "looks" ok, but still behaves wrongly. Well, that's what bugs are...

Another bug is, that in some cases (I have not yet figure out how to systematically reproduce it) the LFO has no effect on the oscillators. Normally, reloading the patch does fixes it, but I don't like to release even another beta if I know that such bugs exist.

Furthermore, I started writing some manual, which is not yet quite finished, and I want to revamp the webpage to reflect the new version.

The main problem is, that my daytime job gives me very little time to work on the plugin.

Anyway, I don't want to waste more time writing posts, rather get back to debugging...

Cheers,
Martin

martin_l · Post by **martin_l** » Sun Jan 31, 2016 2:50 pm

OK. Next beta is out.

Main Changes:

DX offset should be fixed
Ring modulator slightly improved
LFO delay times adjusted

https://www.dropbox.com/sh/e5oop1vf8vpl ... eezxa?dl=0

This could be a final release candidate if no further bugs show up.

Happy testing!

Martin

ras.s · Post by **ras.s** » Sun Jan 31, 2016 4:03 pm

Thanks for the update, once again.

I'm reporting that on 64-bit Windows 7, the 64-bit version doesn't pass Bitwig Studio's validation process. However, the 32-bit version does validate (Bitwig has an internal bit-bridge) and so does the previous 64-bit version.
It throws this error message:

D:\vst-64bit\Synthesizers\PG8X\PG8X.dll
com.bitwig.flt.library.metadata.reader.exception.

CouldNotReadMetadataException: could not read metadata: Could not read VST plug-in metadata

64 bit plugin host reported errors: Error executing command "C:\Program Files (x86)\Bitwig Studio\bin\x64\BitwigPluginHost64.exe" info-file C:\Users\X\AppData\Local\Temp\vst-info5342412629448157628tmp D:\vst-64bit\Synthesizers\PG8X\PG8X.dll: null

32 bit plugin host reported errors: Pluginhost returned non zero exit code -1

The last line is there I guess because it then tried loading it as 32-bit, which of course fails as well. The temp file the error message points to has this in it:

Printing plug-in meta data for D:\vst-64bit\Synthesizers\PG8X\PG8X.dll ...

PLUGIN:
Vendor:MLVST
Name:PG-8X
Identifier:50473858
Version:0
Category:Synth
HasAudioInput:yes
HasNoteInput:yes
HasAudioOutput:yes
HasNoteOutput:yes
AudioInChannelCount:2
AudioOutChannelCount:2
DeviceTypes:note_to_audio

And I hope I could still sneak in a teeny weeny feature request, which I think would make it slightly faster to get started with PG8X: please add the option to have it load a default bank. It could be defined in the .ini file or have it look for default.PG8Xbank in the plugin directory .. It's already great that I can have the default folder defined, that's where I put my banks, but having it load a default bank would make it instantly playable without any mouse clicks after loading the plugin.

Anyways, thanks for the update and congrats on having it almost finished. :)

Mutant · Post by **Mutant** » Sun Jan 31, 2016 4:15 pm

ras.s wrote: And I hope I could still sneak in a teeny weeny feature request, which I think would make it slightly faster to get started with PG8X: please add the option to have it load a default bank. It could be defined in the .ini file or have it look for default.PG8Xbank in the plugin directory .. It's already great that I can have the default folder defined, that's where I put my banks, but having it load a default bank would make it instantly playable without any mouse clicks after loading the plugin.

+1

martin_l · Post by **martin_l** » Sun Jan 31, 2016 4:58 pm

OK. I will investigate the 64bit problem. Need to see whether I can reproduce it.

As for the default bank. It's already there, I just did not manage to describe it yet as I did not fully test that part yet.
There is the pg8x.ini file, where you can add the keyword DEFAULT_BANK = "full path to bank".

Cheers,
Martin

ras.s · Post by **ras.s** » Sun Jan 31, 2016 5:09 pm

!

I can happily say setting the default bank works like a charm over here. Thank you.

martin_l · Post by **martin_l** » Sun Jan 31, 2016 5:22 pm

ras.s wrote:Thanks for the update, once again.

I'm reporting that on 64-bit Windows 7, the 64-bit version doesn't pass Bitwig Studio's validation process. However, the 32-bit version does validate (Bitwig has an internal bit-bridge) and so does the previous 64-bit version.
It throws this error message:

D:\vst-64bit\Synthesizers\PG8X\PG8X.dll
com.bitwig.flt.library.metadata.reader.exception.

CouldNotReadMetadataException: could not read metadata: Could not read VST plug-in metadata

64 bit plugin host reported errors: Error executing command "C:\Program Files (x86)\Bitwig Studio\bin\x64\BitwigPluginHost64.exe" info-file C:\Users\X\AppData\Local\Temp\vst-info5342412629448157628tmp D:\vst-64bit\Synthesizers\PG8X\PG8X.dll: null

32 bit plugin host reported errors: Pluginhost returned non zero exit code -1

Just tried the 64bit version in reaper 5.12 and it loaded without problem.
Have you tried to clear completely the plugin cash your bitwig might have?
Maybe there are some things left from the last version which cause a conflict?

Cheers,
Martin

martin_l · Post by **martin_l** » Sun Jan 31, 2016 5:32 pm

martin_l wrote:
ras.s wrote:Thanks for the update, once again.

I'm reporting that on 64-bit Windows 7, the 64-bit version doesn't pass Bitwig Studio's validation process. However, the 32-bit version does validate (Bitwig has an internal bit-bridge) and so does the previous 64-bit version.
It throws this error message:

D:\vst-64bit\Synthesizers\PG8X\PG8X.dll
com.bitwig.flt.library.metadata.reader.exception.

CouldNotReadMetadataException: could not read metadata: Could not read VST plug-in metadata

64 bit plugin host reported errors: Error executing command "C:\Program Files (x86)\Bitwig Studio\bin\x64\BitwigPluginHost64.exe" info-file C:\Users\X\AppData\Local\Temp\vst-info5342412629448157628tmp D:\vst-64bit\Synthesizers\PG8X\PG8X.dll: null

32 bit plugin host reported errors: Pluginhost returned non zero exit code -1

Just tried the 64bit version in reaper 5.12 and it loaded without problem.
Have you tried to clear completely the plugin cash your bitwig might have?
Maybe there are some things left from the last version which cause a conflict?

EDIT: Just downloaded the demo version of Bitwig, and it seems to load fine here.

Cheers,
Martin

ras.s · Post by **ras.s** » Sun Jan 31, 2016 5:56 pm

Yes, it was a false alarm, sorry about that.

I removed all the copies of the plugin, had Bitwig scan again, then put the plugin back in and had Bitwig scan and now it shows up correctly (both versions, though I'll stick with the 64-bit and remove the other). Either a user error or something on Bitwig's side, since now it shows two copies of the 32-bit pointing at the same file, but in any case, everything's cool.

martin_l · Post by **martin_l** » Sun Jan 31, 2016 6:07 pm

ras.s wrote:Yes, it was a false alarm, sorry about that.

I removed all the copies of the plugin, had Bitwig scan again, then put the plugin back in and had Bitwig scan and now it shows up correctly (both versions, though I'll stick with the 64-bit and remove the other). Either a user error or something on Bitwig's side, since now it shows two copies of the 32-bit pointing at the same file, but in any case, everything's cool.

Glad to hear that.

The confusion about the 32/64 bit versions in Bitwig could be because they use the same VST ID. But it should not be a problem if you only use one of them anyway. There is no reason to keep both if your host is 64bit.

Cheers,
Martin

martin_l · Post by **martin_l** » Fri Feb 05, 2016 6:16 pm

Questions to all MAC 10.8 users:

I got a report that the 64-bit VST plugin does not show up in Ableton nor in Bitwig on Mac 10.8.
Can anybody confirm that this is the case? Or is there anybody who can use it on that system?

Thanks!
Martin

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