The MBP-Apogee Ensemble dance.

[onion]

man, that sux! did you talk to apogee tech support? what did they say?

using an ensemble with an imac here. i don't experience any of those problems. i'm not at all aware of the boot order; in fact i usually only shutdown/restart my machine when i install new software or leave my apartment for more than a couple days. maybe you have a flaky firewire port or cable. try switching out the cable.

is your ensemble firmware up to date?

[chazwood]

Yes, the firmware is up to date.
Support says, "Hmmm, that's weird"..... "try this..... try that....... should be OK" .........

guess what.

If I start the apogee last, forget it. It will actually lose connection after a pop. Start it first and then reboot the MBP and it may be OK, but then half the time, it won't.
I thought it was just me.
I will try the fire-wire cable.

[jeffsjeffsjeffs]

I just started using an Ensemble with my new Macbook Pro 17" Unibody, and am having similar issues. It's not a buffer problem as I get dropouts and clicks even when listening to iTunes. This is a real drag coming from my MOTU 828 MkII which was solid as a rock when it came to drivers and using on several computers. Really thought I'd be able to load up, plug in, and use without problems considering the price of the Ensemble.

I called tech support and they mentioned things like turning off Airport, external USB drives, etc... what is that? I haven't had this issue with other interfaces.

Anyway, all firmware is up to date, I've tried different cables and booting in different orders, really don't know what else to do other than sell this unit. I would never trust it for a recording with the kind of glitches I've had so far. I'm sure not everyone experiences these problems, but I'm on a brand new laptop, even with default settings there shouldn't be a problem such as clicks and dropouts.

Anyone else made any headway to solving this kind of problem?

[che_guitarra]

Pops and clicks generally mean some sort of clocking error. Can you deselect/reselect your clock source at all?

[lean]

I've got a Mid-2007 aluminum iMac and I'm having a similar problem.

My Ensemble works perfectly IF I have just recently booted the computer and then I power on the Ensemble (or take it out of standby, to be more exact) The status LED will turn blue and all is OK. I can use the Ensemble for as long as I want without problems.

However, if I turn off the Ensemble and wait for a little while, or just boot the computer without using the Ensemble, what will eventually happen is something goes weird with the FireWire on the computer and my kernel.log fills up with the following message, maybe about five per second appear in the logs:

iMac kernel[0]: AppleFWOHCI_AsyncReceive::waitForDMA - context not going inactive.

This seems to be related to having the Ensemble attached to the computer but in standby mode. I don't think it's necessarily even specifically a problem with the Ensemble, but perhaps with some or all FireWire devices or chipsets... I haven't had the time or interest to do more extensive testing with other devices.

After that happens, powering up the Ensemble only results in the green status LED going on, which means that no FireWire connection is present. Rebooting fixes this.

It appears to be a bug with Apple's FireWire drivers. I say this because my Ensemble used to work perfectly until I hit a certain revision of Leopard. I'm not exactly sure where it went wrong, it certainly didn't work with 10.5.7 or 10.5.8, but I recently reinstalled 10.5 from the original Leopard CD and it worked correctly. Don't want to stick with running an older revision and plus Logic 9 requires versions that have this bug. Snow Leopard seems to be broken too, unfortunately. Nothing is wrong with my hardware, I've run hardware tests and had it looked at by Apple.

Oh and another thing is one the kernel.log messages start coming, if I put the computer to sleep, it will not wake up. So basically having the Ensemble attached to my Mac destroys sleep functionality. Really annoying. I basically have to reboot every time I want to start doing some audio stuff. It's like being back in 1997.

Reported this problem to Apogee last week but haven't heard back yet. Also reported to Apple as bug #7200285.

I've found a lot of people online with similar problems. Here's a thread that has some more detail: Apple - Support - Discussions - iMac not waking up from sleep mode ...

[jeffsjeffsjeffs]

Originally Posted by che_guitarra

Pops and clicks generally mean some sort of clocking error. Can you deselect/reselect your clock source at all?

No because this is happening even when I am just listening to iTunes, the SRC Rate in Mastro is gray and set to 44.1kHz. I'd like to solve this seemingly simpler issue before I even get into working with a DAW and clocking...

I've been searching google and seeing whispers that it could be some issue with newer MacBook Pro's and the firewire port, something about a Texas Instrument chip that has been affecting RME Fireface performance as well? Also a lot about what order to boot up Ensemble...

As I write this I was having a good 10 minutes with no issue (listening to the new POLVO record ) and then BAM the Ensemble completely lost connection and dropped out all the way.. ??

Have tried various cable connections, combinations and some with better performance than others but always this occasional dropout.

Just wondering if it is really a compatibility with my computer and the Ensemble. Seems odd, but I've learned that this kind of thing does happen.

[jeffsjeffsjeffs]

I'm attaching my setup in signature... although these problems are coming with the simplified connection of Ensemble to MacBook Pro.

Also, has anyone had issues with the quality of Firewire cables? I'm sure like anything there are duds, but I have noticed some dropouts are less frequent with some cables over others, this could just be due to the restarting of the Ensemble and less to do with cable. Can anyone recommend their most reliable FW 400 to 800 cable? I'd like to go ahead and get a better one anyway.

Really makes me appreciate MOTU, really NEVER had a problem with the drivers, OS updates, and upgrading my computer 3 times in the last 4 years (the most recent due to theft :( )... only problem is it sounds like a MOTU , and I'm ready to upgrade.

Ensemble sounds great by the way, even just monitoring familiar recordings... if it wasn't for this dropout issue...

[dougb415]

Originally Posted by chazwood

This is what I do.....
I turn on the Apogee first.
I reboot the MBP. (if I do it the other way around the apogee pops, clicks and drops out)
I open a saved concert that worked fine a few days ago and sometimes if I hold my mouth just right everything works.
If not, the blue light on the apogee is on but I get no communication between the MBP and it.

Do you have the latest software and firmware?

Here's what I do:

Boot the iMac, wait until the login screen.

Turn on the Ensemble. If the light goes blue, cool. If the light is green, turn the Ensemble off, then turn it on again. If the light is red, login and usually it turns blue within a few seconds.

It works A-OK after that.

[jeffsjeffsjeffs]

Well, it seems my problem has been solved!

Installed the new Apogee Snow Leopard update released last week (although I'm not in Snow Leopard, it says it is recommended for all users) which apparently includes a firewire driver update and all seems to be working fine.

Odd thing though, after installing the new Apogee driver when I then went to use my MOTU 828 as an interface, it no longer was recognized! So I then reinstalled the MOTU driver released in July 09 and got my MOTU running OK.

Back to the Apogee and still ok.. now both units seem capable of being interfaces on the same machine without conflict...

For the time being atleast I am a happy camper!

[derdomme]

Hi Guys,
my experience with apogee ensemble and the new macbook pro`s:
They doesn`t work together. I´m now in contact for two and a half month with apogee and they are not able to resolve my problem!!! Apogee Service really sucks!!!! I have digital drop outs while playing songs in Itunes, but this appears only with the newest macbook pro´s (unibody), the older ones are working fine. They told me, that the unit has to be repaired!! Complete bullshit, I know, that they really have problems with "older" Ensembles working togehter with the new macbook pro´s. There is no solution for these dropouts!!!!!!!!!!!!!!!!
i´m a professionell user and they don`t help me for more than 10 weeks!!!! Great Support!!!

[MatzeMillion]

I have issues with 2 Apogee Ensembles on a MacPro (early 2008), too.

I use them as an aggregated device and get audio dropouts and crackling very often. Most of the time I can get rid of it if I switch the clock from internal to wordclock and then back to internal. That seems to reset the audio engine (see kernel log). I tried different combinations of syncing (wordclock, adat, both master), different cables and a dedicated firewire card. but I had no luck getting rid of the issues.

Booting without the ensembles switched on is a no go. If I power them up later the hole audio system freaks out.

I really love the sound of these suckers but wish the drivers were programmed by rme...

[Dreamsilent]

Originally Posted by MatzeMillion

I have issues with 2 Apogee Ensembles on a MacPro (early 2008), too.

I use them as an aggregated device and get audio dropouts and crackling very often. Most of the time I can get rid of it if I switch the clock from internal to wordclock and then back to internal. That seems to reset the audio engine (see kernel log). I tried different combinations of syncing (wordclock, adat, both master), different cables and a dedicated firewire card. but I had no luck getting rid of the issues.

Booting without the ensembles switched on is a no go. If I power them up later the hole audio system freaks out.

I really love the sound of these suckers but wish the drivers were programmed by rme...

Might the problem lie in the aggregation? Just a suggestion.

Why not run one into the other via ADAT? Or is there a need to have them Aggregated?

[jweisbin]

These interfaces are plagued with problems as you can see from an internet search, and I have seen in my personal experience (tech for 15+ composers).

I used to have a lot of respect for Apogee as a company, but no longer.

[gussyg2007]

I've had one for years... and it never ever gives me any problems ,it's been the most solid consistent piece of HW I've ever owned !!!

[Doc Mixwell]

Originally Posted by Dreamsilent

Might the problem lie in the aggregation? Just a suggestion.

Why not run one into the other via ADAT? Or is there a need to have them Aggregated?

All you'll find with the aggregate is aggravation!!! its plain hack shop swill...I wont touch it anymore, and i have an eight core!!!

You wanna run the second Ensemble over the Optical port of the first!!! Forget the aggregate unless you want to chew on some Tylenol like its pop rocks

[NBarnes21]

What OS are you running? There's been really spotty use with apogee stuff and Lion, I had a horrible experience with my Duet 1 after I upgraded to Lion and ended up buying an RME Babyface. It has to do with some sort of issue with the computer recognizing external audio equipment connected

[Mr. Landmark]

I've been using an Ensemble with a PowerMac G5 and six different MacBook Pros over the last four years or so with very little trouble. Did some firmware experimenting in the beginning but it's been running rock solid with Mac OS X Leopard, Snow Leopard and since 2011 with Lion. And I'm always running the latest gen. MacBook Pro with the latest OS.

The Ensemble works fine regardless of me turning it on before I turn on or wake my Mac from sleep.

I did have som issues with external clocking but that was quickly solved by Apogee support and firmware updater 1.9.29.

What firmware version are your Ensemble running?

[vido]

Same here, problems with ensemble and a macbook pro (late 2011). I recently stepped up from a duet and have been pretty disappointed with the ensemble so far. Clicks and pops mostly, also during itunes, youtube, and especially netflix. Got help from apogee support, was supposed to update the firmware but that resulted in more trouble including the ensemble not being recognized by the laptop. Now I've got it recognized but clicks and pops are still there. Strange thin is that it seems to work ok for a while, and then it starts making trouble.

I'm especially disappointed since this thread is quite old, and apogee/apple still haven't figured out a good solution to this.

[Dyami]

Alas, December and I am in contact with Apogee as well with no solution. Ensemble worked fine no problems with old macbook and mac pro tower. New MBP retina and all the clicks/pops dropouts previously mentioned regardless of what firmware/maestro/drivers installed, as well as recognition problems, volume controls within OS X.

[TreyC]

OK. I wanted to give you guys a little hope regarding the Ensemble and MBP. I have a 13" unibody with the troublesome Lucent firewire chip (hold apple key and S on startup and the menu will tell you if you have the TI or the Lucent). I had a horrible time with Lion and Ensemble. Last night I upgraded to Mountain Lion 10.8.3. and reinstalled the latest ensemble/firmware/Maestro2 pack from the apogee website. It works....but you gotta know the dance.

First make sure ML is not set to reopen programs on startup. Then, turn the Ensemble ON with the computer OFF. Give it 15 seconds to do it's dance. Then cold boot the computer. After ML is up and running then you can open Maestro2. If the knobs on the Ensemble activate the Headphone and mic icons that float on the screen and you have active meters in the Maestro2 input meters you're good to go. If you DON'T have that you are not synced up even if you get some sound in your DAW. Eventually it will crackle and pop and give up.

I tried lots of combinations and this is the only one that seems to work every time. I've been able to do lengthy 8 channel at a time sessions with no pops or garbage at all at 24 bit, 48K, 128 samples (Studio One2). I use the Maestro2 mixer for no latency monitoring and mute the Maestro2 mixer channels for playback (which is stupid but Apogee doesn't seem to mind). I've got an active powered repeater cable (kind of a 1 hub extension cable) and a Belkin usb/firewire hub on order as these things seem to be solutions for others. If I didn't love the sound I would have given up on it....Hey, Apogee did!

Good luck and let us know how it goes.
T