Recording

Recording

[Manuel Jander]

Hello,

I'm having serious trouble implementing record support into the Aureal 
Vortex driver.
I get total lockups...

The obvious answer would be: the cards overwrites your kernel :) ... but 
i double checked
that. If that would be the case, playback wouldnt work either (i would 
hear noise, or at least a crack).
I'm using the same operator functions (callbacks) for recording and 
playback with some very few
branch code to decide between record and playback.

Is there something like a typical pitfal list ? Any important difference 
when recording
instead of playback ? Can i use runtime->dma_addr just as when doing 
playback for
the DMA address programmed into the SoundCard ?

If anyone has something to say about recording, please tell me

Best Regards

Manuel Jander



-------------------------------------------------------
This SF.net email is sponsored by:Crypto Challenge is now open! 
Get cracking and register here for some mind boggling fun and 
the chance of winning an Apple iPod:
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en

Re: Recording

[Takashi Iwai]

At Sun, 23 Mar 2003 02:08:51 -0400,
Manuel Jander wrote:
> 
> Hello,
> 
> I'm having serious trouble implementing record support into the Aureal 
> Vortex driver.
> I get total lockups...
> 
> The obvious answer would be: the cards overwrites your kernel :) ... but 
> i double checked
> that. If that would be the case, playback wouldnt work either (i would 
> hear noise, or at least a crack).
> I'm using the same operator functions (callbacks) for recording and 
> playback with some very few
> branch code to decide between record and playback.
> 
> Is there something like a typical pitfal list ? Any important difference 
> when recording
> instead of playback ?

i don't know of any big differences between playback and capture
except for the hardwares which need buffer copy.

> Can i use runtime->dma_addr just as when doing 
> playback for
> the DMA address programmed into the SoundCard ?

yes.

hmm, what i would check are

- the buffer allocation and the hardware config are ok?
	-> check debug print in prepare()
- interrupts properly acknowledged?
	-> check the interrupt handler
- any spin dead locks?
	-> removing locks first (for UP)

and if alt+sysrq works, you can get the trace.


Takashi


-------------------------------------------------------
This SF.net email is sponsored by:
The Definitive IT and Networking Event. Be There!
NetWorld+Interop Las Vegas 2003 -- Register today!
http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en