pingdynasty/firmwaresender

Utility program to package and send firmware and dynamic program images to an OWL.

firmwaresender's Issues

Leak assertion fail in debug builds

FYI a current build of d9e0d95 on Mac OS X

…if I build it in the Debug configuration, then every time I run it with parameters (IE, if I pass -l or -in -out) it prints this as its final two lines

*** Leaked objects detected: 1 instance(s) of class MessageManager
JUCE Assertion failure in juce_LeakedObjectDetector.h:88

If I build in release configuration I don't see this, I assume because assertions are disabled.

Can only send in debug (not release) builds on OS X

I am on OS X 10.13.6 with Xcode 10.1 Build version 10B61. I checked out FirmwareSender and did two builds, a debug build with xcodebuild and a release build with xcodebuild -configuration Release.

The debug build works. If I run

./FirmwareSender/Builds/MacOSX/build/Debug/FirmwareSender -in Build/patch.bin -out OWL-MIDI -run

It prints

JUCE v5.2.1
Sending file patch.bin
        to MIDI output
checksum 0xec0c1cf4
*** Leaked objects detected: 1 instance(s) of class MessageManager
JUCE Assertion failure in juce_LeakedObjectDetector.h:88

(It does that last thing every time and it is harmless, see issue #3.)

But if I -run with the release build

(cd .. && ../FirmwareSender/Builds/MacOSX/build/Release/FirmwareSender -in Build/patch.bin -out OWL-MIDI -run)

I get

CoreMIDI error: 387 - ffffffce
MIDI device not available: OWL-MIDI

I don't know what that error is. The docs seem to suggest all the expected error messages are in the negative ten thousands.

Leaked object messages in Debug build

When running the Debug build on Linux, a number of messages come up similar to:
*** Leaked objects detected: 1 instance(s) of class MidiOutputDevice JUCE Assertion failure in juce_LeakedObjectDetector.h:95

This should be fixed and a new release produced.

Feature request: -erase for patches.

I can use FirmwareSender to -store a patch. However, there is no way in FirmwareSender to delete a patch I have uploaded. What if I upload the wrong patch, or store to the wrong number? In fact there seems to be no way to delete patches at all except to use the Device web app and erase the storage completely.

There should be an -erase NUM option to FirmwareSender. If for some technical reason it is only possible to erase patches off the end, that would be fine.

xcode needed for FirmwareSender Compilation

Hi,

Trying to compile for OSX, but (very) reluctant to download and install Xcode. Is there a simple way for you to add a generic make file? That would be very much appreciated. I tried compiling the linux build, but of course that did not work (alsa)