LFO tool for MIDI editor and envelopes

[EvilDragon]

CC version with swing parameter at some point?

[_Stevie_]

I concur :P

[juliansader]

Originally Posted by EvilDragon

CC version with swing parameter at some point?

Of course!

[Bri1]

any chances of a small rhythm library?
could 1 take info from any 1bar midi drum pattern> and get that to work with the lfo tool? be
this is fantastic tool btw!! surely it could be native,with all credits given??

[EvilDragon]

Probably not because these waveforms are algorithmically generated, rather than discrete MIDI events.

[Bri1]

lolz-ok well today is let's make the impossible possible day---like each day-- cc data can be gathered from audio already---surely it's just a simplex convertion thang...
am believing juliansader has the abilty to change possible realities.so be it. =)

[Bri1]

ohh-n while all are learning--music has been algorithmatically generated since it very 1st began

it's all a matter of sequence,timing,tones as most well know.
there is also the ability for programmes to 'learn'- i think you may find this is what some label 'artificial intelligeance'-- but,if used with caution+purified intentions-- ai will,or could,benefit all man/creature/mineral kinds!!
some people have access to matlab-it can learn apparently... > https://en.wikipedia.org/wiki/Machin...ource_software

[dupont]

There are strange behaviors when duplicate pooled AI.
The AI is not refreshed until LFO tool is selected and when moving, AI curves vanish.
Pooled copies of AI are not automatically updated but when the cursor in over LFO tool UI.

https://drive.google.com/open?id=17k...psEZjkAz2cFohq

[juliansader]

Originally Posted by dupont

There are strange behaviors when duplicate pooled AI.

Originally Posted by EvilDragon

CC version with swing parameter at some point?

I have uploaded new versions over the past week, including MIDI editor versions with Swing:

[EvilDragon]

Brilliant! Thank you very much


I assume it is intentional that the envelope version uses different UI colors than MIDI CC version? I would suggest to perhaps tweak the header name of the script window (in gfx.init), for envelope script to say "Envelope LFO" instead of "LFO tool" and for MIDI CC version to say "MIDI CC LFO". This way they'd appear a little more consistent.

For future it might be a cool idea to have a few color themes selectable for both scripts, maybe?


This amount of work is worthy of a beer or two. Donation sent!

[dupont]

Hi,

Great job, duplicated AIs seem OK now.
I noticed a bug with LFO CC.
The first CC at the beginning of the midi item, position 1.1.0, disappears when LFO tool is called.
Perhaps a conflict with Reaper CC quantize ?

https://drive.google.com/open?id=1kZ...w0OVe9cDNuqKJf

[Vagelis]

Oh boy,now we can swing everywhere,thanks!

[juliansader]

Originally Posted by dupont

I noticed a bug with LFO CC.
The first CC at the beginning of the midi item, position 1.1.0, disappears when LFO tool is called.

This is strange... The CC seems to still be there, since its shadow is visible, but somehow the CC is not drawn, or perhaps hidden beyond the left edge of the item.

Could you send me an RPP containing that MIDI item, so that I can try to replicate the issue?

[dupont]

Originally Posted by juliansader

This is strange... The CC seems to still be there, since its shadow is visible, but somehow the CC is not drawn, or perhaps hidden beyond the left edge of the item.

Could you send me an RPP containing that MIDI item, so that I can try to replicate the issue?

If I quantize the CC, the missing CC comes back.

[juliansader]

Originally Posted by juliansader

* Recall AI curves: When working in Automation Items, the script will try to automatically recall the last-used curve, when you re-select a previously used AI. This feature uses AI IDs, so isn't completely reliable and doesn't work when the AI's ID changes, but it is probably the best we can do at the moment. (FR: "Item notes" for automation items.) To reactivate the script and load the AI curve after working the arrange view, just move the mouse across the envelope area or click on any of the other GUI elements.

REAPER v5.976 gave us AI notes, so the LFO Tool can now recall AI curves even if the ID changes, and AIs can freely be moved and copied, even to other projects, without losing their LFO information.

[Eliseat]

Originally Posted by juliansader

REAPER v5.976 gave us AI notes, so the LFO Tool can now recall AI curves even if the ID changes, and AIs can freely be moved and copied, even to other projects, without losing their LFO information.

Hi juliansader,

that's great news as this was the only annoying thing with LFO-Tool. Many thanks for your great work. Its just stunning how easy it is to create nice LFO pattern with your script.

Greetings
Eli

[Vagelis]

Great news Julian thanks a lot!

I'd like to ask you, would it be possible in the future to store-map lfo shapes to different midi keys? Then we could recall-control different lfo shapes with the midi keys, which would give a lot of accuracy for automations.

Here's something similar that is possible in FLstudio:

https://www.youtube.com/watch?v=LBIURosTSSg

[Breeder]

I'm having trouble finding things in LFO code.

When I engage LFO tool, rate is ALMOST 1/4 but not exactly. Where in the code can we change default curve values?

Also, it seems LFO tool doesn't respect the default CC curve shape, that's a real shame

[juliansader]

Originally Posted by Breeder

I'm having trouble finding things in LFO code.

When I engage LFO tool, rate is ALMOST 1/4 but not exactly. Where in the code can we change default curve values?

Also, it seems LFO tool doesn't respect the default CC curve shape, that's a real shame

The LFO code is quite a mess, unfortunately. (IIRC, I actually mention it in my comments in the code, as a warning to the reader.) The script was originally an abandoned, unfinished script by Xenakios, which I then modded and completed.

You can save any curve as "default", and it will then automatically load at startup.

Alternatively, go to the "constructNewGUI" function, and
* in the "GUIelement_RATE" line, change "0.5" to "1/3", and
* in the "GUIelement_TIMEBASE" line, change "0.0" to "1" to start with timebase = beats.

[Breeder]

Originally Posted by juliansader

The LFO code is quite a mess, unfortunately. (IIRC, I actually mention it in my comments in the code, as a warning to the reader.) The script was originally an abandoned, unfinished script by Xenakios, which I then modded and completed.

You can save any curve as "default", and it will then automatically load at startup.

Alternatively, go to the "constructNewGUI" function, and
* in the "GUIelement_RATE" line, change "0.5" to "1/3", and
* in the "GUIelement_TIMEBASE" line, change "0.0" to "1" to start with timebase = beats.

Awesome, thank you!!!!!

P.S.
I can't find a way to save curve as default?

[Tarrasque]

Hi. Complete Reaper newbie here.

I just installed ReaPack and then this tool through it.

How do I activate it?

[juliansader]

Originally Posted by Tarrasque

Hi. Complete Reaper newbie here.

I just installed ReaPack and then this tool through it.

How do I activate it?

Once you have installed a script, it will be listed in REAPER's Actions list along with all the native actions, and you can activate and use it in the same way that you do native actions: You can select and run it directly from the Actions list, or you can assign a keyboard shortcut to the script (so that the script runs whenever you press the shortcut keys), or you can link the script to a toolbar button (so that the script runs when you click the button).

[Tarrasque]

Originally Posted by juliansader

Once you have installed a script, it will be listed in REAPER's Actions list along with all the native actions, and you can activate and use it in the same way that you do native actions: You can select and run it directly from the Actions list, or you can assign a keyboard shortcut to the script (so that the script runs whenever you press the shortcut keys), or you can link the script to a toolbar button (so that the script runs when you click the button).

When I tried to launch the tool I first got a "missing stuff" error (don't remember what) that I fixed via ReaPack.

Now I get an error regarding "SWS/SM extension not installed". On the website I see only Windows binaries that technically should work with WINE (I'm using Linux).

Are they actually working or should I search somewhere elase for a Linux binary?

[_Stevie_]

https://forum.cockos.com/showthread.php?t=210733

[juliansader]

The SWS Linux binaries are not hosted on Landoleet anymore, but can be downloaded from the SWS website, among the pre-releases.

[GonZ]

Hi, it's a very nice tool, I love it! I'm wondering, is there a way to turn off record on undo history? Thanks!

[mozart999uk]

This is an amazing script. So flexible!!!!

Is there a way to enlarge the font?

[Rumario]

What I have to do that it works in the midi editor?

[gobywan]

Originally Posted by Rumario

What I have to do that it works in the midi editor?

You just need to run the scripts beginning with "Script: js_LFO Tool (MIDI editor version" somehow - I have the "last clicked lane" ones as buttons on a toolbar, but you can also set up keyboard shortcuts for the "lane under mouse" ones if that's your preference.

A request for juliansader: could you add a way to change the minimum and maximum timebase values somewhere in the UI? Two whole notes as the minimum period is a good default - I'm just looking to use it a bit differently. I've manually changed them in all 6 MIDI editor scripts, but that was super tedious, I had to look through this thread to figure out how to do it in the first place, and those changes won't stick around if you push a new update for the scripts. I'd much prefer a way to do it through the script's interface, preferably one that will save my settings and apply to all 7 script files at once. (Apologies if this isn't possible or if it's too complicated to bother with, I know next to nothing about how Reaper scripts work.)

[Vagelis]

Hi Julian, I found a bug with lfo tool and take pitch envelope. While it's working fine with rest take envelopes, with take pitch it doesn't use the whole pitch range.

[juliansader]

Does this happen only in this one take, or in other projects and takes too?

Could you perhaps send me a minimal project with the problematic take and pitch envelope?

[Vagelis]

Originally Posted by juliansader

Does this happen only in this one take, or in other projects and takes too?

Could you perhaps send me a minimal project with the problematic take and pitch envelope?

But this happens with every project or take only with pitch envelope. I tried with samples from different folders too.

I'm on Win 10 64bit, Latest Reaper version

[juliansader]

I found the source of the problem!

When the Pitch envelope's range has been changed, the script doesn't pick it up. I'll try to find a solution.

[Vagelis]

Originally Posted by juliansader

I found the source of the problem!

When the Pitch envelope's range has been changed, the script doesn't pick it up. I'll try to find a solution.

All right great news! Yes makes sense, my range is up to 36 semi.

[juliansader]

I've uploaded v2.15 of the script, which should hopefully fix the bug.

[Vagelis]

Originally Posted by juliansader

I've uploaded v2.15 of the script, which should hopefully fix the bug.

Sorry the problem still happens with the pitch range set to 36 semitones
I changed the pitch range to default -3 to +3 semitones, then the envelope was being shown with full range on take, with the lfo amplitude set to maximum.

My pitch range setting is up to 36 semitones, did you try it with this range on your setup too and it worked?

[Vagelis]

Actually with the newest lfo version i found another bug which was not there previously.
The problem is that i can't trigger properly the lfo by touching the take envelope.
And when i'm adjusting the lfo parameters, the changes on the envelope are not updated in real-time. I have to drag an envelope point to show up, but if i drag an envelope point again it resets the lfo adjustments to the previous shape the envelope was before. And it goes like this in cycle.

P.S this is happening only with take envelopes and not with track envelopes.

Here's a gif:

[juliansader]

Actually with the newest lfo version i found another bug which was not there previously.

Whoops! Please try the new v2.16.

Sorry the problem still happens with the pitch range set to 36 semitones

Hopefully the hotfix for the regression also solves this problem. It works perfectly on my side.

* When you edit the problematic envelope, does the UI say "Pitch" at the bottom? (Which indicates that the script detected a pitch envelope.)

[Vagelis]

Originally Posted by juliansader

Whoops! Please try the new v2.16.

Hopefully the hotfix for the regression also solves this problem. It works perfectly on my side.

* When you edit the problematic envelope, does the UI say "Pitch" at the bottom? (Which indicates that the script detected a pitch envelope.)

Wow it works on your side? I tried again the latest update, I can trigger the lfo as I could do previously but still it didn't solve the issue with the pitch range here
Really sad because Lfo tool is one of my basic tools and pitch envelope is really important for my work.

[juliansader]

Ah, thanks for the GIF! I see what the problem is: you're using the Pitch settings in global Preferences whereas I was using the per-envelope settings that you get when right-clicking on an envelope. (I actually forgot about the settings in Preferences. REAPER has so many settings!)

I will try to figure out how to read those global Pitch settings.