Changing VIs / keeping MIDI track connections
Moderator: James Steele
Forum rules
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
This forum is for seeking solutions to technical problems involving Digital Performer and/or plug-ins on MacOS, as well as feature requests, criticisms, comparison to other DAWs.
Changing VIs / keeping MIDI track connections
Is this just a glitch or is there anything I can do?
When I change a virtual instrument to a different module, any MIDI tracks that were output to the original automatically update to be output to the new one. BUT, they don't actually output to the new one unless I go to the track and manually reselect the new one again.
When I change a virtual instrument to a different module, any MIDI tracks that were output to the original automatically update to be output to the new one. BUT, they don't actually output to the new one unless I go to the track and manually reselect the new one again.
- kelldammit
- Posts: 1012
- Joined: Sun May 22, 2005 10:01 pm
- Primary DAW OS: Windows
- Location: right behind you!
- Contact:
i think switching VI's behaves roughly the same way even when you're just monitoring (i.e. working out parts, not recording yet)...
though i think all i've had to do to cure that is to switch the MIDI track out of rec, and back to rec again.
i haven't tried it with prerecorded MIDI tracks, but it seems to make sense that there would be a problem there too.
kell
though i think all i've had to do to cure that is to switch the MIDI track out of rec, and back to rec again.
i haven't tried it with prerecorded MIDI tracks, but it seems to make sense that there would be a problem there too.
kell
Yes, this happens when I'm just fiddling around. I never put the track in record at all. Switching record-enable on and off is just as annoying as choosing the track output again.
It lists the right output, it just apparently doesn't make the virtual connections until an actual action is taken to connect them. It shouldn't have to be that way.
It lists the right output, it just apparently doesn't make the virtual connections until an actual action is taken to connect them. It shouldn't have to be that way.
- kelldammit
- Posts: 1012
- Joined: Sun May 22, 2005 10:01 pm
- Primary DAW OS: Windows
- Location: right behind you!
- Contact:
- richard
- Posts: 132
- Joined: Fri Oct 15, 2004 10:01 pm
- Primary DAW OS: MacOS
- Location: Los Angeles
- Contact:
For me, it's a low priority glitch compared to simply improving the code to be more CPU friendly.stickwolf wrote:Anybody? Should I just report this as a glitch to MOTU?
One problem implementing this feature would be that some instruments are multi-timbral. If you replaced a VI that previously had a MIDI track using that synth on channel 8, and replace it with a VI that uses only one channel, what is supposed to happen?
Richard Temple
G5 2x2 4.5Gb, MacBook, 828mkII, Tascam FW 1804, DP, Logic, Giga, MachV, Reason, Live, EW Gold, Stormdrums, Atmosphere....
www.mutexmusic.com
G5 2x2 4.5Gb, MacBook, 828mkII, Tascam FW 1804, DP, Logic, Giga, MachV, Reason, Live, EW Gold, Stormdrums, Atmosphere....
www.mutexmusic.com