Forum Replies Created
Hmm, strange, I updated the OS and issue went away.
I’ll keep you posted if it resumes.
I sent the entire log folder in rar archive as it compresses better.
Thanks, I’ll keep an eye out for Version 7
That sucks 🙁
Any approximate ETA on AMD support? Or it’s ready whenever it’s ready? Any beta versions you need testing?
It says: NoMachine supports H.264 hardware encoding provided by graphics cards with Nvidia Kepler microarchitecture onward.
Does it mean AMD is unsupported? Chrome detects h.264 acceleration. RX550 specs say h.264 acceleration is supported.
Found the Log. Apparently It can’t load the H.264 library. Any idea why?
NXAGENT – Version 6.0.66
Copyright (C) 2001, 2016 NoMachine.
See http://www.nomachine.com/ for more information.
Session: Starting session at Fri Jan 19 20:55:04 2018.
Info: Agent running with pid 708.
Info: Slave server running with pid 3632.
Info: Listening to slave connections on port 12001.
Info: Display running with pid 8684.
Info: Audio server started with pid 2936.
Info: Audio client started with pid 5636.
Info: Display server started with pid 7244.
708 8684 20:55:04 500.312 AudioSystemUtilities: WARNING! Could not request original voice card name.
Session: Session started at Fri Jan 19 20:55:04 2018.
708 8684 20:55:06 296.415 AudioSystemUtilities: WARNING! Could not request original voice card name.
Warning: Can’t load H.264 codec library.
Warning: Child process 1396 exited with code 2, ‘No such file or directory’.
Info: Events handler running with pid 1092.
Info: Using SSE3 for screen analysis.
Info: Screen capture running with pid 6788.
Info: Using display polling for screen updates.
Info: Using screen size 1280×768.
Info: Screen analysis running with pid 3484.
Info: Using desktop manager for screen updates.
Info: Using DirectX for screen updates.
Info: RT handler running with pid 6352.
Info: Display server for 3F143A6617976D10126AB53146E15873 connected on Fri Jan 19 20:55:08 2018.
Info: Audio server for 3F143A6617976D10126AB53146E15873 connected on Fri Jan 19 20:55:08 2018.
Info: Audio client for 3F143A6617976D10126AB53146E15873 connected on Fri Jan 19 20:55:08 2018.
708 4564 20:55:08 319.531 AudioIoWasapiClientDevice: Cannot activate client.
708 4564 20:55:08 319.531 AudioIoWasapiClientDevice: Error is AUDCLNT_E_DEVICE_INVALIDATED.
Info: Using Vp8 software encoder.
708 6788 20:55:08 378.534 GPUEngine: Configuring GPU resources.
708 6788 20:57:43 395.401 MediaRealtime/Realtime: WARNING! Write to FD#2024 would block.
Sorry, forgot to mention that I’m using NoMachine Server for Windows
Any such files on Windows version?
ThanksJanuary 17, 2018 at 15:37 in reply to: Changing resolution on remote headless Windows Server #17159
Just to update this thread and say it’s fixed. Dongles solved my problem. Now I can choose up to 4k, what rx550 can push out.January 3, 2018 at 09:43 in reply to: Changing resolution on remote headless Windows Server #17032
Huh, Didn’t think about using headless dvi dongle.
Thanks GrayWolf. I’ll order one right away and will check it out. Most likely it will work then.