MRhythmizer feature requests

[paterpeter]

Hi there,

I have two feature requests for MRhythmizer/MMultiBandRhythmizer

1) More synchronization options: currently, if you sync the tempo to the host, MRhythmizer always aligns the pattern position to the bars of the song. And if I manually set the tempo to the tempo of the song, any time I change the pattern, it starts from the beginning. What I'd like to see are more options for synchronization:
- "Trigger sync": Trigger the next pattern on the next 1/8, 1/4, 1/2 etc. (ie. finer granularity than the current "Next Bar" trigger). Gross Beat can do this, for example.
- "Restart on change": Keep sync-to-host on, but restart the pattern on each pattern change (ie., just like it is now if you set the tempo manually, but with sync-to-host on. It's just a minor simplification for the user)


2) Play the pattern as long as the respective MIDI key is held. When the key is released, immediately return to pattern 1. This is a variation to the current single shot trigger. Of course I can achieve this effect e.g. in FLS by using an envelope controller, but built into MRhythmizer would be nicer.

With those two additions, the following would be easy to setup:
- create a stutter pattern, e.g. always repeat 1/16.
- enable "restart pattern on change"
- set trigger sync to 1/8
- when the track plays, hold the respective MIDI key to achieve a nice on-the-fly stutter effect of the next 1/8 ("The Finger" anyone?)


It would be great to see those additions in the future.

Regards,
Andre

[MeldaProduction]

Hi Andre,

1) Smaller granularities - well, that could be done I guess, but I'm think more like allow "sequence lengths" smaller than the signature. This would leave the minimum as 1/4 (quarter note), but I think that is more than enough.

Restart on change - this is NOT sync with host. Sync with host means that if host is on 3rd quarter in the bar, the plugin is there as well. You want "tempo sync", which could be done I guess. We'll see.

2) MIDI note release - I'll check .

[paterpeter]

Hi Vojtech,
Thanks for your reply.

1) Smaller granularities - well, that could be done I guess, but I'm think more like allow "sequence lengths" smaller than the signature. This would leave the minimum as 1/4 (quarter note), but I think that is more than enough.

Please still consider trigger sync, it's a completely different feature than smaller sequence lengths.

1) I see at least two scenarios where smaller trigger sync values are very useful. As mentioned in my first post, when performing live to ensure that the pattern starts at a proper time value (quarter, 1/8ths, whatever). It is probably useful to allow a small tolerance here: e.g. say the trigger sync interval is set to quarters and the player changes the pattern for example 5% or 10 ms after the last quarter beat then MRhythmizer could still immediately switch the pattern (and set the play cursor to 5% / 10ms into the new pattern of course).

2) When using parameter automation to switch the pattern one could use a continuous controller (like a hardware controller knob) to select the pattern but still ensure that the switch itself takes place at a proper timing value. See e.g. or for example applications of "one-knob-effects".

Restart on change - this is NOT sync with host. Sync with host means that if host is on 3rd quarter in the bar, the plugin is there as well. You want "tempo sync", which could be done I guess. We'll see.

Ah, yes, tempo sync. That's what I meant

2) MIDI note release - I'll check .

Cool!

[plauto]

Hello, I think I found something wrong, perhaps a graphic bug, I do not know, but it would be best that these lines do not exist. Everything indicates that the buffer captures these lines causing intervention.



I have another question related to the grid line display, it seems hard to find the offset (music segment) pretent right to build what is perhaps the possibility of changing the color of the grid line would solve that.

Thank you for your attention.

[MeldaProduction]

Hello, I think I found something wrong, perhaps a graphic bug, I do not know, but it would be best that these lines do not exist. Everything indicates that the buffer captures these lines causing intervention.

Interesting, it seems like a very weird use of the stairs or pulses segments. How did you do this?

I have another question related to the grid line display, it seems hard to find the offset (music segment) pretent right to build what is perhaps the possibility of changing the color of the grid line would solve that.

Thank you for your attention.

Well, I don't really get this. What you mean exactly?

[plauto]

Interesting, it seems like a very weird use of the stairs or pulses segments. How did you do this?

These online translators are not much help in communication, but I believe that you can understand through the moving image:



The other question was about viewing the grid line, it seems too light, that impedes the creation of things...

[MeldaProduction]

Aaaha, thanks, now I understand. I'll take a look at the first one. With the grid lines I'm afraid I'll most likely cancel it, we'll see.

[Grodada]

I support the previous remark Plauto and paterpeter, I would like to see also
several choices of filters and a pitch shifter superimposed on the time's graph or independent.
I also have a problem with the audio engine of the host, which continues after stop
when the plug is set in real time.
Thank,gro D.

[Grodada]

I have a problem, the resampling in Renoise, Reaper and Ableton Live 8 is not working properly, there is a lag in the registration and once registered the effect is not faithful, it is unusable. you have an explanation, all my software is current, on xp 32 bit, thank you for responding.

[MeldaProduction]

I have a problem, the resampling in Renoise, Reaper and Ableton Live 8 is not working properly, there is a lag in the registration and once registered the effect is not faithful, it is unusable. you have an explanation, all my software is current, on xp 32 bit, thank you for responding.

What you mean by that??? What is registration lag???

[Grodada]

not "registration" but "record", sorry is google translation, I will say bounce
or resampling, "lag" of recording, the time effect does not work well after
to record audio tracks.I said it had a license to vst(two or three weeks) and
the website MeldaProduction towards to kvr forum.Voila tout,si c'est pas clair
je peux écrire en français aussi, la captation ou enregistrement du flux audio
passé par le vst n'est pas fidèle, il y a une latence dans l'enregistrement de
l'effet temporel qui décale et fausse l'enregistrement,merci pour votre écoute
, thank you.

[MeldaProduction]

Well, you will have to be more specific, I have no reports of any unproper behaviour so far. So example, send me a project, which doesn't work or something.

[Grodada]

for time setting(stair curve) in the graph (0,-1) to (4,-5), this setting produces silence in the recording, in real time as for the first reading after it is audible.
It will be difficult thing to show you in the export project the "before / after",the best is a video capture software but it crash my pc,if I can provide more details,thank you.

[MeldaProduction]

for time setting(stair curve) in the graph (0,-1) to (4,-5), this setting produces silence in the recording, in real time as for the first reading after it is audible.
It will be difficult thing to show you in the export project the "before / after",the best is a video capture software but it crash my pc,if I can provide more details,thank you.

In that case I believe it is absolutely correct. What you did is that you let MRhythmizer start playing recent quarter notes, but since the playback has just started, there is nothing but silence!