ToH2002
Member
Hi all,
I had originally promised to leave this post for good, but since it seems to stay up on the first page, i must admit I got curious
Now since people seem to discuss what I did and did not say and why I wrote to Fractal, I'd like to add my own statement to put this in perspective:
I discovered the sysex issue whilst trying to upload some impulses (I just find Bome's more convenient, since you just double-click the file you want to upload from the Explorer and hit F4, just personal preference; in AxeEdit you need to change the source every time you want to switch the folder, you can't double-click but need to right-click and "Audition", yada yada). At first I thought: "oh, these impulses all sound similar", since the sound didn't change
Then, when I realized that apparently the impulse change didn't work, I started fiddling around with program settings, restarting my MIDI interface, checking cables, the works.
It was then that I remembered that there was a line in the readme for the update that said something about sysex, which led me to realize the consequence of this change. The fix was then a pretty easy matter.
My key motivation in contacting Fractal was NOT to make them aware of the tool (and get glory from it)! I wanted to make them aware of the consequence of the Sysex ID change for users of MidiOX et al (in case they hadn't been) and to ask them to make this more explicit on their website and in the README, so that other users would not have to go through this. That was it, PERIOD.
The request for help with the mac version was more an afterthought and not really that important to me. Maybe was misunderstood (communication is a difficult thing...).
Regarding my tool: it IS a "little utility"! I knocked it together in not much more than an hour (I warned you - use at your own risk ). My frustration stemmed not from the fact that my tool was not appreciated but from the rude way Fractal treated an (up to then) enthusiastic AxeFX owner who had found a legitimate issue and brought it to their attention, NOT by ranting and raving but by providing constructive suggestions. I was only trying to help, for heaven's sake!
Did I step on someone's pride??
Lastly to electronpirate/Ron: I think I have explained my reason for being "peeved" - no need to put words in my mouth (or mind)... I agree with you that Fractal is doing an incredible job with constant updates, added functionality etc. I disagree with your statement that Cliff has NO obligation to fix issues with third-party sysex transfer. Let me explain (if you're interested):
Accepting valid sysex files is a feature of the product (AxeFX), that has been working since the product was launched (at least since I got mine). How to get these sysex files to the product is essentially the user's decision (especially since the Axe-Edit, as often mentioned, is officially in not-supported beta stage) - sending sysex files is a standardized functionality that should not require any specific software. After the firmware update, this normal sysex transfer does not work anymore for your existing files - something got broken. My old principle is: if you break something, you're (at least morally) obliged to fix it.
Fractal have certainly provided a workaround with the Axe-Edit, both for sending and for converting individual sysex files, which is appreciated! But at the very least, they have confused the h** out of me and a couple of other users who wondered why their established way of working didn't work any more.
Thanx to all of you who gave me positive feedback - appreciated!
Cheers,
Torsten
I had originally promised to leave this post for good, but since it seems to stay up on the first page, i must admit I got curious
Now since people seem to discuss what I did and did not say and why I wrote to Fractal, I'd like to add my own statement to put this in perspective:
I discovered the sysex issue whilst trying to upload some impulses (I just find Bome's more convenient, since you just double-click the file you want to upload from the Explorer and hit F4, just personal preference; in AxeEdit you need to change the source every time you want to switch the folder, you can't double-click but need to right-click and "Audition", yada yada). At first I thought: "oh, these impulses all sound similar", since the sound didn't change
Then, when I realized that apparently the impulse change didn't work, I started fiddling around with program settings, restarting my MIDI interface, checking cables, the works.
It was then that I remembered that there was a line in the readme for the update that said something about sysex, which led me to realize the consequence of this change. The fix was then a pretty easy matter.
My key motivation in contacting Fractal was NOT to make them aware of the tool (and get glory from it)! I wanted to make them aware of the consequence of the Sysex ID change for users of MidiOX et al (in case they hadn't been) and to ask them to make this more explicit on their website and in the README, so that other users would not have to go through this. That was it, PERIOD.
The request for help with the mac version was more an afterthought and not really that important to me. Maybe was misunderstood (communication is a difficult thing...).
Regarding my tool: it IS a "little utility"! I knocked it together in not much more than an hour (I warned you - use at your own risk ). My frustration stemmed not from the fact that my tool was not appreciated but from the rude way Fractal treated an (up to then) enthusiastic AxeFX owner who had found a legitimate issue and brought it to their attention, NOT by ranting and raving but by providing constructive suggestions. I was only trying to help, for heaven's sake!
Did I step on someone's pride??
Lastly to electronpirate/Ron: I think I have explained my reason for being "peeved" - no need to put words in my mouth (or mind)... I agree with you that Fractal is doing an incredible job with constant updates, added functionality etc. I disagree with your statement that Cliff has NO obligation to fix issues with third-party sysex transfer. Let me explain (if you're interested):
Accepting valid sysex files is a feature of the product (AxeFX), that has been working since the product was launched (at least since I got mine). How to get these sysex files to the product is essentially the user's decision (especially since the Axe-Edit, as often mentioned, is officially in not-supported beta stage) - sending sysex files is a standardized functionality that should not require any specific software. After the firmware update, this normal sysex transfer does not work anymore for your existing files - something got broken. My old principle is: if you break something, you're (at least morally) obliged to fix it.
Fractal have certainly provided a workaround with the Axe-Edit, both for sending and for converting individual sysex files, which is appreciated! But at the very least, they have confused the h** out of me and a couple of other users who wondered why their established way of working didn't work any more.
Thanx to all of you who gave me positive feedback - appreciated!
Cheers,
Torsten