Home of the Squeezebox™ & Transporter® network music players.
Page 333 of 334 FirstFirst ... 233283323331332333334 LastLast
Results 3,321 to 3,330 of 3338
  1. #3321
    Senior Member ralphy's Avatar
    Join Date
    Jan 2006
    Location
    Canada
    Posts
    1,887
    Quote Originally Posted by bchab View Post
    Hi,

    I intall squeezebox on olimex A20 lime board.
    I have a problem to map my usb sound card to the output.

    squeezelite -l gives this :

    ALSA lib confmisc.c:1286snd_func_refer) Unable to find definition 'cards.sunxi-CODEC.pcm.front.0:CARD=0'
    ALSA lib conf.c:4259_snd_config_evaluate) function snd_func_refer returned error: No such file or directory
    ALSA lib conf.c:4738snd_config_expand) Evaluate error: No such file or directory
    ALSA lib pcm.c:2239snd_pcm_open_noupdate) Unknown PCM front
    ALSA lib pcm.c:2239snd_pcm_open_noupdate) Unknown PCM cards.pcm.rear
    ...
    ...
    ...
    ALSA lib pcm.c:2239snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem
    ALSA lib pcm.c:2239snd_pcm_open_noupdate) Unknown PCM cards.pcm.modem
    ALSA lib pcm.c:2239snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline
    ALSA lib pcm.c:2239snd_pcm_open_noupdate) Unknown PCM cards.pcm.phoneline
    Cannot connect to server socket err = No such file or directory
    Cannot connect to server request channel
    jack server is not running or cannot be started
    Output devices:
    0 - sunxi-CODEC: PCM (hw:0,0) [ALSA]
    1 - Combo384 Amanero: USB Audio (hw:1,0) [ALSA]
    2 - sysdefault [ALSA]
    3 - dmix [ALSA]
    4 - default [ALSA]

    When i try to map the Amanero card

    root@A20-OLinuXino:/etc# squeezelite -o hw:1,0

    i got the same error ...

    Is there something wrong in my command ?
    The default output of the board is not working but i think this is normal as there is no audio output on this board.

    thank you for your help

    B.
    Looks like you're using a portaudio build of squeezelite which doesn't use the hw: options. You need to use the number before your device with the -o 1 option.

    Check the bottom of the output from the -? option.

    Build options: LINUX ALSA EVENTFD RESAMPLE FFMPEG VISEXPORT LINKALL

    Or

    Build options: LINUX PORTAUDIO EVENTFD RESAMPLE FFMPEG VISEXPORT LINKALL
    Ralphy

    1-Touch, 5-Classics, 3-Booms, 1-UE Radio
    Squeezebox client builds donations always appreciated.

  2. #3322
    Junior Member
    Join Date
    Aug 2014
    Posts
    16

    Squeezelite (or Alsa) stream sample rate info

    I'm trying to build an externally clocked I2S DAC application where the DAC acts as master and the Pi (or BBB, whatever) acts as I2S slave - ie, DAC LRCLK/BCLK ➔ MPU DAI and MPU DAI Data ➔ DAC. In order to select the appropriate external clock (44.1 or 48 multiple), I need the file/stream info (sample rate & bit depth) from the file header or stream meta. Can anyone enlighten me where/how that is queried in squeezelite, and where I can access the info in real time prior to starting the read?
    Last edited by bullitbd; 2017-12-10 at 22:49.

  3. #3323

    -o default

    Quote Originally Posted by Richard Kimber View Post
    Thanks. I'll try that later. I'm currently experimenting with adding -o hw:CARD=HDAudio,DEV=0. I haven't had it going long enough to test this properly.

    - Richard.
    Hi
    I tried this option but while adding a new

    -o in etc/default/sequeezelite, the -o default persists.

    How can I get rid of it?

    I have
    SB_EXTRA_ARGS="-V Speaker -o dmix:CARD=Device,DEV=0 -a :::0 -m 00:00:00:00:00:95 -d all=debug -f /var/log/squeezelite.log"
    thanks

  4. #3324
    Senior Member ralphy's Avatar
    Join Date
    Jan 2006
    Location
    Canada
    Posts
    1,887
    Quote Originally Posted by rlsx View Post
    Sorry -- my mistake.
    I meant to ask about the "new format" squeezelite:
    : Squeezelite-x86_64-1.8.7r1052.dmg
    How does one configure the command-line arguments, such as "output device" ?

    (You will forgive me if this isn't the correct thread, for squeezelite...)

    Thanks
    I use launchctl so squeezelite starts at boot on the mac.

    From a terminal window

    Get the device name to use with the -o option.

    Code:
    $ /Applications/Squeezelite.app/Contents/MacOS/Squeezelite -l
    Output devices:
      0 - Soundflower (64ch) [Core Audio]
      1 - Soundflower (2ch) [Core Audio]
    Test it. Play a track and then press control-c to quit.
    Code:
    $ /Applications/Squeezelite.app/Contents/MacOS/Squeezelite -o "Soundflower (2ch)" -d all=debug
    [07:37:04.541770] stream_init:294 init stream
    [07:37:04.542361] stream_init:295 streambuf size: 2097152
    [07:37:04.542678] output_init_pa:493 init output
    [07:37:04.542705] output_init_pa:513 requested latency: 0
    [07:37:04.648629] output_init_common:347 outputbuf size: 3528000
    [07:37:04.649345] output_init_common:371 idle timeout: 0
    [07:37:04.962476] output_init_common:411 supported rates: 384000 352800 192000 176400 96000 88200 48000 44100 32000 24000 22500 16000 12000 11025 8000 
    [07:37:04.962516] _pa_open:302 opening device in PlayNice mode
    [07:37:04.976796] _pa_open:330 opened device 1 - Soundflower (2ch) at 44100 latency 11 ms
    [07:37:04.977083] decode_init:153 init decode
    ... snip ...
    ^C[07:37:11.845776] slimproto_stop:1004 slimproto stop
    [07:37:11.946470] decode_close:212 close decode
    [07:37:11.980752] stream_close:331 close stream
    [07:37:12.016236] output_close_pa:533 close output
    Copy the included squeezelite.plist to the launchctl folder.

    Code:
    $ sudo cp /Applications/Squeezelite.app/Contents/MacOS/squeezelite.plist /Library/LaunchDaemons/squeezelite.plist
    Add the -o option to /Library/LaunchDaemons/squeezelite.plist

    Code:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
            <key>EnvironmentVariables</key>
            <dict>
                    <key>StandardErrorPath</key>
                    <string>/dev/null</string>
                    <key>StandardOutPath</key>
                    <string>/dev/null</string>
            </dict>
            <key>KeepAlive</key>
            <true/>
            <key>Label</key>
            <string>squeezelite</string>
            <key>OnDemand</key>
            <false/>
            <key>ProgramArguments</key>
            <array>
                    <string>/Applications/Squeezelite.app/Contents/MacOS/Squeezelite</string>
                    <string>-o</string>
                    <string>Soundflower (2ch)</string>
                    <string>-a</string>
                    <string>100</string>
                    <string>-f</string>
                    <string>/var/log/Squeezelite.log</string>
                    <string>-N</string>
                    <string>/var/log/Squeezelite.name</string>
            </array>
            <key>RunAtLoad</key>
            <true/>
    </dict>
    </plist>
    Start squeezelite and enable autostart at boot.

    Code:
    sudo launchctl load -w /Library/LaunchDaemons/squeezelite.plist
    Confirm it started. If not, check the log /var/log/Squeezelite.log

    Code:
    $ ps -fe | grep Squeezelite
        0 17610     1   0  7:57AM ??         0:00.37 /Applications/Squeezelite.app/Contents/MacOS/Squeezelite -o Soundflower (2ch) -a 100 -f /var/log/Squeezelite.log -N /var/log/Squeezelite.name
    To stop squeezelite and disable autostart.

    Code:
    sudo launchctl unload -w /Library/LaunchDaemons/squeezelite.plist
    Ralphy

    1-Touch, 5-Classics, 3-Booms, 1-UE Radio
    Squeezebox client builds donations always appreciated.

  5. #3325
    Senior Member
    Join Date
    Nov 2009
    Location
    DUS
    Posts
    809
    Hi folks.

    Ts been a while.

    I think I brought this issue up some time a back. Don't know if there've been anything done in that area.

    I think I mentioned that I use the buffers of squeezelite as full-track RAM buffers.
    Something like "-b 10000:400000" would allocate a huge 400MB output buffer.
    There's usually plenty of RAM, even on machines like RPI, to store a track into that output buffer.
    The OS itself usually allocates less then 50MB.

    Basically all streaming and DSP work can be done at the beginning of playback - call it "bulk-processing".
    During playback there'd be just minor activities ongoing.
    And that's actually how it works. At 44.1/16 with flacs I experience CPU loads in the range of 0.3-0.7%
    after a few seconds high load in the beginning of a track.
    Without bulk-processing you usually face loads around 2-4% throughout the playback. Factor 5
    I'd consider plausible.

    Now. The issue when starting a playlist is that the end of a track is not recognized properly.
    squeezelite loads more then just a single track if the buffer is larger then the final track size.

    That leads to an odd behavior.

    E.g. the pointer for "next track" will refer to the track after the next track, because the next track is
    already partially processed.

    Do you guys think there'd be a way that squeezelite loads and/or processes just one track at time,
    no matter how big the output buffer and/or the playlist is?

    Or another - a 2nd best option - might be to not shift the "next-track" pointer, before a track is
    actually being played back.

    Can this be handled by squeezelite at all or are we looking at a LMS issue?

    Thx.

  6. #3326
    Senior Member
    Join Date
    Dec 2009
    Location
    Albinea (Bologna Area) Italy
    Posts
    604
    Quote Originally Posted by soundcheck View Post
    Hi folks.

    Ts been a while.

    I think I brought this issue up some time a back. Don't know if there've been anything done in that area.

    I think I mentioned that I use the buffers of squeezelite as full-track RAM buffers.
    Something like "-b 10000:400000" would allocate a huge 400MB output buffer.
    There's usually plenty of RAM, even on machines like RPI, to store a track into that output buffer.
    The OS itself usually allocates less then 50MB.

    Basically all streaming and DSP work can be done at the beginning of playback - call it "bulk-processing".
    During playback there'd be just minor activities ongoing.
    And that's actually how it works. At 44.1/16 with flacs I experience CPU loads in the range of 0.3-0.7%
    after a few seconds high load in the beginning of a track.
    Without bulk-processing you usually face loads around 2-4% throughout the playback. Factor 5
    I'd consider plausible.

    Now. The issue when starting a playlist is that the end of a track is not recognized properly.
    squeezelite loads more then just a single track if the buffer is larger then the final track size.

    That leads to an odd behavior.

    E.g. the pointer for "next track" will refer to the track after the next track, because the next track is
    already partially processed.

    Do you guys think there'd be a way that squeezelite loads and/or processes just one track at time,
    no matter how big the output buffer and/or the playlist is?

    Or another - a 2nd best option - might be to not shift the "next-track" pointer, before a track is
    actually being played back.

    Can this be handled by squeezelite at all or are we looking at a LMS issue?

    Thx.
    Is not a bug, is how is designed to work and is the reason why we don't suffer by gapeless problems, among others. In my opinion it should go over the second track, to avoid problems with shorts ones (see what I've been working on with qobuz plugin) but the "limit"
    come from the SB firmware that could handle only 2 tracks in the buffer, the current and the next.

    BTW the pointer to next track shifts when the player 'streams outs', not when it ends to load current track in iinput buffer.
    __________________________________________________ ______________________
    Author of C-3PO plugin, Squeezelite-R2, Falcon Web interface - See www.marcoc1712.it

  7. #3327
    Senior Member
    Join Date
    Nov 2009
    Location
    DUS
    Posts
    809
    To me it's still a bug. If you call it design, or design flaw or weakness or compromise - that doesn't matter to me.

    If "next" is the not "next" after the track being played back at that very moment, it's IMO a very questionable design.

    Even with gapless "next" should be "next".

    I guess very "short ones" are an exemption. 99.999% are rather normal size tracks.


    If the next-pointer shifts at stream-out to the next-after-next track - it's still a bug to me.


    If you also say that a config option like "gapless yes/no" might be an option to get easily around this.
    Why not trying it?
    Last edited by soundcheck; 2018-03-12 at 08:18.

  8. #3328
    Senior Member
    Join Date
    Nov 2010
    Location
    Hertfordshire, UK
    Posts
    2,701
    Quote Originally Posted by soundcheck View Post
    To me it's still a bug. If you call it design, or design flaw or weakness or compromise - that doesn't matter to me.

    If "next" is the not "next" after the track being played back at that very moment, it's IMO a very questionable design.

    Even with gapless "next" should be "next".

    I guess very "short ones" are an exemption. 99.999% are rather normal size tracks.


    If the next-pointer shifts at stream-out to the next-after-next track - it's still a bug to me.


    If you also say that a config option like "gapless yes/no" might be an option to get easily around this.
    Why not trying it?
    Playing 16/44 and 24/96 (stereo) flacs of a few minutes each it all works normally for me, gapless and playing the next track correctly with options as below. Maybe there's a specific combination of track lengths that gives problems?
    Code:
    hw:CARD=DAC,DEV=0 -a 60 -p 2 -r 192000-192000 -n VBslite -u vLX -m 00:00:00:00:00:99 -s localhost:3483 -b 10000:400000
    LMS 7.9.1 on VortexBox Midi box, Xubuntu 17.10, FLACs 16->24 bit, 44.1->192kbps. Touch & EDO. 2nd Touch standard.
    LMS plugin UPnP/DLNA Bridge to MF M1 CLiC (to A308CR amp & ESLs) & Marantz CR603 UPnP renderers.
    Alternatively Minimserver & Upplay to same & to upmpdcli/mpd PC renderers.
    Squeezelite to Meridian USB Explorer DAC to PC speakers/headphones.
    Wireless Xubuntu 17.10 laptop firefox/upplay or Android 'phone with Squeeze-Commander/BubbleUPnP controls LMS/Minimserver.

  9. #3329
    Senior Member
    Join Date
    Nov 2009
    Location
    DUS
    Posts
    809
    Try adding another song to the current playlist - with e.g. "play next".

  10. #3330
    Senior Member Mnyb's Avatar
    Join Date
    Feb 2006
    Location
    Vństerňs Sweden
    Posts
    16,339
    Well don't forget crossfade if you design something
    --------------------------------------------------------------------
    Main hifi: Touch + CIA PS +MeridianG68J MeridianHD621 MeridianG98DH 2 x MeridianDSP5200 MeridianDSP5200HC 2 xMeridianDSP3100 +Rel Stadium 3 sub.
    Bedroom/Office: Boom
    Kitchen: Touch + powered Fostex PM0.4
    Misc use: Radio (with battery)
    iPad1 with iPengHD & SqueezePad
    (spares Touch, SB3, reciever ,controller )
    server HP proliant micro server N36L with ClearOS Linux

    http://people.xiph.org/~xiphmont/demo/neil-young.html

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •