-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
small issues with midi plugout #20
Comments
D'oh: The number part of the filename is the subsong number, so we can't increment it for subsequent exports. |
task 1 fixed with e1872f6 |
task 2 fixed with 729d1f8 (documentation only, no changes) |
@ranma Two plugouts (iodumper and midi) don't implement the write callback because they don't need it. In the midi output this also manifests as the global volume being empty in the status line during conversion, while the per-channel-volumes are displayed correctly. What should we do?
What do you think? |
Thanks! |
Checking out issue #19 I ran the midi plugout for the first time in a long time and found some small issues:
gbsplay -o list
says MIDI sound driver but it is a file writer likestdout
. This should be a simple rename.gbsplay-1.mid
. When you run it again, that file is silently overwritten. We should either output a warning, disallow the overwrite or sequentially name the output files (there is already a-1
in there, so using-2
and so on should not be too surprising to the user).gbsplay -o midi examples/nightmode.gbs
, output stops after 2 seconds because gbsplay runs into the default silence timeout.-T
has to be set to export more than 2 seconds. I'd guess silence detection does not work because no waveform is generated.The text was updated successfully, but these errors were encountered: