Hi James.
Thanks for that. Glad to know the sysex bugs been squashed. Can you tell
us what will be in the next version? What will be the cool new feature
this time? lol
Regarding controllers, right now that's what I do, place any controllers
that need to go in a specific order 1 tick apart, but again, thanks for
taking the time to look into this.
While I'm here, I thought it would be cool if qws could have a sort of
text/macro input language for manipulating midi. It perhaps could be
another view on the midi file, for examples of text languages for midi,
take a look at zel, or mml, the basis of the basic programming language
play statement.
thanks,
Arthur
On 20/12/2013 9:15 PM, James Bowden wrote:
Hi Arthur,
Thanks for your message. It's good to hear from you again.
1. Bug with Sysex: this bug is fixed in version 1.56.
(not yet released). Sorry it has been so long since a new build.
2. Bug with NRPN and RPN:
Interesting one. Yes, I think you are right, most likely everything is
normally sorted.
I'll have to add this to the to-do list and will look into it.
Thanks fordrawing this to my attention.
Of course, there would be a workaround: put the CC#6 one tick later
than the other controllers.
Thanks once again for your mail and I hope this helps.
With best regards,
James.
----- Original Message ----- From: "Arthur Pirika" <[email protected]>
To: "QWS list" <[email protected]>
Sent: Friday, December 20, 2013 6:13 AM
Subject: QWS List A Sysex bug and some suggestions
Hi there, it's been a while since I contributed to the list. But here I
am.
The first thing I want to bring up is that I've discovered a bug when
moving sysex around in a midi file. Here's steps to reproduce.
In the event list.
1. Either insert a sysex or find one in an existing midi file to
manipulate.
2. Move the sysex start time around in the same beat, it works just
fine.
3. Now move it to a start time with a different beat, say 1.000 from
0.000. Now look at the sysex. It's been destroyed. The event still shows
up as a sysex, but there's no sysex string anymore.
Second, the handling of certain controllers could be improved. The
scenario, your working with rpn and/or nrpn controllers. These
controllers
need to be sent in a specific order to the synth. Controllers 101 and
100,
or 99 and 98, then followed by data entry controller 6 and possibly 38.
Now, if all of these controllers are inserted at the exact same time,
they
show up fine initially, but as soon as the midi's saved, the controllers
get sorted, lowest number to highest, destroying any association between
rpn/nrpns, and their data entries. Could this be looked into for the
future?
Thanks,
Arthur
To unsubscribe or change list options, see http://lists.andrelouis.com
for archived list posts, see
http://www.mail-archive.com/[email protected]
To unsubscribe or change list options, see http://lists.andrelouis.com
for archived list posts, see
http://www.mail-archive.com/[email protected]
To unsubscribe or change list options, see http://lists.andrelouis.com
for archived list posts, see http://www.mail-archive.com/[email protected]
