"In the morning on an empty stomach"
"Hypocritically"
"With a lot of difficulty"
“With conviction and a rigorous sadness”
“With a healthy superiority”
“Don’t eat too much”
“Shake like a leaf”
“Do not cough”
“Go away”
“Like a nightingale with a toothache”
x.ugly_hack=blah <- “With conviction and a rigorous sadness”They all allow different amounts of precision and interpretation of the performance. Staff notation is open to interpretation on the performance level. MIDI is an exact recording (or programming) of a performance.
With staff notation you can mark eighth notes and say "staccato, lag behind the beat", and there's an infinite number of subtly different ways to play it, even within the own composers interpretation. With MIDI, it would represented as "Note on A3, 12 pulses after first quarter note, velocity of 87. Note off A3, 54 pulses after first quarter note, velocity of 0. Note on C3 (etc....)". MIDI is great for computers (or routing signals during live performance) because it's exact.
MIDI is a pretty exact specification. If a sequencer is changing the timing of anything, the underlying MIDI structures are not the same then. You can have different amounts of swing or different PPQ values, but then I wouldn't consider that "the same MIDI".
You can feed it to different sound generators of course, different drum machines, synths, a laptop, what-have-you, (most sequencers have both builtin together) but that's different from the MIDI itself.
Given a specific MIDI file, with specific applied quantization, they should absolutely play the same way -- the only exception is the timing resolution they offer and smallish latency issues (which in practice should be 100% transparent).
Most classically trained players do too.
Besides we have much more control over step sequences than you probably think, e.g.
http://www.steinberg.net/en/company/technologies/vst_express...
Plus, of course, tons of CC, etc.
Compared to the possibilities for expression in step sequencing, something like a piano, which basically just has velocity and sustain/dumper is not even close.
I think you mean "dense and efficient".
I've understood that for a large category of adult learners, when starting on an instrument for the first time in their life, it's the staff notation that creates an usurmountable barrier. So, yeah, it's not definetly 'easy' for most beginners.
Musical keys are "mathematically" interchangeable. The physical keys that correspond to notes not in the key of C major (alternatively, A minor) are colored black for practical reasons. That is, for knowing one's place while playing the piano.
Fortunately I sorted this out in college, and I've enjoyed making music for my own enjoyment since.
I wish we had pianos with slightly thinner keys (to allow for the same reach) but with same-level black and white keys.
It would make piano playing normalized (like e.g. bass playing is), and make learning scales, transposing, etc childs play.
It would probably still need some color or small "bump" on C to know where our hands are, but that would be it.
Of course there are also several hexagonal etc keyboards with similar normalized layouts, but they also haven't caught on.
Take a tune, and now arrange some graph paper like the "note pattern view" in a sequencer, with one difference. Instead of arranging the pitches in the normal way, arrange them by the order they come in the tune. (so the first note of the tune will be the "lowest" pitch, second note the second "lowest" and so on.
You might see some interesting things that you didn't hear!
Probably Mozart would be a good target to do this with, and pop music would not, but I could be wrong on that. Possibly this is over your head, but possibly not.
Then if you want to add a ton more formalism, read a little about serialism, and apply this technique to a twelve tone piece. You will be rewarded for your efforts, as a previously difficult to follow piece makes much more sense. Doesn't mean you'll find it pleasing to listen to though.
Homepage: http://composerssketchpad.com
I've been a Mac user for almost ten years now, but the lack of FLStudio for OSX makes me question that decision every six months or so.
But apart from that, you can do the same things (although less builtin tooling for electronic music, but still enough) with Garageband, and, if you don't have invested in VSTs/AUs, Reason.
Most other DAW's have caught up with their piano roll implementation but I still like FL's the most. I think what makes it unique is its toolset -- as in, the toolbar up top -- as its modal editing workflow lets you add, delete, and then transform notes incredibly quickly. Most of these modes have a shortcut to get to them, and its easy to flip between them. It even has a chord option, which functions much in the same way as that hook tool. Other DAWs take a modal approach but in many cases they complicate their implementation.
It's also worth noting that FL is pattern-based, whereas most DAWs are not. ("Pattern-based" means you generally write music phrases/patterns and repeat them throughout the track, this is helpful for electronic dance music.) A repeating bassline pattern in FL is more akin to a series of symlinks back to the original file, whereas in Cubase and Logic, each of these repeats would be copies (unless you specify otherwise, but I found the implementation convoluted and troublesome.)
Most of the other DAWs I've worked with are much more fiddly and require messing with technical details and audio routing to get a good result. FL also requires this, but again the implementation is seamless, has sensible defaults, and stays out of your way until you need to mess with it. (In the middle of a good flow I have very little patience for routing.) I do not find this to be the case with Live, Cubase, or especially Logic... I put in an effort to learn each of these at some point and ultimately left to return to FL.
I've noticed DAWs tend to optimize around performances (Live), MIDI orchestration (Cubase, Logic), recording (ProTools, Reaper) or 'in-the-box' production (FL). All of the above have tools for composing by mouse but FL's workflow is optimized for this specific use-case.
[1] Great studio guitarist Glen Campbell supposedly couldn't read music at all, just went along with what he heard and made it work; Tommy Tedesco by comparison could read sheet music upside down.
Joni Mitchell apparently didn't even use regular tab notation. She'd detune her guitar and annotate the relative pitch shift per string, e.g. D-2 G+1, etc or similar.
But of course, up to a point, lowering barriers is always a good thing for beginners.
Here's a screenshot I took of a random song in TuxGuitar (a GNU licensed tablature editor/viewer). You can see the rhythm fairly clearly, as well as the difference between pull-offs and slides.
There's a huge jump in the complexity of how you need to reason about translating the music to the instrument with staff notation. Tabs solve this by explicitly telling the musician what fingering to use.
Guitar players should still learn to read music because it's useful, but anyone who wants a guitarist to play their music (especially by sight) should use a notation similar to tabs, but with rhythm indicated as well. Good software to convert between the two could be generally useful, but I imagine there is a bit of nuance to what fingerings sound the best.
Nothing has been "denied to you". You just haven't spent the time it takes to learn. Have foreign languages been "denied to you", too?
What, precisely, is ridiculous about music notation? It represents time, on the x axis, and pitch, on the y axis (on a basic level). Seems reasonably logical, to me.