allow passed in pins for TLV320, volume limit too low #18
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was working on refactoring the new audio API into some of the Fruit Jam apps and realized that for apps that might be run on other boards like the Metro RP2350 with a TLV320 breakout, the library would crash when trying to use the defined I2S pins that the Fruit Jam has. I think we may have the same issue if we try and use the library's screen API but I didn't look closely at that. (maybe the Metro RP2350 has the same DVI pin names so at least that board would work)
This is the Fruit Jam library so I understand if we don't care that it doesn't work on other boards in which case I'll just stick to using the TLV320 library for Apps that may run on other boards.
I also found that the new volume settings were too soft. I set the default safe_volume_limit up to 17. The old value translated to -11.4dB and the 17 translates to about 10 which I found was still not loud on both headphones and the speaker. I'm going to also open an issue about the volume level so if you would like me to drop that change from this PR for now I can do that too.