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

VST, AU, AAX, CLAP, etc. Plugin Virtual Instruments Discussion
Locked New Topic
RELATED
PRODUCTS
pg-8x

Post

zimmerabc wrote:Hi Martin,
any timeline for the
new sysex-import?
Best Regards
zimmerabc
Hi there.

Sorry for the long silence. I was on business travels for the last couple of weeks, and right now on holiday, and away from my DAW. I should be able to continue the development, in a week or two. I hope it won't take me too long to finish it.

Martin

Post

matt1314 wrote:Just noticed this plug-in. Really nice one, I like it! :D But how can we import these extra banks into it? And how can we save our own patches?
Thanks for the kind words.

At the moment, the only way to load or save banks is through the host's patch management system. I am planning to implement a native bank support in a future version.

Cheers,
Martin

Post

Nice to hear from you, Martin. I'm using your VST and I'm really glad to have a JX-8P emulation, it sounds really nice. Hope you import your planned features when you can. :)
My newest project: Synthiox

Yamaha MM6, Novation Ultranova, Behringer FCB1010

Post

hi everyone, i love the sound of the JX-8p.

The following youtube user has some excellent covers made with his JX8P



I wondered if someone would be able to reproduce the sound on the VST and share the settings? thanks!

Post

@ Maten_j Any news ?

Post

loungedumore wrote:@ Maten_j Any news ?
no ?

Post

pleeeaaazzzeeee.....

Post

zimmerabc wrote:pleeeaaazzzeeee.....
Apologies to those who are waiting...

The last month I was (and still am) very busy with my real-life job.

I did continue somethings though, but I am a bit stuck. The JX8P sysex allows to receive a patch (i.e. tone) and write it into a new memory location. This is very difficult in synthedit, at least when patches are handled the normal SE way.

I am working on a new way to handle patches, which is nearly ready and working, but it won't be compatible with the old fxb files. I am trying to come up with a way how to transfer the old fxb banks to sysex banks, which would then be the standard way how to load and save patches.


Cheers,
Martin

Post

Martin, this plugin is awesome! I've had a JX8P since the 80s and it recently died on me. The PG8X really does sound like it. Many thanks for your work!

Post

any update is a good update ?

Post

this thing makes some sweet warm analog strings...
very close to the JX8P
HW SYNTHS [KORG T2EX - AKAI AX80 - YAMAHA SY77 - ENSONIQ VFX]
HW MODULES [OBi M1000 - ROLAND MKS-50 - ROLAND JV880 - KURZ 1000PX]
SW [CHARLATAN - OBXD - OXE - ELEKTRO - MICROTERA - M1 - SURGE - RMiV]
DAW [ENERGY XT2/1U RACK WINXP / MAUDIO 1010LT PCI]

Post

Martin,
Thanks for such a great synth. Been following the development of this synth with great interest from the start.
Just uploaded a new track I made using it for pad sounds.

http://soundcloud.com/ifihadahifi/fairfield

CIAD

Post

loungedumore wrote:any update is a good update ?
Hi there.

Sorry for the long silence. The reason is, that the new patch system, which would allow import of SYSEX banks, caused me a lot of headache. So much, that I decided to abandon the development....


Well, that means with Synthedit, as the SE patch system is so different from what I need. Here comes the good news:

I started rewriting the whole thing as a native plugin, fully coded in C++ and SSE assembly. Most of the DSP side of the pg8x was coded this way anyway (SE sem's).

The reasons for this decision were that I hope to squeese a bit better performance out of it, that it will be easier to port to MAC or 64bit, and also I was not happy with the order of parameters for Automatization. Also the names were a mess.

Correcting this means that the new plugin will NOT be compatible with the old one. Sorry!! But, the new one will not sound any differet form the old one. So for projects where you use it, there is absolutely no reason to upgrade.

Also, the old one already CAN read Sysex data, however only for one patch at a time. It can also send sysex in the same way. This will be the mechanism to transfer banks from the old one to the new one.


I am still only in the beginning phase of the new plugin, as I had to spend quite some time getting familiar with the VST SDK.

I'll keep you updated about the development, and will post beta's as soon as I have something that runs.

Till then, thanks for your patience and your support, and keep enjoying the old version for the time beeing.


Cheers,
Martin

Post

martin_l wrote:
loungedumore wrote:any update is a good update ?
Hi there.

Sorry for the long silence. The reason is, that the new patch system, which would allow import of SYSEX banks, caused me a lot of headache. So much, that I decided to abandon the development....


Well, that means with Synthedit, as the SE patch system is so different from what I need. Here comes the good news:

I started rewriting the whole thing as a native plugin, fully coded in C++ and SSE assembly. Most of the DSP side of the pg8x was coded this way anyway (SE sem's).

The reasons for this decision were that I hope to squeese a bit better performance out of it, that it will be easier to port to MAC or 64bit, and also I was not happy with the order of parameters for Automatization. Also the names were a mess.

Correcting this means that the new plugin will NOT be compatible with the old one. Sorry!! But, the new one will not sound any differet form the old one. So for projects where you use it, there is absolutely no reason to upgrade.

Also, the old one already CAN read Sysex data, however only for one patch at a time. It can also send sysex in the same way. This will be the mechanism to transfer banks from the old one to the new one.


I am still only in the beginning phase of the new plugin, as I had to spend quite some time getting familiar with the VST SDK.

I'll keep you updated about the development, and will post beta's as soon as I have something that runs.

Till then, thanks for your patience and your support, and keep enjoying the old version for the time beeing.


Cheers,
Martin
WTG Martin! :tu:

Curious, what are you using for your GUI code? VSTGUI? If so, what version? And which version of the VST SDK? Hopefully not 3.anything. :roll:

Post

AdmiralQuality wrote: WTG Martin! :tu:

Curious, what are you using for your GUI code? VSTGUI? If so, what version? And which version of the VST SDK? Hopefully not 3.anything. :roll:
For the VST SDK I use version 2.4. For the GUI probably VST GUI 3.6. I want to keep the GUI similar to the old version, and that only contains quite simple elements. So I guess it should not be too hard with VST GUI.

To be honest, I have not started with the GUI yet. I am still in the progress of putting all DSP elements together.


Martin

Locked

Return to “Instruments”