Hi all,
Platform: Windows XP SP3 4G Memory.
Audio/MIDI: LPSII into Presonus Firestudio Tube. MIDI via MOTU 5x5.
DAW: Presonus Studio One Pro 2 - ver 2.5
Latest firmware in the LPSII and latest Rekon / Moog VST.
This is a Quad Core 2.66 GHz machine with 4G mem and 3 cores assigned to S1 Pro2. The VST is configured as per the manual example picture in the VST manual.
I have the VST set up and working *mostly*. I have in/out set to MIDI channels 1 & 2 - as per the settings I have on the LPSII itself.
I can control the LPSII and send and receive panel settings changes, load banks and send patches.
I can play the LPSII kbd and see the MIDI in the instrument track (I have a separate audio in from the LPSII of course). The MIDI is being routed out to the kbd OK and I hear audio in S1Pro just fine.
However, when I use the pitch bend wheel on the LPSII, the VST seems to send so many events that the VST causes a CPU spike. (Monitored with the S1 Pro 2 monitor)
Nothing else is talking to the MIDI port. I.e. I do not have entries in S1 Pro for the same MIDI port.
I *have* tried (separately) with an external kb and external instrument setup in S1 Pro directed from/to the LPSII and I *don't* see any CPU spikes for the MIDI data coming in raw from the LPSII even from the pitch bend, so it seems like there may be an issue with the VST messages to/from the LPSII / DAW)
It may be that I still have the software routing wrong in the setup. I would be glad for suggestions.
If you need any more information from me, please don't hesitate to ask.
I'd like to get this working so I can save and load patched directly within S1 Pro II via the VST, but as it stands, I can't use it because of the spiking. I can go back to an S1 Pro 2 instrument / kbd out/in setup, but then I can't save patches of course - which is one main reason I bought the VST. Yes, I can run the VST as the EXE application standalone, but, then I can't hear what the result sounds like with inserts, FX, etc. inside the DAW. Catch 22 at the moment.
Any help appreciated.
Kind regards
Derek Jones, Owner: MusicInclusive LLC
www.musicinclusive.com
LPSII VST pitch bend CPU spikes
-
MusicInclusive
- Posts: 8
- Joined: Sat Feb 02, 2013 2:15 pm
Re: LPSII VST pitch bend CPU spikes
Well, to answer my own post, I needed to work up to the required setup one setting at a time to eliminate any potential loops.
I think the VST is better with a Little Phatty than with a Stage Phatty. The problem seems to be that using the LP SII keyboard / wheels to send the MIDI events for note on/off / pressure - and using the mod wheel and pitch bend - *into* the VST and then out again from the VST to trigger the synth is a bad idea since it's hard to avoid loops. I guess this VST was designed to be used with input coming from a different keyboard to trigger the LPSII, rather than using the keyboard on the LPSII itself. Likely designed when only the LP existed without a keyboard.
So, I've settled on a halfway house. I'm using an external keyboard / instrument pair in S1Pro2 connected to the LPSII and then using the exe version of the VST to *only* control / follow LPSII parameters, save and load patches and banks, etc. using a minimal CC and Sysex and program change setup instead.
It's a workable solution that is "OK" but not as nice has having it all work seamlessly as a VST.
Another problem is that the VST spikes randomly on its own after a while, even when nothing is being played or anything else is happening with S1Pro 2 - i.e. it's totally idle - whereas that doesn't seem to happen with the exe version.
I'll try and get round to posting a setup pic for the VST at some point.
Kind regards
Derek.
I think the VST is better with a Little Phatty than with a Stage Phatty. The problem seems to be that using the LP SII keyboard / wheels to send the MIDI events for note on/off / pressure - and using the mod wheel and pitch bend - *into* the VST and then out again from the VST to trigger the synth is a bad idea since it's hard to avoid loops. I guess this VST was designed to be used with input coming from a different keyboard to trigger the LPSII, rather than using the keyboard on the LPSII itself. Likely designed when only the LP existed without a keyboard.
So, I've settled on a halfway house. I'm using an external keyboard / instrument pair in S1Pro2 connected to the LPSII and then using the exe version of the VST to *only* control / follow LPSII parameters, save and load patches and banks, etc. using a minimal CC and Sysex and program change setup instead.
It's a workable solution that is "OK" but not as nice has having it all work seamlessly as a VST.
Another problem is that the VST spikes randomly on its own after a while, even when nothing is being played or anything else is happening with S1Pro 2 - i.e. it's totally idle - whereas that doesn't seem to happen with the exe version.
I'll try and get round to posting a setup pic for the VST at some point.
Kind regards
Derek.