On May 9, 2022, ossandust wrote:

You would have been as disappointed if I would have added the Roland specific sysex system with checksum, because the Yamaha uses a different sysex format. That's why I believe it's not a good idea to add brand specific functionality, unless it's in a brand specific firmware chip like the FCB-505 or UnO4Kemper firmware.

Thanks X, yeah that's a good point.

The computer MIDI software I used gave me the ability to do the SYSEX checksum calculation in raw maths, and that's what I did. (Incl. summing all data in a loop, and mod-ing result; tho it's like 10yrs ago, so my memory is rusty.)   

So that would be quite a bit more programming for you implement and not sure if the code-space is there.  So not sure if it's possible or justifiable.  But pls add it to the list of requested features.

Cheers.

On Sat, May 7, 2022 at 09:55 AM, Synthaxe wrote:

BOSS VF-1 and Yamaha VL70-m both require checksums in their SYSEX. 

I've used the FCB1010 in this way before, but needed a computer with software to do the calculations. 

I presumed it would be possible with the UNO2 v1.3 and disappointed that it's not as that's an important feature I needed

You would have been as disappointed if I would have added the Roland specific sysex system with checksum, because the Yamaha uses a different sysex format. That's why I believe it's not a good idea to add brand specific functionality, unless it's in a brand specific firmware chip like the FCB-505 or UnO4Kemper firmware.

Yeah.. I'm all for adding new features, and a checksum is simple math, but supporting a non-standard SYSEX feature like that is WAY out in left field.  I can understand using SYSEX to send setup messages to a device, but to use it for an active, changing value like pedal position?? That's just plain nuts!  Roland has gotten away with this stuff because of their historic reputation for quality and the fact that very few people actually used those SYSEX features.  They've been riding that reputation, charging a premium for the Roland name, and letting their quality suffer for years now, and the Roland name is starting to tarnish.  With the increase in popularity of MIDI control in home studios and with people publishing their own music, Roland is going to get a wake-up call sooner or later.  They'll either become a niche company with a few proprietary products or get with the program and standardize.
<end soapbox rant>

BOSS VF-1 and Yamaha VL70-m both require checksums in their SYSEX. 

I've used the FCB1010 in this way before, but needed a computer with software to do the calculations. 

I presumed it would be possible with the UNO2 v1.3 and disappointed that it's not as that's an important feature I needed. So yes, I too would very much like this feature.

And I still love the v1.3 upgrade.  Some awesome features there.  Thanks! :-)

Roland implements checksum into most  (if not all) of it's products and the same way. 

Without a valid checksum, I doubt if SysEX would work for any Roland product.
If you can make VALUE a readable variable, then that would prove might useful. 

--
Regards,
Alf
🪗 🎶🎤

Correction : the sysex solution is useless _for you_.  Sysex does not have a checksum at all, check the MIDI spec. 
There may be manufacturers who have added this to their brand specific sysex format (Roland for instance). I'll do some research to see if the Roland implementation is wide spread enough to consider adding this specific sysex format (including an auto-generated checksum) as an option for expression pedal sysex messages. 

the Sysex has a checksum and that includes the "value".
your sysex solution is useless, if I cannot calculate the checksum.
I purchased UNO2 V1.3 only for that reason.

You can't access the expressionpedal value in code

for calculating the sysex checksum I need the the current value of the pedal.
As far as I can see the "value" can only be used in sysex.
How can the "value" be accessed and where can the checksum be coded?