previous by dateindexnext by date
previous in topictopic list 

Subject: RE: [chromapolaris] saving Polaris programs on a computer

From: Thomas Rizzi <rizzitech@...>
Date: 2009-07-30

Would MIDI OX help this situation?

--- On Wed, 7/29/09, Paul D. DeRocco <pderocco@...> wrote:

From: Paul D. DeRocco <pderocco@...>
Subject: RE: [chromapolaris] saving Polaris programs on a computer, and exporting them back
To: chromapolaris@yahoogroups.com
Date: Wednesday, July 29, 2009, 10:48 AM

 

> From: thomas wilk
>
> Thank you so much for your response it was very helpul. It has
> helped me solve one half of my problem.
>
> This is what is happening:
>
> I have a M-Audio interface between my Mac Laptop and my Polaris.
> The interface is connected to the MIDI IN and MIDI OUT and goes
> to my laptop via USB.
>
> I am running SysEx Librarian and I have it set up to record messsages.
>
> I select the program on the Polaris that I have manually created
> and then I hit LF, Cass., 12, and it sends program information to
> SysEx Librarian, which records the single program.
>
> Ok, so that much is great!
>
> Now, I have not been able to find a way to send the program back
> to the Polaris. For instance, if I make a program on A1, record
> it in SysEx, and then delete A1 on the Polaris, I cannot get the
> A1 that I have saved in SysEx back onto my Polaris.
>
> However, I have downloaded the patches from the Polaris site,
> (polprog1.syx, polprog2.syx, and deangelis.syx) and had SysEx
> send them to my Polaris and these files program all the program
> banks on my Polaris.
>
> I do not understand why I cannot receive SysEx files that were
> programs originally created on my Polaris, sent to SysEx, and
> then sent back to the Polaris.
>
> I have read through all the related sections on MIDI, computer
> interfacing, data streams, and the different toggle functions,
> but I am baffled.

Well, I don't have a Polaris up and running to try, but what's supposed to
happen, when you send the Sysex back into the Polaris, is that it gets
loaded into the main workspace controlling the sound. You then have to store
it manually.

If you have a way of viewing the .syx files in hex, and you're technically
inclined, it might be possible to figure out what's going on. I expect the
file containing the standard sounds contain Sysex messages that directly
access the stored programs, while the Sysex that you recorded from the
Polaris uses a different Sysex message which accesses the main workspace.

The best solution would probably be to get software tailored to Polaris,
instead of trying to get a generic program to do it for you. I notice that
while the MIDI Quest editor Frank mentioned is rather expensive because it's
universal, they also sell a cheap version called UniQuest for a single
instrument. Unfortunately, it's only available for Windows.

--

Ciao, Paul D. DeRocco
Paul mailto:pderocco@ix. netcom.com