[Csnd] MIDI and qutecsound
Date | 2009-11-16 10:40 |
From | Victor Lazzarini |
Subject | [Csnd] MIDI and qutecsound |
Andres, I have found that there is a problem with QuteCsound running MIDI, which might be only with PortMIDI (on the Mac there is no choice). When playing with -M , QuteCsound crashes after the performance is stopped (and started again or if you try to click on any interface element, for instance to quit). This might or might not be related to the fact that PortMIDI is not reentrant. So I guess a Csound instance has to be completely destroyed for PortMIDI to restart (but even that might not be enough). Anyway, this is something you might want to watch out for. Also: when using FLTK (say the Virtual Keyboard), whenever a performance is finished, qutecsound exits. This might be to do with some funny interaction between FLTK and Qute. Victor Send bugs reports to this list. To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" |
Date | 2009-11-16 11:05 |
From | Rory Walsh |
Subject | [Csnd] Re: MIDI and qutecsound |
I've had problems with this too. I can run one midi instrument once but when I try again I get a portmidi error saying invalid device id. If I run in terminal it runs fine. Rory. 2009/11/16 Victor Lazzarini |
Date | 2009-11-16 11:10 |
From | Victor Lazzarini |
Subject | [Csnd] Re: Re: MIDI and qutecsound |
Can you try -+rtmidi=mme if you are on Windows? This is to see if the problem is with portmidi. On 16 Nov 2009, at 11:05, Rory Walsh wrote: > I've had problems with this too. I can run one midi instrument once > but when I try again I get a portmidi error saying invalid device id. > If I run in terminal it runs fine. > > Rory. > > > 2009/11/16 Victor Lazzarini |
Date | 2009-11-16 11:36 |
From | Rory Walsh |
Subject | [Csnd] Re: Re: Re: MIDI and qutecsound |
I'll try it later when I get a chance, I hadn't thought of that before. 2009/11/16 Victor Lazzarini |
Date | 2009-11-16 16:10 |
From | Iain McCurdy |
Subject | [Csnd] RE: Re: Re: Re: MIDI and qutecsound |
I don't seem to having the same problems you guys are having. Stopping and restarting PortMIDI works fine for me on both IntelMac10.4 and WinXP, both running Csound5.11. Using virtual keyboard causes spontaneous quitting when trying to stop a normal QuTe session. Run in Terminal and virtual keyboard works fine and quits and restarts in both for me. Iain. > From: rorywalsh@ear.ie > Date: Mon, 16 Nov 2009 11:36:29 +0000 > To: csound@lists.bath.ac.uk > Subject: [Csnd] Re: Re: Re: MIDI and qutecsound > > I'll try it later when I get a chance, I hadn't thought of that before. > > 2009/11/16 Victor Lazzarini <Victor.Lazzarini@nuim.ie>: > > Can you try -+rtmidi=mme if you are on Windows? This is to see if the > > problem is with portmidi. > > On 16 Nov 2009, at 11:05, Rory Walsh wrote: > > > >> I've had problems with this too. I can run one midi instrument once > >> but when I try again I get a portmidi error saying invalid device id. > >> If I run in terminal it runs fine. > >> > >> Rory. > >> > >> > >> 2009/11/16 Victor Lazzarini <Victor.Lazzarini@nuim.ie>: > >>> > >>> Andres, > >>> > >>> I have found that there is a problem with QuteCsound running MIDI, which > >>> might be only with PortMIDI (on the Mac there is no choice). > >>> > >>> When playing with -M , QuteCsound crashes after the performance is > >>> stopped > >>> (and started again or if you try to click on any interface element, for > >>> instance to quit). > >>> > >>> This might or might not be related to the fact that PortMIDI is not > >>> reentrant. So I guess a Csound instance has to be completely destroyed > >>> for > >>> PortMIDI to restart (but even that might not be enough). > >>> > >>> Anyway, this is something you might want to watch out for. > >>> > >>> Also: when using FLTK (say the Virtual Keyboard), whenever a performance > >>> is > >>> finished, qutecsound exits. This might be to do with some funny > >>> interaction > >>> between FLTK and Qute. > >>> > >>> Victor > >>> > >>> > >>> Send bugs reports to this list. > >>> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe > >>> csound" > >>> > >> > >> > >> Send bugs reports to this list. > >> To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe > >> csound" > > > > > > > > Send bugs reports to this list. > > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe > > csound" > > > > > Send bugs reports to this list. > To unsubscribe, send email sympa@lists.bath.ac.uk with body "unsubscribe csound" Use Hotmail to send and receive mail from your different email accounts. Find out how. |
Date | 2009-11-16 16:27 |
From | Rory Walsh |
Subject | [Csnd] Re: RE: Re: Re: Re: MIDI and qutecsound |
Actually I'm no longer experiencing those problems either? Most likely it was the midi device I was using which I don't have access to now, it was a midiman usb converter. It seems to work fine now with my M-Audio keyboard and my UC-33 controller. Rory. 2009/11/16 Iain McCurdy |
Date | 2009-11-16 17:11 |
From | Victor Lazzarini |
Subject | [Csnd] Re: Re: RE: Re: Re: Re: MIDI and qutecsound |
Well on OSX 10.5, I get this issue. Not sure really what the problem is. Victor On 16 Nov 2009, at 16:27, Rory Walsh wrote: > Actually I'm no longer experiencing those problems either? Most likely > it was the midi device I was using which I don't have access to now, > it was a midiman usb converter. It seems to work fine now with my > M-Audio keyboard and my UC-33 controller. > > Rory. > > > 2009/11/16 Iain McCurdy |
Date | 2009-11-17 07:58 |
From | Andres Cabrera |
Subject | [Csnd] Re: Re: Re: RE: Re: Re: Re: MIDI and qutecsound |
Hi Victor, Are you using -Ma? I fixed a bug for this after the latest release, so it should be fine in cvs but the release version will crash when using -Ma. Also you can check too see if the problem is Csound or QuteCsound by running inside QuteCsound in an external terminal. If Csound exits cleanly there, it's QuteCsound's fault. Let me know if you can pinpoint the problem. Cheers, Andrés On 11/16/09, Victor Lazzarini |
Date | 2009-11-17 08:47 |
From | victor |
Subject | [Csnd] Re: Re: Re: Re: RE: Re: Re: Re: MIDI and qutecsound |
No, I 'm not using -Ma. Running csound on the terminal is fine, but then the reentrant issues with portmidi are not relevant. I'll see what I can find out more. I'll update from svn and then rebuild, just in case. Victor ----- Original Message ----- From: "Andres Cabrera" |
Date | 2009-11-17 08:51 |
From | Andres Cabrera |
Subject | [Csnd] Re: Re: Re: Re: Re: RE: Re: Re: Re: MIDI and qutecsound |
Hi Victor, QuteCsound destroys Csound on every run (you can change this behavior by removing definition of the QUTECSOUND_DESTROY_CSOUND in line 52 of src/qutecsound.h), so I'm not sure what the problem was... Cheers, Andrés On Tue, Nov 17, 2009 at 8:47 AM, victor |
Date | 2009-11-17 09:50 |
From | Victor Lazzarini |
Subject | [Csnd] Re: Re: Re: Re: Re: Re: RE: Re: Re: Re: MIDI and qutecsound |
I'll see if I can find out what is going on. Since this is not happening elsewhere, it's not a major concern. Victor On 17 Nov 2009, at 08:51, Andres Cabrera wrote: > Hi Victor, > > QuteCsound destroys Csound on every run (you can change this behavior > by removing definition of the QUTECSOUND_DESTROY_CSOUND in line 52 of > src/qutecsound.h), so I'm not sure what the problem was... > > Cheers, > Andrés > > On Tue, Nov 17, 2009 at 8:47 AM, victor |