-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Would be nice to have a linux version #2
Comments
I tried to build it on Linux but I have 0 JUCE experience. My first finding was the missing include for the serial implementation in UpdaterApplication.cpp. I added the following:
and
But I can't even start the build because the buttons are greyd out. I guess that there's something missing somewhere but I can't figure it out. (No error messages or such) But even when this would compile I would hesitate to use the tool because there's no official statement about the functionality. Maybe the Linux implementation of LinnStrumentSerial is broken and will brick my LinnStrument. |
Hello unidentified person,
I’m sorry but LinnStrument programmer Geert has a heavy workload and therefore is unable to help you with creating a Linux version of the LinnStrument Updater app.
Perhaps it might be faster to visit a friend who has a Mac or Windows computer on those rare occasions when a LinnStrument update is released.
Best,
Roger Linn
… On Sep 18, 2019, at 9:26 AM, Noir ***@***.***> wrote:
I tried to build it on Linux but I have 0 JUCE experience. My first finding was the missing include for the serial implementation in UpdaterApplication.cpp. I added the following:
#if JUCE_MAC
#include "LinnStrumentSerialMac.h"
#elif JUCE_WINDOWS
#include "LinnStrumentSerialWindows.h"
#else
#include "LinnStrumentSerial.h"
#endif
and
UpdaterApplication::UpdaterApplication() :
#if JUCE_MAC
linnStrumentSerial(new LinnStrumentSerialMac())
#elif JUCE_WINDOWS
linnStrumentSerial(new LinnStrumentSerialWindows())
#else
linnStrumentSerial(new LinnStrumentSerial())
#endif
{
};
But I can't even start the build because the buttons are greyd out. I guess that there's something missing somewhere but I can't figure it out. (No error messages or such)
But even when this would compile I would hesitate to use the tool because there's no official statement about the functionality. Maybe the Linux implementation of LinnStrumentSerial is broken and will brick my LinnStrument.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Hello Roger, Thanks for your lighting fast response. But it's a fact that Geert is busy so I'll go this way. Maybe I will just change the default values to match my preferences. Cheers, |
Thank you for understanding, David.
… On Sep 18, 2019, at 1:24 PM, Noir ***@***.***> wrote:
Hello Roger,
Thanks for your lighting fast response.
I'm planing to modify the firmware of the LinnStrument (And if it's stable and usable enough I'd issue a pull request). Therefore, I'd have to patch the firmware quite often. I'm aware that there's the way of uploading the firmware directly but I'd like to avoid losing my settings every time.
But it's a fact that Geert is busy so I'll go this way. Maybe I will just change the default values to match my preferences.
Cheers,
David
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Update on that: I also tried the update in a virtual machine (Virtualbox is the hypervisor) but the updater is unable to retrieve the settings of the LinnStrument. Sometimes it works for some projects until it fails. I guess the update process is very time critical and the USB forwarding process is not playing well with this. I guess when the settings could not be read, the calibration data is lost. I also made some progress in building the JUCE app but as long as it's unconfirmed that the Linux implementation of the LinnStrument serial interface is working correctly I don't want to risk breaking something. So the whole process is still an issue to me. A physical windows machine is not feasible to me. Cheers, |
Hi David,
My site's Source Code page (accessed from the LinnStrument menu) tells you how to upload without losing the calibration data.
Roger Linn
… On Oct 14, 2019, at 3:07 PM, Noir ***@***.***> wrote:
Update on that:
I tried updating within the Arduino IDE and it worked fine so far. But I realized that the calibration data is also lost with this. And calibrating the LinnStrument is not that easy... (even though it looks very easy in your video, I guess you did it hundreds of times) Since I'm still in the learning phase of controlling the LinnStrument I fear that re-calibrating it could change the behavior (reactions) a bit which makes it harder to control.
I also tried the update in a virtual machine (Virtualbox is the hypervisor) but the updater is unable to retrieve the settings of the LinnStrument. Sometimes it works for some projects until it fails. I guess the update process is very time critical and the USB forwarding process is not playing well with this.
I guess when the settings could not be read, the calibration data is lost.
I also made some progress in building the JUCE app but as long as it's unconfirmed that the Linux implementation of the LinnStrument serial interface is working correctly I don't want to risk breaking something.
So the whole process is still an issue to me. A physical windows machine is not feasible to me.
Cheers,
David
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#2?email_source=notifications&email_token=ABU7KZ6SZ6K4TIU4QCIJ4MDQOTUR3A5CNFSM4EULY6Q2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBGYEPA#issuecomment-541950524>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABU7KZ3VDED47BEH6A6JHATQOTUR3ANCNFSM4EULY6QQ>.
|
Hi Roger, yes I know this method and the updater tool in this repository is part of it 😉 |
Since it is based on Juce, it should not be too hard. At least a CLI tool would be nice to have.
The text was updated successfully, but these errors were encountered: