4 ms·

Awesome news :) For the mp3 demo, what is the song encoded at? Also, is there a way to listen to the same tracks encoded with the various encoders to compare?

Awesome news :) For the mp3 demo, what is the song encoded at? Also, is there a way to listen to the same tracks encoded with the various encoders to compare? I come up with my own encoder / decoder a few years ago and ran a MUSHRA test against various other popular codecs; I wish I had this tool back then!

jensnockert 14y ago
It is 128kbit in the MP3 demo, I think I used LAME to encode it, but I am not sure, could have been the one in OS X. It plays 320kbit files fine though.
- StavrosK 14y ago
  It sounds really bad in Chrome on Ubuntu 12.04. Choppy, I don't think the speed is right, etc. I didn't see a link to the original, though, so it might be just really crappy music.
  - drivebyacct2 14y ago
    Chrome and Ubuntu have been having both HTML5/Flash audio since early this year unfortunately. It's rare that I have any audio played correctly via Chrome regardless of the source, it sounds corrupt and plays at the wrong speed most of the time. Suspicions are PulseAudio. You can try killing it and reloading the page and trying again (you may also need to restart Chrome).
    - timb 14y ago
      try adding tsched=0 to one of the lines in /etc/pulse/default.pa so it becomes load-module module-udev-detect tsched=0 this fixed my chrome ubuntu audio problems. (source: links at bottom of http://code.google.com/p/chromium/issues/detail?id=110375 http://code.google.com/p/chromium/issues/detail?id=110375 )
  - jensnockert 14y ago
    http://labs.official.fm/media/vibe@44100.flac http://labs.official.fm/media/vibe@44100.flac, but it shouldn't sound 'choppy'. We have had some problems on Linux where Chrome(ium) for some reason reports the wrong sample-rate, but that usually just changes the playback speed. Does it use high amounts of CPU too?
    - StavrosK 14y ago
      Yep, that sounds normal. It uses about 12% CPU for Pulse and 12% for Chrome (this is a Core 2 Quad).
      - jensnockert 14y ago
        Could you please add an issue with some more precise information about your browser(s)/sound server at https://github.com/ofmlabs/aurora.js/issues https://github.com/ofmlabs/aurora.js/issues ?

jensnockert 14y ago

It is 128kbit in the MP3 demo, I think I used LAME to encode it, but I am not sure, could have been the one in OS X. It plays 320kbit files fine though.

StavrosK 14y ago
It sounds really bad in Chrome on Ubuntu 12.04. Choppy, I don't think the speed is right, etc. I didn't see a link to the original, though, so it might be just really crappy music.
- drivebyacct2 14y ago
  Chrome and Ubuntu have been having both HTML5/Flash audio since early this year unfortunately. It's rare that I have any audio played correctly via Chrome regardless of the source, it sounds corrupt and plays at the wrong speed most of the time. Suspicions are PulseAudio. You can try killing it and reloading the page and trying again (you may also need to restart Chrome).
  - timb 14y ago
    try adding tsched=0 to one of the lines in /etc/pulse/default.pa so it becomes load-module module-udev-detect tsched=0 this fixed my chrome ubuntu audio problems. (source: links at bottom of http://code.google.com/p/chromium/issues/detail?id=110375 http://code.google.com/p/chromium/issues/detail?id=110375 )
- jensnockert 14y ago
  http://labs.official.fm/media/vibe@44100.flac http://labs.official.fm/media/vibe@44100.flac, but it shouldn't sound 'choppy'. We have had some problems on Linux where Chrome(ium) for some reason reports the wrong sample-rate, but that usually just changes the playback speed. Does it use high amounts of CPU too?
  - StavrosK 14y ago
    Yep, that sounds normal. It uses about 12% CPU for Pulse and 12% for Chrome (this is a Core 2 Quad).
    - jensnockert 14y ago
      Could you please add an issue with some more precise information about your browser(s)/sound server at https://github.com/ofmlabs/aurora.js/issues https://github.com/ofmlabs/aurora.js/issues ?