Yahoo Groups archive

Elektron Musical Instruments

Index last updated: 2026-04-28 23:22 UTC

Thread

Re: [elektron] SIDStation OS version & stuff

Re: [elektron] SIDStation OS version & stuff

2001-06-05 by Nick

I've done resets so many times already trying to get it' SysEx
All-Patches dump to work right without corrupting it's own entire RAM.
Though, when I try sending the Ninja Patch .syx file (from sidstation's
web site in support section), that too makes the SIDStation lock up and
crash and display weird icons on the LCD.

Methinks they didn't bug test this particular make of SIDStation before
sending it out =/

-nick

Daniel Hansson wrote:
Show quoted textHide quoted text
>> Don't downgrade - it won't help. The R34 has some code that gives
> compatibility with a new type of display used in later SidStations. the
> upgrade is for people with older SidStations with old OS:es. As a general
> notice - downgrading or reinstalling OS:es will never help, but is a
> dangerous operations which involves erasing the flash.
> 
> Try resetting the memory and start from there. There is probably some
> weird patch lurking in the memory somewhere. And don't be alarmed if a
> empty memory gives short memory dumps. An empty patch location only takes
> a few bytes.


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

Re: [elektron] SIDStation OS version & stuff

2001-06-05 by Joeri Vankeirsbilck

Hi,

> Well I e-mailed Elektron's support addy and they're taking literally
> -forever- to reply, so I thought I'd ask here from people who may have
> had similar problems w/ the SIDStation.

I think they're giving absolute priority to finishing the Machinedrum.... or
their email is down.

> My SIDStation came with OS v1.11 R34, but the web page says the latest
> is OS 1.1 R33.

I just checked: mine has v1.1 R33

> ) SysEx dump of ALL PATCHES sends less than 1kb of data.  When it does
> this, the memory is corrupted (all patches in SIDStation's memory are
> gone and it locks up, have to reset)

Weird.

> All other SysEx files
> (from their webpage for example) that contain "all patches" are roughly
> 20-35kb files.

If I remember well, a patch is about 340 bytes. There are 100 patch memories
available. That makes 34kb.

> 2) When I try playing a sequence of different patches (even at slow
> speeds), it sounds muffled.  This may be to do with the SID chip, or
> not.  I try basic sequences alternating between my BD, hihat, and snare
> patches, and when it's sequenced like that and switches between patches
> the patches sound nothing like they do when you play one of them alone.

??? I don't understand how you're playing sequences of several instruments.
Remember the SidStation either has 1 voice (3oscs) or 3 voices (1osc).

> Anyone else had these problems?

Not me.

> Would downgrading to OS v1.1 R33 at
> least fix problem #1?

You could try.

> Is it even possible to downgrade the SIDStation's
> OS with a lower version?

I'm not sure, but I don't see why I wouldn't be possible.

Bye,
Joeri

--
Joeri Vankeirsbilck
joeri@...

Belway Productions      -     http://www.belway.com
List-admin   Logic-users/SoundD*ver-users/Logic-TDM

Re: [elektron] SIDStation OS version & stuff

2001-06-05 by Janne G-son Berg

On Tue Jun 05 2001, Joeri Vankeirsbilck <joeri@...> wrote:

> I think they're giving absolute priority to finishing the Machinedrum.... or
> their email is down.

I think it is the MD...

> > 2) When I try playing a sequence of different patches (even at slow
> > speeds), it sounds muffled.  This may be to do with the SID chip, or
> > not.  I try basic sequences alternating between my BD, hihat, and snare
> > patches, and when it's sequenced like that and switches between patches
> > the patches sound nothing like they do when you play one of them alone.
> 
> ??? I don't understand how you're playing sequences of several instruments.
> Remember the SidStation either has 1 voice (3oscs) or 3 voices (1osc).

He is switching patches via midi if I understand correctly.

Patch 1: BD
Patch 2: CH
Patch 3: SD
Patch 1: BD
Patch 4: OH
Patch 1: BD
Patch 3: SD
Patch 2: CH

/Janne

-- 
Janne G:son Berg, d3berg@...   http://www.dtek.chalmers.se/~d3berg
                          Prima liv med ungdomskorpen!

Re: [elektron] SIDStation OS version & stuff

2001-06-05 by Joeri Vankeirsbilck

> He is switching patches via midi if I understand correctly.
> Patch 1: BD
> Patch 2: CH
> Patch 3: SD
> Patch 1: BD
> Patch 4: OH
> Patch 1: BD
> Patch 3: SD
> Patch 2: CH

Then I wouldn't be surprised if the SidStation's processor is simply too slow for
that!

Bye,
Joeri

--
Joeri Vankeirsbilck
joeri@...

Belway Productions      -     http://www.belway.com
List-admin   Logic-users/SoundD*ver-users/Logic-TDM

Re: [elektron] SIDStation OS version & stuff

2001-06-05 by Daniel Hansson

On Tue, 5 Jun 2001, Joeri Vankeirsbilck wrote:

> > He is switching patches via midi if I understand correctly.
> > Patch 1: BD
> > Patch 2: CH
> > Patch 3: SD
> > Patch 1: BD
> > Patch 4: OH
> > Patch 1: BD
> > Patch 3: SD
> > Patch 2: CH
>
> Then I wouldn't be surprised if the SidStation's processor is simply too slow for
> that!

It's more probable that the patches are using different filters. The SID
doesn't like switching them - that's why you hear popping sounds when you
choose patches with different filter settings. Changing patches should
give immediate results if they use the same filter settings.

Don't downgrade - it won't help. The R34 has some code that gives
compatibility with a new type of display used in later SidStations. the
upgrade is for people with older SidStations with old OS:es. As a general
notice - downgrading or reinstalling OS:es will never help, but is a
dangerous operations which involves erasing the flash.

Try resetting the memory and start from there. There is probably some
weird patch lurking in the memory somewhere. And don't be alarmed if a
empty memory gives short memory dumps. An empty patch location only takes
a few bytes.

Daniel

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.