I’ve found some older somewhat similar threads, and they don’t seem hopeful on this topic, but maybe there are some other ideas. What I’m trying to do:
I have a Windows 2000 server computer, which is the only one on-hand with a line-in connection. Because of that, it’s the only thing I can use to digitize audio cassettes through a line-in cable from a stereo system across the room. I can make it work when running the W2K box natively, but that’s less convenient (I have to juggle keyboards, mice, and hit lots of buttons on a monitor to switch its input to display the W2K box instead of my main PC, which runs Windows 7 Professional, 64 bit.
I can connect to the W2K box via RDP from the Win7 box, and most things work that way. Audacity, unfortunately, is not one of them. When I bring up Audacity (I have 2.06, which is apparently the most recent version that will work on W2K, but I also have an older version, and they behave no differently in this respect). I don’t think this is Audacity’s “fault,” since none of the audio-related tools will work over my RDP connection. Volume Control, for example, reports “no active mixer devices available.” Audacity likewise sees no audio devices in this mode.
I went to Terminal Services, Connections properties on the W2K box, where RDP gets configured, and navigated to “client settings.” There is a panel, “Disable the following” and “audio mapping” is checked and greyed-out so that I can’t un-check it.
So, I’m wondering if there’s a way to convince my W2K box to see its audio system. I intend to have Audacity record to the W2K box and then export to my Win7 box when done. I don’t think there’s a way for Audacity on my Win7 box to see the audio devices on the W2K box (as in theory, I can use a printer on a networked computer from the client), so my guess is that’s not an option. Otherwise, I guess I’ll either deal with the keyboard/mouse/monitor juggling or look into a line-in to USB adapter for my Win7 box.