Yahoo Groups archive

Emu XL-7 & MP-7 User's Group

Index last updated: 2026-04-09 23:09 UTC

Message

Re: [xl7] Prodatum Revisited (2010)

2010-09-11 by simon wilkinson

Thanks, the folder edit prevents the program from crashing. I don't understand much (but then, I'm mainly a guitar player) about synths, so any suggestions as to how to get the most out of my P2K (it has 3 boards installed btw) and Prodatum would be gladly appreciated.

--- On Sat, 17/7/10, steve_the_composer <smw-mail@...> wrote:


From: steve_the_composer <smw-mail@...>
Subject: [xl7] Prodatum Revisited (2010)
To: xl7@yahoogroups.com
Date: Saturday, 17 July, 2010, 15:14


  



Some of you may remember that I did quite a bit of playing around with Prodatum a year or so ago. All of this was just testing. Now, I decided I want to try to make some serious use of Prodatum (v0.41) on my XPSP3 PC and ran into some issues that I thought I'd share.

(1) Prodatum causes error/lockup when opening a device 
The solution that worked for me: 
Delete (or rename as backup) the prodatum folder in the Application Data folder.

Mine was here:
C:\Documents and Settings\<USER>\Application Data\prodatum
where <USER> is the Windows Login name (aka profile name).

(2) Prodatum deletes your current settings and restores Multisetup 000
The only solution that I can see is to make sure you backup your current settings into a multisetup (possibly 000). 
I now recall discovering this before and doing extensive testing to track down the problem. In the process I discovered that the E-Mu boxes somehow save the settings that are in effect at power down. I seem to recall this is not 100% identical with what's stored in a multisetup. For more info, see the discussion in this thread:

http://launch.groups.yahoo.com/group/xl7/message/20136 .

Fortunately for me, I saved my settings (as a multisetup) last night before installing/firing up Prodatum v.0.41 today.

--Steve

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.