flashstorage branch?

Home Forums OWL flashstorage branch?

This topic contains 8 replies, has 5 voices, and was last updated by  Martin Klang 1 year, 3 months ago.

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
  • #2885


    What’s the current stage of the flash storage development?
    Do you guys have a timeline for a release whatsoever?



    I’m also interested on this. I think this will be the best improvement since I have the OWL.



    Yeah! (Besides putting more buttons, faders and switches into that stomp box, which i am planning since long, but didn’t dare to do it yet…)



    Martin? Any news about this?


    Martin Klang

    I’ve been revisiting this last week, but hit a couple of reliability issues, which is not good for non-volatile storage. I’ll try to find the time to fix a few things and release a beta version.

    To prioritise: what functionality are you most after?
    1) more user slots (ie all 40 programs)
    2) the fast exp and log implementations I’ve been promising
    3) ability to store and retrieve data, e.g. samples
    4) something else?



    Hey Martin, I’d test a beta version right away!
    I personally i favor

    – more user slots.

    – replacing exp in gen with the codebox workaround i proposed here is not an option? Worked fine for me, though it actually might need readjustment for certain value ranges (untested besides i used it in a transpose to pitch situation).

    – i have no use for samples myself, other than sampling from live input, which is possible already. Hardcoding sample into code could be sexy for some i suppose. A user Sliderule over at the Patchblocks site developed a cool idea for this including a sample to code converter on a website. Just FYI.

    – some guitar pedal manufacturers provide MIDI over jack input things (Chase Bliss), this could be an interesting thing, if only to select patches without having to use the push button, but not just that.

    Thanx for the good news!



    Hello Martin,

    I’m mainly using the owl for small, quick setups at live gigs, where I don’t like to bring Laptop etc.

    So my list would be
    1) more user slots (ie all 40 programs)
    2) the fast exp and log implementations
    3) the ability to directly attach a midi controller via usb.

    tnx a lot for all the effort




    Hi Martin,

    Just checking in on the status of this development. I’d be happy to test a beta version as well.

    Thank you!


    Martin Klang

    The OwlWare firmware updates have become a bit of a mess. We’ve been struggling with adding features to an old codebase and with the lack of support for the ST peripherals libraries. No news there!

    So I started a clean-room firmware implementation, taking all the bits that work well in OwlWare and restructuring the whole project. And making it work not just for the current OWL Pedal and Modular hardware, but also for the prototypes we’ve been developing here with updated hardware.

    You can find it here: https://github.com/pingdynasty/OpenWare

    It’s still a work in progress, but the new structure will make it much easier to add features in the future. And it already has a working flexible filesystem (more user slots!) and better memory allocation strategy.

    The new firmware is really important going forward, to ensure that the current hardware will still be supported even if/when we launch new products.

    Apologies that it’s all taking longer than expected, but the end result should be worth it! I’m hoping to have a beta release ready fairly soon. From there on it will be easier to accept push requests too, should others want to contribute.

Viewing 9 posts - 1 through 9 (of 9 total)

You must be logged in to reply to this topic.

Latest News


Follow us on Twitter