SurroundByUs.com

I'll give that a try. Yes, I'm saving my layouts (frequently) and running Windows XP with A P4 processor.

I saved a layout with the program on (Xover set to 80), then closed Plogue. (When it asked to save when closing the program I said "no" since, after saving with it on, I now had the program turned off. That way it would not save again with the layout in the "Off" position. Make sense?) I opened the layout with notepad and found both the lines, exactly as you had typed (I did a 'copy' and 'find' for both). I checked the logs (there are two) and neither has any E:Ox - everything is I:Ox. I opened the layout again and the Xover frequency is back to 200 and Slice mode goes to Mute when I hit "On".

FYI the overall processing mode isn't saved with the layout. That is controlled by a Plogue preference, "process at start".

Also, if there are two logs it means at one point you had two instances of Plogue running. Let's make sure you don't have run running still. Either reboot or start the task manager and check for more that one (or one if you have closed plogue) plogue process. Sometimes they get stuck and hang around.

RE:Process at start..I knew that, just trying to cover all bases in figuring this problem out. I have that unchecked.
I did open the program twice one instance, not realizing I already had it open, and immediately closed the second session. I have re-booted several times since then (twice today, actually) and this problem with the Xover defaulting if the program is closed and Slice going to Mute mode when I hit On has been happening the entire time I have had the program. (That's why I thought they might be bugs or the way the program was purposely designed to work.) Do I need to delete one of the logs? (Biduke.log or Bidule_0.log)

No, you don't need to delete one of the logs.

Last question before reporting this as a bug on plogue.com; Other obvious setttings or changes in your layouts are getting saved and re-loaded?

Yes, all other settings, levels, processes, etc. do save and reload properly. Anybody else experiencing these oddities?

Update: Zeerround got me fixed up. Turned out I was making a stupid mistake. Problem solved. Thanks!!