JeromeB Contributions

#22

He thx for the effort. I am really deep in my multitrack looper / fx setup so I didn't really try it out yet, but I will test it soon :slight_smile:

#23

No problem when you have time ! :slight_smile:

#24

Hey
I finally got to try your beatslicer out. It's is pretty nice, especially the DEV patches you sent to me!

However I'm a bit unsure of how to use it atm. My my main goal is a multitrack Audio Looper that can also do the magic stuff like mangling, pitching etc.
Step one is building the multitrack looper, I did so using the looper blocks of @rbrt. The next step would be to integrate the mangling elements, like your beat detection slicing. However this would be combining two different systems, it would be the most efficient to have all in one system and i'm a bit unsure how to do that.

@rbrt you see any possibilty of integrating @JeromB's work into you looper blocks? It would be quite amazing :slight_smile:

#25

hi Simon,
I will check out @JeromeB 's stuff real soon,'cause I just tried to patch a live-slicer some days ago..and I wasn't really satisfied with my own objects..
especially ,there has to be some kind of x-fading between the slices...

#26

...but right now I'm really busy on some new midi and sequencer stuff..

#27

Thanks for your feedback.
When I would have time, I want to write a midi looper. My goal is to record each slice detection in a midi recorder in order to have the same function as a looper but with new capacities like removing a slice, change pitch (with and without change length of the slice), change sequence tempo without change pitch of each slice, reverse slice, retrig slice, etc. All of this in live mode. But my ideas on the matter are not too clear, I am lacking time to investigate this.

#28

@rbrt
that would be very very dope :slight_smile:

@JeromeB
cool I think we want to to very similiar stuff! writing positions of transients to a table would be a great first step.
All the other stuff you describe is I think achievable with patching.

But for me I already have the looper environment, I only need the information where in the table the transients are, then I could do what I want with this information.
so it's pretty great of @rbrt to show interest in this :slight_smile:

#29

Hi @JeromeB I must say I really enjoy using your objects, so thanks and bravo for the hard work.

I was playing around with the turing.axo object today, it's really amazing and great fun to use live (and just plain useful I must admit), but I was wondering if there was a way for the bit buffer to be adjustable so that we could have 3 / 5 / 7 / 9 bar loops instead of always 4 ?

#30

Hi @mtyas. Thank you very much for your feedback.
I think it's possible to have an adjustable buffer length.

But, I work on an alternative : a mix between an euclidean sequencer and an turing sequencer.
I use a cpu efficient euclidean rhythms generator inspired by an old puredata patch.

Capture du 2017-12-18 21-21-45.png713x586 28.7 KB

Turing sequencer produce an periodic random number.
This number is used as an array index, of pentatonic scale.
Euclidean algorithm is used for the rhythm.
I have a patch for that, as an attachment of this post.

I have to go on a business trip. I'm looking at how to change the length of the buffer when I get back.

turing_euclidean_dev.axp (14.0 KB)

PS : Recently I write all my sequencers for a STM32F429 card. That way I can keep some CPU for signal processing and I have a display. Requires only a few resistors, an optocoupler and a diode.

Custom Object Mixed Variable Types
#31

Euclidean + turing sequencer on an external STM32F49I-Discovery board.

DSC01940.JPG3461x2596 2.18 MB

MDP32 in order to control STM32F429I board.
Midi out to axoloti board.

#32

hi there, i realise this is an old post...hehe.
i was wondering if there is a "simple" way to completely empty out a beaslicer object, so that the buffer is zeroed out and all audio output stops? i would need this to build a "crazy" drum machine. great slicer object really!!

#33

Hi,

I can't remember the code in detail, it's old object, but I think that is possible.
I intend to do clean my objects repository next week.
I'll let you know, of course !

#34

thanks for considering!!
another bug i found is that in your beastlicer example with the turing sequencers the beastlicer does not seem to react to multiplications of the clock when in reverse mode. this is a rather strange bug since those are two separate objects.

EDIT: maybe it is just the retrig inlet that stops working in reverse mode...

#35

Thanks for the feedback ! I will look at it.
Unfortunately, I have work at home that takes time and next week I go on vacation.
I'll try to work on my patches when I get back. Thank you very much for your patience Lokki !

PS : I took 5 minutes to look at the "retrig" problem.
If silence_threshold parameter is too small, end of slice is detected when input level is very low. Then fadeout of slice is long and if you play slice in reverse mode (with the attack of slice at the end), slice begins with inaudible sound. In "retrig" mode, with a small period between trigs, this inaudible part is interrupted and another inaudible part is played. This problem is increased when you play sound with low pitch.
To avoid this, increase silence threshold parameter (but it's a problem to record sound that lasts) and play with pitch parameter.

Try attached patch, and play with pitch, clock and silence threshold.
beatslicer_lokki.axp (3.7 KB)

#36

hey, thanks for taking the time and explaining, this makes much sense actually. i will try to see if i can get a sweet spot with the silence_threshold.

#37

Hi lokki,
Work in progress in axoloti-contrib/patches/gao/dev/beatslicer.axp
Still some bugs but objects are usable. Give your opinion !

Changelog :

  • stereo input signal
  • principle : 1 capture module and 1 or many slices players modules
  • 1 reset input for empty all buffers (in fact, only index is zeroed)

Todo :

  • add reverse mode in the slice player module
  • display last sample number
  • erase a selected sample
#38

New beatslicer and beatplayer

see help patch in Menu :
Help -> library -> community -> gao -> sample -> beatplayer2
Help -> library -> community -> gao -> sample -> beatslicer2

see beatslicer2 help patch for configuring analyser.
This version use float : code is easier to understand and float does not impact performance.
Mono input, in place of stereo input : the code contains fewer bugs.
It's possible to delete last slice on the stack.

Play function :

  • slice selection
  • pitch
  • reverse mode
  • retrig option (store current slice index, pitch and direction and wait for the end of the reading to start again)

It's possible to use more than one sliceplayer with the same slice stack.

#39

Fantastic, have been using the patch you made above for Blindsmyth for quick chops, and either midi or euclid sequencer play into a Factotum, for pitch and further mangling....very excited to check out the mark 2

#40

Thanks !

New objects :

Turing and euclidean sequencer : gao/seq/TESeq.axo
Help -> library -> community -> gao -> seq -> TESeq.axo

Biscuitage distortions update :
Help -> library -> community -> gao -> dist -> biscuitage_r
Help -> library -> community -> gao -> dist -> biscuitage_m

And a demo (more sophisticated than the help version) :
library -> community -> gao -> Beatslicer_Demo2

#41

And a new beatslicer companion : slice player time compression/expansion with looped sample.
Just a new version of rockafella object (https://sebiik.github.io/community.axoloti.com.backup/t/solved-pd-sampler-rockafella-example-on-axoloti/850/2?u=jeromeb), but for beatslicer buffer and cpu friendly version.

Check Help -> library -> community -> gao -> sample -> spTimeExpansion

patches -> gao -> and Beatslicer_Demo2