nix808

I have been brewing this idea for a VST host for years.

Just wondering if anyone wants to work on it too?

I have the elements for a host built, also at the link.

The biggest problem I have is saving and recalling all the plugin states.

I'm feeling this is a cool thing and will get back to it soon.

Heya 8D,
I have been brewing this idea for a VST host for years.
I got into some Maxxing at some stage,
you can find the executable here->
http://www.phonicsaudio.com/
under applications.
Just wondering if anyone wants to work on it too?
I have the elements for a host built, also at the link.

The biggest problem I have is saving and recalling all the plugin states.
Any ideas?
I'm feeling this is a cool thing and will get back to it soon.
Cheers and hope the tech is a blast


synergy-vst-host

what approach you should use really depends on the application.

any max object which is able to store more than one number or symbol at a time and has a load/save option will do.

[coll] for example could be used just fine to first copy all parameter values and then save the whole patch to disk.

such a saved file can later be opened automatically if you want it to.

you might also try to use the textedit object.

a third option would be to automate writing and saving fxp files secretly in background.

what approach you should use really depends on the application. 

you might also try to use the textedit object. 

It is VST plug states that are the larger issue.

I understand there is patch recall implementable for

I would be perfectly happy to write presets,

and read them. If the user could press one button,

and save a named file, and also load by selecting that name

I have had trouble actually doing it though.

it is required to load the patch manually for each plug.

Any hints on automation of saving and recalling the correct .fxp?

I will look at where I got to with it and be more specific about what I am doing.

Here is the host currently as an editable max patch->

It includes the sequencer and an instrument as VSTi

Hi there!
It is VST plug states that are the larger issue.
I understand there is patch recall implementable for
MAX objects, is it pattr or something?
I would be perfectly happy to write presets,
and read them. If the user could press one button,
and save a named file, and also load by selecting that name
in a dialog. This would be sufficient.
I have had trouble actually doing it though.
Something like-
it is required to load the patch manually for each plug.
Any hints on automation of saving and recalling the correct .fxp?
I will look at where I got to with it and be more specific about what I am doing.
Here is the host currently as an editable max patch->
https://www.sendspace.com/pro/dl/y85y6s
It includes the sequencer and an instrument as VSTi
I am keen on a community project,
if anyone likes the basic concept.
Cheers Nick  -PhonicsAudio


even something like pattr will require that you first get all the parameters and values from vst~ and write them into numberboxes or something like that.

for the messages ssee the helpfiles, it is all there. you would first ask the plug-in how many parameters it has, then you can use a counter to get all their values.

i would use a special subfolder. make this at first in your maxmspfolder, and then later in your build (or maxRT for that matter)

you could have a textfile there which acts as project preferendes file and tracks all other exported files.

I see I can use the users selected plug name as

Much appreciated for helping me throw some neural switches!

hmm- OK I got it.
Thanks!
I see I can use the users selected plug name as
the cue to auto load.
I think I might be able to do this now.
Much appreciated for helping me throw some neural switches!


Synergy VST host!