Does the FireWire interface work with the current Mac OS?
Hi i need ipad monitor mix application for midas pro1. for musicians to make their own mix.
And I'd love to put the lock screen on the logo thanks.
To all, thanks for taking the time to look at this (especially @ChaseMcKnight ).
Our Pro2 running 3.4.6 Build 9 is having an issue with the first POP group button. Generally speaking it works fine. Sometimes the screen gets what I would describe as pixel trash on it. Almost like someone dropped a digital ink blot. Other times the text just freezes. It will respond to color change but not to text change. The button also never loses its ability to function. These anomalies can't be forced. They can be temporarily fixed by rebooting the console.
Any insight would be great. Especially if it doesn't involve desoldering and replacing. That has a place on two lists... things I can do and things I don't want to do unless I have to.
Thanks.
Hi guys,
so I have an m32c and building up a rack rig to use as a Monitor/FOH split rig. I still need to do more research but looking for opinions on what stagebox I need that will give me the most flexible options. I've been looking into the pro series stageboxes but the I/O s are confusing and it's a bit overwhelming with the options. Looking at maybe 2 DL 153s and a DL231? If I was running a Pro 1 with the m32c? Is that enough channels? Or would I need something different?
@Daanderson You would need to confirm the Pro level "blue" stagebox versions you choose can operate at 48K. Many do but not all as I recall. The DL32 and DL16 boxes would be better with the M32C imo if you want to stay Midas and Midas Pro level mic pre's. They are more or less meant for each other. You can also daisy chain via aes50 with them. With a 'Blue' pro level stagebox, even though they have the extra aes50 ports you can't. The ports are there for redundancy, should one fail the other keeps on going (which won't apply with the M32C anyway) So if you have one Blue stagebox that works at 48k on aes50a, that's it for that port regardless of ch count. Yes you still can use aes50b if need be but daisy chaining can be an issue with those boxes and of that you should be aware.
Also any of the Behringer versions will work with the M32C. The SD8/16 or the S16/S32. If you are primarily using this at shows as opposed to a studio setup, I would suggest using multiple small boxes like 2 DL16's instead of 1 DL32. Or 2 DL16's and one or 2 SD8's. This allows the stageboxes to be placed on the stage more aligned with what plugs in there. An Sd8 for drums or keys, DL16 for stage L and R etc. Just my opinion.
How you get any of these to the FOH is another whole story to consider. Some plan to split the ch's so the FOH can be independent of your monitor rig needs consideration. One case for the DL32/S32 as a stagebox is the way it operates (unlike other stageboxes). It allows 2 mixers to access the full 32 mic pre's via its aes50A and B ports. So any venue that had an M32 X32 or WING at FOH you could forget bringing any other splitter devices.
Hi @Daanderson
As @GaryHiggins pointed out - the "Blue" stage boxes, i.e. DL15x, DL25x, DL231 are able to operate at 48kHz but you're limited on the amount of devices you can connect as these units cannot daisy-chain like the DL16 + DL32.
You mentioned interest in the DL231. This would be a great option, especially if you're using a Pro1. Because it features asynchronous clocking, you'd be able connect the Pro1 (96kHz) to one side of the DL231 and the M32C (48kHz) to the other. If you went with DL153, for example, you'd also need to integrate a DN9650 w/ KT-AES50 card for the two consoles to communicate digitally.
I think I'm missing something key here, and I'm hoping one of y'all will pull me out of the rhubarb.
I understand the utility for post-eq (pre-fader) mix bus for, like, a monitor send.
And I understand the utility of post-fader mix bus for sending to an effect.
But, what's the difference between a post-fader mix bus and a sub-group? Why would you use a sub-group instead of a post-fader mix bus?
The reason I ask is that I need to dynamically process a signal coming in on an Auxin. I plan to route that Auxin to a mix bus, and use the dynamics there. But... should I use a sub-group? Why?
Thx in advance for your sage and reasoned responses.
Dwayne A
Hi Dwayne ( @DwayneAasberg) ,
I don't know if I'd call @Paul_Vannatto or @Roblof "sage or reasoned" but here you go:
https://community.musictribe.com/t5/Mixing/Mixbus-Post-Fader-vs-Subgroup/td-p/108259
Ken
Think of a subgroup as a post-fader send with the send level locked at unity.
On older analogue consoles, with the send level essentially locked at unity, it's one less gain stage (potentiometer on an analogue console) that the signal would have to go through. Instead of a variable send it was simply an assign\unassign switch. Less complex circuitry = cleaner signal. Not so much of an issue on a digital console.
The question then becomes (at least for digital consoles,) why would you want the send level to be locked at unity, rather than have it variable? Basically because it's simpler to work with. It also depends on what the subgroup is actually for. With things like FX sends, you might want the send levels variable to help you control the dry:wet of individual channels in the main mix vs how much FX they get. OTOH, you benefit from a send locked at unity if there are things like thresholds to worry about with parallel processing and you don't want things getting out of whack.
The other thing is that with stereo subgroups, the ch>subgroup pan follows the ch>LR pan, maintaining the stereo image, whereas if you have a stereo post fade send, you can set a different ch>bus pan than what the ch>LR pan is.
For your use case I'd use a subgroup because it's simpler (or I'd get a spare channel with full processing and set that channel's source as aux1.)
@KenMitchell wrote:
I don't know if I'd call @Paul_Vannatto or @Roblof "sage or reasoned"
I'm wondering, since sage is a spice, the OP meant to say "sage or seasoned"
https://community.musictribe.com/t5/Mixing/Mixbus-Post-Fader-vs-Subgroup/td-p/108259
Oh my! Back then (2013) I was still trying to figure this "darn thing" (X32) out (just like I'm now doing with the Wing). @DwayneAasberg I would suggest you understand @CraigFowler 's explanation.
I am in the Post fader Mix Bus send camp. I actually find it easier to select the Mix Bus that you want the channels assigned to and select sends on faders and bring up to Nominal the channels you want to send to that Mix Bus. Having to use the Mute as the on /off I have found confusing at times. It is referred to as variable sub groups by most people that use this method. I also like that this method gives me the ability to vary how much I send of each channel to that Mix Bus.
But one of the things that is so nice with digital consoles is there are different ways to do things so you can do it the way you like it. You have options.
This is originally from another post but I started a new one because I am wondering if other M32 owners have a similar experience with firmware 4.01. Specific to me, this is an M32R. Anyone else tried this yet and had a similar experience?
The back story is with version 4.0 the fader speed on M32's was reduced/smoothed out, it was (and apparantly still is) a permanent change. With this newer firmware 4.01 there is a "fast fader" checkbox that reboots the mixer and was intended to return the faders back to the 'fast' version.
Well there seems to be a BIG bug or something with the new M32 fader speed! I loaded up 4.01 and went right to the config page/fast fader checkbox area to see if I could get my mixer fader speed back the way it was prior to updating to V4. I confirmed I wanted that 'fast fader' option and....it reboots....and it did change BUT It is WAY different than before. Now the faders "snap" in to place (kind of like it used to) but there is this very worrisome fader motor "after spin" sound (more than just sound) that occurs. (a digital mixer's version of grinding gears) I can tell you 100% this never existed before. I went right back to the (since 4.0) slower fader version and that sound (and whatever process this was) went away! Not ready for prime time I think!
I am tempted to try it once more to see if maybe it was just a quirky firmware update and I may do so later in the day.
EDIT: I just tried the fast fader reboot again with the same results. I am told this is normal and expected however it's a normal I can't live with. I will again say that noise was never there for me before this. I can live with the slower version so there it will stay.
I will be setting up a system this afternoon for an event this weekend and we will be using one of the M32s (still on V3.07 of the firmware) for this. I will try and pay attention to the fader behavior and report back later today.
@KevinMaxwell Well, I finally located firmware version 3.07 myself and when I loaded it up, my nice, snappy and essentially noise free faders returned!! Yippy! NOW the question is if I reload 4.01 from here if it will return them to this fast version when I do so. At least I know how to get them back to what was my normal now. 3.08 did not, 3.11 did not. And I now know I am not crazy (well sort of know) I wil also report back.
EDIT: Loading 4.01 again puts the faders at the slower, smoother speed and the fast fader option makes them fast again but with losts of extraneous "after" noise NOT like version 3.07 at all. I made some short videos of all 3 and when I figure HOW to post them, I will.
I listened very carefully and on the M32 I was setting up (that has V3.07 on it) there was no weird noises like you were experiencing with the console running 4.01 and the faders set to fast. I agree with you that it sounds like there is a bug in the 4.01 fast fader firmware.
@KevinMaxwell Thanks Kevin, my experience exactly. I can't seem to upload my little videos so I'm trying to post them via dropbox link instead. These show the differences quite clearly (though video is NOT my thing). Hope they will be up soon.
@KevinMaxwell or anyone else interested: Video 3 is the "new" fast fader version Again the news for anyone wanting the faders back the way they used to be prior to firmware 4.0 or 4.01 Load version 3.7 (it's still availble if you choose to include the archived version in search on the Midas page) In my case it brought back the fader speed to what it was the day I bought it. BUT 4.01 puts them right back to slow or (noisy) fast. I am choosing to use the slower faders and stay on 4.01 due to its awsomeness in other areas and until such time as the old fast and noisefree version returns. And.....just like the recent US Congressional hearings, The gentleman recognizes himself as to the solution
https://www.dropbox.com/sh/5ru6bwfno5fcg5k/AAA9ugBcV-Se8L7YtteR35uYa?dl=0
EDIT2: I re-loaded firmware 3.7 to see what fader version it is that runs across the bottom of the screen-it appears to be fader version r/R .12 or r/R 1.2
EDIT: As an aside I noticed in this process of loading different firmware versions that if you use the console global setup page (bottom left) for updating firmware, you can have several firmware files at the root directory at once, and pick which one to load. I always made sure there was only 1 in the past as that was the specifried way to do it. FWIW
Hello all,
As you know the M32C has 2 1/4 out on the back labled "monitoring outoput" I would like to send a paif of mix buses out to these physical outs.
I'm having trouble understand if that is possible. Please help if you can.
@shadwell wrote:
Hello all,
As you know the M32C has 2 1/4 out on the back labled "monitoring outoput" I would like to send a paif of mix buses out to these physical outs.
Solo the desired mixbus master strip
PAUL thank you!
Im sorry, Paul you are correct in that by soloing the mix bus it in fact passes to the monitoring out.
I just simply want to route the output of mix bus 1&2 to the monitoring out with no use of solos. It's for an IEM mix. The other IEM mixes would come off the stage box.
For the the life of me , i find this box hard to use and I must say I am starting to think I might have purchased the wrong item. I hope with some elbow grease I can turn this feeling around.
There's monitoring and there's monitoring. There are the console's 16 buses you'd use for monitoring (eg for wedges or IEMs,) then there's the console's stereo solo bus you'd use for solo-ing a particular channel in your headphones\nearfield monitors.
The dedicated "monitor" sockets on the rear of the console are tied to the console's solo bus. They'll only ever output whatever's in the console's solo bus, unless nothing is soloed, in which case they'll output whatever is set in Monitor>Monitor Source option of the console.
The other XLR\TRS sockets on the rear of the console can have any bus routed to them (including the solo bus.)
What you cannot do is route a (non-solo) bus to the dedicated monitor sockets (at least not without sacrificing the console's solo functionality.)
If you let us know what console and stageboxes you've got, as well as which signals you'd like to appear on which outputs, we can probably figure out how to route it for you.
@CraigFowler thanks very much for your patient response. Ill get back to you with some thing more after some rest, its been a good long 12hr day and im more that a little fried.
im really hoping I can feel good about this purchase, but right now im feeling really bummed out.
best, A
Anyone experienced this before? After touching some of the knobs on the Pro2, the values will randomly change as if it thinks someone is turning the knob. Happens on the gain, eq, compressor and gate. Only seems to happen after you touch one of the knobs, if you never touch the knobs and use the trackball it doesn't seem to happen. Any thoughts?
Yes, was warned about it by a sound company that owns a number of PRO consoles. Suggest to contact Midas and send them Log Files.
Ishai
We call that "ghosting". This likely means the physical encoders will need replacing. Please fill out the support form and get in touch with our service team and they can assist.
I had this issue on some encoders of my Pro-1 (espacially on eq-encoders)
the Midas-SAV replaced the whole encoder card/pannel without any costs (under waranty)
now, all is fine !!
Thanks to @RexBeckett, I now have my 12 input signals Post-routed to Ableton using the P16 Outs.
Now, I would like to reverse this and route back the recorded tracks to different inputs on the M32.
**It would be really handy if I could use the DCA/BUS/MATRIX faders section as inputs for the Ableton tracks.
Hi Manos
I suggest you use the Routing PLAY/REC function on the Routing Input screen :
- Set your regular input banks depending on what you want to record when you're in REC mode
- Now turn 6th encoder to select PLAY and push
- You now have a 2nd set of input routing where all the sources are replaced by the output from Ableton
(by default the PLAY routing is set to Cards)
DCA are not really channels
BUS and MATRIX cannot be reassigned to get card returns
So you have to use regular channels / aux to get audio back from Ableton.
I suggest you watch a couple tutorial videos about the Routing capabilities of the M/X32 series
Hope this helped
Best regards
Hi Manos, the last time I saw your scene, you were only using channels 1-12 & 31/32. You could route your twelve playback tracks to, say, channels 17-28 so they would be available by switching layers rather than using the Record/Play routing switch.
Using the shiny new User In routing:
Can anyone tell me the AES50 Connection mapping for 96k operation for the DL252