Elektron Musical Instruments

Someone mentioned a SID console for Digital Performer. Where can I find
one?

                                        Thanks,
                                        Inform3r
-----------
http://www.inform3r.com

--- In elektron-users@egroups.com, Inform3r <inform3r@o...> wrote:
>     Someone mentioned a SID console for Digital Performer. Where
can 
I find
> one?
> 
>                                         Thanks,
>                                         Inform3r
> -----------
> http://www.inform3r.co

i was the one that mentioned making a console.  i can post it to the 
files section, i had thought of doing so but wasn't really sure if 
anyone was interested or not. it's set up to use the 100 or so cc's 
the sid responds to.  i'd REALLY like to add some of the Sys-Ex 
messages to it, but i can't quite get them to work.  i really only 
need an example of what a string for a particular parameter looks 
like.*this next part is directed towards anyone who would care to 
give some insight:)*  from the manaul this is what i gather it ought 
to look like.  on the bottom right of page 41 there starts a new 
paragraph which says *SYSEX Direct Program Message:  All direct 
program messages start with the general sidstation direct program 
sequence: F0 00 20 3c 01 00 04* <this i gather as being what every 
message ought to start out looking as with the appropriate parameter 
sequence added after it and ending with F7, right?>  The next part i 
am a little fuzzy about.  *The x/y-characters refers to data as 
specified in the function row.*  <at the end of every program
sequence 
there are these.. %0000yyyyy with a different amount of zero's and
y's 
for every program sequence.  i assume this is the function row?  or 
maybe the function row is what your seeing on the sidstation's actual 
display for that particular parameter, sort of like a reference to 
where this menu and parameter is located in the os?>  the next and 
last part of this paragraph just mentions using only the specified 
program sequences, if other bytes are used or added then this might 
make the sid get confused and wipe it's memory. <this makes perfect 
sense>  so in my crash course of sidstation Sys-Ex stringing, this is 
my example of what a message ought to look like for changing the 
resonance.  *F0 00 20 3c 01 00 04*(Direct Program Sequence)+ *00 18
0f 
04 F7*.  ok, i currently can't test this at the moment cause i've
sort 
of packed away my sidstation in lieu of me killing it, but i have 
tried this numerous times in the past with no success.  now in my 
sequencer, motu performer, it has a Sys-Ex editor incorporated into 
the console building menu which you can assign to any graphical 
object.  i'll give you an idea of it's layout.  the top and main 
portion of it contains a window where you enter your string(s).  on 
the right of this it has some boxes you can check for 
Checksumming options(which i'm not wholely understanding of).  these 
boxes you can click are as follows; Use Checksum, Straight Sum 
(CS=Databytes), and Sum to Zero (data bytes + CS=0.  Does the 
sidstation use any sort of checksumming?  if so, i guess i'll be
doing 
some research.  Underneath the Main Window is a pull down menu which  
houses the Byte Formats to use, these are; Midi(7bit), Nibble(4bit), 
ASCII, BCD 00-79 in one byte, and BCD one digit per byte.  i've only 
ever used the midi byte format with any of the consoles i've made,
and 
i assume this is what the sidstation uses, right?  to the right of 
this are some radio buttons; LSB->MSB, and MSB->LSB.  most
significant 
byte and least significant byte, that is about my understanding level 
of these.  it's either or so i can't go to wrong there.  now for the 
last part of this editor, it lists value(which i know is where you 
enter in what bytes in the string are used as the status bytes)i 
don't know how to tell for the sidstation, i can guess though 
reasonably well. underneath this is the box where you can type in the 
checksum if used.  i'm sorry if i bore anyone with this, but i asked 
this once before and didn't get any response.  so i figured i'd plug 
again with a more thorough question.  please anyone feel free to 
anwser!  i do read my manuals and the manual, for motu goes into
vague 
detail about it's Sys-Ex editor, it's assuming you know about midi
and 
it's various protocals.  which i have just kind of winged so far.  
thanks

---

christian


btw: the console i'm uploading was made with motu performer 6.03 but 
should i think work with earlier versions of performer and digital 
performer.  you ought to be able to open up the project file itself, 
or import the console with the load command.

Hey,

    I'll check out that console soon. Also, how do I dump all of my SID
patches into Digital Performer??

                                    Thanks,
                                    Inform3r
-----------
http://www.inform3r.com

welcome(in regards to your thanks),  in digi performer all you really 
have to make sure of is that the global or track filter isn't 
excluding Sys-Ex messages from being recorded or sent and that your 
bpm is set to something under 120.  on the sid in the first menu
after 
turning it on go to the midi menu, then to i think it's called patch 
dump where you'll be asked if you want to dump a single patch or the 
entire memory.  hit record on digi performer and the x button on the 
sid and off you go, it may take upwards of 20 measures.  trim the 
begining and end and there you have your patches all safe and sound.  
what i tend to do with sid patches is save each individual voice i'm 
going to be using and puttin them either into a particular project 
clipping window and or a performer clipping window as well as dumping 
the memory every so often(i've lost a lot of patches by not backing 
things up, including this last mishap of mine).  this way you 
allways have your patches at your fingertips, as you can drag and
drop 
whatever is in these windows into a project.  i find this very
usefull 
for archiving singular patches. 


---

christian

btw: nice pics up on your site, very slutty 80's synth pop like(i
hate 
labels, but hey it's sorta of fun creating them). no offense meant by 
that term.  

 


--- In elektron-users@egroups.com, Inform3r <inform3r@o...> wrote:
>     Hey,
> 
>     I'll check out that console soon. Also, how do I dump all of my 
SID

> patches into Digital Performer??
> 
>                                     Thanks,
>                                     Inform3r
> -----------
> http://www.inform3r.com

On Tue, 7 Nov 2000 sophalicus@... wrote:

> sequence: F0 00 20 3c 01 00 04* <this i gather as being what every 
> message ought to start out looking as with the appropriate parameter 
> sequence added after it and ending with F7, right?> 

Correct!

> The next part i am a little fuzzy about. 
> *The x/y-characters refers to data as specified in the function row.* 
> At the end of every program sequence there are these.. 
> %0000yyyyy with a different amount of zero's and y's for every program
> sequence. 
> i assume this is the function row?

Correct again. It says "Function" on the top of the row as well. :)

> or maybe the function row is what your seeing on the
> sidstation's actual display for that particular parameter, sort of
> like a reference to where this menu and parameter is located in the
> os?

No.

> the next and last part of this paragraph just mentions using only
> the specified program sequences, if other bytes are used or added then
> this might make the sid get confused and wipe it's memory. <this makes
> perfect sense> so in my crash course of sidstation Sys-Ex stringing,
> this is my example of what a message ought to look like for changing
> the resonance.  *F0 00 20 3c 01 00 04*(Direct Program Sequence)+ *00
> 18 0f 04 F7*.

That's right - and here is what the resonance DP-sequence would be:

(hex) $00 $18 $0f $04 $RS

Where $RS is the Resonance value between $00 and $0f. You can see that
only the lowest four bits are activefrom the %0000yyyy. This is binary,
and indicates that the highest four bits should always be zero, and the
lowest four (the yyyy) is the active value. The binary sequence beginning
with %0 shows you what range the parameter is in.

The full sequence for programming the resonance to 10 ($0a) would be:

F0 20 3c 01 00 04 00 18 0f 04 0a f7

> Underneath the Main Window is a pull down menu which houses the Byte
> Formats to use, these are; Midi(7bit), Nibble(4bit), ASCII, BCD 00-79
> in one byte, and BCD one digit per byte. 

Midi (7bit) is what you should use for most I guess.

> underneath this is the box where you can type in the checksum if used.  

There is no checksum used.

This SYSEX thing is simple, really. It's just about transmitting 7-bit
data in the way it is specified. An understanding of hexadecimal and
binary number systems will help though.

 //Daniel

thanks for the reply daniel, it's still not working though.  i 
realized i was missing a byte in the string and when added, nothing.  
the os still works on my sid so i dunno what the deal is.  maybe 
someone else would care to add some sysex functions to my console, so 
i can see what i'm doing wrong.  good day

---

christian