Pure Data Compiler

Hi!
The PD compiler doesn’t seem to be working. I get the following error message:

[91mError:[0m An HTTP error has occurred with URL /a/heavy 405 Client Error: METHOD NOT ALLOWED INFO: make exit code is 2.

Maybe the recent changes at Enzien’s side broke something?

Hi trocado -

thanks for flagging this up. Yes, it seems that something has broken with our Heavy integration. I’ve raised an issue with them and we should hopefully have it resolved later today. Sorry!

It was a problem with the uploader, now fixed. I’ve tested a couple of Pure Data compilations and they work fine again - let us know if you have any more problems!

Thanks for fixing this.
Incidentally I can’t seem to be able to use the “print” object to pass messages to OwlControl: it doesn’t compile. The error is:
/tmp/ccEbszvW.ltrans0.ltrans.o: In function msg_toString’: <artificial>:(.text+0x4cc): undefined reference toftoa’ <artificial>:(.text+0x52c): undefined reference to `ftoa’ collect2: error: ld returned 1 exit status make[1]: *** [/tmp/owl-build-aGz3AY/patch.elf] Error 1 make: *** [patch] Error 2 ERROR: Patch build failed.

Am I doing something wrong or is this not working?

Oh, okay - that might be a problem with the web build. I will look into it.

print should be working now. We’re also updated to run on the latest Enzien Audio Heavy release.

How does print work exactly? Where should the messages appear in Owlcontrol?

From the documentation:
remember to test whether your patch runs in PD-Vanilla, testing using sliders (with the correct range) and debug with the print object. Once you’ve uploaded your patch you can use the print to display messages in OwlControl or in the midi tab of the patch page.

But I can’t find the messages in Owlcontrol and I don’t see a midi tab in the patch page.

They should turn up on the same line as the CPU reading, under ‘Remote Control’.
Are you on Firmware v12?

There’s not really a MIDI tab anymore, but if you click Connect to OWL and then Load it should show up by Message:, see e.g. https://hoxtonowl.com/patch-library/patch/untitled_96a7437d1dbb

Note: loading patches from the browser only works out of the box with Chrome!

I got it working in the browser, but not in OwlControl. Owl firmware is v12. OwlControl is version 11 (shows v10 though), on Windows.

Okay so that might be a Windows MIDI thing. Only one program at a time can access a MIDI device under Windows.
When Chrome uses Web MIDI, it seems it never lets go, so you can’t communicate with the device with any other program, including of course OwlControl.
You’ll notice if the little green indicator doesn’t come on in OwlControl, and you can’t select the OWL MIDI device in Application Settings even though it’s listed.
Closing Chrome doesn’t even help, it seems you have to open Task Manager and kill every one of the dozen or so Chrome processes that are still running. Oh Windows!

Hi, the uploader is failing again:

Building patch Gate [91mError:[0m An HTTP error has occurred with URL /a/patches/owl/owl/jobs/ 405 Client Error: METHOD NOT ALLOWED INFO: make exit code is 2.

I can confirm this is currently broken, looking to get it fixed asap!

Heavy uploader has been updated, working now.

Sorry for the glitch!

It’s working now. Thanks!

Have a problem with the pd compiler.
Patch compiled first, but when i tried reuploading a refined version i get

/bin/sh: -c: line 0: syntax error near unexpected token (’ /bin/sh: -c: line 0:echo Building patch CT5 Mode 1 emu (Pitch Delay)’ make: *** [.FORCE] Error 1 ERROR: Patch build failed.

upon pressing COMPILE in stderr.

Patch is here.

Thanks for looking into this!

I can’t remember right now how the patch name is processed by the compiler scripts, but perhaps it’s choking on the parenthesis. Was it working with this name?

You’re right. I removed them from the patch name and it compiles. Whew ha!
Check out the patch, it’s a lovely one for drums and monophonic instruments. Had just spent 250 € on an original Count To Five from 2016. What a gorgeous unit. And actually quite rebuildable on the OWL :wink: We should be donating to the original developer…

EDIT Due to renaming the patch is now here.

Damn, the .syx reports memory overflow in OwlControl… doesn’t run here. No sound whatsoever. Factory patches work…

EDIT: I’ll unpublish this for now.