[ZueriParticipant]

I would also like to see improved support for Windows. A&H should just do the same as on Mac, write a small DAW Control application with support of Mackie Control and HUI.

In Windows the ASIO driver is not working if you don’t turn on PC and QU in correct order (which remembers me of Windows 9x days and older hardware), MIDI is not really supported (or at least not as comfortable as on Mac). Even if Mac is used more often for DAW, there are plenty of Windows users out here. So please A&H, invest some money and make us Windows users happy (as you just did for Android 😉

[ZueriParticipant]

I’m using the following switch without any problem: https://www.edimax.com/edimax/merchandise/merchandise_detail/data/edimax/global/smb_switches_poe/gs-1008p

It is limited regarding features (unmanaged, Layer 2 only) but therefor in my opinion better for an ME-1 system (less features cause less problems).

[ZueriParticipant]

@Dhak: do you have a midi template for qu-24 and reaper? I tried to set it up as DAW in Windows but couldn’t get the faders move or control reaper. I’m new to this midi stuff and have no idea how to start.

[ZueriParticipant]

+1 for Names, both overall & channel.

[ZueriParticipant]

Sounds amazing. Let’s see if I can make it to Frankfurt. But good news anyway.

[ZueriParticipant]

+1
I am also waiting for this.

[ZueriParticipant]

Thanks xapbob. That’s exactly my point. Anyways. I’m not going to go with flame wars for iOS or Android. Boths systems are ok and have their users.

It is not a must requirement and I would never buy a console based on the criteria if it provides Andorid support or not. There are many factors which are far more important than app support. But if it has support for the OS I’m using it is an additional argument to buy it. That’s why I asked to implement QU-You Android by myself because my band members would like to have it (it is a cool feature).

@Pfr: I cannot confirm your experience. Many of our customers do their Android apps first and afterwards iOS because the market for Android is much bigger. Depends maybe on the app and the region, check https://goo.gl/vlLkDF to see a nice overview. Also we never had such issues as you are telling. If you have a good technical base you don’t care if your apps run on 10 or 100 or 1000 different Android devices because they just run. This if you don’t need all the fancy stuff you can do in Android or need to support Android 2.x but that’s the same for older iOS versions. And the costs are not really 50:50 it’s more like 70% for the first OS and 30% for the other.

Anyways. There is no spec and therefore no app made by myself.

[ZueriParticipant]

Thank you Nicola for your answer. Even if this means that I cannot start the project. Maybe we get A&H Android Apps with the next firmware version. Would be a nice surprise 😉

[ZueriParticipant]

This would be bad news for my plan. Let’s see if we can get an offical statement of A&H.

[ZueriParticipant]

Maybe I could find an iDevice user. But I prefer doing engineering work to reverse-engineering. Means if there is no documentation I will just not start working on this and spend my limited spare time with trying to figure out how qu-you works by analyzing network traffic.

[ZueriParticipant]

An updated MIDI protocol document would be perfect. To get a netowrk dump I would need an iPhone which is not the case 🙁 All our band members use Android phones (as the majority of smartphone users do). That’s why I wanted to have a look at the protocol to see if I can do something by myself until A&H decides to support the major mobile platform as many forum members here are requesting (if this is ever the case).

[Author]

Posts