Another Gotchya, VSTi tracks always Armed!

Every time I load a VSTi along with it's outputs, the VSTi track is always Armed. I use separate Midi tracks and simply don't stop to think about the VSTi being Armed. My VSTi tracks are in the MCP so I don't notice they have midi on them. Consequently I end up with a bunch of midi recorded on the VSTi track before I finally notice it's Armed. This eventually interferes with my other midi tracks. The default for loading VSTi tracks should not be that they're Armed, if you truly want to record on them it's just a simple matter of hitting the Arm button. Heh heh, now there might be a way of turning that off and I will end up being embarrassed again.:eek: However, I've looked all over and can't find anything. :)

How about the "Build 16 channels of MIDI routing to this track" automatically disarming the VSTi track? I cannot think of any reason why I would want it to remain Armed.

^^^^ I meant that to be read as an FR - it doesn't do that at the moment. :)

Interesting. I always use right click add track with Virtual Instrument & never noticed it automatically arming record... I will go away and play. Dern! You are right! Next question is "did it always do this"? And this of course leads to: YES we need either a bugfix or a FR. I would regard this as a bug, even though it was doubtless coded deliberately to do this as default. IMO this is dangerous behaviour, bearing in mind how easy it is to just hit the record button to record something you WANTED recorded without checking what else is record enabled.

It always did that, yes. The idea is probably "If a user inserts a new VSTi, chances are that he wants to play/record it as the next step." Would you really insert a new VSTi, hit record, and expect to record all but the new instrument you just added? That sounds unlikely. I believe this action was created particularly with new users in mind. With the intent to easily add a simple (single in/single out on a single track) instrument and have it playable/record ready with no further ado. I like DarkStar's idea, because as soon as MIDI tracks to drive a VSTi are added, the record arm of the original VSTi track indeed is counter productive (the situation Tod describes in the OP). Easy workaround for people who don't like it this way, but still want to benefit from the other automatisms of this action: As the action ends up with the new track exclusively selected you could make a custom action adding either "Track: Set track record mode to none" (keeps the VSTi playable but won't record) or "Toggle record arm for selected tracks" and maybe "Track: Set track record monitor to off" and use that instead.

Good idea, Darkstar. Voted.

I cant replicate this on 4.62

I can ;) (For clarification, I have modified the context in the Issue Tracker.)

Hi DS, I'm glad you did this but you've stipulated that it should only dis-arm when you "Build 16 channels of MIDI routing to this track", right? Like I mentioned in the tracker, I never use "Build 16 channels of MIDI routing to this track", I simply load the VSTi, let it build it's outputs, and then set it so that it's in the MCP. From there I just start building my midi tracks. Until now, I've just never paid any attention to the fact that it was armed. :eek::) So it should be disarmed when it's loaded. I should add though, I'm going to be a lot more attentive in the future. :)

So ... "never RecArmed"?