Forum Replies Created
-
AuthorPosts
-
kvicParticipant
Good to hear. Thanks again!
kvicParticipantIt works now!
I’ve been using it for a day at various quality settings. Eventually it will end up crystal sharp every time (after a very brief transition). Thank you very much!
My last wish (not related to this thread):
Hopefully AMD GPU will be supported for HW encoding soon as in FR01P03578.
🙂
kvicParticipantHi there
First of all, great to hear you have a breakthrough on this issue!
I’m sorry for my late response. I followed the instructions in the email. nx server starts successfully. But then cannot make a connection.
I followed your webpage’s instructions on checking server log and found the following errors in “session” file when nx client attempts to connect to nx server:
NXAGENT – Version 6.9.2
Copyright (C) 2001, 2019 NoMachine.
See http://www.nomachine.com/ for more information.Session: Starting session at Sun Jan 26 00:05:44 2020.
Info: Agent running with pid 1287.
Info: Slave server running with pid 19971.
Info: Display running with pid 19203.
Info: Listening to slave connections on port 12002.
Session: Session started at Sun Jan 26 00:05:45 2020.
dyld: lazy symbol binding failed: Symbol not found: _NXShadowOptionSetXTestWorkaround
Referenced from: /Applications/NoMachine.app/Contents/Frameworks/bin/../lib/libnxdiag.dylib
Expected in: /Applications/NoMachine.app/Contents/Frameworks/bin/../lib/../lib/libnxdimi.dylibdyld: Symbol not found: _NXShadowOptionSetXTestWorkaround
Referenced from: /Applications/NoMachine.app/Contents/Frameworks/bin/../lib/libnxdiag.dylib
Expected in: /Applications/NoMachine.app/Contents/Frameworks/bin/../lib/../lib/libnxdimi.dylibPlease advise.
Cheers
kvicParticipantHi there,
Server side has four items listed under “Scaled” resolutions:
- 2560×1440
- 1600×900
- 1080p
- 720p
Client side has exactly the same items.
I tried to set server to different scaled resolutions in macOS. I also realized that NX client can request custom resolution as well as setting to match client. Played with them individually or in combination. Make no difference.
I believe the issue may be before the encoder (as it happens in h264, VP8 and MJPEG). Perhaps a common setting applicable to all of them in the encoding pipeline.
I’m no expert in video encoding. Google pointed me to discussions about color space. In particular, some people mentioned YUV 4:4:4 vs YUV 4:2:2. The latter hurts bright colors in non-video materials (such as graphics and text). Don’t know if it’s relevant but worth checking.
Cheers
kvicParticipantHi fra81
Thanks for the prompt help. I tried your suggestion but no difference unfortunately. Based on in-line comments in the file, I also tried ‘EncoderMode quality’ but no difference either.
Cheers
kvicParticipantJust installed 6.8.2 (typing this message from it). So far the fix works flawlessly. It’s a huge relief for me personally & I hope it benefits other users suffering from the same issue.
Thank you very much for the quick fix & being so helpful!
-
AuthorPosts