Yahoo Groups archive

MOTM

Index last updated: 2026-03-31 23:28 UTC

Thread

MOTM-650 bug reporting time

MOTM-650 bug reporting time

2009-08-20 by Paul Schreiber

I have collected MOTM-650 bug reports over the years and sent them in as a
whole to Jeffrey so he can address them. In many cases, he is unable to
reproduce the error. The exception is CC message assignments to the AUX
outputs, that is currently fixed and he is testing that code right now.

Things that people have reported in the past include:

a) running a high rate clock into EXT CLK for the arpeggiators (like into
the audio range) will cause a lock-up

b) scrolling the menus while receiving MIDI data will lock up

c) external MIDI clock seems to run the arpeggiators at 1/2 speed

The current firmware release is V1.3 that shows up when you power up the
device. If you re NOT on V1.3 (there should be nothing else, like RC1 or
V127) email me. There will be a new beta firmware version available in ~ 2
weeks. If you want to be a beta tester email me. Right now, the firmware
updater is XP only, Jeffrey thinks he has a Mac solution that will be ready
in time.

So, I'm asking people with '650s to really pound on them this weekend/next
week, watch for any strange lockups and *write down* what happened and then
repeat it several times so he can also see it.

Fixing the CC messages is a big plus, but I want to get everything quashed
in this release.

Paul S.

RE: [motm] MOTM-650 bug reporting time

2009-08-20 by John L Rice

Thanks Paul, I'll try to get some debug time in this weekend.

Two bugs I encountered that you didn't mention below (and I'll give exact
details on in a few days, this is from memory) are:

1) setting the glide rate too fast and then playing the keyboard quickly
over a several octave range can cause the CV output to become erratic

2) sending certain patch changes from a Yamaha RM1X to the MOTM-650 can
cause it the 650 to lock up


John L Rice


Show quoted textHide quoted text
> -----Original Message-----
> From: motm@yahoogroups.com [mailto:motm@yahoogroups.com] On Behalf Of
> Paul Schreiber
> Sent: Wednesday, August 19, 2009 7:27 PM
> To: MOTM List
> Subject: [motm] MOTM-650 bug reporting time
>
> I have collected MOTM-650 bug reports over the years and sent them in
> as a
> whole to Jeffrey so he can address them. In many cases, he is unable to
> reproduce the error. The exception is CC message assignments to the AUX
> outputs, that is currently fixed and he is testing that code right now.
>
> Things that people have reported in the past include:
>
> a) running a high rate clock into EXT CLK for the arpeggiators (like
> into
> the audio range) will cause a lock-up
>
> b) scrolling the menus while receiving MIDI data will lock up
>
> c) external MIDI clock seems to run the arpeggiators at 1/2 speed
>
> The current firmware release is V1.3 that shows up when you power up
> the
> device. If you re NOT on V1.3 (there should be nothing else, like RC1
> or
> V127) email me. There will be a new beta firmware version available in
> ~ 2
> weeks. If you want to be a beta tester email me. Right now, the
> firmware
> updater is XP only, Jeffrey thinks he has a Mac solution that will be
> ready
> in time.
>
> So, I'm asking people with '650s to really pound on them this
> weekend/next
> week, watch for any strange lockups and *write down* what happened and
> then
> repeat it several times so he can also see it.
>
> Fixing the CC messages is a big plus, but I want to get everything
> quashed
> in this release.
>
> Paul S.
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>

Re: [motm] MOTM-650 bug reporting time

2009-08-20 by Ben Stuyts

Hi Paul,

On 20 aug 2009, at 04:27, Paul Schreiber wrote:

> b) scrolling the menus while receiving MIDI data will lock up

Maybe this is related: if I power up the '650 after the connected midi
keyboard (a GEM S2), the '650 will sometimes lock up. The Gem S2 sends
out midi data as soon as it's booted up (maybe midi clock or active
sensing) as can be seen from the led on the '650.

I haven't seen this if I power up the '650 before the keyboard.

Ben

Re: [motm] MOTM-650 bug reporting time

2009-08-20 by James Elliott

Damn it! I would volunteer to be a beta tester for this as I've been bitching about these bugs either privately to Paul or openly to this list over the last two years, however I'll be traveling over the next month so I won't be able to provide any input :(

Anyway, it looks like the two issues I've run into are being addressed:
1) Assert errors when sending CC's to the Aux outputs
2) Hosed error when receiving on the external clock input

I'm really looking forward to this release, Paul & Jeffrey. Other than the frustrations associated with the various bug's I've reported, I really do like the 650. The only reason why I haven't returned it was because I had faith that you two would try to get these issues ironed out :)

Also, I understand that this is bug fixing time, however I had a thought (a 'feature' wet dream) and wanted to throw this out there....
Would it be possible for the 650 to be able to transmit a clock pulse from the "ext clock" jack and have the pulses controlled by midi start/stop messages? I'm imaging a configuration where that jack could be configured to send or receive clock via a menu option. This would allow the 650 to gate a sequencer without sacrificing any of the other outputs (as well as syncing LFO's). That would be super duper handy; and not only that but also a gold medal to those who have remained faithful to the cause......

-Jim

Show quoted textHide quoted text
From: Paul Schreiber <synth1@...>
To: MOTM List <motm@yahoogroups.com>
Sent: Wednesday, August 19, 2009 9:27:17 PM
Subject: [motm] MOTM-650 bug reporting time

I have collected MOTM-650 bug reports over the years and sent them in as a
whole to Jeffrey so he can address them. In many cases, he is unable to
reproduce the error. The exception is CC message assignments to the AUX
outputs, that is currently fixed and he is testing that code right now.

Things that people have reported in the past include:

a) running a high rate clock into EXT CLK for the arpeggiators (like into
the audio range) will cause a lock-up

b) scrolling the menus while receiving MIDI data will lock up

c) external MIDI clock seems to run the arpeggiators at 1/2 speed

The current firmware release is V1.3 that shows up when you power up the
device. If you re NOT on V1.3 (there should be nothing else, like RC1 or
V127) email me. There will be a new beta firmware version available in ~ 2
weeks. If you want to be a beta tester email me. Right now, the firmware
updater is XP only, Jeffrey thinks he has a Mac solution that will be ready
in time.

So, I'm asking people with '650s to really pound on them this weekend/next
week, watch for any strange lockups and *write down* what happened and then
repeat it several times so he can also see it.

Fixing the CC messages is a big plus, but I want to get everything quashed
in this release.

Paul S.


Re: [motm] MOTM-650 bug reporting time

2009-08-20 by Paul Schreiber

The EXT CLK is hard-wired as input only: there is a LM311 comparator circuit to allow any waveshape (not just squares/pulses) to be a clock.
Jeffrey still gets a gold start for the CC<>AUX fixes.
Paul S.

Re: MOTM-650 bug reporting time

2009-08-21 by xiphiguy

Paul,
Please include the ability to daisy-chain two 650s in the update. I purchased two so that I could take advantage of this advertised feature.
~Terry

Re: [motm] MOTM-650 bug reporting time

2009-08-21 by Ti_

Well, So far I've Never been able to get four separately controlled voices via the 1/1/1/1 Voice Group type and controlling each voice with a separate MIDI channel. Voices 1 & 2 work fine and dandy, the problems are with Voices 3 & 4.

a) The Pitch CV from Voice3 and Voice4 have a strange sort of interaction.
As an example, I have 2 midi tracks coming from a sequencer (I use ProTools and/or Live). Midi track 3 controlling Voice3 on the 650 and Midi track 4 controlling Voice4 on the 650. In my case I just have the same scale playing from the bottom end up the scale on both midi channels.

a1) if you mute the midi output of channel 3, both voices (even V3 which should ONLY be tracking with midi channel 3) track up to A3 and then don't play any higher notes and won't go any higher despite what the sequence is playing.

a2) if you mute the midi output of channel 4, Both voices (even V4 which should ONLY be tracking with midi channel 4) only track up to B0 before locking up.

a3) BUT...if you have BOTH midi channels active(Midi3 to V3 and Midi4 to V4) Both Voices will track normally up into the inaudible range!

That's the one issue I have that keeps me from loving it unconditionally, but probably won't be able to live with it unless it can be fixed.

Thanks,
Tim C.


Show quoted textHide quoted text
From: Paul Schreiber <synth1@...>
To: MOTM List <motm@yahoogroups.com>
Sent: Wednesday, August 19, 2009 9:27:17 PM
Subject: [motm] MOTM-650 bug reporting time

I have collected MOTM-650 bug reports over the years and sent them in as a
whole to Jeffrey so he can address them. In many cases, he is unable to
reproduce the error. The exception is CC message assignments to the AUX
outputs, that is currently fixed and he is testing that code right now.

Things that people have reported in the past include:

a) running a high rate clock into EXT CLK for the arpeggiators (like into
the audio range) will cause a lock-up

b) scrolling the menus while receiving MIDI data will lock up

c) external MIDI clock seems to run the arpeggiators at 1/2 speed

The current firmware release is V1.3 that shows up when you power up the
device. If you re NOT on V1.3 (there should be nothing else, like RC1 or
V127) email me. There will be a new beta firmware version available in ~ 2
weeks. If you want to be a beta tester email me. Right now, the firmware
updater is XP only, Jeffrey thinks he has a Mac solution that will be ready
in time.

So, I'm asking people with '650s to really pound on them this weekend/next
week, watch for any strange lockups and *write down* what happened and then
repeat it several times so he can also see it.

Fixing the CC messages is a big plus, but I want to get everything quashed
in this release.

Paul S.


Re: [motm] MOTM-650 bug reporting time

2009-09-19 by James Elliott

Need anymore beta testers?

Show quoted textHide quoted text
From: James Elliott <johans121@...>
To: MOTM List <motm@yahoogroups.com>
Sent: Thursday, August 20, 2009 6:04:03 PM
Subject: Re: [motm] MOTM-650 bug reporting time

Damn it! I would volunteer to be a beta tester for this as I've been bitching about these bugs either privately to Paul or openly to this list over the last two years, however I'll be traveling over the next month so I won't be able to provide any input :(

Anyway, it looks like the two issues I've run into are being addressed:
1) Assert errors when sending CC's to the Aux outputs
2) Hosed error when receiving on the external clock input

I'm really looking forward to this release, Paul & Jeffrey. Other than the frustrations associated with the various bug's I've reported, I really do like the 650. The only reason why I haven't returned it was because I had faith that you two would try to get these issues ironed out :)

Also, I understand that this is bug fixing time, however I had a thought (a 'feature' wet dream) and wanted to throw this out there....
Would it be possible for the 650 to be able to transmit a clock pulse from the "ext clock" jack and have the pulses controlled by midi start/stop messages? I'm imaging a configuration where that jack could be configured to send or receive clock via a menu option. This would allow the 650 to gate a sequencer without sacrificing any of the other outputs (as well as syncing LFO's). That would be super duper handy; and not only that but also a gold medal to those who have remained faithful to the cause......

-Jim

From: Paul Schreiber <synth1@airmail. net>
To: MOTM List <motm@yahoogroups. com>
Sent: Wednesday, August 19, 2009 9:27:17 PM
Subject: [motm] MOTM-650 bug reporting time

I have collected MOTM-650 bug reports over the years and sent them in as a
whole to Jeffrey so he can address them. In many cases, he is unable to
reproduce the error. The exception is CC message assignments to the AUX
outputs, that is currently fixed and he is testing that code right now.

Things that people have reported in the past include:

a) running a high rate clock into EXT CLK for the arpeggiators (like into
the audio range) will cause a lock-up

b) scrolling the menus while receiving MIDI data will lock up

c) external MIDI clock seems to run the arpeggiators at 1/2 speed

The current firmware release is V1.3 that shows up when you power up the
device. If you re NOT on V1.3 (there should be nothing else, like RC1 or
V127) email me. There will be a new beta firmware version available in ~ 2
weeks. If you want to be a beta tester email me. Right now, the firmware
updater is XP only, Jeffrey thinks he has a Mac solution that will be ready
in time.

So, I'm asking people with '650s to really pound on them this weekend/next
week, watch for any strange lockups and *write down* what happened and then
repeat it several times so he can also see it.

Fixing the CC messages is a big plus, but I want to get everything quashed
in this release.

Paul S.



Re: [motm] MOTM-650 bug reporting time

2010-01-26 by James Elliott

Paul, any news on the 650 bug fixes? If I'm not mistaken you mentioned that some of the fixes were already implemented back in August....

-Jim

Show quoted textHide quoted text
From: James Elliott <johans121@...>
To: MOTM List <motm@yahoogroups.com>
Sent: Sat, September 19, 2009 2:31:31 PM
Subject: Re: [motm] MOTM-650 bug reporting time

Need anymore beta testers?

From: James Elliott <johans121@...>
To: MOTM List <motm@yahoogroups.com>
Sent: Thursday, August 20, 2009 6:04:03 PM
Subject: Re: [motm] MOTM-650 bug reporting time

Damn it! I would volunteer to be a beta tester for this as I've been bitching about these bugs either privately to Paul or openly to this list over the last two years, however I'll be traveling over the next month so I won't be able to provide any input :(

Anyway, it looks like the two issues I've run into are being addressed:
1) Assert errors when sending CC's to the Aux outputs
2) Hosed error when receiving on the external clock input

I'm really looking forward to this release, Paul & Jeffrey. Other than the frustrations associated with the various bug's I've reported, I really do like the 650. The only reason why I haven't returned it was because I had faith that you two would try to get these issues ironed out :)

Also, I understand that this is bug fixing time, however I had a thought (a 'feature' wet dream) and wanted to throw this out there....
Would it be possible for the 650 to be able to transmit a clock pulse from the "ext clock" jack and have the pulses controlled by midi start/stop messages? I'm imaging a configuration where that jack could be configured to send or receive clock via a menu option. This would allow the 650 to gate a sequencer without sacrificing any of the other outputs (as well as syncing LFO's). That would be super duper handy; and not only that but also a gold medal to those who have remained faithful to the cause......

-Jim

From: Paul Schreiber <synth1@airmail. net>
To: MOTM List <motm@yahoogroups. com>
Sent: Wednesday, August 19, 2009 9:27:17 PM
Subject: [motm] MOTM-650 bug reporting time

I have collected MOTM-650 bug reports over the years and sent them in as a
whole to Jeffrey so he can address them. In many cases, he is unable to
reproduce the error. The exception is CC message assignments to the AUX
outputs, that is currently fixed and he is testing that code right now.

Things that people have reported in the past include:

a) running a high rate clock into EXT CLK for the arpeggiators (like into
the audio range) will cause a lock-up

b) scrolling the menus while receiving MIDI data will lock up

c) external MIDI clock seems to run the arpeggiators at 1/2 speed

The current firmware release is V1.3 that shows up when you power up the
device. If you re NOT on V1.3 (there should be nothing else, like RC1 or
V127) email me. There will be a new beta firmware version available in ~ 2
weeks. If you want to be a beta tester email me. Right now, the firmware
updater is XP only, Jeffrey thinks he has a Mac solution that will be ready
in time.

So, I'm asking people with '650s to really pound on them this weekend/next
week, watch for any strange lockups and *write down* what happened and then
repeat it several times so he can also see it.

Fixing the CC messages is a big plus, but I want to get everything quashed
in this release.

Paul S.




Re: [motm] MOTM-650 bug reporting time

2010-01-26 by James Elliott

Jeffrey, anything we can do to get this thing fixed? Can we buy the code from you for a couple cases of beer or something?

-Jim

Show quoted textHide quoted text
From: James Elliott <johans121@...>
To: MOTM List <motm@yahoogroups.com>
Sent: Mon, January 25, 2010 10:15:49 PM
Subject: Re: [motm] MOTM-650 bug reporting time

Paul, any news on the 650 bug fixes? If I'm not mistaken you mentioned that some of the fixes were already implemented back in August....

-Jim

From: James Elliott <johans121@yahoo. com>
To: MOTM List <motm@yahoogroups.. com>
Sent: Sat, September 19, 2009 2:31:31 PM
Subject: Re: [motm] MOTM-650 bug reporting time

Need anymore beta testers?

From: James Elliott <johans121@yahoo. com>
To: MOTM List <motm@yahoogroups. com>
Sent: Thursday, August 20, 2009 6:04:03 PM
Subject: Re: [motm] MOTM-650 bug reporting time

Damn it! I would volunteer to be a beta tester for this as I've been bitching about these bugs either privately to Paul or openly to this list over the last two years, however I'll be traveling over the next month so I won't be able to provide any input :(

Anyway, it looks like the two issues I've run into are being addressed:
1) Assert errors when sending CC's to the Aux outputs
2) Hosed error when receiving on the external clock input

I'm really looking forward to this release, Paul & Jeffrey. Other than the frustrations associated with the various bug's I've reported, I really do like the 650. The only reason why I haven't returned it was because I had faith that you two would try to get these issues ironed out :)

Also, I understand that this is bug fixing time, however I had a thought (a 'feature' wet dream) and wanted to throw this out there....
Would it be possible for the 650 to be able to transmit a clock pulse from the "ext clock" jack and have the pulses controlled by midi start/stop messages? I'm imaging a configuration where that jack could be configured to send or receive clock via a menu option. This would allow the 650 to gate a sequencer without sacrificing any of the other outputs (as well as syncing LFO's). That would be super duper handy; and not only that but also a gold medal to those who have remained faithful to the cause......

-Jim

From: Paul Schreiber <synth1@airmail. net>
To: MOTM List <motm@yahoogroups. com>
Sent: Wednesday, August 19, 2009 9:27:17 PM
Subject: [motm] MOTM-650 bug reporting time

I have collected MOTM-650 bug reports over the years and sent them in as a
whole to Jeffrey so he can address them. In many cases, he is unable to
reproduce the error. The exception is CC message assignments to the AUX
outputs, that is currently fixed and he is testing that code right now.

Things that people have reported in the past include:

a) running a high rate clock into EXT CLK for the arpeggiators (like into
the audio range) will cause a lock-up

b) scrolling the menus while receiving MIDI data will lock up

c) external MIDI clock seems to run the arpeggiators at 1/2 speed

The current firmware release is V1.3 that shows up when you power up the
device. If you re NOT on V1.3 (there should be nothing else, like RC1 or
V127) email me. There will be a new beta firmware version available in ~ 2
weeks. If you want to be a beta tester email me. Right now, the firmware
updater is XP only, Jeffrey thinks he has a Mac solution that will be ready
in time.

So, I'm asking people with '650s to really pound on them this weekend/next
week, watch for any strange lockups and *write down* what happened and then
repeat it several times so he can also see it.

Fixing the CC messages is a big plus, but I want to get everything quashed
in this release.

Paul S.