Re: The Orchestral Staff Attribute Bug
Reply #54 –
I won't try to address everything you've mentioned - this is quite a meal you've served up However, I'll try to hit a couple of highlights and see if I can help in some things.
It seems that you already expect quite a bit from your customers. While I'm quite sure you know them better than I do I have found that users can often surprise - both pleasantly and frustratingly so I do understand your pain, but I suggest that you may also be underrating some of them.
I say this 'cos if they have mastered as much as you say then they can probably cope with a little more. But as I said, you know 'em better than I do. I only mention it because I occasionally must remind my staff that our customers aren't actually idiots - though some can make you wonder...
That said, I agree that simplifying things as much as possible from a user perspective is a good thing. I am a great believer in the KISS principle.
Hmm, confirmed - I've never noticed this as I practically never use the mouse when editing in NWC - too slow. Nevertheless, using the keyboard does work so this may save you some pain. I recall suggesting you learn the keyboard shortcuts - you won't regret doing so.
Sorry 'bout that - I sometimes forget that not everyone has broadband... Do you know anyone with broadband that can download it for you and burn to CD?
OK, here goes:
You don't need to learn to program in PHP, or VB or any other programming language to use the user tools. I cannot cut code - I freely admit it - I'm a glorified user who builds, maintains and services networks and their connected resources. This is how I and my staff make a living - we have no need to cut code - that's what programmers are for
Yet I use user tools all the time. The "Starter Kit" comes with a grab bag of tools that covers a large proportion of identified needs:
My personal favourites from this list are Global Modification, parts, Variable dump and Transpose Chords.
There are several others available including a "tripletise" tool for fixing imported MIDIs - 'taint perfect but it does work. I agree it would be better for NWC to import MIDI triplets natively but until it does, this tool helps.
Enharmonic spelling problems can be improved a lot in the way that I have already mentioned:
Correct the Key sig.
Audic Enharmonic spelling
It won't be perfect, but it WILL be a lot better.
You can also try transposing to a different key and back, while specifying sharp/flat preferences.
This also won't be perfect, but again, can help a lot when working from a raw MIDI. I'm not sure how well this can be improved in NWC - it is partly a function of the MIDI spec itself that gives us these poor results, though I'm sure a sufficiently motivated programmer could improve things. I suspect that it would need more user intervention in the import setup though... Like specifying the key sig. for the import - bit hard when you don't even know what it was supposed to be...
Barry occasionally mentions a pair of tools: mf2t and t2mf which convert MIDI to text which you can edit and then convert back. I'm sure this will also help.
Dynamics can be deleted with a global mod user tool command:
and also tempo markings:
No problem, NWC2 now has the ability to export to NWC1.75 - some formatting detail will be lost, like:
Highlights greater than 3 will revert to highlight 3
"hairpins" will disappear - I don't know if there is an automatic cresc. decresc. replacement - I suspect not.
If you use alternative system fonts these will revert to the standard NWCV15
There are almost certainly others but I can't think of them - I never use NWC1 any more - regardless, I'm sure they can be compensated for and still leave you with a reduced workload.