You think there could possibly come any, some time in the future? Or do you think this was really it, and #246 is the Final Cut of updates for OG?
its probably it. and i think it went out with a bang adding usb audio support. i strongly suggest everyone with an og-1 try out the custom firmware. the filter effect alone is worth it. i’m surprised its not in the official firmware. its not like someone else modified or created the filter effect, it just got unlocked.
would love to see a terminal or lofi type effect on the og-1 though. i have the field and xy, love them, but still love the og-1 too
4 Likes
the more i think about it… hell yes there should be another firmware. unlock all of the cool shit !!!
anyone who agrees should high five this thread. reportedly, te read these things
1 Like
I think they should make the OG-1
OPEN SOURCE
And let the community continue to experiment with it since it’s discontinued
6 Likes
they will not do this. this is directly first hand from the source, not conjecture. the code was never made to be shared to the public. its in no shape to share or to mod. everyone would just brick their machines instantly.
3 Likes
I believe you dude hahah
When you speak , we listen!
2 Likes
Interesting. I’d love to hear more about this (speaking as someone with 25+ years of experience in software engineering for an open-source company). There’s already a successful precedent for opening the source code of complex musical hardware: the Synthstrom Deluge. That sequencer is still being sold by a company even smaller than TE.
Unless this vision was part of the initial development, code like this typically isn’t designed to be shared with the public. Still, it seems that it can be done. While I can understand an American company fearing litigation, neither TE nor Synthstrom strike me as being anti-consumer. Personally, I’m in favor of letting users risk bricking their machines if they’re willing to take that chance. For me, it’s unlikely I’d try it on my current OP-1 Field, but I would consider it with the OP-1 OG.
I say to TE: please release the OS in a state where it can be compiled and installed on the machine (which may require some work, I know), and leave the rest to the community. Maybe update TE-boot to robust-ify the “factory reset” a bit. Make me sign as many forms as you want, put it behind a ton of disclaimers, including one during the boot, and I’m still on board.
1 Like
100% agree
if they were willing to do this it would’ve happened already or would’ve been hinted at but te has never been about opening dev up to users (except with videolab unity stuff)
on the other hand they’ve ALWAYS been interested in physical mods and external augmentation
that open spirit never transferred to firmware/api etc
this? seems like exaggerration and i’m not sure if thats their opinion or yours
either way the worry may have been over allocating resources to deal with flood of queries if/when units got bricked as well as discomfort with public scrutiny of their code
i totally get that but it’s unfortunate…i think there are enough talented users to implement safe custom firmwares and feature extensions to beloved older gear
1 Like
their words, not mine. though it was in a casual conversation so i imagine hyperbole could be seen here but the same as any other just hanging out conversation, it wasn’t an intense technical discussion.
this is exactly all of it right here.
1 Like
i’m not familiar at all with writing firmware or whatever, but isn’t there already an option to add custom firmware to the op-1? some people hacked it, there’s a great thread here on the op forum…
1 Like
Yes, I’m familiar with much of it (though it’s a massive thread), but that’s not quite the same thing. A set of tools was developed to unpack and subsequently repack the OP-1 OG firmware. For a time, the OP-1 Field firmware could also be unpacked thanks to a hack, but then the encryption keys were changed.
Some resources, like graphics and local SQLite databases, were extracted, allowing for minor modifications to visuals and colors (great detective work by the group) and enabling a couple of filters to be restored. However, this isn’t the actual source code. The code driving the BlackFin DSP remained in its assembled LDR form. While they may have managed to disassemble it, understanding and reading that level of code requires significant expertise.
Having access to the entire source code, ideally in a higher-level form with comments, would make a big difference. That said, we’re now in the AI-assisted era, and tools like ChatGPT or other LLMs might have intrinsic knowledge they’ve absorbed that could potentially be leveraged.
Regarding the risks, I believe in treating people like responsible adults: if you choose to use custom firmware, you do so at your own risk and shouldn’t expect any support. Especially for the OP-1 OG—can you even return it for support anymore? It’s safe to assume all warranties have expired by now. Even for those willing to pay for repairs, TE could implement an online form with a straightforward first question: “Did you use custom firmware?” If the answer is yes, the process ends there (maybe you even have to send a picture of the bootloader in the process, for proof). And if someone lies and still sends in their OP-1 OG, and a custom firmware is detected, they shouldn’t expect to get it back.
3 Likes
It’s likely that there’s code in the firmware that they licensed for use in their device but couldn’t give away for all uses everywhere. Like the cwo, for example, perhaps.
2 Likes