5.5 question

[Rich LePage]

Finally got around to setting up Medit 5.5 on a WinXP pro machine, Athlon XP 2500 CPU.

Noticed that the m/media driver is GONE-- Wondered why?
Will one of the earlier ones work?
It is helpful to be able to play out of Krystal for running
with Cool Edit pro (or the Adobe version) when using
their EQ or other processing, to check the quality using
preview or similar in an external program.

Also, the Direct X link STILL seems to not work right.
I cannot get it to not crash. I've been noting this ever
since the link first appeared in Medit -- I was never able
to get it to work with any 3rd party DX plug ins.

On the XP Pro system, I have authorized Waves
plug ins-- quite a few of them. Their new system uses
a USB dongle called ILOK, so that you can put their
software on ANY computer, and then you insert your
authorized-by-them ILOK key and the plug ins will run.

But though they run perfectly with Cool Edit and some other
stuff, I cannot still get them to run with Medit. Medit will always
crash when attempting to run them-- or anyone else's.
Not just on this machine, either-- on any we've ever tried
to run the Direct X link on. We've been trying since way back
in Direct X 8.0. But with Cool Edit Pro installed on the same
machines (mostly Win98 and WinME) and the 5.4. Medit
m/media driver installed, the other programs run the
Direct X stuff, but Medit crashes on every try.

Any ideas of what can be tried? Been asking on this one
for some time. The fact that the other programs always
run them seems to rule out Direct X problems etc.
Also DXDiag has always reported all was fine when
I've tested this in the past on Win98, ME, etc.

The m/m driver would be handy. Presently I have to
use the motherboard's onboard NVidea audio out to
audition with. It is reasonably good quality for an
onboard device, but nowhere near Krystal of course.

Let me know, also if anyone else has seen this or
what's noted below.

Medit will also nearly always over-run on this machine
when you start a session, with nothing else running
or anything. I have seen this with both the Krystal
analog input as well as with its SPDIF in and AES, too.

When you first start it recording, it will run 10 to 15
seconds, then stop and report an over-run.
This occurs at standard 44.1K, 16 bit.

However, when you then discard what was recorded,
close the record screen, re-open the filename you
want to record, and then try again, it will work OK.

This is something I've never seen on any of our other
MTU systems. Anything I should check or change?

Both the boot drive and drives being recorded on
(removable) are FAT32, and regular EIDE/ATAPI drives
that seem to be set up correctly. XP indicates nothing
is fragmented on them. This will happen with everything
from IBM 9 gig drives to Maxtor 80 giggers. I also tried
with some of my FAT16 drives and same thing happens.


The machine is an Athlon 2500 with 1 gig RAM.

All best to all at MTU and here on the forums,
let me know if anyone has input on these-- thx.

Rich LePage