SirSickSik Contributions

[lokki]

i agree. i have always renamed my stuff to axo files, but that is not ideal.

[SirSickSik]

oh hmm, could I also just save the tab as an .axo file and it would still work?

[lokki]

yes should work. the "enduser" will have to rename it accordingly of course. and the file size has to be within the limits. try!

[jaffasplaffa]

Would be nice if we could also upload tab-data on here instead of only patches..

Yeah I agree.

I think the problem with that Axoloti page is sometimes down is because of lack of space on the server. So I dont think we are going to be able to upload other stuff, as the server is all ready flooded.

You could try something like https://mega.nz/

They offer tons of free space. For smaller files it is good but for bigger files you might be restricted by some download restrictions.

Dropbox?

There are many free cloud services

[SirSickSik]

would it be save to use one-drive and post a public link? (never used it, don't know if it can..)

[SirSickSik]

I've uploaded the tab as an .axo file, just rename it.
It's in the original post, where the former drum table link was posted.
oh, and I see it's also below thanks to the link.. XD

DRUM TABLE FILE FOR DOWNLOAD: Dseq001.axo (2.2 MB) You have to rename this file to work: Dseq001.tab (it's the .tab part that's important, name it whatever you like for the other part) This is a file containing 2913 pre-recorded midi drum sequences. It's to be used with the dedicated drum-sequencer that I will upload shortly from now (just checking last things and adding info). This file should be put on the SD-card in your axoloti and can be loaded with the normal, factory "table-load" and …

[SirSickSik]

hmm.. just thinking..
It would be nice if I made an editor with this drum sequencer, so we could use the patterns as templates to design our own rhythm banks (as this is just a collection of midi files I got from the internet, probably with quite some duplicates).
This way we could make seperate banks for techno, drum&bass, breakbeat, rock, latin, whatever, etc etc
Perhaps a few accompanying modules like a rhythm combiner/randomiser (randomised combinations of different patterns) would be helpfull with this. If you guys could then help me building these banks, we'ld have an awesome drum machine for the axoloti instantly ready for play in each new patch!
As a gift I'll try to make a low-cpu dedicated drum-synth ala jomox, that you could just hook up

[SirSickSik]

my new automation and continuous gate recorder for the axoloti is working!
Though I screwed up the connector of the screen, losing the X axis..
Luckily the second half of the rotary encoder connects the Y axis to channel B, so I can still record to all channels.
I hooked up the led of the buttons to the "normally closed" output, so they'll lit up nicely as long as they're not pressed.

[jaffasplaffa]

@SirSickSik

Did you get the issues fixed? The ones that you mentioned suddenly stopped working?

[jaffasplaffa]

I dont know one-drive personally.

But there are a lot of services where you can make more permanent links. To be honest I think you just need to pick one I dont think there is alot difference between the free ones.

If you want something specific, you probably gotta pay for it, but for some Axo files and so on, I think any cloud service is good

[SirSickSik]

yes, mouse is now behaving the right way.
It was quite a hassle to do, but I managed. Not the "right way" (just added an extra pair of axis and treated the incoming mouse data as 4 axis (in the hid-mouse .h/.c files, also in some file called patch I needed to add these X and Y as externals (besides x and y), as it seems this allows these to be used inside a patch).
After this I combine them to 2 axis and use the data as absolute instead of relative (usbconfig in main firmware folder).
This allows the full 12 bit of the position-data to be used
I probably have changed more to the firmware then I've should, so it's not really recommendable to use it for something else then my patch for my eurorack-module. It seemed a bit buggy with some axoloti modules, producing errors.

Hmm.. just thinking.. I'm now looking at my 55" screen with 10-finger touch... perhaps there's still some room inside for some axoloti's XD

[mokomo]

Brilliant - thanks.
I've been aiming to build an axo drum pattern generator/morpher to feed into external machines and looking forward to getting to know this.
Editor sounds like a great idea for people to build custom banks to seed it.

[SirSickSik]

I've quickly made the first part for editing the sequences.

Check sss/test/
-baseditor
-basaveload

copy and paste the baseditor so you'll have 8 of it.
Don't forget to refer to the right modules:
baseditor: "baseq_1"
basaveload: "baseditor_1" up to "baseditor_8"

[mokomo]

hi I can't seem to get 'dseq001.tab' to work as the table in a table/load object

In member function 'void rootc::instanceload__1::dsp(const char*, bool)':
C:\Users\justi\DOCUME~1\axoloti/build/xpatch.cpp:60:34: error: 'class rootc' has no member named 'instancedseq001_dot_tab_i'
int rem_sz = sizeof(parent->instancedseq001_dot_tab_i.array)parent->instancedseq001_dot_tab_i.LENGTH;
^
C:\Users\justi\DOCUME~1\axoloti/build/xpatch.cpp:60:75: error: 'class rootc' has no member named 'instancedseq001_dot_tab_i'
int rem_sz = sizeof(parent->instancedseq001_dot_tab_i.array)parent->instancedseq001_dot_tab_i.LENGTH;
^
C:\Users\justi\DOCUME~1\axoloti/build/xpatch.cpp:66:34: error: 'class rootc' has no member named 'instancedseq001_dot_tab_i'
memcpy((char *)(&parent->instancedseq001_dot_tab_i.array[0]) + offset,(char *)fbuff,bytes_read);
^
C:\Users\justi\DOCUME~1\axoloti/build/xpatch.cpp:71:34: error: 'class rootc' has no member named 'instancedseq001_dot_tab_i'
memcpy((char *)(&parent->instancedseq001_dot_tab_i.array[0]) + offset,(char *)fbuff,bytes_read);

[SirSickSik]

and if you use 0:/Dseq001.tab and save the file to the main folder?

[SirSickSik]

ps... capital letters is a thing....

[reubenfinger]

Just wanted to say Thank you for all the hard work you put into all these modules, I have been using Factotum together with a Loop4 all mostly synced to midi clock, my patch needs refining, but it's amazing fun trying and learning it's secrets, finding sweet spots and getting surprised by what the machine spits back out in my face

[MattilynMattroe]

I was just thinking the same thing. I just put four of them after a guitar Looper, each with a sequencer sequencing recording/pitch/direction. Just incredible! Factotum is amazingly useful

[mokomo]

Made some progress thanks Sir...

Should I be able to see the beats on the charts in my following set-up?

[SirSickSik]

several things:
-first of all, the triggers are 1-sample triggers, so these displays might miss them (not sure about which update rate they have), so, to test, connect a "c>0" module and a timed gate generator, this should turn it into gates. When using a latch module, you can sample&hold the velocity of the trigger.
-secondly, the patterns are 96 steps long (8*12 steps to enable thirds), not 16.
-thirdly, about the first 40 patterns don't contain many notes. For a first test, just check out pattern 48 for techno.
-fourthly, it seems channel number 0 ("kick") is rarely used by the midi files, the kicks are mostly triggered by channel number 1 (basskick).

also check out my test-folder, in there, I have two modules that can be used to read load/edit/save the channels and patterns. You can load the one with the 96 sliders 8 times to view/edit all channels together