Archive of the former Yahoo!Groups mailing list: MOTM

previous by date index next by date
previous in topic topic list next in topic

Subject: 650 OS Update?

From: James Elliott <johans121@...>
Date: 2009-01-23

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@...>
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 thepoint in bringing up Robert Rich. He might have different needs thensome of us do when it comes to our 650.

example:
I've alwayswanted a spectralis. On paper, that thing is truly bad ass. The reasonI never bought one is because it is 'full' of 'features' that have yetto be implemented - and those missing features are well documented andare readily available to the public. Many people have purchased aspectralis knowing that there are 'features' that were advertised butdo not exist. Some of those people have made wonderful music with thatmachine even though it doesn't work as advertised. Other people, likeme, have decided to pass on it until certain promised features areactually there.

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

Iwould not have purchased my 650 knowing that using 1 out of the 4 auxouts causes it to crash (among other things). It would have been niceif there was a published list of known bugs so I could have made aninformed decision before purchasing it & then having to wait over ayear to receive it. I think a constant appearance of used 650's on themarket would probably hurt new sales at some point. So I would imaginethat getting the OS updated would be a priority, especially since the650 would be the heart in a lot of different systems (be it a synthtechmodular, somebody else's modular, or possibly a studio full of vintagesynths, or maybe for that special someone with a bunch of digitaldelays that have CV inputs on them [which I would imagine would be alot 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 fullyoperational $500 module that I waited over a year to receive.... I'mnot trying to be an ass. But I would really like some kind ofmeaningful 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 funkybehavior that we encounter. I've already sent you a general descriptionof these problems on 10/13, and I will go into more detail here.

GeneralProblem: My 650 quits responding to midi when I send midi cc's tocontrol aux1. When I say quit responding I mean that the output jacksdo not transmit a signal - the midi LED still responds to midi. One oftwo things happens once the 650 is in this state.

1) If Iperform the following actions, then the 650 begins to respond to midiagain (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 levelmenu, 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

-VoiceGroups2 - 4 are set up exactly like group 1 except that the PBends are set to0, 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.......

Ireally hope this gets fixed in the next patch release because havingone of the 4 aux outs messed up sucks. Other than this problem, the 650is 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.

Itseems as if I control aux 1 with a midi cc (as anyone would) my 650becomes unresponsive to midi until I reload a patch. If I press enteron global options while in this state, I get an "Assert LXXXX" errormessage (they have been different each time, depending on what buttonsI hit after this happens - the one I am starring at right now isL2028). When I get the error message, I have to power off my 650completely to get it to work again. can't quite figure out what iscausing this to happen. The only thing I am doing is sending ccinformation 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


__._,_.__