Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Bus 32-64 Bug?

Step 1) In the Audio Preferences I have "64 Busses" unchecked
* When I open the "Audio Configuration" window from the Audio menu, I see:
In the "I/O Label" View: 32 busses
In the "All Components" View: 32 busses


Step 2) I go back to the Audio Preference and check the "64 Busses" (press re-launch CoreAudio)
When I open the "Audio Configuration" window from the Audio menu again, I see:
In the "I/O Label" View: 64 busses
In the "All Components" View: 64 busses


Step 3) I go back to the Audio Preference and uncheck the "64 Busses" (press re-launch CoreAudio)
When I open the "Audio Configuration" window from the Audio menu, I see:
In the "I/O Label" View: 32 busses
In the "All Components" View, 64 busse BUT: only Bus 1-32 have Insert an Output popup menus. Bus 33-64 are listet but have no popup menus


The Result (Bug?):
It seems that once I activated the 64 Busses and go back and deactivate it, Bus 33-64 "stick" in the "All Components" View. This would be not a big deal if it didn't had one annoying side affect: Now when I'm in the Mixer and want to select a Bus from the send popup menu, a looong list pops up with 64 busses. Bus 1-32 are active and bus 33-64 are inactive (grayed out). So even if you uncheck the 64 Busses in he Preferences, Logic remembers that you once had the 64 Busses checked and therefore keeps al l the busses in the list. That "long term memory" is stored with he song which means, once you have switched to 64 Busses, it will stick with your song and if that song is a very complex Autoload song, then you have no choice than to rebuild that song to avoid that long scrolling menu every time you want to select a send bus.

Screenshot:
http://homepage.mac.com/edgarrothermich/.Public/Screenshots/Bus1-64.png

Can anyone confirm that behavior and maybe have a cure how to get rid of the grayed out busses?

Thanks



G5 Dual 2.5G - 4.5GB RAM Mac OS X (10.4.7) Logic 7.2.2

Posted on Sep 19, 2006 10:52 AM

Reply
7 replies

Sep 19, 2006 11:11 AM in response to EdgarRothermich

No, it's not a bug I don't think, but I'd need to check and see if I can replicate it. If it is a bug, it looks like it's a display-only bug, so I don't think it's a big deal. Does it go away again if you restart Logic with 64-busses unchecked, or does the display do the same thing?

Note: Enabling 64-busses doesn't give you 64 busses, it gives you *the potential to have 64 busses*. In order to actually use 64 busses, you have to have bus or aux objects that correspond to the busses you are using.

So, if there are 64 busses in your list, but the last 32 of them are greyed out, it means you have the first 32 bus objects in your arrange, but not objects for busses 33-64. In order to use them, and have them not be greyed out in the list, you'd need to create objects for them.

Sep 19, 2006 11:16 AM in response to EdgarRothermich

Hi,

this is not a bug at all. You have created 64 "real" bus objects by performing the mentioned steps. Bus 33-64 are without "real" funtionality, if you uncheck the "64 Busses" checkbox.

If you want to get rid of them, just try to select all the unneeded bus objects in the environment and push backspace...

Logic Pro will not automatically delete unused or unneeded objects in the environment. If you are opening a song that is created on a different system or with a different audio hardware all existing objects will stay intact, even if they do not have any functionality on your system.

Best,
21th



Sep 19, 2006 11:23 AM in response to Bee Jay

I just checked, and I get the same behaviour you see.

It might just be a display thing - the 64 created busses initialise the menu list with 64 entries, and once you uncheck 64-busses, those lists stay 64-items long, with the last 32 greyed out.

I guess it could be classed as a bug, but a fairly minor (display-only) one.

Sep 19, 2006 12:21 PM in response to Bee Jay

I agree with Bee Jay that the following statement is not true

"You have created 64 "real" bus objects by performing the mentioned steps"

My understanding is that there is a fine distinction between "components" and "objects"

Components
They are visible in the Audio Configuration window and you can't change their availability in that window. What you see here i based on the following settings:
* Inputs: based on the selcted Audio Device (I usually call them "input busses", not to be confused with "Input Objects")
* Outputs: based on the selcted Audio Device (I usually call them "output busses" not to be confused with "Output Objects")
* Busses: 32 or 64 based on the Audio Preference Setting (I usually call them "aux busses" not to be confused with "Bus Objects" or "Aux Objects")
* Tracks: max 255, based on the Audio Preference Setting
* Instruments: always 128
* Aux: default 3, (max I think 255, if they have been created in the Environment)
* Rewire: based on installed Rewire applications

The Audio Configuration window shows you what components are available to you based on your setup. Those are the elements that are available for you to assign to audio Objects in the Environment

Objects
In the Environment, you create Objects and assign Components to it. Those Objects then can be assigned to sequencer tracks. You can delete all Objects in your Environment and still have the Components available.

But from here on, it gets really tricky:
When you create an audio Object and assign a Component to it (the Environment calls it "channel"), i.e. an Audio Instrument, then that Object becomes and Audio Instrument Object, using an Audio Instrument Component. Now yo can assign that Object to a Sequencer Track and play it. What happens when you delete this Object?
The Object is gone in the Environment and you can't use it in the Sequencer anymore. BUT, all the settings you made to that Object are still there, when assigning the same Audio Instrument Component to a new Audio Object.
So from no on it is more a question of the use of different terminology than what is right or wrong.

Is a Component an Object (because it seems to store all the information you made when you assigned it to an Object), or do you only call an Object what you create in the Environment.
How about a spiritual explanation of that issue: "The Component is the soul that can live without the Object (body), but a body can't live without a soul. When a soul (Component) reincarnates into a body (Object), it carries the imprint of the soul (Component). When the body dies (delete the Object), the soul (Component) will still live on until it reincarnates into a new body (Object) with its new experience from its previous lives (edits made to the previous Object)

Back to the "Logic" world.
The question is, when changing the settings in the Audio Preferences that affect the components (Bus, Tracks, Input, Output), should the Audio Configuration window follow and reflect that?
The way Logic behaves, it doesn't look like a bug, because it is consistent. If you change the Track number from 48 to 4, then the behavior with the "leftover" components and grayed out menu items is the same. Also, when you have an Audio Device selected with 20 Inputs/Outputs and then switch to the Built-in Audio Device.
Restart doesn't clean the leftovers, it seemed to be stored in the song file.

Back to the bus. If not a bug, at least it is annoying when you have to scroll to 64 item menu when you defined only 32.


G5 Dual 2.5G - 4.5GB RAM Mac OS X (10.4.7) Logic 7.2.2

Bus 32-64 Bug?

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.