Quote:
Originally Posted by Blackbelt Jones
If I actually figure out a way to do this, I will update this thread as I can't believe I am the only person who thought "damn, it would be nice to change the soft knob settings on these 30 patches without having to update them one-at-a-time".
|
You're definitely not the only one who has wanted bulk patch modifications to the Virus -- I've seen others request solutions for it in the past, on these forums even. I'm pretty sure the past consensus though has been that it's not yet been doable to date.
I think you're on the right path by communicating with the developer of that editor. Many developers of small niche software like this really make their product their passion and spend their weekends working on it, and are always looking for ways to improve it. I've been surprised on more than one occasion when I sent a developer feedback on a critical feature I'd like to see, only to see them quickly implement it in the next release.
Some ways to help influence inclusion of a new feature in that case:
1. Buy the software if you like it and it otherwise meets your need -- they are much more likely to listen to supporting users than someone they think has no interest in a purchase. Obviously though, YMMV in this particular case -- if lack of bulk editing is a deal breaker for you and without it you aren't interested in buying, I'd just mention that to him as well.
2. Communicate the feature you have in mind as clearly and specifically as you can. This goes a long way -- the less the developer has to think about the requirement, the more time he can devote to the implementation. I love it when I get users who really know what they want and communicate it well, I almost always ignore feedback them it is poorly defined, non-specific, the user hasn't thought it through, or just isn't communicating it effectively. It's just that there's only so many hours in the day and I figure if they don't know what they want or can't take the time to explain, it's not worth my time to play guess the magic numbers. There are some folks on the FLStudio forum that actually go so far as to put together photoshopped screen mockups of what the feature should look like, describing the workflow in detail etc. I've seen lots of features included in FLS simply due to the clout those users gain by taking the time to do that.
3. Never whine. I can tell this wouldn't be an issue for you, but there are some users that will just send an e-mail going "this really sucks why can't I do ________?!?!?!?!?!", or rant in all caps or whatever. Their mails get ignored fast
Only constructive requests will have the desired effect.
Anyway sounds like you're on the right track. Wonder why he doesn't currently support the TI? I missed that fact in the initial perusal of his site. Maybe he figures VC has all the bases covered already and there's no point. Or maybe there's a technical/legal hurdle in his way? Anyway it seems like if it supports standalone file imports and doesn't necessarily require communicating with the device, both tech and legal hurdles should be few. In other words export data from TI to some file format (is it possible?), use his software to bulk modify the file, then re-import using Virus control software.