-
Notifications
You must be signed in to change notification settings - Fork 146
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
Fully non-interactive work-flow #50
Comments
The most difficult design question here is figuring out the syntax the CLI argument. Currently there is some guess-work, based on the number of parameters given. Ideally the syntax could be made more flexible by introducing name parameters, like There are several libraries that make things like this very easy... but if we really want to avoid adding any dependencies, it's also possible to it manually... |
Yes, in my fork you can run sth like this to render the individual frames. ("State" is the configuration file.)
Or you can omit the directory and pipe the raw video stream into ffmpeg to render a video file:
If you are working with MuseScore/MusicXML files: bemuse uses this internally to export a MSCZ file to PDF, MIDI, MP4 etc. and also has nicer command line arguments. |
Yes, I have already integrating the fork into my workflow. Actually, I have a simpler command:
Actually, I see two challenges with the fork:
I will check out bemuse later. I am using MuseScore, but not for the current project. For this, I am using live MIDI recordings.. |
It’s possible I accidentally screwed up the pre-roll setting as I’m not using it. As for the key coloring, yes, this would have to be undone manually (maybe you could revert some of the commits on my fork, or just check out an older version where the key coloring was still unchanged, and cherry-pick the stdout rendering).
|
Nah. I just created a small MIDI pre-processor, so that I can use your version as-is, without making any changes to the code, but still get the result I need. |
Hello to both of you! First of all a huge thanks for your suggestions and solutions, and your assistance with the Github issues! |
Hi @kosua20! I took a bit of a pause from generating music videos, but now I am back. I have recently tested this, and it works wonderfully! |
I would like to integrate MIDIVisualizer into my automatic workflow for creating educational videos based on MIDI files. Basically, I would like to use it is a filter within a scripted workflow: the MIDI file comes in, and the rendered images come out.
Currently, I have to manually open the MIDI file, then manually load the settings, set the image size (via setting window size), set the FPS, then start the button for offline rendering, select the directory, etc.
Ideally, I would like to specify all of these either as command like arguments, or as part of the settings file to load. (And then the name of the setting file should be added as a command line argument.)
When running the app in this mode, the GUI shouldn't even be shown; just execute the task at hand, and then exit.
What do you think about this? Would you accept a PR that enables this?
The text was updated successfully, but these errors were encountered: