It mostly works as it is.

The thing is that you can't proceed on the assumption that your RG
composition will come popping out the other end of csound at the press
of a button. I use it to make a start on a csound score which then
needs some touching up by hand. However, just getting all notes down
in the right order is a huge headstart on the problem.

The other day I tried entering twelve bars worth of a 12/8 phrase into
a csound score manually, and it took most of the evening because I
kept miscounting the syncopated bits and had to keep fixing my
mistakes.

While most instruments are going to take more parameters than the
basic five, in general, the value will just be a "." in a human edited
score.

So, while RG isn't going to output a renderable .csd file any time
soon it is a very handy tool for generating the note lists.

For example, here's a chunk of an actual score I'm working on:

; p1    p2      p3      p4      p5      p6      p7      p8      p9
; Inst  Start   Dur     Amp     Pitch   Press   BowPos  Vfreq   Vamp

i 1     0       1       40      6.00    3       0.13    5       0.01
i 1     +       .       32      6.07    2.5     .       .       .
i 1     +       .       34      7.03    2.0     .       .       .
i 1     +       .       28      6.00    1.5     .       .       .

Note how many of the values past p5 are just dots (repeat the value
from the line before). RG can generate output like the scrap below,
which means that if you wanted to play it with the wgbow instrument
for which the above scrap was written, you'd just have to go through
and tack on the bits after p5. I assure you that this is a huge help
to me. The below output was made using my modified CsoundExport.cpp
file, fyi. The stock version would have "i 0" in place of "i 1" and
would have p4 (Amp) and p5 (Pch) reversed.

;; Inst Start   Dur     Amp     Pch
;; ---- ----    ---     -----   ----
;; Event type: clefchange
;; Event type: keychange
   i1   0       1       127     9.02
   i1   0       1       127     8.11
   i1   0       1       127     8.07
   i1   1       0.3     104     8.07
   i1   1       0.3     104     8.11
   i1   1       0.3     104     9.02
   i1   1.33333 0.3     96      8.07
   i1   1.33333 0.3     96      8.11
   i1   1.33333 0.3     96      9.02
   i1   1.66667 0.183333        96      8.07
   i1   1.66667 0.183333        96      8.11
   i1   1.66667 0.183333        96      9.02
   i1   2       0.6     124     8.07
   i1   2       0.6     124     8.11
   i1   2       0.6     124     9.04
   i1   3       0.6     119     8.07
   i1   3       0.6     119     8.11

(This is the first phrase of one of the tunes from The Nutcracker, btw).

Punching the notes into the notation editor is immensely quicker than
working out the note times in a text editor.

What RG can't do though is to help you with the orchestra files. Kind
of on your own with the documentation on that front. That said, the
folks at the csound mailing list are active and helpful.

The preferable solution would be to have a spreadsheet sort of editor
to which extra columns can be added to accomodate the extra p values.
Pretty sure Qt already has a spreadsheet library built in.

------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Rosegarden-user mailing list
[email protected] - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user

Reply via email to