Om2csound basic problem

[ma_stro]

Dear Michal,

Are you sure that you have the latest version of OMChroma (5.1)? The function “printdate” is defined in the file “utils.lisp” (in the OMChroma 5.1 / sources / chroma folder), it is an old function which has always worked. When I try add-1 in OMChroma, it works without problems.
If you need to access this function from a patch (it is not an essential one, it just nicely prints the current date in the csound score), you need to type “cr::printdate”. Perhaps you can try it in a patch, just to see if you get the same message.
Let us know, please.
Marco

[michalszostalo]

Dear Marco, thanks a lot, I updated to 5.1 and it fixed the problem. In the meantime, my learning curve with csound has been pretty high (I discovered cabbage, and also some texts by Richard Boulanger), so I’m very excited to learn about all of these new functionalities.

best,
Michal

[bresson]

Hello Michal,
If you read some French (or if you master automatic translation tools!) you can also have a look ad Jean-Michel Darremont’s OM-Csound tutorials:
http://www.jmdarremont.net/tag/csound/

[haddad]

Dear Michal,

For a starter, you can go there:
https://csound.com/get-started.html

Now what about the incorrect pitch sound output?
Can you please specify if this happens while playing audio in OM and/or MIDI ?

Best
K

[michalszostalo]

Dear Karim:

Thank you for the link. The problem for me is the user manuals only start to make sense after I’ve spent a lot of time doing trial and error. So for instance I understand, in theory, that you can make additional p-fields, but not why they don’t seem to work when I make a .sco with them. (I have this problem with OM as well but after 4 years or so, it’s getting better). I found a lot of youtube videos that bridged the gap, though.

Anyway, about the audio, the issue seems to be that audio files come out sharp, in comparison to the MIDI, which I’m almost certain is correct. The really strange part is that when I played them back outside of OM, they were normal (I didn’t know that was even possible). I fiddled with the sample rate and bit rate, but that doesn’t seem to help.

Cher Jean, merci pour ces links, ils sont tres utiles. L’ecriture est proche de mon niveau de comprehension aussi, j’ai apprisait beaucoup en lisant les instructions pour omtristan…

Thanks again and all the best,
M

[michalszostalo]

Just a few more questions:

First, the playback problem was indeed caused by having the wrong sampling rate.

Second: I downloaded OMPrisma (v.2.35) and every single patch gives me this error message:

So, am I missing something obvious, or did I download the wrong version again, or is it a Catalina problem?

best,
Michal

[haddad]

Deear Michal.

Hmm this seems an error with omprisma library. Can you send the patch ?
Best
K

[michalszostalo]

Sorry, I’m not quite sure what you’d like me to send. I’ll take a guess and hope it’s this. 1-overview.omp (7.0 KB).

But actually I get the same message in every patch.

Cheers

[haddad]

No i meant the patch in your screenshot. Anyhow, it is in onprisma help files and called panning. Got it!
THe problem seems as i suspected coming from prisma:

rtmidi: ALSA Raw MIDI module enabled
:: error: e[mUnable to find opcode entry for ‘limit’ with matching argument types:
:: e[mFound: a limit iic
:: adelaytime limit idelaytime …
:: Line: 94
:: from file /home/karim/Downloads/sofia.wrk/out-files/my_synt.orc (1)
:: Parsing failed due to syntax errors
:: Stopping on parser failuree[m
:: e[mcannot compile orchestrae[m
:: e[mend of score. overall amps: 0
:: 1 errors in performance
:: a beep!

Meaning that there’s a non standard Csound opcode used here: limit . It must be a user defined opcode and should be defined here in this synthesis.
Please do contact the author of the library in order to fix this.

Best
K

[michalszostalo]

Thanks, I will try to contact him and let him know. Do you think that one problem would cause the whole library to malfunction?

[smalllotus]

Hi,

there’s a real problem with this patch.

I can open OMPrisma… everything looks ok but your patch asks me that :

twice
and all then box are dead :

the same patch, coming from tutorials, works !

Hoping it helps…

Jerome

[michalszostalo]

OK, this is turning into a real head-scratcher… the patch I sent is directly from the tutorial. So actually I don’t understand anything now.

[haddad]

No Michal,

It is not the whole library that is malfunctioning. It is simply a bug in the .orc generated by the example. I advise you if you need to learn csound, just use the om2csound for a start. Then you can start exploring the amazing omChroma library. As for prisma, i am afraid that you will encounter more than a bug.

Now concerning the Jerome issue, he just opened the patch without the needed linked patches (yes sometimes patches refer to others.). The patch is linked to another one to be found in the help tutorials of the same library.

Best
K

[michalszostalo]

Hi Karim,

That’s how I’m doing it. I am having an easier time with Chroma than OM2Csound (because Chroma doesn’t require me to really know much about CSound), but I am using both. I wanted to use Prism simply to turn the output of Chroma into nice stereo files. The more elaborate stuff isn’t really for me. There is a bit of spatialization in OMChroma, but it seems to be at the i-rate rather than k.

So, either way, I will make do without prisma, but what confuses me is that for me, none of it works (the link I provided is directly from the downloaded helpfiles, I didn’t modify it in any way). OK, back to learning CSound for me,

best,
Michal

[smalllotus]

Dear K,

You gave me an idea for a question.

About patches and sub-patches, is there a way to transform a patch in a patch (green patches) into a sub-patch (red patches) in order to merge everything ? I use do that with copy/paste… there must be a better method.

THX in advance,

Jerome

[haddad]

Yes:

Just slide your green patch into another one. Select your patch, type ‘a’
(TIP: when inside a patch type ‘h’ for help)

Best
K

[michalszostalo]

Hi, just a quick question. I still haven’t figured out how to get OM-Prisma running, and for the time being, I’m learning how to use OM2Csound and OMChroma.

OMChroma has a function called chroma-prisma for basic spatialization. What I’d like to know is, is there anyway to do dynamic spatialization with this tool, or does it only pan notes at the i-rate? In line with this question, can I find specific documentation for the “synthesize” tool somewhere? It seems there are a lot of extra keyword functions (like maybe dynamic panning?) that I’m having a hard time deciphering.

Thanks in advance,
Michal

[haddad]

Dear Michal,

I suggest to post this on the OMChroma discussion. Because, it is not related specifically to synthesisze which is a very general function. The chroma-prisma spatialization is specific to omprisma which s not updated at all (i suggest to contact the author)

Best
K

[ma_stro]

Dear Michal,

You raise an important issue, which is the spatialisation in sound synthesis. OMPrisma was written by Marlon Schumacher to address this issue in a very exhaustive and extremely powerful way. However, it is mainly his work and, to my knowledge, it has not been updated for a while.
Until then, there are two main issues regarding spatialising a sound from inside, that is during its synthesis: how many channels one needs and if the space is dynamic or static.
While there is no general agreement regarding the first issue, the second can lead to a granular spatialisation (static placement of short sounds yielding the impression that a sound moves) or to a dynamic one (the sound itself moves during its synthesis).
Give the lack of agreement, the quickest solution for you would probably be to write a Csound orchestra that fits to your needs, then generate a OMChroma class from it (through “get-instrument”, which is relatively well documented). I took away the non-mono orchestras in OMChroma when OMPrisma was released, in order not to have hundreds of classes differing only from their number of channels, but one might think to put some back to the library, it this is needed.
I hope that this long reply may help you.
Best,
Marco

[michalszostalo]

Dear Marco,

Thanks for your reply, and please excuse my delay in replying, I just returned from a 2-week camping trip and wasn’t using the internet. I’ve figured out how to do static spatialization (at least in a simple way), but it would be interesting to do something with dynamic spatialization. I also recently discovered the ‘make instrument’ function, and I’m planning to try it out this week. To be honest, though, my understanding of spatialization in CSound is pretty dim, as I’m still learning the software. I’ve managed to create some interesting stereo effects more or less by accident though, that don’t make use of the spatialization opcodes at all.

If you might be willing to make some of the other (stereo) libraries available, I would be very grateful.

best,
Michal

P.S. I wrote to Mr. Schumacher but I’m not sure if he received my message, so for the time being Chroma is off the table.