The problem with recording from the microphone

[АйкиН]

When trying to record from a microphone, they write. Failed to create a new audio recording file. What to do? I've been trying to do something for a week now, but without success

[reginaldStjohn]

We really need to know more about your setup. What audio card are you using? What driver mode? Is this the built in microphone on a laptop or a dedicated microphone plugged into an audio interface?

Can you record audio from another source or do all recording modes fail?

Please try the tutorials section to see some examples.

[slartabartfast]

39 minutes ago, АйкиН said:

Failed to create a new audio recording file

I have not seen that error message before. Are you sure you are using the Cakewalk application, and not some other software like Bandlab?

Time to back up and give us all (you included) something to think about.

How is the microphone connected to the computer? If it is a typical analog connection, then is it plugged in to the audio input socket on the motherboard, or are you using an external audio interface that in turn connects to the computer (usually by USB)? If it is a "USB microphone" plugged directly into the computer by a USB socket, then is the driver (logical microphone) showing up as working in Windows? Alternatively can you record anything from the mic in another application--like the windows voice recorder which is installed by default? That would test that the physical connections and microphone--so if that works...

Does the driver for the mic or the audio interface show up as an input for Cakewalk?

Does that input show up as the input to an audio track?

Is the track armed? 

 

[scook]

If this is the error I am thinking of, it means some other process is preventing Cakewalk from creating files.

Generally, it is a good idea to post an image of the English version of the error message instead of interpreting them.

 

The problem may be antivirus or antimalware software blocking disk writes.

Make sure these programs are up to date.

Years ago, there was a rogue antimalware program called ByteFence that was secretly installed with some software. It is known to cause this problem. The solution in this case was uninstalling ByteFence.