1. Home
  2. Projects
  3. Squeezebox Player
We have upgraded the community system as part of the upgrade a password reset is required for all users before login in.

Squeezebox Player

  • B

    @Sawyer-McBride Do you have an ethernet expansion? You will need that to reflash the firmware.

    0 S 1 Reply
  • S

    @Boken-Lin I have, although I've only got a mini-dock at the moment so will have to patch it on a breadboard. Have you any pinouts and/or a link to the re-flash guide, I did see another guy had to go through the process

    0
  • T

    Hi,

    I'm very interested in doing quite the same thing.
    Did you have any success with running squeezeslave on the omega?

    Thanks

    0
  • R

    I am very interested in this as I intend to use the Omega and the "C-Media Electronics Inc." dongle as a wi-fi intercom for use in a community theatre for communication among the crew.

    0 S 1 Reply
  • Daniel Wright

    @Sawyer-McBride,
    I would be very interested in this. I have been working with the Raspberry Pi to create remote speakers for church, but this could make a cheaper solution if it works.
    Thanks for your hard work.

    0
  • F

    I've been poking at USB audio as well. It seems to be supported under OpenWRT via the 'kmod-usb-audio' package. Unfortunately, that one hasn't been built for the Omega yet. Hopefully it will be part of the larger batch of packages coming over in the future! šŸ™‚

    0 S 1 Reply
  • R

    Thanks, fader. I didn't realize it hadn't been built yet. It is listed in:

    opkg list | grep audio | grep usb

    Of course,
    opkg list | grep usb
    leaves a lot of experimenting yet to be done! Sadly, "opkg install sox" on most of these (sox here used as example) gives:

    • satisfy_dependencies_for: Cannot satisfy the following dependencies for sox:
    • kernel (= 3.18.20-1-7bed08fa9c06eb8089e82c200340ec66) *
    • opkg_install_cmd: Cannot install package sox.

    On the other hand, usbreset does seem to work so there is a connection to the 3D dongle.

    0
  • K

    @Ross-Pratt The error you are getting on "Cannot satisfy dependency" indicates the package expects a different (newer) kernel version than the one installed.
    Unless the package really needs a feature that is in the newer kernel, it is usually OK to still install the package.
    This can be done using:

    • opkg --force-depends install <package-name>

    The worst that can happen is that the installed package really doesn't work with the older kernel, in which case you can remove it using:

    • opkg remove <package-name>>

    And other than not having the package you want, you are no worse off.

    FYI: I have done this with a few packages that initially indicate problem with kernel version dependency and have had no problems.

    0
  • F

    It's certainly something you could try but it's basically a guarantee that a kernel module of version X will not load in a kernel of version Y (or even X.0.1 :)). You can get away with ignoring those dependencies for userspace packages on occasion if they just need a feature provided by a given kernelversion which also happens to be present in the version you have installed (though you're still asking for trouble, as the feature may behave in different ways). But a kernel module has to be mapped into kernel memory, executed in Ring 0, etc. so there are both a lot more things that can go wrong and a lot more checks for specific versions before code gets to be loaded.

    I'm hoping we get all the kmod-* packages over soon, as that will dramatically increase the amount of hardware we can play with!

    0
  • K

    I would basically agree with the comments by @fader
    If you use a package that was intended for a different kernel release (even if it was for the same hardware) you do run a risk that it won't work - particularly if the package is for a kernel module.
    There is a greater likelihood that a user mode package will work.

    However, in my opinion you are highly unlikely to cause any damage by using a package with mismatching kernel version - and some times it is the only way to progress while waiting on getting the right version.

    But bottom line is that it is up to the call of each individual to decide whether it is worth it or not and to have a recovery plan if it doesn't work (usually just a removal of offending package, sometimes a factory reset) - but a lot of this is all part of the experimentation/development process.

    1
  • R

    Thank you Kit and Fader! Oddly it was actually looking for an older version! I am on 3.18.23.
    --force-depends install works a treat. I'm now filling my 8 gig stick with software that will probably turn out useless but I can't tell otherwise what will work.
    I sure wish gforth was available.

    0
  • S

    @Ross-Pratt I am planning on using the same audio card I believe, a small white one? about Ā£2.50 on ebay? I think it would be a very do-able project that would work well as long as we can get it to recognise the card!

    0
  • S

    @fader I did see that the Omega kernel doesnt have the feature enabled for kmod-usb-audio and also another audio related feature. I did try to custom build the kernel but bricked my omega, havn't had time to try again since doing a firmware recovery. It is defo still on my to-do list. @Boken-Lin did say in another thread that they might do a few different releases with differing kernels. If they do, hopefully they'll do one with the USB audio stuff! Until then next time I have some free time I'll try and custom build a firmware again! It's just a pain for me as to do a firmware recovery I have to jam wires into the minidock as my proper dock hasnt turned up yet (Battery dock has been delayed).

    0
  • Igor Neuhold

    i'm planning to cross-compile kmod-usb-audio, it's just taking forever for initial build to finish, i have no idea how many hours have already passed. Hopefully I'll be able to compile it in next few hours.
    I've tried with ignore-depends and even some other kmods from other repos but nothing works

    0
  • R

    @Sawyer-McBride Mine is blue, has "3D SOUND" printed on it and was cheap, probably from DealExtreme or Banggood, probably less than Ā£2.50 .
    My kmod-usb-audio installed:
    root@Omega-1CD5:~# opkg list-installed|grep audio
    kmod-usb-audio - 3.18.20-1
    libaudiofile - 0.3.6-3
    but then, I am on 3.18.23. Be aware that upgrade took /overlay away from my USB-stick and I had to modify fstab again.
    Still haven't connected to sound yet.

    0
  • T

    Finally I have squeezeslave running with usb audio...

    Here you can find my compiled kmod-sound-core_3.18.23-1_ar71xx.ipk and kmod-usb-audio_3.18.23-1_ar71xx.ipk.

    Please check before, that there are no other versions installed with these commands:
    opkg remove kmod-usb-audio
    opkg remove kmod-sound-core

    After that, install both packages with:
    opkg --force-depends install kmod-sound-core
    opkg --force-depends install kmod-usb-audio

    Have fun and enjoy šŸ˜‰

    1
  • T

    I've also added package for squeezelite in my dropbox share...
    Squeezelite is not so power consuming like squeezeslave.
    Just download it and install with
    opkg install squeezelite_1.8-1_ar71xx.ipk

    Great little device šŸ˜‰

    0 S 1 Reply
  • S

    @Thomas-Mueller Any chance I can get those files from you?

    0
  • T

    @Sawyer-McBride

    which files do you need? For getting usb audio to work, or squeezelite, or squeezeslave?

    But in general you should be able to find it here: https://www.dropbox.com/sh/g12gf4ko9512pec/AACDj55QPvxf46LM1V5AwpHoa?dl=0

    For usb audio devices @fader also wrote a great howto.

    0
audio 30 project 26 music streamer 2 squeezebox 1
Log in to reply
 

Looks like your connection to Community was lost, please wait while we try to reconnect.