Midas

Hi Kaj @Dionysos,

Welcome to the forum. Before doing anything drastic like sending it back, have you tried plugging in your XR18 to the same power cord to make sure the cord, etc. is working? To be honest with you, I haven't opened up my MR18 (or XR18 for that matter) to see if there is a fuse inside. Both have been working flawlessly since I got them.

Hi Paul

Yes, I've tried that. I geues it's just bad luck.

It did, however, sound great the four days it was alive. I don't know if it was the better pre-amps, but it was really sweet, the fx came to life in a new way too. I will send it back - and hope to hear it again in 2019

Thanks for your input

If it's brand new, can't you just return it to where you bought it and get another one?  I'd expect that to be much quicker than trying to get it repaired under warranty. 

Ken

Hi @djn111 

Yes, the X-WSG works the same in M32C as it does with the other M32 / X32 console versions. 

Hi @Alphasounds,

The MR18 does not have AES input or output. Ultranet is a proprietary (Klark Teknik) one directional protocol that is designed to feed P16 and Ultranet capable speakers (eg. TurboSound iQ series). Also the M-Air (and X-Air) family of consoles were not designed for expansion. If you do need this, consider getting an X32 Rack and one of the AES capable stagebox (such as the DL16).

Thanks Paul. Sorry for the Spelling mistakes.

The X air + DL 32 is just too ugly ...

I muted the high mid out and use the subs, from aux 6 with another set of active tops with no DSP. The difference in latency is very little with a compressor plug in at the master.

GreetingThor.

Wish I had a Pro9 to then have your issue!..so...Just guessing here but the size of the drive usually matters, probably less than 32 gig will work. If it were me I would try 16 gig or 8. Some drives just won’t work no matter what. Try formatting it Fat32 that is usually the format used. Some 32gig or larger drives may work if you can format them using fat 32. My best guess!

Hi. If as Garyh says it has to be in FAT32.
And I ask you, do you already have any scenes or Upgrades inside the USB memory?
If you have to update the version. Create a folder with the name
DL3Upgrades and inside place the file as it was downloaded.
And insert the memory into the USB port with the blue LED on.
You may have already done this.
I hope it is useful.
I remain at your service
best regards
Carlos M Perrone

Thanks for the feedback,

i'll pass this on to the MIDAS team. I don't think there is a software/Plug-In version available.

For some free Spectrum analysers checks these: 

• Fre(a)koscope by [email protected] (Mac, Windows)


• FreqAnalyst by Blue Cat Audio (Mac, Windows)


• Inspector by RNDigital (Mac, Windows)


• MAnalyzer by MeldaProduction (Mac, Windows)


• MultiFreek Junior by U.F.O Scientific (Windows)


• MultiInspectorFree by VertexDSP (Mac, Windows)


• Oscarizor by Sugar Audio (Mac, Windows)


• Real Time Analyzer by reFuse Software (Mac)


• Sonogram SG-1 by ag-works (Windows)


• SPAN by Voxengo (Mac, Windows)


• Spectrum Analyzer by Seven Phases (Windows)

I can recommend Melda's Multi Analyser, which i bought last year:
https://www.meldaproduction.com/MMultiAnalyzer

Best regards,

Mike

Hi,

Not PRO Series, only ProX consoles.

It seems it needs CPU ans Neutron can provide it, not PRO1/2/2C.

---

@gtcode wrote:

Question: Will Scenario 2 work? We want to leave the M32 powered off, and be able to use the X32 Core AES50-A to the DL32 AES50-B.

---

No it will not work. The DL32 can only receive the wordclock from the AES50 A port. So if you turn off the M32 (with sync as internal - thus master clock), you will have to connect the X32 Core to the DL32 AES50 A port and turn on the sync (on X32 Core) to internal. Just remember that when you want scenario to switch it back (AES50 B and sync to AES50 A).

If you don't want to hassle with changing sync and ports, a better way to set this up would be:

M32 [B] <-> [A] X32 Core [B] <-> [A] DL32

Make the X32 Core master clock (sync = Internal) and M32 as slave (sync = AES50 B)

X32 Core Routing, AES50-a screen (DL32 inputs to M32)

* Outputs 1-8 -> AES50 B1-8

* Outputs 9-16 -> AES50 B9-16

* Outputs 17-24 -> AES50 B17-24

* Outputs 25-32 -> AES50 B25-32

X32 Core Routing, AES50-b screen (M32 outputs to DL32 outputs)

* Outputs 1-8 -> AES50 A1-8

* Outputs 9-16 -> AES50 A9-16

For scenario 2, if you want X32 Core outputs to go to the DL32, you will probably want to change the Routing, AES50-b screen to:

* Outputs 1-8 -> Out 1-8

* Outputs 9-16 -> Out 9-16

Thanks Paul.  Would the proposed second setup introduce additional latency to the M32 since the audio is ostensibly now passing through the X32 Core?

---

@gtcode wrote:

Would the proposed second setup introduce additional latency to the M32 since the audio is ostensibly now passing through the X32 Core?

---

If I remember correctly the AES50 latency is 0.9ms. So if you are traveling the speed of light, I guess that would be significant. 

I wonder exactly how they would add up.  Maybe it's 0.9ms per stage and side, so M32->X32Core->DL32->X32Core->M32 might introduce 4 * 0.9ms = 3.6ms round trip.

Well all I can say is that of all of the many users I've helped (over the 6+ years) with similar scenarios (console <> console <> stagebox <> stagebox), I've yet to hear from one that complained about latency issues.

No for either the X or M 32 I'm afraid. many of the FX that are in the left hand side are very processor intensive and the mixers don't have enough processing power to make all the effects work in all eight FX slots. You can only have the simpler FX in the right hand four slots.

Hi @NelsonVega 

Typically this is due to a corrupt firmware, likely it just downloaded incorrectly. Try downloading the update file again from the website and if you can connect to the internet via landline, even better. 

Re-format your USB drive (FAT or FAT32) and create a folder '  DL2Upgrades ' - then place the unzipped .tar file in the folder and try upgrading the console firmware again. 

Let me know if you have any other issues.

Hi @Edwinvansteenbe 

There is no cheap, easy way to get low-latency audio down the Ethernet cable. A remote computer on the stage end, or your main computer on stage controlled by an iPad is possible. I would think your idea is the easiest, simple solution.