ba_midi
Max Output Level: 0 dBFS
- Total Posts : 14061
- Joined: 2003/11/05 16:58:18
- Location: NYC
- Status: offline
X1B mute/solo comment
I'm noticing a LOT more "stuck" notes in X1B after muting or soloing a track or tracks. This has always been an issue in Sonar, but more pronounced in X1B. I'll live with it. But it's annoying.
|
Dave Modisette
Max Output Level: 0 dBFS
- Total Posts : 11050
- Joined: 2003/11/13 22:12:55
- Location: Brandon, Florida
- Status: offline
Re:X1B mute/solo comment
2011/03/21 19:12:59
(permalink)
ba_midi I'm noticing a LOT more "stuck" notes in X1B after muting or soloing a track or tracks. This has always been an issue in Sonar, but more pronounced in X1B. I'll live with it. But it's annoying. I believe that's related to how Cakewalk handles Midi note off. IIRC, the TT boys have had to deal with that (with SONAR) before. Something unrelated to your problem.
|
ba_midi
Max Output Level: 0 dBFS
- Total Posts : 14061
- Joined: 2003/11/05 16:58:18
- Location: NYC
- Status: offline
Re:X1B mute/solo comment
2011/03/21 19:14:35
(permalink)
Mod Bod ba_midi I'm noticing a LOT more "stuck" notes in X1B after muting or soloing a track or tracks. This has always been an issue in Sonar, but more pronounced in X1B. I'll live with it. But it's annoying. I believe that's related to how Cakewalk handles Midi note off. IIRC, the TT boys have had to deal with that (with SONAR) before. Something unrelated to your problem. Yes, and as I said it's not a new issue. It just eeems worse at the moment. I just took a large project and did the exact same tests in 8.5.3 and X1B. 8.5.3 was much better at handling it. Don't ask me why :O
|
SilkTone
Max Output Level: -59.5 dBFS
- Total Posts : 1566
- Joined: 2003/11/10 17:41:28
- Status: offline
Re:X1B mute/solo comment
2011/03/21 19:41:54
(permalink)
I have said for a while now that there is absolutely no reason to mute MIDI tracks at all, just audio tracks. Temporarily interrupting a stream of MIDI data will often result in soft synths getting out of sync, especially some plugins don't like that. So doing something as simple as mute/unmute of a soft synth would result in needing to stop and restart the transport to get things back into sync. Ideally there should be a global setting that allows MIDI and audio tracks to be unlinked in such a way that if you mute the audio track, the MIDI track is not muted at all. Then if you unmute it again, the audio would be perfectly in sync since the soft synth was receiving an uninterrupted stream of MIDI events the whole time. If you want to mute the MIDI itself, just mute the MIDI track directly. I fail to see why it works the the way it does right now in Sonar.
Windows 10 Pro x64, SONAR Platinum 64-bitFocusrite Scarlett 18i8 USB, ASRock Z97 Pro4, Haswell 4790k @ 4.4GHz32GB DDR3/1600, 500GB SSD (OS) + 256 GB SSD + 3TB MDNVIDIA GTX-1070, 40" 4K Monitor + 1 Monitor in ISO booth
|
ba_midi
Max Output Level: 0 dBFS
- Total Posts : 14061
- Joined: 2003/11/05 16:58:18
- Location: NYC
- Status: offline
Re:X1B mute/solo comment
2011/03/21 19:45:56
(permalink)
SilkTone I have said for a while now that there is absolutely no reason to mute MIDI tracks at all, just audio tracks. Temporarily interrupting a stream of MIDI data will often result in soft synths getting out of sync, especially some plugins don't like that. So doing something as simple as mute/unmute of a soft synth would result in needing to stop and restart the transport to get things back into sync. Ideally there should be a global setting that allows MIDI and audio tracks to be unlinked in such a way that if you mute the audio track, the MIDI track is not muted at all. Then if you unmute it again, the audio would be perfectly in sync since the soft synth was receiving an uninterrupted stream of MIDI events the whole time. If you want to mute the MIDI itself, just mute the MIDI track directly. I fail to see why it works the the way it does right now in Sonar. In general, I would agree. There ARE circumstance where needing to mute a MIDI track is necessary, however. BUT, this happens with SOLOing audio tracks because, in effect, it mutes other tracks. So the result still is annoying. Without know the mechanics, it seems to me any MIDI tracks should be "silently streamed" when other tracks get solo'd so that there wouldn't be this result. At least that's one thought that comes to mind. But I'm not an audio programmer, so I don't know how it actually works. IOW, I agree with your premise.
post edited by ba_midi - 2011/03/21 19:48:00
|
SilkTone
Max Output Level: -59.5 dBFS
- Total Posts : 1566
- Joined: 2003/11/10 17:41:28
- Status: offline
Re:X1B mute/solo comment
2011/03/21 19:48:35
(permalink)
ba_midi SilkTone I have said for a while now that there is absolutely no reason to mute MIDI tracks at all, just audio tracks. Temporarily interrupting a stream of MIDI data will often result in soft synths getting out of sync, especially some plugins don't like that. So doing something as simple as mute/unmute of a soft synth would result in needing to stop and restart the transport to get things back into sync. Ideally there should be a global setting that allows MIDI and audio tracks to be unlinked in such a way that if you mute the audio track, the MIDI track is not muted at all. Then if you unmute it again, the audio would be perfectly in sync since the soft synth was receiving an uninterrupted stream of MIDI events the whole time. If you want to mute the MIDI itself, just mute the MIDI track directly. I fail to see why it works the the way it does right now in Sonar. In general, I would agree. There ARE circumstance where needing to mute a MIDI track is necessary, however. BUT, this happens with SOLOing audio tracks because, in effect, it mutes other tracks. So the result still is annoying. In those cases you can mute the MIDI track directly. Also, soloing would benefit from such a change as well since the exact same logic would apply. When soloing a track, only mute other audio tracks, but keep their MIDI tracks unmuted.
Windows 10 Pro x64, SONAR Platinum 64-bitFocusrite Scarlett 18i8 USB, ASRock Z97 Pro4, Haswell 4790k @ 4.4GHz32GB DDR3/1600, 500GB SSD (OS) + 256 GB SSD + 3TB MDNVIDIA GTX-1070, 40" 4K Monitor + 1 Monitor in ISO booth
|
ba_midi
Max Output Level: 0 dBFS
- Total Posts : 14061
- Joined: 2003/11/05 16:58:18
- Location: NYC
- Status: offline
Re:X1B mute/solo comment
2011/03/21 19:56:26
(permalink)
SilkTone ba_midi SilkTone I have said for a while now that there is absolutely no reason to mute MIDI tracks at all, just audio tracks. Temporarily interrupting a stream of MIDI data will often result in soft synths getting out of sync, especially some plugins don't like that. So doing something as simple as mute/unmute of a soft synth would result in needing to stop and restart the transport to get things back into sync. Ideally there should be a global setting that allows MIDI and audio tracks to be unlinked in such a way that if you mute the audio track, the MIDI track is not muted at all. Then if you unmute it again, the audio would be perfectly in sync since the soft synth was receiving an uninterrupted stream of MIDI events the whole time. If you want to mute the MIDI itself, just mute the MIDI track directly. I fail to see why it works the the way it does right now in Sonar. In general, I would agree. There ARE circumstance where needing to mute a MIDI track is necessary, however. BUT, this happens with SOLOing audio tracks because, in effect, it mutes other tracks. So the result still is annoying. In those cases you can mute the MIDI track directly. Also, soloing would benefit from such a change as well since the exact same logic would apply. When soloing a track, only mute other audio tracks, but keep their MIDI tracks unmuted. In the heat of battle, so to speak, things aren't always simple. In a big project, moving around, adjusting things, changing things, it becomes almost 2nd nature to grab for the mute or solo where you are. But, the real problem is the way Sonar handles all this. That's what needs a solution.
|