Will the Befaco Oneiroi be coming to the 4ms Meta?

Personal view. Let Befaco sell through the hardware and the hardware with PODs. Eventually, sales and enthusiasm will decline and it should make it palatable to port to MM. Befaco is a business afrer all.

1 Like

i had to send mine back due to all the issues (calibration, -5-+5 pitch CV etc). But Befaco was very responsive and appears on top of it.

This module is already on VCV and I have bought it ($35) so I would love to see a meta port soon! Any updates? Is meta already constructed so that only people who have bought premium modules on VCV can then use them on meta or isn’t it a thing?

1 Like

Yeah personally inwould gladly pay for yhe premium on VCV to get access to it on my MM, but i do get there are some basic constraints that make figuring this process out not ideal (or well, not a top priority) at the moment

Anny news about the Oneiroi?

curious too!

2 Likes

me too

1 Like

Interestingly, it was recently ported as a plug-in for the Expert Sleepers Disting NT by a third party (not Expert Sleepers) using the source code published on Befaco’s GitHub site.The last time I saw a post about it, the individual who ported it was still performing optimizations on it. It apparently pushes the NT’s processor to its limits.

1 Like

thanks for that @Rrobosyn … led me down an interesting rabbit hole.

I did not know Oneiroi was based on the OWL platform :slight_smile:
I can see how that would lend itself well to other native platform ports, via an ā€˜owl’ wrapper.
might be fun to create one for 4ms Meta (and others), owl is quite interesting generally.

specific to vcv/meta, the vcv port is closed source , so its down to hemmer.
(unless someone decides to do their own variation based on the hardware version open source - as above)

1 Like

Thank you very much for providing that additional context. I didn’t intend to imply in my post that since it was ported to one technology platform (the NT) that it should be able to be ported similarly to the MM, although I see that it could have been interpreted that way by some. Programming code is not something in my wheelhouse, but I do recognize that MM & the NT are very different platforms with respect to the coding of the plug-ins.

no, I didn’t take it that way… rather I was thankful you led me down an interesting avenue, so wanted to thank you - and thought id add some ā€˜extra info’, that I thought was an interesting aside.

I think owl could be an interesting avenue to explore , as its user accessible - its something I looked at almost a decade ago, and had almost forgotten it existed :slight_smile:
(actually, I think when they released Witch and Lich it hit my radar again briefly)

Just to say, unfortunately I’ve just been slammed with other projects (including two young kids!) at the moment. It does compile and run, but there are still few rough edges to iron out. I’m hoping to carve out a little time to get it over the line, maybe with a little help from Dan. Thank you for patience!

It’s also unfortunate that it’s not possible to open source the vcv side of things (vcv rules on premium plugins)…

6 Likes

Knock.. knock.. :sweat_smile:

2 Likes

Yes please…..

Befaco Oneiroi’s transfer to the 4ms Meta is more than a simple copy-and-paste task, so don’t hold your breath. Everything from VCV or desktop builds must be modified or optimized for the embedded environment, including the CPU budget, memory restrictions, real-time constraints, etc., as Meta operates on the 4ms firmware stack (Daisy-based). Granular + fx + modulation makes Oneiroi’s internal architecture quite complex, making it non-trivial on Meta hardware.
It’s unlikely to just ā€œappearā€ until Befaco formally commits to a Meta build. It is theoretically possible, but it would need a dedicated port and significant 4ms Meta optimization.
would be amazing, however. In a tiny system, Oneiroi on Meta would be crazy.

The MetaModule isn’t built on a Daisy. I don’t think any 4ms modules use the Daisy but definitely not the Meta.

Update!

First @LisaHall is on the right lines in terms of complexity, but no MM isn’t daisy based. Oneiroi is written for OWL platform (hardware land), which needed some work to get working in VCV (software land), which need further work and optimisations to work on MM (back in hardware land) so it’s gone full circle! Dan has been helping with those optimisations. Befaco would like to see it on MM, but it is a side project amongst lots of other fun projects. :slight_smile:

Anyway, I finally managed to find time to get a workable flashing/debug process up and running using my STLINK, but it takes 2 minutes to re-upload every time I make a change. :melting_face: But I did manage to get a coding agent to live debug Oneiroi MM plugin over JTAG using tmux which felt like black magic :mage:, I might do writeup if there is interest.

Next steps:

Fix bug where module would be silent (NANs for exceeding Nyquist for 32k sample rates :person_facepalming: )
Prepare patch that lets metamodule draw most recently touch widget on top (needed as have multiple layers of knobs with visibility - Draw most recently moved knob on top by hemmer Ā· Pull Request #559 Ā· 4ms/metamodule Ā· GitHub
[~] Loading saving WAV files for looper (partially done, but needs testing)
[~] Momentary light buttons for record etc. Technically working but looks janky.
Improve legibility of graphics

6 Likes

Thanks so far… :innocent:

There is definitely interest from me!

1 Like

Very interested!

2 Likes