sequencer to work with mscore
hi guys,
So, as mentioned in lots of posts in the musescore forum real-time midi entry doesn't seem to be implement into musescore so i wonder (as a sort of survey) which sequencer are you using for midi input ? And the reasons why you rather it instead of another.
thanks for testimonies and notices
Comments
I don't think of real time MIDI as an effective way to enter notation. Tried it with various other programs, including Finale and also Notator which was probably the best program ever invented for integrating sequencing and notation, and never found it nearly as efficient as simple step time entry. Except in the very simplest of cases, there is way too much cleanup required to sort out voices, staves, etc. And in the very simple cases where this is not required, step time entry can still be even faster if the input consists of long notes (I don't have to wait four beats before moving on after entering a whole note). I even prefer the computer keyboard to a MIDI keyboard for my step time entry, as that way I don't have to worry about the program guessing wrong about how to spell accidentals.
So as far as I am concerned, if the goal is to get usable notation, real time MIDI input - include via a sequencer - is a step backwards. So a question of which sequencer to use is more a question of asking, how *(big* a step backwards to you want to take. And unfortunately, all of the free / open source sequencers I've seen (for Windows) are a pretty big step backwards. Notator got close to parity by tightly integrating the sequencing with the notation, but the moment you need to use a separate program, create a file, import it, etc - that's another step backwards. And if the UI of that program is not very good, that's possibly several more steps backwards. And unfortunately, I am not aware of any good free / open source sequencers (for Windows, anyhow) that don't feel like several steps backwards in the UI department on top of the other steps backwards always inherent in using a separate sequencer.
That said, I do occasionally have need for a sequencer in situations that have nothing to do with notation. In those cases, I do wish there were better options available. I've played with Sekaiju and use it when necessary, but I don't really like it.
In reply to I don't think of real time by Marc Sabatella
Hi Mark,
Quite a misunderstood about my survey (but it's my fault),
so, I just wonder if someone first compose with a sequencer and then use a kind of export (and which one ? XML ? Midi ? other ?) and import into musescore having the less work and the best result.
The fact is i've tested Cubase 7 a week ago and honestly it's a really good tool to compose because you can use many vsti, but, every compositors using it also use a real score editor software (sibelius in this case and still with VSTi), so I just wonder if there is such workflow in linux world as for the moment, MIDI out doesn't work very well in musescore (specialy with JACK sound server)
Anyway, thanks for your testimony Mark :)
In reply to thanks for your reply by Daeavelwyn
For the record, I didn't misunderstand. I know you were asking which sequencer works best as a way of preparing input for MuseScore. Your question seems to carry an assumption that if you only use the right sequencer, real time MIDI input will become a viable method of note input, better than the regular step time input. I am simply observing that I think your assumption is wrong. I don't care how good your sequencer is, it will never be a better method of creating notated scores than step time input. A good sequencer might be a better way of creating sequences, but it won't be a better way of entering notation.
There are so many options around that it's really hard to say which one is the best one. Moreover, each of us has his own preferred way of "working", so what's great for one may fail for another. That said--
For preparing midi files to import in MuseScore, I like using SIMPLE sequencers, that's to say sequencer with as few features as possible (the fewer, the better, so that the workflow is fast and efficient). My sequencer of choice is the free Logic Fun (not officially available any more).
What I think is really important, is the fact that the midi file has to be fine-tuned in order to provide the best solution for midi import -- using midi files designed for playback is not the best solution at all, and usually leads to bad results.
I prepare as many MONOPHONIC track as are the parts I need (I mean - let's say I have four staves, one of which a piano double-staff with two voices for the upper one; I would prepare 1 track for the first single and monophonic staff, another track for the second single and monophonic track, 1 track for the lower monophonic staff for the piano and 2 tracks for the upper two-voices staff for the piano).
I pay particular attention to the fact that midi notes have to be accurately and precisely quantized. This has to be managed in a maniac-flavour indeed. Notes overlapping is not an option, as it will lead for sure to bad results.
Midi files prepared with notation-import in mind do not sound good. They sound flat and, litterally, robotic. They totally lack of expression, but expression is not what is needed for effectively importing a midi file in a notation program.
That's what I do. I hope my words can be useful.