Subtracks, polyphonic tracks

What is the problem?

Currently, the tracker only supports 8 audio tracks, which was sufficient for TFMX Editor, 34 years ago. However, for modern music, this is limiting for users who want to use the tracker as their primary composition tool. 8 voice polyphony in not enough.

What should this feature achieve?

Make tracks capable of containing 4 sub-tracks. The sub-tracks will be routed through the parent track’s channel.

Proposal:

  • The user expands a track using Shift+Pattern, or using an option in the pattern settings.
  • Once expanded, the track will be split into 4.
  • When collapsed, the track can be named “Track 1 [=]”, displaying the data of the first sub-track.
  • When expanded, they can be named “Track 1 [A]”, “Track 1 [B]”, etc.

Some limitations may apply:

  • Only one track can be expanded at a time. If another is expanded, the others will collapse.
  • Only the first 4 tracks can contain sub-tracks.
  • They can only be for audio (not MIDI).

Advantages of this solution:

  • This solution preserves the functionality, layout, and user experience of the views built based on the current number of tracks (Master, Performance, Song) and the implementation of multitrack USB streaming.
  • It is scalable. It can be implemented on a single track or multiple tracks depending on the hardware capabilities.
  • It offers an opportunity to extend sound polyphony beyond 8 voices.
  • It can be ported to Play+.

Are there any workarounds?

Resampling (partially)

This workflow doesn’t help at the beginning of the creative process when you’re experimenting. It doesn’t give you the opportunity to refine.

Any links to related discussions?

Any references to other products?

Elektron Tonverk, Sonicware Smpltrek (drumkits)

3 Likes

Oh man, having polyphony might be the best upgrade of the Tracker ever. But I never dared to post this request, because I presume CPU limitations just don’t allow for any more sample tracks. Were that not the case, I’d think the MIDI Chord FX for sample tracks might already have been implemented.

But anyway, this has my vote of course.

1 Like

This would be epic. I would gladly give up midi/synth tracks as well if it helped curb the CPU usage.

1 Like

Sample polyphony should consume minimal CPU resources. My suggestion to save some CPU is to route the subtracks through one mixer (parent) track, as the other devices mentioned do.
The synths are the biggest CPU consumers in the Tracker.

I disagree and think 8 is perfectly OK. It’s a tracker with its roots in demo-scene history where many of the most famous tracks ever produced used just 4 tracks. Sometimes less is more, and some jobs require certain tools. Did you pick the correct tool?

3 Likes

I’m with you on this, having limitations inspires creativity.

Weird hills to die on, but okie dokie🤷‍♂️ This is an awesome idea and well thought out. It would make a great addition to the tracker’s workflow.

I know where this sentiment is coming from and I have the same tracker origin myself, but I 100% do not agree with this. Over many years of usage I’ve come to appreciate trackers for their songwriting strengths beyond just cramming as much as possible in four tracks like I did in the Protracker days. No other sequencer is this capable, period.

So I don’t think the Tracker needs to be burdened by a forty year old demo scene attitude. It already evolved way past its 4 track legacy by including proper effects, mixing, performance tools, synths, to name just a few. So having polyphony would just be another massive improvement.