Posted
When importing MIDI file, there should be a item or track #, the MIDI channel it's on, and the choice of also converting that MIDI channel to another. (but also still keep the retain MIDI channel command)
I, like many always put basic tracks on the same MIDI channel to make life easier. I know you can convert it later.. But doing it in import streamlines the process. Then your import device could already have a proper MIDI channel template set up.
Mon, 2013-03-25 - 10:53 Permalink
By assigning a target sound to the track, you already also assign its channel (if it is a fixed-channel sound).
Mon, 2013-03-25 - 17:08 Permalink
Thanx. This is another example of SFP's 'obtuse' programming.. That is not intuitive. Mac programs are generally known for the ability for one to figure something out without referring to the manual..
I know this is a small issue, but the more obvious, the more reduntancy a program, has the easier it is to use.
Mon, 2013-03-25 - 17:55 Permalink
This could as well be considered the opposite, a very good example of Mac-like intuitive operation: Instead of figuring out which sounds are currently patched to which channel, you simply point the track to the sound you want. Done ;-)
Mon, 2013-03-25 - 21:39 Permalink
Yeah I like that. For me, after many years of playing, it's about the sound pallette you use. The 'color' or 'tonal character' of the instrument patches you are using GREATLY affects what notes, lengths and velocities you can use to create a certain feeling.
Lately in Logic I have suprising myself about how many 'wrong' notes you can put on the 'and' (mostly on 16th notes) of the beat.. Use of velocity and length, articulation, timing, and filter open a flood gates of possibilities. By doing this you change the attitude of the song, It even begins to imply a different chordal or modality structure..
I can see/hear this effect in SFP too. It's wonderful for creating 'hues of ambiguity'.