MOTUnation.com

OK they did not fix the DP cpu hit read out, they claim that it should be ignored and only worry if the system really goes down to it's knees. It seems that they are right...

Can any body - on DP7 - comment on the cpu hit issue?

I can't comment on the CPU hit issue in DP7, but it seems to be much less frequent for me in 7.0.1. Now that also may have something to do with the fact that I disabled the Airport in my studio iMac and went straight ethernet to a router for the network and MC Mix. Prior I had Airport for network, Mc Mix in the ethernet port.

I haven't sniffed the ethernet streams but I notice that with my router, the activity leds for anything connected to the ports is pretty busy. So at this point I'm considering putting in an ethernet switch to cut down on the network traffic. This won't do anything if the Euphonix driver is using UDP packets instead of directly "talking" TCP to the MC Mix.

I've had a few emails back and forth with Euphonix and as a result I've canceled my MC Transport I had on order. My guess is that Euphonix might be the engineers who design the MC series, but I strongly suspect they have some outside firm developing the software for them. The excuses and slow updates seem to indicate this to me.

From a cold boot my MC Mix will work for most of the day in DP 7.0.1. But sooner or later, even if DP is no longer running, the Euphonix software will crash. At least it doesn't take down DP if it happens to be running.

I still LOVE the MC Mix, just don't like the company.

Mel

chaim wrote:Can any body - on DP7 - comment on the cpu hit issue?

The actual CPU reading for my machine is low with DP7 and Eucon. I don't bother looking at DP's CPU meter as I don't find it to be accurate compared to that of Activity Monitor and iStat.

DP7 appears to be working as well as 6.02 was with Eucon. That said, the 2.1 software update from Euphonix is overdue at this point and it needs to be a good one or they risk some defections. I'm happy with the MC Control but I don't expect it to be the heart of my workflow.

KEVORKIAN wrote:

chaim wrote:Can any body - on DP7 - comment on the cpu hit issue?

The actual CPU reading for my machine is low with DP7 and Eucon. I don't bother looking at DP's CPU meter as I don't find it to be accurate compared to that of Activity Monitor and iStat.

DP7 appears to be working as well as 6.02 was with Eucon. That said, the 2.1 software update from Euphonix is overdue at this point and it needs to be a good one or they risk some defections. I'm happy with the MC Control but I don't expect it to be the heart of my workflow.

I find Apples Activity monitor takes a big hit itself and I don't tend to use it much. I'm not sure if it's simply a GUI for the TOP command or more. But often I'll just use the terminal and TOP.

That iStat is a GOOD idea! I never thought of that one, worth a try. Thanks for the tip!

I still love my MC Mix and it is the focal point of my workflow. Without it, I'd have to resort to the mouse and that's not something I like to use. I'm using a Korg Nanopad and an FCB1010 for transport controllers now. Scrubbing and shuttle are the two functions I could use but through the use of markers I can still use what I have with some reasonable results.

The 2.1 update is long overdue but as you point it, it better be good.

Mel

wabbitguy wrote: ....I'm using a Korg Nanopad and an FCB1010 for transport controllers now. Scrubbing and shuttle are the two functions I could use but through the use of markers I can still use what I have with some reasonable results.

The 2.1 update is long overdue but as you point it, it better be good.

Mel

How are you using the FCB1010 with DP? I use one with Ableton Live using MIDI Translator, but I'd be curious as to how you do it. Thanks

KEVORKIAN wrote:How are you using the FCB1010 with DP? I use one with Ableton Live using MIDI Translator, but I'd be curious as to how you do it. Thanks

Hi,

I use the FCB1010 as basic transport control (rtz, stop, pause, play, rec), and then for prev/next marker, add marker, ff and rew (slow). I use all of those with the FCB1010's note ON/OFF cmds. I don't use the pc's or cc's for DP. I have one global MIDI channel for the note commands set in the FCB1010 and that's the one that DP listens to for it's MIDI commands.

The main drawback is programming the FCB1010, but I wrote my own software to help me do it. Makes it a lot easier than performing the "River Dance" on the floorboard to program it.

Mel

wabbitguy wrote:

KEVORKIAN wrote:How are you using the FCB1010 with DP? I use one with Ableton Live using MIDI Translator, but I'd be curious as to how you do it. Thanks

Hi,

I use the FCB1010 as basic transport control (rtz, stop, pause, play, rec), and then for prev/next marker, add marker, ff and rew (slow). I use all of those with the FCB1010's note ON/OFF cmds. I don't use the pc's or cc's for DP. I have one global MIDI channel for the note commands set in the FCB1010 and that's the one that DP listens to for it's MIDI commands.

The main drawback is programming the FCB1010, but I wrote my own software to help me do it. Makes it a lot easier than performing the "River Dance" on the floorboard to program it.

Mel

Thanks for that info... I'll have to set mine up to control DP. I don't do a ton of my composition in DP (I mostly arrange and mix) but there is no reason not to set it up.

I use this iFCB to set up the unit: http://www.wabbitwanch.com/iFCB.html but if I knew how to write something I'm sure that would be even better.

I just realized that iFCB is from wabbit wanch design... that can't be a coincidence right?...

KEVORKIAN wrote: I just realized that iFCB is from wabbit wanch design... that can't be a coincidence right?...

ROF LOL....guilty as charged...Wabbit Wanch Design and iFCB, yep, that's me.

My music site is wabbitwanch.net (best viewed with Geritol in hand)...

Mel

wabbitguy wrote:I can't comment on the CPU hit issue in DP7, but it seems to be much less frequent for me in 7.0.1. Now that also may have something to do with the fact that I disabled the Airport in my studio iMac and went straight ethernet to a router for the network and MC Mix. Prior I had Airport for network, Mc Mix in the ethernet port.

So you're connected to the internet and the MC Mix now over the same ethernet connection? I wonder if that slows it up too? What about just turning off Airport while actively using DP 7.01?

wabbitguy wrote:

KEVORKIAN wrote: I just realized that iFCB is from wabbit wanch design... that can't be a coincidence right?...

ROF LOL....guilty as charged...Wabbit Wanch Design and iFCB, yep, that's me.

My music site is wabbitwanch.net (best viewed with Geritol in hand)...

Mel

That's too funny! I took a look around the site and enjoyed the very authentic surf instrumentals and current studio shots. Thanks for sharing and thanks for writing iFCB! It's a very good editor for complicated footpedal. You do a good job keeping it updated as well and I appreciate that.

James Steele wrote:

wabbitguy wrote:I can't comment on the CPU hit issue in DP7, but it seems to be much less frequent for me in 7.0.1. Now that also may have something to do with the fact that I disabled the Airport in my studio iMac and went straight ethernet to a router for the network and MC Mix. Prior I had Airport for network, Mc Mix in the ethernet port.

So you're connected to the internet and the MC Mix now over the same ethernet connection? I wonder if that slows it up too? What about just turning off Airport while actively using DP 7.01?

The router isn't connected to the internet directly (I have multiple wireless systems in the studio and office here). My Airport on the studio iMac is disabled (turned off) so the iMac, MC Mix, and Cisco wireless bridge are connected to the router. It was the activity of the bridge in the office that set me off looking at "who" was yakking. Turns out its the Eucon software talking to the MC Mix (and it's chatty).

The router is just a spare that I pressed into service, Netgear rp614, and it's supposed to be a switched router. So tcp packets that go to the MC MIx are only supposed to only supposed to go there. What I see is the splattering of packets hitting the other office network (across the wireless bridge). Which is what made me suspect either the routing isn't accurately sending the TCP packets to the MC Mix and no where else OR, Eucon is sending out UDP packets as well. And I'm leaning towards UDP because the Eucon can share devices over a network and the easiest way to "find" a device is to send out a UDP packet and wait til someone answers. But I'd have to put a switch on the network or sniff it to be sure. I haven't had time to do that yet.

Even with all this, the ethernet seems to work better than the airport connection. With the airport active, I'd be mixing down 12 to 14 audio tracks (I mix out of the box) and there'd be a huge "hiccup" in playback, followed by the CPU pinning, distortion/clipping and a useless mix down session. I could retry it and sometimes it will work, sometimes it craps out in a different spot.

I use minimal plug ins, if any, an Apple EQ. All my compressors, EQ's and effects are rack gear so they are external.

Even if I just start up the iMac in the morning with the MC Mix and Eucon running and do nothing on it all day, by the end of the day I have a crash report about Eucon. Which I have forwarded to Euphonix each time. Only to be stonewalled with some truly lame excuses. But that's another story...

Mel

wabbitguy wrote: Even if I just start up the iMac in the morning with the MC Mix and Eucon running and do nothing on it all day, by the end of the day I have a crash report about Eucon. Which I have forwarded to Euphonix each time. Only to be stonewalled with some truly lame excuses. But that's another story...

Mel

That's bad... I have seen this behavior in the past. One thing I did was to set a DHCP reservation for my MC Control in my router/firewall, within the same IP range as that of my primary NIC. That seems to have settled things down a bit. It's could be possible that when your machine idles or sleeps (if you do that), that eucon loses track of it's IP (via it's crappy drivers, etc).

KEVORKIAN wrote:

wabbitguy wrote: Even if I just start up the iMac in the morning with the MC Mix and Eucon running and do nothing on it all day, by the end of the day I have a crash report about Eucon. Which I have forwarded to Euphonix each time. Only to be stonewalled with some truly lame excuses. But that's another story...

Mel

That's bad... I have seen this behavior in the past. One thing I did was to set a DHCP reservation for my MC Control in my router/firewall, within the same IP range as that of my primary NIC. That seems to have settled things down a bit. It's could be possible that when your machine idles or sleeps (if you do that), that eucon loses track of it's IP (via it's crappy drivers, etc).

mmmm....good thing to try. I'm going to change the IP in the MC Mix to static and remove the DHCP and see what happens. I don't let the system sleep. Ever. The screen dims and that's it. The CPU and drive are running all the time.

Mel