Yep, you're right. I don't know why these didn't show up when doing a search within Xcode. I had to use BBEdit to find them instead. Commented them out, and built. Thx.

I'm using the latest Nightly build (cog 0.08 r1934) because it fixes a bug I was experiencing. But it writes to the log a lot. I can't find the NSLog / printf calls responsible for this, so I assume they are in frameworks where I can't see the code. Is there any way to solve this or do I just have to wait for a later build that removes the logging? Thx.

3

(3 replies, posted in General)

Cool. Feature suggestion: maybe Cog could have a kind of little red light that comes on when this happens? The reason is that sample rate conversion is a kind of skanky process, so if I'm playing a 48 kHz file I'll get better sound by swithing my USB device to 48 kHz, avoiding the conversion. But I'm not normally conscious that the conversion is happening, so I'm thinking maybe Cog could help by alerting me. smile Thx!

4

(3 replies, posted in General)

This question is about sample rates - e.g., 44.1 khz or 48 khz (don't confuse this with bitrate).

I listen to Cog on a Mac OS X machine through a USB A/D converter (a Tascam device) which can be set to 44.1 khz or 48 khz. Cog sounds just the same through either setting, no matter whether the file has a 44.1 or 48 khz sample rate. In other words, even if the file sample rate and the USB device's sample rate don't match, everything is fine.

My question is - why? Is Cog performing a sample rate conversion behind the scenes? Or is the system somehow performing the conversion?