Post by tickboxtyrant on May 23, 2013 10:37:36 GMT
Hi Nic, after spending a few hours using the new Stream Byter module, here is some feedback.
Firstly, it works, is stable and took most everything I could throw at it Midi wise, for several intense hours. Great!
Its flexibility is also like a breath of fresh air!
There are a couple of niggles though. Using the editor is really quite tiresome, it isn't possible to enlarge the text, so using the touch screen to accurately place the cursor in order to edit characters is hit and miss to say the least! One of the most infuriating things is the fact the parser sticks #ERR permanently in front of your code, which you then have to try and remove before the next test.... This was on an iPad screen. Really the facility to enlarge the text size/edit area would make basic editing much easier. Also the iPad keyboard places #=- on different keyboards, making them multi keystrokes away. Having specific buttons for these and the other accepted codes, would make it much quicker and easier to enter stuff, and to know what is a valid entry! This is something the iRealB editor has done quite well.
Next: I can understand that hex is the most obvious numbering scheme for editing byte code, but when you are copying patch numbers etc from most devices it is in normally decimal format. Being able to designate the format (eg 20h.. 32d) and so enable the use of either hex or decimal would be a great help.
I have a little issue with the actual meaning of 'X' in your language.. It clearly means any number ( wild card ) on the left of the equals sign, but on the right it means something closer to 'As it was'. Strictly i think NX = N3 ought to work... But it doesn't whereas NX = X3 does..
Finally, it would be nice to be able to do some maths on the stream numbers, e.g. To invert the action of a controller, say to enable it to behave like a drawbar ( biggest number at the bottom) Say (XX xor 7F) Don't know if that's currently possible?
Firstly, it works, is stable and took most everything I could throw at it Midi wise, for several intense hours. Great!
Its flexibility is also like a breath of fresh air!
There are a couple of niggles though. Using the editor is really quite tiresome, it isn't possible to enlarge the text, so using the touch screen to accurately place the cursor in order to edit characters is hit and miss to say the least! One of the most infuriating things is the fact the parser sticks #ERR permanently in front of your code, which you then have to try and remove before the next test.... This was on an iPad screen. Really the facility to enlarge the text size/edit area would make basic editing much easier. Also the iPad keyboard places #=- on different keyboards, making them multi keystrokes away. Having specific buttons for these and the other accepted codes, would make it much quicker and easier to enter stuff, and to know what is a valid entry! This is something the iRealB editor has done quite well.
Next: I can understand that hex is the most obvious numbering scheme for editing byte code, but when you are copying patch numbers etc from most devices it is in normally decimal format. Being able to designate the format (eg 20h.. 32d) and so enable the use of either hex or decimal would be a great help.
I have a little issue with the actual meaning of 'X' in your language.. It clearly means any number ( wild card ) on the left of the equals sign, but on the right it means something closer to 'As it was'. Strictly i think NX = N3 ought to work... But it doesn't whereas NX = X3 does..
Finally, it would be nice to be able to do some maths on the stream numbers, e.g. To invert the action of a controller, say to enable it to behave like a drawbar ( biggest number at the bottom) Say (XX xor 7F) Don't know if that's currently possible?