Audiotool board archive

Multi-Track Sending (Very Applicable!)

Wiz · started 2022-09-08 08:45 · updated 2023-05-25 06:20

The Idea

The idea behind this is to allow users the ability to send information from one track to either one or multiple other tracks. This information can include either the notes that are on that track, or the automations on that track.

The Menu

[[Attachment:9]]

I have went through the effort of using photoshop to simulate the menu that could be used for this.
It should be self explanatory in the image to the right.

How it Works

Everything is designed to be very intuitive. You should expect to be able to navigate throughout this menu with ease. Each section explains the workings of this feature, as well as any limitations that are included.

Icon Style

An icon will be located on the track. Using this icon, you will be able to open the menu. The icon was designed to fit the Audiotool workstation as best as possible, with individual color codes for what that track is doing or if a limitation occurs (explained in Limitations). Below, you can find what these icons might look like:

  • Neither Sending nor Receiving (First Image)
[[Attachment:1]]
  • Sending info to another track (Second Image)
[[Attachment:2]]
  • Receiving info from another track (Third Image)
[[Attachment:3]]
  • Sending & Receiving to and from other tracks (Fourth Image)
[[Attachment:14]]
  • Error sending info to another Track (Fifth Image)
[[Attachment:13]]

Menu Selections

In the menu you can find two areas to work with. The first area is "Selection". There is where you will apply any track sends you wish to use. The second area is "Track Sends". This will show a list of all track sends from the track you have selected, as well as their destination. Track Sends is also where you can modify and remove current track sends.

About Sending

When you are sending from one track to another, the position of all items on the timeline for the track that is sending will also apply to the receiving track. The only way to modify this is to change the position and/or status of the item on the sending track.

Limitations

If a receiving track already has items similar to those that it is receiving (i.e. there is already a note block present), those items will take priority over any send items and a red icon will be shown (see Icon Style). This means that in order to receive information from another track, there must not be similar items on the receiving track.

If you choose to send information from one track to another, all information that can be sent will be. This works similarly to being able to receive items in ways of needing to have an automation/note track open for that device.

[[Attachment:12]]

For example, let's say the sending track includes tracks for Notes, Gain, and Velocity (and you choose to send Notes & Automations from the menu) and the receiving track only has tracks for Notes and Gain. Then the sending track will send Notes and Gain while Velocity is not sent. Any other tracks will not be sent.

When you are recording to a track, the recording will not be applied as a send until the recoding is complete.

Why is this Necessary?

This helps by allowing you to control what data is sent, and preventing a situation where if you are sending from one track which is for a device that is different than the receiving track (i.e. sending from a Heisenburg to a Pulverisator). In this case, only applicable information will be sent. This means if you are sending to a track that does not have the automations required to receive, that information will not be sent.

Due to complications, and many errors that can come up when implementing this, tracks can only send or receive information, NOT both.

Conclusion

This feature would provide many users a great way to reduce the amount of work required from them, while opening many doors to new ideas. It allows shortcuts that were not present before, and would be very easy on the user as it does not add a lot of workload to the client. All while being easy to use.

Comments (3)

2022-09-15 12:04 · 2022-09-15

Not gonna comment on the feature itself, but the request... I don't remember last time when I saw someone put such an effort into creating one.
Kudos to you!

2023-05-25 02:48 · 2023-05-25

Popping a comment in here in hopes that this might get be set as #Open or #Noted

a-records · reply
2023-05-25 06:20 · 2023-05-25

Thanks for the request. It's on the list