Jump to content

Rangarajan

Members
  • Posts

    222
  • Joined

  • Last visited

Everything posted by Rangarajan

  1. The new release 1.1.18468 fixes the above modes, but I found a new issue. I think 'raga-rageshri2-rageshwari' should actually be 'raga-rageshri2'. Not sure, though. Regards, Rangarajan
  2. Hi, When I was examining the various modes/scales in the pre-defined 'modes library, I noticed that the following modes all have the same interval as 'major scale: (raga-shankarabharanam mela-shankarabharanam xin ararai rast peruvian-major dastgah-mahur dastgah-rast-panjgah hypolydian-medieval lydian-greek ionian major) In other words, the expression: (pitch-to-interval (expand-tonality '(c4 <a-mode>))) returns the same interval list for all the above modes. I can understand that 'ionian' is the same as 'major', but finding the others to be the same as major scale was a bit surprising. Looks like other musical cultures such as India, Iran, Peru, and Ethiopia used the same major scale under a different name. Can anyone throw further light on this coincidence? Regards, Rangarajan
  3. Hi, I am getting "Error: Unbound variable ..." when I try to use the following modes: phrygian-b4, locrian-b4, blues-scal, blues-scale6, raga-zill, algeria, ewish-scale1, raga-kanakambariraga-kanakambari I checked and found that the last 3 are incorrectly spelt: 'algeria' should be 'algerian' 'ewish-scale1' should be 'jewish-scale1' 'raga-kanakambariraga-kanakambari' should be 'raga-kanakambari' But I do not know about the others. Please check. Regards, Rangarajan
  4. What you have given is perfectly acceptable. The example I gave is from the documentation of the function, where the pitches and lengths are given separately. My observation was with respect to that usage pattern. Anyway, if that pattern is not common, then my suggestion is not very relevant. Regards, Rangarajan
  5. The filter-tie function allows the keyword parameter :omn. On initial reading, I thought this would return the result in OMN form if :omn t is supplied as the option. But that is not the case. Just wondering if changing the behaviour slightly would be useful. For example, (filter-tie (list '(c4 c4 c4 d4 d4 e4) '(e e e e e e)) :omn t) => (q. c4 q d4 e e4) instead of ((c4 d4 e4) (q. q e)) If :omn nil (the default), then the result would be ((c4 d4 e4) (q. q e)) -Rangarajan
  6. I saw use of do-verbose function in SB's "Etude1OrchestraForumExerpt.opmo" file. To the extent I remember, it is not in common lisp and it is not documented in Opusmodus. I would like to learn about it. Regards, Rangarajan
  7. Personally, I prefer to keep 1-based degree in Harmonic-progression. But that will break existing code (which is 0-based). The next preference is to use an extra "key", say :offset to specify whether it is 0-based on 1-based. The default is 0-based to maintain compatibility. If these two are not acceptable, then I would go with: (integer-transpose -1 prog) This is just my preference. -Rangarajan
  8. The documentation for the function "gen-markov-from-transitions" names the function as "gen-markov-form-transitions". Please check and correct. Rangarajan
  9. Thank you. Just out of curiosity, how do I find out what other such "libraries" exist? Where is this list of pre-defined libraries documented? -Rangarajan
  10. Hi, In the documentation of "Tonalities", I can see a large number of interesting pre-defined tonalities. Is this collection exposed as a "Library", or in some other manner? How can I programmatically access these tonalities? Regards, Rangarajan
  11. Very nice. I was doing something similar and felt at that time it might be more useful if the HARMONIC-PROGRESSION function could work with 1-based degrees instead of 0-based degrees. That way, we don't have to subtract 1 as you have correctly done. Regards, Rangarajan
  12. OK, but hope that a future version of Opusmodus will support it! Regards, Rangarajan
  13. Just as compile-score allows us to create a midi output file of the score, is there a way to get mp3 file output? Or should I use some other software for it? Regards, Rangarajan
  14. I got confused between these two comments: #! Can't have this comment inside def-score!!! !# #| This is fine |# What is the first type? I see that in some places, for e.g., in "Stage 11.opmo". I thought this was the block comment in CCL. Regards, Rangarajan
  15. Hi, While single-line comments are accepted within def-score, block comments are not! When I comment out multiple instruments using block comments in def-score, I get compiler error when I "Evaluate and Play". Is this a known issue? Regards, Rangarajan
  16. Hi, Are you saying that N should be greater than the size of the tendency list (arg)? What is the rationale? Secondly, with the keyword :list t option, the result is grouped into 3 element sets. What is this grouping? Regards, Rangarajan
  17. Hi, I am having difficulty understanding this new function. When I read the starting statement "The GEN-TENDENCY function generates N samples of given values (floating numbers)..." I thought, the function will generate N samples from the given list, but it does not do that! It does not directly generate from the "given values". Perhaps it will be of help if the explanation can be elaborated a bit more. For example, what does this do? (gen-tendency 2 '(0.9 0.1 0.7 0.9)) On my system, it gives => (0.917174 0.100803904) I immediately thought it will generate two values closest to what is in the given list, but the following proved me wrong. (gen-tendency 4 '(0.9 0.1 0.7 0.9)) => (0.90942806 0.09511808 0.09851663 0.68883634) Can you explain the behaviour in greater detail? As a beginner, I am not able to relate the generated output with "tendency" argument. Regards, Rangarajan
  18. Amazing, great work! Regards, Rangarajan
  19. I did not know about "melodize". Thanks a lot! As always, your generalisation is very good. Regards, Rangarajan Just now noticed that "melodize" is not documented. Intentional? Regards, Rangarajan
  20. OK, I have written the following function to solve my problem. Is it the correct approach? ;; E.g: (expand-scale '(c4 major)) => (c4 d4 e4 f4 g4 a4 b4) ;; E.g: (expand-scale '(d4 phrygian-greek)) => (d4 e4 f4 g4 a4 b4 c5) (defun expand-scale (root-and-mode-name-pair) (pitch-transpose (first root-and-mode-name-pair) (expand-chord-name (second root-and-mode-name-pair) :type :pitch))) Regards, Rangarajan
  21. Hi, Is there a direct way to get the pitches of a scale represented as, say, '(d4 major)? This representation of scale is well supported in HARMONIC-PROGRESSION function, but I want to get only the pitches in the scale, not the chord or progression. The following works: (expand-chord-name 'major :type :pitch) => (c4 d4 e4 f4 g4 a4 b4) But I want the root to be also specified as part of the scale such as '(d4 minor). The function should ideally be called "expand-scale" or something similar, but I do not find such a function in the library (I may be missing it!) Regards, Rangarajan
×
×
  • Create New...

Important Information

Terms of Use Privacy Policy