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

OK, as usual I've got some more questions and one correction.

First of all Sean (the Emu tech), I need to apologize about giving you 
some incorrect information in my last huge question post.  I had stated 
that moving in and out of Record modes caused the tracks to not get 
updated correctly between modes (ie, the wrong track was selected).  After 
playing around with this some more last night, I narrowed it down to being 
caused by track number changes made in the Preset view mode, NOT from 
entering a record mode.  Sometimes I'm doing a lot of things at once while 
writing, and it appeared to be the Record mode messing things up. Anyways, 
changing tracks while in Preset view, does NOT cause the proper track to 
be displayed if you go into Record mode, or back to your Pattern View. 
Just wanted to clear that up and see if it can be fixed in a future OS 
update.

Question:
Are there any plans to allow users to use E-Loader for saving and moving 
Presets around?  I think it's a great program for managing your patterns, 
and it would be great if we had the same features for managing Presets. 
Relying on sysex is slow and awkward at best.

Has anyone else had problems with E-Loader?  I can use it fine as soon as 
I power on my computer, but if I close it out, I can't restart the 
application later on.  It just freezes at the splash screen, and I have to 
restart my computer to get it to load properly again.  Is it just my set 
up, or have other seen this?  No big deal, just curious..

rEalm

erik_magrini@... wrote:

> Anyways, changing tracks while in Preset view, does NOT cause the
> proper track to be displayed

The number on the Preset screen is channel, not track.  Changing the
track also changes the channel because it is a direct mapping (unless
you're using multitracks).  Since channels are not mapped to tracks
(rather the other way around), changing the channel doesn't affect the
track.

-Aaron

Cool, glad it was just me being an idiot!  Thanx.

rEalm



Anyways, changing tracks while in Preset view, does NOT cause the proper 
track to be displayed

The number on the Preset screen is channel, not track.  Changing the track also changes the channel because it is a direct 
mapping (unless you're using multitracks).  Since channels are not mapped 
to tracks (rather the other way around), changing the channel doesn't 
affect the track. 
-Aaron

on 11/7/01 6:20 AM, erik_magrini@... at erik_magrini@...
wrote:

> Has anyone else had problems with E-Loader?  I can use it fine as soon as I
> power on my computer, but if I close it out, I can't restart the application
> later on.  It just freezes at the splash screen, and I have to restart my
> computer to get it to load properly again.  Is it just my set up, or have
> other seen this?  No big deal, just curious..


I'll guess that you are using a PC, and I'll guess further that you are
probably using WinME?

There are some known issues with Win* and quitting E-Loader. It's been a
tough one to tackle, but I just recently found what I believe may be the
cause. There will be a new version of E-Loader coming out soon - I can't say
exactly when yet - and hopefully it will fix those kinds of problems once
and for all.

Instead of restarting your computer you may be able to kill the process
using the Windows Task Manager. E-Loader may not show up in the Application
list, but if you see java.exe, javaw.exe, jview.exe or wjview.exe in the
Processes list you can try killing that (you'll only see one of these -
which one depends on which version of Java you are using).

Sorry I don't have any better workarounds for that specific problem right
now. Other than noting that it doesn't do that on my Win2000 system. I think
Win98/SE is more reliable than ME also. At least that's my experience in
regards to E-Loader.

Scott

Sorry, I should have clarified further on my set up:

Win98se
Echo Layla24
Athlon 1.0gHz Processor
Asus A7V133 MBD
256MB SDRAM PC133
Asus AGP-V7100 GeForce Video Card 16MB
Matrox 15.3GB & 30.7GB 7200RPM ATA100 HDD's
HP CD-RW 9140i 8x4x32

I tried initially to just kill it with Task Manager, and since I'm runnign 
such a lean set up (audio only PC) it's easy to see what shouldn't be 
running.  Still didn't work though, I had to restart again.  Thanx for the 
reply though!

rEalm




I'll guess that you are using a PC, and I'll guess further that you are
probably using WinME?

There are some known issues with Win* and quitting E-Loader. It's been a
tough one to tackle, but I just recently found what I believe may be the
cause. There will be a new version of E-Loader coming out soon - I can't 
say
exactly when yet - and hopefully it will fix those kinds of problems once
and for all.

Instead of restarting your computer you may be able to kill the process
using the Windows Task Manager. E-Loader may not show up in the 
Application
list, but if you see java.exe, javaw.exe, jview.exe or wjview.exe in the
Processes list you can try killing that (you'll only see one of these -
which one depends on which version of Java you are using).

Sorry I don't have any better workarounds for that specific problem right
now. Other than noting that it doesn't do that on my Win2000 system. I 
think
Win98/SE is more reliable than ME also. At least that's my experience in
regards to E-Loader.

Scott


To unsubscribe from this group, send an email to:
xl7-unsubscribe@yahoogroups.com

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

on 11/8/01 4:33 AM, erik_magrini@... at erik_magrini@...
wrote:


> Sorry, I should have clarified further on my set up:
> 
> Win98se 
> Echo Layla24 
> Athlon 1.0gHz Processor
> Asus A7V133 MBD 
> 256MB SDRAM PC133
> Asus AGP-V7100 GeForce Video Card 16MB
> Matrox 15.3GB & 30.7GB 7200RPM ATA100 HDD's
> HP CD-RW 9140i 8x4x32
> 
> I tried initially to just kill it with Task Manager, and since I'm runnign
> such a lean set up (audio only PC) it's easy to see what shouldn't be running.
> Still didn't work though, I had to restart again.  Thanx for the reply though!

I've had reports of problems with the Layla card, but I thought it was just
a total failure, and not a lockup at application quit time. I'll see if I
can get any more information about the Layla compatibility issues.

Otherwise maybe you can contact me off-list about some beta testing for the
possible fixes I found since E-Loader 1.0.

Scott