Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[d_pert]

Hi,

Is there a way to set initial/startup Audio View Scheme?

I have a number of saved view schemes (*.jvi) and when I "Add" (import), there doesn't seem to be much logic as to which one is designated the initial Scheme when/if I go out of Audio (e.g., to Playing Now) and then return to Audio, or restart the application.

If I delete / re-add / delete / re-add / delete / re-add all the Schemes is some randomized approach, I can eventually get the Scheme I want to "stick", as "default", as long as I don't add / delete any other Schemes.  

Thanks!

[kensn]

If you are looking to have MC start in a particular view use:
Tools - Options - Startup

Under Startup Interface select the Location you want. Make sure your view is first on the list in the tree.

Ken

[d_pert]

The Options > Start-up only determines that I want "Audio" (in general) as the start-up place.

To your point about positioning the favoured Scheme at the top of the list:

- I cannot find a way to "order" the Schemes list under "Audio"

- The de facto "start-up" Scheme can end up being any Scheme at any point in the list, with no apparent logic as to what makes MC choose which one, at which position, under which circumstances (just try adding and deleting a few different schemes, leaving and returning to that part of the tree between each step and you'll see what I mean)

Thanks!

[d_pert]

Have been digging and searching further re: this issue...

I still cannot see either:

a) a feature/setting anywhere to explicitly set the preferred start-up Scheme

b) any logic to how MC arbitrarily selects its start-up scheme from the ones added, based on order or "Adding", "Deleting", or naming (e.g. alpha), or some kind of "stack" logic; it's not simply "the top one" and seems to be randomly changed every time any change is made to the list

Is this possibly an accidental omission or oversight in the application design?
 ?

[d_pert]

Three years later ... and I just hit the exact same issue. Has there been any development on this since 2014 / v.19?

Thanks.