Re: [Csnd] [EXTERNAL] [Csnd] Problems with -F
Date | 2024-03-20 20:35 |
From | Risto Kuusisto |
Subject | Re: [Csnd] [EXTERNAL] [Csnd] Problems with -F |
The original purpose of this csd was to set (FLsetVal) some FLslider values to CC-values sent through a midi connection from a (ancient) guitar effect processor (Yamaha DG-Stomp). To test the idea i first made a simple midi-file including a few CC's and some note-on's and -off's and used that for testing. Then i found that there is something wrong either in my thinking or missing command-line flags because there were no time-gaps between csound visible printing outputs but midi-file events had quite long time delays between each other. Let me first tell how i think how csound works in this case. My thinking is that the given print-commands in csd-file activate according to the the time-points in the midi-file. So the present very simple csd reads only the midi-file and at the moment there is a new event, prints the information about that. In this case according to the time-stamps i would see messages at the terminal roughly after every 2 s. Here's the csd-file: |
Date | 2024-03-20 20:48 |
From | Victor Lazzarini |
Subject | Re: [Csnd] [EXTERNAL] [Csnd] Problems with -F |
Attachments | favicon.ico |
Ok, what will happen here is that any midi note on in channel will cause instrument 1 to run until you get a midi note off. If you want that, it's what you get. Read this:
This is probably what is confusing you.
However if you want to run instrument 1 as a midi monitor, you need to disable midi triggering of instruments with massign.
Then you can run it as you did and it will just print the midi data coming in from midiin
Prof. Victor Lazzarini
Maynooth University
Ireland
On 20 Mar 2024, at 20:35, Risto Kuusisto <rjzkuusisto@gmail.com> wrote:
|