one (of quite some) user unfriendly absurdities in sonar

here an interesting example of how things are NOT spontaneous at all  in sonar (an aspect of the app that i have been criticising regrading several other issues since i jumped ship 3 years ago
 
take it as an info, take it as a rant - it doens´t matter - i just present some pure facts that make me feel annoyed:
 
what i wanted to do (and wanting this isnt anything exotic - so please dont question what i want to do ;-)
 
recieve external synths midi dumps in order to archivate specifically edited sound ONLY within the specific project file and not in the synths themselves
 
THIS IS WHAT HAS TO BE DONE TO DO THIS IN SONAR:
 
1: open sysex-view
2: arm the recieving status
3: select the way how the signal transmission is activated
4: send dumop from synth
5: confirm dump has been fully transmitted
6: remember the bank number (because names are not displayed later in the event insert !!!)
7: select a midiclip
8: open the event list
9: insert an event pressing "ins"
10 :choose eventtype
11: choose number of eventtype
12: specify the time of the event - because in contrary to the manuals claim the inserted event is NOT where the nowtime is allocated but at the end of the selcted clip...
 
NOW THIS IS 12 (!!!!) clicks only because sonar cant handel dumps that are bigger than 255byte (yet almost all sounddumps (and i talk about SINGLE sounds) are bigger than that
 
THIS IS WHAT HAS TO BE DONE IN LOGIC:
 
1: arm a miditrack
2: make the dump
 
 
what sould i say???  this operation is 600% more intense ... :-)
 
actually i could name quite some other overly complicated things that can be done with ONE click in other apps that still take 3,4 or more clicks in sonar...(from transposing, quantizing etc.. )
 
actually in my everyday use this means that with sonar (under certain common circumstances) i have a 300 to 500% higher "mouseclick-rate" than with other apps i used in the past.. and although i like many features id say that this IS an issue
  

 
thanks for your attention
 
 
 
 
 

hello john - thanks for your reply - the only thing i can say ist that EVERYTHING i wrote is 100% certified (manual, testing, reviews)
for what i want to do there is NO other way than that one i described...

its also specifically written in the manual of sonar 8 that it can only handle sysex dumps up to 255byte  in the "track-mode"

as i described the procedure above i am well aware of gow bigger dumps work in sonar - but its "That way" that is very questionable ;-)

btw: what i mean with "sound dumps" is just the whole data package that tells the synth how a single preset is built...

actually sonar can record dynamic sysex in track mode - but those are something else (automation) for many synths where the cc are not enough for remote controling all available parameters,  so the additional sysex messages  are no "dumps" but sort of "just another control message"

actually i know that what i have described above sounds like it should not be true - but unfortunately it is...

and if you read what i want to use those dumps for you (hopefully) agrre with me that a 12.step procedure is a real pain - compared to the stress free handling in the old logic

regards