One midi controller for multiple tracks. What am I doing wrong, or, is the latest update buggy?{SOLVED]

Discussion about: tracktion.com
RELATED
PRODUCTS

Post

Peter Widdicombe wrote: Mon Jun 29, 2020 12:08 am Yeah, without using a rack, you may not get both functional on one track. Remember - most MIDI plugins will NOT respond to audio input, so will be silent. Similarly, MIDI "note events" without a VST can't be heard. If you really MUST do this, you probably need a rack, so you can send the audio in to audio out, and midi IN to the VST you drop into it - and it's audio ALSO to the output. You can also have a rack with multiple VST's in parallel, so MIDI in on that track hitting the rack can feed all of the VST's in the rack; and their output all combined in the output.

There are probably about 3 other ways of doing that MIDI overlay thing... but you can save a rack as a preset if you have odd combinations you use often. Like keyboard splitting -
1. Create a rack and drop 2 VST's into it.
2. Drop a MIDI filter in front of each to block keys above/below a given key
3. Route MIDI in to both filters, and one filter to each of the VST's
4. Audio out on both VST's to L/R output.

Now when you play the keyboard, low notes go to one vst and high notes go to the other.

If your keyboard already HAS keyboard-split to different MIDI channels, replace the filter with one that filters based on MIDI channel input.

I have one keyboard with pitch bend and no mod wheel. Using these tricks and MIDI modifiers, I can reverse that and use the pitch bend wheel as a mod wheel instead.
I actually understand what you're saying for the most part. Since I know about guitar pedals and signal chains, that's helped me understand a bit easier working with VSTs. Can't recall what moved me to think about setting up VSTs in parallel, but I dabbled in that area. Connecting the wiring got confusing, but at least I know it's an option. Creating multi-out for a drum kit is more important for me, at the moment.

Good tip on how to create a split keyboard (my Arturia is as new as WF, and I haven't learned all the ins and outs of that).

I have more pressing problems now. I've discovered that some of my Izotope plugins aren't working. Imager doesn't pass validation. Ozone 9 does, but when I load the plugin, the sliders and everything else doesn't respond. So I'm going through all my plugins.

I'd rather have a root canal, than to do a clean reinstall of the OS, which is really quick. It's all the plugins and authorizations. I may post in the Problem Plugins thread, or write support whether the latest update is problematic. I may check the Tracktion website and see if there's earlier versions of WF 11, and maybe install the version prior to the last 2 updates. Inevitably, I'll toast my system, and be forced to do a reinstall. I haven't had so much trouble since Win 98. And I lost all my earlier restore poinst. Something's up with my computer, and it's only a year and a half old.

Post

Using Izotope plugins with Win 10 and Waveform, and all are working fine. I hate to suggest that you may have some fundamental technical issues....
Spotify, Apple Music, YouTube, and even Deezer, whatever the hell Deezer is.

More fun at Twitter @watchfulactual

Post

Watchful wrote: Mon Jun 29, 2020 11:52 pm Using Izotope plugins with Win 10 and Waveform, and all are working fine. I hate to suggest that you may have some fundamental technical issues....
Yeah, no doubt, and it's driving me crazy. 10 days ago, everything was working just fine.

But, speaking of crazy- my computer desk has 2 tiers. On the top tier is an old 21" monitor, I think the resolution is no more than 780. My laptop is a 4k resolution, and I've extended the monitors. When I drag Imager or Ozone 9 to the larger monitor, the plugins work. And I still get an error message when I do the plugin validator thing for Imager, and Ozone 9.

I know lots of people have problems with the scale of a lot of plugins on high resolution monitors, and when the Imager and Ozone 9 was on my high res laptop monitor, the scale was off, and I had trouble dragging it aound (didn't have this problem 2 weeks ago, but I got a mess of Dell driver updates). On a whim, I decided to drag the Imager plugin to the low res monitor, and it came to life. Same with Ozone 9.

I have both VST2 & VST3 plugins loaded. I have to figure out which ones give the error message. To make things more confusing, when I click "open containing folder" from the plugin tab, the VSTs aren't there. But that's not new for me. I googled "VST doesn't work in high resolution monitor" and found a hit that was similar and it involved Izotope: https://www.reddit.com/r/StudioOne/comm ... f=readnext

Maybe I can avoid a reinstall of everything. I was thinking of building a dedicated small form factor pc, with a dedicated video card. I wanted to get a high res monitor to extend to, but it would be pointless if it causes more problems. FFS, it's 3:30 a.m. I've spent countless hours on this, but for now, I think everything is working.

Post Reply

Return to “Tracktion”