Using FluCoMa tools with reaper

Are you using ReaCoMa 1.0 or the new 2.0 version?

I’ve now created a new minor version of ReaCoMa 2 that works with the updated version of ReaImGui.

1 Like

As @tremblap found, I actually didn’t account for a new way that colours were managed in the 0.7 version of the ReaImGui API. This meant you got a very esoteric error if you were setting up for the first time. So… this version fixes it:

A small update. I’ve just hit go on ReaCoMa 2.5 which adds support for audiotransport and nmfcross.

To facilitate setting up hybridisations, there is a new GUI for source/target type relationships with drag and drop. I would have liked to create something which allows you to link any selected media item in a ā€œpatch bayā€ but unfortunately proved too difficult and for nmfcross in particular that will spike your wait times significantly :slight_smile:

A preview of the new interface

You can download the latest release below. Likely to be some bugs in there so please let me know if you do find any.

2 Likes

now… I need a hybrid between jaw-dropping-emoji and mic-drop-emoji, can NMF help me with this?

Hi,

Thanks for this new release.

I just tried to install ReaCoMa, with a fresh install of Reaper but get an issue with some processes.

For example, when trying the onset slice script I get the following error message when clicking on the ā€˜create markers’ button:

ā€œā€¦Support/REAPER/Scripts/ReaCoMa 2.0/lib/imgui_helpers.lua:117: attempt to index a nil value (field ā€˜item_pos’)ā€

Did I mess something when installing or can someone reproduce ?

Best,
Julien

Looks like me a problem :stuck_out_tongue: I’m investigating.

I can confirm I did a bad boo-boo and will fix it ASAP.

@jln can you try this new release and get back to me?

Hi James,

Thanks for your messages. I can confirm that the error I was getting is gone. Thanks !

Best,
Julien

2 Likes

Huzzah. This prompted me to go refactor the whole thing so that I can actually test the code automatically for this kind of stuff :slight_smile:

1 Like

Another few bugs fixed. If you recently upgraded please upgrade again:

1 Like

Sorry, but I’m not finding this at all in the menu after I installed it. Apologies, but I’m often slow at this. Everything else works (although the download is labelled as 2.0, so maybe that’s where my error begins)

If you have a minute.

Thanks in advance,

Rick

Hi @rick, it isn’t somethign you will be able to find in any menus by default. What you have ā€œinstalledā€ are just a folder of scripts which you can run with the REAPER action for running Lua/Reascripts. You can find this in the action menu (Shift + /).

Thanks. I’ve been using several of these via Lua scripts for a while. 6 or so of them are in a docked toolbox on my edit window.
I’m not finding the scripts for nmfcross etc.

Is that not yet part of what’s in?

Belay all that, I’m sure it’s just where reaper is looking for them. I keep getting confused with the version numbers (both folders are 2.0 so I keep sending things to the wrong place.) Like I said, I’m often slow at this.

They should be in the folder, can you see them there?

Yeah, they’re in the folder. I just can’t seem to point reaper to them in order to make them work. Although
image
all these still work fine.

Look, don’t sweat it. I’m just a ā€˜hobby composer’. I’ll figure it out but it won’t be worth your time. I just like the way it takes things apart. It’s very nice stuff. Playing with it reminds me of when Soundhack first came out.

Great work btw

r

I reckon the little widget just has lost association to the script - probably because the folder name has changed is my hunch. So what I think you have to do is this…

Click new action…

Click Load ReaScript... this will spawn a finder window to go locate a script.

Pick the non-existant or broken script. This registers that script as an action in REAPER

Go back to the action menu in REAPER and click menu editor...

Choose one of the empty floating toolbars from the drop-down menu at the top left or a toolbar you want to edit. Then click add to add a button for a registered action (this is why we registered the script before).

Now it shows up in the floating toolbar, which you will have to place somewhere in your UI or float above


I think that should help you just going through that process again.

It’s no trouble whatsoever, and thanks for your positive words

So far so good for some of them. the transient related ones are still an issue but I’m sure it’ll clear up.

Thanks again (I’m running a resynthesis process on two short sounds and yeah, like the original soundhack I’m gonna be letting it run overnight! I’m still running an intel machine.

cheers,

Rick