bkshepard

I have a delay line in a patcher that uses the tapin~/tapout~ combination. Whenever I change sample rate, I get the following error message in the Max window:

tapout~ sampling rate does not match tapin~

I did find references to this in the 2002 forum, but it sounded like it would be fixed long ago. Is this still a problem?

I have a delay line in a patcher that uses the tapin~/tapout~ combination.  Whenever I change sample rate, I get the following error message in the Max window:

I did find references to this in the 2002 forum, but it sounded like it would be fixed long ago.  Is this still a problem?


tapout-sampling-rate-does-not-match-tapin

bkshepard wrote on Fri, 20 March 2009 18:57

i am not the one to comment if that can be considered 

a "bug" or is somehow a natural result of changing the samplerate, but wouldnt a "clear" message to the tapin~, triggered by changes to system rate as indicated by dspstate

bkshepard wrote on Fri, 20 March 2009 18:57I have a delay line in a patcher that uses the tapin~/tapout~ combination.  Whenever I change sample rate, I get the following error message in the Max window:

I did find references to this in the 2002 forum, but it sounded like it would be fixed long ago.  Is this still a problem?

i am not the one to comment if that can be considered 
a "bug" or is somehow a natural result of changing the samplerate, but wouldnt a "clear" message to the tapin~, triggered by changes to system rate as indicated by dspstate
already solve it?


That's an interesting suggestion. Perhaps I'm doing it incorrectly, but it seems that the change in sample rate gets reported to tapin~ before it can even get the clear message triggered by dpstate~.

That's an interesting suggestion.  Perhaps I'm doing it incorrectly, but it seems that the change in sample rate gets reported to tapin~ before it can even get the clear message triggered by dpstate~.


 from back in 2002. Is it still a problem?

I found this thread from back in 2002.  Is it still a problem?


This would only be a problem if you'd want to change sample rates on the fly. A simple reinstantiation of the tapin~/tapout~ or a reload of the patch should solve it.

This is a guess, but tapin~/tapout~ need to determine the times according to the sample rate. If they do this only on instantiation, it is probably way more effective. I don't see a problem here and would not want to sacrifice performance for something unimportant...

If you really want to change sample rates on the fly, just script replace your taps on the fly and you should be fine...

This would only be a problem if you'd want to change sample rates on the fly. A simple reinstantiation of the tapin~/tapout~ or a reload of the patch should solve it.
This is a guess, but tapin~/tapout~ need to determine the times according to the sample rate. If they do this only on instantiation, it is probably way more effective. I don't see a problem here and would not want to sacrifice performance for something unimportant...

I don't know that it's even a problem. It's just that when I get an error message in the Max window I start wondering. I'm not actually changing sample rate on the fly, but after stopping audio. It just seems to be a quirk that is more cosmetic than anything from what I can tell. Thanks again.

I don't know that it's even a problem.  It's just that when I get an error message in the Max window I start wondering. I'm not actually changing sample rate on the fly, but after stopping audio. It just seems to be a quirk that is more cosmetic than anything from what I can tell.  Thanks again.
