HUI PROBLEM!! need a fix before I sell my board

[tyler8wb]

Is there something im missing about the MCU's? DO they have a bad rep or something? Im just trying to shift my gear more towards logic and controlling logic. I am starting to build a preamp rig along side some interfaces for more integration into logic. Also since my interfaces go to 192 (i normally run at 96) I am getting better quality than running inputs through the D8b The D8b is a great piece but I don't think that DAW integration was exactly what they had in mind when they designed this piece. Marc's project interests me a lot but seeing as its being developed on windows and I'm 100% mac I don't see this coming to me to soon. I guess I just really need input. I was looking at the Mackie MCU's but also the Tascam us-2400 and if I do decide to go mainly pro tools (just got a copy of pro tools 9 last week ) then maybe a Digidesign Pro Control.... any advice?

[anyhorizon]

The old MCUs had fader issues. So did some of the newer ones until they ditched the Penny and Giles jobs and started installing Alps.

Peter

[Marc Girard]

Our d8b software will be cross-platform. It's being developed in Windows 7 x64 for the moment but ports are planned. 32bit and MacOS X versions. As we're still working on the core engine, we're concentrating on making it work, we'll deal with the rest later.

MG

[mackdaddie]

Try this in your BIOS settings

maybe it wil work to

This is indeed caused by wrong settings in the BIOS.

When your CMOS battery died, your BIOS settings reset themselves to default values.

One of those settings enables/disables the onboard USB controller, which, when enabled, uses IRQ10 - the same IRQ to which the d8b's MIDI card is configured to use from the factory.

This results in the d8b being able to send MIDI but being unable to receive it.

To resolve this issue, do the following:

1. Power down the mixer.

2. Power up the mixer and hit DEL when you see the BIOS screen to enter the BIOS (i.e., press DEL when you see the memory size and processor type on the screen).

3. Disable the onboard USB controller:

* If you have the older motherboard, disable the "Onboard USB Device" option under "INTEGRATED PERIPHERALS." Also disable "USB Keyboard Support" under "CHIPSET OPTIONS" (or equivalent category) and any other option related to USB.

* If you have the newer motherboard, disable the "Assign IRQ to USB" option under "INTEGRATED PERIPHERALS" and any other option related to USB.

4. Exit the BIOS and SAVE YOUR CHANGES.

Your d8b will now again be able to receive MIDI and your HUI mode will work properly.

[High C Double G]

Good call mackdaddie! You noticed he upgraded to a 900Mhz MB. That one totally slipped by me.

However, having a 900Mhz MB in a d8b CPU is like having a Formula one race car on a Los Angeles freeway during rush hour!!!

It can go faster, but it won't.

Michael

[tyler8wb]

My original processor was the 166Mhz and it made me a little nervous when the One moment please message came up like every minute. So I upgraded my processor to 900Mhz and added a stick of 256mb ram. All the messages disappeared and everything is good now. and mackdaddie I went into my bios settings and it didnt work.... also my normal midi map isnt receiving midi but my transport section is?? im confused now

[High C Double G]

Actually...

FYI: the d8b does not transmit MTC it only receives it. So your computer DAW needs to be set up to transmit MTC to the d8b. I am sure you have referred to the manual and appendix F in particular. As well the DataBase is huge full of info like… This…

taken from the d8b DataBase under sub section > Tips > labeled MIDI Mapping: Useful Info.
POST 2:
One thing to remember is that the d8b does not send out MTC (Midi Time Code). It only receives this in order to run its automation engine. What the d8b also sends and receives are midi and MMC commands. The d8b midi map function specifies how the d8b deals with these messages.
Also… there is also another cool offering from Anyhorizon at the bottom of the Tips page labeled MIDI communication – Troubleshooting.

What is going on is something probably quite simple. I know for myself that when you introduce a few pieces of gear to communicate with each other it really gets confusing (at least for me) and it is a lot of reading and trail and error, plug it this way that doesn’t work, write that down so not to repeat, try another way, write that way down as to not repeat, etc…

Hope this helps,

Michael

[High C Double G]

Just one more thing, actually two things, MMC is machine control (MIDI Machine Control) and that is transmitted by the d8b, so that is why your transport works, the Time Code is set to be received by the d8b only and needs to be sent by your computer DAW to the d8b. The manual and the database are your friends, and we are too of course!

Michael

[tyler8wb]

Sorry if I made this a little unclear. My TRansport section works and everything but my mapped out 24 channel strips only send midi and do not receive it. I have send and receive selected in the mapping menu on the d8b but when a new project loads or I grab a fader or something in logic, nothing happens on the d8b...

[anyhorizon]

You need to load your midimap whilst in the Startup session and then save the startup session so that the midimap always loads when you start something new. Anything created prior to that process means you'll always have to load the midimap separately. Once you save any changes in those earlier files, when you re-load, the midimap will be operative.

Peter