Csound Csound-dev Csound-tekno Search About

Re: [Csnd-dev] [EXTERNAL] Re: [Csnd-dev] Manual for Csound 7

Date2025-04-19 17:43
FromMenno Knevel
SubjectRe: [Csnd-dev] [EXTERNAL] Re: [Csnd-dev] Manual for Csound 7
I have skimmed trough the old manual to see if something was missing.
Also i have written down some other thoughts, we can discuss these of course...

1. a) NEW MANUAL Introduction → Historical Preface: after the name Barry Vercoe add (MIT Media Lab). 
1. b) Can we still add some text of docs/manual/Introduction.html???But how??
2. OLD MANUAL: is the text from docs/manual/OrchExpress.html missing in the new one?
3. OLD MANUAL::  is the text from docs/manual/ScoreStrings.html missing in the new one?
4. OLD MANUAL: can we add the text from docs/manual/OviewFrontEnds.html to the NEW MANUAL Introduction-→ Links?
5. NEW MANUAL: Generic Input and Output should be renamed: Generic MIDI Input and Output
6. What to do with Deprecated Section?
7. NEW MANUAL: in Real time MIDI support, there is text about the Virtual MIDI keyboard. Does this still work as there is no FLTK involved??
8. some text to be added about ftgen versus GEN use
9. documentation for the plugin opcodes that are now part of  the Csound Plugins repo can be removed:
- DSSi
- Ableton
- Jacko
- FLTK
- image
- Cuda
- python
-....
A new manual containing these manual pages should be created, in the same style as the new one.

Date2025-04-20 07:58
FromFrancois PINOT
SubjectRe: [Csnd-dev] [EXTERNAL] Re: [Csnd-dev] Manual for Csound 7
1. a) NEW MANUAL Introduction → Historical Preface: after the name Barry Vercoe add (MIT Media Lab).
      Done: https://csound.com/manual/intro/historic-preface/
1. b) Can we still add some text of docs/manual/Introduction.html???But how??
      I don't understand this question.
2. OLD MANUAL: is the text from docs/manual/OrchExpress.html missing in the new one?
      Done: https://csound.com/manual/orch/data-types/#expressions
3. OLD MANUAL::  is the text from docs/manual/ScoreStrings.html missing in the new one?
      Done: https://csound.com/manual/score/parameter-fields/#strings-in-p-fields
4. OLD MANUAL: can we add the text from docs/manual/OviewFrontEnds.html to the NEW MANUAL Introduction-→ Links?
      Done: https://csound.com/manual/overview/links/#front-ends
5. NEW MANUAL: Generic Input and Output should be renamed: Generic MIDI Input and Output
      Done: https://csound.com/manual/midi/generic/
6. What to do with Deprecated Section?
       Deprecated opcodes are here for backup compatibility. Maybe we should have a page listing the deprecated opcodes with a short comment on how they have been replaced and a link to the 6.18 manual entry for the deprecated opcode notice?
7. NEW MANUAL: in Real time MIDI support, there is text about the Virtual MIDI keyboard. Does this still work as there is no FLTK involved??
       See the end of this page: https://csound.com/manual/midi/top/
8. some text to be added about ftgen versus GEN use
       Joachim? Menno?
9. documentation for the plugin opcodes that are now part of  the Csound Plugins repo can be removed:
       This has effectively to be done when the plugins repository will be adapted for Csound7

I'm actually writing a more complete README.md page to show how to work with the manual (build,
export etc)

Regards

François

Le sam. 19 avr. 2025 à 18:43, Menno Knevel <magknevel@gmail.com> a écrit :
I have skimmed trough the old manual to see if something was missing.
Also i have written down some other thoughts, we can discuss these of course...

1. a) NEW MANUAL Introduction → Historical Preface: after the name Barry Vercoe add (MIT Media Lab).
1. b) Can we still add some text of docs/manual/Introduction.html???But how??
2. OLD MANUAL: is the text from docs/manual/OrchExpress.html missing in the new one?
3. OLD MANUAL::  is the text from docs/manual/ScoreStrings.html missing in the new one?
4. OLD MANUAL: can we add the text from docs/manual/OviewFrontEnds.html to the NEW MANUAL Introduction-→ Links?
5. NEW MANUAL: Generic Input and Output should be renamed: Generic MIDI Input and Output
6. What to do with Deprecated Section?
7. NEW MANUAL: in Real time MIDI support, there is text about the Virtual MIDI keyboard. Does this still work as there is no FLTK involved??
8. some text to be added about ftgen versus GEN use
9. documentation for the plugin opcodes that are now part of  the Csound Plugins repo can be removed:
- DSSi
- Ableton
- Jacko
- FLTK
- image
- Cuda
- python
-....
A new manual containing these manual pages should be created, in the same style as the new one.

Date2025-04-20 08:49
Fromtjingboem
SubjectRe: [Csnd-dev] [EXTERNAL] Re: [Csnd-dev] Manual for Csound 7
This is all great, François!
I can not react in detail atm (family matters), but i like the solution for 6. That is, to point to the old manual containing the Deprecated Section. This also means this old manual containing this section should never be removed.
Another solution would be to transfer the Deprecated Section over to the Wiki of the manual: https://github.com/csound/manual/wiki
Or both solutions...?

Quote: I'm actually writing a more complete README.md page to show how to work with the manual (build,
export etc)

Thanks, very good. 
Perhaps we have a text in the README.md about the second manual (to be created) for the plugin opcodes? It is quite a list and i think most users do want to install and use these.

Same goes for the text of the Csound7 repo.

About OSC, Network and non-MIDI Devices,  there are some opcodes that are plugin opcodes. I still do not not have 100% clear what opcodes are the CsoundPlugins and which ones are not.
As i understand it, there is the main repo Csound that is supported by the Csound Team, while a second repo Plugins is not supported by this Csound Team but are supported by the individual creators of these opcodes  (if they choose to do so)?



On Sun, Apr 20, 2025 at 8:58 AM Francois PINOT <fggpinot@gmail.com> wrote:
1. a) NEW MANUAL Introduction → Historical Preface: after the name Barry Vercoe add (MIT Media Lab).
      Done: https://csound.com/manual/intro/historic-preface/
1. b) Can we still add some text of docs/manual/Introduction.html???But how??
      I don't understand this question.
2. OLD MANUAL: is the text from docs/manual/OrchExpress.html missing in the new one?
      Done: https://csound.com/manual/orch/data-types/#expressions
3. OLD MANUAL::  is the text from docs/manual/ScoreStrings.html missing in the new one?
      Done: https://csound.com/manual/score/parameter-fields/#strings-in-p-fields
4. OLD MANUAL: can we add the text from docs/manual/OviewFrontEnds.html to the NEW MANUAL Introduction-→ Links?
      Done: https://csound.com/manual/overview/links/#front-ends
5. NEW MANUAL: Generic Input and Output should be renamed: Generic MIDI Input and Output
      Done: https://csound.com/manual/midi/generic/
6. What to do with Deprecated Section?
       Deprecated opcodes are here for backup compatibility. Maybe we should have a page listing the deprecated opcodes with a short comment on how they have been replaced and a link to the 6.18 manual entry for the deprecated opcode notice?
7. NEW MANUAL: in Real time MIDI support, there is text about the Virtual MIDI keyboard. Does this still work as there is no FLTK involved??
       See the end of this page: https://csound.com/manual/midi/top/
8. some text to be added about ftgen versus GEN use
       Joachim? Menno?
9. documentation for the plugin opcodes that are now part of  the Csound Plugins repo can be removed:
       This has effectively to be done when the plugins repository will be adapted for Csound7

I'm actually writing a more complete README.md page to show how to work with the manual (build,
export etc)

Regards

François

Le sam. 19 avr. 2025 à 18:43, Menno Knevel <magknevel@gmail.com> a écrit :
I have skimmed trough the old manual to see if something was missing.
Also i have written down some other thoughts, we can discuss these of course...

1. a) NEW MANUAL Introduction → Historical Preface: after the name Barry Vercoe add (MIT Media Lab).
1. b) Can we still add some text of docs/manual/Introduction.html???But how??
2. OLD MANUAL: is the text from docs/manual/OrchExpress.html missing in the new one?
3. OLD MANUAL::  is the text from docs/manual/ScoreStrings.html missing in the new one?
4. OLD MANUAL: can we add the text from docs/manual/OviewFrontEnds.html to the NEW MANUAL Introduction-→ Links?
5. NEW MANUAL: Generic Input and Output should be renamed: Generic MIDI Input and Output
6. What to do with Deprecated Section?
7. NEW MANUAL: in Real time MIDI support, there is text about the Virtual MIDI keyboard. Does this still work as there is no FLTK involved??
8. some text to be added about ftgen versus GEN use
9. documentation for the plugin opcodes that are now part of  the Csound Plugins repo can be removed:
- DSSi
- Ableton
- Jacko
- FLTK
- image
- Cuda
- python
-....
A new manual containing these manual pages should be created, in the same style as the new one.