Home of the Squeezebox™ & Transporter® network music players.
Page 70 of 71 FirstFirst ... 206068697071 LastLast
Results 691 to 700 of 701
  1. #691
    I'm trying to use Squeezelite on Windows 10 with the Jriver WDM driver. Here is a list of devices on my system:

    Output devices:
    3 - - Output [MME]
    4 - JRiver Media Center 25 (JRiver [MME]
    5 - Speakers (ODAC-revB USB DAC) [MME]
    6 - Speakers (Steam Streaming Micro [MME]
    7 - Speakers (Steam Streaming Speak [MME]
    11 - Primary Sound Driver [Windows DirectSound]
    12 - JRiver Media Center 25 (JRiver Media Center 25) [Windows DirectSound]
    13 - Speakers (ODAC-revB USB DAC) [Windows DirectSound]
    14 - Speakers (Steam Streaming Microphone) [Windows DirectSound]
    15 - Speakers (Steam Streaming Speakers) [Windows DirectSound]
    16 - Realtek ASIO [ASIO]
    17 - JRiver Media Center 25 (JRiver Media Center 25) [Windows WASAPI]
    18 - Speakers (ODAC-revB USB DAC) [Windows WASAPI]
    19 - Speakers (Steam Streaming Microphone) [Windows WASAPI]
    20 - Speakers (Steam Streaming Speakers) [Windows WASAPI]
    23 - Output () [Windows WDM-KS]
    25 - Speakers (Steam Streaming Microphone Wave) [Windows WDM-KS]
    28 - Speakers (Steam Streaming Speakers Wave) [Windows WDM-KS]
    29 - Speakers (ODAC-revB USB DAC) [Windows WDM-KS]
    30 - Output (JRVAD Wave) [Windows WDM-KS]

    If I try to use kernel streaming, squeezelite fails to run with the following:

    PS D:\Downloads\squeezelite-1.9.6-1210-win32> .\squeezelite-ffmpeg.exe -s kraken -o 30 -C 60
    [18:52:57.052] test_open:237 error opening portaudio stream: Sample format not supported
    [18:52:57.052] output_init_common:391 unable to open output device: 30

    I'm able to access the WASAPI driver in normal mode, but exclusive mode outputs the following:

    PS D:\Downloads\squeezelite-1.9.6-1210-win32> .\squeezelite-win.exe -s kraken -C 60 -a 50:1 -o 17
    [19:11:36.651] _pa_open:395 error opening device 17 - JRiver Media Center 25 (JRiver Media Center 25) [Windows WASAPI] : Invalid device
    [19:11:36.729] _pa_open:395 error opening device 17 - JRiver Media Center 25 (JRiver Media Center 25) [Windows WASAPI] : Invalid device
    [19:11:36.791] _pa_open:395 error opening device 17 - JRiver Media Center 25 (JRiver Media Center 25) [Windows WASAPI] : Invalid device
    [19:11:36.852] _pa_open:395 error opening device 17 - JRiver Media Center 25 (JRiver Media Center 25) [Windows WASAPI] : Invalid device
    [19:11:36.914] _pa_open:395 error opening device 17 - JRiver Media Center 25 (JRiver Media Center 25) [Windows WASAPI] : Invalid device
    [19:11:36.975] _pa_open:395 error opening device 17 - JRiver Media Center 25 (JRiver Media Center 25) [Windows WASAPI] : Invalid device
    [19:11:37.035] _pa_open:395 error opening device 17 - JRiver Media Center 25 (JRiver Media Center 25) [Windows WASAPI] : Invalid device

    I have no problem accessing the device in WASAPI exclusive mode from Foobar2000.

  2. #692
    Senior Member ralphy's Avatar
    Join Date
    Jan 2006
    Location
    Canada
    Posts
    2,502
    Quote Originally Posted by Theriverlethe View Post
    PS D:\Downloads\squeezelite-1.9.6-1210-win32> .\squeezelite-ffmpeg.exe -s kraken -o 30 -C 60
    [18:52:57.052] test_open:237 error opening portaudio stream: Sample format not supported
    [18:52:57.052] output_init_common:391 unable to open output device: 30
    Squeezelite tries to open the device using 32bit samples and the device/driver responds that the Sample format is not supported so the tests fail.

    Add -d all=debug to the command line it might give more insight.

    If not, you will need a squeezelite build that has debug logging enabled in the portaudio library to help track down what PA doesn't like about the device.

    Quote Originally Posted by Theriverlethe View Post
    I'm able to access the WASAPI driver in normal mode, but exclusive mode outputs the following:

    PS D:\Downloads\squeezelite-1.9.6-1210-win32> .\squeezelite-win.exe -s kraken -C 60 -a 50:1 -o 17
    [19:11:36.651] _pa_open:395 error opening device 17 - JRiver Media Center 25 (JRiver Media Center 25) [Windows WASAPI] : Invalid device
    [19:11:36.729] _pa_open:395 error opening device 17 - JRiver Media Center 25 (JRiver Media Center 25) [Windows WASAPI] : Invalid device
    [19:11:36.791] _pa_open:395 error opening device 17 - JRiver Media Center 25 (JRiver Media Center 25) [Windows WASAPI] : Invalid device
    [19:11:36.852] _pa_open:395 error opening device 17 - JRiver Media Center 25 (JRiver Media Center 25) [Windows WASAPI] : Invalid device
    [19:11:36.914] _pa_open:395 error opening device 17 - JRiver Media Center 25 (JRiver Media Center 25) [Windows WASAPI] : Invalid device
    [19:11:36.975] _pa_open:395 error opening device 17 - JRiver Media Center 25 (JRiver Media Center 25) [Windows WASAPI] : Invalid device
    [19:11:37.035] _pa_open:395 error opening device 17 - JRiver Media Center 25 (JRiver Media Center 25) [Windows WASAPI] : Invalid device

    I have no problem accessing the device in WASAPI exclusive mode from Foobar2000.
    If you haven't already, set the default format for the device to 16bit, 44100Hz in the advanced sound settings. Also add -d all=debug to the command line when testing.
    Ralphy

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

  3. #693
    Quote Originally Posted by ralphy View Post
    Squeezelite tries to open the device using 32bit samples and the device/driver responds that the Sample format is not supported so the tests fail.

    Add -d all=debug to the command line it might give more insight.

    If not, you will need a squeezelite build that has debug logging enabled in the portaudio library to help track down what PA doesn't like about the device.



    If you haven't already, set the default format for the device to 16bit, 44100Hz in the advanced sound settings. Also add -d all=debug to the command line when testing.
    Setting the WASAPI driver to 16/44100Hz as you suggest allows squeezelite to output successfully, but all audio is stuck at 16-bits. It's possible that the driver isn't correctly reporting its capabilities through whatever mechanism portaudio is probing. Foobar2000's WASAPI plugin has no problem outputting 24-bits but not 32-bits.

    Using the WDM-KS driver, I get this:

    PS D:\Downloads\squeezelite-1.9.6-1210-win32> .\squeezelite-ffmpeg.exe -s kraken -o 30 -d all=debug
    [14:45:02.416] stream_init:370 init stream
    [14:45:02.416] stream_init:371 streambuf size: 2097152
    [14:45:02.461] output_init_pa:573 init output
    [14:45:02.461] output_init_pa:593 requested latency: 0
    [14:45:02.571] output_init_common:350 outputbuf size: 3528000
    [14:45:02.571] output_init_common:374 idle timeout: 0
    [14:45:02.572] test_open:237 error opening portaudio stream: Sample format not supported
    [14:45:02.572] output_init_common:391 unable to open output device: 30
    Last edited by Theriverlethe; 2020-05-30 at 12:14.

  4. #694
    When I specify sample rates, I get the following in a loop:

    PS D:\Downloads\squeezelite-1.9.6-1210-win32> .\squeezelite-ffmpeg.exe -s kraken -o 30 -d all=debug -r 44100-96000
    [15:09:14.611] stream_init:370 init stream
    [15:09:14.611] stream_init:371 streambuf size: 2097152
    [15:09:14.657] output_init_pa:573 init output
    [15:09:14.658] output_init_pa:593 requested latency: 0
    [15:09:14.768] output_init_common:350 outputbuf size: 3528000
    [15:09:14.768] output_init_common:374 idle timeout: 0
    [15:09:14.776] output_init_common:422 supported rates: 96000 88200 48000 44100
    [15:09:14.777] _pa_open:395 error opening device 30 - Output (JRVAD Wave) [Windows WDM-KS] : Invalid device
    [15:09:14.777] decode_init:154 init decode
    [15:09:14.777] pa_monitor:275 start monitor thread
    [15:09:14.777] pa_monitor:289 probing device 30
    [15:09:14.777] register_dsd:908 using dsd to decode dsf,dff
    [15:09:14.777] register_ff:795 using ffmpeg to decode alc
    [15:09:14.777] register_ff:779 using ffmpeg to decode wma,wmap
    [15:09:14.777] register_faad:641 using faad to decode aac
    [15:09:14.778] register_vorbis:377 using vorbis to decode ogg
    [15:09:14.778] register_opus:320 using opus to decode ops
    [15:09:14.778] register_flac:314 using flac to decode ogf,flc
    [15:09:14.778] register_pcm:433 using pcm to decode aif,pcm
    [15:09:14.778] register_mad:414 using mad to decode mp3
    [15:09:14.778] decode_init:195 include codecs: exclude codecs:
    [15:09:14.835] pa_monitor:294 device reopen
    [15:09:14.835] pa_monitor:304 end monitor thread
    [15:09:14.836] _pa_open:395 error opening device 30 - Output (JRVAD Wave) [Windows WDM-KS] : Invalid device
    [15:09:14.836] slimproto:887 connecting to 192.168.6.142:3483
    [15:09:14.836] pa_monitor:275 start monitor thread
    [15:09:14.836] pa_monitor:289 probing device 30
    [15:09:14.837] slimproto:926 connected
    [15:09:14.837] sendHELO:142 mac: 2c:4d:54:f1:27:85
    [15:09:14.837] sendHELO:144 cap: CanHTTPS=1,Model=squeezelite,AccuratePlayPoints=1, HasDigitalOut=1,HasPolarityInversion=1,Firmware=v1 .9.6-1210,ModelName=SqueezeLite,MaxSampleRate=96000,dsf ,dff,alc,wma,wmap,aac,ogg,ops,ogf,flc,aif,pcm,mp3
    [15:09:14.893] pa_monitor:294 device reopen
    [15:09:14.893] pa_monitor:304 end monitor thread
    [15:09:14.894] _pa_open:395 error opening device 30 - Output (JRVAD Wave) [Windows WDM-KS] : Invalid device

  5. #695
    Senior Member ralphy's Avatar
    Join Date
    Jan 2006
    Location
    Canada
    Posts
    2,502
    The squeezelite 1.9.7-1250 zip for windows has a 2nd binary squeezelite-debug.exe which has logging enabled for portaudio.

    Run your tests again from a command prompt, not powershell, using the command lines below which redirect the output to a file, zip the 2 log files and attach the zip to your post. They will be large, so please don't copy/paste it's too hard to review.

    Code:
    squeezelite-debug.exe -s kraken -C 60 -a 50:1 -o 17 -d all=debug 2> test1log.txt
    
    squeezelite-debug.exe -s kraken -o 30 -C 60 -d all=debug 2> test2log.txt
    Hopefully that will help us see where portaudio is failing.
    Ralphy

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

  6. #696
    Quote Originally Posted by ralphy View Post
    The squeezelite 1.9.7-1250 zip for windows has a 2nd binary squeezelite-debug.exe which has logging enabled for portaudio.

    Run your tests again from a command prompt, not powershell, using the command lines below which redirect the output to a file, zip the 2 log files and attach the zip to your post. They will be large, so please don't copy/paste it's too hard to review.

    Code:
    squeezelite-debug.exe -s kraken -C 60 -a 50:1 -o 17 -d all=debug 2> test1log.txt
    
    squeezelite-debug.exe -s kraken -o 30 -C 60 -d all=debug 2> test2log.txt
    Hopefully that will help us see where portaudio is failing.
    Thanks. Device enumeration changed since last time:

    Output devices:
    3 - - Output [MME]
    4 - JRiver Media Center 25 (JRiver [MME]
    5 - DENON-AVR (NVIDIA High Definiti [MME]
    6 - Speakers (ODAC-revB USB DAC) [MME]
    7 - U3277WB (NVIDIA High Definition [MME]
    8 - Speakers (Steam Streaming Micro [MME]
    9 - Speakers (Steam Streaming Speak [MME]
    13 - Primary Sound Driver [Windows DirectSound]
    14 - JRiver Media Center 25 (JRiver Media Center 25) [Windows DirectSound]
    15 - DENON-AVR (NVIDIA High Definition Audio) [Windows DirectSound]
    16 - Speakers (ODAC-revB USB DAC) [Windows DirectSound]
    17 - U3277WB (NVIDIA High Definition Audio) [Windows DirectSound]
    18 - Speakers (Steam Streaming Microphone) [Windows DirectSound]
    19 - Speakers (Steam Streaming Speakers) [Windows DirectSound]
    20 - Realtek ASIO [ASIO]
    21 - JRiver Media Center 25 (JRiver Media Center 25) [Windows WASAPI]
    22 - DENON-AVR (NVIDIA High Definition Audio) [Windows WASAPI]
    23 - Speakers (ODAC-revB USB DAC) [Windows WASAPI]
    24 - U3277WB (NVIDIA High Definition Audio) [Windows WASAPI]
    25 - Speakers (Steam Streaming Microphone) [Windows WASAPI]
    26 - Speakers (Steam Streaming Speakers) [Windows WASAPI]
    29 - Output (NVIDIA High Definition Audio) [Windows WDM-KS]
    30 - Output () [Windows WDM-KS]
    32 - Speakers (Steam Streaming Microphone Wave) [Windows WDM-KS]
    35 - Speakers (Steam Streaming Speakers Wave) [Windows WDM-KS]
    36 - Speakers (ODAC-revB USB DAC) [Windows WDM-KS]
    37 - Output (JRVAD Wave) [Windows WDM-KS]
    Attached Files Attached Files

  7. #697
    I've also noticed that this build doesn't output any audio, even in DirectSound mode. Is that intentional?

  8. #698
    Further experimentation with the previous build yielded some REALLY unexpected results. Running "squeezelite-win.exe -o 21 -s kraken -a 50:1 -a 24 -u v" produces audio that matches the Windows driver settings. If Windows is set to 24/96kHz, squeezelite will play all audio upsampled to 24/96kHz. If Windows is set to 16/48kHz, squeezelite will only play audio at 16/48kHz and ignore the "-a 24" flag."

    If I set Windows to 24/48kHz, squeezelite will play everything at 24/48kHz, but when I omit "-a 24" squeezelite outputs 16bit audio even for 24/96kHz files. However, it upsamples everything to the highest supported sample rate, 192kHz.

    If I omit both upsampling and format flags (".\squeezelite-win.exe -o 21 -s kraken -a 50:1"), squeezelite correctly ignores the Windows setting and matches the file's sample rate, but truncates everything to 16 bits. In this case Windows is set to 24/48kHz, but squeezelite ignores the bit depth setting as well.

    Running ".\squeezelite-win.exe -o 21 -s kraken -a 50:1 -a 24" without the upsampling flag just produces "_pa_open:395 error opening device 21 - JRiver Media Center 25 (JRiver Media Center 25) [Windows WASAPI] : Invalid device" again.

    I think the best option right now is to set Windows to the highest file sample-rate and just use Sox to upsample everything else with "squeezelite-win.exe -o 21 -s kraken -a 50:1 -a 24 -u v." I can make logs for any of these scenarios if you want.

    To summarize, squeezelite WASAPI output correctly switches sample rates in 16-bit mode regardless of Windows setting. For some reason, squeezelite fails if it tries to output anything other than the Windows driver sample rate setting in 24-bit output mode.

    Edit: Actually, scratch most of that. It appears that adding the "-a=24" flag after "-a 50:1" just disables exclusive mode and sets output to Windows driver settings. So, there is no way to get 24-bit audio out of squeezelite in exclusive mode.
    Last edited by Theriverlethe; 2020-05-31 at 18:48.

  9. #699
    Senior Member ralphy's Avatar
    Join Date
    Jan 2006
    Location
    Canada
    Posts
    2,502
    Quote Originally Posted by Theriverlethe View Post
    I've also noticed that this build doesn't output any audio, even in DirectSound mode. Is that intentional?
    It was not intentional but it provided the info I needed to confirm it's an issue between the driver and portaudio.

    Code:
    PinNew: Found endpoint pin id 1
    PinNew: Pin name 'Output'
    PinNew: Releasing topology filter...
    Pin created successfully
    PinNew: Creating pin 1:
    PinNew: Not source/sink
    PinNew: Error -9996 (paInvalidDevice)
    Filter (WaveCyclic) created with 1 valid pins (total I/Os: 1)
    after paHostApiInitializers[4].
    [12:00:59.114] output_init_common:350 outputbuf size: 3528000
    [12:00:59.114] output_init_common:374 idle timeout: 60000
    OpenStream:sampleRate = 384000.000000
    OpenStream:framesPerBuffer = 0
    Pin create result = 0x00000057 (ERROR_INVALID_PARAMETER) /* First case when pin actually doesn't support the format */ return paSampleFormatNotSupported;
    Pin create result = 0x00000057
    Pin create result = 0x00000057
    Pin create result = 0x00000057
    Pin create result = 0x00000057
    Pin create result = 0x00000057
    Pin create result = 0x00000057
    Pin create result = 0x00000057
    Pin create result = 0x00000057
    Pin create result = 0x00000057
    Pin create result = 0x00000057
    Pin create result = 0x00000057
    Pin create result = 0x00000057
    Pin create result = 0x00000057
    Pin create result = 0x00000057
    Pin create result = 0x00000057
    Pin create result = 0x00000057
    Pin create result = 0x00000057
    Pin create result = 0x00000057
    Pin create result = 0x00000057
    Pin create result = 0x00000057
    Pin create result = 0x00000057
    Pin create result = 0x00000057
    Pin create result = 0x00000057
    Pin create result = 0x00000057
    Pin create result = 0x00000057
    Pin create result = 0x00000057
    Pin create result = 0x00000057
    Pin create result = 0x00000057
    Pin create result = 0x00000057
    Pin create result = 0x00000057
    Pin create result = 0x00000057
    [12:00:59.115] test_open:237 error opening portaudio stream: Sample format not supported
    [12:00:59.115] output_init_common:391 unable to open output device: 37
    I've removed the debug build from the zip file.

    As another test can you try this build using the WASAPI device in exclusive mode using -a 20:1 instead of 50? The wdmks driver is identical to the official portaudio release so I don't expect any difference.
    Ralphy

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

  10. #700
    Junior Member
    Join Date
    Nov 2015
    Posts
    20
    Quote Originally Posted by DeNyss View Post
    Hi. I've performed a fresh installation of LMS nightly version 8.0.0 - 1590399854 and can't find plugin under 3rd party section anymore. Could someone guide me how to install it under Ubuntu server? Thanks.
    Or preferably someone in Triode's unavailability could update the plugin's repo to make it available for version 8.0.
    Last edited by Cebolla; 2020-06-02 at 11:05.

Posting Permissions

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