using receptor with DAW

[kurtr2]

ok, i need some help here people if possible which reflects on important issues regarding receptor.

receptor is great as a live instrument but i want to use it mostly to get good latency for my virtual instruments wiithin a DAW environment. how can i preserve receptors great internal latency as tracks pile up inside the DAW and force a larger buffer setting in the DAW? someone mentioned the use of a midi splitter and merger. can someone give me a signal flow rundown on how this can be used properly?


BTW i am using Digital Performer. as soon as i print a few audio tracks i have to up the buffer settings inside of DP in order to play them, thereby increasing my latency while using receptor.

thanks,
Kurt

[Hybernation]

ok, i need some help here people if possible which reflects on important issues regarding receptor.

receptor is great as a live instrument but i want to use it mostly to get good latency for my virtual instruments wiithin a DAW environment. how can i preserve receptors great internal latency as tracks pile up inside the DAW and force a larger buffer setting in the DAW? someone mentioned the use of a midi splitter and merger. can someone give me a signal flow rundown on how this can be used properly?


BTW i am using Digital Performer. as soon as i print a few audio tracks i have to up the buffer settings inside of DP in order to play them, thereby increasing my latency while using receptor.

thanks,
Kurt

I have had the same issue since day one with Uniwire, and the only answer is this: if you have to run your DAW at anything higher than a 5ms latency, you will need to ditch uniwire and use the MIDI inputs of the Receptor (that is, if you want to play your VST's on receptor in real time while composing on the DAW). It's not such a bad solution if you can feed the SPDIF from the Receptor back into your soundcard. Even better if you can utilize the ADAT outs on Receptor the same way.

Oh, of course the other thing to mention is the buffer size on the Receptor. I find that using the MIDI inputs, 128 is acceptable for everything except drums played in realtime, and some fast/percussive piano parts, in which case I go down to 64. Like any computer, lower buffer = lower latency = higher CPU usage. Same old trade-off.

just by .02 worth (based on a couple of years with my Receptor, before and after Uniwire became available)

John

[JayVee]

I mean no insult by stating the obvious, but you could always use the S/P DIF out, and turn your tracks into great sounding audio as you nail each one.

That'll help you out.

[kurtr2]

yes that is true, no insult taken. thats another discussion about work method, commiting to what you record, etc. i like to keep things open until everything is right, then print all at once.

i have it working pretty good now connected via midi, but one drawback is you are limited to 16 tracks. i guess then you can print something...

still wondering about midi latency from the host when you bump up the buffer, even if receptor stays at a low buffer setting. in this case it seems a midi splitter would work and monitor the DAW off receptors spdif input.

any thoughts?

thanks,
Kurt