LLTI Archives

May 2016, Week 1

LLTI@LISTSERV.DARTMOUTH.EDU

Options: Use Monospaced Font
Show HTML Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"Lynch, John" <[log in to unmask]>
Reply To:
Language Learning and Technology International Information Forum <[log in to unmask]>
Date:
Wed, 4 May 2016 23:12:03 +0000
Content-Type:
multipart/alternative
Parts/Attachments:
text/plain (919 bytes) , text/html (2854 bytes)
I’m working with a faculty member on a website/web application supporting undergraduate linguistics classes. The PHP code behind the application is over 10 years old, with various patches over the years, and the audio files were originally stored as .aiff, and delivered via Quicktime streaming. Unfortunately, now that Quicktime is fading from popularity, this professor is worried that her application will become inaccessible to students if she doesn’t update it.



I’m curious, what format and delivery protocol are people using for audio files, when they want to minimize long-term maintenance of the resources? Obviously, she could just do a direct download of .wav files; but I’m wondering if there’s something else out there that I’m not thinking of.



Sincerely,



John A. Lynch, Ph.D. | Academic Technology Manager

UCLA CENTER FOR DIGITAL HUMANITIES

[log in to unmask]

(310) 206-5630




ATOM RSS1 RSS2