Enlightened Forum Men,
Some questions/thoughts for those in the know...Sifting through the debris of the great 1.6.0 debate can we think of a better way of reporting issues? Now, assuming of course that CK hasn't had a nervous breakdown over all this and intends to release future updates, there are bound to be further teething problems with subsequent beta versions - unavoidable really.What might help with this testing if we had a "standardised toolkit" for reporting issues. Some suggestions under three headings:
1. A set of very simple dry clips that could be re-amped - then we could compare different betas/FWs in a more meaningful way. E.g
(a) Simple strummed chord
(b) Arpeggiated chord
(c) Single line notes below 12th fret
(d) Single line notes above 12th fret
Volume might be an issue here - with even slight Db differences affecting perception - but I'm sure we could find an agreed way of doing this.
There's a lot of talented players here - be a nice advert for them. But I stress - simple clips are probably just as good. Although a library of different clips to cover different styles would be no bad thing. E.g I only hear this problem when I mute a death power chord...
2. Wave form / Spectrum analysis - a problem here as not everyone has things like Ozone, but most wave editors feature some sort of spectrum analysis. I like the Ozone features with the red line showing the differences... those in the know can suggest which tool is most useful - perhaps someone from the Development team could chip in. You have an army of beta testers here - let's get them organised!
3. Latency tests: Yes I know... run screaming. But as CK pointed out, how else can you quantify 'feel'? Can anyone suggest a tool we could use to report on this?
Appendix:
(a) Quick word on jokes... every musician I've ever been around has been a bit of a p*ss taker - banter lightens the mood, lets not get too sensitive about this stuff.
(b) Open letters to CK... not singling anyone out here but I really don't think some of the language used recently helps anyone. Sure, complain if you're not happy (Afterall, we're not cult members in purple robes...) but let's keep the right side of the line in terms of decency. Otherwise... why would he post here? We are a stronger community for having his direct involvement.
(c) One for the developers this really - what about an export function that contains a snapshot of users settings? (Credit to djdyer for the most recent member to suggest this )
With the collective talent we have here the recent thread was a little too chaotic in terms of how people were going about things. I think we can do better...Yep there are problems with attempting this but after all.... we are a rather special community aren't we... much better than others we could mention
We could thrash out the details in this thread and perhaps 'sticky' the final results. Could help all involved...
Thoughts?
Fellow forum man, Brett