a bit of an overview on answers since quite a lot of questions, feel free to ask for more details, and I'm sure others might add some more 'flesh to the bones'
there are a few youtube demos, but as you say like most synths, its rare to publish things 'raw' as its never complimentary when compared to other synths swimming in reverb
there is also a huge set of combinations to explore with things like filters, and you can also do wavetables, samples.
...hmm wil have to think about this.
you have to take the patch live i.e. send it to the board and run it.
so load it, take it live ... this takes a few seconds.
but you cannot just browse.... interesting idea thought, to perhaps save 'previews'
I think the latency will be very good, usb in is processed 'immediately' and then processed at 3khz.
Ive used with the soundplane (so alot of data) and didnt notice any latency.
yes, 'easy' to do with patching.
we do support sysex on midi output for usb, it could be added easily for din
the reason for no input as yet, is sysex messages can be of arbitrary length, and axoloti has 'limited' memory... this means we would have to do 'byte level' processing, and even then the user would have to be careful with memory.
(we allocate memory upfront for the patch, so as to avoid dynamic memory allocation and GC etc)
so no, its not a fundamental limitation, more really down to thinking 'how to do it', and also discovering what use-cases people have.... why do they want axoloti to process sysex, or is it just 'midi thru'
Im not quite sure what your driving at... you can code your own custom objects in C++.
obviously there are some 'framework limitations' e.g. how we send midi around..
again, not fundamental limitations, just what we expose in the 'api'
we don't use Xcode... 10.9 is fine....
java is installed by apple... so you'll be fine
I'm sure @johannes will answer this.... there might be some answers in the hardware faq in the user guide section
hardware its all possible.... slicing etc there are some objects, but as always the 'devils in the details'
it can record to memory, no saving to SDcard, but this could be done, the 'trick' is to do this without having audio glitches,
Im pretty sure the shipping version is not scheduled for any updates
(the only update so far, was adding a bit of extra protection - to avoid an issue a very small number experienced.. there is a detailed post about this somewhere)
again, @johannes will tell you stock levels, I think the website is accurate?
patches can be selected dynamically from computer UI, or by dynamically e.g. via midi messages , gpio etc.
im a user/contributor ... and a fan of axoloti, but don't have any kind of 'investment'...
so heres my opinion, also based on alot of what I've seen on this forum too.
Axoloti is extremely flexible, and its easy to get things patched together using existing 'objects'.
where some have 'fallen foul' is like any modular environment, its designed for you to patch things together rather than be a 'complete system' you plug in and just go... so it does require investment of your time, and the more complex a system you want, the more time it will take!
also, the best way to approach patching (I think) is also to be flexible/creative, sometime an object might not do exactly what you want (e.g. to emulate a piece of hardware) , but often, you can adapt...
also, im not saying there is a limitation to the axoloti hardware, I think its great, but obviously a G2 is 1000 euro (used) and an axoloti 65 euro (new) , so expectations have to be 'managed'.
at the end of the day, like most things (especially complex things) the more time you put in, the more you will get out...
on a parting note (hope this doesn't upset @johannes ) , kind of summary...
if you want think you will enjoy, building things, something new, something to your own desires. Axoloti is fantastic... much better, than say a PI/Arduino (imho, due to the integrated software environment)
if you think you want to emulate a piece of hardware, then you might want to consider how complex that device is... what features does it have?, what do you need? then consider the time required to build this, using basic building blocks... then is that worth it to you?
(your in a good place to do this, as your used to Max/MSP so its going to be similar, albeit you have a new learning curve)
anyway, too much waffling, but I hope some of this may be useful, and as I said at the beginning if you want to 'dive' in to more details, happy to answer more questions.