TC Konnekt 24D Interface Woes
- From: anders.dufay@xxxxxxxxx
- Date: Thu, 26 Jul 2007 03:31:49 -0700
I'm posting this here because I've exhausted my other problem-solving
options, and it just might be the case that one of you fine people has
encountered a similar problem with another piece of equipment, and can
offer a solution that would not otherwise be forthcoming. My apologies
for the novella that follows... feel free to skipip the background
info at the beginning if your patience is limited.
I have been attempting to get the K24D interface to work with my
system since I got it last December. At the time, my AGP Graphics G4
was still running Panther exclusively, and I bought the K24 at that
time because it offered Panther support (had it not, I would have
waited before buying it, or bought something else, since, for a
variety of reasons, I was not ready to move up to Tger).
Sync between the interface and the computer would only be achieved inFrom Day One, it was obvious that all was not well in Konnektland.
10-20% of attempted cases, necessitating a reboot of the computer
every time it failed. Then my Konnekt experienced a hardware failure
which required a replacement of the unit. That brings us to March or
so, when TC released the second or third driver update (1.10) which
did not offer Panther support (nor have any of the more recent
updates). Of course, they never said they were no longer offering
Panther support (well, they never really say very much at all...), so
I waited... and waited... and waited... no Panther-friendly driver
anywhere on the horizon. Finally the 1.20+ series of drivers appeared
in June, still no Panther support, so rather than allow my K24 to
gather dust for the rest of my lifetime, I made some time to move a
bunch of files around and clear off a partition on my HD on which to
install Tiger. Which I did. Upgraded to 10.4.10. I optimistically
installed the most recent Konnket driver package. Turns out there's
some bug in the TC s/w that will not allow me to update the
interface's firmware from my machine (even though I am booted into a
partition that has had no OS X or TC/Konnekt s/w installed on it
before, although I have had earlier versions of the TC s/w installed
under Panther on another drive in the same machine).
Someone suggests connecting the interface to another machine that has
not had any earlier versions of the driver installed, and to try
updating the interface's firmware from that machine. So at the first
opportunity, I take my Konnekt to a friend's place, hook it up to her
G4 which is almost identical to mine, install the TC konnekt driver,
and find that I am, happily, able to update the firmware to the most
recent version, and also able to open the TC Near Control Panel, and
adjust levels, apply effects, etc., in the mixer pane.
Ecstatic, I take the unit back home only to discover that I am once
again stuck at the "No Device or Driver Version Mismatch" message/
window that denies entry to the Control Panel. There is the option to
update the firmware from there, but attemtping to do so leads nowhere
since I now already have the most recent version of the driver
installed. I tested the interface again on my friend's G4, and the
Control Panel opens and can be used on that machine (no error message
as on mine).
So, my question to those of you are knowledgeable in the area of
interfaces, drivers, and the like: what could be causing the TC
Control panel to give that error message on my machine, when it does
not do so on a virtually identical machine, the main relevant
difference between the two being that mine has had earlier driver
versions installed, and the other one has not? Before installing the
most recent driver on my own machine, I not only used the TC
uninstaller to remove the earlier Control Panel, but also--using File
Buddy--tracked down all TC/Konnekt-related files and trashed them
before reinstalling.
I also discovered that this file:
com.apple.Components2.LocalCache.AudioComponents
in volume/library/caches
was modified at the same time as other TC-related files, and so I
trashed it, but unfortunately that did not resolve the issue.
If anyone can offer some insight into what may be going on here--or,
even better, offer some pointers on further things for me to try--I
would be more than grateful. TC are, unfortunately, proving much less
than prompt and helpful in helping myself and others resolve the
issues we are experiencing with our interfaces and the software that
controls them.
Thank you for reading!
.
- Follow-Ups:
- Re: TC Konnekt 24D Interface Woes
- From: Mogens V.
- Re: TC Konnekt 24D Interface Woes
- From: Mogens V.
- Re: TC Konnekt 24D Interface Woes
- Prev by Date: Re: Pre-Amps, A/D, Etc.
- Next by Date: Re: Mic pres - what's the story?
- Previous by thread: FA: Vintage Altec 439A Tube Compressor Limiter
- Next by thread: Re: TC Konnekt 24D Interface Woes
- Index(es):
Relevant Pages
|
