#Pianoteq buy license

'How does the information produced when I strike a key, flow through the keyboard and computer ?' With each complication you introduce into the process, you have to ask the question: 'Rendering' is _not_ a real-time operation the computer can take as much time as it needs - no drop-outs, no glitches. 'Render' the MIDI recording, by playing it through Pianoteq, and recording the digital audio (WAV) output. After finishing playing, save the MIDI recording.

Monitor your playing (while recording) using the Roland's built-in sounds, or the (possibly glitchy) Pianoteq audio output. MIDI recordings are really short (a few bytes per note), and won't stress the CPU at all. Record the piano performance as a MIDI file (Pianoteq lets you do that, probably so does every other VST). (b) One way around the 'slow CPU' problem: FP-90 / FP-90x are both modelled (for their main piano sounds) - no samples. FP-10 is sampled, with some some algorithmic aids for the 'SuperNatural' pianos.

(a) The FP-10 and FP-90 have completely different sound generators for piano:

#Pianoteq buy license

Otherwise, I would invest in an interface and maybe pickup a license down the road when you can hopefully afford to be pickier about the sound. If you've got good hardware and will be recording the keyboard individually, using a VST is probably a safe bet (and fortunately you can test that for free). HOWEVER, when I record simultaneously with vocals or anything else, I switch to the Focusrite because most VSTs I use either hog the audio card or lag otherwise on my hardware.

The sound is just better and more customizable than Roland's. I happen to have both a Focusrite 2i2 and a Roland FP-90 (same sound I believe) as well as some VSTs, and I've recorded many more VST tracks than lineouts (I'm partial to Garritan CFX).