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

Nice to hear that there will be a native version :)
I tried to download this VST forever now but the download just doesn't want to work :(
It always cancels after a few kb :(

Cheers
Dennis
Last edited by Bronto Scorpio on Sun Nov 27, 2011 7:09 pm, edited 1 time in total.
Top

Post

Very exciting Martin. I'll be waiting patiently. :tu:
Anyone who can make you believe absurdities can make you commit atrocities.
Top

Post

martin_l wrote:
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.
That's exactly what I use and would recommend.

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


Martin
I usually start with the GUI. But that's because I usually know what I want, and (mostly) how I'm going to get it, before I start. I kind of do panel design and feature selection at the same time, so when the panel is finished, I've also got my spec. And I just find it's easier to develop and test DSP when you've got a full interface to run it with. As well, you're forcing yourself to use the same interface your users will use, so you'll be the first one to know if it's useful or not. :) If something's really annoying, chances are you'll fix it for your own needs before you ever even do a Beta release. If you do it the other way, the GUI, which is almost always the most complex and error prone part, gets done last and tested "in the wild". It just makes for a far more stable and satisfying to use first release. It's really great that the second it sounds right, you're done, and can immediately get it out there for people to use.
Top

Post

The other reason to do GUI first is of course because the DSP is WAY more fun. Saving the best for last gives you reason to go on! ;)

You of course already have all your DSP code. It won't be hard to throw the business logic of your SEM implementation into the VST 2.4 SDK framework.
Top

Post

AdmiralQuality wrote:The other reason to do GUI first is of course because the DSP is WAY more fun. Saving the best for last gives you reason to go on! ;)

You of course already have all your DSP code. It won't be hard to throw the business logic of your SEM implementation into the VST 2.4 SDK framework.
I guess once I have something together which makes some noise, then I will do the GUI before finishing the DSP part.

I just did not know how to test the GUI without having any rudimentary DSP part ready.

By the way, thanks very much for any advise.

Cheers,
Martin
Top

Post

martin_l wrote:
AdmiralQuality wrote:The other reason to do GUI first is of course because the DSP is WAY more fun. Saving the best for last gives you reason to go on! ;)

You of course already have all your DSP code. It won't be hard to throw the business logic of your SEM implementation into the VST 2.4 SDK framework.
I guess once I have something together which makes some noise, then I will do the GUI before finishing the DSP part.

I just did not know how to test the GUI without having any rudimentary DSP part ready.

By the way, thanks very much for any advise.

Cheers,
Martin
The GUI will work as usual and send setParameterAutomated calls to the host, which calls the effect. If the effect has no such parameter (yet) your switch/case statement in effect::setParameter won't do anything with that control/parameter index.

And happy to help. Lots more help to be found in the Developers Forum as well.

Cheers!
Top

Post

AdmiralQuality wrote: The GUI will work as usual and send setParameterAutomated calls to the host, which calls the effect. If the effect has no such parameter (yet) your switch/case statement in effect::setParameter won't do anything with that control/parameter index.

And happy to help. Lots more help to be found in the Developers Forum as well.

Cheers!
Thanks a lot. I already did read a lot of interesting threads on the developers forum.
Bronto Scorpio wrote: Nice to hear that there will be a native version :)
I tried to download this VST forever now but the download just doesn't want to work :(
It always cancels after a few kb :(
Let me know if the problem persists, then I can try to find an alternative download location.

Cheers,
Martin
Top

Post

Probably already mentioned, didn't read the whole thread, but... would it be possible to add an 'expanded' mode for bringing the synth up-to-date?

Accurate emulations are nice, but why not expanding on the original concepts with nowdays possibilities?

Obvious example: artificial polyphony limitations, to that of the original hardware.

Since you're rebuilding it from scratch, please take some fresh ideas into consideration.
Top

Post

Evan wrote:Probably already mentioned, didn't read the whole thread, but... would it be possible to add an 'expanded' mode for bringing the synth up-to-date?

Accurate emulations are nice, but why not expanding on the original concepts with nowdays possibilities?

Obvious example: artificial polyphony limitations, to that of the original hardware.

Since you're rebuilding it from scratch, please take some fresh ideas into consideration.
I am planning to leave this one as what it is now (just coded differently, maybe some small changes to the GUI, which I want to make a bit more compact).

However, I am writing the new code such, that I easily can build an extended version. I am planning to release a new synth, build on the same engine, but with some more features.


Which features so you have in mind? I can't promise that I can implement all, but at least it is nice to hear some ideas.


Cheers,
Martin
Top

Post

I didn't notice any sound demos... any around?
Top

Post

martin_l wrote: Which features so you have in mind? I can't promise that I can implement all, but at least it is nice to hear some ideas.
Thanks for the reply. Well I can't comment on anything specific, I am not familiar with the original instrument. It's better to ask yourself and those who are familiar with it. If you extended the synth, it would be good to do so in the spirit of the original and similar synths.

Polyphony is an obvious area of improvement.
Top

Post

Wow Martin, great news :tu:
Resizable gui would be very cool :)
It`s not a bug... it`s a feature!
Top

Post

pdxindy wrote:I didn't notice any sound demos... any around?
There have been some audio examples in this thread. Here are the links. I don't know whether they are still working, though. No guarantee...

http://s000.tinyupload.com/download.php ... 5595165643

http://dl.dropbox.com/u/6185854/kvr%20s ... ver%29.mp3

http://www.divshare.com/download/14080605-504

http://soundcloud.com/kujaschi/patchbankexamples-pg-8x#

http://www.divshare.com/download/14080605-504

http://www.divshare.com/download/14090073-3f3

http://www.divshare.com/download/14099340-a65

http://www.divshare.com/download/14142458-b62

http://www.divshare.com/download/14172246-ffb


And, just download the plugin (http://sites.google.com/site/mlvst0) and try it out yourself. It's free...


Martin
Top

Post

Wow - doesn't sound half bad!

Can't wait until the Mac AU version is for sale!

/Joachim
If it were easy, anybody could do it!
Top

Post

Spitfire31 wrote:Wow - doesn't sound half bad!

Can't wait until the Mac AU version is for sale!

/Joachim
Well, sorry. I am not planning to get into AU at the moment. But I will try to get an Mac VST version running....

Martin
Top
Locked

Return to “Instruments”