|
ECS-L Home Automation and Security Archives |
learn more
| view messages for this
month | NetBloc® | terms of use | search
subject (prev) or (next) |
time (prev) or (next) |
author (prev) or (next) |
view more subjects
Subject: From: Date: | Beware of read-only WAV's David Kindred Thu, 24 Feb 2000 23:14:38 -0500 |
Hey, guys.
Just tracked down a crazy problem I was having. Thought I'd share the result
with you in case you should encounter it.
Here's the gist of it: Don't use read-only WAV files with ECS.
Before a WAV file is played, a copy of the file is made in the ECS directory
with a file name of SQWV0.WAV. If two are queued up to play at the same
time, the first is SQWV0.WAV and the next is SQWV1.WAV. You get the picture.
Anyway, one of my WAV's was from a Windows theme that I copied from
elsewhere on my drive, and I never bothered to check the file attribute.
When it needed to be played, it was copied as SQWV0.WAV and played, but
because of the read-only attribute, it was not immediately nuked afterwards,
as was normally done. The next time a WAV was attempted to be played, ECS
reported an 'Access Denied' error as it tried to create a new SQWV0.WAV
file. At first, I thought it was a multimedia error, but I found that other
programs could still play files. Finally the lightbulb went on.
Thought you guys might want to check your WAV's to make sure they're
"clean".
--Davey-san
subject (prev) or (next) |
time (prev) or (next) |
author (prev) or (next) |
view more subjects