“oh hey nerdy person, do you love small talk?!”
I used to think I was good (and perhaps I was in my youth, doubt it…) but today i hit a wall so quickly and feel I’m probably staring into a corner of the room while drooling.
3 Likes
I fully agree that we are not aware of the code base. And being able to say « this is simple to code » or « that is harder to code » can be problematic specifically for the guy reading it and who will be in charge of the job. And some code base could be a nightmare to deal with.
But I can not see this as simple as black or white. And don’t speak you are not part of the project so you have no idea if it’s simple or not. If you have develop a VST or done some embedded you might have clue how the challenge would be on specific features.
For example, I really guess putting a second filter on the DT, per track, might have been a bigger challenge on the technical side than putting a song mode.
It’s really two different thing to implements. And it require fully different skill set.
But the optimization that might be required for the filter one might have been - I guess - more challenging than the UI update, project management, and validation of the workflow of the 3xDigi to put the song mode…
I don’t say that there is more/less work between second filter and song mode. But I really guess the « song mode » is probably easier, maybe more work long term but easier.
Needless to say that I have no clue on how Digi code works. But there is feature on embedded system which are definitely high challenges. Specifically when you need to deal with performance, real-time and crude optimization.
Or at least, on my side I know when I code something, if this part will be really complicated because I’m already near full at cpu level or ram. And sometime I’m surprise how hard another task which look simple became a nightmare.
But I can not think as everything is equal to another thing. Or it lead to, we can not discuss about thing because we have not read the source code or make any commit on the code 
And at least good work Elektron on those fabulous update over time ! You’re my favorite company for music 
3 Likes
One of the unexpectedly cool things about Chicago is that you can talk to literally anyone about music, art or boats and get an enthusiastically positive response. If all else fails, my sailor’s enthusiasm for weather is a match for any farmer. I just have to remember to not try to do small talk when I’m on the east coast or west coast. 
File under “we clearly live in a simulation” - years ago I lived above a Seattle coffee shop. One day, I ran into a very nerdy guy who was also good at small talk. We started talking about his cinematography hobby before he revealed that he too paid his bills writing software. In Smalltalk. So I upped my small talk game by talking to a Smalltalk guy.
8 Likes
“It should be simple to code”
A very good attitude to have by the way, when you actually sit down to type.
3 Likes
I’ve actually had those conversations with management, where they say “We want X” and I tell them that’s not possible. They say, “What would it take,” and I tell them literally rewriting the code from the ground up.
The funny part is that was supposed to be my way of dissuading them. Unfortunately, they took me up on it 
2 Likes
<SHUDDER>
3 Likes
Lucky he wasn’t a Brainfuck guy. [->-.-<-]
2 Likes
So with all these bright minds in here, I just downloaded the Analog-Rytm_MKII_OS1.46_BETA1 from the forum and it’s a .syx file… how would you convert to something that is then ‘Hopper friendly’ ?
I’m fairly comfortable making general statements about how complex something is to do given I used to run a team of embedded developers writing realtime audio processing hardware.
However it’s not possible to make judgements about the implementation complexity of a feature on a specific device unless you are familiar with it.
I worked with one device which hadn’t been architected properly and so all the synchronization was done manually with hand crafted waits. Literally any line of code added anywhere could break anything.
Adding a new effect to a groovebox could be the work of a few hours if you were using an open source algorithm and had loads of CPU to spare or it could be months if you were short of resources and needed to rearchitect a bunch of stuff.
10 Likes
Can you explain what “Hopper friendly” means?
Which Operating System are you using? You would choose whatever application to upload sysex through.
https://www.elektron.se/us/download-support-transfer should be able to up a SYX file to your Rytm.
Man, times are changing. It’s not all nerdy little fuckers anymore… At least in California there are a bunch of big, gym-addicted “brogrammer” types, who think they sound cool when they talk tech in public. They’re probably also all over the internet saying things “should be easy to code”.
3 Likes
Hopper is a disassembler 
1 Like
There are incel-adjacent “gymbros” who do code for a living, there are also hustle-grindset “influencer” style NFT/crypto/GME/AMC/GaryVee style fake-it-till-you-make-it sorts that would have become “Amway Mentors” twenty years ago.
Oh lol yeah I just assumed that the “coding this would be easy” sort can read assembler natively, like the Matrix.
2 Likes
I actually just opened it on macvim with xxd and looking as hex file ahahahahahahahahahah 
I guess the first step is to remove the midi msg wrappers to get the actual bytes
Still sound like nerds to me.
I bet they’d still have piss running out the bottom of their trackies if you showed them a real day’s work.
3 Likes
Are you a debt collector for the mafia or something?
4 Likes
I do look like one, to be fair.
But we don’t have any Mafia round here. In fact, the only gangsters round here are car park operators and they can’t offer me the glamour, kudos and free drugs that real gangsters like the Mafia offer.
1 Like
For example, the file starts like this: f000 203c 0c00 7f
this is a midi SysEx message (f0), followed by elektron identification 00 203c, as found in Manufacturer SysEx ID Numbers, followed by probably their command that says that we are transferring a file 0c 00, followed by the close of the midi message 7f. I just wondered if there was a common protocol for transferring the firmware through midi, similar to the Midi Sample Dump Standard for audio file, for example
My mental image of you has just been completely ruined.
nice thread. made me feel like «thanks Great Chaos that i don’t code for living».