Problem getting audio in Premiere 6.0/6.5

[mayancastle]

I know this technology is taking us back to archaic times, but I am using a Matrox RT2000 on a Win2k box with Premiere 6.0/6.5. I hadn't used the computer in nearly a year and recently I woke up in the middle of the night wanting to check something out on the machine. But at boot up, it kept complaining about no system drive. So, I looked into the cabinet and realized that the last time I dickered with it I had tried to install a hard drive with WinXP on it. That failed and I never connected back the original hard drive. But, it was sitting there, and stupidly, ( I guess because I just woke up in the middle of the night), I tried to plug it in with the power on....

ZAP!

And the thing went dead. And wouldn't start back up.

So, a few days later I took the thing downstairs and rebuilt it. To my surprise, no damage was done. All the harddrives worked. The RAM was all good. The fasttrak striping device was fine. I got sound. All my software was there and the videos and audio files were all there. I did have to reset some of the BIOS settings.

So, now I've got a couple of projects I need to work on. But I can't get sound in Adobe Premiere 6.0 or 6.5. I get sound through the operating system. Just not in Premiere. I get video in Premiere. And when I check the Matrox audio meter, it is detecting sound. But, it's not playing.

I've gone all over the web. Matrox no longer gives any support for the RT2000. Not even the forums. I did go through the archived forum and tried ideas from there.

I've uninstalled the Matrox video tools. I also uninstalled both versions of Premiere and re-installed 6.0. Then re-installed MVT. The most recent tools, can't remember the version number off hand.

I came to the conclusion that it's hardware problem. And I think it's the link between the sound card, ( a SoundBlaster Live 5.1 running off of the OS driver only. No proprietary drivers.), and the Matrox capture card. The manual states any audio in or out of Premiere goes through the capture card. The cable that connects the cards, (through the auxiliary in on the SBLive), allows me to plug it in more ways than one and I've tried all configurations uninstalling and reinstalling MVTools each time.

I'm at wits end. Perhaps this was the only damage done by midnight prowl? But it seems odd that it would happen to the capture card and nothing else. The spark occurred at the hard drive power plug.

I'm hoping someone from this forum might have had some experience with the Matrox solution and can give me ideas. Or at least give me some diagnostic advice to determine if it is indeed the capture card, ( Oh, I also tried to capture into the system. I got video, no audio. Not even on the Matrox audio meter). Maybe I can pick up a cheap used Matrox capture card somewhere?

Thanks.

[mayancastle]

Just a follow up...

If anyone out there has a Matrox RT2000 they can sell at a reasonable price, I would be interested.

[edDV]

I suggest you uninstall and reinstall all in the order suggested by Matrox.

I'd use Premiere 6.5. It is much more stable.

I have Premiere 6.5 installed (without hardware) under XP SP3. It works fine.

In a simple install, the audio out device shows under Windows Volume, Playback, Properties.

Here is a screen shot.

[mayancastle]

edDV said:
"I suggest you uninstall and reinstall all in the order suggested by Matrox.

I'd use Premiere 6.5. It is much more stable. "

Yes, I am thinking of reinstalling everything one more time. But I can't do that with Premiere 6.5 because Matrox Video Tools will only install with 6.0 - if 6.5 is present the tool installation will quit. To install 6.5 you have to first have the tools installed with Premiere 6.0 and then use a hotfix patch.

I decided to try a firewire capture to see how that would work out. (Before I was capturing through the BOB.) Again, there was video but no audio. But on playback I saw audio through the Matrox audio meter. It turns out that Premiere saved the audio in a special folder. That wouldn't happen with a capture through the BOB. And I could play the audio through CoolEdit, outside of Premiere.

I'll rebuild the system one more time tomorrow and see what happens, but I can't re-install win2k itself because I'll never retreive some of the programs I have installed. I no longer have a backup for some of them, like cooledit and soft encode.

[edDV]

edDV said:
"I suggest you uninstall and reinstall all in the order suggested by Matrox.

I'd use Premiere 6.5. It is much more stable. "

Yes, I am thinking of reinstalling everything one more time. But I can't do that with Premiere 6.5 because Matrox Video Tools will only install with 6.0 - if 6.5 is present the tool installation will quit. To install 6.5 you have to first have the tools installed with Premiere 6.0 and then use a hotfix patch.

I decided to try a firewire capture to see how that would work out. (Before I was capturing through the BOB.) Again, there was video but no audio. But on playback I saw audio through the Matrox audio meter. It turns out that Premiere saved the audio in a special folder. That wouldn't happen with a capture through the BOB. And I could play the audio through CoolEdit, outside of Premiere.

I'll rebuild the system one more time tomorrow and see what happens, but I can't re-install win2k itself because I'll never retreive some of the programs I have installed. I no longer have a backup for some of them, like cooledit and soft encode.

I can't help directly with the Matrox card but the hardware drivers from that era are mini applications. They separate the hardware from the Windows API. Without the hardware driver, Premiere 6.5 will default connect to the sound card for audio out and to the IEEE-1394 for audio input.

My experience is with the Miro-Pinnacle DC-30Plus and DC-1000.

[filmboss80]

I have PM'd you about a Matrox RT2500 that is in my possession. I have no use for it at this point. Let me know if you are interested.

[mayancastle]

Got it working. I'm not sure what the problem was I just uninstalled the software and rebuilt the computer and reinstalled the software and this time it worked.

Can't complain, I guess, but I sure wish I knew what it was.

Thanks all.