MOTUnation.com

Try 4.51 and get off 4.52.

I have.

Must reload OS & 4.5 then update to 4.51. backup users and main library on HD front page to another drive first.

Rename the copied library 'old library' and 'old users' after.

Thanks again for the advice Gary. Don't think I have the 4.51 update, only 4.5 and 4.52. What do you find works better for you in 4.51 than 4.52?

I'm holding off doing anything much for a few days... because

a) I'm hoping to test my Mackie on someone else's setup, to convince myself that it's just my system that has the problem (not that I don't believe you guys, but...)

b) MOTU may well have a Tiger-related update in the works - which with luck will fix some stuff

A weekend of cleaning the apartment and making cables is what I need to take my mind off things! Everyone's help and suggestions are much appreciated, thanks. I'll let you know how it goes (the MOTU problem, not the apartment cleaning

P

When you are ready to use it let me know. Email me direcly and I'll get it to you.

Just an update:

New Tiger installation on a fresh volume, new DP4.52 installation, FW 1.2.5, MIDI 1.3.1 (all of which worked fine by the way on my Dual 2G). Nothing else installed.

The automation bug is still there, so my Mackie Control is still unusable. See the bug at http://www.lx3.co.uk/notsosecret

It happens with my Mackie Control, it also happens with my MC Expander (so I don't think it's the MC).

MIDI Express 128, 896 HD, G5 Dual 2GHz.

The problem doesn't happen in 4.12, and I can switch back to 4.12 under Panther and prove it to myself over and over.

This is very very very strange, and I honestly have no idea what the problem is (unless it's DP4.5 and I'm the only person who's spotted it... which seems unlikely).

I am up s*&t creek now. Dawn, expect a phone call!

Paul

I've been reading these posts for about 2 months, but this is my first post...

I've been having some problems with my Mackie Control since I've upgraded to 4.52. I just upgraded to Tiger, but I was having these same problems in 10.3 when i was running 4.52. My Mackie control would not have the following problem in 4.12

The problem that I'm having is when I switch apps between CueMix and DP (i do this all the time with keyboard shortcut "apple-Tab") I can't get DP to recognize my Mackie Control again. I asked Mackie and they thought I may try updating my firmware in the Control. I did (now my Mackie Control is v2.1.2) and I'm still having the problem. When I switch back from CueMix to DP, the faders don't jump back to where they should be in the DP mix, but if I move them, they will alter the DP mix. The way that i can get DP to recognize the Mackie Control correctly after using CueMix, is to go thru the "studio- Select Control Surface" command. When i choose Mackie Control, everything seems to work fine until i switch back to CueMix, then i have to do it all over again...

Anyone have any ideas about what may be happening???

The digital stuff in my rig is a Dual 2.0 G5, 828mkII (which i don't use for MIDI at all), Motu Express XT, Yamaha Motif 8, and Mackie Control.

thanks...

Hey there Todd. It's nice to be able to help someone else for a change

I don't generally use my MC to control CueMix. Maybe I should! But my needs from CueMix are very basic (FX returns for outboard, that's about all), so I don't need the faders flying around any more than necessary

Anyway, I hadn't noticed what you describe, so I started experimenting. Here's the deal:

* "Out of the box", when you install DP and CueMix, the Mackie does not control CueMix. Also, it seems "Enable Surface in background" in the Control Surface setup in DP is checked by default (I think). So when you switch to any other application, your MC stays right where it is - nothing moves. That suits me fine, so that's where I have left it until now.

* In CueMix, if you switch on "Control Surfaces->Mackie Control Surfaces->Enabled", CueMix will take over the Mackie when you switch to CueMix.

* However, as you rightly say, once CueMix gets hold of the Mackie, it tends not to let go. Again, I think that's the default behaviour, so I can see it could catch people out. To share the MC between CueMix and DP (so DP gets control back properly), switch on "Control Surfaces->Share surfaces with other applications" in CueMix. ALSO... it seems you MUST have "Listen to control surface in background" switched OFF in DP (under "Setup->Control Surface Setup").

* I also have "Application follows control surface" switched off in CueMix. I don't quite get the purpose of that option (but then I've only been playing with this CueMix business for the last ten minutes).

I think this should do it for you. Works good for me - 4.52, Tiger, etc, etc. Only pain is that it takes a few seconds for DP to re-initialise the Mackie when you switch to DP, which might slow you down a little.

Lastly, if you have an expander, do a "Configure..." under the Control Surfaces menu in CueMix, and read the help section. A lot like configuring control surface setup in DP.

Hope that fixes things for you. Have you encountered my particular bug?

Paul

I have the exact same problem (Creeping Automation Points) using DP 4.5 and MCU at v2.1.2 firmware. I posted this on another thread just a couple of days ago.

The only way I can solve it is to open the Event List, record my automation moves, and then manually delete out that last creeping bit of data. Everything is fine then. It's crap to have to do that, but it seems for now that is the only way.

I emailed MOTU about this on Wednesday, and the sound of the crickets chirping in the void of no response from them is now deafening.

Tiger (even if it fixed this) is not an option for me becuase UAD1 does not work in Tiger yet

Wonderful... Thanks Paul. I had done everything that you suggested except for the step in DP where you turn off "Listen to Control Surface in Background". Makes perfect sense, but i just never noticed that box for some reason...

"Application follows control surface" in CueMix is for if you choose the "Flip" button on your Mackie Control and switch to a different bus, the application will show that bus.

I'm not sure how you cannot be using CueMix often. I'm always working with live mics in my small studio, and i'm in CueMix all the time to pull mic faders down after I track to prevent feedback loops. I also monitor when tracking thru a MPX 550 (via SPDIF) so the singers can have a little bit of a wet mix without latency in the cans, so i'm often messing with the sends to the MPX. Does that make sense?

Anyway. Sorry to jump onto your post with something that was slightly off the subject, but i really appreciate you setting me straight on getting Mackie Control to work in CueMix and DP.

I haven't tried to recreate your problem, but i'll try it on Monday.

Hi again, glad it managed to fix your problem.

Re my use of CueMix - I don't record in DP, I'm primarily using it to mix in. My business is live recording of shows, which I do on an HD24XR, then Fireport the files to my G5 and mix in DP. So no serious input monitoring needs.

I setup sends and returns over AES-EBU (896HD) to a TC M3000, and use CueMix to monitor the return. It's great having latency-free monitoring of a digital input Eventually I print those FX to disk and bounce the whole result to stereo.

MOTU are now looking into my particular mix issue. Still not sure if it's just something peculiar to my system, or if everyone on DP4.5 has it. Is your "automation creep" the same thing as I'm experiencing? (see the movie on my website).

Cheers. P.

<small>[ May 29, 2005, 06:29 AM: Message edited by: Timeline ]</small>

you know, I had a fader control problem and I wound up creating an identical but new/clean MIDI setup in audio/MIDI set up.

Everything started working perfectly since then. Including touch fading.

Just a though, worth a try.

Has anyone had any solution to thi sproblem yet? I am also experiencing the same issues regarding the automation with an MCU.

Nope. I was told by MOTU that it's a Mackie Control problem. Well, that's pretty damn lame since it was not a problem in 4.12, but it no longer works in 4.5. Since nothing changed with Mackie Control, sounds to me like DP 4.5 broke it. I kind of gave up on getting MOTU to look into it. I just do my old trick of opening the event list and deleting that last automation point. Maybe 4.53 will fix it......along with putting a switch on Dynamic CPU Management.

Hi Paul,

Since we're grabbing at straws, a couple things that have helped me with MIDI issues in the past:

1. Is Preferences->MIDI Solo & Patch Thru->Use CoreMIDI Patch Thru enabled? If not, try enabling that.

2. Is Studio->Multirecord enabled? If not, try enabling it and specifically selecting your MIDI controller as Input to all MIDI channels.

I've got a MCU, so will try to reproduce your issues later today...

I also have issues where If I pull the fader down on the MCU I still hear the track. In other words I am not hearing what is being written.