From: chrubis@suse.cz
To: subashchandra.bose@wipro.com
Cc: ltp-list@lists.sourceforge.net
Subject: Re: [LTP] Getting User input data not working
Date: Mon, 7 Jan 2013 11:52:47 +0100 [thread overview]
Message-ID: <20130107105247.GA4812@rei> (raw)
In-Reply-To: <27EF8FABF41315449203A213FE201313553430FD@BLR-SJP-MBX-4.wipro.com>
Hi!
> Thanks for the response, I want to test sound driver releated testing to do playback and capture where, User needs to confirm playback and capture functionlity.
>
> So, based on User feedback I want flag the testcase pass or fail.
What about physically plugging the output cable to the capture input?
That way you can check that you have recorded something similar to the
sound that has been played. Exact matching would be really hard, but if
you play something like 1Hz sine wave you can simply use fftw library to
match the frequency...
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
MVPs and experts. SALE $99.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122412
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
prev parent reply other threads:[~2013-01-07 10:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-26 4:53 [LTP] Getting User input data not working subashchandra.bose
2013-01-03 11:23 ` chrubis
[not found] ` <EAFD815A-FF7B-4FCE-B88D-B1077401C753@gmail.com>
[not found] ` <27EF8FABF41315449203A213FE201313553430FD@BLR-SJP-MBX-4.wipro.com>
2013-01-07 10:52 ` chrubis [this message]
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=20130107105247.GA4812@rei \
--to=chrubis@suse.cz \
--cc=ltp-list@lists.sourceforge.net \
--cc=subashchandra.bose@wipro.com \
/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