Conversation
…not be cached in a temp dir
… not be cached in a temp dir
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changed
sstvno longer takes anoutput_wavpositional arg (local + server). The WAV path is now derived automatically and cached under<tempdir>/bw_sstv/, based on(image path, mode, image mtime). Re-running the same image+mode reuses the cached file instead of regenerating it (faster).shared/sstv.pynow pulls in grayscale modes (Robot8BW,Robot24BW) alongside the existing color modesmodenow logs a warning and falls back to auto-detect instead of failing silently.Breaking change
Anyone with saved commands/scripts using the old signature:
needs to drop the
output_wavslot:Old invocations that supplied
output_wavwill now have that value parsed asfrequencyand throwValueError: could not convert string to float.