The Yamaha AN1x Synthesizer mailing list

Hi, I'm a complete novice when it comes to both synthesizers and MIDI,
so I'm not sure whether the problems I'm having are my mistakes, or
actual hardware or driver issues.
Basically, normal MIDI messages appear to be passing correctly in both
directions, but SysEx commands do not appear to be received by the AN1x.
And manually-sent bulk dumps from the AN1x are received by the PC, but
appear to be incorrect.
My setup: Windows XP SP3, AN1x 1.02, and a cheap USB-2MIDI adapter
<http://www.ebay.co.uk/itm/230695658396> . I've read on this forum
previous reports of problems with such USB MIDI adapters but haven't
seen a satisfactory explanation of what exactly the problem is.
Symptoms with AN1xEdit v1.1:
* The virtual keyboard notes are relayed correctly to the synthesizer,
as is the pitch controller and modulation wheel.
* Any parameter or voice changes are not reflected on the AN1x (although
anything currently playing is stopped).
* Clicking on "Request" results in pause followed by "Receive error".
Ditto with Retry.
* No error messages are displayed on the AN1x at all.

Analysis with Midi-Ox v7.0.2.372:
* The virtual keyboard controls the AN1x notes correctly.
* Normal MIDI messages like Note on/off, pitch bend etc. appear correct
in the Monitor Input window.
* When anything is being sent from the AN1x, the green MIDI IN light on
the adapter flashes.(and it flashes continously because of the FE
Activity Sensing message)
* When anything is sent from MidiOx, the orange MIDI OUT light on the
adapter flashes.
* Nothing at all is received from the AN1x in response to SysEx
commands.I've tried for instance the Identity Request command: F0 7E 7F
06 01 F7
* The "SX" LED on the output port shown in the Midi Port Activity window
does not light when I'm sending SysEx commands.
* The SX LED on the input port does light up when receiving SysEx data
from the AN1x (e.g. bulk dumps).
* Bulk dump data from the AN1x appear to be incorrect. For example,
here are example "1 ptn" and "1 vce" dumps:
BulkDump, 1 ptn:SYSX: F0 43 00 5C 10 0E 00 04 00 00 00 3C 3C 3C 3C 3C 3C
3CSYSX: 3C 3C 3C 64 64 64 64 64 64 64 64 64 64 64 3C 3C 3C 3CSYSX: 3C 3C
3C 3C 3C 3C 3C 00 00 00 00 00 00 00 00 00 00 50SYSX: F7
BulkDump, 1 vce:SYSX: F0 43 00 5C 10 00 00 52 61 78 78 20 20 14 01 02 06
01SYSX: 0A 3C 04 40 72 05 00 00 03 00 27 01 30 00 00 1D 42 28SYSX: 34 44
00 01 7D 11 04 21 05 01 03 00 3C 01 23 00 07 00[snip]
I'm assuming these messages should match the format of "CURRENT SEQ" and
"CURRENT VOICE" respectively, as described on page 11 of the AN1x Data
List manual. Interestingly, for both those messages after the "F0 43 00
5C" there should be 2 bytes giving the data size, followed by "10 0E"
for "1 ptn" and "10 00" for the voice. Note that "10 0E" and "10 00"
are present, but immediately after the 5C. In all my test bulk messages
from the AN1x the data size bytes appear to be missing.
Can any of you shed any light on any of this?


[Non-text portions of this message have been removed]

Hi,

Yer pays yer money and you takes yer choice! :-)

I know of a few people who have reported problems with my x.factory librarians, including an.factory for the AN1x, and in most of these cases recently, the problems are traced to these USB MIDI "Cables".

As you've found, they seem to work fine for basic MIDI duties but are hopeless at handling SYSEX data. Probably because they cannot handle the burst of data.

Purchase a "proper" USB MIDI interface and I'd bet money that your problems will go away.

Cheers
Derek

--- In AN1x-list@yahoogroups.com, "witchole" <dougwoodrow@...> wrote:
>
> Hi, I'm a complete novice when it comes to both synthesizers and MIDI,
> so I'm not sure whether the problems I'm having are my mistakes, or
> actual hardware or driver issues.
> Basically, normal MIDI messages appear to be passing correctly in both
> directions, but SysEx commands do not appear to be received by the AN1x.
> And manually-sent bulk dumps from the AN1x are received by the PC, but
> appear to be incorrect.
> My setup: Windows XP SP3, AN1x 1.02, and a cheap USB-2MIDI adapter
> <http://www.ebay.co.uk/itm/230695658396> . I've read on this forum
> previous reports of problems with such USB MIDI adapters but haven't
> seen a satisfactory explanation of what exactly the problem is.
> Symptoms with AN1xEdit v1.1:
> * The virtual keyboard notes are relayed correctly to the synthesizer,
> as is the pitch controller and modulation wheel.
> * Any parameter or voice changes are not reflected on the AN1x (although
> anything currently playing is stopped).
> * Clicking on "Request" results in pause followed by "Receive error".
> Ditto with Retry.
> * No error messages are displayed on the AN1x at all.
>
> Analysis with Midi-Ox v7.0.2.372:
> * The virtual keyboard controls the AN1x notes correctly.
> * Normal MIDI messages like Note on/off, pitch bend etc. appear correct
> in the Monitor Input window.
> * When anything is being sent from the AN1x, the green MIDI IN light on
> the adapter flashes.(and it flashes continously because of the FE
> Activity Sensing message)
> * When anything is sent from MidiOx, the orange MIDI OUT light on the
> adapter flashes.
> * Nothing at all is received from the AN1x in response to SysEx
> commands.I've tried for instance the Identity Request command: F0 7E 7F
> 06 01 F7
> * The "SX" LED on the output port shown in the Midi Port Activity window
> does not light when I'm sending SysEx commands.
> * The SX LED on the input port does light up when receiving SysEx data
> from the AN1x (e.g. bulk dumps).
> * Bulk dump data from the AN1x appear to be incorrect. For example,
> here are example "1 ptn" and "1 vce" dumps:
> BulkDump, 1 ptn:SYSX: F0 43 00 5C 10 0E 00 04 00 00 00 3C 3C 3C 3C 3C 3C
> 3CSYSX: 3C 3C 3C 64 64 64 64 64 64 64 64 64 64 64 3C 3C 3C 3CSYSX: 3C 3C
> 3C 3C 3C 3C 3C 00 00 00 00 00 00 00 00 00 00 50SYSX: F7
> BulkDump, 1 vce:SYSX: F0 43 00 5C 10 00 00 52 61 78 78 20 20 14 01 02 06
> 01SYSX: 0A 3C 04 40 72 05 00 00 03 00 27 01 30 00 00 1D 42 28SYSX: 34 44
> 00 01 7D 11 04 21 05 01 03 00 3C 01 23 00 07 00[snip]
> I'm assuming these messages should match the format of "CURRENT SEQ" and
> "CURRENT VOICE" respectively, as described on page 11 of the AN1x Data
> List manual. Interestingly, for both those messages after the "F0 43 00
> 5C" there should be 2 bytes giving the data size, followed by "10 0E"
> for "1 ptn" and "10 00" for the voice. Note that "10 0E" and "10 00"
> are present, but immediately after the 5C. In all my test bulk messages
> from the AN1x the data size bytes appear to be missing.
> Can any of you shed any light on any of this?
>
>
> [Non-text portions of this message have been removed]
>

Hi Derek, thanks for replying.

--- In AN1x-list@yahoogroups.com, "derek192603" <dacook.sa432bb@...> wrote:
>
> As you've found, they seem to work fine for basic MIDI duties but are hopeless at handling SYSEX data. Probably because they cannot handle the burst of data.

Maybe, but it doesn't quite make sense to me - the "request identity" command for instance is only 6 bytes, whereas I can send a stream of pitch bend commands to the synth with no problem at all.

Also, the manual dumps consistently miss out the 2 data count bytes. Interestingly, exactly the same problem that Lance Taylor reported and that you analysed in http://launch.groups.yahoo.com/group/AN1x-list/message/12042. As far as I can see, the 10 0E part is a correct response, and 00 06 00 is a correct address, it's just the data length that is missing.

I wonder if there is a pattern to what data is missing from the dumps - can anyone provide correct factory setting dumps so that I can compare them?


> Purchase a "proper" USB MIDI interface and I'd bet money that your problems will go away.

Yes, I am certainly intending to do so, but I'd like to understand why exactly this cheap one is failing.

(PS sorry about the format of my post - I won't be using Yahoo's rich-text editor again in a hurry).

some usb to midi devices dont totally impliment the sysex protocol so that they dont send sysex properly

find a usb midi device that has full sysex send and recieve

i use a midisport 8x8 a 4x4 and a 2x2

they work great and have drivers for win xp3

----- Original Message -----
From: witchole
To: AN1x-list@yahoogroups.com
Sent: Tuesday, December 20, 2011 7:28 PM
Subject: [AN1x] Problems with USB MIDI adapter



Hi, I'm a complete novice when it comes to both synthesizers and MIDI,
so I'm not sure whether the problems I'm having are my mistakes, or
actual hardware or driver issues.
Basically, normal MIDI messages appear to be passing correctly in both
directions, but SysEx commands do not appear to be received by the AN1x.
And manually-sent bulk dumps from the AN1x are received by the PC, but
appear to be incorrect.
My setup: Windows XP SP3, AN1x 1.02, and a cheap USB-2MIDI adapter
<http://www.ebay.co.uk/itm/230695658396> . I've read on this forum
previous reports of problems with such USB MIDI adapters but haven't
seen a satisfactory explanation of what exactly the problem is.
Symptoms with AN1xEdit v1.1:
* The virtual keyboard notes are relayed correctly to the synthesizer,
as is the pitch controller and modulation wheel.
* Any parameter or voice changes are not reflected on the AN1x (although
anything currently playing is stopped).
* Clicking on "Request" results in pause followed by "Receive error".
Ditto with Retry.
* No error messages are displayed on the AN1x at all.

Analysis with Midi-Ox v7.0.2.372:
* The virtual keyboard controls the AN1x notes correctly.
* Normal MIDI messages like Note on/off, pitch bend etc. appear correct
in the Monitor Input window.
* When anything is being sent from the AN1x, the green MIDI IN light on
the adapter flashes.(and it flashes continously because of the FE
Activity Sensing message)
* When anything is sent from MidiOx, the orange MIDI OUT light on the
adapter flashes.
* Nothing at all is received from the AN1x in response to SysEx
commands.I've tried for instance the Identity Request command: F0 7E 7F
06 01 F7
* The "SX" LED on the output port shown in the Midi Port Activity window
does not light when I'm sending SysEx commands.
* The SX LED on the input port does light up when receiving SysEx data
from the AN1x (e.g. bulk dumps).
* Bulk dump data from the AN1x appear to be incorrect. For example,
here are example "1 ptn" and "1 vce" dumps:
BulkDump, 1 ptn:SYSX: F0 43 00 5C 10 0E 00 04 00 00 00 3C 3C 3C 3C 3C 3C
3CSYSX: 3C 3C 3C 64 64 64 64 64 64 64 64 64 64 64 3C 3C 3C 3CSYSX: 3C 3C
3C 3C 3C 3C 3C 00 00 00 00 00 00 00 00 00 00 50SYSX: F7
BulkDump, 1 vce:SYSX: F0 43 00 5C 10 00 00 52 61 78 78 20 20 14 01 02 06
01SYSX: 0A 3C 04 40 72 05 00 00 03 00 27 01 30 00 00 1D 42 28SYSX: 34 44
00 01 7D 11 04 21 05 01 03 00 3C 01 23 00 07 00[snip]
I'm assuming these messages should match the format of "CURRENT SEQ" and
"CURRENT VOICE" respectively, as described on page 11 of the AN1x Data
List manual. Interestingly, for both those messages after the "F0 43 00
5C" there should be 2 bytes giving the data size, followed by "10 0E"
for "1 ptn" and "10 00" for the voice. Note that "10 0E" and "10 00"
are present, but immediately after the 5C. In all my test bulk messages
from the AN1x the data size bytes appear to be missing.
Can any of you shed any light on any of this?

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]

--- In AN1x-list@yahoogroups.com, "jammie" <jammie.emma@...> wrote:

>
> some usb to midi devices dont totally impliment the sysex protocol so that they dont send sysex properly

Ah, that's interesting, and this is the bit I really don't understand. Isn't the protocol only something that the synthesizer and PC software need to know about?

To my understanding, a MIDI adapter needs to convert the MIDI electrical signal into a sequence of bytes, and vice versa. If it can do that for "normal" MIDI messages why can't it do it for SysEx messages?

In other words, why should the content of the data being passed have any relevance to the MIDI adapter?

Derek suggested that the problem might be due to the sheer size of SysEx messages, and I can understand that badly-designed buffering might cause data to be lost, but the problem occurs even with a 6-byte identity request message, and I'm having trouble believing such a short message would be affected by buffering problems.

Can you tell me whether the "SX" LED on the output port shown in Midi-Ox's "Midi Port Activity" window lights up when you're sending SysEx commands? I'm not sure how Midi-Ox detects the SX status, but I find it odd that it will show the SysEx F0 status byte going out in the Output Monitor window, but the SX LED doesn't even flicker.

> i use a midisport 8x8 a 4x4 and a 2x2

Thanks for the recommendation.

--- In AN1x-list@yahoogroups.com, "derek192603" <dacook.sa432bb@...> wrote:

>
> As you've found, they seem to work fine for basic MIDI duties but are hopeless at handling SYSEX data. Probably because they cannot handle the burst of data.

That does indeed appear to be the case. The vendor:product id of my device is 1a86:752d, which is a CH345 device made by QinHeng Electronics. I've discovered this device is included in Linux reports of buggy USB MIDI firmware that "reports it can do more than 4 bytes in a packet when they can only properly handle 4".

http://comments.gmane.org/gmane.linux.alsa.devel/83706
and
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3752

This fits perfectly with the missing 5th and 6th data length bytes I've witnessed.

It looks from the above that the Linux guys are getting around the problem by ignoring the reported capability of such devices, and restricting the packet size to 4 bytes. I did actually already try the device under Crunchbang with no success, maybe I need to try updating the ALSA driver.

But if it can be fixed in Linux, surely it can be fixed in Windows too - anyone know if there are any alternative drivers available?

[PS will my messages always have to be approved by a moderator on this group?]

Hi ladies & gentlemen !
I have an inexpensive PRODIPE 1 in / 1 out MIDI interface (let's say :
cable) and it works fine with AN1xedit (and other synth editor
librarian...).
I suppose that some similar devices filter SYSEX messages and keep only
note and velocity data, obviously AN1x edit does not work.....
Be careful with MIDI - USB devices drivers, some are not compatible with
AN1x edit...
Cheers.
J.F.


jammie a écrit :

> some usb to midi devices dont totally impliment the sysex protocol so that they dont send sysex properly
>
> find a usb midi device that has full sysex send and recieve
>
> i use a midisport 8x8 a 4x4 and a 2x2
>
> they work great and have drivers for win xp3
> ----- Original Message -----
> From: witchole
> To: AN1x-list@yahoogroups.com
> Sent: Tuesday, December 20, 2011 7:28 PM
> Subject: [AN1x] Problems with USB MIDI adapter
>
>
>
> Hi, I'm a complete novice when it comes to both synthesizers and MIDI,
> so I'm not sure whether the problems I'm having are my mistakes, or
> actual hardware or driver issues.
> Basically, normal MIDI messages appear to be passing correctly in both
> directions, but SysEx commands do not appear to be received by the AN1x.
> And manually-sent bulk dumps from the AN1x are received by the PC, but
> appear to be incorrect.
> My setup: Windows XP SP3, AN1x 1.02, and a cheap USB-2MIDI adapter
> <http://www.ebay.co.uk/itm/230695658396> . I've read on this forum
> previous reports of problems with such USB MIDI adapters but haven't
> seen a satisfactory explanation of what exactly the problem is.
> Symptoms with AN1xEdit v1.1:
> * The virtual keyboard notes are relayed correctly to the synthesizer,
> as is the pitch controller and modulation wheel.
> * Any parameter or voice changes are not reflected on the AN1x (although
> anything currently playing is stopped).
> * Clicking on "Request" results in pause followed by "Receive error".
> Ditto with Retry.
> * No error messages are displayed on the AN1x at all.
>
> Analysis with Midi-Ox v7.0.2.372:
> * The virtual keyboard controls the AN1x notes correctly.
> * Normal MIDI messages like Note on/off, pitch bend etc. appear correct
> in the Monitor Input window.
> * When anything is being sent from the AN1x, the green MIDI IN light on
> the adapter flashes.(and it flashes continously because of the FE
> Activity Sensing message)
> * When anything is sent from MidiOx, the orange MIDI OUT light on the
> adapter flashes.
> * Nothing at all is received from the AN1x in response to SysEx
> commands.I've tried for instance the Identity Request command: F0 7E 7F
> 06 01 F7
> * The "SX" LED on the output port shown in the Midi Port Activity window
> does not light when I'm sending SysEx commands.
> * The SX LED on the input port does light up when receiving SysEx data
> from the AN1x (e.g. bulk dumps).
> * Bulk dump data from the AN1x appear to be incorrect. For example,
> here are example "1 ptn" and "1 vce" dumps:
> BulkDump, 1 ptn:SYSX: F0 43 00 5C 10 0E 00 04 00 00 00 3C 3C 3C 3C 3C 3C
> 3CSYSX: 3C 3C 3C 64 64 64 64 64 64 64 64 64 64 64 3C 3C 3C 3CSYSX: 3C 3C
> 3C 3C 3C 3C 3C 00 00 00 00 00 00 00 00 00 00 50SYSX: F7
> BulkDump, 1 vce:SYSX: F0 43 00 5C 10 00 00 52 61 78 78 20 20 14 01 02 06
> 01SYSX: 0A 3C 04 40 72 05 00 00 03 00 27 01 30 00 00 1D 42 28SYSX: 34 44
> 00 01 7D 11 04 21 05 01 03 00 3C 01 23 00 07 00[snip]
> I'm assuming these messages should match the format of "CURRENT SEQ" and
> "CURRENT VOICE" respectively, as described on page 11 of the AN1x Data
> List manual. Interestingly, for both those messages after the "F0 43 00
> 5C" there should be 2 bytes giving the data size, followed by "10 0E"
> for "1 ptn" and "10 00" for the voice. Note that "10 0E" and "10 00"
> are present, but immediately after the 5C. In all my test bulk messages
> from the AN1x the data size bytes appear to be missing.
> Can any of you shed any light on any of this?
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
> [Non-text portions of this message have been removed]
>
>

Hi,

As well as your fourth and fifth bytes, you're also probably missing a lot more data!

What you've reported fits in with my suspicion that some of these devices (but not all, as Jeff has one that works! :-) ) can have very small buffers which will easily overflow with SYSEX data. SYSEX data is the odd man out in the MIDI protocol in that (IIRC) all other messages are three bytes or less. But SYSEX messages are of variable length, but will never be less than four bytes!

An AN1x voice bulk dump will provide nearly 800 bytes of data, which must be received continuously with no interruption or loss. Most MIDI interfaces will handle this case by having several buffers. One buffer will be filled and then dealt with, whilst the next one is received. But typically, such buffers are 256 bytes in length.

I'd be very wary about trying to use a device with such a limited buffer size in any form of "kludge" mode, as you may risk data corruption.

re the ability to fix a problem in Windows that is fixable in Linux, remember we are talking about Windows! :-)

I actually think MIDI support in Windows is going backwards. See the following link for a post of a problem with the Yamaha EX5 and Windows 7, which doesn't occur with earlier versions of Windows!

http://www.ex5tech.com/ex5ubb_cgi/ultimatebb.cgi?ubb=get_topic&f=8&t=000491

I think your best "fix" is to get a reputable MIDI interface. I used a low cost MIDISPORT 2x2 for a long time, and that was rock solid.

http://www.m-audio.com/products/en_us/MIDISPORT2x2.html

My current studio and live setups use a combination of a MOTU MIDI Express 128, Focusrite Sapphire 6, EMU 1212M, and an Edirol interface. All of those have proven to be very good over time.

Cheers
Derek

--- In AN1x-list@yahoogroups.com, "witchole" <dougwoodrow@...> wrote:
>
>
>
> --- In AN1x-list@yahoogroups.com, "derek192603" <dacook.sa432bb@> wrote:
> >
> > As you've found, they seem to work fine for basic MIDI duties but are hopeless at handling SYSEX data. Probably because they cannot handle the burst of data.
>
> That does indeed appear to be the case. The vendor:product id of my device is 1a86:752d, which is a CH345 device made by QinHeng Electronics. I've discovered this device is included in Linux reports of buggy USB MIDI firmware that "reports it can do more than 4 bytes in a packet when they can only properly handle 4".
>
> http://comments.gmane.org/gmane.linux.alsa.devel/83706
> and
> https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3752
>
> This fits perfectly with the missing 5th and 6th data length bytes I've witnessed.
>
> It looks from the above that the Linux guys are getting around the problem by ignoring the reported capability of such devices, and restricting the packet size to 4 bytes. I did actually already try the device under Crunchbang with no success, maybe I need to try updating the ALSA driver.
>
> But if it can be fixed in Linux, surely it can be fixed in Windows too - anyone know if there are any alternative drivers available?
>
> [PS will my messages always have to be approved by a moderator on this group?]
>

--- In AN1x-list@yahoogroups.com, Jeff <jf.serviere@...> wrote:

>
> Hi ladies & gentlemen !
> I have an inexpensive PRODIPE 1 in / 1 out MIDI interface (let's say :
> cable) and it works fine with AN1xedit (and other synth editor
> librarian...).

Thanks JF, that's another one for me to look for.

Have you tried backing up everything from the AN1x, doing a factory reset, then restoring your backup using that Prodipe interface?

Thanks again Derek,

I think you're right, a reputable interface is the way to go. Even if I found a Windows driver that can send the data 4 bytes at a time, there would still be the problem of data sent in the other direction, from the AN1x.

That Windows 7 bug you've discovered sounds frustrating, but also very clear-cut and easy to verify - have you tried reporting it to Microsoft?

Doug.

--- In AN1x-list@yahoogroups.com, "derek192603" <dacook.sa432bb@...> wrote:
>
> Hi,
>
> As well as your fourth and fifth bytes, you're also probably missing a lot more data!
>
> What you've reported fits in with my suspicion that some of these devices (but not all, as Jeff has one that works! :-) ) can have very small buffers which will easily overflow with SYSEX data. SYSEX data is the odd man out in the MIDI protocol in that (IIRC) all other messages are three bytes or less. But SYSEX messages are of variable length, but will never be less than four bytes!
>
> An AN1x voice bulk dump will provide nearly 800 bytes of data, which must be received continuously with no interruption or loss. Most MIDI interfaces will handle this case by having several buffers. One buffer will be filled and then dealt with, whilst the next one is received. But typically, such buffers are 256 bytes in length.
>
> I'd be very wary about trying to use a device with such a limited buffer size in any form of "kludge" mode, as you may risk data corruption.
>
> re the ability to fix a problem in Windows that is fixable in Linux, remember we are talking about Windows! :-)
>
> I actually think MIDI support in Windows is going backwards. See the following link for a post of a problem with the Yamaha EX5 and Windows 7, which doesn't occur with earlier versions of Windows!
>
> http://www.ex5tech.com/ex5ubb_cgi/ultimatebb.cgi?ubb=get_topic&f=8&t=000491
>
> I think your best "fix" is to get a reputable MIDI interface. I used a low cost MIDISPORT 2x2 for a long time, and that was rock solid.
>
> http://www.m-audio.com/products/en_us/MIDISPORT2x2.html
>
> My current studio and live setups use a combination of a MOTU MIDI Express 128, Focusrite Sapphire 6, EMU 1212M, and an Edirol interface. All of those have proven to be very good over time.

--- In AN1x-list@yahoogroups.com, "derek192603" <dacook.sa432bb@...> wrote:

> I'd be very wary about trying to use a device with such a limited buffer size in any form of "kludge" mode, as you may risk data corruption.

Yup indeed. Just noticed that the "SysEx View" window in MidiOx has an option to set the "low level" output buffer size, and delay between packets. So I tried setting the buffer size to 4 and it still doesn't work. In fact with a buffer size of 2 you can't even send a Note ON command. Clearly the MidiOx level is not low enough, it has to be done at the driver level.

Interesting reading (thanks Clemens Ladisch!) for anyone so inclined:

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;hb=HEAD;f=sound/usb/midi.c

You'll notice it's not just my cheap adapter that has problems, some reputable devices also behave in non-standard ways and the driver has been written to work with various quirky behaviours.

Anyway, the upshot of all this is that under Linux with the latest driver I can now send SysEx commands successfully to the AN1x. Unfortunately though, as I suspected, the driver is unable to correct the inadequate buffer size on the QinHeng device for data coming from the synthesizer, so SysEx dumps received from the AN1x are still corrupted.

witchole a écrit :

>
> --- In AN1x-list@yahoogroups.com, Jeff<jf.serviere@...> wrote:
>> Hi ladies& gentlemen !
>> I have an inexpensive PRODIPE 1 in / 1 out MIDI interface (let's say :
>> cable) and it works fine with AN1xedit (and other synth editor
>> librarian...).
> Thanks JF, that's another one for me to look for.
>
> Have you tried backing up everything from the AN1x, doing a factory reset, then restoring your backup using that Prodipe interface?
>
>

Yes, partially ! I have to change the backup battery ... the patches
should be back after this operation. IMHO if it works downwards, it
should work upwards. Individual patches are stored and downloaded
without any issue, as Casio CZ or Kawaï K1 patches do.
I use a PC with Win XP SP3 , it worked with SP2 too.

http://www.prodipe.com/en/products/interfaces/item/59-interface-1in/1out

As you can see it is one of the cheapest MIDI - USB "interface"...
Cheers.
J.F.
P.S. Somewhere on the group's website you should find the "good" and
"bad" USB devices for AN1x edit, according to the members experience.

--- In AN1x-list@yahoogroups.com, Jeff <jf.serviere@...> wrote:

>
> Yes, partially ! I have to change the backup battery ... the patches
> should be back after this operation. IMHO if it works downwards, it
> should work upwards. Individual patches are stored and downloaded
> without any issue, as Casio CZ or Kawaï K1 patches do.

That's good to know, thanks.

> http://www.prodipe.com/en/products/interfaces/item/59-interface-1in/1out
>
> As you can see it is one of the cheapest MIDI - USB "interface"...

Indeed, and it's even cheaper on Amazon:
http://www.amazon.co.uk/Prodipe-1i1o/dp/B001CVMVGW

> P.S. Somewhere on the group's website you should find the "good" and
> "bad" USB devices for AN1x edit, according to the members experience.

Yes, I've found threads
http://launch.groups.yahoo.com/group/AN1x-list/message/2783
and
http://launch.groups.yahoo.com/group/AN1x-list/message/11988


Thanks JF, the Prodipe is definitely on my shortlist.

Doug.

witchole a écrit :

> --- In AN1x-list@yahoogroups.com, Jeff<jf.serviere@...> wrote:
>> Yes, partially ! I have to change the backup battery ... the patches
>> should be back after this operation. IMHO if it works downwards, it
>> should work upwards. Individual patches are stored and downloaded
>> without any issue, as Casio CZ or Kawaï K1 patches do.
> That's good to know, thanks.
>
>
>> http://www.prodipe.com/en/products/interfaces/item/59-interface-1in/1out
>>
>> As you can see it is one of the cheapest MIDI - USB "interface"...
> Indeed, and it's even cheaper on Amazon:
> http://www.amazon.co.uk/Prodipe-1i1o/dp/B001CVMVGW
>
>
>> P.S. Somewhere on the group's website you should find the "good" and
>> "bad" USB devices for AN1x edit, according to the members experience.
> Yes, I've found threads
> http://launch.groups.yahoo.com/group/AN1x-list/message/2783
> and
> http://launch.groups.yahoo.com/group/AN1x-list/message/11988
>
>
> Thanks JF, the Prodipe is definitely on my shortlist.
>
> Doug.
>
>

Hi Doug !
one more thing ... Beware of MIDI mergers , if you have any hidden
somewhere in your gear : most of them "filter" any other message than
"note on - note off - velocity". I have one, a little black box , and
nothing else goes through it...
@+
J.F.

--- In AN1x-list@yahoogroups.com, Jeff <jf.serviere@...> wrote:

>
> one more thing ... Beware of MIDI mergers , if you have any hidden
> somewhere in your gear : most of them "filter" any other message than
> "note on - note off - velocity". I have one, a little black box , and
> nothing else goes through it...

Thanks JF, I'll remember that if I ever get more than one MIDI device.

I just missed out on an eMagic MT-4 2x4 MIDI interface on ebay but then I managed to win an Edirol UM-1SX, hopefully that should do SysEx dumps properly.