Encoding/Decoding error

Forum / NoMachine for Windows / Encoding/Decoding error

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #25402
    ryan
    Participant

    Re-posting this with more detail. Please see image below

    Server is Windows 10 Pro 1809

    Client is Windows 10 Pro 1803

    The affected apps are After Effects and Mocha for AE and the issue happens intermittently but always when scrubbing or interacting with the timeline (eg moving the play head around). Something else to note is that both apps utilize the GPU for performance. Please help!

    Attachments:
    #25411
    ryan
    Participant

    My sense of this is that it has something to do with GPU resources and having said that I need my apps to GPU priority over NoMachine while at the same time getting the best NoMachine experience possible.

    #25414
    Britgirl
    Keymaster

    Hi ryan,

    thanks for the image.

    Can you submit logs from both client side and server side?

    Instructions on how to to do that are here:

    Server side – https://www.nomachine.com/DT10O00163#1.4

    Client side – https://www.nomachine.com/DT10O00163#2.3

     

    Send via email to forum[at]nomachine[dot]com making sure you reference your topic 🙂

    #25446
    Britgirl
    Keymaster

    Ryan, we received the logs but you didn’t send us the logs from the server side – the remote computer. Also, what you sent us seems to be just the installation dir from the client side, it doesn’t contain the user home directory which is what we need to see.

    For the Windows client: write the following in the address bar or the file browser:
    USERPROFILE\.nx

    or navigate through the computer folder till the user’s home and type .nx in the navigation toolbar to reach the folder. The path can be similar to: C:/Users/USERPROFILE/.nx
    Zip up this folder.

    On the remote Windows host, zip up NoMachine’s /var/log folder typically found at PROGRAMDATA/NoMachine/var/log.

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

Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.