Skip to contentSkip to conversation

C-Media 8738 SPDIF problem

Alsa-user Thomas Tonino 4 participants 8 messages Feb 16, 2002 – Feb 18, 2002 8 messages not in the archive

lore
Share & tools
lore
#8 lore raw
In reply to a message not in the archive
Quoted 4 lines · Takashi Iwai

Done. Now committed cvs.
please give a try.

Sorry for responding so late. Here are the results for the cmipci driver cvs version as of today:

I see no way to listen to a signal on the digital input.
In a standard setting, there is no signal on the normal analog output.

I can get analog out by:

unmute IEC958 Output
(this enables digital out, as expected)

unmute IEC958 In Monitor
(strangely enough, this routes the IEC output to the internal DAC)

When I input an spdif signal, this has no effect.

When I enable SPDIF loop, the SPDIF signal goes, but the internal DAC keeps playing with the above settings.

But both IEC958 Output and IEC958 In Monitor need to be enabled to get analog out.

But with SPDIF loop on, I see no way to get a signal in the coaxial input repeated on the output and/or DAC.

In the above setting, the PCM volume slider and mute controls have no effect.

Cheers,

Thomas

_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

#10 lore raw

PCM frames already played

Is there a way to determine the number of bytes/frames already played through the DAC since last reset via snd_pcm_status in v0.9.x ?

Its possible in OSS via ioctl and in alsa v0.5.0 you can view at a element "bytes" in sthe respective structure.

But how does it work in v0.9.x ?

rds guenther

_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

#11 lore raw

RE: PCM frames already played

I do this by counting how many frames have already been written(from the app), minus the frames still waiting to be written (from alsa, i.e. How many frames are still in the sound cards buffer waiting to be output.)

Cheers
James

Quoted 19 lines

-----Original Message-----
From: [email protected] [mailto:[email protected]]On Behalf Of Guenther Sohler
Sent: 17 February 2002 10:28
To: [email protected]
Subject: [Alsa-devel] PCM frames already played

Is there a way to determine the number of bytes/frames already played through
the DAC since last reset via snd_pcm_status in v0.9.x ?

Its possible in OSS via ioctl and in alsa v0.5.0 you can view at a element "bytes" in sthe respective structure.

But how does it work in v0.9.x ?

Quoted 6 lines

rds guenther

_______________________________________________
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

#12 lore raw

RE: PCM frames already played

Thank you very much. This sounds reasonably. I will try it. Until now I hoped there would be a more easy solution. But this is ok.

rds guenther

Quoted 35 lines · On 17-Feb-02 James Courtier-Dutton wrote:

I do this by counting how many frames have already been written(from the app), minus the frames still waiting to be written (from alsa, i.e. How many frames are still in the sound cards buffer waiting to be output.)

Cheers
James

Quoted 19 lines

-----Original Message-----
From: [email protected] [mailto:[email protected]]On Behalf Of Guenther Sohler
Sent: 17 February 2002 10:28
To: [email protected]
Subject: [Alsa-devel] PCM frames already played

Is there a way to determine the number of bytes/frames already played through
the DAC since last reset via snd_pcm_status in v0.9.x ?

Its possible in OSS via ioctl and in alsa v0.5.0 you can view at a element "bytes" in sthe respective structure.

But how does it work in v0.9.x ?

Quoted 6 lines

rds guenther

_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Quoted 4 lines

_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Guenther Sohler

NewLogic Technologies AG
Millennium Park 6
A-6890 Lustenau

                                           Phone: +43-5577-62000-507

E-Mail: [email protected] Fax: +43-5577-62000-988

_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

#13 lore raw

Receiving Sequencer Events

In reply to James Courtier-Dutton

Hallo List,

I want to receive midi events from my external midi keyboard.

Therefore I tried the seq decoder which comes with the alsa package. This application creates a port and when I connect the midi port to this listener ports, i can see the events coming from the keyboard.

That means, If i want to receive events, i have to create a port and connect it to the source port(external midi "port") - then receive the events with

snd_seq_input_event (not sure whether this is the correct name)

My question: is'nt it possible receiving events without creating a port.

For sure snd_seq_input_event cannot know where to get the events from, but how can i tell snd_seq_input_event ???

rds guenther

_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

#14 lore raw

Re: Receiving Sequencer Events

Quoted 8 lines · Guenther Sohler

Hallo List,

I want to receive midi events from my external midi keyboard.

Therefore I tried the seq decoder which comes with the alsa package. This application creates a port and when I connect the midi port to this listener ports, i can see the events coming from the keyboard.

Quoted 6 lines

That means, If i want to receive events, i have to create a port and connect it to the source port(external midi "port") - then receive the events with

snd_seq_input_event (not sure whether this is the correct name)

My question: is'nt it possible receiving events without creating a port.

Sorry, but the MIDI router code must know a destination which is given exactly a client+port address. This is concept of the ALSA's sequencer code.

Jaroslav

-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project http://www.alsa-project.org
SuSE Linux http://www.suse.com

_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

#15 lore raw

Re: Receiving Sequencer Events

Thank you very much. I'll implement it like that.

rds guenther

Quoted 22 lines · On 17-Feb-02 Jaroslav Kysela wrote:
Quoted 8 lines · Guenther Sohler

Hallo List,

I want to receive midi events from my external midi keyboard.

Therefore I tried the seq decoder which comes with the alsa package. This application creates a port and when I connect the midi port to this listener ports, i can see the events coming from the keyboard.

Quoted 7 lines

That means, If i want to receive events, i have to create a port and connect it
to the source port(external midi "port") - then receive the events with

snd_seq_input_event (not sure whether this is the correct name)

My question: is'nt it possible receiving events without creating a port.

Sorry, but the MIDI router code must know a destination which is given exactly a client+port address. This is concept of the ALSA's sequencer code.

Quoted 8 lines

Jaroslav

-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project http://www.alsa-project.org
SuSE Linux http://www.suse.com

Guenther Sohler

NewLogic Technologies AG
Millennium Park 6
A-6890 Lustenau

                                           Phone: +43-5577-62000-507

E-Mail: [email protected] Fax: +43-5577-62000-988

_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel