Migrate to Wasted-Audio branch of hvcc

[shakfu]

I just saw that you refactored the owl modular / owl pedal code.

If one owns an owl modular should one use the 'refactored' owl pedal code?

On a totally separate note: To what extent is the heavy compiler still used in your platform. I note that your fork of the compiler is still only python 2.7 compatible. Incidentally there's a completed python3 fork that could be useful to you is this still relevant: https://github.com/Wasted-Audio/hvcc

[pingdynasty]

I'm planning to release a new firmware today or tomorrow:
#55
this will have an OWL Pedal and OWL Modular binary, which you can update using webdfu (instructions to follow).

hvcc: thanks for the link, I'd not seen that. We will probably wait until a stable release is ready, then backport our changes.
We use heavy obviously for Pure data patches, on our online server, and also support it locally with OwlProgram.

[pingdynasty]

Hi there, firmware release is now done:
https://github.com/pingdynasty/OpenWare/releases/tag/v21.2

and upgrade instructions are here:
https://community.rebeltech.org/t/new-firmware-openware-v21-2/1677

any problems hit us up on the forum!

[dromer]

@pingdynasty it's hard to determine when a release can be considered "stable". It's very hard to test all of the various targets that hvcc aims to integrate with!

However compared to the original code-base I'm already quite happy that we have it working for modern python3 with at least basic acceptance criteria. Hopefully when we get more tests working some better grasp on reliability will come.
"original" hvcc doesn't have any of these acceptance criteria of course, nor can it be installed in your path.

Internally everything still works the same. More testers and fixes are of course always welcome to make sure that every ones niche target still works! ;)

[dromer]

Btw I believe I have ported most of your hvcc fixes into my fork as well: https://github.com/pingdynasty/hvcc/commits/master
Together with commits from a bunch of other forks. I think it would certainly be better if we reduce all the fragmentation and concentrate the efforts on a single project.

I accept pull requests :)

[pingdynasty]

Reopening to track migration task