Bug 3856 – Harsh noise in transition between 48kHz and 44.1kHz Ogg Vorbis files

Bug 3856 - Harsh noise in transition between 48kHz and 44.1kHz Ogg Vorbis files

Summary:

Harsh noise in transition between 48kHz and 44.1kHz Ogg Vorbis files

Status:	RESOLVED INVALID

Product:	SB 2/3
Classification:	Unclassified
Component:	Audio
Version:	55
Platform:	PC Windows (legacy)

Importance:	P2 normal (vote)
Target Milestone:	---
Assigned To:	Blackketter Dean

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2006-08-01 12:06 UTC by Steve Tregidgo
Modified:	2006-08-18 11:37 UTC (History)
CC List:	0 users

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 Steve Tregidgo 2006-08-01 12:06:05 UTC

Playing two Ogg Vorbis files (through the random songs mix feature; haven't yet tried with a normal playlist) sometimes results in a harsh, garbled noise between the two tracks.  I've only heard this when a 48kHz Ogg Vorbis file is followed by a 44.1kHz file.  The "File Types" section of my server settings indicates that Ogg may be converted to FLAC or AIFF; I haven't tried adjusting this.

I've tried playing one pair of files directly through foobar2000 (having just checked my SB2's playlist to see which files last showed the problem), and the noise does not exist in the files.  I don't have cross-fading or replaygain enabled.  I use the digital outputs, with the volume permanently set to maximum and with no bitrate limiting.

Are there any particular debug flags I should turn on to help get to the bottom of this?

Comment 1 Steve Tregidgo 2006-08-09 10:55:45 UTC

Update: one of the 48kHz files just came up through foobar2000, and I heard the same noise this time.  So I now doubt the accuracy of my original report!  This may well be a problem with the Ogg Vorbis file itself, after all.  Apologies.

Comment 2 Chris Owens 2006-08-18 11:37:11 UTC

If you think this is a Squeezbox error, please post a couple of problems files and reopen the bug.