Save your praat scripts before you run them. That way, if they take too long, you can run them from the command line and get on with work.

Love,

Leanne
Like · · 8 minutes ago near Seattle, WA ·

C.J. Adams-Collier Yeah, by the way, the command line is usually the way to go if you want to get anything done. I get lost with all those buttons. I’ve got 104 of them I keep pretty good track of. Those ones that keep moving around? Yeah, that’s confusing.
6 minutes ago · Like
Leanne Rolston I’ve noticed. I need to add praat to my path so I can stop having to hunt it down every time I want to do something!
5 minutes ago · Like
C.J. Adams-Collier also, teach me praat?
5 minutes ago · Like
C.J. Adams-Collier cjac@phx1:/usr/share/wordpress/wp-content/plugins$ apt-cache search praat
praat – program for speech analysis and synthesis
4 minutes ago · Like
C.J. Adams-Collier oh, nevermind. my homies already taught me.
4 minutes ago · Like
Leanne Rolston Sure. It’s simple – In the praat scripting window, there’s a paste history command.. anything you want to do, do it using the buttons, paste history, and kapow!
3 minutes ago · Like
C.J. Adams-Collier $ less /usr/share/doc/praat/README.Debian
3 minutes ago · Like
C.J. Adams-Collier can I save the script that I put together with buttons to something I can open with emacs?
2 minutes ago · Like
Leanne Rolston Yup. Just save it with a .praat extension.
about a minute ago · Like
Leanne Rolston http://depts.washington.edu/phonlab/resources.htm <=- some good sample scripts, and praat has a scripting tutorial.
Phonetics Lab | Department of Linguistics | University of Washington
depts.washington.edu
The Phonetics Lab at UW is located in Padelford Hall, Room A-216 on the campus of UW Seattle.
a few seconds ago · Like
C.J. Adams-Collier http://www.ling.lu.se/persons/Sidney/praate/frames.html

.

When we were living at 6162 NE Middle in the nine-eight 292, we got an 80386 which ran Doom. Yeah, the original one, not the fancy new one with the double barrel shotgun, but it would probably run that one, too. It was also totally sweet and all thanks to our armadillo friends down south and partially thanks to their publishers, Apogee. I suckered my brothers into giving me their allowance from Dad one time so that we could all go in on a Sound Blaster Pro 16 sound card for the family’s 386. I played a lot of Team Fortress and Q2CTF on that rig. I even attended the Quake 3 Arena launch party that happened at Zoid‘s place. I recall that he ported the original quake to Linux. I also recall there being naughty remarks included in the README.txt.

When my older brother, Aaron turned 16, he was gifted a fancy car. When asked what type of car I would like when I turned 16, I said that I’d prefer a computer instead. So I got a high-end 80486 with math co-processor. It could compile the kernel in 15 minutes flat. With all the bits turned on on in /usr/src/linux/.config. But this was later. I hadn’t even heard of linux when I got my system. I wanted to be entertained by the thing. I made sure to get a CD-Rom and a sound card. I got on the beta for Ultima Online and spent a summer as a virtual collier. Digging stuff out of mines north of Britannia and hauling them to town to make weapons and armor out of them. And then setting out in said armor only to be PK’d because I forgot healing potions and I was no good at fighting.

While I was in the middle of all this gaming, my friend Lucas told me that I should try out this lynx thing that they run at the University of Washington. He heard that it was reported to run doom faster than it ran on MS-DOS. It turns out that it did, but that it was not, in fact, called lynx. Or pine. The Doom engine ran so fast that the video couldn’t keep up. This was probably because they didn’t use double buffering for frame display, since they didn’t want to waste the time maintaining and switching context. I think I downloaded the boot/root 3.5″ disk pair and was able to get the system to a shell with an on-phone assist from the Rev. I then promptly got lost in bash and the virtual terminals (OMG! I GET SIX CONSOLES!?) and bought a book on the subject. It shipped with slackware. Which I ran. Until Debian came along. Lucas also recommended that I try out this IRC thing, so I did. And I’m still doing it on #linpeople just like I did back then.

I learned to write Pascal on dos. Then I learned c while they were trying to teach me c++. I learned emacs and vi when I was attending North Kitsap High School. I learned sed and only a little awk when I took Running Start classes in Lynnwood at Edmonds Community College and perl & x.509 while attending Olympic Community College and simultaneously jr-administering Sinclair Communications. I studied TCP/IP, UNP, APUE, C and algorithms & data structures while preparing for an interview with a company whose CEO claimed to have invented SCSI. I learned PGP and PHP while writing web-based adware for this company. I didn’t want to write ads and instead wanted to work in security, so took a job with Security Portal. While there, I wrote what one might call a blogging platform. It worked and made it possible for authors to write prose and poetry. Editors didn’t have to manage a database in order to review and publish the posts that were “ready.” Everyone but me was able to avoid html and cgi.

Then I sold pizza. Then I helped bring the bombay company onto the interwebs using the Amazon ECS (now AWS) platform. Then I helped support MaxDB. Then I helped develop and maintain the Amazon blogging platform. And then attempted to reduce the load on the Amazon pager system by doing and enforcing code reviews. It turns out that they prefer to run their support team at full bore and a load average of 16.

I am now, still, fully employed in an effort to make hard things possible. The hard thing we’re working on now is the implementation and ongoing operations of distributed x.500 infrastructure. This includes request handling, processing and delivery of response (à la HTTP, SMTP, IMAP, SIP, RTP, RTSP, OCSP) including authentication, authorization and auditing (AAA) of all transactions. It’s a hard thing to get right, but our product development team gets it right. Consistently and reliably. We make mistakes sometimes (sorry Bago), but we correct them and make the product better.

I’m the newest member of an R and d team (note: big R, little d) called NTR, which sits behind the firewall that is Product Development, out of production space. In a manner that reminds me of Debian Testing. We try new things. Our current project is to allow users to compare their current (cloud-based or iron-based) IT system with what their system would be like with a BIG-IP in front of it. I can probably come up with a demo if anyone’s interested in checking it out. I’ll go work on that now.

Also of note, the web server now redirects requests for the blog on port 80 over to 443.

# MariaDB repository list – created 2012-07-31 05:17 UTC # http://downloads.mariadb.org/mariadb/repositories/deb http://ftp.osuosl.org/pub/mariadb/repo/5.5/debian squeeze main deb-src http://ftp.osuosl.org/pub/mariadb/repo/5.5/debian squeeze main

Brought to you by the studio that brought you buzz, rex, bo, hamm, slink, potato, woody, sarge, etch, lenny, squeeze and wheezy.

I am currently exercising the new (to us) equipment and hope to winnow the less than awesome equipment over the next quarter. I spent the last six months finding the best in breed of the surplussed DL385 and DL380 chassis we (work) were going to have recycled. The team and I were able to find enough equipment to bring up one of each with eight and six gigs of memory, respectively. These will make excellent hypervisors for provisioning embedded instances of Slackware, Fedora, RHEL, CentOS, Debian, FreeBSD, OpenSolaris, OpenIndiana, FreeDOS, etc.

When I initially configured this xen paravirt environment, I failed to plan for integration with libvirt, so I am now re-jiggering the software bridges so that they are managed using virt-manager. My experience doing this in the Eastsound lab has proved to be quite rewarding. Once network, storage and memory allocation are handled by libvirt, it will be trivial to automate the process of deploying, reclaiming, and managing these Telecommunications Resources efficiently and effectively using Perl.

The new equipment we racked over the last weekend all has hardware assisted virtualization and is capable of hosting operating systems which have not been patched to communicate with the host hypervisor. This provides a higher level of assurance that guests will receive the full amount of provisioned resources and reduces the likelihood of resource conflicts, should the cluster operations team mistakenly over-commit. It also makes it possible for these nodes to host Windows-based operating systems. Oh, and they will also host these not insignificant things called BIG-IP Local Traffic Manager Virtual Edition (VE) and BIG-IP GTM Virtual Edition.

cjac@foxtrot:/usr/src/git/f5/NIST-NVD-Store-SQLite3$ perl Makefile.PL ; make ; make test ; cjac@foxtrot:/usr/src/git/f5/NIST-NVD-Store-SQLite3$ perl -MNIST::NVD::Query -MData::Dumper -e '
$q = NIST::NVD::Query->new(store    => q{SQLite3},database => q{t/data/nvdcve-2.0.db});
$cve_list = $q->cve_for_cpe( cpe => q{cpe:/a:microsoft:ie:7.0.5730.11} );
print Data::Dumper::Dumper { cve_list => $cve_list, first_cvss => $q->cve( cve_id => $cve_list->[0] )->{q{vuln:cvss}} }
'
$VAR1 = {
          'cve_list' => [
                          'CVE-2002-2435',
                          'CVE-2010-5071'
                        ],
          'first_cvss' => {
                            'cvss:base_metrics' => {
                                                   'cvss:confidentiality-impact' => 'PARTIAL',
                                                   'cvss:score' => '4.3',
                                                   'cvss:authentication' => 'NONE',
                                                   'cvss:access-vector' => 'NETWORK',
                                                   'cvss:source' => 'http://nvd.nist.gov',
                                                   'cvss:generated-on-datetime' => '2011-12-08T06:47:00.000-05:00',
                                                   'cvss:availability-impact' => 'NONE',
                                                   'cvss:integrity-impact' => 'NONE',
                                                   'cvss:access-complexity' => 'MEDIUM'
                                                 }
                          }
        };

https://metacpan.org/release/CJCOLLIER/NIST-NVD-Store-SQLite3-1.00.00