Billy86
Max Output Level: -83 dBFS
- Total Posts : 362
- Joined: 2015/03/06 16:03:26
- Location: Seattle
- Status: offline
Newb needs help with editing midi events
Situation: I'm trying to insert a sustain pedal "off" then "on" command in the MIDI events viewer because I've got a Gm chord sustaining from its sustain pedal command, and running under the next chord, a C Major. (see images in dropbox link). One is the PRV image, and the other is the Event Viewer. I replicated what's working with the other pedal "on" and "off" instances you can see in the Events viewer pic. My problem areas are marked in red. I inserted a sustain pedal "off" after the Gm chord in the Events viewer to try and make it stop, then added an "on" pedal event before the C chord, but Sonar doesn't seem to be reading it. The Gm stays sustained, while the C chord plays on top of it. Not pretty. Can anyone tell me if I'm missing something? Here are the screenshots: https://www.dropbox.com/s...njv0lF20fKD53WSba?dl=0 Thank you!
Windows 10 x64 on a Dell/Intel i5, 500 Gig SSD, 32 gig RAM, Focusrite Scarlett 2i4, Sonar Professional, Melodyne 4 Assistant, Kurzweil SP-76 stage piano, Baldwin RP 100 digital upright, Novation Impulse 25, Breedlove Pursuit Concert Acous/Elec, Fender American Standard Tele, Fender G-DEC 30 modeling amp, Sigma DM-5 Acoustic, Ovation MCS148 Celebrity Acous/Elec. Mandolin, Roland V-Drums TD-11KV, AKG P220, Yamaha MG82CX mixer, KRK Rokit 6 Powered Monitors, PreSonus FaderPort
|
bvideo
Max Output Level: -58 dBFS
- Total Posts : 1707
- Joined: 2006/09/02 22:20:02
- Status: offline
Re: Newb needs help with editing midi events
2017/02/07 01:34:33
(permalink)
Looks like the durations of the notes all continue past the sustain off & on. E.g. the pedal goes on 1:066 after the first note starts, but the first note has a duration of 1:099, so it is still held at that time, so it gets sustained. So move the sustain events a little later or shorten the notes. Assuming the notes are all responsive to the sustain, they don't need to be held so long.
W10 pro, Sonar Platinum, Alesis Multimix 16 FW, MOTU Express 128, Gigabyte Z370 HD3P, i7 8700K, 16 Gigs, ssd + 2 X 2T disks, D50-MEX, JV80, A90EX, M1REX
|
Billy86
Max Output Level: -83 dBFS
- Total Posts : 362
- Joined: 2015/03/06 16:03:26
- Location: Seattle
- Status: offline
Re: Newb needs help with editing midi events
2017/02/07 09:25:31
(permalink)
Thank you. I'll give it a shot.
Windows 10 x64 on a Dell/Intel i5, 500 Gig SSD, 32 gig RAM, Focusrite Scarlett 2i4, Sonar Professional, Melodyne 4 Assistant, Kurzweil SP-76 stage piano, Baldwin RP 100 digital upright, Novation Impulse 25, Breedlove Pursuit Concert Acous/Elec, Fender American Standard Tele, Fender G-DEC 30 modeling amp, Sigma DM-5 Acoustic, Ovation MCS148 Celebrity Acous/Elec. Mandolin, Roland V-Drums TD-11KV, AKG P220, Yamaha MG82CX mixer, KRK Rokit 6 Powered Monitors, PreSonus FaderPort
|
Billy86
Max Output Level: -83 dBFS
- Total Posts : 362
- Joined: 2015/03/06 16:03:26
- Location: Seattle
- Status: offline
Re: Newb needs help with editing midi events
2017/02/07 11:54:43
(permalink)
bvideo
Looks like the durations of the notes all continue past the sustain off & on. E.g. the pedal goes on 1:066 after the first note starts, but the first note has a duration of 1:099, so it is still held at that time, so it gets sustained. So move the sustain events a little later or shorten the notes. Assuming the notes are all responsive to the sustain, they don't need to be held so long.
Confused. Sorry. Tried to get it to work, but still can't. I tried to adjust the Gm note lengths, and/or the sustain timing, and what's happening is that the notes continue to sustain or cut off too early (before the C chord starts). Obviously (I assume) because I'm not doing the math right down to the "tick" level or something? Not sure which columns/numbers to work with exactly. To that end: the orange-colored pedal sustain events in the Viewer. I'm watching the PRV timeline and following along in the Viewer as it tracks what's happening in PRV, and it seems like the sustain on/off events that come AFTER the various chords are the ones highlighted during the chord, implying those "post-chord" events are the sustain controllers for the PREVIOUS chords. Is this right? "Looks like the durations of the notes all continue past the sustain off & on. " Yes. "E.g. the pedal goes on 1:066 after the first note starts..." How did you determine this? Which column of numbers holds this key? Thanks for the help!
Windows 10 x64 on a Dell/Intel i5, 500 Gig SSD, 32 gig RAM, Focusrite Scarlett 2i4, Sonar Professional, Melodyne 4 Assistant, Kurzweil SP-76 stage piano, Baldwin RP 100 digital upright, Novation Impulse 25, Breedlove Pursuit Concert Acous/Elec, Fender American Standard Tele, Fender G-DEC 30 modeling amp, Sigma DM-5 Acoustic, Ovation MCS148 Celebrity Acous/Elec. Mandolin, Roland V-Drums TD-11KV, AKG P220, Yamaha MG82CX mixer, KRK Rokit 6 Powered Monitors, PreSonus FaderPort
|
bvideo
Max Output Level: -58 dBFS
- Total Posts : 1707
- Joined: 2006/09/02 22:20:02
- Status: offline
Re: Newb needs help with editing midi events
2017/02/07 17:12:47
(permalink)
☼ Best Answerby Billy86 2017/02/07 19:29:05
The start time of each event is in the 3rd column, in Measure:Beat:Tick format. The duration of each note is in the far right column, also in M:B:T (or B:T). The value column shows either your note numbers or your sustain values (0 for off, 127 for on in your screen shot).
So the first G6 starts at measure 89, the first beat. It is held until beat 2 tick 99 (1:000 plus 1:099). Meanwhile, the sustain pedal is 'On' (value 127) at tick 66 of beat 2, i.e. before the key is let go at tick 99 of beat 2. Therefore, the sustain pedal is directing that note to sustain (until the next sustain 'off' in measure 91). The "1:066" is just by arithmetic, tick 66 of beat 2 is one beat and 66 ticks after the G6 at the first beat of the measure.
The exact response of notes that cut off vs. sustain will depend on the note durations, the sustain 'off' time (value 0), and the sustain 'on' time. A 'tick' is a fraction of a beat, either 1/960 or some other value configurable by you.
W10 pro, Sonar Platinum, Alesis Multimix 16 FW, MOTU Express 128, Gigabyte Z370 HD3P, i7 8700K, 16 Gigs, ssd + 2 X 2T disks, D50-MEX, JV80, A90EX, M1REX
|
Billy86
Max Output Level: -83 dBFS
- Total Posts : 362
- Joined: 2015/03/06 16:03:26
- Location: Seattle
- Status: offline
Re: Newb needs help with editing midi events
2017/02/07 19:29:11
(permalink)
Thanks for your explanation! I got it figured out. I could tell it was math-based, but I didn't know what all the numbers meant, which represented what, and which to calculate with. I see now where my sustain ran over the start of the next chord, and got things back in align. Thanks again, bvideo!
Windows 10 x64 on a Dell/Intel i5, 500 Gig SSD, 32 gig RAM, Focusrite Scarlett 2i4, Sonar Professional, Melodyne 4 Assistant, Kurzweil SP-76 stage piano, Baldwin RP 100 digital upright, Novation Impulse 25, Breedlove Pursuit Concert Acous/Elec, Fender American Standard Tele, Fender G-DEC 30 modeling amp, Sigma DM-5 Acoustic, Ovation MCS148 Celebrity Acous/Elec. Mandolin, Roland V-Drums TD-11KV, AKG P220, Yamaha MG82CX mixer, KRK Rokit 6 Powered Monitors, PreSonus FaderPort
|
bvideo
Max Output Level: -58 dBFS
- Total Posts : 1707
- Joined: 2006/09/02 22:20:02
- Status: offline
Re: Newb needs help with editing midi events
2017/02/07 20:24:39
(permalink)
W10 pro, Sonar Platinum, Alesis Multimix 16 FW, MOTU Express 128, Gigabyte Z370 HD3P, i7 8700K, 16 Gigs, ssd + 2 X 2T disks, D50-MEX, JV80, A90EX, M1REX
|