While working on a sample player, I noticed that the sample sounded slightly different when played through Audacity and when played through my Pd patch. It's hard to notice the difference (unless you have perfect pitch, which I don't), but when played through Audacity, it has a slightly higher pitch. If you play them both at the same time, the difference is obvious.

So I extracted just the essentials from my patch to illustrate. I don't know if I'm doing something wrong in my patch, but I don't see any problem. I used Audacity to create the sample in the first place, which is exactly 44,100 samples long, at a sample rate of 44,100.

Anybody see any problem with my patch?

Patch: https://drive.google.com/file/d/151cvF_9_4ViebScR_zOS-IRaQXok0XIJ/view?usp=share_link

Sound file: https://drive.google.com/file/d/18UyB1o6mOfS1oW2OhIUtpA1KdJhHBTm9/view?usp=share_link

I'm going to create another file in Audacity at a SR of 48000, then try playing it back at 48000 in both. Maybe I'll have better luck. I'll also try using a different driver (audio host?) in Audacity.

@dfkettle said:

Gotcha. I changed the SR to 48000 and now the test shows exactly 1000 ms.

... which, to be clear, has nothing to do with the original problem.

I know that, but I thought maybe the CPU might be too busy and the data wasn't being sent to the audio interface fast enough.

If that's the case, then there would be noticeable glitches in the audio. If the outgoing signal is smooth, then all of the blocks of samples are being delivered on time.

I'm going to create another file in Audacity at a SR of 48000, then try playing it back at 48000 in both. Maybe I'll have better luck.

At this point, I'm pretty well satisfied that Pd's behavior is fine, and your patch is doing the right thing. So the real point of this test is to find out the boundaries of Audacity's correct behavior, not really anything else.

hjh

@ddw_music said:

At this point, I'm pretty well satisfied that Pd's behavior is fine, and your patch is doing the right thing. So the real point of this test is to find out the boundaries of Audacity's correct behavior, not really anything else.

Likewise, although I'm a little surprised, given that Audacity has been around for so long, and since I'm playing back at the same sample rate no interpolation is required. It's just sending the sample data in blocks to the audio driver or host. Maybe something to do with the latency setting? I'm just letting it default, I've never played around with it before.

So I tried a three-way comparison. I played the file back in Audacity, my patch and WIndows Media Player. None of them matched, they all varied in frequency, although Audacity and WMP came the closest to matching. Any thoughts on that?

@dfkettle That's unfortunate.
Maybe try Asio4All...... https://www.asio4all.org/....... as a universal driver for Pd and Audacity.
It will have a settings window...... individual for each application..... so try to keep them as identical as possible.
It will give you lower latency and allow you to use multiple soundcards so it can be useful anyway.
David.

@dfkettle what does the 'playback' tab look like for them?

@dfkettle said:

So I tried a three-way comparison. I played the file back in Audacity, my patch and WIndows Media Player. None of them matched...

It seems, if you want them to match, that using a different operating system may be the only solution.

I know, that's a terrible answer... but "terrible" is also a kind word to describe the utter disaster that is professional audio in Windows.

How about this: Record your Pd patch to a disk file, and measure the number of samples between soundfile attacks (or phasor jumps). This will either match the sample rate (assuming the 1 Hz cycle) or it won't.

If it does match (give or take one sample, due to fp rounding), then you know definitively that Pd is producing a correct sequence of samples and the situation in your patch cannot be improved. At that point, it's irrelevant that Audacity and WMP are wrong -- evaluating the worth of a correct result, against other software's incorrect behavior, is not useful.

If it doesn't match, then it would be a bug report. But I'm quite confident that won't be the case.

hjh

@whale-av said:

@dfkettle That's unfortunate.
Maybe try Asio4All...... https://www.asio4all.org/....... as a universal driver for Pd and Audacity.
It will have a settings window...... individual for each application..... so try to keep them as identical as possible.
It will give you lower latency and allow you to use multiple soundcards so it can be useful anyway.
David.

I don't think that's an option for Audacity, at least not under Windows. It uses PortAudio for all three "hosts" (MME, Windows DirectSound or WASAPI), as you can see in the screen capture above. I have to confess that I don't really understand the difference between audio "host" and "driver", though, as they're called in Audacity. Maybe there's a way to tell Audacity to use ASIO4All, but I don't know how. I already have ASIO4All installed, I use it with other programs.

@dfkettle Sorry...... I see Audacity has to be recompiled to use ASIO.
That's unfortunate too...
David.

possibly related? idk: https://github.com/pure-data/pure-data/issues/1998