OK, maybe I expressed myself wrongly.

Please read takes as events (meaning separate pieces of audio).

So I have 100 separate pieces of audio on my track.

When doing something like this, Solo the wanted track and then render the track - I do that by using the File/Render As option (choice of audio codecs) rather than Render to New Track.

When doing something like this, Solo the wanted track and then render the track - I do that by using the File/Render As option (choice of audio codecs) rather than Render to New Track.

Oh, so the best option is Render As (WAV for ex) and re-import the modified wav manually on a new track?

So what does the Render to a new track do?

OK, I guess I assumed that render to a new track would render the selected tracks.

Turned out that Render To a New Track, renders what is audible, not what is selected.

So I solo the wanted track (as per dexcon sugg) and I render to a new track.

Oh, so the best option is Render As (WAV for ex) and re-import the modified wav manually on a new track?

IMO, yes - for a track rather than individual event, and I do use WAV as my codec choice.

So what does the Render to a new track do?

I use that option rarely, but for a single event only, not for the entire track. Again, my opinion only. Actually, I find it annoying because it creates a new track on the timeline to place the newly rendered event which I then have to delete after moving the new event down to a lower track previously created track.

EDIT:

So I solo the wanted track (as per dexcon sugg) and I render to a new track.

Yes and no. The render via File/Render As does not create a new track, it simply creates a new file in the folder that you've selected the render to be saved to. All you have to do then is to import that new event to the timeline as you would any other media.

Oh, so the best option is Render As (WAV for ex) and re-import the modified wav manually on a new track?

IMO, yes - for a track rather than individual event, and I do use WAV as my codec choice.

So what does the Render to a new track do?

I use that option rarely, but for a single event only, not for the entire track. Again, my opinion only. Actually, I find it annoying because it creates a new track on the timeline to place the newly rendered event which I then have to delete after moving the new event down to a lower track previously created track.

EDIT:

So I solo the wanted track (as per dexcon sugg) and I render to a new track.

Yes and no. The render via File/Render As does not create a new track, it simply creates a new file in the folder that you've selected the render to be saved to. All you have to do then is to import that new event to the timeline as you would any other media.

What I meant is that this is the way I found it works.

Honestly I would rather vegas create the new track for me via the Render As a New Track than me exporting/creating a new track/and importing

I just created 3 audio tracks with 3 different audio events (VP17 b421), selected solo for the middle event and used Render As New Track - and it created a new track with just the solo track recreated. It did not render the other 2 tracks which had effectively been muted.

I just created 3 audio tracks with 3 different audio events (VP17 b421), selected solo for the middle event and used Render As New Track - and it created a new track with just the solo track recreated. It did not render the other 2 tracks which had effectively been muted.

I think we are saying the same thing :)

So I will use Render as a new Track.

Now I'm confused because in your original post you said:

I tried something called "Render To New Track" whilst the track was selected, it just rendered all the audio tracks into a single track.

Perhaps the selected track wasn't solo'd.