Re: [Isisalsa-devel] First driver release

[Pieter P. <pie...@st...>]

Adrian Prantl wrote:

>On Saturday 26 July 2003 15:28, Pieter Palmers wrote:
>  
>
>>I personally experience some problems which I cannot pinpoint an origin
>>for. I guess they originate in a spinlock problem.
>>
>>The major tests you should perform are:
>>1) try using both SAM pcm channels (hw:?,1 & hw:?,2) at the same time,
>>for a longer duration (e.g. 2 alsaplayers with a long playlist)
>>    
>>
>that seems to work fine.
>
>  
>
OK

>>2) try using the maestro pcm (hw:?,0) in addition to point 1. This
>>should mess things up
>>    
>>
>it certainly does.. the current buffer seems to be played in an endless loop 
>even if I kill all alsaplayers.
>hmm. when I then try to find the ill-behaving channel with alsamixer my whole 
>system responds really slow, too.
>  
>
That's what I thought... This will be solved in the rewrite.

>  
>
>>3) try starting & stopping a program several times, while other pcm
>>channels are playing, with different fragment sizes, etc... I have the
>>impression that once you open a channel with a specified fragment size,
>>and then close it, you can't use another fragment size on a subsequent
>>open of the channel.
>>    
>>
>see above.
>
where?

>>jackd should be a nice test too.
>>    
>>
>
>For "isis" beeing defined as 
>pcm.isis {
>        type hw
>        card 1
>}
>ctl.isis {
>        type hw
>        card 1
>}
>
>-------------------------
>adrian@vicviper:~$ /usr/local/bin/jackd -d alsa -d isis
>jackd 0.74.1
>Copyright 2001-2003 Paul Davis and others.
>jackd comes with ABSOLUTELY NO WARRANTY
>This is free software, and you are welcome to redistribute it
>under certain conditions; see the file COPYING for details
>
>JACK compiled with System V SHM support
>loading driver ..
>creating alsa driver ... isis|isis|1024|2|48000|nomon|swmeter|rt
>open
>ALSA: the playback and capture components for this PCM device differ in their 
>use of channel interleaving. We cannot use this PCM device.
>starting engine
>engine driver not set; cannot start
>cannot start main JACK thread
>jack main caught signal 15
>-------------------------
>hmmm..
>
This is because Jack needs capture as well as playback, and the current 
ISIS driver doesn't implement capture yet. But I think there is an 
option to jack to force it not to use the capture port:

" -P, --playback
              Provide only playback ports."

This seems to work, provided you use only SAM pcm devices in .asoundrc


Pieter