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 6381 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Re: Foo_record

Reply #25 –
Uploaded a new test build: https://foobar.hyv.fi/foo_record_debug.fb2k-component. The bottom test options are not saved in config, they are only remembered while foobar2000 is running. Note that they take effect after recording is stopped and restarted.
The buffer length option allows overriding the internal WASAPI record buffer length. Default 0 means to use device default (typically 10 ms).
Chunk length option overrides how much data is given to foobar2000 per request for more data, the length is in frames.
And finally there's an override to disable event driven recording and use pull mode.

Re: Foo_record

Reply #26 –
Thank you for your work! WIll test in a bit and report back.
Random digital audio nerd girl
A potato

Re: Foo_record

Reply #27 –
Pull mode & default buffer: Perfect
Pull mode & default buffer & 1024 data chunk: Perfect

Event mode & default buffer: Choppy, exactly like the release version i first spotted this issue in

Event mode & gradually increasing buffer length from 200ms to 1000ms: Initially smooth stream, but eventually the dropouts and ""AUDCLNT_BUFFERFLAGS_DATA_DISCONTINUITY"" errors start creeping in. With 1000ms buffer it can take more than a minute for error threshold to be crossed.

In conclusion, it seems that my system generally has issues with WASAPI Event mode (i vaguely remember having similar issues with regular playback using this kind of output config in the past).

Thank you for implementing the pull mode, please do keep it in the future releases. I'd love for the advanced options to be kept too, perhaps explicitly marked as advanced.
Random digital audio nerd girl
A potato

Re: Foo_record

Reply #28 –
That's good, thanks for testing. I think I'll leave the buffer length configurable, but I don't think the chunk size needs to be adjustable. It's static with other inputs after all. Does adjusting it affect your visualization smoothness?

Re: Foo_record

Reply #29 –
Nope, didn't seem to have any effect, i guess it might be removed.
Random digital audio nerd girl
A potato

Re: Foo_record

Reply #30 –
Hello,

I use foo_record with Cosmos ADC as input device.

I get limited to 192k sample rate, but the device can do 32/384.

Is there a sample rate limitation in foo_record ?

Best regards,

n.

Re: Foo_record

Reply #31 –
There is a sanity check for configured sample rate, it must be within legal range that foobar2000 allows. That is, at least 1 kHz and at most 20 MHz.
If I understood Archimago's test of the device, he too couldn't get the device recording working at higher than 192 kHz except in one software and by using ASIO drivers.

Out of curiosity, does foo_record give some error when you try to use higher sampling rate? And did you try both normal and exclusive mode?

Re: Foo_record

Reply #32 –
Quote from: Case on
There is a sanity check for configured sample rate, it must be within legal range that foobar2000 allows. That is, at least 1 kHz and at most 20 MHz.
If I understood Archimago's test of the device, he too couldn't get the device recording working at higher than 192 kHz except in one software and by using ASIO drivers.

Out of curiosity, does foo_record give some error when you try to use higher sampling rate? And did you try both normal and exclusive mode?

Hi Case.

When ADC is configured @ 32/384 in Windows, I can record at that sample rate in Wavelab.

However in foobar recorder is at max at 192k. I guess it resamples automatically the 384k stream.
No error message is displayed.

I tried DirectSound and Exclusive (ASIO?) and both work for recording, 96 or 192k using foobar Converter

Best regards,

n.

Re: Foo_record

Reply #33 –
Just to be clear, did you notice that you can type any sample rate to the dialog? The dropdown is prefilled with some common defaults but you can manually type anything.

Re: Foo_record

Reply #34 –
Hi Case,
Quote from: Case on
Just to be clear, did you notice that you can type any sample rate to the dialog? The dropdown is prefilled with some common defaults but you can manually type anything.
I've just read your message, thank you !  O:)

You're right, I didn't notice what you point out, but it works by typing manually sample rate.
I have to make some more tests, but it seems OK to me

Best regards,

n.

Re: Foo_record

Reply #35 –
I must ask, where do the output files go?

Re: Foo_record

Reply #36 –
Recorded output goes into foobar playback buffer…
If u wanna record to file, use Audacity.
 

Re: Foo_record

Reply #37 –
If you add a record:// source to a playlist and just listen to it, there are no output files. You are simply listening to the recording source in real time.

You can save the recording to an output file with Converter. Remember to end the recording with the "Stop recording" button in Playback menu, not with the Abort button in Converter. Aborting will by default delete the target file.
You are in control of what format is used with Converter and where the output is saved.