ice1724: from 1.0.4 to 1.0.5a upgrading problem

ice1724: from 1.0.4 to 1.0.5a upgrading problem

[Andrew Gaydenko]

Hi,

After upgrading the driver from 1.0.4 to 1.0.5a I'm not able to start jack server
with 96000 rate for alsa driver. I use hw:0,1 device which is digital out in my
Terratek  Aureon Space 7.1. Instead of 96000, jack server starts with 48000. For
hw:0,0 the problem doesn't take place. Can anybody point me further direction to
resolve the problem?

P.S. BTW, 1.0.5a driver has few new mixer controls. What are meaning of
     these controls: 'ADC Oversampling' and 'DAC Deemphasis Switch'?

Andrew


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com

Re: ice1724: from 1.0.4 to 1.0.5a upgrading problem

[Takashi Iwai]

At Wed, 14 Jul 2004 17:18:03 +0400,
Andrew Gaydenko wrote:
> 
> Hi,
> 
> After upgrading the driver from 1.0.4 to 1.0.5a I'm not able to start jack server
> with 96000 rate for alsa driver. I use hw:0,1 device which is digital out in my
> Terratek  Aureon Space 7.1. Instead of 96000, jack server starts with 48000. For
> hw:0,0 the problem doesn't take place. Can anybody point me further direction to
> resolve the problem?

The digital out doesn't support 96kHz (yet)...


> P.S. BTW, 1.0.5a driver has few new mixer controls. What are meaning of
>      these controls: 'ADC Oversampling' and 'DAC Deemphasis Switch'?

The former defines the oversampling range, either 128 or 64 times.
The latter is a toggle switch to turn on/off deemphasis (I forgot the
frequency...)  You can turn if off unless you need something special.


Takashi


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com

Re: ice1724: from 1.0.4 to 1.0.5a upgrading problem

[Andrew Gaydenko]

Takashi,

To tell the truth, have not understood the word "yet": just now (with 1.0.4)
my receiver (as qjackctl) shows 96KHz (alsaplayer-jack-alsadriver-hw:0,1-spdif).
Does it mean some redesign was done for this driver since 1.0.4?

Andrew

======= On Wednesday 14 July 2004 17:32, Takashi Iwai wrote: =======
At Wed, 14 Jul 2004 17:18:03 +0400,
Andrew Gaydenko wrote:
> 
> Hi,
> 
> After upgrading the driver from 1.0.4 to 1.0.5a I'm not able to start jack server
> with 96000 rate for alsa driver. I use hw:0,1 device which is digital out in my
> Terratek  Aureon Space 7.1. Instead of 96000, jack server starts with 48000. For
> hw:0,0 the problem doesn't take place. Can anybody point me further direction to
> resolve the problem?

The digital out doesn't support 96kHz (yet)...


...

Takashi


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com

Re: ice1724: from 1.0.4 to 1.0.5a upgrading problem

[Takashi Iwai]

At Wed, 14 Jul 2004 17:49:42 +0400,
Andrew Gaydenko wrote:
> 
> Takashi,
> 
> To tell the truth, have not understood the word "yet": just now (with 1.0.4)
> my receiver (as qjackctl) shows 96KHz (alsaplayer-jack-alsadriver-hw:0,1-spdif).
> Does it mean some redesign was done for this driver since 1.0.4?

The spdif doesn't support 96kHz without a special handling.
It was a bug that 96kHz was accepted for that interface.


Takashi


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com

Re: ice1724: from 1.0.4 to 1.0.5a upgrading problem

[Tommi Sakari Uimonen]

>> To tell the truth, have not understood the word "yet": just now (with 1.0.4)
>> my receiver (as qjackctl) shows 96KHz (alsaplayer-jack-alsadriver-hw:0,1-spdif).
>> Does it mean some redesign was done for this driver since 1.0.4?
>
> The spdif doesn't support 96kHz without a special handling.
> It was a bug that 96kHz was accepted for that interface.

Does this affect all soundcards that use ice1712 driver?

About a year ago I synced two MAudio Delta cards (AP 2496 & 1010LT) 
through spdif and the rate was 96khz for the master card. I experienced 
some driver lockups and I had to do '/etc/init.d/alsa restart' after every 
recording to have 'fresh' start for new recording.

But other than that, sync worked fine.

(I remember that few months later some patch was sent to fix some spdif 
issue with ice1712, but I don't know if that would have fixed my problem, 
or was it due to this current situation)

Tommi


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click

Re: ice1724: from 1.0.4 to 1.0.5a upgrading problem

[Andrew Gaydenko]

Takashi,

Inspired with successfull resolving of "build error in pcm_native.c"
problem I have become rather brave to ask some additional questions
concerning this message subject:

- am I understand well, there were attempts to supply 96k earlier,
  but old code has not supplied a working of 96k for wide range of
  users, and code was redone to be more democratic but less functional
  (at least for me)?

- what does it mean: "special handling" for 96k? Who is handler?
  User? Further driver version?

- are there some development patches to try 96k on current CVS base?

Thanks in advance,
Andrew

======= On Wednesday 14 July 2004 17:57, Takashi Iwai wrote: =======
At Wed, 14 Jul 2004 17:49:42 +0400,
Andrew Gaydenko wrote:
> 
> Takashi,
> 
> To tell the truth, have not understood the word "yet": just now (with 1.0.4)
> my receiver (as qjackctl) shows 96KHz (alsaplayer-jack-alsadriver-hw:0,1-spdif).
> Does it mean some redesign was done for this driver since 1.0.4?

The spdif doesn't support 96kHz without a special handling.
It was a bug that 96kHz was accepted for that interface.


Takashi





-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click

Re: ice1724: from 1.0.4 to 1.0.5a upgrading problem

[Takashi Iwai]

At Fri, 16 Jul 2004 18:58:08 +0400,
Andrew Gaydenko wrote:
> 
> Takashi,
> 
> Inspired with successfull resolving of "build error in pcm_native.c"
> problem I have become rather brave to ask some additional questions
> concerning this message subject:
> 
> - am I understand well, there were attempts to supply 96k earlier,
>   but old code has not supplied a working of 96k for wide range of
>   users, and code was redone to be more democratic but less functional
>   (at least for me)?

for SPDIF?  i don't know of it...

> - what does it mean: "special handling" for 96k? Who is handler?
>   User? Further driver version?

96kHz is not defined in the standard format.
it was an extention.

> - are there some development patches to try 96k on current CVS base?

no.

to make the things clearer: the analog works fine with 96/192kHz.
only the spdif matters.


Takashi

> Thanks in advance,
> Andrew
> 
> ======= On Wednesday 14 July 2004 17:57, Takashi Iwai wrote: =======
> At Wed, 14 Jul 2004 17:49:42 +0400,
> Andrew Gaydenko wrote:
> > 
> > Takashi,
> > 
> > To tell the truth, have not understood the word "yet": just now (with 1.0.4)
> > my receiver (as qjackctl) shows 96KHz (alsaplayer-jack-alsadriver-hw:0,1-spdif).
> > Does it mean some redesign was done for this driver since 1.0.4?
> 
> The spdif doesn't support 96kHz without a special handling.
> It was a bug that 96kHz was accepted for that interface.
> 
> 
> Takashi
> 
> 
> 


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click