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

squidlr wrote:
martin_l wrote:
squidlr wrote:Probably it's already mentioned in this huge thread, didn't have time to read thru - PG-8X forgets loaded presets once you save a project including PG-8X in Logic Pro X, so you have to load the presets back each time you open project in Logic.
I assume you are talking about the AU..?
I don't have Logic, I will try to test later with GarageBand, which hopefully will behave similarly.

Cheers,
Martin
Yes, the AU version - seems like the above problem is apparent in Garageband too.
OK. I will investigate tonight.

Martin

Post

DrewDale wrote:32 patches here http://www.kvraudio.com/product/pg-8x-b ... /downloads in syx & PG-8X file format :)
These patches are phat!!! Thx :)

Post

squidlr wrote: These patches are phat!!! Thx :)
Cheers :tu:
:tu: All is good

Post

layzer wrote:on my musicroom xp x32 system that has a spidif connection that forces the daw to 48khz, loading up PG8X causes the output on other
vst's to crackle. .....WEIRD! on my xp x32 HP Elitebook it seems fine at 41khz. so there may be a issue with running it a 48khz sample rate.

edit: confirmed... just switched EXT2 on the notebook to 48khz and it did the same thing as the musicroom PC.
I just tried it at 48 kHz (x64 version, in Reaper x64, Win 7 64 Pro, through an Edirol UA-1000 USB 2.0 audio interface) and it was fine (including the sound from other VSTs). It's probably just available CPU power and/or differences between your two systems.

Post

Fantastic sound, crystal clear, punchy, phat, warm!
Thank you very much, Martin.
Only thing that makes me wonder is why only one preset and not 32, 64 or 128 are exposed to the host.
And why it should not be possible to load fxb banks with the VST version?

Post

ZonderP wrote:Fantastic sound, crystal clear, punchy, phat, warm!
Thank you very much, Martin.
Only thing that makes me wonder is why only one preset and not 32, 64 or 128 are exposed to the host.
And why it should not be possible to load fxb banks with the VST version?
Because that's how he chose to do it, basing it on some other non-compliant products. (I tried!)

Post

That is sad...
Nonetheless the synth itself is a Lamborghini (except its doors open to the ground :ud: )

Post

ZonderP wrote:That is sad...
Nonetheless the synth itself is a Lamborghini (except its doors open to the ground :ud: )
Yes, I think he's done a very good job with it, otherwise. It's a very faithful sounding reproduction of the original JX-8P.

Post

ZonderP wrote:That is sad...
Nonetheless the synth itself is a Lamborghini (except its doors open to the ground :ud: )
Thanks for your kind words.

The reason, I decided to take this "non standard" approach is, that I wanted to give users the option to use it in the "hardware style", i.e. you need to write presets to make the synth remember them. Most hardware behaves like that, and also many other plugins, in particular emulations of hardware.

Based on the previous discussions, I now implemented both (keeper and restorer) modes. In the "MIDI" panel (name of that panel not yet finalized), you can choose whether changes are automatically written to the current preset, or whether they need to be written. This behaviour would have been inconsistent with the normal way, exposing all presets to the host (thanks for pointing this out, AdmiralQuality).

Personally, I don't see any disadvantage of exposing only one preset to the host. Presets can be changed via MIDI (programme change) or via the readout display (Note to myself: write the manual!!). Writing the native pg8xbank files also is performing the same task as writing fxb's through the host. The only difference is that it is done through the plugin.

The doors might open in a different way, but I would say, they do the job. If there is anything which really disturbs the workflow (other than just being slightly different that other VST's), please let me know.


Cheers,
Martin

PS. Now off to fixing the denormal issue...

Post

New Windows betas (*04-02*):

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

Denormal bug (on Windows VST) should (hopefully) be fixed...
Please, let me know....


Martin

Post

martin_l wrote:New Windows betas (*04-02*):

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

Denormal bug (on Windows VST) should (hopefully) be fixed...
Please, let me know....


Martin
whatever you denormalized, it appears to have fixed the crackling. thanks Martin! now if only Jorgen could address issues with the new multicore ENERGYXT2 3.0 as quick as you, my music creating world would be perfect! :hihi:
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

Yes it is fixed.
Thank you very much ! :)
[====[\\\\\\\\]>------,

Ay caramba !

Post

Mutant wrote:Yes it is fixed.
Thank you very much ! :)
That's good news. Thanks for letting me know.

Martin

Post

I see no problem with exposing just one preset to the host. u-he plugins are just fine with the same approach, since they have their own file browsers.

Post

EvilDragon wrote:I see no problem with exposing just one preset to the host. u-he plugins are just fine with the same approach, since they have their own file browsers.
U-he has a better patch management system.
[Insert Signature Here]

Locked

Return to “Instruments”