SirSickSik Contributions

#911

cool! is my "own contributions-folder" just a folder I make beside the folders of the other users in the axoloti-contrib/objects folder? I didn't find the home-folder - or is it the "objects" folder in the main axoloti-folder? it is empty atm.

#912

I forgot what exactly you need to do to get your own contrib folder, there should be a topic about that here somewhere.
Think you needed to response in that topic to get your own.

#913

hey SSS, playing around with your fxchainer DEMO.axp + factotum inside for sampling (amazing combo!). weird problem thou: the pitchshift of the factotum doesn't react, not to knob, not to modulation. in other patch it works normal. I tried all I could. new factotum, 2nd factotum, changing all the parameters... could it be that something in the fx chainer DEMO prevents the pitchshifter to react?
EDIT: reloaded the patch (closed & opened axoloti). now it works. still strange. :wink:
EDIT2: hm, could it be that if window=0 the pitchshifter has no influence? it works like this in my patch. also pitchshifter doesn't work linearly in certain window settings. at a low window setting while pitching up, at some point it pitches down... is this normal behavior, because of interdependent granular-setting or what not? :slight_smile:

#914

the window is the size of the buffer that gets pitched up/down. If this is zero, there is nothing to play faster/slower and the pitchshift won't work. Also, if the buffer gets too small, it will not be able to create a full waveform. You could see this as frequencies above nyquist, it just doesn't have enough information to work with.

#915

sss/midi/THRU causes my axoloti to disconnect and freeze after about 5 or 6 notes unless I'm using the midi device with my computer via Bitwig. So I can't play it standalone anymore. Does it mess up if there's nowhere for the midi to go?

#916

That's weird, haven't had any problems myself with that, but I've only send midi over the midi output.
Could it be that you're also sending midi thru from your computer back to the axoloti?
In that case you're putting more and more midi into a loop.

#917

I believe it happened even when the computer was turned off and just supplying power.

#918

the only way that I can do this is by sending thru the midi to the internal engine (which is indeed an option that I should have removed) as this would make it loop within itself.
All the other options just work on my board..

#919

I believe I was sending to "usb device port 1".

#920

I'm not sure, but perhaps, if the usb ain't connected, this device won't be loaded. So if you use it without a computer, make sure another device is listening over that usb-port or send the midi over the midi-out.

#921

Hmm, could you make it fail silently? I've detached to midi portion of my board so I could fit it into my keystep.

#922

have you made a midi-loop over usb with the keystep?
What exactly have you done? Which midi ins and outs are you using? What is the midi-thru doing according to you?

#923

The keystep is sending midi to the axoloti via the big USB port. The axolotl is relaying that midi to the computer via the small USB port and sss/midi/THRU set to "usb device port 1". It works great when I have my DAW open, but when I power my axolotl standalone it crashes the whole thing after a few notes.

#924

try putting the midi thru object into a subpatch where you can select the midi source. like so:

miditest.axp (1.9 KB)

#925

Hey @SirSickSik

I was just checking out the sss/env/AHDSRa envelopen. It sounds really smooth.

But here I am experiencing some odd behaviour. When I look at the scope and listen to it, it seems like the longer time there is between a note is send to it, the quieter the output is. If you send notes to it rapidly, it will send out increasingly louder signal on each trigger. There is quiet a big difference in loudness between playing notes with long time between and playing notes close to each other.

Do you have any idea what this might be?

#926

oh, I gave the wrong anwser XD
I added a function that would use the velocity of the trigger input and add it to the velocity "memory", which is then constantly decayed. This way, when playing a flam, it would automatically "grow". You can remove this by embedding the module and use the green code for the velocity in and remove:
"vel-=vel>>14;"
and
"vel=_USAT((inlettrg>>1)+vel,27);"

#927

Pretty cool function actually, I think I am going to keep it, but with an onn off button, so it can be on only when needed.

Thanks for the tip :slight_smile:

#928

btw, it's also really nice to connect a resonating filter to the audio-rate ADSR,
though in the code, the frequency should get shifted to the left by about 6 to get it in the right rate, so:
"freq=freq>>6;"
or add an "octave" int selector to set a base octave range:
freq=freq>>-param_octave;
(param_octave should go from -10 to 0 in this case)

You can add a stage-output in the control-rate code of the envelope to use a switch module for selecting different values per stage:
"outlet_stage=stage;"
and add a stage-output in the outlets.

Then use the stage output to select different values for the cutoff and resonance of the filter and/or dry/wet mix for each stage. Smoothing the selected values can also add some nice twists.
My "mostfilter" is able to give some nice atom-like resonances btw.

#929

I am trying the polyXL sequencer.
Besides from the wrong order of the Edit Buttons,
I have got it working, but no delay.
Also i have a hard Time record/play another channel.
Could you have a look?
polyxl.axp (40.2 KB)

.....also the port info is misslabeld

#930
  • id like to have a del note inlet. So if i want to delete for instance c3 on active channel, i press delnote and c3 on my input device and all c3 are deleted. Also i would prefer the delete input do be live momentary so i could delete parts only.