Skip to content

Conversation

pull[bot]
Copy link

@pull pull bot commented Sep 10, 2025

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.3)

Can you help keep this open source service alive? 💖 Please sponsor : )

tanakamasayuki and others added 30 commits May 15, 2025 12:23
Added initialization time for UART, etc. Default value is 0.
Add function definition and SET_SETUP_WAIT_TICH function
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
This PR will allow the user to modify the MIDI USB Device Name (device descriptor). Fomer API continues to be valid and the default device name is "TinyUSB MIDI". The user can change the device name by passing a string to the constructor, declaring it like this `USBMIDI myMIDI("MyDeviceName");
The problem affects more often SoC that supports REF_TICK UART Clock source (ESP32 and ESP32-S2). The implementation has an issue retated to when the user doesn't set any specific UART source clock and the UART changes its baudrate from lower than 250,000 to higher (ESP32/ESP32-S2). The bug is about not changing the clock source to something faster (APB) in order to get correct clock resolution in order to reach closer enough to the new baudrate selection. The new behaviour (which was working before) is that is the application doesn't set any specific UART clock rate, it shall follow a rule: ESP32/ESP32-S2 will use REF_TICK whenever baudrate is lower than 250,000. Other SoC will use XTAL. ESP32/ESP32-S2 will change UART Clock Source to APB when baudrate is higher than 250,000 for a better final result. If the user application explicitaly changes the UART Clock Source using `setClockSource()`, this new clock source will be used always, independently from the target SoC and selected baudrate (overriding the rule above).
Adds a new function `rmtWriteLoopingCount()` to send a specific number of times, repeating the same RMT Symbols.
Adds: bool rmtWriteLoopingCount(int pin, rmt_data_t *data, size_t num_rmt_symbols, uint32_t loop_count) It will send a pattern defined by `*data` RMT Symbols for `loop_count` times (repeated). This is different from `rmtWriteLooping()`, which will repeat it for ever (endless looping).
Updated MIDI device initialization to use default constructor.
SuGlider and others added 27 commits September 9, 2025 10:46
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
feat(core): Add wait time before setup
feat(usb): allow the MIDI constructor to define a device name
fix(uart): always applies the user selected UART Clock Source
feat(rmt): adds new function to send specific number of loops
…eaders feat(HTTPClient): add support for collecting all HTTP headers
ci(pre-commit): Comment when fixes are needed
@pull pull bot locked and limited conversation to collaborators Sep 10, 2025
@pull pull bot added the ⤵️ pull label Sep 10, 2025
@pull pull bot merged commit 56842da into Stars1233:master Sep 10, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

5 participants