robertsonics/wtconfig

Tsunami / WAV Trigger Unified Configurator Utility

WTConfig

Tsunami /WAV Trigger Unified Configurator Utility

This project is written using JUCE, the cross-platform C++ framework. It will build successfully on Window (Visual Studio 2015), OSX (Xcode) and Linux (make.)

wtconfig's Issues

USB TTL adapters not recognized on macOS

Your apps are not finding my serial adapter. I have a cheap generic USB↔︎TTL adapter which IOKit lists as follows (on macOS 10.14.6 at least):

{
    CFBundleIdentifier = "com.apple.iokit.IOSerialFamily";
    IOCalloutDevice = "/dev/cu.Repleo-PL2303-00001014";
    IOClass = IOSerialBSDClient;
    IODialinDevice = "/dev/tty.Repleo-PL2303-00001014";
    IOMatchCategory = IODefaultMatchCategory;
    IOProbeScore = 1000;
    IOProviderClass = IOSerialStreamSync;
    IOResourceMatch = IOBSD;
    IOSerialBSDClientType = IOSerialStream;
    IOTTYBaseName = "Repleo-PL2303-";
    IOTTYDevice = "Repleo-PL2303-00001014";
    IOTTYSuffix = 00001014;
}

There's two troubles here:

1. In your

   WTConfig/Source/mac_Serial.cpp

   Line 44 in 6df9642

   CFDictionarySetValue(classesToMatch, CFSTR(kIOSerialBSDTypeKey), CFSTR(kIOSerialBSDRS232Type));

   you are matching on kIOSerialBSDRS232Type. If you search for kIOSerialBSDAllTypes instead, this will at least be included in the results of SerialPort::getSerialPortPaths.
2. In

   WTConfig/Source/MainComponent.cpp

   Line 213 in 6df9642

   if (portlist.getAllKeys()[i].contains("usbserial")) {

   you are further filtering the list such that the kIOTTYDeviceKey (IOTTYDevice above, what your mac_Serial code calls the "friendly" name) has to include the string "usbserial" — in this case the friendly name is "Repleo-PL2303-00001014" and gets discarded.

This affects all the apps (WT-Flasher, WAV-Trigger-Remote, etc.) but filing here as it's sort of the "main" app. There's not a real easy workaround other than to fix the code, although by carefully tweaking the string constants (and one corresponding CFString length field) in the app binary I was able to get the flasher tool to work on my own machine.

Unable to Install/Compile under GNU/Linux

Could provide some more precise instructions on how to compile this utility under GNU/Linux?

There's this blog entry, https://robertsonics.com/2017/11/26/new-unified-init-file-maker-app/,
which states

"you do have to download JUCE, install some dev packages, and then run make on the source project"

but where do I get that JUCE you are talking about. Is that it?
https://juce.com/
... I mean that JUCE claims to be an audio software, which is confusing, because WTConfig is only supposed to write a text file.

I installed JUCE (hopefully it was the right one), but when running make I get

make: *** No targets specified and no makefile found.  Stop.

Question about velocity and the license

Thanks for the great work RObert. I'm willing to contribute to this project but I wonder:

1. what is the license of the code? It doesn't mention it anywhere.

2. the feature I am VERY interested in is defining different wave files for different velocities, or ranges of velocities. It seems that currently this feature is not programmed, or is it? If not, do you have any suggestion where to start and how it should be implemented?

Cheers,

juce_core.h missing

Hi

I tried to compile this on Arch Linux and got an error that juce_core.h is missing:

Compiling AudioSettings.cpp In file included from ../../Source/OutputComponent.h:23, from ../../Source/AudioSettings.cpp:22: ../../Source/../JuceLibraryCode/JuceHeader.h:17:10: schwerwiegender Fehler: juce_core/juce_core.h: Datei oder Verzeichnis nicht gefunden #include <juce_core/juce_core.h> ^~~~~~~~~~~~~~~~~~~~~~~ Kompilierung beendet. make: *** [Makefile:103: build/intermediate/Debug/AudioSettings_52f030fa.o] Fehler 1

False triggering in active mode WTconfig

I'm triggering the wav trigger using a movement sensor that goes HIGH when movement is detect.
I set the init file as follow:

Trigger: 1
Hardware Interface: Active
Type: Edge
Function: Normal
Invert: tick
Re-trigger: untick
Polyphonic: untick
loop: untick

most of the time it works as it should: new triggers will not restart the track until finished. Sometime it happens that new triggers are indeed restarting the track, which is not desired.
What could be the issue?