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

Monstro plugin request #4

Open
faraway1nspace opened this issue Jul 22, 2015 · 3 comments
Open

Monstro plugin request #4

faraway1nspace opened this issue Jul 22, 2015 · 3 comments

Comments

@faraway1nspace
Copy link

This is a request to do a port of the LMMS native instrument Monstro to lv2.

Monstro is highly versatile and unlike anything else in the lv2 instrument world: described by the author as a Zynaddsubfx triple-osc hybrid. But its more than that. Best features:

  • it has a variety of sync functions that I admit I don't understand, but have HUGE impacts on the sound, such as different "master send" functions and different slave receive functions (hard sync, reverse polarity). I've never seen such features in any other lv2 synth, nor the resulting sounds.
  • a great but simple matrix to route 2 envelopes and 2 LFOs to a variety of parameters, especially for the slave pitches (very flexible sync-sweeps!) and for pulse-width modulation (not possible in Zyn!)
  • plus all the other features one likes from 3xOSC: FM, AM, PM, phase-shift, stereo-offset

Thanks!

@pgiblock
Copy link
Owner

What are you asking for? How is this an issue?

@faraway1nspace
Copy link
Author

Hello,
Sorry if its not clear, but its a feature request to have the new LMMS instrument Monstro ported to lv2. I noticed Monstro wasn't on your readme todo list so I thought I'd bring it to your attention.

@pgiblock
Copy link
Owner

Oh that makes sense. I was thinking Monstro wasn't even in LMMS.

Thanks

On Wed Jul 22 2015 14:57:17 GMT-0400 (EDT), Robert Rankin wrote:

Hello,
Sorry if its not clear, but its a feature request to have the new LMMS instrument Monstro ported to lv2. I noticed Monstro wasn't on your readme todo list so I thought I'd bring it to your attention.


Reply to this email directly or view it on GitHub:
#4 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants