[Csnd] problems in real-time CSD moving to win 7
| Date | 2012-02-22 07:38 |
| From | Dennis Raddle |
| Subject | [Csnd] problems in real-time CSD moving to win 7 |
| I just moved from XP to Win 7, and a real-time csd that ran perfectly
fine before is now causing clicks. Increasing the -B and -b sizes by a whole lot does reduce but doesn't eliminate the clicks, and is unacceptable latency even if it did eliminate the clicks. The clicks occur when a new instrument initializes, and the clicks are louder when there is more sound going at that moment. This makes me wonder if I did something wrong in my code, but then why did it work fine before, and why does increasing the latency reduce the clicks? I'm using the same version of csound, 5.13. I'm using an M-AUDIO Delta 2496 sound card. The M-AUDIO driver is by necessity different (since I needed a recent Win 7 driver). The motherboard is also different, but I hope that wouldn't matter. Any idea where to start poking around? Mike |
| Date | 2012-02-22 08:07 |
| From | Øyvind Brandtsegg |
| Subject | SV: [Csnd] problems in real-time CSD moving to win 7 |
|
I think you could try the most recent Csound version, as it now supports WASAPI which could be more efficient for realtime audio handling. I haven't gotten around to testing this
myself yet, but frankly I'm dying to get around to do it and find out for myself.
Clicks can commonly occur when you start a new instance of an instrument, and it might be related to instrument init (if there's a lot to be done, allocating ftables etc), and more commonly it is related to printing something to the console. Is anything printed to console when a new instance of an instrument is started? You could try -m0 as a command line flag to minimize printing. best Oeyvind Oeyvind Brandtsegg
Professor of Music Technology NTNU 7491 Trondheim Norway Cell: +47 92 203 205 http://flyndresang.no/ http://www.partikkelaudio.com/ http://soundcloud.com/brandtsegg http://soundcloud.com/t-emp Fra: Dennis Raddle [dennis.raddle@gmail.com]
Sendt: 22. februar 2012 08:38 Til: csound@lists.bath.ac.uk Emne: [Csnd] problems in real-time CSD moving to win 7 I just moved from XP to Win 7, and a real-time csd that ran perfectly fine before is now causing clicks. Increasing the -B and -b sizes by a whole lot does reduce but doesn't eliminate the clicks, and is unacceptable latency even if it did eliminate the
clicks.
The clicks occur when a new instrument initializes, and the clicks are louder when there is more sound going at that moment. This makes me wonder if I did something wrong in my code, but then why did it work fine before, and why does increasing the latency reduce the clicks? I'm using the same version of csound, 5.13. I'm using an M-AUDIO Delta 2496 sound card. The M-AUDIO driver is by necessity different (since I needed a recent Win 7 driver). The motherboard is also different, but I hope that wouldn't matter. Any idea where to start poking around? Mike |
| Date | 2012-02-22 08:27 |
| From | Dennis Raddle |
| Subject | Re: [Csnd] problems in real-time CSD moving to win 7 |
| -m0 fixed it. I was reading MIDI input, so csound was printing vast amounts of stuff to the console. For some reason this was never a problem in XP no matter how dense the MIDI notes were. I guess Win 7 handles the console differently than XP. On Wed, Feb 22, 2012 at 12:07 AM, Øyvind Brandtsegg <oyvind.brandtsegg@ntnu.no> wrote:
|