Is this a bug?

SHTUNOT wrote on 4/21/2003, 2:57 PM
When I try soloing a audio track any other track that is set to "pre volume" is still being fed to an assignable effect/bus. I can hear it in my outputs with my soloed track. Why?

The routing is ofcourse being done thru the multipurpose slider. If this is a good thing then I would like to know why.

Vegas 4.0B
XP [all updated]
layla 20bit 6.05 drivers

Ed.

Comments

SHTUNOT wrote on 4/22/2003, 1:57 PM
Ok fine so it isn't a bug but why does this make sense?

Issue:
1)Take 10 audio tracks.
2) 1-9 set the multipurpose fader to route audio to either a assignable fx or bus via "pre-volume".
3)TRACK 10 is being routed thru the Masterouts OR a Buss via the normal method of audio routing in the track itself.
4) Try soloing trck 10 to hear just trck 10 and you'll also get ALL the audio being routed from the multipurpose faders set to prevolume through the FX/busses in my master outs as well? WHY?

The whole point of "soloing" a audio track is to just hear THAT track. NOT with anything else. I have to MUTE any offending busses/assignable fx's to get what I'm after. Then hit ctrl+mute button to deselect the muted tracks.

I would just prefer to have solo do what it suppose to. I can't see why a track being "pre/post volume" should have anything to do with solo. In terms of FX I won't argue. But Solo should be in charge over pre/post.

Any comments pro/con? Am I making any sense? Peter? Dennis? Spot?

This is happening in BOTH Vegas 4.0b AND Acid 4.0b..current builds.

Ed.
SonyEPM wrote on 4/22/2003, 2:07 PM
I understand what you are after but it isn't currently possible with our routing flow. We'll put it on the list for re-evaluation for a future version.
Rednroll wrote on 4/22/2003, 2:10 PM
I ran into this same problem today. I was trying to do an A/B comparison of fade types, by routing 2 duplicate tracks to seperate buses, and then putting different volume fades on each bus. The volume for each track was set for "pre-fader". So soloing each track was not effective for what I was trying to do, because it was not muting the pre-fader send of the muted track.

I would think this is a bug. I can't see a reason why you would want to still hear the bus/effect of a seperate track that is set for "pre-volume" when you are just trying to listen to the track that is soloed. You can even hit the mute button for that particular track and the pre-volume send is not muted, just the volume fader is muted.

Peter?
PipelineAudio wrote on 4/22/2003, 2:14 PM
I've always thought " theres gotta be some reason and some situation, where this " feature" must be useful" I just cant find it yet. Im glad you guys are on the same page.

Soloed tracks' FX sometimes show " FX-muted" bug, but muted tracks sends arent muted? whats this world coming to ?
SHTUNOT wrote on 4/22/2003, 2:37 PM
---We'll put it on the list for re-evaluation for a future version---

As in Vegas 5? Or 4.0c? Crap...I have only myself to blame for not catching this sooner. But I will be expecting this out of Acid 5 since thats the next release down the road after Soundforge 7.

Thanks for the response.

Ed.
CDM wrote on 4/22/2003, 2:52 PM
I totally agree. I was in fact going to write about this same issue last week.

Solo should be solo should be solo.
Greg_M wrote on 4/22/2003, 3:14 PM
SHTUNOT,
I think what you are describing is the same thing as a "pre-fader send". If it is, this is a standard configuration and not necessarily a bug. I agree that it would be convenient to only hear the track you are soloing. I guess what would have to happen then, is that when you hit the solo button it also mutes all of the other tracks and their pre-fader sends.
Greg
SHTUNOT wrote on 4/22/2003, 3:49 PM
I guess what would have to happen then, is that when you hit the solo button it also mutes all of the other tracks and their pre-fader sends.
Greg---

Exactly. Solo should be solo. ;)

Ed.
Rednroll wrote on 4/22/2003, 4:33 PM
Greg M said:
"I think what you are describing is the same thing as a "pre-fader send". If it is, this is a standard configuration and not necessarily a bug."

This should be identical as a "pre-fader send". Now I would like to know what "standard configuration" you are referring too? My current hardware mixer has solo and mute buttons. The MUTE is located prior to "pre-fader send", thus when you press MUTE, it cuts the signal off from the pre-fader send. This is the same as any other hardware mixer I've used in the past, which include SSL,Neve,Sound Craft, Yamaha, API and a couple others. So I'm not sure what you mean by "standard configuration"? If anything, this is definately non-standard configuration from my experience.