-
Notifications
You must be signed in to change notification settings - Fork 456
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Only getting noise output #17
Comments
Hi, |
Hi,
|
Hi, |
@maosuyun2009 this is a different thing as the initial ticket was created for. You are mixing up PCM, a digital representation of audio, with WAV as a file format. It also would be very inefficient to have uncompressed audio in a WAV file, so currently a lot of them are compressed. And PCM is not compressed audio data! Even if you have PCM in the WAV, you still have a header and this might cause horrible noise. In short PCM != WAV! |
@Lakritzator Thanks, In oss architechture, i always cat wav file to /dev/oss, so I just think i can do it like oss |
@maosuyun2009 actually for "normal" (containing PCM data) WAV-files cat will work. A requirement for the cat method is that the wave header size is a multiple of 4 (usually it's 44 bytes). Otherwise left/right and upper/lower bytes are mixed up and cause noisy audio. |
Found a solution. Working on Ubuntu 15.10 (Wili Werewolf), mopidy 2.0.0-1 (jessie), snapcast (git-master) with standard gst-launch-1.0 From my edit: changed the output string, it didn't play well between 48KHz and 44.1KHz input. |
added this to the Readme.md (3a4bfbd) |
client and server are connected, tested with /dev/urandom.
mopidy config is writing to /tmp/snapfifo, but only delivering noise.
starting and stopping the server audio in mopidy does start/stop noise at client end.
local client (on same server as mopidy) also produces the same issue.
[running on Pi2 server and PiB on client]
The text was updated successfully, but these errors were encountered: