Bug 8836 – audio problems when syncing rhapsody - cracks, pops, and squeaks

Bug 8836 - audio problems when syncing rhapsody - cracks, pops, and squeaks

Summary:

audio problems when syncing rhapsody - cracks, pops, and squeaks

Status:	RESOLVED DUPLICATE of bug 9003

Product:	Logitech Media Server
Classification:	Unclassified
Component:	Rhapsody Direct
Version:	unspecified
Platform:	PC Windows XP

Importance:	-- normal (vote)
Target Milestone:	Investigating
Assigned To:	Squeezebox QA Team email alias

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2008-07-22 12:46 UTC by Michael Valera
Modified:	2008-11-18 11:35 UTC (History)
CC List:	1 user (show)

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Michael Valera 2008-07-22 12:46:40 UTC

Was syncing Rhapsody to 3 rooms this Saturday on the latest boom 7.2 new streaming via SVN.

I ran into major problems. It ran fine for a few songs, and then at the beginning of new songs would play only on one Squeezebox, and nothing but cracks, pops, and squeaks out of the other two.

Skipping tracks back or forward would fix the problem for one song only, and then the cracks/pops/squeaks would return for at the beginning of the next song.

Mike

Comment 1 Michael Valera 2008-07-23 09:26:25 UTC

This happened again last night.

Updated 7/20 via SVN.

Mike

Comment 2 James Richardson 2008-10-20 08:40:43 UTC

Michael: can you still reproduce this with the 7.3?

Comment 3 James Richardson 2008-10-24 23:30:32 UTC

This appears to be addressed, please reopen if you feel differently

Comment 4 Michael Valera 2008-11-14 14:29:04 UTC

Just happened again today.

7.3 - 23612

Tranporter FW 66

Pops and squeaks when going from one song to the next. You have to skip fwd or back to load another song for it to go away.

Happens only once in a long while.

Mike

Comment 5 Andy Grundman 2008-11-18 11:35:01 UTC

Pretty sure this is the same bug as 9003.

*** This bug has been marked as a duplicate of bug 9003 ***