Symptom: I press the record button and it creates a new audio track, but the time marker remains stuck at zero.
Reaper has no problem recording on my setup.
The only host that works for me in Audacity is WASAPI. The rest give errors no matter what I do. For some reason, the input got set to a value it didn’t like. It could be that was why it was taking forever for Audacity to start up. That delay seems to have gone away, maybe because I set the input to a value it thinks is OK and now it remembers.
It did record once, yesterday, after I ran the Windows troubleshooter on my sound system. Today Audacity refuses, but Reaper does fine.
I’m never sure if this is a Windows Update issue or an Audacity update issue, but this version of Audacity seems to be more stubbornly refusing to record. I’ve had similar issues with the older version (I forget which) but running Windows troubleshooter has always fixed those, and generally I think they were the result of Windoze updates (e.g. incorrectly unchecking the 44.1khz box for the device) This time I’m leaning towards thinking Audacity is the culprit.
Windows 10, MOTU 828 mixer via firewire
thanks,
-=miles=-
1 Like
That’s a feature not a bug …
" Windows WASAPI host only records loopback when there is an active signal present. When there is no active signal, recording pauses and will restart once an active signal resumes."
https://manual.audacityteam.org/man/tutorial_recording_computer_playback_on_windows.html
What do you mean by “signal?” I’ve seen it record silence, which is what I want at the beginning. I don’t want the behaviour you are describing, nor have I seen it before. NOT a feature, in my book!
Audacity recognized the device (MOTU 828) and all of its inputs and outputs. I selected one of them (actually I tried several, but nothing worked). How is there no “signal?” If that makes sense, I don’t understand how. There is definitely sound being transmitted on those channels, but that didn’t solve the problem.
Therefore, I label this a bug.
I notice that Reaper is using ASIO. That option is not available for me in Audacity. The 828 is an older piece of hardware, probably more designed for the Mac, which would explain why the older driver might work better, particularly for Windoze.
Is there some way I can use ASIO with Audacity? ASIO seems to work perfectly, whereas Audacity isn’t working at all, to record, as it once did.
Now I’m really sorry I "up"graded - and may have to deal with the hassle of regressing to an earlier version.
I simply cannot get 3.7.3 to behave at all; sometimes one host works, sometimes not, then another will “work” I say “work” because the sound on any overdubbed track - assuming I can get it do more than start and immediately stop - is atrocious: clicks, drop outs, distortion, slowing down(!), variable latency. It’s a joke.
It’s been about 15 years since I tried to record using a computer and audio interface and I thunk things are actually worse now than then. I spend all of the time I want to spend recording effing about with the recording devices! Bloody hell - maybe I should buy a porta studio!
1 Like
v2.4.2 is only 5 years old … Old Audacity versions download
Some swear by it, (rather than swear at it).
NB: Audacity projects are not backwards compatible: v3 projects cannot be opened by v2.
1 Like
Many years ago, any program could use any device without needing to ask you for permission.
People began to worry about some program doing this to spy on you.
Now security device protections are part of the operating system, and are meant to look out for you. But it makes legitimately using those devices more difficult.
Is there some reason Audacity doesn’t support ASIO?
Or better, something I can do to convince it to?
It can record a silent stream (which is a stream of zeros) but it can’t record “nothing”. This is a Microsoft characteristic. There are work-arounds like playing a silent file in the background but that “trick” isn’t built-into Audacity.
Microsoft: