michaelpilyavskiy / reascripts Goto Github PK

Being able to set the minimum linking parameter value down to -100% conflicts with the concept of using the lower range of the 'Macro' control for decreasing the initial offset values.
If you move the 'Macro' knob to 0% and the 'Min' link range to -100% you end up with -200%, if I understand it correctly.

We'll have to think about the scaling a bit more.

Try to manually drag the 'Tune' parameter down one or two octaves and you'll probably notice a problem (assuming you have the script docked to the bottom as I do). As soon as you'll reach the border of the screen the parameter stops moving. Can you change that?
Sure, you can always right click and type if you want a specific big parameter jump, but for rather sensitive parameters like pitch or filter frequencies it's much better to have a continious controller.

Hi. Found an issue in script:
https://github.com/MichaelPilyavskiy/ReaScripts/blob/master/Various/mpl_Align%20takes.lua

Here's the error message:

mpl_Align takes.lua:2181: attempt to call a nil value (field 'BR_Win32_GetPrivateProfileString')

Loading the first DB preset for a track works perfectly. But if you want to switch to another one it just doesn't seem to do anything.

Workaround: use the function 'Clear current database map' and after that load the new DB preset. Then it works.

When you start moving a knob to a certain region and then hit "Ctrl" to make fine adjustments while still holding the mouse key pressed, the parameter jumps to the value you started with when clicking the mouse.
I guess it's intended to press "Ctrl" before clicking on the knob, but it would be really nice if it would also work the other way around.

Hi!

I've got the following problem. I'd like to use align takes for my vocals but when I want to use it on its own or through a selected action shortcut I run into the following error: mpl_Align takes.lua:2221: attempt to call a nil value (field 'BR_Win32_WritePrivateProfileString')

Can someone help me out please?
Thanks a lot!
Ben

(in "Float instrument relevant to MIDI editor" v1.1)

When the track containing the MIDI take has both a send leading to the instrument and a parent track, the script fails to find the instrument from the send.

It's actually looking for sends in parent track instead because take_track is overwritten while looking in the parent tracks.

(I've been able to workaround this by moving the send lookup logic above the parent lookup step, but I don't know if looking in the sends first is the desired behavior)

At the moment, everytime you open Reaper and hit 'New Kit' once or several times, you end up getting the same kits in the same order. Although this is not really super bad, it wouldn't be hard to fix it (I guess).

I don't know which random function you're using, but I guess defining a seed for it is possible. The easiest, quick and dirty solution (that might probably be totally fine here) would be to use the current time of the OS or something similar on startup of the script.

Since the Macro has to know about the parameter ranges of its slaves anyway, can't we use those real values for the 'Min' and 'Max' fields in the link list?
It would be really handy to explicitly say for example that you want the pitch range to be between -12 and +3 semitones instead of trying to translate that experimentally to the percantage scale.

When using # in a marker label (which is the standard CD marker symbol in REAPER), the CUE file should not include it in the track name. e.g. a marker labelled #TrackName should be called TrackName.

selecting Y for yes doesn't seem to work

mpl_RS5k_manager_obj:lua:1637:attempt to call a nil value (global ´BR_GetMediaTrackByGUID´)
I'm using REAPER v5.983/x64

Is it possible to decrease the stepsize for the 'Pad overview' navigation? At the moment you can only move in steps of 8 pads, which is not too bad, but sometimes a bit annoying. Maybe 4 is better? Or even 2?
Ideally one could click and drag to navigate it, but I can imagine this to be complicated to implement. Anyway, it's rather low priority.

THIS IS THE ERROR IM GETTING

Update C;/Users/denni/AppData/Roaming/Reaper/Scripts/MPL
Scripts/Functions/mpl_Various_functions.lua to verision 3.59 or newer

I have the newest version installed!!!!!!!

Hi !

The MIDI CC learn manager displays wrong values if non absolute mode is set.

For eg, MIDI CC9 become MIDI CC 521 in the display.

It would be nice if the learn manager was able to find in what relative mode the CC learning is made,
it would then also fix the wrong CC value display !

Thx for your support !

EDIT: I also just found that the other option of CC learn (work with selected track, work with active FX window etc) also shift the real CC value.

Having this mod displayed in the table will also help !

Best,

Hi,

While tracking down a memory leak bug in ReaPack, I found that your script Randomize Track FX parameters has has two equivalent versions 1.01 and 1.1. As I explained in this post, these are both computed as the same in ReaPack.

1.1beta2 and onward will error out when it finds duplicate (or equivalent) versions to fix the memory leak. I'll also make changes in the indexer to prevent this from happening in the future.

Many solutions are possible depending on how you want to name your versions, but you'll need to manually edit index.xml and remove one of the equivalent versions.

v1.01 and v1.1 cannot co-exist within the same package.

Sorry for the trouble. 😉

When I erase a link it doesn't disappear until I move the mouse outside the link list section.

Hey, how are you? :)
I'm having problem in executing mpl_RS5k manager(background).lua in REAPER. The repository didn't came with this archive, so I copied the code here in github and created an archive with it...but it didn't solve too hahaha
It's appearing this:

Without the archive, just with the files that downloaded with the repository it's appearing this:

My /Functions doens't exist...I had to create it too!
Any ideas how to solve this problem?

Thanks!

The min and max parameters in the link list only update their visible state on mouse release. Which is not really useful for a drag&drop control. It's a bit like driving blindfolded, only being allowed to look when hitting the breaks.

It's probably related to the 'pad replace' issue, because it shows the same symptoms. The names revert when you hit undo, but not the samples.

Hi. Loving the sidechain script.

I wonder if some mods would be possible.

Source being a track named "SIDECHAINER"
Destination being selected track
ReaComp using a preset named "Sidechain"

So that way it can be triggered from a toolbar button. Not having to go to the source track is a cool feat.

Best

Is there any chance of getting the mousewheel scrolling the lists in the 'Macro' and 'Children chain' menu?

When you change the current sample of a pad and then try to undo it, it only undoes the name but not the actual sample. You don't get back the sound you had before.

I'm using Reaper v6.08/x64 on Windows 10, and I have the contents of this entire repository copied to %APPDATA%\Roaming\REAPER\Scripts\MPL Scripts. (of course, upon fetching the individual scripts via ReaPack, at first it complained about the availablility of mpl_Various_functions.lua).

I have a track selected and a different track underneath my mouse cursor and then I call the action via a keyboard shortcut I created. The result: 😢

mpl_Create ReaComp sidechain routing.lua:43: attempt to call a nil value (global 'BR_GetMediaTrackByGUID')

and likewise:

mpl_Create ReaGate sidechain routing.lua:42: attempt to call a nil value (global 'BR_GetMediaTrackByGUID')

Surprised since this is relatively new... I subsequently installed Various_functions as well the way you instruct people to and it has made no difference.

When using time selection, track numbers in CUE file should be relative and not absolute i.e. first marker within time selection should be TRACK 01.

Could you please make the last played pad stand out a bit more? Sometimes I can't tell which pad was triggered last just by looking at it. Especially when using different track/pad colors, the thin border around the pad gets kind of indistinguishable.

Hello there, and thank you very much for your awesome work !

I am trying to install the RS5K manager and I am getting the following exception:
https://github.com/MichaelPilyavskiy/ReaScripts/raw/5b13cc05a34c162031a220db9cd8d7314139ac62/FX%20specific/mpl_RS5k_manager_functions/mpl_RS5k_manager_GUI.lua: HTTP response code said error (22): The requested URL returned error: 502 Bad Gateway

I thought that it might be the issue that the file was missing on that specific commit. But after opening the specific commit I can see that the file exists, it seems to be a GitHub issue.

To demonstrate, if you try to click RAW it returned 502: Failure
https://github.com/MichaelPilyavskiy/ReaScripts/blob/5b13cc05a34c162031a220db9cd8d7314139ac62/FX%20specific/mpl_RS5k_manager_functions/mpl_RS5k_manager_GUI.lua

It seems that this a temporary GitHub issue, now it works properly, just adding it here for refernce in case anyone else has the same problem.

I think it would be useful to have a simple button to clear all current samples. Sometimes users might want to start anew.
Sure, they could just create a new track to have an empty bank again, but I think it's more convenient to add a button like 'Clear kit' or to add it as an option to the right click context menu.

I've always wanted something like this. :)

I'm wondering if it could be possible to add an option only randomize touched parameters? Maybe click on get parameters, touch the ones you want randomized, then click it again to lock randomization only to those parameters?

That way we could make slight modifications from a starting point we already like.

Also I'm not sure how feasible this would be, but one one of the worst things about "randomize" functions in most VSTi's is that they randomize things like the pitch and tuning which basically leads unusable out of tune results.

If parameters containing certain keywords like pitch, tuning, cents, transpose etc. could be ignored for instruments the results are likely to be far better. :)

Melda has an incredible "smart randomize" in all their plugins which is light-years ahead of anything else I've tried and I've always wished there was something similar for third-party VST(i). Much of the "smart" aspect (if I understand correctly) is that it limits the range of randomization based on the values of existing presets. One possibly could be reading a plugin's existing presets (.rpl or .fxb, since they are open standards) and limiting the randomization range to the highest/lowest values of each parameter found in the presets. It would probably be quite a challenge, but thought I'd share the idea anyway...

When using align takes (installed with all the latest SWS actions) I get a script error.
aligntake version 2.23
VariousFunctions 3.55

Reaper version 6.75
64bit

I've tried re-installing aligntake and variousfunctions but same error. The initial error I recieve tells me to "Switch to Full Mode"

Followed by this script error.

Installed using Reapack.
See the video below (deleted in 90 days):

https://streamable.com/ypoion

When copying spectral edits from an item (using "mpl_Copy selected item spectral edits.lua") and pasting it with "mpl_Paste and replace spectral edits to selected item.lua", it seems to only past the first few edits (in my case its always the first seven edits).
Can anyone replicate this?

I'm running Reaper v6.16 on OSX 10.15.7. Scripts run without error messages.

If you link parameters, especially when you have several parameters of the same type (like all pitch), there's no chance of knowing which entry in the list belongs to which pad.
Prepending the name of the pad in front of the parameter name would solve that.

Sometimes when you're moving samples it only moves its name, but the sound remains on the previous pad. Which then looks like an empty pad but it plays sounds unexpectedly.

Unfortunately I couldn't find a pattern to reproduce it reliably yet, but it happened several times by now. Maybe you have some intuition where to look.

Please add an optional widget which changes item playrate.

This should have at least 4 decimal points, so fine changes can be accomplished.

I achieved this on my machine by substituting D_PITCH for D_PLAYRATE in the GUI and Widgets Item scripts, but I wasn't able to work out how to create my own widget, or how to add more decimal places.
I am not a very good scripter :)

Suggestion: if there is no user-defined time selection on running the script, default to entire project length.

Without linking 'Attack' has a range from 0 to 500ms. When linked it goes from 0 to 2000ms. 'Decay', 'Release' and 'Loop' show similar behaviour (with different values though).

By updating ReaScript with Reaper, I get this error on your script:

As the title sais, when moving the 'Macro' knob really slowly it stops updating its GUI. It still continues to sends changing values to its slaves though.

Hi, thanks for this amazing reaper plugin, I want to report two bugs:

1. for Macs, the reapack installation won't work, I'm assuming it's the lacks of Raw folder:
   https://github.com/MichaelPilyavskiy/ReaScripts/raw/master/index.xml

2. Once I installed on my windows laptop, I found the learnt mapping for master track is not showing up in the learnEditor.

Hope these can be fixed, really appreciate your work!

I chop a sample, select all choped items, and call one of the scripts and I get this error:

...tems to RS5k instances on selected track (drum mode).lua:60: attempt to call a nil value (field 'BR_GetMediaItemGUID')