Jonatan Liljedahl
Jonatan Liljedahl
On windows it simply has `MIDIEndPoint("Island1", "Island1"), MIDIEndPoint("Island1", "Island1")`, while on macOS it has `MIDIEndPoint("Island1", "Port 1"), MIDIEndPoint("Island2", "Port 1")`. Not sure if this is a PortMIDI bug or SC.
This is the USB info on mac, btw: ``` Product ID: 0x0485 Vendor ID: 0x16c0 Version: 2.73 Serial Number: 7750070 Manufacturer: Teensyduino ``` serial number and product name are different...
I have now also tried changing both manufacturer string and midi port string, but SC still sees them as having the same name.
Here's someone having the same problem 6 years ago: https://stackoverflow.com/questions/63195134/usb-midi-device-name-problems-under-windows
It also shows up with the same name in Ableton for example, so maybe it's a bug in PortMIDI and Ableton is using that, or it's a bug in Windows.
In this case it's Windows 7. The devices does have different names in the Windows device manager. However, in all software we tried they are listed with the same name....
I had the same problem. What's not clear in the docs is that the resolution argument is actually "max value + 1", and not number of bits as I first...
Chiming in here too.. as the developer of AUM I'm a bit concerned about music apps ability to work good together :) C/C++ vs Swift in the audio thread is...
I just tried this here and it works fine!
Yes, I understand that host time and sample time does drift when compared to each other. The thing is that it drifts much more on some devices. On most devices...