1 person found this helpful
Did you try bypassing the Matrox?
fiddled around with player settings/input/output stuff...
Which "player settings?" I think the ones that the error message are referring to are actually in Edit > Preferences > Player. It's probably set to "Matrox Player" and would work if set to "Adobe Player" (it's a dropdown selector).
Hi Jim, thanks for taking the time. Bypassing the Matrox means, for me, using the Sound Blaster input instead. Happy I had that one built in the system anyway...
This input works like a charm: it records straight to the timeline and everything is processed very fast.
However, I think it's strange that the Matrox MX02 LE, especially designed for working with Premiere, seems to be failing at the first attempt to do something very very simple: record a voice over... It must be a setting somehow.
The point is that it just feels strange to have all of the audio input connected through one SoundBlaster minijack, while on the other hand the Matrox box with all of its sturdy input ports remains unused... in case of audio I mean.
Anyway, the bypass is a reasonable workaround. Thanks for your reply!
Hello guys, Jim, Colin,
I just seem to have fixed the problem.... I noticed that after switching forth to the Sound Blaster inputs and back to the Matrox inputs again, I could all of a sudden press recording in the timeline WITHOUT the error screen, however the sound was not recorded any longer than a few samples, less than a second .....
So my guess was, that it really came down to a syncing problem... and yes, I tried a couple of Matrox settings again, but no different than yesterday. But then Matrox also has its own capture settings screen, where you define the right audio AND video inputs. Here lied the problem: video was still referring to SDI input but there was no such device connected. Switching to S-Video (which was connected) at first changed nothing, however, deliberately switching to a disconnected analog video input source (composite) and back to S-Video again solved the problem!
It's a bit of an unsatisfying way to "solve" a problem, but somehow this seemed to have worked.... anyway, thanks so much for your time and answers. I am really relieved that it wasn't a bug or actual shortcoming in software or hardware.
So cheers dear people! I hope that if anyone else ever bumps into this problem, this thread could be helpful...