-
Notifications
You must be signed in to change notification settings - Fork 29
Manual Changes for Csound 7
Menno Knevel edited this page Oct 22, 2024
·
4 revisions
(joachim) I go here through the current items in the Csound 7 Manual
We still have Barry's historical preface here. Suggestion:
- Write a new preface
- Put Barry's historical preface (if possible with the year - 1996?) in an own item afterwards
- ok (add Joachim to : The manual is currently maintained by François Pinot, Menno Knevel and Stefano Cucchi with...-Menno)
- Remove mentions of CsoundAC
- Add present time (1991-2024 rather than 1991-2008 ...)
- Fix some links (sourceforge ...)
- Should this be removed?
- Or a very short description? Or a collection of links?
- We have this version on the Csound homepage. Better one place? (i like to centralize things as much as possible. Perhaps a few words on all different platforms Csound runs on, with a link to https://csound.com/get-started.html for the latest news on the topic? - Menno)
That is definitely very important. Suggestion:
- Write a short text here, kind of overview. (i always liked this Changelog but not so interesting for the user. For the user Csound is presented as is... words on the new syntax? - Menno)
- Link to the (to be written) chapter in the FLOSS Manual about the same topic.
- By the way: here 1984 is said to be the birth of Csound ... =)
- This introduction is outdated in many ways, and mostly repeats historical facts: REMOVE? (remove or replace to Historical Overview - Menno)
- ok ( i think this information could find a better place, it is somewhat lost and will not be found by the user. Add the text to manual/CommandEnvironment.html? - Menno)
- small updates (CSOUND7RC etc)
- small updates
- I think the title is not consistent. The usage of Csound in terminal was explained in the previous section.
- Title suggestion: Command line flags / Options (alphabetically)
- Title suggestion: Command line flags / Options (by category)
- In general good; needs some updates.
- Remove the HTML paragraph?
- small updates (add this to Order of Precedence - Menno)
- ok? (not ok but don´t know how to improve yet - Menno)
- in general ok
- this is written in a different tone: not any more as technical description but as tutorial. I would suggest to keep the tone of a reference, so here more dense and short
- very nice and short description about the architecture
- the subchapter "Csound's processing buffers" is not visible in the overview page!
- In general good but again the tone could be more technial and less tutorial
- Table 2 should show more precise values for 0dbfs = 1
- seems good to me, just some updates needed
- I think this is good; perhaps small additions needed
- I am not very happy with these platform dependent descriptions.
- Remove? Move to FLOSS Manual? (See https://flossmanual.csound.com/how-to) (yes, move to FLOSS - Menno)
- More or less the same question (same answer - Menno)
- This is outdated. Remove? (text about the PATH could be added to Order of Precedence - Menno)
- here is a lot which must be modified and updated
- more or less ok, just some improvements
- ok
- it is a bit abstract but ok ( i have never seen this one before. Can this text be put in a better place? - Menno)
- needs some updates but in general ok
- ok ( i have never seen this one before. Can this text be put in a better place? - Menno)
- ok (stopped checking, will continue next time - Menno)
- ok
- ok
- should be rewritten
- might be better to have together with numbered instruments
- needs to be changed for CS7
- at the end should also mention other UDO collections, like from Steven and Jeanette
- must be rewritten
- needs update for CS7
- good
- needs some updates
- I think it's fine; perhaps small updates
- fine
- ok
- ok
- the description is good but the formatting follows the paradigm of a manual page rather than being a part of this introduction
- same
- same
- can be removed I think
- would it be better to point here to the download page at csound.com or to https://flossmanual.csound.com/how-to/installation?
*the content is ok; not sure it is necessary here though
- same question: should it have a place in the reference manual, or on the website