VS1053b / VS1103b MIDI Controls

Designing hardware that uses VLSI Solution's devices as slave codecs such as an external MP3 decoder chip for a host microcontroller.
rom3
User
Posts: 3
Joined: Sun 2019-08-25 21:56

Re: VS1053b / VS1103b MIDI Controls

Post by rom3 » Thu 2019-08-29 17:06

Hi again,
I think I got it work. My mistake was that the reverb intensity is global for all midi channels, panning and volume can change separately for each midi channel. I'm right? So I change a little bit the program to set the reverb for each channel separately.

User avatar
Panu
VLSI Staff. Currently on holiday.
Posts: 2715
Joined: Tue 2010-06-22 13:43

Re: VS1053b / VS1103b MIDI Controls

Post by Panu » Thu 2019-08-29 21:27

Hi!

Pasi has written the midi decoder, he will be back soon from his holiday to answer you... :D
Info: Line In and Line Out, VS1000 User interface, Overlay howto, Latest VSIDE, MCU Howto, Youtube
Panu-Kristian Poiksalo, VLSI Solution Oy

User avatar
pasi
VLSI Staff
Posts: 1621
Joined: Thu 2010-07-15 16:04

Re: VS1053b / VS1103b MIDI Controls

Post by pasi » Mon 2019-09-02 15:25

Channel Parameters which affect reverb:
- effect control 1 (0x0c) - controls decay time (global)
- effects level (0x5b) - channel reverb send level (channel-specific, default is 12)

The final reverb amount for a note also depends on the instrument - each instrument has their own "base reverb", and the channel effects level can increase this level.
Visit https://www.facebook.com/VLSISolution VLSI Solution on Facebook

rom3
User
Posts: 3
Joined: Sun 2019-08-25 21:56

Re: VS1053b / VS1103b MIDI Controls

Post by rom3 » Thu 2019-09-05 12:45

Thank you for your explain,
now I got it work. I don't know why I make the 0x5b instruction to 0x58. Need new glasses? But now, I understand the midi parameter a little bit more. You write all in the first treat. Sorry for my silly question.

User avatar
pasi
VLSI Staff
Posts: 1621
Joined: Thu 2010-07-15 16:04

Re: VS1053b / VS1103b MIDI Controls

Post by pasi » Mon 2019-09-09 12:06

Great!

It is always good to double-check how it should work from the actual code, so no harm done.
Visit https://www.facebook.com/VLSISolution VLSI Solution on Facebook

Post Reply