First, let me say that this is not a big issue and there are definitely workarounds, but I have noticed that QLC+ does not always recognize all of the MIDI ports that are available on OS X. For example, I was setting up MIDI on my Maschine MK2 controller last night and while the physical MIDI In/Out ports on the Maschine show up in QLC+, the virtual MIDI ports (those would be the ports that would actually send control data to and from the device) do not. In order to workaround this, I just used MIDI Pipe (or another app, doesn't really matter) to send MIDI to an IAC bus into QLC+ which works fine. It would be nice if QLC+ could natively recognize these ports. If not, the workaround is fine, it would just be nice if I didn't have to remember to launch another program to make my controller work in QLC+.
Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Honestly, I'm not entirely sure. I don't know if virtual port is being created by a driver for the Maschine or what. Like I said, it's not a big deal, just thought I would mention it in case it was a trivial fix. Also, if you like, I've attached an input profile for the Maschine.
George, I've had a look at the input profile (sorry for the delay !).
I see all the buttons have a "Button #" name.
Do they actually have a meaning in Maschine or are they generic buttons ?
I think it would be better if we can give them a meaningful name, so users can immediately recognize their functionality.
Thanks !
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Also, I know this is totally off topic, but I've noticed that the pulldown under the open icon (which lists recently opened files) displays recently opened files but will not actually open them on OS X.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi George, sorry but your last post got stuck on the SF approval system :S
The behaviour you have noticed is related to the switch to Qt5. I noticed that too...only on OSX.
You need to click two times. Once to open the popup, then release, then click on the recent file.
P.S. It might sound incredible but...I've got a Mac Mini now ! :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Heiko, I am probably the one misreading things, but your post sounds like QLC+ on OSX is not supported !
I think you didn't mean that, did you ? :)
If you meant my personal support for Apple products...well...forget it ! :)
I am not going to suggest anyone to pay 1000€ for a computer and then feel their hands tied to it, finding EVERYTHING non-free (starting from iOS apps)
I am not in favour for lobbies (which Apple created) but more for openness and sharing, even if this turns things slow in a short term, but powerful and almost perfect in a long term.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In fact, the OLA plugin doesn't compile on this new Mac ! lol
Seriously, most of graphical glitches that you see are cause of Qt, so probably they're the ones to blame in this case.
If QLC+ has bugs, then they're true cross-platform bugs ! :)
I hope to reduce this platform differences gap with the next generation QLC+.
We'll see...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
First, let me say that this is not a big issue and there are definitely workarounds, but I have noticed that QLC+ does not always recognize all of the MIDI ports that are available on OS X. For example, I was setting up MIDI on my Maschine MK2 controller last night and while the physical MIDI In/Out ports on the Maschine show up in QLC+, the virtual MIDI ports (those would be the ports that would actually send control data to and from the device) do not. In order to workaround this, I just used MIDI Pipe (or another app, doesn't really matter) to send MIDI to an IAC bus into QLC+ which works fine. It would be nice if QLC+ could natively recognize these ports. If not, the workaround is fine, it would just be nice if I didn't have to remember to launch another program to make my controller work in QLC+.
Thanks!
Hi George, I am no OSX expert but I'm wondering what is the difference between the devices.
QLC+ uses these API:
https://developer.apple.com/library/ios/documentation/CoreMidi/Reference/MIDIServices_Reference/
Massimo,
Honestly, I'm not entirely sure. I don't know if virtual port is being created by a driver for the Maschine or what. Like I said, it's not a big deal, just thought I would mention it in case it was a trivial fix. Also, if you like, I've attached an input profile for the Maschine.
George, I've had a look at the input profile (sorry for the delay !).
I see all the buttons have a "Button #" name.
Do they actually have a meaning in Maschine or are they generic buttons ?
I think it would be better if we can give them a meaningful name, so users can immediately recognize their functionality.
Thanks !
Also, I know this is totally off topic, but I've noticed that the pulldown under the open icon (which lists recently opened files) displays recently opened files but will not actually open them on OS X.
Hi George, sorry but your last post got stuck on the SF approval system :S
The behaviour you have noticed is related to the switch to Qt5. I noticed that too...only on OSX.
You need to click two times. Once to open the popup, then release, then click on the recent file.
P.S. It might sound incredible but...I've got a Mac Mini now ! :)
That gives me hope that you support OS X in future Massimo :)
Heiko, I am probably the one misreading things, but your post sounds like QLC+ on OSX is not supported !
I think you didn't mean that, did you ? :)
If you meant my personal support for Apple products...well...forget it ! :)
I am not going to suggest anyone to pay 1000€ for a computer and then feel their hands tied to it, finding EVERYTHING non-free (starting from iOS apps)
I am not in favour for lobbies (which Apple created) but more for openness and sharing, even if this turns things slow in a short term, but powerful and almost perfect in a long term.
No Massimo, i didn't mean that OS X is unsupported :)
But i know who horrible OS X is for a developer like you - who wan't to have a cross-platform-software like QLC+.
In fact, the OLA plugin doesn't compile on this new Mac ! lol
Seriously, most of graphical glitches that you see are cause of Qt, so probably they're the ones to blame in this case.
If QLC+ has bugs, then they're true cross-platform bugs ! :)
I hope to reduce this platform differences gap with the next generation QLC+.
We'll see...