Hi!
Some midi import questions. I get wrong interpretation /grid for my midi import. This: imported is this: then intepreted like this: How to I get this right? Notion 4 x32, imported from Reaper
Last edited by geirsolerd on Thu Nov 20, 2014 7:49 am, edited 1 time in total.
|
And
for D major I have to manually correct all Db to C# Is there a way to get there automatically? |
geirsolerd wroteHi! Before export first carefully quantize all the _Note-on AND Note-off_ events to what you know to be correct. Notion will then do a reasonable interpretation. Timing in the world of notation is exact. So the imported data "must" be very close if not right-on what you expect the notation to be. The "Key Signature" information should be embedded in the MIDI file. Reaper most likely has a preference setting for key signature. ,Newberry |
johnnewberry wrotegeirsolerd wroteHi! |
Thanks!
johnnewberry wroteBefore export first carefully quantize all the _Note-on AND Note-off_ events to what you know to be correct. Notion will then do a reasonable interpretation. Timing in the world of notation is exact. So the imported data "must" be very close if not right-on what you expect the notation to be. Well, you see exactly the midi in img#1. It's quantized to 1/16
Actually not. Reaper has very little on key-signature -and no score-view. Just piano-roll. Maybe I should import it to Sonar first then? |
Hmm. Opened in Sonar X3, loaded and converted fine.
Both quantization and key-setting. Exporting was harder MusicXML and MIdi0, Midi1 failed to open in Notion and Reaper. Will try Studio One |
Hmm.. same with Studio One.
Don't understand.. |
geirsolerd,
I also am having problems with "key-signature" changes imported into Notion from the SMF format (Standard MIDI Files). I can export a SMF from Sonar x2 that has "key-signature" Metadata embedded into it. (I added (4)four changes for my test.) Notion only recognized the last "key" change in the MIDI file. When the same file is imported into Sonar x2 all of the key-signature changes are present (recognized). So, it seems Notion does not read all of the "Metadata" in SMFs. Notion also does not export MIDI Metsdata. Also, neither Studio One or Reaper seem to export key change Metadata in there SMF exports. These are important features that should be addressed. PS. Again, quantizing the note-on and note-off event times carefully! before exporting MIDI files from a DAW or MIDI Sequencer greatly improves the notation accuracy of imported MIDI files in Notion. ,Newberry |
Thanks!
Seems like I did an error on import to Notion. Used open instead of import. Now it's fine. Just some other issue (new post) |
I use Studio1 artist 3 to sequence with midi controller, then go back and quantize everything perfectly. Then I export by sending to notion6 under menu <song "send to notion". It opens a file in notion in the key of c. All the notes are correct tones( with the exception of some missing despite perfect quantization.
My problem is that when I try to add the key signature in notion by dragging a key signature onto the first bar of the score. All notes remain correct tones but my G# all read Ab. I've also tried >edit > select all > transpose > same octave> up major third." but then whole melody is shifted. i can find one means of setting key signature in studio one before transporting to notion and that is via the edit window for individual vr tracks. One can select the scale there. It only seems to aid note input though and does not transfer to notion. Did you ever find a solution? |
Users browsing this forum: No registered users and 12 guests