Just trying to get my feet under the table and explore the character of the sound, and also get experience with the workflow
I have many many questions, most may be covered before, but i'd like to ask those i stumble across which don't seem tackled before (at least by my cursory searching)
I guess there are some fundamental things which i will get used to, but as i have established workflows i want to understand the reasoning for differences here and possibly explore workarounds
It's now evident you cannot patch a Yellow signal into Red
This would be doable in e.g. The Nord Modular or a real Modular or a soft-modular
This technique is handy to 'ping' a filter - catching the leading edge of a pulse signal, it acts as a momentary impulse if you have a resonant filter
My experience so far with the filter resonance is that it's quite harsh, but that's maybe a reflection of other early days patching confusion and keeping gain down
Is there a sweet filter to start with to get a feel for this, and is there any reason why a Logic signal can't be abused (through choice) in this modular environment ?
If we are stuck with the constraint, what's the most elegant way to excite a filter without a sound source as such ?
There's a pulse/dirac object that provides an impulse and can be triggered by yellow signals. Alternatively you could use conv/interp or conv/nointerp (probably better) to go from yellow to red.
The reason you can't directly connect blue to red is that red (sound) is treated ad s-rate, which is 48000 cycles per second. Blue (and yellow and green and pink) signals are treated at 1/16 of that speed (3000 cycles per second) instead.
The objects however "talk " between them at k-rate, and s-rate signals are transported from one object to another in packets (buffers), so if you directly connect blue outlet to red inlet what you're doing is feeding the red inlet with the wrong data type, which is not recognized
As for filters, they don't have a particular character. They're just biquad filters, really plain response
It's probably a key thing to work with going forward
But as i test it with the vcf3 the filter resonance (various values) it is either ringing on or not ringing at all
With my experience of resonance values and a ping, i'm expecting a 'natural' decaying filter, as per a Tom circuit e.g. .. so the filter is excited at full tilt and decays depending on the res val
Yes you can, you just need to use a conv/nointerp to convert it from yellow to red. This can be used to rst an oscillator, by connecting it to a sync input on the osc, for example. I have nord G2 and Nm1 and on does you are correct you can connect them directly. But for Axoloti you need the conv/nointerp object inbetween.
EDIT: Ah, I see it have all ready been answered, I was on mobile before and didnt see the answers.
It seems to be (partly) so. The 'resonance' of the filter is quite short-lived in relation to my 'expectation' for the desired characteristic. Especially in terms of it decaying naturally for an audible period once excited to resonance.
It may well be beyond the current filter. I just need to establish what's my limited understanding and what's the limit of this particular filter model
Even at 63.5 the filter resonates for only relatively few cycles, it's being given a temporary lift into infinite res in that example - i guess it's just the way these particular filters are which is a shame if you're chasing those west-coast vibes
Use shift+mouse to tweak the resonance parameter value in smaller steps than 0.5, or when a parameter is focused, you can also enter a value on the keyboard, followed by enter to accept (or esc to cancel). Or press (ctrl+)shift+arrow-up/down when a parameter is focused. But yes, the sweet spot is rather small, also in terms of signal headroom.
Also check the jt/filter/vcf4pole object in community library.
Okay - having been catching up on other basic workflow techniques i can see that there are modifiers to allow finer control - the filter will be more 'ringing' when the res is set to 63.95 !!
I do have a lot of general feedback that i think is useful although some may be misguided/premature - but there are a few new user insights i think that could be helpful to make all new user (or any) experiences a little smoother
If i want to start up a general catch-all thread with miscellaneous feedback for a new user with prior experiences will this be cool - it can perhaps sound critical if you only highlight places to improve by 'marginal gains' but i think these are sound ux ui observations worth throwing in the mix as i think of myself as a typical potential user
I see Johannes has just spelled out what i was just discovering, but i'll post this up now anyway : )
A connected how-to query that follows on nicely here, rather than asking in a new thread
I imagine there are a range of techniques to achieve a limiting of a range, but in this example, hypothetically, if i wanted to have a broad range of inputs to the resonance modulation input - could i ensure that the maximum submitted was 63.95 to avoid the infinite res position .. i'm not thinking of mathematical techniques more objects dedicated to scaling ranges or limiting values and so on
As it stands in terms of acquiring insight into the palette of objects it's going to be a rather dry reading experience, rather than looking through some pictures of the modules with example usage descriptions
id suggest a couple of (perhaps obvious) things first....
make sure you read the manual first and if its not correct/out of date, feel free to update it
search the forum for similar topics not only does it 'strengthen the request', but its likely we will have already commented on the topic. (the community is blessed with having lots of new users from many backgrounds, so the feedback has been tremendous!)
spend some time patching many things are done for a reason, that may not be obvious at first... and whilst axoloti is similar to say max/pd/g2 its not intended as a 'clone'
also... if you make one general post, it tends not be great for a focused discussion, it'll usually end up only discussing one or two points that others have views on.
have you looked at the tutorials, and the help patches attached to objects? there are of course gaps, but they are a good starting pointing.... and if you think they are missing certain aspects, we would be happy for you to contribute additional patches. (or build the 'thing' that you have in mind)
I have asked before, but will comment again - a new users perspective is a wonderfully unique experience, and I think it would be great contribution if new users could somehow collate 'gotchas' , unexpected things, tips, 'light bulb moments' as they embark on the journey, and then put these in the user-guide section. (not sure the best format, leave that up to the contributor)
I wrote alot of the initial version of the user guide, but honestly I was probably not the ideal person, I'm probably too technical, and when I did it, had already been involved (in a small part) of the coding... so didnt have fresh eyes (and honestly, I've never been a good documentation writer!) so there is huge scope for improvement and this is one of the reasons it was made available as a wiki so it could be edited by the community.
on the Elektron community, I know there are some very popular guides written by users, that are 'must reads' for newcomers - something like this for Axoloti would be excellent. (the issue with forums, is even though it can be searched, the information becomes very scattered)
ahh, hadn't found those yet, the whole new user path is a little reliant on intuitive searching in the early stages
that is ideal
I've been patching for maybe a few hours and i've lost count of the number of times i've cmd.clicked onto an empty part of the patcher to either exit or enter live mode (as you would in Max) (where you can also use cmd E coincidentally) It's those level of little cumulative things i wanted to offer as suggestions - often the tiniest things for the easily dissuaded make the difference between hanging around for the duration and giving up - i'm not the giving up type, but i do get frustrated by little things (such as the tiny startup windows for main/patch .. can these be user scaled to defaults beyond tiny?)
I'm also very much into establishing why things are the way they are, these moments are a reflection of understanding to a higher level - it's all too easy to ask a question and only reveal a little bit of ignorance - i'm basically cutting a few corners as a new user with lots of prior expectation, this just ups the number of 'apparent' obstacles to bypass
Okay - maybe just one last general Logic question, but again related to pinging filters - this is how i'd do it on the Nord Modular - it's a way to only get the Leading edge of a logic gate
this works out great - it ignores the gate closing
however, the same on the Axo is pinging on up and down .. any thoughts ? (was it a happy accident on the Nord)
you dont want to use nointerp, use pulse/dirac - this will cause the single sample pulse you want.
if you use nointerp, then you will end up with a sample buffer (16 samples) of ones, not the single pulse you are after. (all the control rate stuff is done 3khz, and so is not on a sample level)
as for the tone, use scope, on the output of the nointerp, you can see its causing a pulse wave, ... id need to think about this as to why... my guess would be due to your feedback line, which is executed one cycle later.
another note: have a search on here about excution order..., its worth understanding that from the beginning, you example is probably not executing in the order you expect it too hint: the wires are NOT determining the order of execution, but object placement !!!
I think this is all a good example, of how patches may not translate 1-1
i'm not sure if you mean straight after the gate, or in place on my screen dump - i will now try the latter, the former was no use as it had no stimulating effect
edit:makes no difference to the 'impulse' energy - very weak - but it also (whilst in that placement order) does not obscure the gate down
(and honestly, I've never been a good documentation writer!)
