Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Creating option for opening VST GUIs #27

Open
to-the-sun opened this issue Jun 6, 2018 · 0 comments
Open

Creating option for opening VST GUIs #27

to-the-sun opened this issue Jun 6, 2018 · 0 comments
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@to-the-sun
Copy link
Owner

Repository

https://github.com/to-the-sun/amanuensis

The Amanuensis is an automated songwriting and recording system aimed at ridding the process of anything left-brained, so one need never leave a creative, spontaneous and improvisational state of mind, from the inception of the song until its final master. The program will construct a cohesive song structure, using the best of what you give it, looping around you and growing in real-time as you play. All you have to do is jam and fully written songs will flow out behind you wherever you go.
If you want to try it out, please get a hold of me! Playtesters wanted!

Details

Currently when playing VST instruments the user must rely on presets, because there is no way to actually open up the VSTs' GUIs. Personally I have always had no problem with this functionality, but many if not most others would feel stifled without this ability, so this task request would be for enabling that option. It'd be great if someone could handle this while I work on other things!

VSTs are loaded into [vst~] and the command to open up its GUI is a simple open message sent to the object.

The other half of the request would be placing an "open VST GUI" option of some kind on The Amanuensis's UI as well.

Components

The backend portion of this request would involve synth.maxpat and the abstraction found in it vsti.maxpat.

Two things will need to happen here: first, a message designating the track/channel will need to be sent to that [gate 16] and immediately after, the open message sent through it.

That message will then have to navigate its way down to the actual [vst~] object. These objects are created dynamically with scripting, so they're not present in the above screenshot, but messages are delivered to them through the right inlet of [join @triggers 1]. Really it's not as complicated as it looks. A simple [routepass open] at the very beginning of vsti.maxpat may be all it takes.

On the front-end (sound.maxpat), I'd like to keep things as uncluttered as possible, so perhaps an option can be appended to the synth umenu to the effect of "[open the selected VST's name here UI]" and when chosen, the explained functionality is executed. No extra buttons would then be required, but the menu would need to have its options updated dynamically.

Deadline

I'm hoping for the right person this would be an easy task. Maybe something that takes no more than 10 days.

Communication

Reply to this post or contact me through Github for more details.

Proof of Work Done

https://github.com/to-the-sun

@to-the-sun to-the-sun added enhancement New feature or request help wanted Extra attention is needed good first issue Good for newcomers labels Jun 6, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant