Thank you for being a valued part of the CNET community. As of December 1, 2020, the forums are in read-only format. In early 2021, CNET Forums will no longer be available. We are grateful for the participation and advice you have provided to one another over the years.

Thanks,

CNET Support

General discussion

echo?

Feb 13, 2006 9:02AM PST

Is it just me, or did monday's podcast have an echo? I was listening to it through my headphones, and for the first time, I noticed an odd echo in the sound. This didnt happen when I listened to the others again. Did anyone else notice this, or is it my headphones.

Discussion is locked

- Collapse -
I didn't notice anything
Feb 13, 2006 9:12AM PST

But I do think the file was at a lower bitrate than normal. Trying to find an echo, I could only hear slight , uh, "fuzzies" (not sure of what real term to use), but only because I was looking for something.

- Collapse -
It was Molly's empty chair
Feb 13, 2006 9:20AM PST

Just leaves a wide open space for echo.

Or it could be the lower bitrate Veronica tried. She can explain more but before anyone says it, yes we're using LAME.

- Collapse -
echo
Feb 13, 2006 9:24AM PST

I noticed the same thing when i was listening to it through the headphones on my computer.

- Collapse -
definietly headphones
Feb 13, 2006 9:39AM PST

When i listened again, i noticed that if I only had on one ear on my headphones it was fine, but with both the sync was a little off, so it wasn't really an echo, but sounded like one. I don't know how that works exactly, but one side was going faster than the other.

- Collapse -
At the beginning
Feb 13, 2006 9:56AM PST

That's mostly where I noticed it and then it wasn't so bad after that.

-Kevin

- Collapse -
HAH!

I knew it. Yes, I encoded it with LAME at 96kbps this time, and you still noticed the difference!

That's it, I'm sticking to what I always do.
V

- Collapse -
(NT) (NT) Rather sacrifice a bit of quality for smaller file siz
Feb 13, 2006 8:19PM PST