Tromegan

Forum Replies Created

Viewing 9 posts - 1 through 9 (of 9 total)
  • Author
    Posts
  • in reply to: State of Pipewire support #43543
    Tromegan
    Participant

    Hi @kubaszym1 – thanks a lot for your response – looking forward to the upcoming version.

    As for the current version – I have 8.4.2 on client and server – I also do have pw-cli under ‘/usr/bin/pw-cli’

    When it comes to sockets and their creation – the log says:

    2580686 2580686 2023-03-22 12:17:40 653.053 NXNODE   Starting audio service with session type ‘physicalAttachDesktop’.
    2580686 2580686 2023-03-22 12:17:40 653.091 NXNODE   Audio is enabled in configuration.
    2580686 2580686 2023-03-22 12:17:40 653.143 NXNODE   AUDIO returning 5:9:opus:fifo-/home/user/.nx/nxdevice/D-1002-70F1C3A3919CFF56CD4C4CE8603E2F64/audio/audio_in.fifo:1.
    2580686 2580686 2023-03-22 12:17:40 653.199 NXNODE   AUDIO returning 5:11:speex:fifo-/home/user/.nx/nxdevice/D-1002-70F1C3A3919CFF56CD4C4CE8603E2F64/audio/voice_out.fifo:1.
    2580686 2580686 2023-03-22 12:17:40 653.352 NXNODE   NXOptionsFile: Created options string ‘nx/nx,keyboard=evdev/en_US,cpus=6,threads=auto,priority=realtime,client=winnt,servercopysize=0,clientcopysize=0,audioin=5:9:opus:fifo-/home/user/.nx/nxdevice/D-1002-*****/audio/audio_in.fifo:1,voiceout=5:11:speex:fifo-/home/user/.nx/nxdevice/D-1002-*****/audio/voice_out.fifo:1,volume=0,devicesmartcard=1,deviceports=1,devicenetwork=1,legacykb=0,slave=1,cache=16M,images=64M,link=9,type=physical-desktop,clipboard=both,cleanup=0,accept=127.0.0.1,product=LS/None,shmem=1,backingstore=1,shpix=1,cookie=*****,id=ginaz-1002-*****,render=1,multipass=1,networkadaptive=0,encryption=1,proxy=8/8,monitor=9,rtremotehost=192.168.86.49,rtremoteport=4000,rtlocalport=4011,rtsession=25,rtkey=*****,rtiv=*****,rekey=32G,deblock=1,downsampling=0,mode=1,shadowmode=2,shadowuid=1000,shading=1,shadow=:1001:1002\n’.
    2580686 2580686 2023-03-22 12:17:40 653.436 NXNODE   NXOpen FD#10 – file /home/user/.nx/node/C-ginaz-1002-70F1C3A3919CFF56CD4C4CE8603E2F64/options with mode 1089 and permissions 384 from main::create_user_readable_only_file.
    2580686 2580686 2023-03-22 12:17:40 653.483 NXNODE   libnxh::NXFileMode(/home/user/.nx/node/C-ginaz-1002-70F1C3A3919CFF56CD4C4CE8603E2F64/options, 384)
    2580686 2580686 2023-03-22 12:17:40 653.527 NXNODE   libnxh::NXFileMode returns ‘0’.
    2580686 2580686 2023-03-22 12:17:40 653.562 NXNODE   file ‘/home/user/.nx/node/C-ginaz-1002-70F1C3A3919CFF56CD4C4CE8603E2F64/options’ opened for appending: FD [10]
    2580686 2580686 2023-03-22 12:17:40 653.639 NXNODE   written to file ‘/home/user/.nx/node/C-ginaz-1002-70F1C3A3919CFF56CD4C4CE8603E2F64/options’ bytes ‘nx/nx,keyboard=evdev/en_US,cpus=6,threads=auto,priority=realtime,client=winnt,servercopysize=0,clientcopysize=0,audioin=5:9:opus:fifo-/home/user/.nx/nxdevice/D-1002-*****/audio/audio_in.fifo:1,voiceout=5:11:speex:fifo-/home/user/.nx/nxdevice/D-1002-*****/audio/voice_out.fifo:1,volume=0,devicesmartcard=1,deviceports=1,devicenetwork=1,legacykb=0,slave=1,cache=16M,images=64M,link=9,type=physical-desktop,clipboard=both,cleanup=0,accept=127.0.0.1,product=LS/None,shmem=1,backingstore=1,shpix=1,cookie=******,id=ginaz-1002-*****,render=1,multipass=1,networkadaptive=0,encryption=1,proxy=8/8,monitor=9,rtremotehost=192.168.86.49,rtremoteport=4000,rtlocalport=4011,rtsession=25,rtkey=*****,rtiv=*****,rekey=32G,deblock=1,downsampling=0,mode=1,shadowmode=2,shadowuid=1000,shading=1,shadow=:1001:1002\n’

    and while it refers to creating those sockets – there is no audio under /home/user/.nx/D-1002-*/ – there is only cups, disk and printer.

    in reply to: State of Pipewire support #43427
    Tromegan
    Participant

    @Bilbotine – thanks! That article is what we started with – I am connecting to a physical session, and I do have pipewire configured and working

    in reply to: State of Pipewire support #43382
    Tromegan
    Participant

    Any update on this topic? Anything else I can provide to help figuring this out? Something else I should try?

    in reply to: State of Pipewire support #43294
    Tromegan
    Participant

    I do have pactl:

    user@host ~ $ which pactl
    /usr/bin/pactl
    user@host ~ $ LC_ALL=C pactl info
    Server String: /run/user/1000/pulse/native
    Library Protocol Version: 35
    Server Protocol Version: 35
    Is Local: yes
    Client Index: 178572
    Tile Size: 65472
    User Name: user
    Host Name: host
    Server Name: PulseAudio (on PipeWire 0.3.63)
    Server Version: 15.0.0
    Default Sample Specification: float32le 2ch 48000Hz
    Default Channel Map: front-left,front-right
    Default Sink: alsa_output.pci-0000_00_1f.3.analog-stereo
    Default Source: alsa_input.pci-0000_00_1f.3.analog-stereo.2
    Cookie: 83e0:ae3e

    in reply to: State of Pipewire support #43230
    Tromegan
    Participant

    Sorry, my bad – now sent both – userdir and full set of NX server logs as per documentation.

    in reply to: State of Pipewire support #43203
    Tromegan
    Participant

    Done – should be there..

    in reply to: State of Pipewire support #43200
    Tromegan
    Participant

    My server is Gentoo Linux with NoMachine 8.4.2 and my client is Windows 11 and also 8.4.2

    My config is like the following:

    # grep Audio ../../etc/node.cfg
    AudioInterface alsa
    EnableAudio 1
    # Specify path and name of the command to start PulseAudio server.
    CommandStartPulseAudio “”

    and attached is the nxserver log I am getting…

    in reply to: State of Pipewire support #43194
    Tromegan
    Participant

    Hm.. Thanks for the link, but it doesn’t really have anything on how to get pipewire to work.. Maybe I am missing something – it seems to be more focused on “temporary solution for virtual desktop cases” – like what should be set in node.cfg for Pipewire to work? I have “pulseaudio” there – is that right? I have: AudioInterface pulseaudio, EnableAudio 1 and CommandStartPulseAudio “” – is that right?

     

    in reply to: State of Pipewire support #43139
    Tromegan
    Participant

    Thanks @Britgirl for your response – is there any documentation on how to get it to work? I am connecting to a physical session, and I do have sound locally, but not via NoMachine..

Viewing 9 posts - 1 through 9 (of 9 total)