Posted
I find myself bothering Supertonic and others a lot with questions about whether or not I can do something or not, after I fail to find an answer in the manual.
Many time, thankfully!, the answer is, "Yes." But the route to doing that something is, from my view, obscure with respect to which menu and then which menu item accomplishes this.
The manual would have to be 10 times longer if all these wonderful functions were explained in text.
But, an appendix nested by the specific window, then the first menu with all menu items nested under it with brief definitions/ explanations, on to the next menu, etc., etc., on to the next window, then that window's first menu with all menu items nested ..., etc., etc.
Hopefully, you see my point. Such a chart would be immensely illuminating and useful and reduce the demands for 'how to' questions from curious users.
Prado
Thu, 2012-10-18 - 00:35 Permalink
As Smoky said, 'I second that emotion' Many times I look for a piece of information, but cannot find it in the manual.
Thu, 2012-10-18 - 01:26 Permalink
As Smoky said, 'I second that emotion' Many times I look for a piece of information, but cannot find it in the manual.
markstyles
How funny! I just had read your 'Two 'About file' windows' post. Actually, it must be a 'Miracle.' Or, as the other Smokey said: "Only you can prevent forest fires!"
Prado
Thu, 2012-10-18 - 10:19 Permalink
Yes, this would be a good thing, if we can find a way to automatically update the index from source code. The time required to keep things like this up to date manually in multiple languages is a real burden.
Finding more intuitive names for menu items is even better.
Thu, 2012-10-18 - 16:59 Permalink
Andre wrote:
Yes, this would be a good thing, if we can find a way to automatically update the index from source code. The time required to keep things like this up to date manually in multiple languages is a real burden.
Finding more intuitive names for menu items is even better.
I'm pleased you see my point!
Automatic updating would be ideal, but if you maintained the Appendix in a spreadsheet or database, you'd only have to add, delete or modify fields.
You could also save major revisions for major updates, e.g., in HN2 from 2.6 to 2.7 or 3, if it arrives first. In minor updates, just include changes in the normal change log that accompanies each update.
It is probably a tedious and uninspiring task to do it initially, but I imagine that once done it need not be that hard to maintain. You'll do your customers and your company reputation a great service.
As an aside, neither 'basis' nor 'sketch' are, in my opinion, very good descriptors of what they are to represent in HN2. In English the idea would be called 'Instrumentation.' While I know you cater to the world, I think English is the current language of the world. It is possible that those terms are common in classical music, I don't know, but I think terms should reflect the widest possible denominator in the most typical language usage.
Prado
Thu, 2012-10-18 - 18:19 Permalink
I understand the burden of updating all this stuff. Perhaps the users could help.
Is it possible to make the manual(s) available as Word Documents which can then be edited by the user to update those indexes and missing menu items etc. as we discover them. They could then be dated and posted to a User section alongside the regular Cognitone Manuals. Users could download and use either or both.
I've been converting the pdf manual to a Word Doc, including Bookmarks & Hyperlinks, so I can send it to my Kindle to read on the go (pdf's don't work well on a Kindle), but it can easily be converted back to a pdf file if needed.
Boyd
Thu, 2012-10-18 - 22:57 Permalink
I've never done it, but perhaps we could start a wiki encyclopedia for Synfire. Each one of us could contribute little. Andre or Supertonic could look in time to time, and fix or omit glaring errors. Is there a way to make Wiki, only changeable by people with a password or something?
Fri, 2012-10-19 - 00:04 Permalink
Yes, a Wiki would be great. I will eventually have a look at Drupal docs if there is a Wiki module available.
Collaboratively maintaining a large illustrated document without some sophisticated groupware would be very difficult and, according to my experiences, a wasted effort. Workflows like this need to be comfortable, or nobody will contribute anything. A Wiki would be best, I think.
In English the idea would be called 'Instrumentation'.
Good point, However, instrumentation is the role of a sketch in a song. The term would be less appropriate at other places where sketches are used as standalone objects. It also refers to the instruments used rather than the phrases being played. I agree however, that the Basis Sketch menu could be titled "Instrumentation:" and still list sketches.