Are rack latency and note dropping issues in t2 solved?

[rich_h]

Given that one of the demo limitations is sending All Notes Off to all external MIDI devices every so often, and that you're not experiencing this dropped note on every iteration, it would appear to be the demo limitation and not the old "first note dropped" bug. It would be nice if someone in the know would confirm this, though.

[Solarfall]

with T1 I had issues with vsampler. I made a looping clip and the first note was sometimes missing.

[chico.co.uk]

The demo sends midi all notes off to external midi controllers every so often. You are using the demo. You find an external midi controller drops some notes. Because the demo sends midi all notes off to external midi controllers. So external midi controllers don't play all notes. Because the demo has a limitation where it sends midi all notes off to external midi controllers. So the external midi controllers don't play those notes. When the demo sends that midi all notes off command. To the external controllers. Which then don't play those notes. Because the demo sent that note off signal. To the external midi controller. Which receives the midi off note. And doesn't play a note. Because the demo sent a midi off control. To the external midi controller. Because it's a limitation of the demo. like it says. When you start it up.













... sorry, i've no idea what could be causing your problem, maybe someone else can help?

[chico.co.uk]

with T1 I had issues with vsampler. I made a looping clip and the first note was sometimes missing.

We should really coin a term for this kind of thing, something fairly descriptive, so that we're all on the same page when we talk about these things ... hmm, how about "the dropped first note bug"?

[Solarfall]

I would like to ask the beta testers to test this problem in T2. it pretty hinders the use of multi out instruments...

This is a known issue that Jules was made aware of way back when Racks first came out.

I was the one who first noticed it mostly because I tend to work at high latency settings when I am mixing not actually recording midi.

The latency in Racks is equal to the latency setting you are using and has nothing to do with plug-ins.

Put a multi-out drum machine into a rack.

Set each output to it's own output in the rack.

Put a midi clip on the track with a simple drum pattern in it for just 2 or 3 drums.

Put this Rack on 2 or 3 other tracks so that one track plays one drum and the other track plays the other drum (as if you were going to send each drum to a different effect on a different track. No effects used anywhere so we are just looking at the Rack and not introducing any other variables).

Put an instrument of some sort (a piano is good as it is percussive) on another track and add a midi clip with a few notes (preferably not on the drum beats).

Leave the midi clips in place.

Set the latency at around 40ms so the problem will be easily seen.

Render all tracks to one track (to one wave).

Now compare the rendered wave to the midi clips.
You will see that the piano notes line up with the midi notes.
The drum beats in the wave will NOT line up with the drum midi.

If you use Racks as sends and you use the rack more than once, you will have the same trouble. A non corrected latency added to your track that is equal to your latency setting. And that latency will add up for each extra rack you use.

This will give a smearing to you music even at low latency setting.

The only wat around this is to do everything INSIDE of the rack and not send things to other tracks for proccessing.

this is probably why there will be dedicated send in T2.

Hopefully they will work. I don't know what will happen with multi-out instruments. Building a multi out setup with all effects inside of a rack is troublesome.

[tkmattson]

I cannot try the demo because Im at work but I am currious:

Are rack latency and note dropping issues in t2 solved?

Just so you know, the stuck first note on render issue has not been fixed, nor does it sound like it will be fixed on this release, perhaps in an update or perhaps later than that....

http://www.kvraudio.com/forum/viewtopic.php?t=81683

[Solarfall]

yeah I know about that not fixed first note..this is annoying but not THAT important.
but what about latency in multiout samplers in rack? if this is not fixed I will probably not use t2 (after the long wait ufff...damn it). I dont want to go back to fl5 and cubase is so cumbersome...
shit I hope its fixed.

[Cosmic Bandito]

This first note issue was like the one single thing I was looking forward to in T2 (besides loop recording ).

If I recall Sonar had similar problems up until very recently (no count-in/metronome, and dropped notes on the first note of the first measure). I think these issues are heavily internal and probably take rewriting of some major code to fix. I'm not one to care for much in terms of features but music is all about timing for me.

Oh we'll...maybe Live4 works better with my methods of working anyway and I can get all my midi and audio "locked in" together without fighting the 'engine'. But I'd still love to have that in a Tracktion interface on day.

[Solarfall]

bump.

Anybody knows about about latency in multiout samplers in rack?

[Solarfall]

OK. as no tester responded, I assume that problem was not solved and the bug IS still there.

Pity.

[valley]

OK. as no tester responded,

Actually - I posted the answer to your question about three other threads, including one that was specifically title "rack latency" or some such. I got tired of retyping it.

Short answer: it isn't a bug - it's an annoying feature, and yes, racks still introduce latency.

[Solarfall]

thank you for your answer.

for me this is bug and big one, I dont care about PDC as I dont use Sir or any other similar vst but I do use multi out instruments and this bug makes them almost useless..
I dont like workarounds for this kind of basic stuff.