Yahoo Groups archive

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

Archive for xl7.

Index last updated: 2026-03-30 01:19 UTC

Thread

More Prodatum questions

More Prodatum questions

2009-08-10 by gutman75

Greetings all,

I've been using hardware sequencers for years (Yamaha RM1X, then E-mu MP-7 and XL-7, then AKAI MPC1000), but now I want to base my workflow around PC running Reaper, with all hardware synths connected via Midiman MIDISport 4x4. The idea is to use the XL-7 as a 16-channel multitimbral synth, and to edit patches directly on the PC using Prodatum. However I'm having some problems making this setup work:

- when I switch Prodatum to Multi mode and select a channel (e.g. 1), all channel selection buttons (1-16) become disabled. Why does this happen? What is the correct way to use multi mode in Prodatum?

- how do you audition your patches while editing in Prodatum? Does it have some kind of MIDI thru, or do you use a separate program (like MIDI-OX) for that?

- is it possible to have both Reaper and Prodatum running, so I could hear the patches I'm making in project context? Of course, the MIDI driver must be multiclient for this to work, but if it weren't, I expect one of the programs to fail to open the MIDI port. As it is, Reaper appears to open all MIDI ports, but does not send anything to the XL-7. I need to experiment more to see if it's a strictly Reaper problem, or some kind of conflict between it and Prodatum.

- could my problems be related to the fact that the MIDI interface is connected via USB hub?

I'd like to thank Jan again for his great work on Prodatum. From user responses here on the list, it appears to work for everybody - so something must be wrong in my setup. Please help, I'm stuck! ;)

thanks in advance,
Boris.

Re: [xl7] More Prodatum questions

2009-08-10 by Jane

On 10.08.2009, at 13:22, gutman75 wrote:

>
> Greetings all,
>
> I've been using hardware sequencers for years (Yamaha RM1X, then E- 
> mu MP-7 and XL-7, then AKAI MPC1000), but now I want to base my  
> workflow around PC running Reaper, with all hardware synths  
> connected via Midiman MIDISport 4x4. The idea is to use the XL-7 as  
> a 16-channel multitimbral synth, and to edit patches directly on the  
> PC using Prodatum. However I'm having some problems making this  
> setup work:
>
> - when I switch Prodatum to Multi mode and select a channel (e.g.  
> 1), all channel selection buttons (1-16) become disabled. Why does  
> this happen? What is the correct way to use multi mode in Prodatum?
>
it disables channel selection to avoid accidential(?) double clicking  
which would result multiple preset requests. they get enabled when  
again when the preset arrived completely.
so you request a preset but dont receive a dump.
>
> - how do you audition your patches while editing in Prodatum? Does  
> it have some kind of MIDI thru, or do you use a separate program  
> (like MIDI-OX) for that?
>
there are various ways:
- midi thru (controller port in "Open device" dialog)
- press "C" to play a single C
- use the prodatum keyboard ("K" opens the keyboard)
- use the audit button in the channel program/section
>
> - is it possible to have both Reaper and Prodatum running, so I  
> could hear the patches I'm making in project context? Of course, the  
> MIDI driver must be multiclient for this to work, but if it weren't,  
> I expect one of the programs to fail to open the MIDI port. As it  
> is, Reaper appears to open all MIDI ports, but does not send  
> anything to the XL-7. I need to experiment more to see if it's a  
> strictly Reaper problem, or some kind of conflict between it and  
> Prodatum.
>
!!! use the drivers for your usb midi device (don't use the windows  
drivers, even if it "plug and played").
those will hopefully allow multiple clients.
>
> - could my problems be related to the fact that the MIDI interface  
> is connected via USB hub?
>
sure, if the hub is broken. otherwise no.
>
> I'd like to thank Jan again for his great work on Prodatum. From  
> user responses here on the list, it appears to work for everybody -  
> so something must be wrong in my setup. Please help, I'm stuck! ;)
>
i use e-mu xmidi usb devices and had to install the drivers from the e- 
mu site to get prodatum running along with cubase.
of course you know that you must connect your MP-7 bidirectionally.  
also note that some devices do not forward sysex messages when daisy  
chained. so try a direct bidirectional connection.
>
> thanks in advance,
> Boris.
>
cheers,
Jan
>
>

Re: More Prodatum questions

2009-08-10 by steve_the_composer

Hi, Boris.  

I have been trying to duplicate the disabled channel buttons problem using SONAR and Prodatum at the same time. I am using Beta 0.38 on an XP machine with Service Pack 3 with a P2500.

What version of Prodatum are you using? In earlier versions I experienced a lock up when switching channels and the buttons became disabled.

Are you using an external controller or just the XL-7 controls?

Also, see comments below.

--Steve


--- In xl7@yahoogroups.com, "gutman75" <bgutman@...> wrote:
>
> 
> Greetings all,
> 
> I've been using hardware sequencers for years (Yamaha RM1X, then E-mu MP-7 and XL-7, then AKAI MPC1000), but now I want to base my workflow around PC running Reaper, with all hardware synths connected via Midiman MIDISport 4x4. The idea is to use the XL-7 as a 16-channel multitimbral synth, and to edit patches directly on the PC using Prodatum. However I'm having some problems making this setup work:
> 
> - when I switch Prodatum to Multi mode and select a channel (e.g. 1), all channel selection buttons (1-16) become disabled. Why does this happen? What is the correct way to use multi mode in Prodatum?

STEVE: I could only duplcate this in Beta 0.38 by (1) powering down my E-Mu or (2) changing Prodatum a port that disabled two-way communication. Is there something in the software or interface setup that inhibits sysex flow?


> - how do you audition your patches while editing in Prodatum? Does it have some kind of MIDI thru, or do you use a separate program (like MIDI-OX) for that?

STEVE:
(1) Prodatum has an audition button that simulates pressing the audition button on the box.
(2) Prodatum also lets you assign/unassign a control device, such as a usb keyboard. If you have an external controller, this presents two options:
[A] Go to File --> Open Device and select whatever port you want to play thru to test your presets. So far as I can tell, Prodatum simply passes thru that data; it does not reassign the channel to coincide with with the editing channel. So if the device is set to transmit on Channel 1, you can only audition the preset on Channel 1.
[B] If Reaper has echo/thru, use that feature. SONAR lets me turn on and off echo/through on a track-by-track or track folder-by-track folder basis. Midi I/O is assigned for each track.
(3) Midi-ox (or other routing software/utility) might help if either of the above don't work. I don't think you need something like Midi-Yoke to do what you want to do, but that might be an option as well. 
(4) If the XL-7 is your only controller, I don't think you would need any of the above since the box would be playing its own sounds.
(Did I cover all the possibilities here?)
 
> - is it possible to have both Reaper and Prodatum running, so I could hear the patches I'm making in project context? 

STEVE: I have had SONAR, Prodatum, and e-loader [using the midi monitor) up and running at the same time; again, this is with Windows XP Service Pack 3.

> Of course, the MIDI driver must be multiclient for this to work, but if it weren't, I expect one of the programs to fail to open the MIDI port. As it is, Reaper appears to open all MIDI ports, but does not send anything to the XL-7. I need to experiment more to see if it's a strictly Reaper problem, or some kind of conflict between it and Prodatum.

STEVE: My guess is you need to figure out midi wiring, hardware configuration, and software configuration. I would assume Reaper lets you route data to different midi ports and channels, so it should let you send midi data to the XL-7. I would also assume that the latest drivers for your interface are multiclient, but it wouldn't hurt to check. Here's a quick test--get some software up and running and then use e-loader's midi monitor. For example can you record midi data into Reaper and see the data in midi monitor at the same time?

> - could my problems be related to the fact that the MIDI interface is connected via USB hub?

STEVE: It shouldn't.

> 
> I'd like to thank Jan again for his great work on Prodatum. From user responses here on the list, it appears to work for everybody - so something must be wrong in my setup. Please help, I'm stuck! ;)

STEVE: I would first make sure you have two-way midi communication between Prodatum and the XL-7 so you can edit presets on the basic channel and play them directly on the XL-7. (Be sure you don't have midi feedback loop set-up!!!) 

Next, I would boot up e-loader and use midi monitor to watch the data on the port with the XL-7. Open midi monitor up to make sure sysex it is sending sysex data. (Try sending a preset.)

Next, I would boot up Reaper (only after being sure this will not cause a midi feedback loop). Then I would check to make sure all data is flowing where you want. (You might want shut e-loader down and just check recording and playing midi data in Repear.)

If you can record channel 1 data and then play it back, I would then try lopping the playback and editing a preset with Prodatum.

To test this out, I routed all channels on a pattern to external [Pattern Edit --> CHANNEL ASSIGN Dest:ext] from the P2500 to SONAR with echo/thru on routed back to the P2500. At the same time Prodatum is open and I can edit presets in real-time. (Now I really wish Prodatum had a panel with Controllers M-->P!!!!!!!)

To isolate tracks, use mute buttons. Then edit your preset on the fly with Prodatum. When satisfied, save the preset using prodatum.

With the usb keyboard sending out on a non-used channel (in my test case, channel 16), I can basically use Prodatum to edit or even "play" a preset in realtime along with the pattern.

[DREAM: Jan adds additional functionality to Prodatum--real-time performance features, with Prodatum storage and recall capabilities--infinte preset banks stored on your computer, etc.]      

ADDED BONUS (in case you haven't figured this out, yet)
The Controllers sub-panel has a PLAY and a STORE button. You can play with the controllers all you want. When you press STORE, Prodatum puts them in the preset being edited as INITIAL CONTROLLER AMTs. (Of course, you still need to save the edited preset, if you want to keep it.) 

Thanks for posting the problem; I learned a whole bunch about how to integrate Prodatum. I had not really thought of it as a realtime controller, but I see how it can be used that way. 

Just wish there were a Command Station sub panel (for Controllers M-->P as well as Beats triggers, mutes, arps triggers, etc.). BTW, software buttons on paralleling the 16 Command Station buttons need not be limited to Command Stations. For example, Keith Young's Proteum has implemented Beats Buttons which give non-command station owners the funtionality of Beats Triggers.
 
Anyhow, Boris, I hope all this helps you integrate Prodatum into your setup. 

--Steve 

 
> thanks in advance,
> Boris.
>

Re: More Prodatum questions

2009-08-10 by steve_the_composer

--- In xl7@yahoogroups.com, Jane <rdxesy@...> wrote:

[snip]

> it disables channel selection to avoid accidential(?) double clicking  
> which would result multiple preset requests. they get enabled when  
> again when the preset arrived completely.
> so you request a preset but dont receive a dump.

STEVE: Oh, I thought he meant that they became permanently disabled (not momentarily diabled). Maybe Boris can clarify this.


> i use e-mu xmidi usb devices and had to install the drivers from the e- 
> mu site to get prodatum running along with cubase.

STEVE: Hmmmm. I have an Xmidi2x2 (came with Proteus X2). I downloaded the latest e-mu/creative drivers, but in SONAR that is the only interface that I have to re-select the ports every time I boot SONAR. What version are your E-Mu Xmidi drivers? (Mine say 7/19/05 version 5.12.1.2  .)

Best,
Steve

Re: More Prodatum questions

2009-08-10 by just john

Do you have an official bugs list/wish list posted anywhere?

I don't to repetitively harass you with my issues (non-functionality with FastLane/OSX, gratuitous reset of multisetup when connected to Win system (and maybe others)) over and over, but I also don't want you to forget them.

Prodatum as Real-time controller (Was: More Prodatum questions)

2009-08-10 by steve_the_composer

Some footnotes to using Prodatum as a real-time controller in combination with Command Station Sequencer

BACKGROUND:
Boris asked, Is it possible to have a PC sequencer and Prodatum running so that presets being edited can be heard in the context of a specific project?

I tested this out with SONAR and ended up seeing how Prodatum could be used as a real-time controller. Excerpt from previous post: 

> . . . I routed all channels on a pattern to external [Pattern Edit --> CHANNEL ASSIGN Dest:ext] from the P2500 to SONAR with echo/thru on routed back to the P2500. At the same time Prodatum is open and I can edit presets in real-time. (Now I really wish Prodatum had a panel with Controllers M-->P!!!!!!!)
 
> To isolate tracks, use mute buttons. Then edit your preset on the fly with Prodatum. When satisfied, save the preset using prodatum.

WARNING:
In a performance situation where the E-Mu sequencer is playing, do not select a new channel or a new preset. This will cause a whole batch of data to be sent to Prodatum causing the E-Mu sequencer to hiccup or spasm. 

CREATIVITY WITH ARPS:
With Jan's arp editor, you can "play" an arp in realtime. Turing end points on and off with a latched arp adds a new dimension to arp seqeuncing. WISH 1: assignable hot keys (PC keyboard, external controller, both) to program arp edits on the fly. WISH 2: multiple arp windows--maybe even enough to play E-Mu's 32 arps at the click of the mouse in my right hand and selectable arp editor focus from the PC keyboard in the left hand (if they all can't be in focus at the same time). (This would really unleash some of the untapped power in the non-Command Station P2K-based synths.)

You can really do some juxtaposition of odd meters just by turning those end points on and off as your pre-recorded patterns play. 

BTW, if you try this at home (specifically, routing a Command Station sequence's tracks externally through a PC sequencer which in turn echos the sequence back to the Command Station and then playing arps real-time via Prodatum), make sure arps/riffs are NOT being transmited externally.

--Steve

Re: [xl7] Re: More Prodatum questions

2009-08-11 by Jane

On 10.08.2009, at 21:23, just john wrote:

>
> Do you have an official bugs list/wish list posted anywhere?
>
this list and prodatum-users mailing list.
> I don't to repetitively harass you with my issues (non-functionality  
> with FastLane/OSX, gratuitous reset of multisetup when connected to  
> Win system (and maybe others)) over and over, but I also don't want  
> you to forget them.
>
>
i thought it was obvious. either your interface or the OS/interface  
combination cause the failure. if you can try another interface, do it.

Re: More Prodatum questions

2009-08-11 by just john

--- In xl7@yahoogroups.com, Jane <rdxesy@...> wrote:
>
> 
> On 10.08.2009, at 21:23, just john wrote:
> 
> >
> > Do you have an official bugs list/wish list posted anywhere?
> >
> this list and prodatum-users mailing list.
> > I don't to repetitively harass you with my issues (non-functionality  
> > with FastLane/OSX, gratuitous reset of multisetup when connected to  
> > Win system (and maybe others)) over and over, but I also don't want  
> > you to forget them.
> >
> >
> i thought it was obvious. either your interface or the OS/interface  
> combination cause the failure. if you can try another interface, do it.
>


How about the other thing, from when I plugged the same setup into a Windows laptop with your software, and the first thing it did upon recognizing my XL-7 was to reset my Multisetup parameters, including the Viewing Angle, which dictates the visibility of the LCD, based upon how one is looking at the machine.

What earthly reason would you have to do that?  Do I have to explain it further?


See? You need a list.

Re: [xl7] Re: More Prodatum questions

2009-08-11 by Jane

On 11.08.2009, at 03:41, just john wrote:

> --- In xl7@yahoogroups.com, Jane <rdxesy@...> wrote:
> >
> >
> > On 10.08.2009, at 21:23, just john wrote:
> >
> > >
> > > Do you have an official bugs list/wish list posted anywhere?
> > >
> > this list and prodatum-users mailing list.
> > > I don't to repetitively harass you with my issues (non- 
> functionality
> > > with FastLane/OSX, gratuitous reset of multisetup when connected  
> to
> > > Win system (and maybe others)) over and over, but I also don't  
> want
> > > you to forget them.
> > >
> > >
> > i thought it was obvious. either your interface or the OS/interface
> > combination cause the failure. if you can try another interface,  
> do it.
> >
>
> How about the other thing, from when I plugged the same setup into a  
> Windows laptop with your software, and the first thing it did upon  
> recognizing my XL-7 was to reset my Multisetup parameters, including  
> the Viewing Angle, which dictates the visibility of the LCD, based  
> upon how one is looking at the machine.
>
> What earthly reason would you have to do that? Do I have to explain  
> it further?
>
> See? You need a list.
>

you are right, its unexpected undocumented behaviour which is bad.
to get the setup names we need to load every multisetup when we first  
initialize (that's the way the device works). once finished we load  
the very first setup again (which is probably not the same that was  
loaded before).
so all you have to do is to reload your previous setup in the "M" tab  
or using the frontpanel.
before you ask, yes, we could remember the current setup before we  
initialize. but thats coding work which requires time...precious  
lifetime and this is simply not worth it. OTOH, love is to waste....so  
for prodatum, i chose to simply document this behaviour ^^)
jan

Re: More Prodatum questions

2009-08-11 by steve_the_composer

Maybe Aaron can clarify this, but I thought that for the most part, the power up state represents >>last used<< settings [at power down], not necessarily the settings from the last multisetup saved/restored.

--Steve 
  

--- In xl7@yahoogroups.com, Jane <rdxesy@...> wrote:
>
> 
> On 11.08.2009, at 03:41, just john wrote:
> 
> > --- In xl7@yahoogroups.com, Jane <rdxesy@> wrote:
> > >
> > >
> > > On 10.08.2009, at 21:23, just john wrote:
> > >
> > > >
> > > > Do you have an official bugs list/wish list posted anywhere?
> > > >
> > > this list and prodatum-users mailing list.
> > > > I don't to repetitively harass you with my issues (non- 
> > functionality
> > > > with FastLane/OSX, gratuitous reset of multisetup when connected  
> > to
> > > > Win system (and maybe others)) over and over, but I also don't  
> > want
> > > > you to forget them.
> > > >
> > > >
> > > i thought it was obvious. either your interface or the OS/interface
> > > combination cause the failure. if you can try another interface,  
> > do it.
> > >
> >
> > How about the other thing, from when I plugged the same setup into a  
> > Windows laptop with your software, and the first thing it did upon  
> > recognizing my XL-7 was to reset my Multisetup parameters, including  
> > the Viewing Angle, which dictates the visibility of the LCD, based  
> > upon how one is looking at the machine.
> >
> > What earthly reason would you have to do that? Do I have to explain  
> > it further?
> >
> > See? You need a list.
> >
> 
> you are right, its unexpected undocumented behaviour which is bad.
> to get the setup names we need to load every multisetup when we first  
> initialize (that's the way the device works). once finished we load  
> the very first setup again (which is probably not the same that was  
> loaded before).
> so all you have to do is to reload your previous setup in the "M" tab  
> or using the frontpanel.
> before you ask, yes, we could remember the current setup before we  
> initialize. but thats coding work which requires time...precious  
> lifetime and this is simply not worth it. OTOH, love is to waste....so  
> for prodatum, i chose to simply document this behaviour ^^)
> jan
>

Re: More Prodatum questions

2009-08-11 by steve_the_composer

I just did a quick test that would seem to confirm this:

(1) changed viewing angle
(2) powered down (front panel)
(3) powered up (front panel)

The viewing angle returned to the last used state!!!!

Second test:

(1) changed viewing angle, midi sysex delay, and midi merge settings.
(2) powered down (front panel, then back switch)
(3) powered up (back switch)

All 3 settings returned to the last used state!!!!

Third test:

(1) changed viewing angle, various midi settings
(2) powered down (back switch)
(3) powered up (back switch)

All midi settings returned to the last used state, except SEND MIDI SYSEX DATA preset.

So, the big question here is: Does Prodatum save the power-up/last used/current before handling the multisetups and then restore those settings?

Fourth test:
(1) changed viewing angle, various midi settings
(2) booted Prodatum

No change in current system settings.

(3) Pressed arrow on Load Multisetups to see what setups were listed there.

This immediately changed the settings.

***** SUGGESTION # 1: Have a warning when "load" drop down list is activated:****

Are you sure you want to wipe out your current system settings before saving them? YES    SAVE FIRST     CANCEL LOAD

(Please note: the multis listed are from when I tested Prodatum with the XL-1. The P2500 multi list was not refreshed. I had used Run Test to refresh the setup with the P2500. Not sure if forcing a full refresh by unchecking "Open device on startup" will refresh Multi list.)

(4) changed viewing angle and various midi settings
(5) refreshed with "Run test"
(6) viewing angle and various midi settings remained the same
(7) unchecked "Open device on startup"
(8) shut down and restarted Prodatum
(9) chose to open device

There was no forced reload. (Hmmmmm. Do I need to delete the configuration files to test this?) Most system settings seem to have remained in the last state; midi packet delay was changed to 50, however.

(10) Force initialization by concealing configuration data.

YUP!!! That did it: (1) refreshed Multisetup list and (2) wiped out power up/current/last state system settings

****** SUGGESTION # 2: Have a warning before Initializing: ******* 

WARNING: Prodatum will wipe out your current system settings unless you save them now as a multisetup. Options:
1. GO AHEAD WIPE EM OUT
2. CANCEL AND LET ME SAVE THEM MANUALLY
3. SAVE THEM FOR ME, OH GREAT PRODATUM*
(*either user selected slot or a choice of first available or last available empty slot--of course, if the list has not yet been generated, this would be a problem, unless Prodatum did a non-destructive read of the Multisetup names, if that's at all possible.)

In conclusion:
If my testing is correct, PRODATUM will definitely wipe out current system settings (a) at initializtion and (b) when the load drop down is activated.

I hope this helps.

--Steve


--- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@...> wrote:
>
> Maybe Aaron can clarify this, but I thought that for the most part, the power up state represents >>last used<< settings [at power down], not necessarily the settings from the last multisetup saved/restored.
> 
> --Steve 
>   
>

Re: More Prodatum questions

2009-08-11 by steve_the_composer

If I remember correctly an earlier version of the OS did not retain current state settings at power up, but this was ultimately fixed.  

> so all you have to do is to reload your previous setup in the "M"
> tab or using the frontpanel.

If my testing and analysis are correct, users of Prodatum will need to save their current state before the very first time they use Prodatum,  and any other time Prodatum needs to initialize.

Also, just looking at the load multisetup dropdown list will wipe out current state settings.

> before you ask, yes, we could remember the current setup before we  
> initialize. but thats coding work which requires time...precious  
> lifetime and this is simply not worth it. 

I have sung very high praises of Prodatum; however, (1) I believe these flaws are serious and (2) I don't think the solutions will take that much time. So far as I can see, what's needed are two warning dialogs with options.

Certainly you could try to write code to save current system settings, but I think providing warnings and giving users the options to either wipe out the current settings or save them manually before continuing to use Prodatum would be good.  

--Steve

If Aaron is following this thread, maybe he can chime in. Where are the current/last used settings stored? Clearly during the power up/boot cycle the OS pulls last used system settings from some place. Are these accessible through some undocumented sysex address? (Obviously they can be retieved and saved as individual parameters.)

Prodatum / Default Multisetup

2009-08-11 by massimo

According to the v2.0 manual -

"The XX-7 automatically loads Multisetup 00 on power up.
Use this location to store your default settings."

If you use Multi 00 then yes it will start with the last settings you used, otherwise it won't. ;)

Massimo

--- On Tue, 11/8/09, steve_the_composer wrote:
Maybe Aaron can clarify this, but I thought that for the most part, the power up state represents >>last used<< settings [at power down], not necessarily the settings from the last multisetup saved/restored.

--Steve

Re: Prodatum / Default Multisetup

2009-08-11 by steve_the_composer

Hi, Massimo.

This may have been true with an earlier OS (I am using OS2.0), but I believe it caused problems if users did not save the current state every time they powered down. (Hey, maybe that would be a good question for a poll: How often do you save your E-Mu's current system settings as a multisetup before powering down?) 

The test is easy enought to duplicate in about a minute or two. 
(1) Change a few system setting (eg, display angle and midi)
(2) Power down without saving the current setup as a multi 
(3) Power up (possibly after a minute or two) 

If you change the viewing angle to something that you need to lower or raise your head to see clearly, that would seem to be a quick answer.

--Steve

--- In xl7@yahoogroups.com, massimo <massenmedium@...> wrote:
>
> According to the v2.0 manual -
> 
> "The XX-7 automatically loads Multisetup 00 on power up.
> Use this location to store your default settings."
> 
> If you use Multi 00 then yes it will start with the last settings you used, otherwise it won't. ;)
> 
> Massimo
> 
> --- On Tue, 11/8/09, steve_the_composer <smw-mail@...> wrote:
> Maybe Aaron can clarify this, but I thought that for the most part, the power up state represents >>last used<< settings [at power down], not necessarily the settings from the last multisetup saved/restored.
> 
> --Steve
>

Re: Prodatum / Default Multisetup

2009-08-11 by steve_the_composer

Hey, Massimo, this is perplexing. After the power-up/boot sequence finishes, my P2500 does not show signs of having loaded Multi 00--even though the last version of the manual does indeed say it does this. Maybe its the P2500? Maybe its just my unit. 

During the second half of the power-up/boot sequence some settings are pulled from some place--perhaps some are pulled from multisetup 00 and then some last state system settings are restored on top of that.

The last manual (XL-7) also states:

Warning: MIDI Menu changes are automatically saved
when you exit the menu. If the power is turned off before you
exit the menu any changes you have made will be lost.

Warning: Global Menu changes are automatically saved
when you exit the menu. If the power is turned off before you
exit the menu any changes you have made will be lost.

So, maybe these are stored someplace special and are restored at power-up AFTER Multisetup 00 is loaded. If so, perhaps after power-up the E-Mu has the following:

Global Settings - from current state at power-down
MIDI Settings - from current state at power-down
Channel Preset Settings - from Multisetup 00
Sequencer - Sequence 000^0

(I haven't tested controller or arps & beats settings; no idea whether they are from last state at power-down or multi 00; might be good to know, though. )

--Steve_the_I_love_solving_perplexing_E-Mu_issues_but_really_wish_Aaron_could_clarify_this_one_so_I_don't_spend_any_more_time_testing_which_comes_from_where_when_guy

8-}



--- In xl7@yahoogroups.com, massimo <massenmedium@...> wrote:
>
> According to the v2.0 manual -
> 
> "The XX-7 automatically loads Multisetup 00 on power up.
> Use this location to store your default settings."
> 
> If you use Multi 00 then yes it will start with the last settings you used, otherwise it won't. ;)
> 
> Massimo
>

Re: [xl7] Re: More Prodatum questions

2009-08-11 by Jane

On 11.08.2009, at 06:23, steve_the_composer wrote:

> If I remember correctly an earlier version of the OS did not retain  
> current state settings at power up, but this was ultimately fixed.
>
> > so all you have to do is to reload your previous setup in the "M"
> > tab or using the frontpanel.
>
> If my testing and analysis are correct, users of Prodatum will need  
> to save their current state before the very first time they use  
> Prodatum, and any other time Prodatum needs to initialize.
>
> Also, just looking at the load multisetup dropdown list will wipe  
> out current state settings.
>
> > before you ask, yes, we could remember the current setup before we
> > initialize. but thats coding work which requires time...precious
> > lifetime and this is simply not worth it.
>
> I have sung very high praises of Prodatum; however, (1) I believe  
> these flaws are serious and (2) I don't think the solutions will  
> take that much time. So far as I can see, what's needed are two  
> warning dialogs with options.
>
> Certainly you could try to write code to save current system  
> settings, but I think providing warnings and giving users the  
> options to either wipe out the current settings or save them  
> manually before continuing to use Prodatum would be good.
>
> --Steve
>
> If Aaron is following this thread, maybe he can chime in. Where are  
> the current/last used settings stored? Clearly during the power up/ 
> boot cycle the OS pulls last used system settings from some place.  
> Are these accessible through some undocumented sysex address?  
> (Obviously they can be retieved and saved as individual parameters.)
>
wait, nothing gets wiped unless you played a lot with your device  
before you fire up prodatum *the first time*. but you will only loose  
your current setup.
anyway, it would probably be nice to put something like this into a  
README.txt:
"Before you fire up prodatum the first time, make sure to save your  
current multisetup if you did not already." or similar.
help on formulating this appreciated ;)

cheers,
Jan

Prodatum vs OSX

2009-08-11 by just john

--- In xl7@yahoogroups.com, Jane <rdxesy@...> wrote:
>
> 
> On 11.08.2009, at 03:41, just john wrote:
> 
> > --- In xl7@yahoogroups.com, Jane <rdxesy@> wrote:
> > >
> > >
> > > On 10.08.2009, at 21:23, just john wrote:
> > >
> > > >
> > > > Do you have an official bugs list/wish list posted anywhere?
> > > >
> > > this list and prodatum-users mailing list.
> > > > I don't to repetitively harass you with my issues (non- 
> > functionality
> > > > with FastLane/OSX, gratuitous reset of multisetup when connected  
> > to
> > > > Win system (and maybe others)) over and over, but I also don't  
> > want
> > > > you to forget them.
> > > >
> > > >
> > > i thought it was obvious. either your interface or the OS/interface
> > > combination cause the failure. if you can try another interface,  
> > do it


All the hardware, from USB cable thru the Fastlane thru the MIDI cables to the XL-7 worked with Prodatum on a Win machine.  (At least through the startup of Prodatum.  Couldn't go further without massively reconfiguring things to attach a USB hub to the Win machine's sole USB port, and attaching a scrollwheeled thing to the USB hub.)

And with that hardware connected to my OSX machine, other apps can recognize and deal with the XL-7, but Prodatum can't.

Re: [xl7] Prodatum vs OSX

2009-08-12 by Jane

On 11.08.2009, at 21:31, just john wrote:

> --- In xl7@yahoogroups.com, Jane <rdxesy@...> wrote:
> >
> >
> > On 11.08.2009, at 03:41, just john wrote:
> >
> > > --- In xl7@yahoogroups.com, Jane <rdxesy@> wrote:
> > > >
> > > >
> > > > On 10.08.2009, at 21:23, just john wrote:
> > > >
> > > > >
> > > > > Do you have an official bugs list/wish list posted anywhere?
> > > > >
> > > > this list and prodatum-users mailing list.
> > > > > I don't to repetitively harass you with my issues (non-
> > > functionality
> > > > > with FastLane/OSX, gratuitous reset of multisetup when  
> connected
> > > to
> > > > > Win system (and maybe others)) over and over, but I also don't
> > > want
> > > > > you to forget them.
> > > > >
> > > > >
> > > > i thought it was obvious. either your interface or the OS/ 
> interface
> > > > combination cause the failure. if you can try another interface,
> > > do it
>
> All the hardware, from USB cable thru the Fastlane thru the MIDI  
> cables to the XL-7 worked with Prodatum on a Win machine. (At least  
> through the startup of Prodatum. Couldn't go further without  
> massively reconfiguring things to attach a USB hub to the Win  
> machine's sole USB port, and attaching a scrollwheeled thing to the  
> USB hub.)
>
> And with that hardware connected to my OSX machine, other apps can  
> recognize and deal with the XL-7, but Prodatum can't.
>
please standby...
*** error: insufficient parameters.

sorry, does not compute.
jan

Re: Prodatum vs OSX

2009-08-12 by just john

--- In xl7@yahoogroups.com, Jane <rdxesy@...> wrote:
>
> 
> On 11.08.2009, at 21:31, just john wrote:
> 
> > --- In xl7@yahoogroups.com, Jane <rdxesy@> wrote:
> > >
> > >
> > > On 11.08.2009, at 03:41, just john wrote:
> > >
> > > > --- In xl7@yahoogroups.com, Jane <rdxesy@> wrote:
> > > > >
> > > > >
> > > > > On 10.08.2009, at 21:23, just john wrote:
> > > > >
> > > > > >
> > > > > > Do you have an official bugs list/wish list posted anywhere?
> > > > > >
> > > > > this list and prodatum-users mailing list.
> > > > > > I don't to repetitively harass you with my issues (non-
> > > > functionality
> > > > > > with FastLane/OSX, gratuitous reset of multisetup when  
> > connected
> > > > to
> > > > > > Win system (and maybe others)) over and over, but I also don't
> > > > want
> > > > > > you to forget them.
> > > > > >
> > > > > >
> > > > > i thought it was obvious. either your interface or the OS/ 
> > interface
> > > > > combination cause the failure. if you can try another interface,
> > > > do it
> >
> > All the hardware, from USB cable thru the Fastlane thru the MIDI  
> > cables to the XL-7 worked with Prodatum on a Win machine. (At least  
> > through the startup of Prodatum. Couldn't go further without  
> > massively reconfiguring things to attach a USB hub to the Win  
> > machine's sole USB port, and attaching a scrollwheeled thing to the  
> > USB hub.)
> >
> > And with that hardware connected to my OSX machine, other apps can  
> > recognize and deal with the XL-7, but Prodatum can't.
> >
> please standby...
> *** error: insufficient parameters.
> 
> sorry, does not compute.
> jan
>


Sorry, I thought you were the ones begging for beta testers.

I'll know better, next time.

Re: More Prodatum questions

2009-08-12 by gutman75

--- In xl7@yahoogroups.com, Jane <rdxesy@...> wrote:
> > - when I switch Prodatum to Multi mode and select a channel (e.g.  
> > 1), all channel selection buttons (1-16) become disabled. Why does  
> > this happen? What is the correct way to use multi mode in Prodatum?
> >
> it disables channel selection to avoid accidential(?) double clicking  
> which would result multiple preset requests. they get enabled when  
> again when the preset arrived completely.
> so you request a preset but dont receive a dump.

So, now I know what is happening, but I've no idea why ;)
How can I troubleshoot this problem? Is there any setting on the XL-7 I should check ? 

> of course you know that you must connect your MP-7 bidirectionally.  
> also note that some devices do not forward sysex messages when daisy  
> chained. so try a direct bidirectional connection.
> >
That's what I do. The Command Station is correctly identified, along with 4 ROMs in it. The handshake process ("Loading ROM data...") seems to pass fine. So it must be something else...

cheers,
Boris.

Re: More Prodatum questions

2009-08-12 by steve_the_composer

--- In xl7@yahoogroups.com, "gutman75" <bgutman@...> wrote:
>
> --- In xl7@yahoogroups.com, Jane <rdxesy@> wrote:
> > > - when I switch Prodatum to Multi mode and select a channel (e.g.  
> > > 1), all channel selection buttons (1-16) become disabled. Why does  
> > > this happen? What is the correct way to use multi mode in Prodatum?
> > >
> > it disables channel selection to avoid accidential(?) double clicking  
> > which would result multiple preset requests. they get enabled when  
> > again when the preset arrived completely.
> > so you request a preset but dont receive a dump.
> 
> So, now I know what is happening, but I've no idea why ;)

STEVE: Some users are impatient and might keep on clicking channel buttons repeatedly faster than Prodatum can request and receive data thereby causing Prodatum to be unable to handle the data. So, it makes sense that while data is updating Jan has the channels greyed out. Since Prodatum is open source, if the 1 second delay doesn't work with your performance/editing modality perhaps you can create a custom version that doesn't grey out the channels. (By any chance are you thinking about editing more than one preset at a time of different channels? This might be really great to do with 32 arps and 32 editing windows. I think Jan has put some much time into Prodatum, he really can't put any more time into programming advanced capabilities, but maybe he would be willing to advise others who want to try.) 

> How can I troubleshoot this problem? Is there any setting on the XL-7 I should check ?

STEVE: What are you trying to troubleshoot? So far as I can tell, Prodatum works; its just that when changing channels the channel selection mechanism is disabled for a brief time while data is updated. 

STEVE: (Unless I was right in the first place and you really were talking about Prodatum locking up in some way. If that's the issue, I just tried again to recreate the lock up with Beta 0.38 and couldn't. I tried everything--changing multi/omni/poly accepted/ignored settings in Prodatum and the front panel, turning midi data and program change settings to off, trying all the rechannelize settings, plus a few other things just to try to confuse Prodatum. I could not re-create a lock-up. I know that in earlier betas there was a lock-up problem when switching channels in Prodatum, but that bug is fixed in 0.38.)

> > of course you know that you must connect your MP-7 bidirectionally.  
> > also note that some devices do not forward sysex messages when daisy  
> > chained. so try a direct bidirectional connection.
> > >
> That's what I do. The Command Station is correctly identified, along with 4 ROMs in it. The handshake process ("Loading ROM data...") seems to pass fine. So it must be something else...

Hmmmmm. Does anything in your setup block sysex data? (Or did I ask about that before?)

Best wishes,
Steve
 
> cheers,
> Boris.
>

Re: [xl7] Re: Prodatum vs OSX

2009-08-12 by Jane

On 12.08.2009, at 16:26, just john wrote:

> --- In xl7@yahoogroups.com, Jane <rdxesy@...> wrote:
> >
> >
> > On 11.08.2009, at 21:31, just john wrote:
> >
> > > --- In xl7@yahoogroups.com, Jane <rdxesy@> wrote:
> > > >
> > > >
> > > > On 11.08.2009, at 03:41, just john wrote:
> > > >
> > > > > --- In xl7@yahoogroups.com, Jane <rdxesy@> wrote:
> > > > > >
> > > > > >
> > > > > > On 10.08.2009, at 21:23, just john wrote:
> > > > > >
> > > > > > >
> > > > > > > Do you have an official bugs list/wish list posted  
> anywhere?
> > > > > > >
> > > > > > this list and prodatum-users mailing list.
> > > > > > > I don't to repetitively harass you with my issues (non-
> > > > > functionality
> > > > > > > with FastLane/OSX, gratuitous reset of multisetup when
> > > connected
> > > > > to
> > > > > > > Win system (and maybe others)) over and over, but I also  
> don't
> > > > > want
> > > > > > > you to forget them.
> > > > > > >
> > > > > > >
> > > > > > i thought it was obvious. either your interface or the OS/
> > > interface
> > > > > > combination cause the failure. if you can try another  
> interface,
> > > > > do it
> > >
> > > All the hardware, from USB cable thru the Fastlane thru the MIDI
> > > cables to the XL-7 worked with Prodatum on a Win machine. (At  
> least
> > > through the startup of Prodatum. Couldn't go further without
> > > massively reconfiguring things to attach a USB hub to the Win
> > > machine's sole USB port, and attaching a scrollwheeled thing to  
> the
> > > USB hub.)
> > >
> > > And with that hardware connected to my OSX machine, other apps can
> > > recognize and deal with the XL-7, but Prodatum can't.
> > >
> > please standby...
> > *** error: insufficient parameters.
> >
> > sorry, does not compute.
> > jan
> >
>
> Sorry, I thought you were the ones begging for beta testers.
>
> I'll know better, next time.
>
>
no offense included, its just that i don't have an answer because im  
not into all the poissibilities of this universe. not your fault man.
Jan

Re: More Prodatum questions

2009-08-13 by gutman75

--- In xl7@yahoogroups.com, "steve_the_composer" <smw-mail@...> wrote:
> > So, now I know what is happening, but I've no idea why ;)
> 
> STEVE: Some users are impatient and might keep on clicking channel buttons repeatedly faster than Prodatum can request and receive data thereby causing Prodatum to be unable to handle the data. So, it makes sense that while data is updating Jan has the channels greyed out. Since Prodatum is open source, if the 1 second delay doesn't work with your performance/editing modality perhaps you can create a custom version that doesn't grey out the channels.
Hmm, never thought of tinkering with Prodatum source, but it's nice to have the possibility. Anyway, the real question for me is - why doesn't my Command Station respond properly?
> 
> > How can I troubleshoot this problem? Is there any setting on the XL-7 I should check ?
> 
> STEVE: What are you trying to troubleshoot? So far as I can tell, Prodatum works [...]
Exactly! That's what I wrote in my first post - I know Prodatum works for others, so the problem must be on my end. I'm asking in hope that Jan or other Command Station gurus might have an idea why it could be misbehaving like that.

Actually, I had an idea yesterday, haven't checked it though... if it works, I'll let you know!

> STEVE: Does anything in your setup block sysex data?
If that was the case, I suppose the Command Station would not be recognized at all.

Re: More Prodatum questions

2009-08-13 by steve_the_composer

I would really like to help you find a solution, but it is still very unclear what the problem is. I have posed several diagnostic leads but unless I missed it (sorry if I did), I have not seen answers to these questions:

(1) Do the Channel Selection Buttons:
---(A) get greyed out [disabled] when you press one of them and stay greyed out, or
---(b) get greyed out momentarily (approx. 0.5 to 1.5 seconds) and then function normally?

(2) What version of Prodatum are you using?


> . . . the real question for me is - why doesn't my Command Station respond properly?

> > > How can I troubleshoot this problem? Is there any setting on the XL-7 I should check ?
> > 
> > STEVE: What are you trying to troubleshoot? So far as I can tell, Prodatum works [...]

> Exactly! That's what I wrote in my first post . . .

This is one of the issues you mentioned in your first post:

> - when I switch Prodatum to Multi mode and select a channel (e.g. 1), all channel selection buttons (1-16) become disabled. Why does this happen? What is the correct way to use multi mode in Prodatum?

Jan answered that question assuming you meant "momentarily become disabled." I then replied, "Oh, I thought Boris meant "permanently become disabled." (If you clarified which you meant, I apologize in advance; I didn't see it.)

In response to Jan, you did say:
>So, now I know what is happening, but I've no idea why ;)

This confused me, because Jan explained quite clearly why the Channel Select Buttons greyed out [became disabled] momentarily. So, in my reply, I explained it further.

You also said in reply to Jan:
>How can I troubleshoot this problem? 
If you meant "momentarily" instead of "permanently," THERE IS NO PROBLEM TO TROUBLE SHOOT.

I suppose that

IF you are saying that: 

(1) the channel buttons work before you change Prodatum to Multi 
(2) you can edit presets in Prodatum before you change Prodatum to Multi
(3) when you press Multi on Prodatum and then Prodatum locks up and no longer functions.

THEN:
(4) DON'T PRESS MULTI ON PRODATUM!!!!!!!

OR:

IF you are not trying to say (1), (2), and (3)

THEN: 

IF you want others to try to help

Tell them something more than "When I press M [Multi button on Prodatum] and then press CB [Channel Button], CBs become diabled."

Getting back to your original request for help on this and other issues (http://launch.groups.yahoo.com/group/xl7/message/20126).

(1) Can you now play which ever device you list as a control device to audition the presets being edited? 
(2) Did you successfully figure out how to integrate the XL-7, Prodatum and Reaper?

Just curious how you have faired with these other issues because you haven't said anything them. Did you try any of the solutions posed? 

Good luck to you. 

--Steve

Re: [xl7] Re: Prodatum / Default Multisetup

2009-08-13 by massimo

Yes Steve you are right, it's certainly not as straightforward as Multi 00 just being loaded on startup. I tried making some changes in Global and restarted the machine and it had retained those settings, while subsequently restoring Multi 00 then reinstated the last actually saved settings, if you see what I mean. So the current global settings at least are indeed stored seperately and restored on startup.

Bit confusing maybe, and it would be good if someone could fully clarify this, but tbh I haven't got the inclination to look into it in much detail right now and it's not been an issue when using the XX-7 so far.

Maybe you've thrashed this out a bit more in subsequent posts anyway.

Massimo

--- On Tue, 11/8/09, steve_the_composer wrote:

From: steve_the_composer
Subject: [xl7] Re: Prodatum / Default Multisetup
To: xl7@yahoogroups.com
Date: Tuesday, 11 August, 2009, 4:16 PM

Hey, Massimo, this is perplexing. After the power-up/boot sequence finishes, my P2500 does not show signs of having loaded Multi 00--even though the last version of the manual does indeed say it does this. Maybe its the P2500? Maybe its just my unit.

During the second half of the power-up/boot sequence some settings are pulled from some place--perhaps some are pulled from multisetup 00 and then some last state system settings are restored on top of that.

The last manual (XL-7) also states:

Warning: MIDI Menu changes are automatically saved
when you exit the menu. If the power is turned off before you
exit the menu any changes you have made will be lost.

Warning: Global Menu changes are automatically saved
when you exit the menu. If the power is turned off before you
exit the menu any changes you have made will be lost.

So, maybe these are stored someplace special and are restored at power-up AFTER Multisetup 00 is loaded. If so, perhaps after power-up the E-Mu has the following:

Global Settings - from current state at power-down
MIDI Settings - from current state at power-down
Channel Preset Settings - from Multisetup 00
Sequencer - Sequence 000^0

(I haven't tested controller or arps & beats settings; no idea whether they are from last state at power-down or multi 00; might be good to know, though. )

--Steve_the_I_love_solving_perplexing_E-Mu_issues_but_really_wish_Aaron_could_clarify_this_one_so_I_don't_spend_any_more_time_testing_which_comes_from_where_when_guy

8-}



--- In xl7@yahoogroups.com, massimo wrote:
>
> According to the v2.0 manual -
>
> "The XX-7 automatically loads Multisetup 00 on power up.
> Use this location to store your default settings."
>
> If you use Multi 00 then yes it will start with the last settings you used, otherwise it won't. ;)
>
> Massimo

Re: Prodatum / Default Multisetup

2009-08-13 by steve_the_composer

Thanks for the confirmation, Massimo!! When I get a chunk of time, I may just make a spreadsheet to track >>all<< the Global, MIDI, arp, controller, and channel/preset parameters and sort which comes from where.** From the testing so far, I have a pretty good idea of most of the parameters. Based on the manual's warning to make sure to exit the MIDI and Global menus before powering down, my guess is that's the bulk of what doesn't get restored from the multi.

Maybe this explains some of those, "This is not the way I thought it was yesterday" mysteries.

--Steve

**Of course if Aaron knows and can spare me alot of testing, that would be great!!!!


--- In xl7@yahoogroups.com, massimo <massenmedium@...> wrote:
>
> Yes Steve you are right, it's certainly not as straightforward as Multi 00 just being loaded on startup. I tried making some changes in Global and restarted the machine and it had retained those settings, while subsequently restoring Multi 00 then reinstated the last actually saved settings, if you see what I mean. So the current global settings at least are indeed stored seperately and restored on startup. 
> 
> Bit confusing maybe, and it would be good if someone could fully clarify this, but tbh I haven't got the inclination to look into it in much detail right now and it's not been an issue when using the XX-7 so far.
> 
> Maybe you've thrashed this out a bit more in subsequent posts anyway.
> 
> Massimo
> 
> --- On Tue, 11/8/09, steve_the_composer <smw-mail@...> wrote:
> 
> From: steve_the_composer <smw-mail@...>
> Subject: [xl7] Re: Prodatum / Default Multisetup
> To: xl7@yahoogroups.com
> Date: Tuesday, 11 August, 2009, 4:16 PM
> 
> Hey, Massimo, this is perplexing. After the power-up/boot sequence finishes, my P2500 does not show signs of having loaded Multi 00--even though the last version of the manual does indeed say it does this. Maybe its the P2500? Maybe its just my unit. 
> 
> During the second half of the power-up/boot sequence some settings are pulled from some place--perhaps some are pulled from multisetup 00 and then some last state system settings are restored on top of that.
> 
> The last manual (XL-7) also states:
> 
> Warning: MIDI Menu changes are automatically saved
> when you exit the menu. If the power is turned off before you
> exit the menu any changes you have made will be lost.
> 
> Warning: Global Menu changes are automatically saved
> when you exit the menu. If the power is turned off before you
> exit the menu any changes you have made will be lost.
> 
> So, maybe these are stored someplace special and are restored at power-up AFTER Multisetup 00 is loaded. If so, perhaps after power-up the E-Mu has the following:
> 
> Global Settings - from current state at power-down
> MIDI Settings - from current state at power-down
> Channel Preset Settings - from Multisetup 00
> Sequencer - Sequence 000^0
> 
> (I haven't tested controller or arps & beats settings; no idea whether they are from last state at power-down or multi 00; might be good to know, though. )
> 
> --Steve_the_I_love_solving_perplexing_E-Mu_issues_but_really_wish_Aaron_could_clarify_this_one_so_I_don't_spend_any_more_time_testing_which_comes_from_where_when_guy
> 
> 8-}
> 
> 
> 
> --- In xl7@yahoogroups.com, massimo <massenmedium@> wrote:
> >
> > According to the v2.0 manual -
> > 
> > "The XX-7 automatically loads Multisetup 00 on power up.
> > Use this location to store your default settings."
> > 
> > If you use Multi 00 then yes it will start with the last settings you used, otherwise it won't. ;)
> > 
> > Massimo
>