MOTM

From: James Elliott <johans121@...>
To: motm@yahoogroups.com
Sent: Wednesday, June 18, 2008 12:56:03 AM
Subject: Re: [motm] 650 OS Update Status....


Here's the details of a bug that I turned in last year which causes my 650 to "crash".

Hopefully this gets addressed in the next update as it is frustrating to no end.

-Jim




Paul, you've asked the list to send you any errors / descriptions of funky behavior that we encounter. I've already sent you a general description of these problems on 10/13, and I will go into more detail here.

General Problem: My 650 quits responding to midi when I send midi cc's to control aux1. When I say quit responding I mean that the output jacks do not transmit a signal - the midi LED still responds to midi. One of two things happens once the 650 is in this state.

1) If I perform the following actions, then the 650 begins to respond to midi again (however it will lock up again if I send midi cc's to aux1)
-Press "ESC"
-Scroll to, and then select, "Module Actions"
-Scroll to, and then select, "Load Patch"
-and finally, load a patch

2) If I don't follow the steps above, I get various assert errors depending on different buttons that I press
-L612: I get this error when I press "Enter" after a lockup
-L2039: When I press "Inc" after a lockup
-L2167: When I press "dec" after a lockup
-L548: First I press "ESC", which allows me to scroll through the top level menu, then press "Enter" on any of the second level menu items 

My 650 is setup as follows:
-Global options:
1) Voice Type - 1/1/1/1
2) CtrlMidi Chan - 1
3) Trig PWM - 10ms
4) VelScale - 8 Volts
5) Backlight - Auto
6) TunTable - 12 Tone
7) Note Inv - Off
8) Priority - LastNote
9) Clock - Internal
10) IClk BPM - 120.0
11) Midi Clk - Transmit
12) Patch Rx - Disabled (I also tried enabled, whatever that does?)
13) SysexSys ID=Global

-VoiceGroup 1 Settings:
1) VG1 Midi Chan - 1
2) VG1 Allc - Solo
3) VG1Glide - Off
4) VG1PBend - 24
5) VG1GType - Normal
6) VG1 V/T - Velocity
7) VG1 Aux - CC12 (Tried others as well with the same issue resulting)
8) VG1AuxSc - 8 Volts

-VoiceGroups 2 - 4 are set up exactly like group 1 except that the PBends are set to 0, and the Aux Midi CC's are set to different values (13, 14, 15).

-Both Arps are turned off.

**This also happens in other other voice modes as well 4/poly1, 4/poly2, 2/2/poly1, etc.......

I really hope this gets fixed in the next patch release because having one of the 4 aux outs messed up sucks. Other than this problem, the 650 is a pretty cool module.

-Jim


----- Original Message ----
From: Paul Schreiber <synth1@...>
To: motm@yahoogroups.com; James Elliott <johans121@...>
Sent: Wednesday, June 18, 2008 12:20:53 AM
Subject: Re: [motm] 650 OS Update Status....


Hopefully Jeffrey will step in and give us an update. I have not heard from 
him in a while.

Meanwhile: the majority of the issues are using external clock to drive the 
arpeggiators and using Voice Group 1/1/1/1 (4 independent MIDI channels). 
The Voice Group
bug seems to be if you change from/into 1/1/1/1 mode. I think if you *start* 
there (the default patch) you are OK.

I have not heard of any other bugs/crashes except in these 2 cases. If 
anyone has other bug to report, please do so.

Paul S.
 
 


----- Forwarded Message ----
From: James Elliott <johans121@...>
To: motm@yahoogroups.com
Sent: Saturday, October 13, 2007 12:13:47 AM
Subject: [motm] 650 Aux 1 Bug?


I am encountering a very frustrating issue with my new 650. 

It seems as if I control aux 1 with a midi cc (as anyone would) my 650 becomes unresponsive to midi until I reload a patch. If I press enter on global options while in this state, I get an "Assert LXXXX" error message (they have been different each time, depending on what buttons I hit after this happens - the one I am starring at right now is L2028). When I get the error message, I have to power off my 650 completely to get it to work again. can't quite figure out what is causing this to happen. The only thing I am doing is sending cc information to control aux 1. 

This does not happen with aux2, 3, or 4.

I am in 1/1/1/1 mode with all voices receiving on channel 1.

Help!

Any ideas!!??!!

-Jim

.

From: James Elliott <johans121@yahoo.com>
To: motm@yahoogroups.com
Sent: Monday, December 1, 2008 2:34:27 PM
Subject: [motm] 650 OS Update?


Paul, is there any news on the 650 OS update to resolve outstanding issues?

Thanks,
Jim





________________________________
From: James Elliott <johans121@yahoo. com>
To: motm@yahoogroups. com
Sent: Wednesday, June 18, 2008 12:56:03 AM
Subject: Re: [motm] 650 OS Update Status....


Here's the details of a bug that I turned in last year which causes my 650 to "crash".

Hopefully this gets addressed in the next update as it is frustrating to no end.

-Jim




Paul, you've asked the list to send you any errors / descriptions of funky behavior that we encounter. I've already sent you a general description of these problems on 10/13, and I will go into more detail here.

General Problem: My 650 quits responding to midi when I send midi cc's to control aux1. When I say quit responding I mean that the output jacks do not transmit a signal - the midi LED still responds to midi. One of two things happens once the 650 is in this state.

1) If I perform the following actions, then the 650 begins to respond to midi again (however it will lock up again if I send midi cc's to aux1)
-Press "ESC"
-Scroll to, and then select, "Module Actions"
-Scroll to, and then select, "Load Patch"
-and finally, load a patch

2) If I don't follow the steps above, I get various assert errors depending on different buttons that I press
-L612: I get this error when I press "Enter" after a lockup
-L2039: When I press "Inc" after a lockup
-L2167: When I press "dec" after a lockup
-L548: First I press "ESC", which allows me to scroll through the top level menu, then press "Enter" on any of the second level menu items 

My 650 is setup as follows:
-Global options:
1) Voice Type - 1/1/1/1
2) CtrlMidi Chan - 1
3) Trig PWM - 10ms
4) VelScale - 8 Volts
5) Backlight - Auto
6) TunTable - 12 Tone
7) Note Inv - Off
8) Priority - LastNote
9) Clock - Internal
10) IClk BPM - 120.0
11) Midi Clk - Transmit
12) Patch Rx - Disabled (I also tried enabled, whatever that does?)
13) SysexSys ID=Global

-VoiceGroup 1 Settings:
1) VG1 Midi Chan - 1
2) VG1 Allc - Solo
3) VG1Glide - Off
4) VG1PBend - 24
5) VG1GType - Normal
6) VG1 V/T - Velocity
7) VG1 Aux - CC12 (Tried others as well with the same issue resulting)
8) VG1AuxSc - 8 Volts

-VoiceGroups 2 - 4 are set up exactly like group 1 except that the PBends are set to 0, and the Aux Midi CC's are set to different values (13, 14, 15).

-Both Arps are turned off.

**This also happens in other other voice modes as well 4/poly1, 4/poly2, 2/2/poly1, etc.......

I really hope this gets fixed in the next patch release because having one of the 4 aux outs messed up sucks. Other than this problem, the 650 is a pretty cool module.

-Jim


----- Original Message ----
From: Paul Schreiber <synth1@airmail. net>
To: motm@yahoogroups. com; James Elliott <johans121@yahoo. com>
Sent: Wednesday, June 18, 2008 12:20:53 AM
Subject: Re: [motm] 650 OS Update Status....


Hopefully Jeffrey will step in and give us an update. I have not heard from 
him in a while.

Meanwhile: the majority of the issues are using external clock to drive the 
arpeggiators and using Voice Group 1/1/1/1 (4 independent MIDI channels). 
The Voice Group
bug seems to be if you change from/into 1/1/1/1 mode. I think if you *start* 
there (the default patch) you are OK.

I have not heard of any other bugs/crashes except in these 2 cases. If 
anyone has other bug to report, please do so.

Paul S.
 
 


----- Forwarded Message ----
From: James Elliott <johans121@yahoo. com>
To: motm@yahoogroups. com
Sent: Saturday, October 13, 2007 12:13:47 AM
Subject: [motm] 650 Aux 1 Bug?


I am encountering a very frustrating issue with my new 650. 

It seems as if I control aux 1 with a midi cc (as anyone would) my 650 becomes unresponsive to midi until I reload a patch. If I press enter on global options while in this state, I get an "Assert LXXXX" error message (they have been different each time, depending on what buttons I hit after this happens - the one I am starring at right now is L2028). When I get the error message, I have to power off my 650 completely to get it to work again. can't quite figure out what is causing this to happen. The only thing I am doing is sending cc information to control aux 1. 

This does not happen with aux2, 3, or 4.

I am in 1/1/1/1 mode with all voices receiving on channel 1.

Help!

Any ideas!!??!!

-Jim

On Dec 11, 2008, at 7:52 PM, James Elliott wrote:

>
> Any news?
>
> I know I can't be the only person that would like a fully  
> operational $500 module that I waited over a year to receive.... I'm  
> not trying to be an ass. But I would really like some kind of  
> meaningful update.
>
> -Jim
>
> From: James Elliott <johans121@...>
> To: motm@yahoogroups.com
> Sent: Monday, December 1, 2008 2:34:27 PM
> Subject: [motm] 650 OS Update?
>
>
> Paul, is there any news on the 650 OS update to resolve outstanding  
> issues?
>
> Thanks,
> Jim
>
>
> From: James Elliott <johans121@yahoo. com>
> To: motm@yahoogroups. com
> Sent: Wednesday, June 18, 2008 12:56:03 AM
> Subject: Re: [motm] 650 OS Update Status....
>
> Here's the details of a bug that I turned in last year which causes  
> my 650 to "crash".
>
> Hopefully this gets addressed in the next update as it is  
> frustrating to no end.
>
> -Jim
>
>
>
>
> Paul, you've asked the list to send you any errors / descriptions of  
> funky behavior that we encounter. I've already sent you a general  
> description of these problems on 10/13, and I will go into more  
> detail here.
>
> General Problem: My 650 quits responding to midi when I send midi  
> cc's to control aux1. When I say quit responding I mean that the  
> output jacks do not transmit a signal - the midi LED still responds  
> to midi. One of two things happens once the 650 is in this state.
>
> 1) If I perform the following actions, then the 650 begins to  
> respond to midi again (however it will lock up again if I send midi  
> cc's to aux1)
> -Press "ESC"
> -Scroll to, and then select, "Module Actions"
> -Scroll to, and then select, "Load Patch"
> -and finally, load a patch
>
> 2) If I don't follow the steps above, I get various assert errors  
> depending on different buttons that I press
> -L612: I get this error when I press "Enter" after a lockup
> -L2039: When I press "Inc" after a lockup
> -L2167: When I press "dec" after a lockup
> -L548: First I press "ESC", which allows me to scroll through the  
> top level menu, then press "Enter" on any of the second level menu  
> items
>
> My 650 is setup as follows:
> -Global options:
> 1) Voice Type - 1/1/1/1
> 2) CtrlMidi Chan - 1
> 3) Trig PWM - 10ms
> 4) VelScale - 8 Volts
> 5) Backlight - Auto
> 6) TunTable - 12 Tone
> 7) Note Inv - Off
> 8) Priority - LastNote
> 9) Clock - Internal
> 10) IClk BPM - 120.0
> 11) Midi Clk - Transmit
> 12) Patch Rx - Disabled (I also tried enabled, whatever that does?)
> 13) SysexSys ID=Global
>
> -VoiceGroup 1 Settings:
> 1) VG1 Midi Chan - 1
> 2) VG1 Allc - Solo
> 3) VG1Glide - Off
> 4) VG1PBend - 24
> 5) VG1GType - Normal
> 6) VG1 V/T - Velocity
> 7) VG1 Aux - CC12 (Tried others as well with the same issue resulting)
> 8) VG1AuxSc - 8 Volts
>
> -VoiceGroups 2 - 4 are set up exactly like group 1 except that the  
> PBends are set to 0, and the Aux Midi CC's are set to different  
> values (13, 14, 15).
>
> -Both Arps are turned off.
>
> **This also happens in other other voice modes as well 4/poly1, 4/ 
> poly2, 2/2/poly1, etc.......
>
> I really hope this gets fixed in the next patch release because  
> having one of the 4 aux outs messed up sucks. Other than this  
> problem, the 650 is a pretty cool module.
>
> -Jim
>
> ----- Original Message ----
> From: Paul Schreiber <synth1@airmail. net>
> To: motm@yahoogroups. com; James Elliott <johans121@yahoo. com>
> Sent: Wednesday, June 18, 2008 12:20:53 AM
> Subject: Re: [motm] 650 OS Update Status....
>
> Hopefully Jeffrey will step in and give us an update. I have not  
> heard from
> him in a while.
>
> Meanwhile: the majority of the issues are using external clock to  
> drive the
> arpeggiators and using Voice Group 1/1/1/1 (4 independent MIDI  
> channels).
> The Voice Group
> bug seems to be if you change from/into 1/1/1/1 mode. I think if you  
> *start*
> there (the default patch) you are OK.
>
> I have not heard of any other bugs/crashes except in these 2 cases. If
> anyone has other bug to report, please do so.
>
> Paul S.
>
>
>
>
>
> ----- Forwarded Message ----
> From: James Elliott <johans121@yahoo. com>
> To: motm@yahoogroups. com
> Sent: Saturday, October 13, 2007 12:13:47 AM
> Subject: [motm] 650 Aux 1 Bug?
>
>
> I am encountering a very frustrating issue with my new 650.
>
> It seems as if I control aux 1 with a midi cc (as anyone would) my  
> 650 becomes unresponsive to midi until I reload a patch. If I press  
> enter on global options while in this state, I get an "Assert LXXXX"  
> error message (they have been different each time, depending on what  
> buttons I hit after this happens - the one I am starring at right  
> now is L2028). When I get the error message, I have to power off my  
> 650 completely to get it to work again. can't quite figure out what  
> is causing this to happen. The only thing I am doing is sending cc  
> information to control aux 1.
>
> This does not happen with aux2, 3, or 4.
>
> I am in 1/1/1/1 mode with all voices receiving on channel 1.
>
> Help!
>
> Any ideas!!??!!
>
> -Jim
>
>
>
>
>

On 11-Dec-08, at 12:00 PM, Aaron Day wrote:

> I have stopped using mine because of the crashes. I thought about  
> selling it but have held off for the hopes that it would, someday,  
> become reliable.
>
> So, I'll add my voice to the issue. I think its a fair question.
>
> ad
>
>

On Dec 11, 2008, at 2:10 PM, Scott Juskiw wrote:

> Add me to the list as well. I don't play live so the problems aren't
> life threatening, but it still is maddening to have to resort to my
> Roland MPU-101 (circa 1984) for crash-free MIDI to CV.
>
> MOTM-650: love the hardware, hate the software.
>
> On 11-Dec-08, at 12:00 PM, Aaron Day wrote:
>
>> I have stopped using mine because of the crashes. I thought about
>> selling it but have held off for the hopes that it would, someday,
>> become reliable.
>>
>> So, I'll add my voice to the issue. I think its a fair question.
>>
>> ad
>>
>>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

From: J.D. McEachin <jdm@...>
To: motm@yahoogroups.com
Sent: Thursday, December 11, 2008 2:39:05 PM
Subject: Re: [motm] 650 OS Update?


At 10:52 AM 12/11/2008 -0800, James Elliott wrote:
>      Any news? 

Sorry, health problems have severely limited my time & energy. 

>  I am encountering a very frustrating issue with my new 650. 

Sorry to hear that.  Which version of the firmware do you have?

At 01:10 PM 12/11/2008 -0700, Scott Juskiw wrote:
>
>MOTM-650: love the hardware, hate the software.

How so?

JD

On Dec 11, 2008, at 7:25 PM, djbrow54 wrote:

> 650 MIDI clock and external MIDI clock differ by 2X. Would be nice  
> if someone else could verify this. It's been so long since I looked  
> at this I don't remember if it's too fast or too slow.
>
> Dave
>

> > 650 MIDI clock and external MIDI clock differ by 2X.  Would be
> > nice if someone else could verify this.  It's been so long since
> > I looked at this I don't remember if it's too fast or too slow.
> 
> Are you 100% sure that you didn't have MIDI clock multiplication
> turned on?
> 
> -->Neil

> I re-setup my system.  The only MIDI clock multiplier I know is for 
> the arpeggiator.  ARP1 is set to 1X and ARP2 is off.  I'm using the 
> clock output from channel 1 (Aux=clock).
> 
> If I set the clock to internal at 120 bpm, I get clock pulses
> at 125 mS, or 8/second, 480/minute.  At 4 clocks per quarter
> note, =120 BPM.
> 
> Now if I leave everything exactly the same, and set the clock to 
> MIDI, and set my controller to 120 BPM, the clock is now 250 mS or 
> 1/2 the frequency. Shouldn't these be the same frequency?
> 
> I believe the 650 is dividing the MIDI clock 2X too much.
> 
> Somebody else please check this.  Am I missing a clock setting 
> somewhere?
> 
> Dave
> 
> --- In motm@yahoogroups.com, Neil Bradley <nb@> wrote:
> > > 650 MIDI clock and external MIDI clock differ by 2X.  Would be
> > > nice if someone else could verify this.  It's been so long since
> > > I looked at this I don't remember if it's too fast or too slow.
> > 
> > Are you 100% sure that you didn't have MIDI clock multiplication
> > turned on?
> > 
> > -->Neil
>

> > > 
> > > Are you 100% sure that you didn't have MIDI clock multiplication
> > > turned on?
> > > 
> > > -->Neil
> >
>

From: James Elliott <johans121@...>
To: motm@yahoogroups.com
Sent: Saturday, December 13, 2008 12:22:48 PM
Subject: Re: [motm] . Re: 650 OS Update?


Paul, once again not to sound like an ass, but I don't see the
point in bringing up Robert Rich. He might have different needs then
some of us do when it comes to our 650.

example:
I've always
wanted a spectralis. On paper, that thing is truly bad ass. The reason
I never bought one is because it is 'full' of 'features' that have yet
to be implemented - and those missing features are well documented and
are readily available to the public. Many people have purchased a
spectralis knowing that there are 'features' that were advertised but
do not exist. Some of those people have made wonderful music with that
machine even though it doesn't work as advertised. Other people, like
me, have decided to pass on it until certain promised features are
actually there. 

Back to Robert Rich & me. When I try to
play the way I want to, my 650 craps out every time. At this point I'm
so frustrated with it I hardly use it. I really don't care about
Robert's success with his, all I can really say is, good for him.

I
would not have purchased my 650 knowing that using 1 out of the 4 aux
outs causes it to crash (among other things). It would have been nice
if there was a published list of known bugs so I could have made an
informed decision before purchasing it & then having to wait over a
year to receive it. I think a constant appearance of used 650's on the
market would probably hurt new sales at some point. So I would imagine
that getting the OS updated would be a priority, especially since the
650 would be the heart in a lot of different systems (be it a synthtech
modular, somebody else's modular, or possibly a studio full of vintage
synths, or maybe for that special someone with a bunch of digital
delays that have CV inputs on them [which I would imagine would be a
lot of fun]).

-Jim


________________________________
From: Paul Schreiber <synth1@...>
To: ivancu@...; motm@yahoogroups.com
Sent: Friday, December 12, 2008 9:48:03 AM
Subject: Re: [motm] . Re: 650 OS Update?

 > And all of this is a great example how one digital product can be a huge 
> suck on developing new analog products.
>

Not in this case. I designed the hardware only. The SW issues have not 
hampered the
development of *anything*.

I'm sure that when Jeffrey is able he will fix the issues. There is a LOT 
going on inside that little 8051,
memory is at a premium and this is why new MOTM uPs are all 32-bit ARMs with 
16X the speed and
memory capacity of the '650 uP.

The firmware can be upgraded over MIDI using the WinXP utility so when the 
fix is available it's a quick
process. Those of you with Macs have a friend with a PC :)

Yes, there are known bug. But then again, Robert Rich has made 5 new CDs and 
been on 3 live tours with
the V1.3 SW so it's not like it's totally unusable.

Paul S.




________________________________
From: James Elliott <johans121@...>
To: motm@yahoogroups.com
Sent: Thursday, December 11, 2008 12:52:03 PM
Subject: Re: [motm] 650 OS Update?


Any news?
 
I know I can't be the only person that would like a fully
operational $500 module that I waited over a year to receive.... I'm
not trying to be an ass. But I would really like some kind of
meaningful update.
 
-Jim




________________________________
 From: James Elliott <johans121@...>
To: motm@yahoogroups.com
Sent: Monday, December 1, 2008 2:34:27 PM
Subject: [motm] 650 OS Update?


Paul, is there any news on the 650 OS update to resolve outstanding issues?
 
Thanks,
Jim





________________________________
 From: James Elliott <johans121@yahoo. com>
To: motm@yahoogroups. com
Sent: Wednesday, June 18, 2008 12:56:03 AM
Subject: Re: [motm] 650 OS Update Status....


Here's the details of a bug that I turned in last year which causes my 650 to "crash".

Hopefully this gets addressed in the next update as it is frustrating to no end.

-Jim




Paul,
you've asked the list to send you any errors / descriptions of funky
behavior that we encounter. I've already sent you a general description
of these problems on 10/13, and I will go into more detail here.

General
Problem: My 650 quits responding to midi when I send midi cc's to
control aux1. When I say quit responding I mean that the output jacks
do not transmit a signal - the midi LED still responds to midi. One of
two things happens once the 650 is in this state.

1) If I
perform the following actions, then the 650 begins to respond to midi
again (however it will lock up again if I send midi cc's to aux1)
-Press "ESC"
-Scroll to, and then select, "Module Actions"
-Scroll to, and then select, "Load Patch"
-and finally, load a patch

2) If I don't follow the steps above, I get various assert errors depending on different buttons that I press
-L612: I get this error when I press "Enter" after a lockup
-L2039: When I press "Inc" after a lockup
-L2167: When I press "dec" after a lockup
-L548:
First I press "ESC", which allows me to scroll through the top level
menu, then press "Enter" on any of the second level menu items 

My 650 is setup as follows:
-Global options:
1) Voice Type - 1/1/1/1
2) CtrlMidi Chan - 1
3) Trig PWM - 10ms
4) VelScale - 8 Volts
5) Backlight - Auto
6) TunTable - 12 Tone
7) Note Inv - Off
8) Priority - LastNote
9) Clock - Internal
10) IClk BPM - 120.0
11) Midi Clk - Transmit
12) Patch Rx - Disabled (I also tried enabled, whatever that does?)
13) SysexSys ID=Global

-VoiceGroup 1 Settings:
1) VG1 Midi Chan - 1
2) VG1 Allc - Solo
3) VG1Glide - Off
4) VG1PBend - 24
5) VG1GType - Normal
6) VG1 V/T - Velocity
7) VG1 Aux - CC12 (Tried others as well with the same issue resulting)
8) VG1AuxSc - 8 Volts

-VoiceGroups
2 - 4 are set up exactly like group 1 except that the PBends are set to
0, and the Aux Midi CC's are set to different values (13, 14, 15).

-Both Arps are turned off.

**This also happens in other other voice modes as well 4/poly1, 4/poly2, 2/2/poly1, etc.......

I
really hope this gets fixed in the next patch release because having
one of the 4 aux outs messed up sucks. Other than this problem, the 650
is a pretty cool module.

-Jim


----- Original Message ----
From: Paul Schreiber <synth1@airmail. net>
To: motm@yahoogroups. com; James Elliott <johans121@yahoo. com>
Sent: Wednesday, June 18, 2008 12:20:53 AM
Subject: Re: [motm] 650 OS Update Status....


Hopefully Jeffrey will step in and give us an update. I have not heard from 
him in a while.

Meanwhile: the majority of the issues are using external clock to drive the 
arpeggiators and using Voice Group 1/1/1/1 (4 independent MIDI channels). 
The Voice Group
bug seems to be if you change from/into 1/1/1/1 mode. I think if you *start* 
there (the default patch) you are OK.

I have not heard of any other bugs/crashes except in these 2 cases. If 
anyone has other bug to report, please do so.

Paul S.
 
 


----- Forwarded Message ----
From: James Elliott <johans121@yahoo. com>
To: motm@yahoogroups. com
Sent: Saturday, October 13, 2007 12:13:47 AM
Subject: [motm] 650 Aux 1 Bug?


I am encountering a very frustrating issue with my new 650. 

It
seems as if I control aux 1 with a midi cc (as anyone would) my 650
becomes unresponsive to midi until I reload a patch. If I press enter
on global options while in this state, I get an "Assert LXXXX" error
message (they have been different each time, depending on what buttons
I hit after this happens - the one I am starring at right now is
L2028). When I get the error message, I have to power off my 650
completely to get it to work again. can't quite figure out what is
causing this to happen. The only thing I am doing is sending cc
information to control aux 1. 

This does not happen with aux2, 3, or 4.

I am in 1/1/1/1 mode with all voices receiving on channel 1.

Help!

Any ideas!!??!!

-Jim


__._,_.__

From: James Elliott <johans121@...>
To: motm@yahoogroups.com
Sent: Friday, January 23, 2009 3:21:43 PM
Subject: [motm] 650 OS Update?


Ok, this thing is really making me mad. For real. I just used an analog external clock (motm 320) to drive the ARP on my 650 for the first time ever, and while I was going through the ARP settings my 650 locked up and gave me a "HOSED Q6" error!!!

Really? Come on. A HOSED error!? Really? I could stomache the 'Assert' errors, but a HOSED error?

I am soo fed up with this thing.

Paul, really, when is this thing going to get an OS update? I am soo tired of it that it makes me sick that I paid as much as I did and waited over a year, after paying for it, to receive it - and still haven't heard anything regarding an update for it a year and a half
after placing my first bug report.

-Jim




________________________________
From: James Elliott <johans121@yahoo. com>
To: motm@yahoogroups. com
Sent: Saturday, December 13, 2008 12:22:48 PM
Subject: Re: [motm] . Re: 650 OS Update?


Paul, once again not to sound like an ass, but I don't see the
point in bringing up Robert Rich. He might have different needs then
some of us do when it comes to our 650.

example:
I've always
wanted a spectralis. On paper, that thing is truly bad ass. The reason
I never bought one is because it is 'full' of 'features' that have yet
to be implemented - and those missing features are well documented and
are readily available to the public. Many people have purchased a
spectralis knowing that there are 'features' that were advertised but
do not exist. Some of those people have made wonderful music with that
machine even though it doesn't work as advertised. Other people, like
me, have decided to pass on it until certain promised features are
actually there. 

Back to Robert Rich & me. When I try to
play the way I want to, my 650 craps out every time. At this point I'm
so frustrated with it I hardly use it. I really don't care about
Robert's success with his, all I can really say is, good for him.

I
would not have purchased my 650 knowing that using 1 out of the 4 aux
outs causes it to crash (among other things). It would have been nice
if there was a published list of known bugs so I could have made an
informed decision before purchasing it & then having to wait over a
year to receive it. I think a constant appearance of used 650's on the
market would probably hurt new sales at some point. So I would imagine
that getting the OS updated would be a priority, especially since the
650 would be the heart in a lot of different systems (be it a synthtech
modular, somebody else's modular, or possibly a studio full of vintage
synths, or maybe for that special someone with a bunch of digital
delays that have CV inputs on them [which I would imagine would be a
lot of fun]).

-Jim


________________________________
From: Paul Schreiber <synth1@airmail. net>
To: ivancu@...; motm@yahoogroups. com
Sent: Friday, December 12, 2008 9:48:03 AM
Subject: Re: [motm] . Re: 650 OS Update?

> And all of this is a great example how one digital product can be a huge 
> suck on developing new analog products.
>

Not in this case. I designed the hardware only. The SW issues have not 
hampered the
development of *anything*.

I'm sure that when Jeffrey is able he will fix the issues. There is a LOT 
going on inside that little 8051,
memory is at a premium and this is why new MOTM uPs are all 32-bit ARMs with 
16X the speed and
memory capacity of the '650 uP.

The firmware can be upgraded over MIDI using the WinXP utility so when the 
fix is available it's a quick
process. Those of you with Macs have a friend with a PC :)

Yes, there are known bug. But then again, Robert Rich has made 5 new CDs and 
been on 3 live tours with
the V1.3 SW so it's not like it's totally unusable.

Paul S.




________________________________
From: James Elliott <johans121@yahoo. com>
To: motm@yahoogroups. com
Sent: Thursday, December 11, 2008 12:52:03 PM
Subject: Re: [motm] 650 OS Update?


Any news?
 
I know I can't be the only person that would like a fully
operational $500 module that I waited over a year to receive.... I'm
not trying to be an ass. But I would really like some kind of
meaningful update.
 
-Jim




________________________________
 From: James Elliott <johans121@yahoo. com>
To: motm@yahoogroups. com
Sent: Monday, December 1, 2008 2:34:27 PM
Subject: [motm] 650 OS Update?


Paul, is there any news on the 650 OS update to resolve outstanding issues?
 
Thanks,
Jim





________________________________
 From: James Elliott <johans121@yahoo. com>
To: motm@yahoogroups. com
Sent: Wednesday, June 18, 2008 12:56:03 AM
Subject: Re: [motm] 650 OS Update Status....


Here's the details of a bug that I turned in last year which causes my 650 to "crash".

Hopefully this gets addressed in the next update as it is frustrating to no end.

-Jim




Paul,
you've asked the list to send you any errors / descriptions of funky
behavior that we encounter. I've already sent you a general description
of these problems on 10/13, and I will go into more detail here.

General
Problem: My 650 quits responding to midi when I send midi cc's to
control aux1. When I say quit responding I mean that the output jacks
do not transmit a signal - the midi LED still responds to midi. One of
two things happens once the 650 is in this state.

1) If I
perform the following actions, then the 650 begins to respond to midi
again (however it will lock up again if I send midi cc's to aux1)
-Press "ESC"
-Scroll to, and then select, "Module Actions"
-Scroll to, and then select, "Load Patch"
-and finally, load a patch

2) If I don't follow the steps above, I get various assert errors depending on different buttons that I press
-L612: I get this error when I press "Enter" after a lockup
-L2039: When I press "Inc" after a lockup
-L2167: When I press "dec" after a lockup
-L548:
First I press "ESC", which allows me to scroll through the top level
menu, then press "Enter" on any of the second level menu items 

My 650 is setup as follows:
-Global options:
1) Voice Type - 1/1/1/1
2) CtrlMidi Chan - 1
3) Trig PWM - 10ms
4) VelScale - 8 Volts
5) Backlight - Auto
6) TunTable - 12 Tone
7) Note Inv - Off
8) Priority - LastNote
9) Clock - Internal
10) IClk BPM - 120.0
11) Midi Clk - Transmit
12) Patch Rx - Disabled (I also tried enabled, whatever that does?)
13) SysexSys ID=Global

-VoiceGroup 1 Settings:
1) VG1 Midi Chan - 1
2) VG1 Allc - Solo
3) VG1Glide - Off
4) VG1PBend - 24
5) VG1GType - Normal
6) VG1 V/T - Velocity
7) VG1 Aux - CC12 (Tried others as well with the same issue resulting)
8) VG1AuxSc - 8 Volts

-VoiceGroups
2 - 4 are set up exactly like group 1 except that the PBends are set to
0, and the Aux Midi CC's are set to different values (13, 14, 15).

-Both Arps are turned off.

**This also happens in other other voice modes as well 4/poly1, 4/poly2, 2/2/poly1, etc.......

I
really hope this gets fixed in the next patch release because having
one of the 4 aux outs messed up sucks. Other than this problem, the 650
is a pretty cool module.

-Jim


----- Original Message ----
From: Paul Schreiber <synth1@airmail. net>
To: motm@yahoogroups. com; James Elliott <johans121@yahoo. com>
Sent: Wednesday, June 18, 2008 12:20:53 AM
Subject: Re: [motm] 650 OS Update Status....


Hopefully Jeffrey will step in and give us an update. I have not heard from 
him in a while.

Meanwhile: the majority of the issues are using external clock to drive the 
arpeggiators and using Voice Group 1/1/1/1 (4 independent MIDI channels). 
The Voice Group
bug seems to be if you change from/into 1/1/1/1 mode. I think if you *start* 
there (the default patch) you are OK.

I have not heard of any other bugs/crashes except in these 2 cases. If 
anyone has other bug to report, please do so.

Paul S.
 
 


----- Forwarded Message ----
From: James Elliott <johans121@yahoo. com>
To: motm@yahoogroups. com
Sent: Saturday, October 13, 2007 12:13:47 AM
Subject: [motm] 650 Aux 1 Bug?


I am encountering a very frustrating issue with my new 650. 

It
seems as if I control aux 1 with a midi cc (as anyone would) my 650
becomes unresponsive to midi until I reload a patch. If I press enter
on global options while in this state, I get an "Assert LXXXX" error
message (they have been different each time, depending on what buttons
I hit after this happens - the one I am starring at right now is
L2028). When I get the error message, I have to power off my 650
completely to get it to work again. can't quite figure out what is
causing this to happen. The only thing I am doing is sending cc
information to control aux 1. 

This does not happen with aux2, 3, or 4.

I am in 1/1/1/1 mode with all voices receiving on channel 1.

Help!

Any ideas!!??!!

-Jim


__._,_.__

>So, is my request for a meaningful update just going to go ignored?
>
>Well, if 'update' means "something new to report", then there is no update.
>
>To spell it out:
>
>a) I did not write the code
>b) I do not have access to the code
>c) the person who has the code is aware of the problems, but has had ongoing
>health issues. I have emailed him several times, and gotten no response.
>d) I have NO IDEA if, or when, a code update will happen
>e) I have taken corrective measures for future modules (both in HW and SW)
>to assure this situation does not happen again
>f) if anyone is unhappy with any MOTM module, for any reason, just email me.
>I will issue a refund *immediately* upon it's return.
>
>Paul S.
>

On Feb 3, 2009, at 8:35 PM, John Blacet wrote:

> ---A post from Paul a week or so ago states that he does not have  
> access
> to the code--very scary!
>
> > is the source to the 650 available?
> >
> > in the absence of the original author, maybe the community could  
> have
> > a go at fixing it.
> >
> >
> >
> >
> >
> >>So, is my request for a meaningful update just going to go ignored?
> >>
> >>Well, if 'update' means "something new to report", then there is no
> >> update.
> >>
> >>To spell it out:
> >>
> >>a) I did not write the code
> >>b) I do not have access to the code
> >>c) the person who has the code is aware of the problems, but has had
> >> ongoing
> >>health issues. I have emailed him several times, and gotten no  
> response.
> >>d) I have NO IDEA if, or when, a code update will happen
> >>e) I have taken corrective measures for future modules (both in HW  
> and
> >> SW)
> >>to assure this situation does not happen again
> >>f) if anyone is unhappy with any MOTM module, for any reason, just  
> email
> >> me.
> >>I will issue a refund *immediately* upon it's return.
> >>
> >>Paul S.
> >>
> >
> >
> >
> >
> >
>
> -- 
> John Blacet
>
>
>

On Feb 3, 2009, at 2:57 PM, Jason Proctor wrote:

>
> >He wrote me and said the same thing. It sounds kind of cheesy but
> >maybe we could send a group letter to the SW engineer and ask/plead
> >that he release it.
>
> in any case, it doesn't need to be a full scale distribution, where
> dodgy things like rights get involved. more like an expansion of the
> development team :-)
>
>
>

-----Original Message-----
From: motm@yahoogroups.com [mailto:motm@yahoogroups.com] On Behalf Of Jason
Proctor
Sent: Tuesday, February 03, 2009 12:18 PM
To: MOTM
Subject: Re: [motm] 650 OS Update?


>If details about the processor and the hardware are known, what's to 
>stop an alternative open-source firmware from being created from 
>scratch?
>
>Granted, it would be a lot of work...

nothing at all. but as you say, fixing the existing OS would 
presumably be several orders of magnitude less effort.

hardware details are easily determined by buying a unit :-)


------------------------------------

Yahoo! Groups Links