..........
its actually my bad because i should make this explanation before everything,
top of this topic & in the video description.
(both fixed now)
why i prefer "Chord Relative" midi preparation
first let me say:
to me, there is no import issue in RC.
i just prefer this method with multiple (personal) reasons
(and want to share because i thought might be helpful for sometime / some Reaper users)
but if i have to pick just one reason, i would say:
i need full control (as much as possible) over the materials, in my DAW's (Reaper) comfort.
-i don't want any scale relative notes involved in this case
a- i have to fix them in RC
b- fix them in the Reaper, before import to RC
i prefer 'b' because after i found especially that two
snap to chord and adjust to given octave Actions i mention below
prepare process become really fast in Reaper..
-if i prepare before import :
i can import large number of midi files at once
instead of one by one import & Note Offset (Scale/Semitone) fix..
because no need to harmony recognition..
-also i prefer to correct the note lengths
for example if note lengths comes from sustain pedal as in some piano midi files,
i want that actual note lengths without sustain CC data.
so i am fixing-editing them in the Reaper when necessary.
-i also prefer to split/adjust parts to a fixed lengths .. for example 4 bars
after split to 4 bars i glue them in a single item again and get rid of the all tiny note cuts/bits if there is any left
via just one Action/click easily, at once..
-if there is some short parts in the midi files (1 bar or 2 bars) .. just duplicating them to fixed length i prefer.
-after preparation done, i can import all as a single file to RC and let the RC split to parts i want and save them
again i don't see/think this is an import issue !
its just because of the nature of the complex materials ..
plus because i am a lazy-control freak that always looking for an easiest way
finally, if i made this preparation before import .. i feel Phrase Voicing more steady "to my taste".
(because i am aware of there is no way to import Chord Relative materials as they are..
plus, to me also there is no "1 Right Way" to import them ..
so, to me, there is always a decision have to made eventually)
Short:
all midi files gets,
--fixed lengths
--fixed range (mostly 1 and a half or 2 octave range)
--fixed Chord Voicing
since i know all should be in the same notes (C Major 7 or C Major 9)
i can quickly alter the chord voicings that i didn't like..
for example if there is some machine gun type figures occur after i execute the snap to chord action
i can spread them across to notes according to my taste and fix it before import to RC.
again,
personally i find this method relatively easy than preparing them the in the RC,
and want to share because i thought might be helpful for sometime / someone
end of the EDIT.
............
--i think this should be in here--
recently i get two new Actions and want to share what i am doing with them
(from video description)
Actions & Links & Notes
--- ReaTrak snap midi takes in selection to chords.lua
(Thanks to MusoBob)
https://forum.cockos.com/showpost.php...
--- Transpose selected MIDI items (all takes) to target octave
(Thanks to spk77)
https://forum.cockos.com/showpost.php...
and
SWS: Create regions from selected items (name by active take)
Important Note: about using the
"ReaTrak snap midi takes in selection to chords" Action
after creating the Regions with chord names
before execute the "snap to chord" Action
be sure
- Track of the Midi files must be "Selected"
- also de-select all items in the project if there is any..
- finally make Time Selection with all the chord name regions inside..
then run the Action!
EDIT:
and
just let me know if i skip anything
or if you had questions (because of my rapidly mouse movements
)...
I would love to fix any import issues so that this preparation step is not necessary.
