From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - tools 0001677]: envy24control word clock lock indication is wrong way around
Date: Mon, 2 Jan 2006 21:55:12 +0100 [thread overview]
Message-ID: <17bea621ff378b211bfb3b164b33efbd@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1677>
======================================================================
Reported By: johnrigg
Assigned To:
======================================================================
Project: ALSA - tools
Issue ID: 1677
Category: envy24control
Reproducibility: always
Severity: major
Priority: normal
Status: new
======================================================================
Date Submitted: 12-24-2005 18:03 CET
Last Modified: 01-02-2006 21:55 CET
======================================================================
Summary: envy24control word clock lock indication is wrong
way around
Description:
The word clock `Locked' indication in envy24control's hardware settings is
backwards. It says `Locked' when there's no signal and `No signal' when
it's
locked.
I'm hoping I'll get a large pot of glue for Christmas so I can stick back
all the hair I've torn out over the last couple of weeks over this :-)
Merry Christmas
John
======================================================================
----------------------------------------------------------------------
johnrigg - 12-26-05 13:12
----------------------------------------------------------------------
The above behaviour happens when syncing clocks via the BNC word clock
in/out connectors. When syncing via S/PDIF the indicator just says
`Locked' whether it's locked or not. The only way to tell is if it's
locked jackd will run, if unlocked it won't.
----------------------------------------------------------------------
johnrigg - 01-02-06 21:55
----------------------------------------------------------------------
Now fixed in CVS. Thanks.
Issue History
Date Modified Username Field Change
======================================================================
12-24-05 18:03 johnrigg New Issue
12-26-05 13:12 johnrigg Note Added: 0007150
01-02-06 21:55 johnrigg Note Added: 0007392
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next reply other threads:[~2006-01-02 20:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-02 20:55 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-02 21:38 [ALSA - tools 0001677]: envy24control word clock lock indication is wrong way around bugtrack
2005-12-26 12:12 bugtrack
2005-12-24 17:03 bugtrack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=17bea621ff378b211bfb3b164b33efbd@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox