Patches and discussion for Ensoniq VFX family group photo

Yahoo Groups archive

Patches and discussion for Ensoniq VFX family

Index last updated: 2026-04-29 00:03 UTC

Thread

error 144... let's try again... bonus: another question

error 144... let's try again... bonus: another question

2011-06-19 by somethingkillingyou

ok,

does anyone know what problem could have been?

my SD-1 is the 32 voice version, so I guess it's not related to keyboard calibration problem, since it seems that all SD-1 left the factory with the 2 boards already soldered...
anyway, calibration has never been a problem with my unit...

the 2 things that come to mind are: overheating and... MIDI!

the SD-1 locked up when I was trying to remotely start the sequencer by sending FA (start) and FC (stop) midi realtime messages... 

sending these messages did not work at all, instead the SD-1 froze, buttons being un-responsive etc.

any similar experience? it is working now, so I guess it's NOT a technical problem...

question number two: how do I start/stop the sequencer remotely?

do I have to use an external midi clock or is there a way to just send the sequencer start/stop messages via midi?


F.

Re: error 144... let's try again... bonus: another question

2011-06-22 by somethingkillingyou

ok, it seems this group is full of stupid useless assholes, so goodbye idiots.

--- In Ensoniq-VFX-SD@yahoogroups.com, "somethingkillingyou" <somethingkillingyou@...> wrote:
Show quoted textHide quoted text
>
> ok,
> 
> does anyone know what problem could have been?
> 
> my SD-1 is the 32 voice version, so I guess it's not related to keyboard calibration problem, since it seems that all SD-1 left the factory with the 2 boards already soldered...
> anyway, calibration has never been a problem with my unit...
> 
> the 2 things that come to mind are: overheating and... MIDI!
> 
> the SD-1 locked up when I was trying to remotely start the sequencer by sending FA (start) and FC (stop) midi realtime messages... 
> 
> sending these messages did not work at all, instead the SD-1 froze, buttons being un-responsive etc.
> 
> any similar experience? it is working now, so I guess it's NOT a technical problem...
> 
> question number two: how do I start/stop the sequencer remotely?
> 
> do I have to use an external midi clock or is there a way to just send the sequencer start/stop messages via midi?
> 
> 
> F.
>

Re: error 144... let's try again... bonus: another question

2011-06-22 by az_spunky

First, you have to set the Seq Control page to CLOCK=MIDI on the Ensoniq.

What are you trying to use to start/stop the sequencer?  As a rule, your remote control will need to send messages (start/stop, etc.) to the Ensoniq on a separate MIDI bus.

For example, I use my Yamaha keyboard's transport buttons as the remote controller.  I have a separate set of MIDI channels 1-16 (it shows up as a separate device) dedicated to remote control operations. 


--- In Ensoniq-VFX-SD@yahoogroups.com, "somethingkillingyou" <somethingkillingyou@...> wrote:
Show quoted textHide quoted text
>
> ok,
> 
> does anyone know what problem could have been?
> 
> my SD-1 is the 32 voice version, so I guess it's not related to keyboard calibration problem, since it seems that all SD-1 left the factory with the 2 boards already soldered...
> anyway, calibration has never been a problem with my unit...
> 
> the 2 things that come to mind are: overheating and... MIDI!
> 
> the SD-1 locked up when I was trying to remotely start the sequencer by sending FA (start) and FC (stop) midi realtime messages... 
> 
> sending these messages did not work at all, instead the SD-1 froze, buttons being un-responsive etc.
> 
> any similar experience? it is working now, so I guess it's NOT a technical problem...
> 
> question number two: how do I start/stop the sequencer remotely?
> 
> do I have to use an external midi clock or is there a way to just send the sequencer start/stop messages via midi?
> 
> 
> F.
>

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.