-
Notifications
You must be signed in to change notification settings - Fork 26
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
Import MIDI #43
Comments
Sure! It wasn't on my task list before but it makes sense as a feature so I'll add it. |
Does UTSU accept voicebanks in other types of formats like Flac or MP3? I believe it would be an interesting addition, if this option is not yet available ... |
@titinko , I have a very rough midi parser that understand the basic to create a utau file. The workflow could be: Using musescore, I noticed than the lyrics interface is very, very good. The format of musescore is not difficult to parse (all XML), and the note and lyrics are stored in the same object. It could be a very cool way to import massive lyrics in utsu. Greetings! |
Not too familiar with MIDI, but in the code opening a MIDI file would mean converting it to a Song object similar to what Ust12Reader and Ust20Reader do now. That workflow sounds good to me, although in step 2 it's probably fine to just default to the first track. In terms of UI, either MIDI files could directly be added as a supported format when opening a Song, or there could be a new "Import MIDI file..." item in the File menu. |
So, the MIDI reader should be on com.utsusynth.utsu.files.song package. Sounds fine.
I like the idea of select track like UTAU does. It would be fairly simple to implement, anyway. No dialog is necessary if only one track is available.
Later should be clearer for users, I think. |
Can you use com.utsusynth.utsu.files.song.midi for a namespace? Any small dialogs can be placed inside com.utsusynth.utsu.common.dialog. |
Sounds fine.
Perfect. |
While this is technically not an issue, I realized that Utsu doesn't have an import MIDI feature. Do you mind adding that to a future update if not the next one?
The text was updated successfully, but these errors were encountered: