fra81

Forum Replies Created

Viewing 15 posts - 346 through 360 (of 736 total)
  • Author
    Posts
  • in reply to: HW encoding on Jetson TX2 #23506
    fra81
    Moderator

    Hi Dario,

    generally reducing image quality doesn’t decrease CPU usage, but reducing frame rate does. It is possible to set any value from 1  to 1000 by editing manually the node.cfg file on server side. For example, to have 10 frames per second, you can uncomment and set the following keys:

    DisplayServerVideoFrameRate 10

    DisplayServerUseVideoFrameRate 1

    Another thing you can do is disabling the “lossless refinement” algorithm:

    DisplayServerExtraOptions “-refinement 0”

    in reply to: HW encoding on Jetson TX2 #23493
    fra81
    Moderator

    Hi Dario,

    at the moment NoMachine needs Nvidia Video Codec (NVENC) and that is not supported on Jetson.

    There is work in progress to leverage OMX encoders and decoders in the future, mainly for mobile and embedded platforms, but I wouldn’t be able to say a date yet.

    in reply to: Frequent freezing of the host display #23343
    fra81
    Moderator

    Please send us logs from the host machine as explained in https://www.nomachine.com/AR10K00697.

    And client side logs as explained in https://www.nomachine.com/DT10O00163#2.3.

    You can also send them to forum[at]nomachine[dot]com.

    in reply to: Hardware encoding failing #23324
    fra81
    Moderator

    At the moment, the only way not to use all monitors is unplugging them physically from the server. Artifacts could be due to a bug in the H.264 software encoder with such a high horizontal resolution. Please try to use a different codec: open Server preferences -> Performance tab, check ‘Use a specific display encoding’ and make sure VP8 is selected, then restart the server and connect again.

    in reply to: Frequent freezing of the host display #23314
    fra81
    Moderator

    Hi Juerg,

    this problem is unknown. As a first try, please open Server preferences -> Performance tab on your host machine, and unselect ‘Use acceleration for display processing’.

    in reply to: Hardware encoding failing #23293
    fra81
    Moderator

    You seem to have two 4K monitors, that give the total screen size reported in the logs:

        Info: Using screen size 7280×1080.

    Unfortunately NVENC (Nvidia’s encoder) supports up to 4K, as you can see here:

    https://developer.nvidia.com/nvidia-video-codec-sdk#NVENCFeatures

    However this Feature Request, when implemented, will address your case:

    https://www.nomachine.com/FR05N03113

    For the records, you can see that the hardware encoder is used when there is a single monitor:

        Info: Using screen size 3840×1080.
        Info: Using Nvidia H.264 hardware encoder.

     

    in reply to: Hardware encoding failing #23271
    fra81
    Moderator

    Hi,

    can you please send all the logs. Whole ‘/usr/NX/var/log’ directory if possible. You can send it to forum[at]nomachine[dot]com.

    fra81
    Moderator

    15% of CPU usage doesn’t seem too much if the screen is updating. Are you using latest NoMachine versions on client and server? Recent versions always ship the H.264 encoder which minimizes CPU usage. Anyway you can check the used codec in the Display settings panel.

    in reply to: Set GPU ID for nxnode.bin in multi-GPU setup #23006
    fra81
    Moderator

    Hi,

    for the moment NoMachine doesn’t have an option to select a specific GPU and NoMachine just iterates by default through available cards. However we’ve created a new feature request that will cover this case:

    https://www.nomachine.com/FR07Q03854

    in reply to: Images corrupted #22700
    fra81
    Moderator

    Does setting max quality in https://www.nomachine.com/DT07M00087#5.7 make any difference? You can also try to check ‘Disable network-adaptive display quality’ and ‘Disable multi-pass display encoding’ in the same panel.

    You may also try to disabled UDP. To do so, enter the Edit panel of the connection, click Advanced and uncheck ‘Use UDP communication for multimedia data’.

    If nothing works, please send a video recording showing the issue.

    in reply to: Images corrupted #22644
    fra81
    Moderator

    Hi,

    for a start, you can try to disable hardware decoding, by checking the box in the session menu:

    https://www.nomachine.com/DT07M00087#5.7

    and hardware encoding, by uncommenting and changing the relevant key in the <installation directory>/etc/node.cfg file:

    EnableHardwareEncoding 0

     

    in reply to: Green screen/hardware decoding problem #22618
    fra81
    Moderator

    Hi gabriele,

    can you specify the driver version? If possible, send us the logs as explained in my post above.

    And does disabling ‘client side hardware decoding’ fix the problem also in your case?

    in reply to: Black screen connecting to NX 6.7.6 on Linux #22510
    fra81
    Moderator

    The problem is, that all opened windows on display “1” (programs, terminals, etc…) opens in display “0” (I see it in task manager), except NoMachine client and server windows, they are opens normally. So, what am I doing wrong? And how fix it?

    I assume that both desktops are owned by the same system user. In that case, how the display to connect to is chosen depends on the application. What you can do is starting the second desktop as a different user. Not sure if you can configure those applications to behave differently.

    in reply to: Black screen connecting to NX 6.7.6 on Linux #22455
    fra81
    Moderator

    Hi,

    we are aware of the issue which is due to incorrect info reported by the X RandR extension on some headless machines. Besides the workarounds you already mentioned, you can use also this one: https://www.nomachine.com/AR03P00973.

    If you’d like to receive a patched version to test, please write to forum[at]nomachine[dot]com.

    in reply to: Green screen/hardware decoding problem #22398
    fra81
    Moderator

    Hi,

    are you aware of any video drivers update on your system? What’s your graphics card model and driver version?

    Please also send client side logs, gathered while reproducing the green screen problem. You can extract them as explained in https://www.nomachine.com/DT10O00163#2 and send to forum[at]nomachine[dot]com.

Viewing 15 posts - 346 through 360 (of 736 total)