Hi,

Here is my first Pd project.
I think i'm like most of Pd n00bs: amazed by the promises of such power, but quite lost in the objects jungle.
Fortunately, there are some serious Pd gurus walking this forum and they are not knowledge-greedy at all.
Special thanks to hardoff who's sample slicer with user selectable slices got me started.

Here's a screenshot of version 0.1 (click to enlarge):

Version 0.2 on its way, with lots of improvements and feature-adds.

You can visit the project page, or just download axiome-0.1 directly.

Any help, comment, feedback, bug report, modding appreciated...

Haven't got an Monome, nor have I had time to test this, but...

NICE interface! Where did you get the idea to use vertcal sliders?

Good work

Thanks for the comment boonier.

I got the idea of vsl for buttons from enrique erne's mMm...
what a piece of work by the way!!

Now i see what boonier means about the vertical slider idea, very ingenious indeed. That's about the most user-friendly pd patch i've ever encountered, the loading and saving works like a charm.

However, it's not totally clear how the pattern thing exactly works. It seems like you have to click a toggle to make a slicer start working, but there's (apparently) no way to make them all stop or start at the same time, or am i missing something.

That's a good question domien: i spent so much time on it that i figured that it would be pretty self-explanatory. My mistake...

I'll write it as a start for a manual:

To play a slicer, you have to push a "radio" (they're vsl's too ). The sample starts at the position of the button (you have to imagine your sample apportionned on the eight buttons, even if it's 4bars length). To stop the sample, press "PLAYING" (i know this is not common sense, but wait for the next release...).
The sample-cutter (eight buttons) actions are quantized to 1/16. So you can start a loop and when it comes at the end, start a second one and if you get the good 1/16 timing, it will sync to the first one. And so on...

Now, the pattern section (darker grey):
A pattern is a recording of actions on the cutter-buttons.
Set the length. (in 1/16)
Press "record" -> it shows "press", waiting for an action on one of the cutter-buttons (not necessarily the first one) to start recording. You can cancel record-enabled, recording or playing states anytime by hitting the record button again.

So, if you enable record and press a cutter-button, you start the record counter (record button became "recording").
Play on the cutter-buttons to record a pattern loop.
At the end of the record loop, the pattern recording plays back automatically what you've just played and becomes "playing".
You can stop the slicer (press "PLAYING"), but the pattern is still playing in the background until you press ("playing") to stop it. You can start the slicer again (press any cutter-button and the pattern is plays at its current position).

@domien:
To start or stop several slicers simultaneously, you'll need to have either:
-several mouse pointers (duh!!?)
-a computer keyboard or a midi keyboard, with key assignments (you'll have to create an abstraction or subpatch. But that would not be difficult, just send bangs to the button's inputs... i may work on that later)
-Other hardware... like the monome, which buttons are mapped to the ui (see the subpatch monome_com inside the slicer abstracts.

Anyway, you can still get the samples in sync by waiting for the end/beginning of the other loop(s).

Hope i didn't confuse you with my long explanations.

Putting the draft into the package...

Oh and thanks for the compliment .

Cheers

This is a rather nice patch, Thank You!
Are you limited to using a monome?

Thanks again

Nope, i designed this patch for the monome 8x8 but you could easily adapt it to any hardware really... see the post just above yours .

What about a Lemur ?

A Lemur would be nice, but....
I was thinking of a UC-33e or some such.
I'm guessing that something to translate MIDI to OSC is in order then?

I also owe a UC33e...

I'm currently developping a patch to use it on the mixer (and maybe on the ongoing multifx processors...)

But starting there, you could use it for the pitch, or poly also: in fact any of the controls...

No need for OSC then, cause the only use i'm making of it in the patch is to talk with the monome.
What you'll have to do (if you don't want to wait for my update) is to map the ranges of the midi controllers (0-127) to the ranges of the sliders (0-1 for the mixer faders, 0.5-2 for the pitch, 1-3 for the poly...): simple. Just create a patch with [ctlin]'s, make the translation for the ranges, and send the output to the vsl's receives.
here is an example:

Did i answer your question?

http://www.pdpatchrepo.info/hurleur/midi_controller.pd.zip

That answered my question perfectly.
Thanks for the response and thanks again for Axiome

this looks really cool. will download it as soon as i find a computer connected to the net without a faulty USB connection.

I haven't gotten around to making my UC-33e talk to Axiome yet, but I've been having fun nonetheless. One odd thing happes when i laod a loop: the open box/file requester reappears shortly after I've loaded the sample. If I hit OK, it will return, but if I hit the Esc key on my keyboard, or close the window, it will stay closed.

This happened in Linux (Ubuntustudio 8.04.1, with Pd-Extended 0.40.3)

Thank you for the feedback, i also experienced the same problem with mac os 10.4 but couldn't manage to resolve it...

But it is quite random on my machine: doesn't happen all the time. Does it on your Hardy Heron?

For the uc33, you might find the attached useful.

http://www.pdpatchrepo.info/hurleur/uc33.zip

No, it doesn't happen with the loading of every sample. It is indeed random.
And thanks for the UC33 patch. I'll try it tonight, hopefully.

Cheers

man, i love it when people make patches that just work straight away. great stuff.

Hi, I'm on Hardy and using Serial-Pyio, I don't know why, but i'm only receiving from PD but my button presses are not going through. 8000 and 8081, prefix /box .

Thanks for this, I've also been banging my head trying to created something similar, how do you implement the pattern recorder? In the Original MLR, he uses a seq~ object which doesn't exist in any form in PD and I've been trying like mad over the past week to create that.

I also took the phasor~ way to read the tabread4~'s, but maybe the vline~ method might work better, problem I find is that using your method, I can't get the samples to play back like how they were originally intended, and everything starts to sound modulated somehow.

ED: Ok got it, Readme says 8000, patch says 8001.

Best
Marc

Yes, sorry for the error in the readme, i corrected that in a new tarball some days ago.

You can find the pattern recorder in [slicer $1]->[pd time].
There is a [seq] object in pd, allthough i don't know if it works like the [seq~] in max.
For your sample playback "modulation", if the sample is played at a lower tempo than its original one, gaps will occur between slices. Now, it may be related to the overlaping of the slices when playing back at a higher tempo: try then with poly to 2 or 1.

I also tried another method using tabreadmix~ for the playback engine but the sound is even more distorded. Maybe an alternative of the two...

Very cool! I'm looking forward to connecting this to my MicroKontrol.

Hi
I've been having fun with Axiome lately. Here are some results:
http://bit.ly/ORUYh
Still no Monome, but I will be building a 40H kit soon.
For these tracks, Axiome is aided and abetted by delays and pattern-controlled filters by Martin Brinkmann( http://www.martin-brinkmann.de/pd-patches.html) and pureverb and compression from Hardoff's brilliant DIY2 set.
Enjoy

Hi!
Weng, thanks for a really cool patch!
I've connect the patch with MPD-32 controller:
If to create 4 shifts (controlled by MPD-slider) to switch between slices, it makes possible to controll all slisers with the controller. Of course, it's not so convenient as to control it with monome, but it's possibe and almost comfortable.
I have another questions related with the Axiome: could you clarify, how FX input\output orginized? I can't fid it.
I'm not idiot, just newbie in PD.
Thank you in advance!

@trkkazulu said:

Very cool! I'm looking forward to connecting this to my MicroKontrol.

Did you end up connecting it? How did it work?