Quantcast
Channel: Axoloti Community - Latest posts
Viewing all 24308 articles
Browse latest View live
↧

A micro Buchla Music Easel

December 15, 2019, 8:38 am
$
0
0

Hello everyone. I've just finished a new synth after 5 months of work. It's a micro music easel :

This is the sound demo : www.youtube.com/watch?v=w7IrjJ7MmoY

This patch is using only around 40% of DSP load but I can't add any other object without overflowing the Board.

I had a lot of help from many of you especially sirsicksik. this patch took me more than 2 months to develop.

For hardware I've used the Teensy 3.2 to add more analog and digital control, and a MPR121 capacitiv touch sensor for the keyboard. Programming and coding the Teensy was the hardest part for me. Every pin is used...
The 15 faders are soldered to the axoloti, but all other controls are soldered to the Teensy.

About the patch sharing. The patch look really unusable with tones of controls and it's hard to know what you can touch if you don't know it. What I want to do is a final object and share it to the community. But the problem is that I don't know how to make a final liscensed object like all others do to share with the community. I mean I understood with parents parameters how to build the object, but not liscensing and sharing to the library. I need to do it for 3 objects, the wavefolder, the Complex oscillator, and the final object. So if somebody is able to explain me how to do that, I will share the final object with pleasure !

I've made another 15min full tutorial video about all functions of this synth : https://www.youtube.com/watch?v=9uBTyjKZKpg

And I can share with you some pics of the hard soldering time and other building process :slight_smile: :

IMG_4590.JPG2579x3869 1.34 MB

IMG_4589.JPG2579x3869 1.38 MB
IMG_4610.JPG3869x2579 1.52 MB
IMG_4604.JPG3869x2579 1.26 MB
↧
Search

Polyphonic Sampler Patch

December 15, 2019, 8:38 am
↧
↧

Next-gen and mini Axoloti hardware discussion

December 15, 2019, 9:44 am
$
0
0

I think there are as many needs as there are users.
I would be happy with an axoloti with updated hardware, but happy to get whatever is going to modify to my needs.

↧

Next-gen and mini Axoloti hardware discussion

December 15, 2019, 11:15 am
$
0
0

Sure,
A ready to code board is pure freedom for Makers like most of us.
We can do whatever we want with it. Self Taylor made :smiley:

A ready to use module will be usable by musicians without electronics skills.

Note that the later can be based on the former. These options are not contradictory, they are complementary.

↧

Next-gen and mini Axoloti hardware discussion

December 15, 2019, 1:49 pm
$
0
0

Personally I'd like a less "hacky" code environment. It's super confusing to try to edit code in each of the little tabs in the properties window, especially when you realize everything's being pasted into one file and you have to watch out for namespaces and stuff. And there's no real benefit to doing fixed point math everywhere, we're not on a Cortex M3. Make it user friendly for both the GUI people and the code people.

↧
↧

A micro Buchla Music Easel

December 15, 2019, 5:30 pm
↧

MIDI Latch LED button on and off

December 16, 2019, 3:10 am
$
0
0

Hello everyone, can I get some help on this one?

I still have not figured it out. I wonder if I'm missing something about how Axo handles midi in and out.

When I try to update the status of an led by sending velocity 1 to the appropriate note, I sometimes see just a flash of light from the LED, indicating that the message is getting through but being immediately turned off again. This does not happen in max, only in Axoloti.

Here is a simple example: if I turn the toggle on, it should send a velocity of 1 to the note -56 (note 8) and turn on its led. But it does not.

↧

MIDI Latch LED button on and off

December 16, 2019, 3:52 am
$
0
0

I've tried it also like this:

I send a velocity of -64 (velocity 0) or velocity -63 (velocity 1). I realized that I should also, like the note number, be scaling back the velocity so that it is between -64 and +63.5. Unfortunately this also does not work.

any suggestions?

↧
Search

MIDI Latch LED button on and off

December 16, 2019, 3:54 am
$
0
0

as you can see the velocity input has a + sign only. this means that it is unipolar and you therefore need to send a value of 0 for velocity 0. for 1 you would send 0.5 (128/64 equals stepsize 0.5)

↧
↧

MIDI Latch LED button on and off

December 16, 2019, 3:56 am
$
0
0

in addition, mixing up green, yellow and blue signals tends to get messy. try with two dials and a mux for a start

↧

MIDI Latch LED button on and off

December 16, 2019, 4:07 am
$
0
0

Ok this is very helpful! Thanks for pointing that out.
=

I've now tried it this way, but still doesn't work: I'm sending a value of 0 for note off, and 0.5 for velocity 1.

Still doesn't work though...

I've also tried it with two dials and a mux, as you suggested, but also does not react.

↧

MIDI Latch LED button on and off

December 16, 2019, 4:11 am
$
0
0

theres a couple of problems...
as @lokki says , you really want to send in a unipolar signal into velocity
(if you actually care about the velocity value sent)

but the other problem, is kind of a bug/mislabelling on midi/out/note...
the trig input is actually acting more like a 'gate' than a trig.
you can see this by changing to the following.

tip: to test, I suggest you send to the usb device port, then you can easily monitor the midi messages going out :wink:

if we look at the midi/out/code we can see this pretty clearly 

if ((inlet_trig>0) && !ntrig) {
lastnote = (64+(inlet_note>>21))&0x7F;
MidiSend3((midi_device_t) attr_device, MIDI_NOTE_ON + (attr_channel-1),lastnote,inlet_velo>>20);  ntrig=1;
}
if (!(inlet_trig>0) && ntrig) {MidiSend3((midi_device_t) attr_device, MIDI_NOTE_OFF + (attr_channel-1),lastnote,__USAT(inlet_velo>>20,7)); ntrig=0;}

see the condition !(inlet_trig>0) && ntrig
this means, IF the inlet is low (false) and we have previously sent a note on, now sent a note off.

when you use a change object, this sends a quick pulse of true/false , and so quickly sends an on/off , hence the behaviour your seeing.

↧

MIDI Latch LED button on and off

December 16, 2019, 4:18 am
$
0
0

Thank you! that works... Super helpful... I had no idea the trig worked that way.

Thanks Lokki and Technobear.

↧
↧

MIDI Latch LED button on and off

December 16, 2019, 4:45 am
$
0
0

yeah, its unfortunately misleading...i think it should perhaps be marked as a gate rather than trig.

in this context, usually a trig means to output the new state on transition from lo-hi,
you would not normally expect a transition, back from hi-lo to do anything for a trig input.

unfortunately, changing (/fixing) the behaviour of such a widely used object now, would break too many users patches... so it is what it is.

anyway, glad you have it work now :slight_smile:

↧

Spacebar like key component?

December 16, 2019, 5:05 am
$
0
0

Hello,

I need a spacebar-like key I can plug into Axoloti, anyone knows where to find or search for one?

I am trying to emulate the wrist-key on this image:

Thank you very much.

↧
Search

Spacebar like key component?

December 16, 2019, 6:31 am
$
0
0

If you are looking for USB solution, I think it would be a pitty to take up the USB port for one single button. But okay, if you don't plan to use the USB port for anything else, I guess it's not an issue :slight_smile:

↧

Spacebar like key component?

December 16, 2019, 6:33 am
↧
↧

Spacebar like key component?

December 16, 2019, 6:38 am
$
0
0

i think axoloti only supports usb-midi. keyboard support was very experimental at best at some point. i would either:

-build my own spacebar key and buy a cheap momentary switch and connect that to the spacebar and read the status of the switch via a GPIO on axoloti

-take apart an old unused keyboard and mount a switch underneath the spacebar (or even use the stock "switch", this will be part of a key matrix though and maybe not that easy to work with for you)

↧

Spacebar like key component?

December 16, 2019, 6:39 am
$
0
0

Yeah makign something that resembles a spacebar, but not uses the USB port is probably the best choice :slight_smile:

↧

Help with controller object

December 16, 2019, 6:44 am
$
0
0

Hi. I know it has been dealt with many times but after having read through the relevant threads I'm still unsure about how to reference the controller objects. I'm even unsure as to whether controllers can be used this way.

Here is what I want to do:

-I want a selectable oscillator bank subpatch, so I can change oscillator types in my synth without having to load an entire new project.
-my synth has three oscillators, so I would like the bank to be available to each one.
-I want to control it by midi, allowing to scroll through the different oscillator types.
-I created this folder: Users/me/axoloti/controllers/oscillators and added it to my preferences.
-then the idea is to have a different subpatch, one for each oscillator type, and when I press a button on my controller the oscillator type changes.

Will this work or am i just wasting my time?

am I correct to understand that there can only be one controller object per project?
I would like at least three different live-selectable subpatches, one for each oscillator.

If it is possible: What should my file structure look like?

I think I would need three controllers: OSC1.axp, OSC2.xp, OSC3.axp.
each of these would reference the same "oscillatorbank" folder of subpatches.

It is really abstract for me, sorry... I can't yet wrap my head around it. Sorry if I am completely off...

Thanks you are so helpful!

↧
Viewing all 24308 articles
Browse latest View live
Search