T7 Racks!!

[alejandrozalaquett]

Thanks! Glad you like the improvements

Do you think yoiu are going to be able to resolve the latency issue?

I wasn't aware there was one. Can you elaborate a bit?

When I route Superior Drummer outputs to several tracks for per mic proccessing it works fine with midi clips input. Although if I try to play superior drummer in realtime, severe latency problems occur. This doesn't happen without the rack routing.

[dRowAudio]

Well it needs a block of latency so that all the tracks are played in sync. Because tracks are processed in parallel we can't process the rack contents until all the tracks have had a chance to provide their input.

The only way around this is to reduce your buffer size a bit. ~4ms should be acceptable to play (as this will get doubled with the multi-track rack).

[alejandrozalaquett]

Well it needs a block of latency so that all the tracks are played in sync. Because tracks are processed in parallel we can't process the rack contents until all the tracks have had a chance to provide their input.

The only way around this is to reduce your buffer size a bit. ~4ms should be acceptable to play (as this will get doubled with the multi-track rack).

Well, the latency I'm referring to is very high (half second?) and with audio dropouts.

[dRowAudio]

What's your device's buffer size and sample rate?

[alejandrozalaquett]

What's your device's buffer size and sample rate?

I work on a RME UCX at 44,100 and 512.
I have never had latency issues until this routing using racks.

[alejandrozalaquett]

What's your device's buffer size and sample rate?

I work on a RME UCX at 44,100 and 512.
I have never had latency issues until this routing using racks.

Another problem is that I have to play every midi clip going through the rack before I can export an edit, otherwise the export misses some notes. It´s like T7 needs to "buffer" the rack.

[dRowAudio]

What's your device's buffer size and sample rate?

I work on a RME UCX at 44,100 and 512.
I have never had latency issues until this routing using racks.

Another problem is that I have to play every midi clip going through the rack before I can export an edit, otherwise the export misses some notes. It´s like T7 needs to "buffer" the rack.

Hmm, that sounds like a bug. Do you have a minimal Edit that demonstrates the problem? I.e. a single (or double) track with a single rack and one, commonly available instrument?

Do any of the plugins inside the rack have latency? It sounds like something might be throwing the PDC calculations off. A buffer size of around 128 is probably better if you're monitoring through a rack. You'll notice anything larger once the rack as introduced its buffer delay (when there are instances on multiple tracks).

[famouswolf]

I'm also curious about these changes as I am kind of on the fence about which daw to use.
I'm experiencing a difference which I'm not sure is a bug or some workflow change.

Say for example: I create a track and add a .wav audio clip to it.
If I then create a pass-through rack on that track, it works.
If I try to duplicate the rack (by dragging a rack instance) to another track
in order to have the signal go to both tracks, I get no sound. Even from the original track.
If I disable the other rack or mute that track, the original rack works again.
If I leave both racks enabled, save and restart tracktion, both racks work and play
as expected.

This happens both at work (Windows 7 x64 using "windows audio")
and at home (Ubuntu 16.04 x64 using jack).
This didn't happen with Tracktion 5 so I wonder if there was some workflow change or default
setting that changed.

[dRowAudio]

Hi famouswolf, what version of Tracktion are you using? I just tried this and it seems to work as expected, the audio is sent out of both tracks. Are you using the "Stereo Pass Through" preset or creating your own?

Do the tracks come to life if you press the "Panic" button in the transport area above the master plugins?

[famouswolf]

Hi dRowAudio

I'm using the latest version of Tracktion 7 64bit from the website, downloaded 4 days ago.
I'll download again and try it out.
I'm creating a new empty rack and just connecting the inputs to the outputs.
Using the stereo pass-through has the same effect.
I'll try and make a video to show exactly whats going on.
The panic button doesn't fix it for me.

Thanks

[famouswolf]

I made a quick video at work using a screen recorder I found.
Unfortunately there is no sound, but you can just look at the level meters.
Here is the link:

[lay it prodctions]

I made a quick video at work using a screen recorder I found.
Unfortunately there is no sound, but you can just look at the level meters.
Here is the link:

IN ORDER TO MAKE A PASS THRU RACK WORK PROPERLY TURN THE SEND PASS THRU (DRY UP AND WET OFF) AND TURN THE RETURN PASS THRU (WET UP AND DRY OFF) . I APOLOGIZE FOR THE ALL CAPS MY KEYBOARD GOT STUCK.

[famouswolf]

Isn't that if you want the original signal to pass through the rack without
any signal being processed by the rack?
What I am trying, is to have the signal basically being duplicated to another track,
Just like in this video
(3mins 32seconds, if the link started playing from the begining)
I just downloaded a demo of T6 and it gives me the exact same behaviour.
I can actually hear tiny millisecond glitches of the signal coming through every now and then
which leads me to think that it is trying to work, but something is preventing it.
I get this on Windows and Linux.

I just installed an older Tracktion 5 ver 5.4.2 on Linux and it works perfectly.
The signal is duplicated as expected.

So it seems something has changed with racks from T6 already.

[operandx]

Think it's a bug. If you don't connect ins and outs directly but via the patch bay (it's called 'read me' in the Stereo Pass Through template) it should work OK.

[famouswolf]

Unfortunately, it still doesn't. It doesn't matter what I put in the rack, I have to close Tracktion and reopen of the send to work.
I was trying to find another way of sending midi data to multiple tracks, but no luck so far.
Aux send only sends audio. If I set the master midi track destination to a midi through channel, I can get it on another track
by selecting its track input. Problem is that an input can only be used once as far as I know.

Ok, so I've found a temp workaround for me. I set the track destination to "Midi Through (1)".
"Midi Through" devices are generic ALSA midi devices in Linux.
Then in Tracktion settings I create a few virtual midi devices with the input being "Midi Through (1)".
I can then set the input of various tracks to be one of these virtual midi devices.
Not ideal, but it does work reliably. I just have to create enough virtual midi devices for all
the instruments I would need.
The main reason I'm trying something like this is to mix drum elements separately.

If anybody has a fix or a better workaround please let me know. Thanks.