VSDSP Forum

The B in vs1003b is the firmware version indicator. You can guess from B that there has been a private vs1003a prototype before the vs1003b production version. The DAC FIFO is 2048 stereo samples, the SDI FIFO is 1024 words. See http://www.vsdsp-forum.com/phpbb/viewtopic.php?f=11&t=1463 For smaller ...

Hi, It seems to refer to the "Connecting SPI Buses" (vs10XXan_spi.pdf) from http://www.vlsi.fi/en/support/applicationnotes.html . Mostly, you have to reserve GPIO pins for all of the chip select signals. Also, you should note that SD/uSD cards connected to the same SPI bus might produce issues, beca...

A better version of the pitch shifter is available for VS1005.

The original version: http://www.vsdsp-forum.com/phpbb/viewto ... =13&t=2092
And later integrated into the regular distribution (see the link in the second post of that thread).

It sounds like that's what that specific algorithm can accomplish. The difference between speeding up and slowing down is that when speeding up, the playback plays everything only once (uses windowing to play two portions at the same time to "compress" the playing time), while when slowing down the ...

Can you record a short piece of what it sounds like? It might give us some more ideas.

Does it happen with all files? Can you attach or send to support the one you use?

The top two reasons for "hickups" are:
1. The clock is not high enough to decode when you speed up tempo or pitch shift higher.
2. You are not providing the audio data quickly enough to SDI.

Can you monitor DREQ?

Cocoa wrote: ↑

Fri 2020-11-13 3:25

the volume changes a lot, besides, it doesn't play fluently, accompanied with noise.

What kind of noise? What you hear could be just due to the very simple (and old) pitch-shifting algorithm.

You should not write to AUDATA. The samplerate is determined from the audio file you send.

Do you have issues when you speed up the tempo or when you slow down the tempo?

Sorry, I'm not familiar with the mp3 shield. Googling got me to where you are, i.e. found the documentation of the getTrackInfo() function, but not how to open/set the filehandle for it (without playing the file). It would apparently require digging deeper into the library source code.

Great that you had that resolved!