I am wanting to expose the crash logs in the SSP… so when a crash occurs it will copy the log to the sd card and can easily be transmitted by a user
I added two params for my plugin – Show Crash Log and Generate crash logs
@thetechnobear you probably know 
there are no crash logs, nor anyway to reliably create them.
ofc, you are welcome to have your own logs for you plugin, wherever you like, but it’ll be about your plugin.
basically, what synthor does ( I believe), and I do , is push some logging to kmsg, i.e. what you see with dmesg. ofc, nothing thats in the dsp path. mostly its initialisation stuff.
and no, its not user focused, its really only there for devs, that’ll ssh into the SSP and want to get some trace info.
(also generally, not a good idea to be writing to an sdcard continually… though infrequent logging would be fine - also bare in mind date/time is never correct on the ssp)
whilst the SSP is NOT an embedded system, from a user perspective, Id say its treated like one… its a black box, it works or doesn’t 
unlike a computer where users try to help diagnose problems etc, mainly because everyones computer setup is different - here all out boxes are the same.
perhaps an ideal goal, rather than reality, but I do think its the right approach…
most that buy musicial hardware (instruments) want it to ‘just work’,
Yeah. I have logs creating successfully for my plugin at least.
“perhaps an ideal goal, rather than reality, but I do think its the right approach…
most that buy musicial hardware (instruments) want it to ‘just work’,”
except for us
I always find stuff in modules I would like to change… or add or swap… etc… thats why I love modules where the dev has opened sourced it
matter of fact huge respect for the devs that have opened source their discontinued product – just continues breathing life into it
yeah, I appreciate open source projects…its a generous act.
but even as an advocate, I also feel strongly that people realise it is the developer choice, no ifs, no buts. like a musician, the developer should own what they create, and have free choice how its used or not used … as inconvenient as that may be.
(ofc, Im talking about ‘in their own time’, devs working for someone else is different)
you mean as devs, sure… but as devs, we always have tools to get into a black box, thats not an issue.
I do think its right that the SSP is seen as a musical instrument, to use ‘as is’, rather than as a devs playground. we all have enough computers in our lives.
this is something a bit ‘different’, first and foremost for me, its a eurorack playground / lab
that said, its a bit of a ‘me’ thing,
Ive struggled for a long time, keeping my music and engineering side “balanced”.
I find it way too easy to fall into engineering mode, and ofc, others often appreciate that
But its kind of hard, when I look at my music gear, and realise Ive spent too much time coding, and not enough time making music… even though, I love coding.
Ditto…. I do this all the time.
yeah, i guess, we aren’t the only ones…
ofc, the modular space, esp these kind of modules its ‘so easy’…
Its why I love things like my Osmose and Octatrack,
no real possibility to get pulled in, turn turn on and start recording and looping and layering.
I love using Live etc, but even there the temptation to tweak, is always there on a computer.
its funny, Ive avoided generative stuff (coding based, not chaos/random) for quite a while, to stop the pull of engineering,
but its an area I do want to explore more… as itd be fun to leverage my engineering side in a musical way, thats not ‘product development’, but creative injection
I always wondered why. A musician developing gear wouldn’t do X or Y. Or the workflow is wonky. Or missed opportunities etc. I always thought obviously he has been using this all the time. He’s a musician and he building this because it’s something that he’s missing in his rack or something.
But I think what happens is you start getting passionate about whatever your developing and you just don’t have the time to actually jam as much as you did while you’re developing and so the thing you’re developing, you actually use for less than you would’ve because you’re spending so much time developing it versus just playing versus if you just bought whatever thing or got it from somebody else
nah I disagree, and its a mistake many users make when they reflect on software…
( you hear it in gaming a LOT… do these devs not play their own game?)
whilst this might be true for a tiny minority of developers,
most I have come across (and hired) are usually passionate, professional and pretty thorough about what they do…and the more niche it is, the truer that is. though, even true in ‘big companies’
devs spend hours on features, debugging… they know (or should) know their project and problem space really deeply… they also often have access to ‘field experts’ they can call on.
often, the reasons, are much more mundane… (developers) vision, (project) scope and resourcing.
unavoidable truths on anything but trivial projects.
but its something users don’t see ,nor really (understandably) care about…
they just wish it did X , and what can be frustrating is, they know software is soft, they “know” it could be done - IF the dev wants to, hence… if they dont, SOME users will resort to they are lazy/untalented
you don’t see it so much with hardware (ignoring firmware), as the product is what it is… and unchangable. users know it either fits their needs or doesn’t…
software is often 90% there for them, and that last 10% is annoyingly ‘just out of reach’