MPL QuantizeTool - align anything to anything

[foxAsteria]

Originally Posted by mpl

2.0pre5 is pretty much working, though it still bad at midi events calculation (working on this).
I think, search area is "include within" (will rename it). If "exclude within" means ignore targets out of dest and source position difference, then I can also implement it, as well as maximum difference limit.

Ok, I'll test it out shortly. Thanks, mpl! As far as "search area," wouldn't "anchor detection range" be pretty accurate? Or how about "max distance?" In ME quantize dialogue, it's called "only quantize range," but I find that a bit confusing. "Include/exclude within" are also very clear. Or are you saying you will have 2 dials to set the range (min/max)?

[pingosimon]

"Search area" is clear enough, though instead of measuring by beats, I would measure it by percent.

I just tried again, and "Search area" doesn't seem to have any effect on stretch markers. My anchor point is "Current grid" (and I tried different sizes), target is stretch markers, action is position-based alignment.

[G-Sun]

Originally Posted by mpl

wasn't much responses here.

Sorry about that. I'll take latest for a spin.

[G-Sun]

Testing v2pre5 now.

Questions:
- I don't identify names as "Anchor points" and "Target" at once. (Although I know the concept of the tool quite well)
Suggest "Reference" and "Quantize" (but Target is ok as well)

After some fiddling I understood getting reference and target.

- Stretch markers in time selection
is that supported yet?
- Reset stretch-markers in item/time-sel ?

[G-Sun]

Bug:
Midi to stretch-markers



Q2 was also doing this thing on a reference track

[G-Sun]

Bug: For a trimmed item Q2 gets reference-points in hidden parts
(stretch-markers

Maybe 1st and last hidden is a good idea, but not the rest

[G-Sun]

Please have a look here:



Tr#2: Ref
Tr#3: Target

Look at SM 2 and 3 in target.
Here a reference for SM2 is missing.
SM3 is correctly moving to ref-point, but SM2 is moving unwanted.
Preferably it should keep it's relative position between SM1 and SM3.

Notice also above bug for ref-item.

[mpl]

Originally Posted by G-Sun

SM3 is correctly moving to ref-point, but SM2 is moving unwanted.

SM2 moving to closest anchor point, so all is expected here. Use "Search area" for this case.
mpl_AlignTakes should handle such material btw.

Edit: probably a case of missing first anchor point+non-zero take offset. Attach here simple project to reproduce and QuantizeTool preset you used (Menu/Dump current preset).

[G-Sun]

Originally Posted by mpl

SM2 moving to closest anchor point, so all is expected here.

It's expected, but always unwanted
-nomatter if ref. is SM, groove or midi
(exception being polyphonic midi)
It's not a bug, but could make the tool smarter

[G-Sun]

Originally Posted by mpl

Edit: probably a case of missing first anchor point+non-zero take offset. Attach here simple project to reproduce and QuantizeTool preset you used (Menu/Dump current preset).

Here's a project:
https://stash.reaper.fm/34880/Q2.zip

Here the QTool failed to quantize target, but produced the bugs as above.

Note that my system has some path issues due to an OS migration.

[mpl]

QuantizeTool 2.0 version is on the ReaPack now.

Small amount of replies here while developing, it seems almost noone interested and using tool like that, so I silently pushed next version to the GitHub and see how it goes...

Here is a short changelog of what was changes (spoiler: everything).

+ Complete script rebuild.
+ GUI: split into 4 sections: target, anchor points, action, and contol area
+ Preset: all objects handling follows external or last saved/touched preset
+ Preset: load/save from/to file/list
+ Preset/Action/Position-based Align: deductive brutforce engine
+ Preset/Action/Position-based Align: independent position/value sliders
+ Preset/Action/Position-based Align: show target points or anchor points
+ Preset/Action/Initialization: various options
+ Preset/Align/AnchorPoints/Groove: new FNG Groove Tool parser
+ Preset/Align/AnchorPoints/Groove: save as .rgt in /Grooves
+ Preset/Align/AnchorPoints/Groove: list/show /Grooves
+ Preset/Align/AnchorPoints/Groove: allow to draw pattern manually, autosave to /Grooves/last_touched.rgt
+ Preset/Align/AnchorPoints/Groove: change length (in beats)
+ Preset/Align/AnchorPoints/Edit cursor
+ Preset/Align/AnchorPoints/Project Markers
+ Preset/Align/Items: obey snap offset
+ Menu/Developer actions to dump internal data
+ Preset/Create: create new objects based on existed
+ Preset/Align/EnvelopePoint: support for take envelopes

[G-Sun]

Originally Posted by mpl

QuantizeTool 2.0 version is on the ReaPack now.

Small amount of replies here while developing, it seems almost noone interested and using tool like that, so I silently pushed next version to the GitHub and see how it goes...

Here is a short changelog of what was changes (spoiler: everything).

Thank you! I will test a little later.

[daxliniere]

Thanks Mikhail! Will check it out, thanks very much.

[matv]

Thanks!

[timothys_monster]

Thanks so much for your effort! Will give this a try in my next mix. Is there any video or gif out there, kind of like "getting started with the Quantize Tool"?

[mpl]

Originally Posted by timothys_monster

Thanks so much for your effort! Will give this a try in my next mix. Is there any video or gif out there, kind of like "getting started with the Quantize Tool"?

I'm not good at making videos unfortunately.
Basic usage is:
1) Setup preset
2) if you are in align mode:
2a) click green button to collect anchor points
2b) blue button to collect targets
2c) red button to calculate output positions/values
2d) move left knob to see results

Bottom green/blue buttons is for showing points as markers. Bottom red button is for applying preset as is (with current slider values, it useful to see how preset will be applied on QT initialization if you disable GUI).

[G-Sun]

I get:

mpl_QuantizeTool_obj.lua:1663: attempt to perform arithmetic on a nil value (field 'exe_val4')

on startup of script.

[mpl]

Probably coming from pre-releases. Should be fixed for 2.01

[dukati]

Are there any videos showing how to use this tool properly? Looks amazing.

[foxAsteria]

Originally Posted by dukati

Are there any videos showing how to use this tool properly? Looks amazing.

No, but it's pretty easy. Target is what gets moved to the anchor points, and you can have the action run manually or right away in the options. Just ignore the ones that don't apply, since it can do a lot of different stuff.

[bhuether]

Hi, trying to get started with that is package, but I am getting this error:

Alert

/REAPER/Scripts/MPL Scripts/Functions/mpl_Various_functions.lua missing

I don't see a Functions folder. I see a Various folder. Maybe a script is pointing to an invalid path?

Also, is there a step by step setup description? I am new to the customs actions side of Reaper. What I did was synchronize packages, installed QuantizeTool. Then under Actions I see 4 actions related to this tool such as

Script: mpl_Quantize Tool (background).lua
Script: mpl_QuantizeTool preset - (MPL) Align selected items to edit cursor.lua
Script: mpl_QuantizeTool preset - (MPL) Create selected envelope points from selected items.lua
Script: mpl_QuantizeTool preset - default.lua

I am running this on MAC Sierra with latest Reaper, latest SWS, latest Reapack.

thanks, Brian

[nofish]

You also need to install Various_functions package from ReaPack for Quantize Tool to work I think.

[Eliseat]

Originally Posted by mpl

QuantizeTool 2.0 version is on the ReaPack now.

Small amount of replies here while developing, it seems almost noone interested and using tool like that, so I silently pushed next version to the GitHub and see how it goes...

Here is a short changelog of what was changes (spoiler: everything).

Hi mpl,

I tested your previous version which didn't work for me as it did not count the strechtmarkers right. But your new version fixed this. And I have to say its a pretty cool tool with a lot of potential. Maybe people don't get in the first place what its all about as I also thought this script doesn't look so important because we already have quantization in Reaper. But now I realized how useful this can be.

Great idea, great implementation. Many thanks for your efforts.

[sinkmusic]

Originally Posted by mpl

Small amount of replies here while developing, it seems almost noone interested and using tool like that.

Hi, MPL
I am very interested, and I think that many people are
Thank you for this new version !

Maybe it's just that it is a bit more complicated to run, as opposed to a native solution (i mean, it takes several steps before even being able to run it, and it can be a bit frightening : not everyone has Reapack running, not everyone knows how to handle the Github content, not everyone knows how to run a script, etc).

I went to Reapack, installed it, installed your Quantize Tool v2, but i get an error message ("/REAPER/Scripts/MPL Scripts/Functions/mpl_Various_functions.lua missing")

[xpander]

Originally Posted by sinkmusic

I went to Reapack, installed it, installed your Quantize Tool v2, but i get an error message ("/REAPER/Scripts/MPL Scripts/Functions/mpl_Various_functions.lua missing")

Same here. I didn't use ReaPack, just manual install for all the files. But even when creating the separate Functions folder and placing mpl_Various_functions.lua inside, I get the same nag.

[Eliseat]

Originally Posted by sinkmusic

Hi, MPL
I am very interested, and I think that many people are
Thank you for this new version !

Maybe it's just that it is a bit more complicated to run, as opposed to a native solution (i mean, it takes several steps before even being able to run it, and it can be a bit frightening : not everyone has Reapack running, not everyone knows how to handle the Github content, not everyone knows how to run a script, etc).

I went to Reapack, installed it, installed your Quantize Tool v2, but i get an error message ("/REAPER/Scripts/MPL Scripts/Functions/mpl_Various_functions.lua missing")

Hm, it seems you only installed the script but not mpl's whole package. I have no idea if this was an installation error. You can check if the file is there by going in menu: options/show Reaper resource path ... Then open the scripts folder/mpl_scripts/functions. If this file or directory doesn't exist you should redownload mpl's package.

Go to Extensions/ReaPack/Import repositories and enter the following URL:

https://github.com/MichaelPilyavskiy/ReaScripts/raw/master/index.xml

Then synchronize the packages and download everything from mpl. I never had problems with that because I always download everything. The files are small and the don't disturb in any way even if you don't use most of them.

Hope you get it to run properly.

Eli

[sinkmusic]

Thank you, Eliseat, that is very helpful

(By the way, it kinda proves my point that having MPL -and others- stuff installed and running is not very user friendly, and might be one of the reasons why there is not more talk about it. I thought Reapack was some kind of automated process for installing and updating scripts and extensions ?)

[Eliseat]

Originally Posted by sinkmusic

Thank you, Eliseat, that is very helpful

(By the way, it kinda proves my point that having MPL -and others- stuff installed and running is not very user friendly, and might be one of the reasons why there is not more talk about it. I thought Reapack was some kind of automated process for installing and updating scripts and extensions ?)

Yes, that's true. For people coming from more compact and user friendly software its sometimes a hassle to achieve simple things. You not only have to solve your problems with scripts you also have to find a way to install them. Though the procedure - once internalized - is pretty easy especially with reaPack.

I recommend to always install all ReaPack stuff and synchronize it often to avoid problems like missing parts of a script. And yes most people are afraid to dig deeper into this functionality because they don't have their mind open to follow lots of steps to get a script. But the effort is worth it. Maybe those things should be a bit more user friendly. Sometimes it is better to just show a few animated gifs with the instructions than writing steps in complicated sentences.

Anyway. I hope you got it to run properly.

Btw: It could be a nice feature to let reapack update (synchronize) automatically at every start (or weekly). At least as an option.

[mpl]

I added basic "Getting started" pdf to the QuantizeTool metapackage:
https://github.com/MichaelPilyavskiy...%20started.pdf
Not sure it is completely filled though. Any suggestions welcome.

Various_Functions is mentioned in a first post. It is a must have packge to make it work. Reapack currently doesn`t allow to handle such thing (using functions package script relations outside main script folder).

[sinkmusic]

Thank you very much, MPL !

[bhuether]

Hi MPL, I used your script to accomplish what I posted here:

https://forum.cockos.com/showthread.php?p=2064190

Your script, along with EEL transients to stretch markers script did the trick!

Really nice work! My only comment is that when I select a MIDI track as anchors using note on, it shows 1 extra detection. SO if I have 5 MIDI notes, it shows 6 detections. But that doesn't seem to affect the alignment with stretch markers. So all seems good!

Огромное спасибо!


Brian

[mpl]

Originally Posted by bhuether

Hi MPL, I used your script to accomplish what I posted here:

https://forum.cockos.com/showthread.php?p=2064190

Your script, along with EEL transients to stretch markers script did the trick!

Really nice work! My only comment is that when I select a MIDI track as anchors using note on, it shows 1 extra detection. SO if I have 5 MIDI notes, it shows 6 detections. But that doesn't seem to affect the alignment with stretch markers. So all seems good!

Yep, I hopefully fixed wrong AP/Targets count (in your case extra point is all-note-off message at the end of any midi item in reaper, it is always ignored for output calculation in QT).

[bhuether]

Hi MPL,

One thing I might recommend is add button to automatically align anchors with targets (as opposed to turning knob), with option to specify %. So 10% means add 10% variation to their alignment, etc.

thanks, Brian

[mpl]

Originally Posted by bhuether

Hi MPL,

One thing I might recommend is add button to automatically align anchors with targets (as opposed to turning knob), with option to specify %. So 10% means add 10% variation to their alignment, etc.

thanks, Brian

Bottom red button is something like "apply current preset", it obeys knob values.
You can also "virtually" hit this button on initialization by checking "Action/Apply action on init" in preset configuration. Knob values are stored in preset.

[bhuether]

Hi MPL,

What I mean, is to have a button that has start of each MIDI Note On and Each Marker align to be the same. Or maybe that amounts to turning the knob all the way up and then doing as you suggest.

thanks, Brian

[bhuether]

Hi MPL,

Here is an example. I recorded a guitar part. Then I have MIDI part with same notes. The timing between the two is off, but not to an extreme. I have them off to this extent just to confirm that this sort of test case will work.

What I think should be doable is for the audio markers and MIDI note ons to align. I have anchors and targets properly detected, but notice how when I start dialing up the align knob, that the 4th MIDI note starts moving to the left, even though the 4th audio marker is to the right.

Ultimately, would be great to align these 11 audio markers and the 11 MIDI note ons, with click of a button, or by turning the align knob all the way up.

thanks! Brian

[mpl]

Originally Posted by bhuether

Hi MPL,

Here is an example.

Ok it seems you need an ordered quantize (align by point ID rather then search closest point). It was planned previously, but not mentioned by anyone during developing. It will be implemented in next version as separate type of action or as a parameter for Position-based alignment (not sure yet how it goes better in the code).

Also it is strange nobody mentioned inverted color bug for OSX.

[bhuether]

Hi MPL, Yes that would be great. Surprised no one else has asked for such a feature. I often like to double my recorded guitar parts with MIDI, where I adjust the MIDI to the guitar. So this sort of feature would be great!

regards, Brian

[_Stevie_]

Not sure if it's already possible, but it would great if we could trigger presets with shortcuts.

[mpl]

Originally Posted by _Stevie_

Not sure if it's already possible, but it would great if we could trigger presets with shortcuts.

It is possible, see first post or Menu/Manual in script GUI.