User Forum    :: Powered by YaBB
  « MIDI-OX User Forum - long sysex: win98 vs xp difference »
Welcome, Guest. Please Login or Register.
May 9th, 2025, 1:32am


Home Home Help Help Search Search Members Members Login Login Register Register


   MIDI-OX User Forum
   MIDI-OX
   Scripting Questions
(Moderator: Jamie OConnell)
   long sysex: win98 vs xp difference
« Previous topic | Next topic »
Pages: 1  Reply Reply Notify of replies Notify of replies Send Topic Send Topic Print Print
   Author  Topic: long sysex: win98 vs xp difference  (Read 2007 times)
fozziemusic
New Member
*



MIDI-OX Rules!

   


Posts: 2
long sysex: win98 vs xp difference
« on: Jan 29th, 2009, 10:23am »
Quote Quote Modify Modify

I have created a script to convert a long sysex string to sysex messages. It is used for converting a waldorf mw-xt sound dump to the corresponding cc's - in most instances the byte values can be mapped 1:1 into cc messages as the value byte. No problems so far.
 
Now, the whole dump is 265 bytes long - just over the 'allowed' 256 bytes in scripting sysex handling. Still no problem, as the last 16 or so bytes are corresponding to the patch name - not something I need (I'm constructing an editor on a NMG2 that can send and receive cc's, not sysex).
 
Now for the weird thing: my testscript was developed and tested on an XP laptop and functioned well. The bytes 257-265 just disappeared into oblivion and I couldn't care less. However, when I run this script on a win98se machine (target PC), the first 256 bytes are discarded and I end up with a worthless 9 byte message. What can I do to get the first 256 bytes? I use the sink method, which works fine otherwise.
IP Logged
Pages: 1  Reply Reply Notify of replies Notify of replies Send Topic Send Topic Print Print

« Previous topic | Next topic »


MIDI-OX User Forum » Powered by YaBB 1 Gold - SP 1.3.1!
YaBB © 2000-2003. All Rights Reserved.