In the new year, Paul Davis wrote: > >Sometimes it says the clock source is word clock and in () it puts no > >signal, and sometimes it doesn't. > > right. you can choose word clock, but if there's no word clock source, > it will default back to the internal word clock source (the h/w does > this, not the driver). > Does the driver get notified of this?
> >If I arecord card0 at 96000, card1 still shows 48000 for its sample > >rate. > > thats correct. there is no 96kHz rate for ADAT. there is no way for > card1 to know that card0 is operating at "double speed mode". this has > always been a hack on all ADAT equipment: you have to explicitly tell > (by pressing a button or running some s/w) each end of the connection > that you're running in double speed, since at the low level, things > have stayed exactly the same: the bits still move at 48kHz. they just > send 1 "channel"'s worth over 2 channels. > even if using word clock? RME suggests word clock can go as low as 25khz to 105khz > I can then not bring the cards back to 48000 or 44100 unless I > >unload and reload the modules--I get device or resource busy if I try to > >switch back. > > it is supposed to stop you from doing this if the card is in use, > because it changes the channel counts and thus many other things. > what were you using to try to change the rates? > arecord, ecasound, ardour, it doesn't matter. _J > --p > > _______________________________________________ > Alsa-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/alsa-devel > _______________________________________________ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
