Hoping to have the vocoder module done by Tuesday!
Are these for Orac? Noticed they’re zip not zop
a developers note: use the deploy.sh I shipped with the replacement s-czz, and the accompanying ‘installation notes’ , I believe this is the simplest for end-users, and so what we should standardise on, so that users don’t get confused about the installation process = less support for us
What are the chances someone could port the monome apps into Orac modules?
ok run into an interesting issue
I’m making a clone of a monome patch using my APC mini (well reimplementation based on watching a video not sure how like the original patch it actually is)
I’m using midi to talk to the APC - both in and out
I’m just adding in note outs and…
well it turns out PDs implementation of midi devices is kind of poor - I don’t seem to be able to select which device to put midi out on (even on my desktop version - it lets me add multiple devices but I can’t see how to control where the midi goes)
basically I want to be able to midi out back to the APC and I want to be able to shove notes out into the depths of orac.
or do I just need to add sound generation to my patch and be done with it?
interesting… I may have to hold off purchase of my second launchpad!
Looking over these threads
pd.info forum thread
It seems that you can address multiple devices using 1-16 for port 1 and 17-32 for port 2.
This still seems like it will be an issue as you will kind of have to sacrifice any kind of midi mapping to be able to fully control the APC.
This is probably why the monome uses serial and OSC (right?)
ah - thank you - well that certainly works on my desktop version.
agree mapping might be a pain - however I’m not getting into the realm of writing some kind of driver
dunno - Max is fairly good at multiple devices (in fact I often use it just to wire different things together)
this is already covered in my how to thread
you have a choices
a) map multiple controllers onto channels 1-16, then in orac you can select midi channel in chain
(i.e. just use different midi channels for each controller)
b) use -mididev in pd-opts.txt to attach multiple channels grouped, 1-16,17-32,33-48 etc.
then use midi channels in chain
if your controller is not able to select midi channel to send on (then after complaining to the manufacturer it should do), use option b, which will put midi channel 1 , 17 etc.
if you do use over channel 16, you will find orac limits selection in the router module
but have no fear, I rarely hard code anything…
go to the router module, open module.json, and there you see midi channel, change range to your new range
e.g. 0-128 (0=off, so keep zero)
cheers - I was looking for puredata only stuff - didn’t think of looking here
anyway - I’m on track again!
I’ve been working on a few modules, just finished one based on samplenest.
Its called sampletwig. It can only hold one sample, but it can be triggered and pitched with midi (using multiple instances should also let you layer samples).
I’ve been getting a lot of cool results sequencing it with arpeggiators, polybeats etc.
Also has two new random loop modes and adds pitch modulation.
you can grab it here:
Readme with more explanation of the parameters is here;
Currently selecting samples is a bit tricky if you have a lot (ORAC native sample support would be very useful here!).
Any feedback / bug reports appreciated!
wowza. can’t wait to try.
edit: i have now, and its amazing.
I spy a few other new one nes in your repository too, they all ready for release?
i don’t quite know what mode 4 is doing, but it sounds amazing.
one possible improvement could be if the envelope had finer adjustment possibility. the samples seem to ‘pop’ a bit (i wonder why), but an envelope setting of 0.1 stops it. i wonder if envelope 0.05 or 0.04 …etc. would work just to stop that tiny click or pop.
I think the envelope knob should actually allow finer adjustments, but the display truncates the number to one decimal place.
Its a bit confusing, I should probably make the range 0-100 instead.
Wannop: Most of the other modules in the repository are unfinished, some are just placeholders for ideas
I have one or two more that are pretty close so hopefully I’ll post them this weekend.
I also posted a MuChord module in the module development thread a while back.
edit: Also to explain mode 4 a bit, its is ‘random ping pong’ mode. Its like the normal ping pong loop mode (the sample plays forward then in reverse) but instead of always changing directions at the end of the sample, the direction reverses at a different random point in the sample each time.
edit 2: Just realized random ping pong is actually mode 5. Mode 4 is ‘random cut’, basically this just choose a random section of buffer to play each time, kinda like granular playback. Next release I want to add more control so you can control the size of each section more.
Figured I’d get some versions out now so I can fix any issues before I update for 1.1.
All packages are available here:
The new modules are:
monophonic audio to note converter. Fairly glitchy but can have interesting results!
polyphonic synth based on polyfolder, now also has LFOs for pitch and folding depth.
An attempt at the Eno/Lanois pitch shift + reverb feedback loop effect.
Parameters are explained here:
Drum machine and bass/chord generator based on Ottorhythmichord and apollostation
Parameters are explained here:
Just put up a couple modules people can try out here:
Warpdelay is a pitch/direction shifting delay, Notegen is a probabilistic midi note generator, and Clockswing is a version of U-clock with swing and humanization controls.
The humanized ‘clockswing’ module is fantastic. Can I feature request? Aux button for global clock start/stop?
Going to work on another conversion of my own this week, we’ll see if it works. Sampler Style REC.
amazing stuff! these are fantastic!
Yep suggestions are welcome! I can give that a try next update.