dbgrande / grandemodular Goto Github PK

Dear David,

The recently released Mrg8 is just wonderful. Small but handy, I have it (& Splt8) everywhere in my patches! There's one feature though that I'm thinking about. Would you please consider normalizing the inputs to each other?

By normalizing the inputs a single cable input #8 would not only open up polyphony channels #1 to #7 but the signal would also be reflected on those channels.

That would mean channel #4 is repeated in #1 to #3 and channel #7 would also appear on channel #5 to #6.

Best regards, Andras

Would you please consider a simple CV2gate module?

Best regards, Andras

I enjoy using PSlt a lot but I'd like to ask you to consider a slightly more flexible (but probably les efficient) polyphonic module.

Top6 allows selecting the top 6 favorite channels of a polyphonic input. (I.e. setting the first knob to #7 it'll forward the 7th channels of PolyIn to the 1st channel to PolyOut.)

Just to avoid these kind of knots in patches:

Kind regards, A.

Quant is my favorite quantizer, particularly the equi switch, but the root input seems to be broken. Putting in a range of inputs just changes the output between two values, which is not the way it's supposed to work, according to the doc,

The output at the bottom seems to be dead

Would you please consider creating a simple '8-channel polyphonic merge' module?

I know that there are 16-channel (VCV Merge) and 4-channel (your great MS4, Aria Salvatrice's Swerge & Werge) modules but no 8-channel ones. I also noticed that I regularly find myself putting a bunch of your MS4 everywhere and not using half of the module. A simple 3HP GrandeModular merge/split would so nice.

Best regards, Andras

New usage, and possible documentation addition

I think there is another major use for Tails4 that perhaps should be documented. Rather than multiple V/Oct inputs for different melodic lines, it can also support a single V/Oct input, plus other CV such as velocity and/or after touch, etc.

I believe this will only work with monophonic inputs.

The same monophonic gate input would be used for all.

Instead of patching V/Oct out to a VCO, it can be patched to the Resplit input, and then each of the polyphonic block outputs can be routed appropriately.

There are a few issues to work around.

• The number of output gate channels should match the user's selected channel count. But the poly Gate output will replicate the channels for each of the "V/Oct" blocks. The solution is to also patch the gate input to one of the V/Oct inputs, and then take the resultant gates from the Resplit output instead of the Gate output.
• The gate output from Resplit will only work properly if the module latch mode is set to Next Note. Otherwise the gate outputs are a constant 10V.
• Depending on what steps were taken to create the patch, the Resplit blocks may be out of sync. They need to be reset so that each block is writing to the same channel at the same time. This can be done from the context menu by the Initialize option, and then the channel count, latch mode, and VCA gain must all be reset appropriately.

Enhancement requests

The above is all well and good, but I would love to see some enhancements to Tails4 to make usage as described above simpler, and a bit more powerful.

1. Add a reset button so to force all blocks to sync their channel assignments, without changing Channel count, latch mode, or CV gain. If space cannot be found, then I suppose it could be a context menu option.
2. Normalize the V/Oct output to the Resplit input, so as to eliminate an unnecessary sample delay. I suppose if the module is in poly mode than the Resplit normalization should be broken.
3. Have a mode that causes the Gate output to create only a single block. I can think of a couple ways to trigger this mode

• A context menu option could be used, but I don't think it should be necessary
• If there is only one Gate input and there are Resplit outputs patched, but no Resplit input (ie, the normalled signal is used), then that could signify that the Gates section should only send a single block output.

The single block gate output mode would have two major benefits

• All latch modes would be available for use. You would no longer be restricted to the "New Note" mode
• All four V/Oct inputs could be used for CV instead of reserving one for the gates

When Tails is bypassed could you pass inputs to outputs unmodified please.

Under normal circumstances the "Frequency modulation" knob is inactive if there is no cable in the "Frequency modulation input" socket. Would you please consider enabling a feature that the same knob (i.e. "Frequency modulation") acts as an attenuator in these cases?

loving your modules. I'm finding a lot of musical application to microtonal arrangements.

I'm writing to request a right click menu action on Microtonal Chords that copies the notes from A to B/C/D. This could be implemented as three right click menu items: a "copy from" submenu selecting from A-D, another for "copy to", and then a "copy" action that does it.

Thanks again.

Could you please add a git tag/release for the v2.6.1 stable version? Thanks :)

Presumably the Push module is designed to be used during performance, but it is very easy to accidently press one of the triangles when intending to press a button. A context menu to lock the triangle state would be most welcome.

To a lesser extent, it would also be nice to have on PSplt, but not really critical.

Thanks