It’s true that you want every event to be assigned to at least one bank. However, it’s equally true that assigning all events to the same bank is a bad idea, and there’s no way for FMOD Studio to guess how you want to distribute events among your banks.
Banks are a way of controlling how your game project loads content, and assigning all events to the same bank means you’d load all of your events into memory at the same time. Loading all your events at once consumes a lot of memory in all but the smallest of projects, so assigning all events to a single bank is usually bad practice - and automatically assigning all events to a specific bank actively encourages that bad practice. (We’ve actually seen this first-hand: Back in the days of FMOD Designer, assets were automatically assigned to banks - and we received complaints that this led to giant banks, and that picking individual assets out and reassigning them to smaller banks was a pain.)
So, we decided it was better to not assign events to banks by default, but to clearly indicate which events aren’t yet assigned to banks and to provide a search filter so that assigning events to banks can be as painless as possible.
That said, a copy of an existing event should be assigned to the same banks as the original. I’ve added that to our bug tracker, and it’ll be fixed in an upcoming release.
Incidentally, the master bank contains information about the project mixer, and so must be loaded into memory at all times. It’s therefore best to assign events to the master bank only if you need the ability to call upon them at a moment’s notice at all times.
Automatically creating a new track if you drag an asset below any existing tracks in the editor is already on our feature/improvement tracker, and will be considered and potentially scheduled at our next quarterly roadmap meeting.