Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Foo_record (Read 6919 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Foo_record

I've been trying and trying again for a week, but to no avail.
I installed the foo_record component, in the recorder section I set the system device and then Add Location and wrote record://. After playing, a Playback Error window appears and I can't do anything else.
Any suggestions?
Thank you

Re: Foo_record

Reply #1
The error message or console should give more details about the problem. But some guesses are that you have configured recording settings incorrectly, like unsupported bit depth or number of channels. Or you are trying to record with a device that is playing in exclusive mode and is thus locked.


Re: Foo_record

Reply #3
The error message or console should give more details about the problem. But some guesses are that you have configured recording settings incorrectly, like unsupported bit depth or number of channels. Or you are trying to record with a device that is playing in exclusive mode and is thus locked.


How can i control the esclusive mode?

Re: Foo_record

Reply #4
The error message explains your problems. You don't have an audio device that can record anything.

Re: Foo_record

Reply #5
What?


Re: Foo_record

Reply #7
As the error message states, your device doesn't support the recording format you have configured.

Re: Foo_record

Reply #8
I tryied all format, from 16 bit 44.1 to 24 bit 192 and the result is the same


Re: Foo_record

Reply #10
I want to use record:// for capturing audio from Browser Edge or Firfox

Re: Foo_record

Reply #11
For starters verify that the component sees your recording capable audio device. In the Preferences -> Tools -> Recorder where you now have "Default Recording Device" listed, if you click on that drop down menu you will see all the recording devices available. The default maps to Windows default and it's always listed, even if you have no audio devices at all. All the actual devices are listed in addition to the default.

Then you should navigate to Windows sound settings. You can use the new modern UI or navigate to the old sound control panel and its Recording tab. Check the properties of the input device you want to use and pay attention to number of channels, bit depth and sampling rate values. The device properties lists what is supported and you should configure the actual device to what you want to use during recording too, so there is no additional resampling involved.

I'm a bit curious about how you are recording as your screenshot seems to show you using UPnP output and you mention here that your DAC is this device that doesn't look like an audio interface for PC.

Re: Foo_record

Reply #12
Yes my endpoint audio device is an Upnp Atoll MS120

But i want to record from system audio, from Edge or Firefox or Youtube

I try to use Virtual Cable, bit I can’t find a solution

Re: Foo_record

Reply #13
You need to install a virtual audio cable device that presents itself as a regular output device for the system and offers a recording interface for reading that output by foo_record.

Re: Foo_record

Reply #14
Thank you.
Examples?

I download VBCable and install it

Do you think to VBCable or others?

Re: Foo_record

Reply #15
I have no recommendations or experience with any of such products. I only know they exist, some freeware and some payware. One you have a working software installed everything will work.

Re: Foo_record

Reply #16
Hello,
I have a strange issue. On one of my desktop, which does NOT have DSD Processor, the VB Cable works fine and I am able to stream Spotify through Foobar using the foo_record. Works like charm.
But for some reason, on the audioserver, it gives me a "Unsupported Format" error. Currently using Oppo UDP-205 as the DAC. Maybe that DAC is not supporting a format, is my guess. OR, I foo_record does not like DSP like DSD Processor - not sure.

Anyone else has issues using DSPs along with foo_record?

Thanks!

Re: Foo_record

Reply #17
@Angelo58 ,
That default device in your screen shot is incorrect.
You should be choosing "CABLE Output (VB-Audio Virtual".

Hope this resolves your issue.

Re: Foo_record

Reply #18
I upgraded my DAC to a T+A DAC 200 and have been converting everything (except pure DSD files) DSD 512 to feed the DAC. I found out that I was sending DoP all these years to the older DAC. So I made setting changes and was able to send native DSD 1024 to the DAC.

With this comes new issues for foo_record. This stopped working.
The issue was resolved after I changed the "Buffer length" in the "Output" from 150ms to 1000ms.

Hope this helps someone searching for issues with foo_record.

Re: Foo_record

Reply #19
Since the last update (moving from MME API to WASAPI), I'm experiencing a bug where input is very choppy - even just monitoring it without writing to disk, the plugin is unable to keep the steady, realtime stream going - it's intermittent, which can both be heard and seen on the oscilloscope/any other visualisation. What might be causing that?
The operating system I'm using is Windows 8.1 x64 non-professional edition.

PS. Please do keep the archive of all previous versions on the official website - it's a hassle to revert to last working version otherwise since i'm forced to use Archive.org
Random digital audio nerd girl
A potato

Re: Foo_record

Reply #20
And you don't run heavy DSP setup like in this thread? I posted a "debug" build in the other thread that prints information to console, it might give a clue what goes wrong. The initial debug version was otherwise identical to 0.2.5, the current one has a slightly different buffering logic. 0.2.5 feeds foobar2000 always with 2048 frames at a time. The test build gives all of the buffered data at once. Usually probably 10 ms worth, but if foobar hasn't asked the data for whatever reason for a while, it could be up-to 5 seconds.

Re: Foo_record

Reply #21
Thank you for the response. As far as my DSP chain goes, there is literally none (see the picture). I will try the debug version and see how it performs.

Random digital audio nerd girl
A potato

Re: Foo_record

Reply #22
Code: [Select]
Opening track for playback: "record://"
13:54:10.995:  Recorder debug: input_record()
13:54:11.002:  Recorder debug: init_recording
13:54:11.003:  Recorder debug: open_device
13:54:11.003:  Recorder debug: Finding the selected recording device
13:54:11.012:  Recorder debug: GetDevicePeriod: default: 10.000000 ms, minimum: 3.000000 ms
13:54:11.030:  Recorder debug: IAudioClient::GetBufferSize returned frame size: 883
13:54:11.087:  Recorder debug: IAudioCaptureClient::GetNextPacketSize reports there are no frames recorded
13:54:11.110:  Recorder debug: IAudioCaptureClient::GetBuffer reported AUDCLNT_BUFFERFLAGS_DATA_DISCONTINUITY
13:54:11.190:  Recorder debug: IAudioCaptureClient::GetBuffer reported AUDCLNT_BUFFERFLAGS_DATA_DISCONTINUITY
13:54:11.200:  Recorder debug: IAudioCaptureClient::GetBuffer reported AUDCLNT_BUFFERFLAGS_DATA_DISCONTINUITY
13:54:11.220:  Recorder debug: IAudioCaptureClient::GetBuffer reported AUDCLNT_BUFFERFLAGS_DATA_DISCONTINUITY
13:54:11.230:  Recorder debug: IAudioCaptureClient::GetBuffer reported AUDCLNT_BUFFERFLAGS_DATA_DISCONTINUITY
13:54:11.251:  Recorder debug: IAudioCaptureClient::GetBuffer reported AUDCLNT_BUFFERFLAGS_DATA_DISCONTINUITY
13:54:11.260:  Recorder debug: IAudioCaptureClient::GetBuffer reported AUDCLNT_BUFFERFLAGS_DATA_DISCONTINUITY
13:54:11.280:  Recorder debug: IAudioCaptureClient::GetBuffer reported AUDCLNT_BUFFERFLAGS_DATA_DISCONTINUITY
13:54:11.290:  Recorder debug: IAudioCaptureClient::GetBuffer reported AUDCLNT_BUFFERFLAGS_DATA_DISCONTINUITY
13:54:11.310:  Recorder debug: IAudioCaptureClient::GetBuffer reported AUDCLNT_BUFFERFLAGS_DATA_DISCONTINUITY
13:54:11.320:  Recorder debug: IAudioCaptureClient::GetBuffer reported AUDCLNT_BUFFERFLAGS_DATA_DISCONTINUITY
13:54:11.340:  Recorder debug: IAudioCaptureClient::GetBuffer reported AUDCLNT_BUFFERFLAGS_DATA_DISCONTINUITY
13:54:11.350:  Recorder debug: IAudioCaptureClient::GetBuffer reported AUDCLNT_BUFFERFLAGS_DATA_DISCONTINUITY
13:54:11.371:  Recorder debug: IAudioCaptureClient::GetBuffer reported AUDCLNT_BUFFERFLAGS_DATA_DISCONTINUITY
13:54:11.380:  Recorder debug: IAudioCaptureClient::GetBuffer reported AUDCLNT_BUFFERFLAGS_DATA_DISCONTINUITY
13:54:11.400:  Recorder debug: IAudioCaptureClient::GetBuffer reported AUDCLNT_BUFFERFLAGS_DATA_DISCONTINUITY
13:54:11.409:  Recorder debug: IAudioCaptureClient::GetBuffer reported AUDCLNT_BUFFERFLAGS_DATA_DISCONTINUITY
13:54:11.429:  Recorder debug: IAudioCaptureClient::GetBuffer reported AUDCLNT_BUFFERFLAGS_DATA_DISCONTINUITY
13:54:11.440:  Recorder debug: IAudioCaptureClient::GetBuffer reported AUDCLNT_BUFFERFLAGS_DATA_DISCONTINUITY
13:54:11.460:  Recorder debug: IAudioCaptureClient::GetBuffer reported AUDCLNT_BUFFERFLAGS_DATA_DISCONTINUITY
13:54:11.470:  Recorder debug: IAudioCaptureClient::GetBuffer reported AUDCLNT_BUFFERFLAGS_DATA_DISCONTINUITY
13:54:11.490:  Recorder debug: IAudioCaptureClient::GetBuffer reported AUDCLNT_BUFFERFLAGS_DATA_DISCONTINUITY
13:54:11.500:  Recorder debug: IAudioCaptureClient::GetBuffer reported AUDCLNT_BUFFERFLAGS_DATA_DISCONTINUITY
13:54:11.520:  Recorder debug: IAudioCaptureClient::GetBuffer reported AUDCLNT_BUFFERFLAGS_DATA_DISCONTINUITY
13:54:11.530:  Recorder debug: IAudioCaptureClient::GetBuffer reported AUDCLNT_BUFFERFLAGS_DATA_DISCONTINUITY
13:54:11.550:  Recorder debug: IAudioCaptureClient::GetBuffer reported AUDCLNT_BUFFERFLAGS_DATA_DISCONTINUITY
13:54:11.560:  Recorder debug: IAudioCaptureClient::GetBuffer reported AUDCLNT_BUFFERFLAGS_DATA_DISCONTINUITY
13:54:11.577:  Recorder debug: ~input_record()
13:54:11.577:  Recorder debug: deinit_recording
13:54:11.580:  Recorder debug: IAudioCaptureClient::GetBuffer reported AUDCLNT_BUFFERFLAGS_DATA_DISCONTINUITY
13:54:11.580:  Recorder debug: close_device
13:54:11.582:  Recorder debug: close_device
13:54:11.582:  Recorder debug: RecordThread ended normally
13:54:11.582:  Recorder debug: close_device

Clearly there is something going on with the data in the buffer (i am recording from Logitech camera's microphone endpoint, but as i tried earlier with Internal Stereo Mix, the effect was pretty much the same).
Random digital audio nerd girl
A potato

Re: Foo_record

Reply #23
Update: I tested several devices/endpoints in different modes (exclusive and shared) again. Here are the results:

Stereo MIx (both exclusive and shared): Stream is uninterrupted and clean, except a single "AUDCLNT_BUFFERFLAGS_DATA_DISCONTINUITY" message at the very start of the capture. All visualisations work as normal, except the oscilloscope which is flickering (never occured in v0.2.3)

Notebook's Integrated Microphone (both exclusive and shared): Same as above

Logitech Camera's Microphone (both modes): As in my original post - constant interruptions and giant error log in the console.
Random digital audio nerd girl
A potato

Re: Foo_record

Reply #24
One more weird behaviour i noticed: The stream behaves fine ONLY if the sampling frequency is set to 48KHz, no matter whether the mode is exclusive or not).

Logitech camera is the exception here - In shared mode 48KHz is as bad as always, and in exclusive mode i am forced to manually enter 32KHz, as this is the highest sampling frequency natively supported by that device.
Random digital audio nerd girl
A potato