MOTM

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 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
>
>
>
>
>