128x128 and 320x320 framesizes added to support ESP32 v.3.1.3 for Arduino #47
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.
It actually took me a lot of hours to trace this bug down to the

framesize_t
enum change in the new version of the esp32-camera library when I first saw a strangely interlaced and stretched video instead of a usual 640x480 frame.I hope this small fix saves someone else's time.
Please see this header for reference: