Forum

thanks for the help before, the garageband tutorial had the answers. now I would like to know if I can save the settings with the midi setup or do you have to always go thru all the steps to set the midi up every time. could I just save it as a user? I did tried that but it didn't seem to work. also I played my pico in record and the pitch bend and mod wheel go crazy can i stop that? I know it's because the keys on the pico are so sensitive

thanks for the help but I ment in eigen D. I don't use garageband. what I ment was after setting up the midi like the guy shows in the garageband tutorial could I save the midi settings in Eigen D and not have to go thru all that jazz to run the midi

The way I thought it worked was: You have a 'current setup', i.e. the one your playing with live. You can save that to a user setup, or you can load it from a user setup. When you exit EigenD, your 'current setup' is saved. When you start EigenD back up, it is restored.

So effectively, if you save your 'current setup' to user 1, then exit EigenD, then start EigenD again, it will restore your 'current setup'... which just so happens to match what you saved to user 1.

This way, you can load a setup, and if you mess it up you don't overwrite it unless you specifically save it again. So you could just load it again to revert to your saved version.

EigenD should always load the last setup that you were running, if it doesn't then that is a bug. Fzzzy, what version of EigenD are you running there? There have been a lot of changes to the load and save dialogues in the newer Unstable (now Testing) branch of EigenD. If you're running Testing then that's a bug we need to fix, and it woud be great to know.

Mike, I think that's a very sensible point about being able to specify which setup to load on start. We did have an automatic 'Setup Choose' dialogue pop up on every startup for a little while, but it was very annoying as a default action, so we took it out as we couldn't think of a nice way to make it work without bringing some level of inconvenience to normal startup (which can be headless remember, ie no screen, so automatically requiring user interaction on startup is now a big nono for us). We could probably add a little 'load this setup on startup' checkbox on the save setups dialogue, or some such but it did seem easier and more intuitive to always load the last loaded setup.

This is all made rather more awkward because the process of moving between setups while running currently has a nasty bug (which is in our sights) which causes big changes (as in between Pico and Alpha setups for example) to disappear off into the wilderness and never return. This will get fixed, as will adding some Pico + Alpha setups for those of you who have both (an increasing number interestingly) at some point soon.

John

John, I think that anything that gives us a choice can only be a positive change, so I vote for the adding of the option :)

Tene

+1 here, I almost always have to load the setup I saved before the next time I run EigenD

Imho it should actually default to loading the last saved setup and adding the 'always ask at startup' option should allow people that work differently to be satisfied also.

Exactly, Geert, last saved, last loaded, or ask would be a great preference choice. A similar discussion about what window(s) to open could be had.

I think that the existence of a screen (or not) is available from the OS so one could also consider allowing a secondary choice of last saved / loaded if no screen is detected (for those of us likely to forget to change the preference before heading out screenless with a preference set to ask)

EigenD is supposed to load the last Setup that you were running, not the last one you loaded, so saving a new setup ought to change the startup as well. I'll log this as a bug and we'll fix it, thanks for finding it. Regarding the other suggestions here, we're going to improve the options for startup sometime soon, probably as part of the next 'Unstable' series.

John

I think we're going to make this a user preference - it seems simpler to be able to select whether you want the choice or not. Mind you, a timeout would be a good idea anyway, for the occasion that one forgets to turn the selection off, goes to a gig without a screen and discovers that EigenD never starts...

John

"We have made a change to the auto loading behaviour upon EigenD startup.
In the past, the setup which automatically loaded on EigenD startup would always be the setup that you previously loaded.
The new behaviour means that when you save a user setup, it is selected as the setup which will automatically load when you next start EigenD."

hmmm... given that eigenD crashes when you try to change a setup, does this not imply that one can *only* load the most recently saved or build a new one from that starting point and then save it?

In other words, without fixing the crash problem, this would seem to make any older setups inaccessible since they cannot be loaded and one cannot restart and have them load. So the *only* setup that can be loaded is the last one saved and the only way to save a new one is to start with the loaded setup.