Transform to Rendered Audio - question

[tune.m.smith]

Yes, they fixed the render/freeze staying as mono with the current version 8.

However, I also don't understand why a mono audio track can't be routed as the input for another mono audio track?

And it does not allow the most elementary thing at all, which is to route the signal from an existing mono track to a new mono track and then record it. And yes, everything works correctly in version SO6.6.4

Here the 'Track 1' is a mono channel highlighted in orange, with mono material.
'Track 2' is set to receive Track 1 as its input and it forces the input into stereo.
This is true for mono virtual instrument channels as well, it forces the input into stereo.

But if an audio interface mono input (setup in the Audio I/O) is selected, the input remains in in mono on Track 2. Highlighted in green.

There is something not identifying the DAW internal routing channels properly. And always forcing the input into stereo, no matter if the channel output is mono.

Are you saying this works properly in one of the v6 releases? Or only the freeze/render worked properly back on that release, but this mono to mono internal routing was not working still?

 

[fikus84]

Yes, they fixed the render/freeze staying as mono with the current version 8.

However, I also don't understand why a mono audio track can't be routed as the input for another mono audio track?


Here the 'Track 1' is a mono channel highlighted in orange, with mono material.
'Track 2' is set to receive Track 1 as its input and it forces the input into stereo.
This is true for mono virtual instrument channels as well, it forces the input into stereo.
View attachment 3526

But if an audio interface mono input (setup in the Audio I/O) is selected, the input remains in in mono on Track 2. Highlighted in green.
View attachment 3527

There is something not identifying the DAW internal routing channels properly. And always forcing the input into stereo, no matter if the channel output is mono.

Are you saying this works properly in one of the v6 releases? Or only the freeze/render worked properly back on that release, but this mono to mono internal routing was not working still?

You described it perfectly. This is exactly how I wrote a support ticket almost 2 years ago. A rational answer never came and the problem went unnoticed. In the latest version of Studio One 6.6.4 this "mono to mono" routing works correctly.

Anyway, it should still be true that there are tracks in the project that must remain in their mono form and not be made into stereo tracks during editing, and that in the easiest and fastest way possible. Not that I will have to keep an eye on and click the speaker format button on each track.

 

[tune.m.smith]

The 'click the speaker format' doesn't apply to freeze/render, or mono channel output to mono channel input. The support tickets you put in profile that v6.xx works in this way specifically?

Btw I'm with you in terms of it needing to be straightforward.

Maybe there is a "best" version of studio one. And maybe that version is a couple of releases back.

 

[fikus84]

The 'click the speaker format' doesn't apply to freeze/render, or mono channel output to mono channel input. The support tickets you put in profile that v6.xx works in this way specifically?

Btw I'm with you in terms of it needing to be straightforward.

Maybe there is a "best" version of studio one. And maybe that version is a couple of releases back.

Changing the speaker format has always been the answer (from support) to how to make a recorded stereo track mono. Unfortunately, they didn't consider changing the volume, which is a small but sometimes important detail. Changing the format has no effect on the output and input, as you write. Yes, in the support ticket I mentioned that it's fine in v6.x.x and I gave it as an example. In terms of track routing/rendering, version 6.6.4. is much better than the current version. It's a shame that no one pays attention to this and instead less important things are addressed in new updates. On the other hand, as someone who has used Studio One since version 1.x, Studio Pro is a good DAW in many ways.

 

[tune.m.smith]

Changing the speaker format has always been the answer (from support) to how to make a recorded stereo track mono. Unfortunately, they didn't consider changing the volume, which is a small but sometimes important detail. Changing the format has no effect on the output and input, as you write. Yes, in the support ticket I mentioned that it's fine in v6.x.x and I gave it as an example. In terms of track routing/rendering, version 6.6.4. is much better than the current version. It's a shame that no one pays attention to this and instead less important things are addressed in new updates. On the other hand, as someone who has used Studio One since version 1.x, Studio Pro is a good DAW in many ways.

But the changing of speaker format only applies to bounce or final export. Not to rendering/freezing. Or to routing within the internal DAW channel input being received from another DAW channel ouput.

 

[fikus84]

But the changing of speaker format only applies to bounce or final export. Not to rendering/freezing. Or to routing within the internal DAW channel input being received from another DAW channel ouput.

Yes, that's right. Speaker format is used when rendering the mix/track. That's why the argument from support was not correct...

We have these cases for freezing:
1. mono track, channel format mono, NO PAN => freeze => mono track
2. mono track, channel format mono, PAN L-R => freeze => stereo track
3. mono track, channel format stereo => freeze => stereo track
4. stereo track, channel format mono, NO PAN => freeze => mono track
5. stereo track, channel format mono, PAN L-R => freeze => stereo track
6. stereo track, channel format stereo => freeze => stereo track

It has no effect on routing inside the DAW. It also has no effect on HW input and output, here it depends on the audio interface settings.

So in the end, you have to take into account what happens when setting points 1-6. And it's still about the fact that it is not possible to route a mono track to a new mono track and then record. Bailatosco said it well in his post.

 

[Craig Anderton]

Here the 'Track 1' is a mono channel highlighted in orange, with mono material.
'Track 2' is set to receive Track 1 as its input and it forces the input into stereo.
This is true for mono virtual instrument channels as well, it forces the input into stereo.

I'm curious under what conditions this matters. The channel meter shows the dual mono audio as if it was a mono signal, and panning acts like a standard mono signal. The two issues I can think of from this behavior are 1) if you want to use a mono-only plug-in with the track, and 2) a dual mono file takes up more memory than a mono file.

As someone who uses mono tracks from time to time, I want to know more about this so I don't run into a "gotcha" I hadn't considered. Are there are other issues, and if so, do they impact workflow or a technical consideration?

 

[SwitchBack]

A mono mono track is 'pan law free'. A centered mono stereo track isn't, so playback can be quieter or louder than the mono mono track (depending on pan laws used).

 

[Craig Anderton]

Thank you! That explains why this issue doesn't affect my workflow, but now I understand how it could affect others.