New Tool (3.3) True Track Bypass

Alpha thrown together today to help preserve some CPU cycles. Mutes all instrument columns and bypasses all fx.

Use cases:

-Discover CPU hogging tracks.
-Doing a manual render and ‘freeze’ of a high CPU track.
-Preserving experimental/ sound design tracks for later and free up the CPU


ledger.scripts.TrueTrackBypass_V0.53.xrnx


Shortcut

True Track Bypass

GUI

  • Toggle Button for each track: mutes all note columns and bypasses fx on track

Muted instrument tracks = Red
Muted group/send/master = Orange

  • Track selection buttons on left.

NOTES:

Tracks aren’t fully muted and sends and groups will still allow sound to pass. It’s just all devices and notes will be bypassed.

If you have a device that you don’t want switched back on when using the tool, put it in a doofer and it will keep its bypassed state - For warning, tracks with any devices already off are marked with a [*]

trk bypass


Changelog, Click To View

-0.53
-Track select buttons are now a lighter shade of grey for Group tracks
-A warning [*] is shown next to any un-bypassed tracks that already have some bypassed devices on them. This is to note that they will be switched on again after activating the track again with the tool. They can be put into doofers if wanted to be kept in a bypassed state though

0.51 quick update:
-when non-inst tracks have no DSPs to bypass, a status is shown and the button will not default to orange

0.52
-made buttons a bit wider and stopped track names overrunning and making buttons bigger

My Other Scripts

5 Likes

Great tool for diagnosing buggy projects. Thanks for this!

2 Likes

Ledger Always something for us to make our lives easier in Renoise.A million thanks for all your effort

2 Likes

In first post

2 Likes

@Ledger thank you so much, it’s so handy!
It would be great to be able to automate :slight_smile:

1 Like

The trouble with automation is the slower speed of Lua threads vs. the main audio engine in renoise. Possibly could be hacked using some flag/ dummy dsp device though.

My intent is to make the best use of the CPU (thus being able to reduce latency), automating would make everything easier. But this is not the main purpose :smiley:

I will have a look at it.

In mean time a new small update in first post

-0.53

  • Track select buttons are now a lighter shade of grey for Group tracks
  • A warning [*] is shown next to any un-bypassed tracks that already have some bypassed devices on them. This is to note that they will be switched on again after activating the track again with the tool. They can be put into doofers if wanted to be kept in a bypassed state though

@Same_Freaky_Sound I’m thinking what your suggesting might be best achieved with a Hydra device i.e; set all of the targets of the device to the Bypass buttons of the track devices and simply automate the Hydra to set all on/ off

I should be able to script up something that will automate the assignment of the Hydra (up to 9 plugs)

To fully cut the sound of the instrument playing, a gainer could be set up at the beginning of the track to inversely mute the track with the same automation; this would take up one of the 9 slots though.

If you want to cut the the instrument playing notes at the same time simply middle-click in the oscilloscope to bypass for that pattern - (matrix X mutes)

This solution would mean you get the reliabilty of renoise’s own automation timing and don’t have to have a tool running in the background playing catch up.

Let me know what you think and I can try to do the Hydra part and add it to the DSP lane menu.

That’s exactly what I’m doing now, but there’s still room for improvement.
For example instrument FX are not easy to bypass; they can be mapped with macros, but with the limit of 8.
Anyway, thank you to take time to think about my suggestion, i really appreciate!

Could you not use Hydras in the Inst. FX chains and link the Hydras to the Macros?

You can even daisy-chain Hydras together so you would have a ‘Master Hydra’ controlling as many others as you need for the same instrument (just make one of the targets from the Master Hydra, the Input of the next).

Then you can bypass all the DSPs in an instrument with one macro, linked to the Master hydra:

[Macro] > [Master hydra] > [optional Chained Hydras] > [Linked FX]

Hydra 2

Hydra 1

@Ledger sorry for the late replay, you’re totally right!
I don’t know if it’s worth it, anyway i’ll we try and I’ll let you know :slight_smile:
Thank you so much!!!

1 Like