fingers' extension updates

[fingers]

fingers' extension is now integrated into the upcoming SWS extension. For a beta go here:
http://code.google.com/p/sws-extension/downloads/list

If you are after 0.1.2 then download:

https://stash.reaper.fm/v/7166/finger...on_012_x64.zip

or

https://stash.reaper.fm/v/7165/finger...on_012_x86.zip

Updates:

Latest version is in

There was a 0.1.1... I sent it to Subz and have since changed a couple of things so jumping to 0.1.2.

New in 0.1.2:
- Added MIDI hardware emulation actions
- Added python scripts so selected MIDI note groove actions can be run from MIDI editor
- Fixed x64 installer issues

New in 0.1.0:

General:
- most actions now work or work better with tempo and time
signature changes

Grooves:
- updated Groove tool which now has a section in the action
list to allow you to pass key commands through to the main
window.
- grooves applied using the groove tool do not override the
current groove stored. This allows you to store a groove in
memory while still applying any saved grooves
- groove tool dialog format has been rearranged and more features
added. It now has the ability to get user grooves, apply a
groove and save the stored groove.
- groove tool can stay on top of other windows
- better groove quantize algorithm. Fixed some edge cases.
- can now apply and get grooves to selected MIDI notes in the active
editor
- Guido's logic grooves now in installer
- Groove tool folder set to folder where you installed the grooves
by default
- Groove markers now saved in project so they can be toggled off
if you save your project with them on

Actions:
- Legato selected media items (modify length only or modify play rate)

MIDI:
- don't clear text events from midi takes.

I have probably missed something, but you get the general idea
Some actions have been renamed but the command ID is still the same so
won't break any macros.

Most of the work went into improving the MIDI handling. This not only
fixed a lot of the issues with the previous extension releases but opens
up the doors to a lot of cool MIDI stuff. MIDI actions only works with
in-project MIDI items, but this is detected and in some cases you will
be asked whether you want to convert the items.

This has been tested prior to the release a lot more than other releases.
Thanks to Subz, musicbynumbers and Jason Brian Merrill for testing and
feedback.

Requires Reaper v3.651 or above.

0.0.8:
- Now with a friendly installer!
- Groove Quantize: Fixed bug when removing same pitch duplicates in midi items
- Groove Quantize: Packaged Subz grooves in installer
- Version action
- now called reaper_fingers.dll deletes both reaper_FNG_Extension.dll and reaper_FNG_Extension_x64.dll

0.0.7:
- Groove Quantize: Fix for Windows 7 when applying grooves to midi
- Groove Quantize: Added Groove dialog to enable you to load grooves in a folder by double clicking
- Groove Quantize: Fix for ghost midi items. Will now apply groove but warn prior as it converts them to in-project items.
- Groove Quantize: Fix for multiple different channels in one midi item
- Groove Quantize: Can apply groove to active take only, no longer kills other takes
- Groove Quantize: Fix for items sometimes jumping ahead by the size of the groove
- Untested 64 bit build (let me know!?)
- New envelope actions to compress / expand around the midpoint between the min and max selected points
- Midi: increase/decrease velocity actions
- Media Items: time stretch / compress items actions
- Action: - deselect items that do not start in time selection
- Action: - move selected item(s) to edit cursor (different to SWS one)

There are two versions in the zip the x64 one is postfixed with x64. Only copy the one you need to your Reaper plugins folder.

As usual, use at your own risk... let me know of any problems.

0.0.6:
Most work went into getting midi quantizing working properly. It now works at multiple rates, multiple channels, with overlapping items, it truncates overlapping items, if two notes of the same pitch end up being in the same position the longer note wins. If a midi item has only one note and it starts with that note then the whole midi item gets moved rather then the note inside. I have tested this a fair bit, the only test that fails is text events which seem to get lost.

There are also some envelope actions. Shift selected points left, right a 16th/32nd, shift points up/down, shift left/right points up/down.

Finally, I added an action to insert a midi note at pitch C4 of size 32nd of a bar, plus commands to shift the pitch of midi items up/down an octave/semitone from the arrange view. There is also an action to set the name of the midi item to the first note of the midi item.

So you can now do some simple midi note sequencing from the arrange view with grooves.

[Subz]

downloading to test midi grooves now

thank you!!!

[Subz]

weeeee

its looking good with midi notes on the same key

i did find a bug though!

if you apply a groove to a midi clip with the midi editor open, reaper will crash,

will check some more

thanks again

Subz

[musicbynumbers]

Truly superb!!!

just tried it out now, works fantastically!!!

will donate something for this!

[jedstar2000]

Nice update .

Originally Posted by fingers

Finally, I added an action to insert a midi note at pitch C4 of size 32nd of a bar, plus commands to shift the pitch of midi items up/down an octave/semitone from the arrange view. There is also an action to set the name of the midi item to the first note of the midi item.

So you can now do some simple midi note sequencing from the arrange view with grooves.

Great new features . The add note is a great one for me ,you know you can already pitch Midi items up and down using actions. I use this quite allot (RusKo style) or do you mean you can pitch the note inside the item up/down from the arrange window ,will have a play

On a side note have you by chance looked at the inline editor if so is it possible to have an action that focuses the editor.

Many thx Jed

[musicbynumbers]

Just been trying it all out and very nice

have you found an easy way to legato gaps in selected items? not just by extending length but also by time stretching?

those two commands would be killer

so one would adjust the end of each item to the start of the next without time stretching and the other would do the same but with.

I know we have this in the quantize controls but it forces yoo to have to quantize at the same time.

Such a good set of commands you have here though!

[fingers]

Hey Subz, can you send me the offending midi file. I ran tests with an open midi editor while playing, recording etc and can't get it to crash. May not be to do with the midi editor.

[Subz]

Originally Posted by fingers

Hey Subz, can you send me the offending midi file. I ran tests with an open midi editor while playing, recording etc and can't get it to crash. May not be to do with the midi editor.

if you enable "reuse MIDI editor for other items" in the midi editor options drop-down then you should be able to reproduce the crash

with this option disabled reaper dose not crash

for now i'm using the secondary editor setting (as this option also dose not crash )

i also have a FR/idea (REMOVED AS ITS ALREADY THERE)

Subz

EDIT: the attached edit will also crash if you apply a groove, it seems to be related to folder tracks & there sub tracks,

[musicbynumbers]

subz I might have misunderstood but we already have a move media up or down command

not tried it on multiple tracks though,

[Subz]

Originally Posted by musicbynumbers

subz I might have misunderstood but we already have a move media up or down command

not tried it on multiple tracks though,

Ahhh i found it

thanks

FR edited

Subz

[jamieskeen]

Thanks so much for continuing to work on this one!!!!

[gofer]

That's awesome stuff. I'm blown away by the actions to move envelope points. Those that are named with 'shift...' do a thing I have never seen before, check them out with a waveform-style envelope, they tilt the shape. Wow.

I also dig that neighbor points won't stop the movement when using the 'move left/right' actions.

Thanks a lot for doing those, they work wonderful.

Do you think actions to compress/expand the amplitude of an envelope's shape (not talking about 'envelope point shapes' here, but rather the difference between highest and lowest selected values), would be doable? That would be a thing often asked for.


I would so like to use the 'point move' actions with MIDI rotary encoders instead of keys ( I managed to "hack" the data sent by them, so I can assign separate actions for left- resp. right turn), but run into problems there. The actions are fast enough to keep up with qwerty key repeat, but not with the MIDI data stream that can come from an encoder. If the rotary is moved too fast, the messages seem to go into a buffer that is processed until the end, long after I stopped turning the knob. All I can do is sit there and watch the point wander to and fro until the last message is processed.
That's not a problem with your actions only and I acknowledge that they are not designed to be used like that, but

Is it theoretically possible for actions to be aware when user input stops and then stop processing that input buffer immediately?


If you don't have the time or aren't inclined to think about it, then never mind, just ignore that question. I should ask somewhere else probably, just taking this opportunity .

Thanks again.

[fingers]

Originally Posted by Subz

if you enable "reuse MIDI editor for other items" in the midi editor options drop-down then you should be able to reproduce the crash

with this option disabled reaper dose not crash

for now i'm using the secondary editor setting (as this option also dose not crash )

i also have a FR/idea (REMOVED AS ITS ALREADY THERE)

Subz

EDIT: the attached edit will also crash if you apply a groove, it seems to be related to folder tracks & there sub tracks,

I still can not get this to crash. What sort of groove are you applying. Can you save it and post it? Thanks.

[Subz]

Hi

try this groove,

i will dig deeper this end

also a few FNG commands crash reaper here if i apply them to sub folder tracks,

off to check if its related to the SWS snapshots i use to hide folder tracks in the sequencer,

Subz

[fingers]

Originally Posted by gofer

Do you think actions to compress/expand the amplitude of an envelope's shape (not talking about 'envelope point shapes' here, but rather the difference between highest and lowest selected values), would be doable? That would be a thing often asked for.


I would so like to use the 'point move' actions with MIDI rotary encoders instead of keys ( I managed to "hack" the data sent by them, so I can assign separate actions for left- resp. right turn), but run into problems there. The actions are fast enough to keep up with qwerty key repeat, but not with the MIDI data stream that can come from an encoder. If the rotary is moved too fast, the messages seem to go into a buffer that is processed until the end, long after I stopped turning the knob. All I can do is sit there and watch the point wander to and fro until the last message is processed.
That's not a problem with your actions only and I acknowledge that they are not designed to be used like that, but

Is it theoretically possible for actions to be aware when user input stops and then stop processing that input buffer immediately?


If you don't have the time or aren't inclined to think about it, then never mind, just ignore that question. I should ask somewhere else probably, just taking this opportunity .

Thanks again.

I like the compression / expansion idea. I did play around with something similar but didn't quite get it right. It is certainly doable. Horizontal and vertical compression / expansion of points would be quite cool.

As for using from midi. I haven't really explored using midi cc input, so don't really know the answer.

[fingers]

Originally Posted by Subz

Hi

try this groove,

i will dig deeper this end

also a few FNG commands crash reaper here if i apply them to sub folder tracks,

off to check if its related to the SWS snapshots i use to hide folder tracks in the sequencer,

Subz

Still no crashing Some reproducible steps would be great if you have time.

[Subz]

Originally Posted by fingers

Still no crashing Some reproducible steps would be great if you have time.

OK i just trashed my ini & all works as expected

so i will go through a process of elimination rebuilding my ini

thank for your time & the plug-in

Subz

[gofer]

Thanks fingers, nevermind. As all actions that are not marked as MIDI CC do that, I guess it would need separate actions to handle the input buffer (or something along that line).
Guess I can forget about my rotary modification and have to wait for more MIDI CC actions to come up.

[fingers]

Originally Posted by Subz

OK i just trashed my ini & all works as expected

so i will go through a process of elimination rebuilding my ini

thank for your time & the plug-in

Subz

Cool. Good to know it is okay now.

[Subz]

Originally Posted by fingers

Still no crashing Some reproducible steps would be great if you have time.

if you apply the groove twice dose it crash?

i renamed my hole reaper/roaming folder,(making Reaper like first install) open reaper, add a track, draw a midi clip, add some random notes anywhere in that clip, load the XT2 50% swing template i posted a few posts up, hit apply groove (all works as expected) hit apply groove again & reaper will crash,

Win7 Reaper 3.35

can you reproduce this?

Subz

[Subz]

attached is a simple reaper ini,

when it asks you if you want to select a audio device just hit no,

make 6 tracks & make the top 5 in to one folder (so 1 folder track with 4 track inside it) & a track by its self,

draw a clip in to a track inside the folder, add randum midi, load xt50% groove apply, it crashes here

i hope this helps?

i'm off to test in XP (may be a win7 thing?)

Subz

[Jeffos]

Originally Posted by gofer

As all actions that are not marked as MIDI CC do that, I guess it would need separate actions to handle the input buffer (or something along that line).
Guess I can forget about my rotary modification and have to wait for more MIDI CC actions to come up.

gofer, not sure I have correctly understood, but, if so: we'd like to.. but 3rd party extensions can't yet define midi CC actions. Tim has entered a FR about that (http://forum.cockos.com/project.php?issueid=1465, 39 votes and not elevated !?)

[fingers]

Originally Posted by Subz

if you apply the groove twice dose it crash?

i renamed my hole reaper/roaming folder,(making Reaper like first install) open reaper, add a track, draw a midi clip, add some random notes anywhere in that clip, load the XT2 50% swing template i posted a few posts up, hit apply groove (all works as expected) hit apply groove again & reaper will crash,

Win7 Reaper 3.35

can you reproduce this?

Subz

Weird. I can't actually, I have 3.35 and Win XP. I can keep on applying a groove while playing or recording on another track.

[fingers]

Originally Posted by Subz

attached is a simple reaper ini,

when it asks you if you want to select a audio device just hit no,

make 6 tracks & make the top 5 in to one folder (so 1 folder track with 4 track inside it) & a track by its self,

draw a clip in to a track inside the folder, add randum midi, load xt50% groove apply, it crashes here

i hope this helps?

i'm off to test in XP (may be a win7 thing?)

Subz

Still can't crash mine.

[Subz]

as i suspected!

WinXP works flawlessley

but win7 is crashing & not always doing to correct groove?

i have tested on 2 win7 pc's & one XP, both win7 pc's crash (allot)

any other win7 users what to help test?

anything i can do to help fingers let me know

Subz

EDIT:: just to say thanks so much for this plugin!! on XP its perfect for my needs (& Quick)

i will just go back to 0.4 on win7 for now

[fingers]

Originally Posted by Jeffos

gofer, not sure I have correctly understood, but, if so: we'd like to.. but 3rd party extensions can't yet define midi CC actions. Tim has entered a FR about that (http://forum.cockos.com/project.php?issueid=1465, 39 votes and not elevated !?)

You can do this with the KbdSectionInfo struct which you register with "accel_section". You get your own little section in the action list as well. Haven't done too much testing but I have got it printing out a number from 0 to 127 from my midi controller

[Subz]

tested 3 win7 box's & 2 XP box's now (got a few peeps here with laptops )

tests are consistent Win7 crashes winXP works flawless!

Subz

[Jeffos]

Originally Posted by fingers

You can do this with the KbdSectionInfo struct which you register with "accel_section". You get your own little section in the action list as well. Haven't done too much testing but I have got it printing out a number from 0 to 128 from my midi controller

humm.. that would mean Tim was drunk when he entered the FR ? or there's a limitation somewhere? Not the best place to continue this discussion, but yeah!! just had a look to accel_section in reaper_plugin.h, it indeed seems do-able (and with relative mode and stuff!!) I'm gonna test that.. cool tip, fingers!

[fingers]

@ Subz I don't use windows 7, but I'll try to figure something out.

[Subz]

Originally Posted by fingers

@ Subz I don't use windows 7, but I'll try to figure something out.

thank you for your time!!!

this plug-in is great!!!

i hope your able to work with someone to get all os's working

if your anywhere near reading (UK) i can lend you a win7 laptop for a few weeks?

like i said any help you need feel free to ask

Subz

edit: i see your location is Sydney so my laptop offer is not of much use

[NAS]

Don't think i would call Sydney near Reading hehe

NAS

[Jeffos]

here's attached an extension plugin that just contains a "jeffos test section" with a single action: "Fingers should join SWS OS ? (midi CC only)", I let curious people run it..

[musicbynumbers]

I figure it's a joke right? just added it and not found any actions!

All though a strong message seems to have formed in my head subliminal .. it seems to be urging me to say..

"fingers.. JOIN US.. JOIN USSS!"

lol

[Subz]

hay fingers

just to let you know i have found a work around to use the 0.5 extension

if you set reaper to open in "Vista SP2 compatibility mode" then i no longer get crashes in Win7

(Subz dose the robot dance )


thank you so much for this extension!!


Subz

[gofer]

Sorry to be OT all the time.

Jeffos does like a joke, but he keeps some good substance when having fun .

His test dll will add a new section to the action list called 'test section jeffos'. Curious people who want to check his MIDI CC action need to change from main section to the new one. Then you easily find his brand new "Fingers should join SWS OS ?" action. Add a CC and you also find the answer to the question whether fingers should join SWS .


I'd like to add a bit on topic as well, but all I can say is: All is well so far here. I didn't go into the groove stuff that much, I am just too floored by the new envelope actions . Tried the macro recorder and it seems to work alright as well. Would be good to have some visualization, maybe a list of recorded actions or some such.

[fingers]

New version up. Fixed recorded midi quantize. Fixed embarrassing note name bug. Fixed insert C4 note as the chunk was slightly wrong. See OP.

[musicbynumbers]

thanks fingers!

I hope you will somehow get this on to mac at somepoint (via sws or independently), not for my sake (not a mac man) but for the people I work with and my students for some of them, it would turn them onto reaper completely!

did you ever give a paypal address for donations?

[Subz]

win7 bug still present in 0.6,

running Reaper in compatibility mode still is a working work around

thanks

Subz

[musicbynumbers]

Subz I just tried extracting a groove, saving it, reloading it and trying it on multiple items of both midi and audio on windows 7 64bit and not been able to get it to crash yet. Maybe there's something else I need to do as well?

Could it not be the groove templates you are using somehow are rounded differently (although I recall you did them with fingers extension right?)


also Fingers, when I zoom really far in to midi that I have quantize from an audio track the midi notes are never perfectly on time (for notes off the beats and bars). Is this solely down to having my midi resolution "PPQN" set to low? I imagine it is, if so how high do you have yours and have you ever notice a lot more cpu from it?

or maybe it really doesn't matter as it's pretty high already!

I always wanted to set it to 44,100 but that's just sadistic!

[musicbynumbers]

Although somehow something I did with it manage to stop my undo working and when I pressed undo it went straight back to the initial state even though I had also done standard things like moving items