Swayed v1.0.3 - available now!

[sheaf]

We've talked about the possible addition of midi out messages to control the hardware. I'm aware this Will be some tedious work, but can you consider possible some kind of "send to hardware" button first to bulk all the patch data to the hardware? (I know you can already do that saving the patch / bank and importing in the hardware with a librarían...too tedious)
In the mentime we can send the patch to the TG/SY 77 after create/modify in Swayed until we can manipulate with real time (sysex) from soft to hardware. That would be Magic!

That's definitely something I want to implement, but there are some difficulties. I already have some code to send an entire patch at once to A01 (it's what I used for testing during development), but I didn't get it working 100% with 4 element patches. For some reason the TG77 is really picky when it comes to receiving SysEx data. If you send the data too fast or too slow it comes in corrupted, or doesn't work. 2 element patches are small enough that you can send the entire data all at once, but 4 element patches need to be broken up in chunks.

Other software seems to suffer from the same problem. For example, with SY Manager I'm unable to send a full bank to my TG77. It also comes in corrupted, exactly the same as my own code. So far only Midi-Ox seems to reliably do the trick for me. Maybe it also depends on what kind of audio interface you have?

I'm curious to hear if other SY77/TG77 owners also have difficulties when uploading SysEx banks to their hardware.

[EvilDragon]

Guess you could investigate how is MIDIOX splitting the sysex messages and at which rate it's sending them, then mimic that...

[gueims]

I haven't find any problem transferring patches from sy.factory or sy manager in any synthesis combination. I'm using a motu espress 128 midi interface in windows 11...

We've talked about the possible addition of midi out messages to control the hardware. I'm aware this Will be some tedious work, but can you consider possible some kind of "send to hardware" button first to bulk all the patch data to the hardware? (I know you can already do that saving the patch / bank and importing in the hardware with a librarían...too tedious)
In the mentime we can send the patch to the TG/SY 77 after create/modify in Swayed until we can manipulate with real time (sysex) from soft to hardware. That would be Magic!

That's definitely something I want to implement, but there are some difficulties. I already have some code to send an entire patch at once to A01 (it's what I used for testing during development), but I didn't get it working 100% with 4 element patches. For some reason the TG77 is really picky when it comes to receiving SysEx data. If you send the data too fast or too slow it comes in corrupted, or doesn't work. 2 element patches are small enough that you can send the entire data all at once, but 4 element patches need to be broken up in chunks.

Other software seems to suffer from the same problem. For example, with SY Manager I'm unable to send a full bank to my TG77. It also comes in corrupted, exactly the same as my own code. So far only Midi-Ox seems to reliably do the trick for me. Maybe it also depends on what kind of audio interface you have?

I'm curious to hear if other SY77/TG77 owners also have difficulties when uploading SysEx banks to their hardware.

[Hangred]

Thank you for the reply. I am trying to attach a sysex file but it won't let me. The note onset info is helpful. I am able to assign a controller on the keyboard and change the filter per note onset. What is interesting is that I can play a note with the filter open and in real time partially close it. If I note onset with the filter closed, it will not real time open. I just sold my real SY77 so I can't see what the real synth does. Ugh! I am trying to control real time MW2.

The way you describe it does sound like it could be a bug. It should either be entirely per note onset (in EG and EG-VA mode) or entirely real time (in LFO mode). I'll investigate. If you like you can always send me a sysex through the "Report an issue" form. But if there's a bug here I can probably find it regardless.

OK, thx. I submitted via the report an issue.

[IvyBirds]

We've talked about the possible addition of midi out messages to control the hardware. I'm aware this Will be some tedious work, but can you consider possible some kind of "send to hardware" button first to bulk all the patch data to the hardware? (I know you can already do that saving the patch / bank and importing in the hardware with a librarían...too tedious)
In the mentime we can send the patch to the TG/SY 77 after create/modify in Swayed until we can manipulate with real time (sysex) from soft to hardware. That would be Magic!

That's definitely something I want to implement, but there are some difficulties. I already have some code to send an entire patch at once to A01 (it's what I used for testing during development), but I didn't get it working 100% with 4 element patches. For some reason the TG77 is really picky when it comes to receiving SysEx data. If you send the data too fast or too slow it comes in corrupted, or doesn't work. 2 element patches are small enough that you can send the entire data all at once, but 4 element patches need to be broken up in chunks.

Other software seems to suffer from the same problem. For example, with SY Manager I'm unable to send a full bank to my TG77. It also comes in corrupted, exactly the same as my own code. So far only Midi-Ox seems to reliably do the trick for me. Maybe it also depends on what kind of audio interface you have?

I'm curious to hear if other SY77/TG77 owners also have difficulties when uploading SysEx banks to their hardware.

It just definitely depends on your interface, and the software Like many Yamaha Synths from the 1980s as an older older MIDI processor. If you send it data too fast, it will drop bytes, and you will get a corrupt patch. For some reason some interface make the situation worse, especially cheap ones..

By default MIDi-Ox inserts lauses in the Sysex file to avoid this issue.

In the SY77 Sysex file there if you look at the Hex Data there with be an F0 at the start of each packet and an F7 at the end of the packet. By default MIDi-Ox is just inserting a delay of 60 to 100 milliseconds between each packet after thr F7

I have no idea how hard that is to program but that is why it works for you. It's allowing time for the SY77 to process each packet before it sends another one

[beely]

Cheap MIDI interfaces often choke on larger sysex messages - they can drop bytes, which is obviously "unhelpful". Or their drivers can have limited buffer sizes which can get exhausted with larger dumps.

Delays between sysex messages are a good idea to give the receiving device time to process the incoming data, especially if you have large chunks.