I updated to Snow Leopard (10.6.8 ) yesterday and now for some reason my Apogee Duet sound card keeps disappearing and randomly disconnecting.

I bought a new iMac yesterday. It's a refurb 27' with i7 3.4 and 2GB Video RAM. It came with Lion so I decided to be brave and start working on it (after transferring my MBP data. Logic 9.1.5 seems to work ok. However I`m finding little bugs. It can pay to start a list. First one is a KC one.

At some point my 'Next EXS instrument' KC starts to work backwards. It goes to the previous one.

Teori Kepribadian Mulia Pdf Merge. ATM only happens when I have the EXS editor open and have clicked on a region. Not BIG but it's disturbing me.

Distinguished Member acmusic makes a very good point here: Interfaces like a Duet or an Ensemble are designed as hardware/software systems. This means that however stellar the hardware (and its embedded firmware) may be and remain over the years, the system can break, lose functionality, or be otherwise degraded through the software hosted by the connected computer/tablet. (Conversely, it can be improved at the software end: great companies try to do that as long as it is economically sensible; the same goes for firmware.) What I was ranting about naively, after imagining bugs, was actually a degrading of the Duet FireWire system through what I will tentatively, and I hope not too unfairly, term 'substandard programming and documenting at the user interface level.' There is no reason for me to chase deeper issues under the hood. If I chose to use outdated hardware I still have lying around, I could downgrade my system to the original Maestro under Snow Leopard on a 2006 Intel Mac. There is however a significant cost to segregating audio work to a separate vintage system.

Especially when space is tight, power management restricted, access to modern, multimedia-heavy Web 2.0 services increasingly desirable, etc. Living Books: ABC By Dr. Seuss. What acmusic describes, if I understand correctly, is a degrading of an early Ensemble system through the elimination of features in the hosted software component.

If there was no serious engineering reason to do so, we might be tempted to assume that Apogee cut out a very useful feature in order to save itself cost, time to market, inconvenience to staff or contractors, whatever interfered with following some unknown in-house path of least resistance toward releasing the current versions of Maestro 2. We may also be tempted to think that Apogee felt comfortable not playing catch-up and restoring functionality in subsequent updates, or to put it less benignly, foisting underwhelming software on its existing user base. The picture that seems to be emerging so far (please correct me if I get this wrong) is that Apogee has allowed developers unknown deliver a new software end for some older systems that is underwhelming due to questionable user interface programming practices and the deletion of control features. Apogee has also, clearly, allowed technical writers unknown to deliver substandard documentation of the resulting software, thus compounding the problem. So, back to the more general issue: we are gradually losing access to perennial, self-contained, hardware/firmware systems. My Mini- stack only needs to be recognized by OS-level tools to operate well with a modern Mac or PC, and it can do a lot without a computer connected.

My Sound Devices gear is designed for the field and their latest USB audio interface can also operate without a computer. Whereas with the first-generation Duet or Ensemble, customers are dealing with systems that were made completely Mac-dependent by design, forcing them to deal with Apple and Adobe with each major iteration of the Apple hardware and operating system. This is hardware whose outward simplicity and slickness come at the cost of being incapable of, say, recording without an OS X or iOS device attached. Well, the problem with designing audio interfaces as extensions of current computers is that eventually we can be forced to preserve older computers as mandatory extensions to these same interfaces. That, in essence, is what happens when we wind up using an outdated Mac and a vintage version of OS X in order to salvage our investment in a poorly supported Apogee audio interface. And so, the same issue that plagues users stuck with questionably marketed abandonware like Bias Peak 7 is looming larger with audio hardware.

It's all about the system as a whole, and with providers like Apogee, unpleasant issues can arise coming either from the hardware/firmware side or from the software side. Potential show-stoppers thus keep multiplying. I am beginning to think that such an investment can be unwise unless there is a budget for replacing entire systems outright if needed -- a proposition that only some users will not balk at outright. My jaundiced view is that a company like Apogee might see an incentive to offering weak(er) support for older hardware if enough users just keep buying newer models. For my simple needs, the audio interface should be a reliable appliance with an absolute minimum of computer/tablet-hosted software (otherwise, why not move on to United Audio?). I tend to dislike control panels blended with proprietary drivers, especially when this mixes higher-level functionality best left to other software, unless they are rock-solid -- which requires the right corporate culture and goals in the first place. So, I really hope Apogee did not knowingly slouch into making their own hardware less reliable and functional over time.

If they will not do the job themselves, they should expose the inner workings of older hardware, low-level software and firmware to third-party developers who might deliver better support through independent efforts. They might even benefit from sharing a open code base with a larger community, especially when much of the effort would relate to a handful of well-documented chips from key manufacturers. Anyway, I'd rather pay a serious developer to keep my good old Duet chugging along without ever having to deal with Maestro again. A specialized driver plus control panel developer could build relationships with audio interface companies across the board in order to create, maintain, and sell such a product.

Something similar was done for scanners by Hamrick Software, and the results are simply rock-solid. What I am saying, in a sense, may amount to a suggestion to open up and outsource Maestro and related software.

One obvious side benefit would be potential support for more associated platforms (assuming Apple did not impose abusively restrictive clauses as part of its partnership with Apogee). I remain, indefinitely, using OSX 10.6.8 specifically because Apogee broke support for Keyboard volume controls. The controls are crucial as the volume pot on my Ensemble is useless. After speaking with them, they were aware of this and had no plans to fix it.

That was a few years ago. However, it sounds great and has been rock solid since I started leaving on overnightNot sure where your issue comes from but I've been using an Ensemble with the latest versions of OSX and Maestro for the last five years with no problems ( including keyboard volume control etc.) I do agree it's not the greatest piece of driver software design ever though. Not sure where your issue comes from but I've been using an Ensemble with the latest versions of OSX and Maestro for the last five years with no problems ( including keyboard volume control etc.) I do agree it's not the greatest piece of driver software design ever though.Wow. I would have absolutely upgraded.

When I spoke to Apogee, I asked specifically if there were plans to fix it and was told a definitive 'No'. The problem was, there no way for me to check, ie. Not going to Update >10.7 to confirm that it didn't work and then have to revert. It had been well documented around various forums and by the time I was looking into the issue, I seem to remember the update was already many months old.

Thanks for reporting this and pointing out my misinfo. Its actually a little reassuring that a co.

That I so depend on would NOT have this issue. When I spoke to Apogee, I asked specifically if there were plans to fix it and was told a definitive 'No'.

The problem was, there no way for me to check, ie. Not going to Update >10.7 to confirm that it didn't work and then have to revert. This is a very good illustration of the implications of relying on hardware/firmware/software systems.

Our computers all are, right off the bat, which is going to create compatibility challenges with three major variables on that side. Add a second such system as a peripheral, and there are a lot more moving parts in terms of possible combinations and interactions. All it took for you, acmusic, to stop looking was awareness that a new computer would be needed just to run Lion (if I read you correctly). Whereas you, explorer, being already past the Lion compatibility hurdle, were free to explore with a later release of Maestro. There is a lot of complication involved, which is not a bad thing in and of itself provided everything works and you can figure out how to make it work. Again, I think the interface confusion and weak documentation cannot be excused if serving customers as well as possible is a core objective (we hope it is) and the resources are available (we know they are).

Apogee employees are found online discussing issues or promoting Apogee solutions (with no mention of their affiliation in some cases). It is obvious that they actively search for discussions, seemingly joining forums for the sole purpose of adding their two cents in some cases. So how come clear interface design and comprehensive documentation are such low priorities at Apogee?