# Using FluCoMa tools with reaper
**URL:** https://discourse.flucoma.org/t/using-flucoma-tools-with-reaper/311
**Category:** Code Sharing
**Created:** [September 10, 2019, 8:44pm UTC](https://discourse.flucoma.org/t/using-flucoma-tools-with-reaper/311 "2019-09-10T20:44:03Z")
**Posts on this page:** 20
**Page:** 5
### Author:  [@jamesbradbury](https://discourse.flucoma.org/u/jamesbradbury)
#### Post date: [September 27, 2019, 4:24pm UTC](https://discourse.flucoma.org/t/using-flucoma-tools-with-reaper/311/81 "2019-09-27T16:24:31Z")
I’ll be adding more as I go to [this repo](https://github.com/jamesb93/REAPER-Scripts/tree/master/pa) and [this repo](https://github.com/jamesb93/ReaCoMa)
copy\_change\_dur.py has now been translated and requires no installation except downloading the script 🙂
---
### Author:  [@rodrigo.constanzo](https://discourse.flucoma.org/u/rodrigo.constanzo)
#### Post date: [October 18, 2019, 7:38am UTC](https://discourse.flucoma.org/t/using-flucoma-tools-with-reaper/311/82 "2019-10-18T07:38:58Z")
I take it the latest update has broken all of these?
---
### Author:  [@weefuzzy](https://discourse.flucoma.org/u/weefuzzy)
#### Post date: [October 18, 2019, 8:10am UTC](https://discourse.flucoma.org/t/using-flucoma-tools-with-reaper/311/83 "2019-10-18T08:10:45Z")
Looks as if @jamesbradbury has already updated the executable names in the repo – you may need to re-pull though.
---
### Author:  [@jamesbradbury](https://discourse.flucoma.org/u/jamesbradbury)
#### Post date: [October 18, 2019, 10:21am UTC](https://discourse.flucoma.org/t/using-flucoma-tools-with-reaper/311/84 "2019-10-18T10:21:22Z")
Hello all,
The scripts work with Beta02 and upwards. There is no need for anything else other than the CLI tools as released by the team and these scripts.
[https://github.com/jamesb93/ReaCoMa](https://github.com/jamesb93/ReaCoMa) Please download the repo from the master branch and see how you go.
Any bugs let me know here or on the github issues page.
P.S
There are some experimental scripts in the /experimental folder. You can try to use these with the disclaimer that I might break them or leave them in a dysfunctional state.
---
### Author:  [@spluta](https://discourse.flucoma.org/u/spluta)
#### Post date: [October 28, 2019, 1:57pm UTC](https://discourse.flucoma.org/t/using-flucoma-tools-with-reaper/311/85 "2019-10-28T13:57:24Z")
This is incredible. Getting a visual for some of this stuff is worth every penny they are paying you James. Thanks for this!
---
### Author:  [@jamesbradbury](https://discourse.flucoma.org/u/jamesbradbury)
#### Post date: [October 28, 2019, 2:18pm UTC](https://discourse.flucoma.org/t/using-flucoma-tools-with-reaper/311/86 "2019-10-28T14:18:12Z")
> [@spluta](#):
>
> worth every penny they are paying you
😉
In all seriousness, I’m really glad you have found it useful. For me it opened up the tools in a way that I didn’t think I would respond all that well to. Any bugs or suggestions let me know so I can include it.
---
### Author:  [@tremblap](https://discourse.flucoma.org/u/tremblap)
#### Post date: [October 28, 2019, 2:50pm UTC](https://discourse.flucoma.org/t/using-flucoma-tools-with-reaper/311/87 "2019-10-28T14:50:57Z")
> [@jamesbradbury](#):
>
> > worth every penny they are paying you
@jamesbradbury is providing this community with these amazing ports for free. He only gets paid in kind: special on-demand access to @weefuzzy and myself. Now, one might think it is not much pay… but he keeps on asking 😉
(all banter apart, thanks again James for this fantastic porting)
---
### Author:  [@jamesbradbury](https://discourse.flucoma.org/u/jamesbradbury)
#### Post date: [October 31, 2019, 4:35pm UTC](https://discourse.flucoma.org/t/using-flucoma-tools-with-reaper/311/88 "2019-10-31T16:35:43Z")
For anyone using these scripts I have found a limitation that is impossible to get around.
If you pitch shift or change the speed of a media item any FluCoMa processing will not respect the changes to that audio unless the audio is bounced/rendered first.
EDIT:
This applies to **ANY** processing
---
### Author:  [@jamesbradbury](https://discourse.flucoma.org/u/jamesbradbury)
#### Post date: [October 31, 2019, 4:53pm UTC](https://discourse.flucoma.org/t/using-flucoma-tools-with-reaper/311/89 "2019-10-31T16:53:04Z")
Also, if you execute a tool with insane parameters (like blocksize 1000 instead of 100) REAPER will hang, you will have to kill it but the process will run on forever in the background unless killed by user. Can’t fix that one unfortunately
---
### Author:  [@tremblap](https://discourse.flucoma.org/u/tremblap)
#### Post date: [November 1, 2019, 8:50am UTC](https://discourse.flucoma.org/t/using-flucoma-tools-with-reaper/311/90 "2019-11-01T08:50:21Z")
> [@jamesbradbury](#):
>
> Can’t fix that one unfortunately
are you certain? I sent you links to timing-out computations and advance threading in reascript… check the command **reaper.ExecProcess( cmdline, timeoutmsec )** [ReaScript API — Documentation](https://www.extremraym.com/cloud/reascript-doc/)
---
### Author:  [@jamesbradbury](https://discourse.flucoma.org/u/jamesbradbury)
#### Post date: [November 1, 2019, 2:31pm UTC](https://discourse.flucoma.org/t/using-flucoma-tools-with-reaper/311/91 "2019-11-01T14:31:35Z")
I was aware of the threading but not this call that can be made. I am currently going through LUA and around the API itself once the script is called. This means I can easily implement a timeout across all the scripts :), perhaps something which is configured with a sane default in the situation you want to do a **chunky** nmf or transient separation process. Given that I can do the command line execution within the API I can probbaly thread it too. Making the command line execute via `os.execute` is all well and good, but reaper cant see it or thread it very easily into the background.
---
### Author:  [@tremblap](https://discourse.flucoma.org/u/tremblap)
#### Post date: [November 1, 2019, 3:18pm UTC](https://discourse.flucoma.org/t/using-flucoma-tools-with-reaper/311/92 "2019-11-01T15:18:24Z")
maybe you could add a variable in the UI with a healthy default, and then if people get timed out, they get the message and can add more time 😉
---
### Author:  [@jamesbradbury](https://discourse.flucoma.org/u/jamesbradbury)
#### Post date: [November 1, 2019, 3:19pm UTC](https://discourse.flucoma.org/t/using-flucoma-tools-with-reaper/311/93 "2019-11-01T15:19:04Z")
Do you want some more time to run:
`fluid-nmf @source file @components 1000 @fftsettings 32767 64 32767`
---
### Author:  [@rodrigo.constanzo](https://discourse.flucoma.org/u/rodrigo.constanzo)
#### Post date: [November 1, 2019, 3:48pm UTC](https://discourse.flucoma.org/t/using-flucoma-tools-with-reaper/311/94 "2019-11-01T15:48:06Z")
Not without `@iterations 999999999999999` though…
---
### Author:  [@jamesbradbury](https://discourse.flucoma.org/u/jamesbradbury)
#### Post date: [November 1, 2019, 4:08pm UTC](https://discourse.flucoma.org/t/using-flucoma-tools-with-reaper/311/95 "2019-11-01T16:08:39Z")
Do you mean `num_iterations`?
🙊
---
### Author:  [@spluta](https://discourse.flucoma.org/u/spluta)
#### Post date: [November 3, 2019, 5:42pm UTC](https://discourse.flucoma.org/t/using-flucoma-tools-with-reaper/311/96 "2019-11-03T17:42:38Z")
Oh, I wasn’t kidding at all. I was working on some segmenting in SC, but then checked out this thread. I downloaded the Reaper tools, could see that the values I was giving the segmenter were giving me crap results, spent about 5 minutes tweaking the parameters (which just wouldn’t have happened in SC), then had a great segmentation that worked perfectly. But I just wouldn’t have had the correct arguments to get it right just working in SC because I couldn’t see the results. For that alone, it is amazing. Plus it can do all the stuff as well in my favorite DAW. Incredible.
---
### Author:  [@rodrigo.constanzo](https://discourse.flucoma.org/u/rodrigo.constanzo)
#### Post date: [November 3, 2019, 6:03pm UTC](https://discourse.flucoma.org/t/using-flucoma-tools-with-reaper/311/97 "2019-11-03T18:03:48Z")
> [@spluta](#):
>
> But I just wouldn’t have had the correct arguments to get it right just working in SC because I couldn’t see the results.
As an aside, this speaks to how useful/awesome it will be if/when @weefuzzy remakes @leafcutterjohn’s [slicer visualizer thingy](http://discourse.flucoma.org/t/buf-slicing-comparison-learning-patch/209). (and same goes for other types of things (e.g. `fluid.ampslice~` envelope visualizers))
On a more topical answer. This is indeed super awesome in Reaper. I still haven’t done anything major in Reaper, mainly relying on Logic (and Audacity(!)) for vanilla “tape recording” as needed.
---
### Author:  [@jamesbradbury](https://discourse.flucoma.org/u/jamesbradbury)
#### Post date: [November 3, 2019, 9:39pm UTC](https://discourse.flucoma.org/t/using-flucoma-tools-with-reaper/311/98 "2019-11-03T21:39:02Z")
I am privy to some code which is in the works by @jacob.hart 🙂 I think he should release it to the forum at some point because its clear that slicing parameters (and finding the right ones) is a pain point.
---
### Author:  [@tremblap](https://discourse.flucoma.org/u/tremblap)
#### Post date: [November 4, 2019, 9:51am UTC](https://discourse.flucoma.org/t/using-flucoma-tools-with-reaper/311/99 "2019-11-04T09:51:35Z")
> [@spluta](#):
>
> Oh, I wasn’t kidding at all.
I know you weren’t. And I know visual feedback was very important when I did my learning in Python on most of the prototypes. That is why Reaper integration was on my todo since the first months of the project (hence my reaper scripts endeavours then), so when @jamesbradbury offered to jump in, I was too happy to support 😉
Another good news: @jacob.hart has some visualiser indeed, but very soon there is a whole new lot of KE material with visual examples coming from @weefuzzy…
---
### Author:  [@weefuzzy](https://discourse.flucoma.org/u/weefuzzy)
#### Post date: [November 4, 2019, 10:19am UTC](https://discourse.flucoma.org/t/using-flucoma-tools-with-reaper/311/100 "2019-11-04T10:19:19Z")
@jacob.hart has very kindly shared his code with me, and I’m going to try and make it a bit faster; with his agreement, we’ll probably include it in the main distro. However, this is Max: I still need to harness enough SC gui-fu to assemble something that would be useful to @spluta.
@rodrigo.constanzo is quite right that being able to see the feature curves themselves would help massively with this, partly because thresholds and curve shapes are so different for various metrics. In my mind, there’s a sort of two-phase idea. The long term idea is a _breaking_ change, where we separate the business of cutting curves from the business of generating them (more flexibility, but also more objects to learn). In the nearer-term, it would probably be possible to simply equip the slicers with new, secondary outputs, without breaking too much of everyone’s stuff.
[Previous page](https://discourse.flucoma.org/t/using-flucoma-tools-with-reaper/311.md?page=4)
[Next page](https://discourse.flucoma.org/t/using-flucoma-tools-with-reaper/311.md?page=6)