Not an upload but this is a taster for what is to come.
The spectrum analyser is completed and nothing like the primitive free version previously uploaded here.
The images start with a voice capture using SOX and displayed at 5mS/Division, Note the red CAPTURE mode inside the top little window. In the COMMAND window the command SPECAN is ready to be entered.
Once entered the next image prompts for an External source for measurement input, for example the external microphone. 'N' will be entered and a 48000 byte main capture raw file is converted to an 8000 byte version for the limited 4KHz resolution of this code. I will try and extend to at least 24KHz resolution at a later date.
After a few seconds the spectrum displays this low resolution capture. This will automatically switch from main red CAPTURE mode to green STORAGE mode for the last image to write protect the current main capture. This display awaits an ENTER to return to the STORAGE screen of the original capture.
This User Gave Thanks to wisecracker For This Post:
We have a system running ssh. When a user logs in, they do not get the project they are assigned to (they run under "system"). I verify the project using the command "ps -e -o user,pid,ppid,args,project". If you do a "su - username", the user does get the project they are assigned to (and all... (2 Replies)
A new project was posted on your project board.
Project title: Bash Shell Tutoring
Estimated Budget:
$50/hr
Start date:
Immediately
Required skills:
Linux, Bash, Shell, UNIX
I work as a datawarehouse designer and developer.
Although I usually stick to the role of an analyst,... (0 Replies)
Hi Admin and Staff...
Thanks for hosting AudioScope.sh on this site. I have had the biggest surprise of my life today.
This months issue of the UK Linux magazine "Linux Format" have done a small piece on the project.
Issue April 2014, LXF 182, page 65...
This I never expected and I... (1 Reply)
Hi all...
Has _below_ ever been done in UNIX shell scripting before?
(I have done this easily in Python but this is using purely the shell.)
The DEMO version IS built and has been tested.
Pre-amble...
I now need at least one control pulse for the AudioScope.sh when in PURELY audio I/O mode,... (2 Replies)
Development machine:- Standard MBP 13 inch, OSX 10.7.5...
GNU bash, version 3.2.48(1)-release (x86_64-apple-darwin11)
Copyright (C) 2007 Free Software Foundation, Inc.
Scenario:- Audio capture for AudioScope.sh for CygWin without ANY third party installs.
I am trying my hardest to get a... (6 Replies)
Hi guys...
Well I have entered an area of partial insnity... ;o)
Below is a photo of the 'ALTDC' board for AudioScope.sh...
I have decided to incorporate all three methods for obtaining DC into this MBP via the MIC input.
1) VFO.
2) CHOPPER.
3) COUNTER.
The controller for the COUNTER... (9 Replies)
Boy oh boy, with only a MONO mic input to use AudioScope gets much more difficult when the ALTDC board is included.
It needs, so far, two hits at the MIC input with a single hit at the HEADPHONE audio output.
The first at the highest practical resolution for the AC component and the second... (0 Replies)
Hi all...
Apologies for any typos...
For those intersted in the AudioScope the next construction is finished.
I have not been totally idle but working out the hard stuff to be able to be very simple to build.
It is a single transistor simple timer that lasts for about 1.2 to 1.8 seconds.... (2 Replies)
Using AudioScope.sh on Ubuntu 17.04 from a live DVD disc I came across an error.
Consider the code below it is a MUCH shortened version of the KEYBOARD input in AudioScope.
#!/bin/bash
bash --version
uname -a
status=0
KEYBOARD()
{
read -r -p "Enter QUIT or EXIT to quit:- " kbinput
if ||... (11 Replies)
Discussion started by: wisecracker
11 Replies
LEARN ABOUT DEBIAN
evtest-capture
EVTEST-CAPTURE(1)EVTEST-CAPTURE(1)NAME
evtest-capture - Input device event capture program
SYNOPSIS
evtest-capture "/dev/input/eventX" [evtest-capture.xml]
DESCRIPTION
evtest-capture captures the information and events from the input device specified on the command line and writes it to the xml file given.
If no filename is given for the output file, evtest-capture.xml is chosen as default.
evtest-capture needs to be able to read from the device; in most cases this means it must be run as root.
Together with with evtest-create-device.xsl, a simple uinput-based software input device can be created that replays the events as if the
same input was performed on the physical device. This can be useful to replicate bugs with input devices in upper layers of the stack.
To convert evtest-capture.xml into such a uinput device, run:
xsltproc evtest-create-device.xls evtest-capture.xml > mydevice.c
gcc -o mydevice mydevice.c
./mydevice
DIAGNOSTICS
If evtest-capture does not see any events even though the device is being used, the device may be grabbed by a process (EVIOCGRAB). This is
usually the case when debugging a synaptics device from within X. VT switching to a TTY or shutting down the X server terminates this grab
and synaptics devices can be debugged.
SEE ALSO evtest(1)AUTHOR
evtest-capture was written by Peter Hutterer <peter.hutterer@redhat.com[1]>.
NOTES
1. peter.hutterer@redhat.com
mailto:peter.hutterer@redhat.com
05/21/2012 EVTEST-CAPTURE(1)