Forum Replies Created
-
AuthorPosts
-
2017/06/14 at 4:27 pm #63893
Console will power on as soon the mains come back, the MIDI command does not actuate the physical switch, it just changes to the shutdown screen and locks the mixer.
2017/06/14 at 1:24 pm #63890Not sure if I’d suggest a 24/7 operation of the desk with lifetime in mind, particularly the backlit LCD. If you go for 24/7 operation I’d at least add a fan (underneath the desk) to reduce internal temperature and extend lifetime of components like capacitors within the power supply. Just as a precaution.
2017/06/13 at 6:46 pm #63875At least powering down the Mixer could be automated using the proper MIDI Sequence (see “Remote Shutdown” in Qu MIDI Protocol). All you need is a tiny tool which is started when the PC enters its shutdown sequence, connects to the Desk and sends the MIDI command. Could be done through network or USB. Sending a fixed data packet to a fixed IP address shouldn’t be too complicated to implement.
2017/06/13 at 5:59 pm #63870Don’t see a big issue with this, as long the Qu is not configured to require a user to login first.
Normally the Qu should to be powered down only after using the “shutdown” command, which places the desk into some frozen state to ensure there are no pending memory updates which may be lost. But if your desk is unattended anyway, there should be no pending changes which needs to be safed at all.
The physical power switch is in series to the mains power connector, so plugging power externally or using the switch effectively is the same.2017/06/11 at 10:04 pm #63829Guys, he’s talking about the Qu which is freezing, not the Mac. 😉
Did you try unconnecting the Qu from USB when this happens? Maybe sort of MIDI loop where the Qu receives back all its own MIDI messages from your DAW.2017/06/09 at 12:12 pm #63781@Leez: Didn’t see a Cruzer Fit ever gets recognized on my Qu, good luck. You may try a Transcend JetFlash 710 as a thumb drive. It least it seems to work for multitrack recordings on my Qu32 but didn’t do a long record yet.
@george: That’s really a strange one. I still wonder how the host port on the Qu is technically realized. If thats a separate controller which is not affected by firmware updates, the Qu16 and Qu32 could origin from different production series. But if the yellow led on the Qu does not even flash when attaching the drive, I’d guess the port itself is broken on that Qu32 for some reason.2017/06/08 at 11:13 am #63757No wedges and high pitch ring? Sounds like the PA is directly bleeding into the Mic(s). What kind of mics are you using? Tried supercardioids?
2017/05/25 at 4:19 pm #63574my gates are normally already open from backround, only closed when band is not playing. Effectively not working during music. Sure, downward expansion would be best.
2017/05/25 at 3:47 pm #63571Never worked with the AMM, but for my understanding it probably would be counter productive in such a chorus scenario, since the idea behind AMM is to emphasize the loudest channel (so the “current speaker” gets the priority). I’d go for regular compressor (plus gates) for the chorus.
2017/05/25 at 12:59 am #63560Of course running the Qu with a dynamic IP address should work, but assigning a fixed one just eliminates some potential problems and simplifies tracing down network issues.
One example would be some other TCP/IP host which tries to connect to the Qu but is not aware of auto-locating it by name, or if the Qu indeed is behind a router which does not pass name broadcasts. Then you need the IP and have to rely it does not change.
Lee’s connection issue when the iPad obviously roamed to the secondary (bridged) WAP could be traced down with simply connecting to the Qu using its IP address (“other”) instead on the name, which requires name broadcasts from the Qu reach the iPad through the WiFi bridge (which shouldn’t be a problem at all). For such a check it again would be helpful if the Qu has a fixed IP.
When I set up my systems I never think about what may be used in the future, I just set it up to support most scenarios without later reconfiguration. Assigning a fixed IP is a somewhat standard step I just do.2017/05/24 at 1:47 pm #63543At least for the router running the DHCP server a fixed IP address is more or less mandatory, right? And I also prefer to have a fixed IP address at the desk, so I know that one is always correct and does not change unexpectedly.
Particularly if you are powering the router along with the Desk and the router isn’t finished booting when the Qu requests an IP address, then you may end up with some auto generated IP address in the mixer, not necessarily matching the address range configured in your DHCP server.
I just prefer to reduce number of potential points of failure instead of crossing fingers each startup… 😉2017/05/23 at 3:44 pm #63531rechecked with my Airport Express, there is no checkbox for network extension (maybe it for a different firmware version/newer unit, don’t know).
Anyway, mine is set to DHCP only with several IP settings in the other dialogs.
First of all, since there is no WAN connection (to the internet), I set Airport to a fixed IP address. I’ve picked the 192.168.50.3 with subnet mask 255.255.255.0, router 192.168.50.1 and primary DNS server to 192.168.50.1 for some historical reasons (not relevant in this case).
For the DHCP settings I’ve choosed the area 192.168.50.70 to 192.168.50.90, where my WiFi clients will get their addresses from.
My Qu also is also assigned to a fixed IP address, maybe 192.168.50.2 (with subnet mask 255.255.255.0 and router 192.168.50.1) in this scenario.
However, I only have a single Airport express running, not sure if these hints will help in your scenario.2017/05/23 at 3:17 pm #63530Hmm, did you check this “Allow this network to be extended” checkbox as decribed in point 8 Setting up and configuring an extended wireless network?
Sounds like your iPad already picks the best WAP but the secondary WAP does not communicate with your main access point.
…strange message regarding your “WAN IP Address”, in that configuration you normally do not have anything on the WAN end…2017/05/23 at 2:46 am #63522Not sure if you really want to run NAT on your WAPs and hope you only activated one DHCP server and set the secondary airport to Bridge mode.
Boxes are not cable-connected, right? Did you follow the “official” documentation (https://support.apple.com/en-us/HT202056)?
Anyway, can’t see anything wrong on the screenshots.2017/05/22 at 9:49 pm #63519Ok, I’m picking my ME1 next days and do a trace. I’m pretty sure the Qu switches protocols depending on whichever unit-type is connected at its dSnake port. It either operates with dSnake or ME-1 protocol. Ever tried to connect AR2412+ME-1 using a switch to the dSnake ports? I did and only one will work, whichever is detected first from the Qu. Had the similar problem with needing more local inputs on my Qu-Pac and a spare AR84 but needed ME-1. No chance so far (plugging the AR84 to the expansion output of the ME-1 wasn’t an option, but I may try as well).
-
AuthorPosts