I just upgraded to Csound 5.08, and I notice two things
when running on Windows XP Pro:

(1) When Csound is interrupted by a Ctl-C, it does not
exit, but rather merely hangs, and must be killed via
the Task Manager.

(2) I just now noticed that at startup, Csound complains:

Pa_GetDeviceInfo: Num input channels reported as 65535! Changed to 2.
Pa_GetDeviceInfo: Num output channels reported as 65535! Changed to 2.

However, my .csd file does say that "nchnls = 1".

Are these known problems? (And if they were, how would
I know that?)

Thanks,

-- JK

-- 
I do not particularly want to go where the money is -
  it usually does not smell nice there. -- A. Stepanov

Adam wrote:
> On Sunday 01 June 2008 02:25 pm, JK wrote:
>> I just upgraded to Csound 5.08, and I notice two things
>> when running on Windows XP Pro:
>>
>> (1) When Csound is interrupted by a Ctl-C, it does not
>> exit, but rather merely hangs, and must be killed via
>> the Task Manager.
> 
> Does it close properly with Ctl-C if you close the ftable 
> graph window first, and then Ctl-C  ?  Or closing when 
> using the -g command line option ? 

It happens whether or not the graph window is displayed.
Using -g makes no difference. If the graph window is
displayed, then hitting ^C in the csound command-line
window causes csound to hang and the graph window to
stop refreshing (that is, damage to the graph window
is never repaired, and attempts to close the graph
window result in Windows displaying a "This process is
not responding. End now?" dialog).

The CPU is not loaded while csound is hung, incidentally.
CPU usage for the csound process goes to 0 and stays there.

I'm only slightly annoyed by this behavior.  If I allow
a score to play through to the end, csound exits cleanly,
so it's only an occasional hassle.  I just wondered if
anyone else was seeing this.

-- JK

-- 
I do not particularly want to go where the money is -
  it usually does not smell nice there. -- A. Stepanov

That's an error that I thought had been removed from portaudio long ago. 
It arises becau8se th "device" being queried is in fact the Windows 
kernel mixer, which automatically downmixes incoming 
(WAVEFORMATEXSTENSIBLE format) audio of N channels to whatever the 
hardware supports; this it always reports 65535 channels as being 
available.  The solution was simply to remove the offending code.

So, worth checking what version of portaudio is being used, etc.



JK wrote:
...
> (2) I just now noticed that at startup, Csound complains:
> 
> Pa_GetDeviceInfo: Num input channels reported as 65535! Changed to 2.
> Pa_GetDeviceInfo: Num output channels reported as 65535! Changed to 2.
> 
> However, my .csd file does say that "nchnls = 1".
> 
> Are these known problems? (And if they were, how would
> I know that?)
> 
> Thanks,
> 
> -- JK
>