can BEN CROSSLAND and marc do me a special favour!! with TI

[Khazul]

I would guess your best estimate of CPU use is going to be roughly inline with your current sound and midi hardware transporting the same amount of data.

I tend to find hardware rates as follows:
Best - good PCI based devices, then Firewire devices, then USB devices with not that much to choose between USB and firewire.

[Tokartta]

Originally Posted by tk

...it will also bring you sample accurate MIDI timing...

How is this handled in hosts without plugin delay compensation? Are you including a small plugin that you can put on a seperate bus which'll delay everything else by the value of the TI delay, like Universal Audio do with their UAD-1? If not, will the delay be reported on the UI (if it's constant) so that Voxengo Sample Delay etc can be used?

Also, have you been in contact with Image-Line regarding FL Studio compatability? They're working on a PDC solution for FLS 6, and it'd help them greatly if you could initiate a conversation, if anything just to make sure that there won't be any unexpected hiccups when the TI and FLS 6 are both available. They were recently appealing to users to suggest VST(i)s that incur latency so that they could test their solution.

Oh, and it's great to see you Access guys amongst the community. (and sorry if this has been asked before!)

[Midi_Glider]

How is this handled in hosts without plugin delay compensation?

I suspect you might have to compensate manually. luckily, most modern hosts do support PDC these days (even Fruity is going to have it it its next update).



Best,
midi.

[Midi_Glider]

If you are using the Virus Control, the external jacks are behave like a external midi interface to the computer, no MIDI is routed to the synth engine then.

Hmmmm. but does the virus control allow you to route the stream of a certain multi part to a physical out instead of the USB ?


Best,
midi.

[F5D]

Originally Posted by Midi_Glider

Hmmmm. but does the virus control allow you to route the stream of a certain multi part to a physical out instead of the USB ?


Best,
midi.

Yes. This was answered somewhere above. However I don't know yet if those tracks will be compensated in anyway. If it doesn't compensate, I will do it manually like with all the other hardware synths I have. I will be using all the outputs, 2xusb + 3xanalog.

[Midi_Glider]

Nuendo 3.1 can now auto compensate for external synths routed trough the audio hardware (and actually treat external synths in a similar fashion to VSTi`s-very cool) so no problem for me there.


Best,
midi.

[F5D]

Originally Posted by Midi_Glider

Nuendo 3.1 can now auto compensate for external synths routed trough the audio hardware (and actually treat external synths in a similar fashion to VSTi`s-very cool) so no problem for me there.


Best,
midi.

I guess you cannot use the TI with the nuendo's external synth plugin if you want to use the TI's virus control software. You have to use the Virus in normal hardware mode without the usb transfers if you want to use the nuendo's own external synth plugin. All the sound tweaking also must be done from the Virus' own control panel.

Logic 7.1 doesn't compensate external synths but that's not a problem if you know what you're doing. Maybe we'll see a delay compensated version of the external synth plugin in logic too in the future...

[Tokartta]

Originally Posted by Midi_Glider

I suspect you might have to compensate manually. luckily, most modern hosts do support PDC these days (even Fruity is going to have it it its next update).

Best,
midi.

I'd need to know the delay, measured in samples, to do manual compenstation. If it isn't shown on the UI or documented then I can't. It need only be tiny text hidden away on some sort of about page that comes up when you click the Access logo or something. Whether FLS 6 will have 'full' PDC or not is still up in the air, and even then it's not due out until well after the TI is released.

[Midi_Glider]

I'd need to know the delay, measured in samples, to do manual compenstation.

This should be quite simple to check out:

1. write a midi part for the TI.

2. Bounce the part to an audio track.

3. compare the difference (in samples) between the original midi notes and corresponding audio event.


surely, this can be done in fruity, can`t it?


Best,
midi.

[Tokartta]

Well, yes. :P. Still, it'd be nice if I didn't have to. Also, if the delay varies, I'd have to do that regularly which is a real workflow bummer.