Joplin is a free, open source note taking and to-do application, which can handle a large number of notes organised into notebooks. The notes are searchable, can be copied, tagged and modified either from the applications directly or from your own text editor. The notes are in Markdown format.
Notes exported from Evernote can be imported into Joplin, including the formatted content (which is converted to Markdown), resources (images, attachments, etc.) and complete metadata (geolocation, updated time, created time, etc.). Plain Markdown files can also be imported.
Joplin is "offline first", which means you always have all your data on your phone or computer. This ensures that your notes are always accessible, whether you have an internet connection or not.
The notes can be securely synchronised using end-to-end encryption with various cloud services including Nextcloud, Dropbox, OneDrive and Joplin Cloud.
Full text search is available on all platforms to quickly find the information you need. The app can be customised using plugins and themes, and you can also easily create your own.
minor feature: lt;ul gt;.
lt;li gt;Improved: Accessibility: Make click outside of dialog content be cancellable lt;/li gt;.
lt;li gt;Improved: Improve behaviour of note list to-dos when ticking a checkbox using the keyboard ( lt;a class="commit-link" data-hovercard-type="commit" data-hovercard-url="https://github.com/laurent22/joplin/commit/44c735afac8b087ac77d05d2b9882ad24f79c605/hovercard" href="https://github.com/laurent22/joplin/commit/44c735afac8b087ac77d05d2b9882ad24f79c605" gt; lt;tt gt;44c735a lt;/tt gt; lt;/a gt;) lt;/li gt;.
lt;li gt;Improved: Improve usability of note list when ticking to-dos using the Space key lt;/li gt;.
lt;li gt;Improved: Plugins: Simplify getting the ID of the note open in an editor lt;/li gt;.
lt;li gt;: OneNote importer not being able to handle corrupted attachments lt;/li gt;.
lt;li gt;: Rich Text right-click and paste regressions lt;/li gt;.
lt;li gt;: Hide extra clear button in search field lt;/li gt;.
lt;li gt;: Preserve attachment file extensions regardless of the mime type lt;/li gt;.
lt;/ul gt;.
 Affero GPLv3 note-taking todo markdown typescript javascript
Self-hosted photo and video management solution
Easily back up, organize, and manage your photos on your own server. Immich helps you browse, search and organize your photos and videos with ease, without sacrificing your privacy.
minor feature: lt;h1 gt;v1.129.0 lt;/h1 gt;.
lt;p gt;Welcome to release lt;code gt;v1.129.0 lt;/code gt; of Immich. The road-to-stable is bumpy, but at least, we have lt;em gt;made memories lt;/em gt; together with the recent changes and with the new memories implementation . We owe you an explanation for the changes. Please find it, along with the highlights of this release below: lt;/p gt;.
lt;ul gt;.
lt;li gt;Videos in memories are now playable on the web. lt;/li gt;.
lt;li gt;Shortcuts ( lt;code gt;L lt;/code gt; and lt;code gt;Shift+L lt;/code gt;) to add assets to an album or shared album on the web. lt;/li gt;.
lt;li gt;an where opening Immich pauses playing music on iOS lt;/li gt;.
lt;li gt;The shared link now has a generated QR code for easier sharing. lt;/li gt;.
lt;/ul gt;.
lt;p align="center" gt;.
lt;a target="_blank" rel="noopener noreferrer" href="https://private-user-images.githubusercontent.com/27055614/419634334-4e65dcab-c4c8-4394-8d0e-9fcddcc9da59.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NDEyMzEyMDIsIm5iZiI6MTc0MTIzMDkwMiwicGF0aCI6Ii8yNzA1NTYxNC80MTk2MzQzMzQtNGU2NWRjYWItYzRjOC00Mzk0LThkMGUtOWZjZGRjYzlkYTU5LnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAzMDYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMzA2VDAzMTUwMlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTNkZjE2ODAzNmIwYzNkMjlhOWFjOGRmZWI5ZDU1MDBiYzM4MTQzYjQ5ODQ1YzMxOGMzMzIxMjYxM2UxMTU0YzMmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.Ic6hxmyVjtzu49jnd2nUGfQaNFqVVxYp8m7HyoT57Iw" gt; lt;img src="https://private-user-images.githubusercontent.com/27055614/419634334-4e65dcab-c4c8-4394-8d0e-9fcddcc9da59.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NDEyMzEyMDIsIm5iZiI6MTc0MTIzMDkwMiwicGF0aCI6Ii8yNzA1NTYxNC80MTk2MzQzMzQtNGU2NWRjYWItYzRjOC
Affero GPLv3 self-hosted backup photos photography video server typescript javascript svelte dart python
LSP (Linux Studio Plugins) is a collection of open-source plugins currently compatible with CLAP, LADSPA, LV2, VST2/LinuxVST, VST3 and JACK standalone formats.
The basic idea is to fill the lack of good and useful plugins under the GNU/Linux platform.
After some contributions to other open source projects the decision was made to implement separate and independent plugin distribution.
minor feature: Implemented default OpenGL rendering engine for the UI for X11-based operating systems. The rendering engine can be switched back to Cairo by setting LSP_WS_LIB_GLXSURFACE=off environment variable. Added possibility to use custom scaling for each plugin bundle. Added highlighting of active item in file navigator nearby sample preview. Several optimizations related to scaling widgets in the graphical toolkit library. Updated several core libraries for better support of MacOS. Additional AVX-512 optimizations of code DSP library. Several changes in Sampler and Multisampler plugin series: Implemented possibility to Drag Drop drumkits, SFZ files and LSPC files directly to the plugin's window for import purpose. Muting button does not disable the listen button. Added 'velocity' button that allows to disable or enable the volume control of a sample by the velocity value of the MIDI note. Added automatic instrument name assign same to current sample file name if UI behavior option 'Take instrument name from file' is enabled and the name of instrument is empty or similar to currently selected sample file. Updated several labels in the UI. Added workaround for Renoise host related to latency reporting by VST2 and VST3 plugins on state load. unnecessary output parameter cleanup when importing configuration that caused several when importing plugin state from file. regression related to impossibility of setting proper values for in several parameters in the VST3 plugin format. some typos in UI.
GNU LGPLv3 audio plugins music vst jack clap ladspa cpp makefile
The qBittorrent project aims to provide an open-source software alternative to µTorrent.
Additionally, qBittorrent runs and provides the same features on all major platforms (Linux, Mac OS X, Windows, OS/2, FreeBSD).
qBittorrent is based on the Qt toolkit and libtorrent-rasterbar library.
minor feature: cannot remove trackers via WebAPI (Chocobo1). : torrent content checkbox state under certain conditions (thalieht). : Hide zero and infinity values in peer list only when that setting is set to. Always (thalieht). : Remove stopped torrent from "error" tracker filter (glassez). WEBUI: memory leak in context menus (skomerko). WEBAPI: Don't trim string parameters (glassez). WINDOWS: Handle Qt style options uniformly (glassez). WINDOWS: NSIS: Update Portuguese translation (Hugo Carvalho). MACOS: Avoid memory leak (Chocobo1).
Apache internet download torrent bittorent file-sharing cpp javascript html python qt
The qBittorrent project aims to provide an open-source software alternative to µTorrent.
Additionally, qBittorrent runs and provides the same features on all major platforms (Linux, Mac OS X, Windows, OS/2, FreeBSD).
qBittorrent is based on the Qt toolkit and libtorrent-rasterbar library.
minor feature: cannot remove trackers via WebAPI (Chocobo1). : torrent content checkbox state under certain conditions (thalieht). : Hide zero and infinity values in peer list only when that setting is set to. Always (thalieht). : Remove stopped torrent from "error" tracker filter (glassez). WEBUI: memory leak in context menus (skomerko). WEBAPI: Don't trim string parameters (glassez). WINDOWS: Handle Qt style options uniformly (glassez). WINDOWS: NSIS: Update Portuguese translation (Hugo Carvalho). MACOS: Avoid memory leak (Chocobo1).
Apache internet download torrent bittorent file-sharing cpp javascript html python qt
The qBittorrent project aims to provide an open-source software alternative to µTorrent.
Additionally, qBittorrent runs and provides the same features on all major platforms (Linux, Mac OS X, Windows, OS/2, FreeBSD).
qBittorrent is based on the Qt toolkit and libtorrent-rasterbar library.
minor feature: cannot remove trackers via WebAPI (Chocobo1). : torrent content checkbox state under certain conditions (thalieht). : Hide zero and infinity values in peer list only when that setting is set to. Always (thalieht). : Remove stopped torrent from "error" tracker filter (glassez). WEBUI: memory leak in context menus (skomerko). WEBAPI: Don't trim string parameters (glassez). WINDOWS: Handle Qt style options uniformly (glassez). WINDOWS: NSIS: Update Portuguese translation (Hugo Carvalho). MACOS: Avoid memory leak (Chocobo1).
Apache internet download torrent bittorent file-sharing cpp javascript html python qt
The qBittorrent project aims to provide an open-source software alternative to µTorrent.
Additionally, qBittorrent runs and provides the same features on all major platforms (Linux, Mac OS X, Windows, OS/2, FreeBSD).
qBittorrent is based on the Qt toolkit and libtorrent-rasterbar library.
minor feature: cannot remove trackers via WebAPI (Chocobo1). : torrent content checkbox state under certain conditions (thalieht). : Hide zero and infinity values in peer list only when that setting is set to. Always (thalieht). : Remove stopped torrent from "error" tracker filter (glassez). WEBUI: memory leak in context menus (skomerko). WEBAPI: Don't trim string parameters (glassez). WINDOWS: Handle Qt style options uniformly (glassez). WINDOWS: NSIS: Update Portuguese translation (Hugo Carvalho). MACOS: Avoid memory leak (Chocobo1).
Apache internet download torrent bittorent file-sharing cpp javascript html python qt
The qBittorrent project aims to provide an open-source software alternative to µTorrent.
Additionally, qBittorrent runs and provides the same features on all major platforms (Linux, Mac OS X, Windows, OS/2, FreeBSD).
qBittorrent is based on the Qt toolkit and libtorrent-rasterbar library.
minor feature: cannot remove trackers via WebAPI (Chocobo1). : torrent content checkbox state under certain conditions (thalieht). : Hide zero and infinity values in peer list only when that setting is set to. Always (thalieht). : Remove stopped torrent from "error" tracker filter (glassez). WEBUI: memory leak in context menus (skomerko). WEBAPI: Don't trim string parameters (glassez). WINDOWS: Handle Qt style options uniformly (glassez). WINDOWS: NSIS: Update Portuguese translation (Hugo Carvalho). MACOS: Avoid memory leak (Chocobo1).
Apache internet download torrent bittorent file-sharing cpp javascript html python qt
The qBittorrent project aims to provide an open-source software alternative to µTorrent.
Additionally, qBittorrent runs and provides the same features on all major platforms (Linux, Mac OS X, Windows, OS/2, FreeBSD).
qBittorrent is based on the Qt toolkit and libtorrent-rasterbar library.
minor feature: cannot remove trackers via WebAPI (Chocobo1). : torrent content checkbox state under certain conditions (thalieht). : Hide zero and infinity values in peer list only when that setting is set to. Always (thalieht). : Remove stopped torrent from "error" tracker filter (glassez). WEBUI: memory leak in context menus (skomerko). WEBAPI: Don't trim string parameters (glassez). WINDOWS: Handle Qt style options uniformly (glassez). WINDOWS: NSIS: Update Portuguese translation (Hugo Carvalho). MACOS: Avoid memory leak (Chocobo1).
Apache internet download torrent bittorent file-sharing cpp javascript html python qt
The qBittorrent project aims to provide an open-source software alternative to µTorrent.
Additionally, qBittorrent runs and provides the same features on all major platforms (Linux, Mac OS X, Windows, OS/2, FreeBSD).
qBittorrent is based on the Qt toolkit and libtorrent-rasterbar library.
minor feature: cannot remove trackers via WebAPI (Chocobo1). : torrent content checkbox state under certain conditions (thalieht). : Hide zero and infinity values in peer list only when that setting is set to. Always (thalieht). : Remove stopped torrent from "error" tracker filter (glassez). WEBUI: memory leak in context menus (skomerko). WEBAPI: Don't trim string parameters (glassez). WINDOWS: Handle Qt style options uniformly (glassez). WINDOWS: NSIS: Update Portuguese translation (Hugo Carvalho). MACOS: Avoid memory leak (Chocobo1).
Apache internet download torrent bittorent file-sharing cpp javascript html python qt
The qBittorrent project aims to provide an open-source software alternative to µTorrent.
Additionally, qBittorrent runs and provides the same features on all major platforms (Linux, Mac OS X, Windows, OS/2, FreeBSD).
qBittorrent is based on the Qt toolkit and libtorrent-rasterbar library.
minor feature: cannot remove trackers via WebAPI (Chocobo1). : torrent content checkbox state under certain conditions (thalieht). : Hide zero and infinity values in peer list only when that setting is set to. Always (thalieht). : Remove stopped torrent from "error" tracker filter (glassez). WEBUI: memory leak in context menus (skomerko). WEBAPI: Don't trim string parameters (glassez). WINDOWS: Handle Qt style options uniformly (glassez). WINDOWS: NSIS: Update Portuguese translation (Hugo Carvalho). MACOS: Avoid memory leak (Chocobo1).
Apache internet download torrent bittorent file-sharing cpp javascript html python qt
The qBittorrent project aims to provide an open-source software alternative to µTorrent.
Additionally, qBittorrent runs and provides the same features on all major platforms (Linux, Mac OS X, Windows, OS/2, FreeBSD).
qBittorrent is based on the Qt toolkit and libtorrent-rasterbar library.
minor feature: cannot remove trackers via WebAPI (Chocobo1). : torrent content checkbox state under certain conditions (thalieht). : Hide zero and infinity values in peer list only when that setting is set to. Always (thalieht). : Remove stopped torrent from "error" tracker filter (glassez). WEBUI: memory leak in context menus (skomerko). WEBAPI: Don't trim string parameters (glassez). WINDOWS: Handle Qt style options uniformly (glassez). WINDOWS: NSIS: Update Portuguese translation (Hugo Carvalho). MACOS: Avoid memory leak (Chocobo1).
Apache internet download torrent bittorent file-sharing cpp javascript html python qt
The qBittorrent project aims to provide an open-source software alternative to µTorrent.
Additionally, qBittorrent runs and provides the same features on all major platforms (Linux, Mac OS X, Windows, OS/2, FreeBSD).
qBittorrent is based on the Qt toolkit and libtorrent-rasterbar library.
minor feature: cannot remove trackers via WebAPI (Chocobo1). : torrent content checkbox state under certain conditions (thalieht). : Hide zero and infinity values in peer list only when that setting is set to. Always (thalieht). : Remove stopped torrent from "error" tracker filter (glassez). WEBUI: memory leak in context menus (skomerko). WEBAPI: Don't trim string parameters (glassez). WINDOWS: Handle Qt style options uniformly (glassez). WINDOWS: NSIS: Update Portuguese translation (Hugo Carvalho). MACOS: Avoid memory leak (Chocobo1).
Apache internet download torrent bittorent file-sharing cpp javascript html python qt
The qBittorrent project aims to provide an open-source software alternative to µTorrent.
Additionally, qBittorrent runs and provides the same features on all major platforms (Linux, Mac OS X, Windows, OS/2, FreeBSD).
qBittorrent is based on the Qt toolkit and libtorrent-rasterbar library.
minor feature: cannot remove trackers via WebAPI (Chocobo1). : torrent content checkbox state under certain conditions (thalieht). : Hide zero and infinity values in peer list only when that setting is set to. Always (thalieht). : Remove stopped torrent from "error" tracker filter (glassez). WEBUI: memory leak in context menus (skomerko). WEBAPI: Don't trim string parameters (glassez). WINDOWS: Handle Qt style options uniformly (glassez). WINDOWS: NSIS: Update Portuguese translation (Hugo Carvalho). MACOS: Avoid memory leak (Chocobo1).
Apache internet download torrent bittorent file-sharing cpp javascript html python qt
TurboVNC is a performance-oriented version of the VNC remote desktop connection protocol, based on TightVNC, x4vnc, TigerVNC, and X.org. It provides 3D rendering and VirtualGL compression, works well on video and image-intensive connections. It remains fully compatible to other implementations, but often requires less than a fifth processing power.
A Java-based VNC viewer is also available
minor feature: ===.
### Significant changes relative to 3.2 beta1:
1. a regression introduced by 3.0.3 7 that, under rare circumstances if.
Automatic desktop resizing was enabled, caused the viewer to deadlock while
Resizing its window in response to a remote desktop size change.
3.2 beta1.
### Significant changes relative to 3.1.4:
1. The TurboVNC Server now incorporates zlib-ng, which accelerates zlib.
Encoding significantly on x86, Arm, and PowerPC CPUs. Relative to TurboVNC
3.1.x, this improves the encoding performance of the Lossless Tight + Zlib
Encoding method, and of non-JPEG (low-color-depth) subrectangles encoded with
One of the Tight + JPEG encoding methods, by approximately 10-15 on reasonably
Modern x86-64 CPUs and 25-30 on reasonably modern AArch64 CPUs.
2. Since all supported TurboVNC host platforms now contain new enough libraries.
to build xorg-server 1.20.x, the TurboVNC Server is now dynamically linked
Against the system-supplied versions of these libraries rather than statically
Linked against in-tree versions. The `TVNC_SYSTEMLIBS` and `TVNC_SYSTEMX11`
CMake variables have been removed, and the build system now behaves as if those
Variables are always on. A new CMake variable (`TVNC_ZLIBNG`) can be used on
X86 platforms to disable the in-tree SIMD-accelerated zlib-ng implementation
And build against the system-supplied zlib implementation.
3. The TurboVNC Server now supports the DRI3 X extension when using open source.
GPU drivers. This enables GPU acceleration in a TurboVNC session without
VirtualGL, although the performance will be better with VirtualGL. Refer to
The description of the `-drinode` option in the Xvnc man page for more details.
4. The default X startup script (`xstartup.turbovnc`) now throws an error.
Rather than trying to execute xinitrc or twm, if a session desktop file for
The default window manager cannot be found.
5. Configuration of the TurboVNC Viewer has been improved in the following.
Ways:
- Advanced param
Apache c vnc rdp remote-desktop 3d tightvnc cross-platform java
TurboVNC is a performance-oriented version of the VNC remote desktop connection protocol, based on TightVNC, x4vnc, TigerVNC, and X.org. It provides 3D rendering and VirtualGL compression, works well on video and image-intensive connections. It remains fully compatible to other implementations, but often requires less than a fifth processing power.
A Java-based VNC viewer is also available
minor feature: ===.
### Significant changes relative to 3.2 beta1:
1. a regression introduced by 3.0.3 7 that, under rare circumstances if.
Automatic desktop resizing was enabled, caused the viewer to deadlock while
Resizing its window in response to a remote desktop size change.
3.2 beta1.
### Significant changes relative to 3.1.4:
1. The TurboVNC Server now incorporates zlib-ng, which accelerates zlib.
Encoding significantly on x86, Arm, and PowerPC CPUs. Relative to TurboVNC
3.1.x, this improves the encoding performance of the Lossless Tight + Zlib
Encoding method, and of non-JPEG (low-color-depth) subrectangles encoded with
One of the Tight + JPEG encoding methods, by approximately 10-15 on reasonably
Modern x86-64 CPUs and 25-30 on reasonably modern AArch64 CPUs.
2. Since all supported TurboVNC host platforms now contain new enough libraries.
to build xorg-server 1.20.x, the TurboVNC Server is now dynamically linked
Against the system-supplied versions of these libraries rather than statically
Linked against in-tree versions. The `TVNC_SYSTEMLIBS` and `TVNC_SYSTEMX11`
CMake variables have been removed, and the build system now behaves as if those
Variables are always on. A new CMake variable (`TVNC_ZLIBNG`) can be used on
X86 platforms to disable the in-tree SIMD-accelerated zlib-ng implementation
And build against the system-supplied zlib implementation.
3. The TurboVNC Server now supports the DRI3 X extension when using open source.
GPU drivers. This enables GPU acceleration in a TurboVNC session without
VirtualGL, although the performance will be better with VirtualGL. Refer to
The description of the `-drinode` option in the Xvnc man page for more details.
4. The default X startup script (`xstartup.turbovnc`) now throws an error.
Rather than trying to execute xinitrc or twm, if a session desktop file for
The default window manager cannot be found.
5. Configuration of the TurboVNC Viewer has been improved in the following.
Ways:
- Advanced param
Apache c vnc rdp remote-desktop 3d tightvnc cross-platform java
TurboVNC is a performance-oriented version of the VNC remote desktop connection protocol, based on TightVNC, x4vnc, TigerVNC, and X.org. It provides 3D rendering and VirtualGL compression, works well on video and image-intensive connections. It remains fully compatible to other implementations, but often requires less than a fifth processing power.
A Java-based VNC viewer is also available
minor feature: ===.
### Significant changes relative to 3.2 beta1:
1. a regression introduced by 3.0.3 7 that, under rare circumstances if.
Automatic desktop resizing was enabled, caused the viewer to deadlock while
Resizing its window in response to a remote desktop size change.
3.2 beta1.
### Significant changes relative to 3.1.4:
1. The TurboVNC Server now incorporates zlib-ng, which accelerates zlib.
Encoding significantly on x86, Arm, and PowerPC CPUs. Relative to TurboVNC
3.1.x, this improves the encoding performance of the Lossless Tight + Zlib
Encoding method, and of non-JPEG (low-color-depth) subrectangles encoded with
One of the Tight + JPEG encoding methods, by approximately 10-15 on reasonably
Modern x86-64 CPUs and 25-30 on reasonably modern AArch64 CPUs.
2. Since all supported TurboVNC host platforms now contain new enough libraries.
to build xorg-server 1.20.x, the TurboVNC Server is now dynamically linked
Against the system-supplied versions of these libraries rather than statically
Linked against in-tree versions. The `TVNC_SYSTEMLIBS` and `TVNC_SYSTEMX11`
CMake variables have been removed, and the build system now behaves as if those
Variables are always on. A new CMake variable (`TVNC_ZLIBNG`) can be used on
X86 platforms to disable the in-tree SIMD-accelerated zlib-ng implementation
And build against the system-supplied zlib implementation.
3. The TurboVNC Server now supports the DRI3 X extension when using open source.
GPU drivers. This enables GPU acceleration in a TurboVNC session without
VirtualGL, although the performance will be better with VirtualGL. Refer to
The description of the `-drinode` option in the Xvnc man page for more details.
4. The default X startup script (`xstartup.turbovnc`) now throws an error.
Rather than trying to execute xinitrc or twm, if a session desktop file for
The default window manager cannot be found.
5. Configuration of the TurboVNC Viewer has been improved in the following.
Ways:
- Advanced param
Apache c vnc rdp remote-desktop 3d tightvnc cross-platform java
TurboVNC is a performance-oriented version of the VNC remote desktop connection protocol, based on TightVNC, x4vnc, TigerVNC, and X.org. It provides 3D rendering and VirtualGL compression, works well on video and image-intensive connections. It remains fully compatible to other implementations, but often requires less than a fifth processing power.
A Java-based VNC viewer is also available
minor feature: ===.
### Significant changes relative to 3.2 beta1:
1. a regression introduced by 3.0.3 7 that, under rare circumstances if.
Automatic desktop resizing was enabled, caused the viewer to deadlock while
Resizing its window in response to a remote desktop size change.
3.2 beta1.
### Significant changes relative to 3.1.4:
1. The TurboVNC Server now incorporates zlib-ng, which accelerates zlib.
Encoding significantly on x86, Arm, and PowerPC CPUs. Relative to TurboVNC
3.1.x, this improves the encoding performance of the Lossless Tight + Zlib
Encoding method, and of non-JPEG (low-color-depth) subrectangles encoded with
One of the Tight + JPEG encoding methods, by approximately 10-15 on reasonably
Modern x86-64 CPUs and 25-30 on reasonably modern AArch64 CPUs.
2. Since all supported TurboVNC host platforms now contain new enough libraries.
to build xorg-server 1.20.x, the TurboVNC Server is now dynamically linked
Against the system-supplied versions of these libraries rather than statically
Linked against in-tree versions. The `TVNC_SYSTEMLIBS` and `TVNC_SYSTEMX11`
CMake variables have been removed, and the build system now behaves as if those
Variables are always on. A new CMake variable (`TVNC_ZLIBNG`) can be used on
X86 platforms to disable the in-tree SIMD-accelerated zlib-ng implementation
And build against the system-supplied zlib implementation.
3. The TurboVNC Server now supports the DRI3 X extension when using open source.
GPU drivers. This enables GPU acceleration in a TurboVNC session without
VirtualGL, although the performance will be better with VirtualGL. Refer to
The description of the `-drinode` option in the Xvnc man page for more details.
4. The default X startup script (`xstartup.turbovnc`) now throws an error.
Rather than trying to execute xinitrc or twm, if a session desktop file for
The default window manager cannot be found.
5. Configuration of the TurboVNC Viewer has been improved in the following.
Ways:
- Advanced param
Apache c vnc rdp remote-desktop 3d tightvnc cross-platform java
TurboVNC is a performance-oriented version of the VNC remote desktop connection protocol, based on TightVNC, x4vnc, TigerVNC, and X.org. It provides 3D rendering and VirtualGL compression, works well on video and image-intensive connections. It remains fully compatible to other implementations, but often requires less than a fifth processing power.
A Java-based VNC viewer is also available
minor feature: ===.
### Significant changes relative to 3.2 beta1:
1. a regression introduced by 3.0.3 7 that, under rare circumstances if.
Automatic desktop resizing was enabled, caused the viewer to deadlock while
Resizing its window in response to a remote desktop size change.
3.2 beta1.
### Significant changes relative to 3.1.4:
1. The TurboVNC Server now incorporates zlib-ng, which accelerates zlib.
Encoding significantly on x86, Arm, and PowerPC CPUs. Relative to TurboVNC
3.1.x, this improves the encoding performance of the Lossless Tight + Zlib
Encoding method, and of non-JPEG (low-color-depth) subrectangles encoded with
One of the Tight + JPEG encoding methods, by approximately 10-15 on reasonably
Modern x86-64 CPUs and 25-30 on reasonably modern AArch64 CPUs.
2. Since all supported TurboVNC host platforms now contain new enough libraries.
to build xorg-server 1.20.x, the TurboVNC Server is now dynamically linked
Against the system-supplied versions of these libraries rather than statically
Linked against in-tree versions. The `TVNC_SYSTEMLIBS` and `TVNC_SYSTEMX11`
CMake variables have been removed, and the build system now behaves as if those
Variables are always on. A new CMake variable (`TVNC_ZLIBNG`) can be used on
X86 platforms to disable the in-tree SIMD-accelerated zlib-ng implementation
And build against the system-supplied zlib implementation.
3. The TurboVNC Server now supports the DRI3 X extension when using open source.
GPU drivers. This enables GPU acceleration in a TurboVNC session without
VirtualGL, although the performance will be better with VirtualGL. Refer to
The description of the `-drinode` option in the Xvnc man page for more details.
4. The default X startup script (`xstartup.turbovnc`) now throws an error.
Rather than trying to execute xinitrc or twm, if a session desktop file for
The default window manager cannot be found.
5. Configuration of the TurboVNC Viewer has been improved in the following.
Ways:
- Advanced param
Apache c vnc rdp remote-desktop 3d tightvnc cross-platform java
TurboVNC is a performance-oriented version of the VNC remote desktop connection protocol, based on TightVNC, x4vnc, TigerVNC, and X.org. It provides 3D rendering and VirtualGL compression, works well on video and image-intensive connections. It remains fully compatible to other implementations, but often requires less than a fifth processing power.
A Java-based VNC viewer is also available
minor feature: ===.
### Significant changes relative to 3.2 beta1:
1. a regression introduced by 3.0.3 7 that, under rare circumstances if.
Automatic desktop resizing was enabled, caused the viewer to deadlock while
Resizing its window in response to a remote desktop size change.
3.2 beta1.
### Significant changes relative to 3.1.4:
1. The TurboVNC Server now incorporates zlib-ng, which accelerates zlib.
Encoding significantly on x86, Arm, and PowerPC CPUs. Relative to TurboVNC
3.1.x, this improves the encoding performance of the Lossless Tight + Zlib
Encoding method, and of non-JPEG (low-color-depth) subrectangles encoded with
One of the Tight + JPEG encoding methods, by approximately 10-15 on reasonably
Modern x86-64 CPUs and 25-30 on reasonably modern AArch64 CPUs.
2. Since all supported TurboVNC host platforms now contain new enough libraries.
to build xorg-server 1.20.x, the TurboVNC Server is now dynamically linked
Against the system-supplied versions of these libraries rather than statically
Linked against in-tree versions. The `TVNC_SYSTEMLIBS` and `TVNC_SYSTEMX11`
CMake variables have been removed, and the build system now behaves as if those
Variables are always on. A new CMake variable (`TVNC_ZLIBNG`) can be used on
X86 platforms to disable the in-tree SIMD-accelerated zlib-ng implementation
And build against the system-supplied zlib implementation.
3. The TurboVNC Server now supports the DRI3 X extension when using open source.
GPU drivers. This enables GPU acceleration in a TurboVNC session without
VirtualGL, although the performance will be better with VirtualGL. Refer to
The description of the `-drinode` option in the Xvnc man page for more details.
4. The default X startup script (`xstartup.turbovnc`) now throws an error.
Rather than trying to execute xinitrc or twm, if a session desktop file for
The default window manager cannot be found.
5. Configuration of the TurboVNC Viewer has been improved in the following.
Ways:
- Advanced param
Apache c vnc rdp remote-desktop 3d tightvnc cross-platform java
TurboVNC is a performance-oriented version of the VNC remote desktop connection protocol, based on TightVNC, x4vnc, TigerVNC, and X.org. It provides 3D rendering and VirtualGL compression, works well on video and image-intensive connections. It remains fully compatible to other implementations, but often requires less than a fifth processing power.
A Java-based VNC viewer is also available
minor feature: ===.
### Significant changes relative to 3.2 beta1:
1. a regression introduced by 3.0.3 7 that, under rare circumstances if.
Automatic desktop resizing was enabled, caused the viewer to deadlock while
Resizing its window in response to a remote desktop size change.
3.2 beta1.
### Significant changes relative to 3.1.4:
1. The TurboVNC Server now incorporates zlib-ng, which accelerates zlib.
Encoding significantly on x86, Arm, and PowerPC CPUs. Relative to TurboVNC
3.1.x, this improves the encoding performance of the Lossless Tight + Zlib
Encoding method, and of non-JPEG (low-color-depth) subrectangles encoded with
One of the Tight + JPEG encoding methods, by approximately 10-15 on reasonably
Modern x86-64 CPUs and 25-30 on reasonably modern AArch64 CPUs.
2. Since all supported TurboVNC host platforms now contain new enough libraries.
to build xorg-server 1.20.x, the TurboVNC Server is now dynamically linked
Against the system-supplied versions of these libraries rather than statically
Linked against in-tree versions. The `TVNC_SYSTEMLIBS` and `TVNC_SYSTEMX11`
CMake variables have been removed, and the build system now behaves as if those
Variables are always on. A new CMake variable (`TVNC_ZLIBNG`) can be used on
X86 platforms to disable the in-tree SIMD-accelerated zlib-ng implementation
And build against the system-supplied zlib implementation.
3. The TurboVNC Server now supports the DRI3 X extension when using open source.
GPU drivers. This enables GPU acceleration in a TurboVNC session without
VirtualGL, although the performance will be better with VirtualGL. Refer to
The description of the `-drinode` option in the Xvnc man page for more details.
4. The default X startup script (`xstartup.turbovnc`) now throws an error.
Rather than trying to execute xinitrc or twm, if a session desktop file for
The default window manager cannot be found.
5. Configuration of the TurboVNC Viewer has been improved in the following.
Ways:
- Advanced param
Apache c vnc rdp remote-desktop 3d tightvnc cross-platform java
TurboVNC is a performance-oriented version of the VNC remote desktop connection protocol, based on TightVNC, x4vnc, TigerVNC, and X.org. It provides 3D rendering and VirtualGL compression, works well on video and image-intensive connections. It remains fully compatible to other implementations, but often requires less than a fifth processing power.
A Java-based VNC viewer is also available
minor feature: ===.
### Significant changes relative to 3.2 beta1:
1. a regression introduced by 3.0.3 7 that, under rare circumstances if.
Automatic desktop resizing was enabled, caused the viewer to deadlock while
Resizing its window in response to a remote desktop size change.
3.2 beta1.
### Significant changes relative to 3.1.4:
1. The TurboVNC Server now incorporates zlib-ng, which accelerates zlib.
Encoding significantly on x86, Arm, and PowerPC CPUs. Relative to TurboVNC
3.1.x, this improves the encoding performance of the Lossless Tight + Zlib
Encoding method, and of non-JPEG (low-color-depth) subrectangles encoded with
One of the Tight + JPEG encoding methods, by approximately 10-15 on reasonably
Modern x86-64 CPUs and 25-30 on reasonably modern AArch64 CPUs.
2. Since all supported TurboVNC host platforms now contain new enough libraries.
to build xorg-server 1.20.x, the TurboVNC Server is now dynamically linked
Against the system-supplied versions of these libraries rather than statically
Linked against in-tree versions. The `TVNC_SYSTEMLIBS` and `TVNC_SYSTEMX11`
CMake variables have been removed, and the build system now behaves as if those
Variables are always on. A new CMake variable (`TVNC_ZLIBNG`) can be used on
X86 platforms to disable the in-tree SIMD-accelerated zlib-ng implementation
And build against the system-supplied zlib implementation.
3. The TurboVNC Server now supports the DRI3 X extension when using open source.
GPU drivers. This enables GPU acceleration in a TurboVNC session without
VirtualGL, although the performance will be better with VirtualGL. Refer to
The description of the `-drinode` option in the Xvnc man page for more details.
4. The default X startup script (`xstartup.turbovnc`) now throws an error.
Rather than trying to execute xinitrc or twm, if a session desktop file for
The default window manager cannot be found.
5. Configuration of the TurboVNC Viewer has been improved in the following.
Ways:
- Advanced param
Apache c vnc rdp remote-desktop 3d tightvnc cross-platform java
TurboVNC is a performance-oriented version of the VNC remote desktop connection protocol, based on TightVNC, x4vnc, TigerVNC, and X.org. It provides 3D rendering and VirtualGL compression, works well on video and image-intensive connections. It remains fully compatible to other implementations, but often requires less than a fifth processing power.
A Java-based VNC viewer is also available
minor feature: ===.
### Significant changes relative to 3.2 beta1:
1. a regression introduced by 3.0.3 7 that, under rare circumstances if.
Automatic desktop resizing was enabled, caused the viewer to deadlock while
Resizing its window in response to a remote desktop size change.
3.2 beta1.
### Significant changes relative to 3.1.4:
1. The TurboVNC Server now incorporates zlib-ng, which accelerates zlib.
Encoding significantly on x86, Arm, and PowerPC CPUs. Relative to TurboVNC
3.1.x, this improves the encoding performance of the Lossless Tight + Zlib
Encoding method, and of non-JPEG (low-color-depth) subrectangles encoded with
One of the Tight + JPEG encoding methods, by approximately 10-15 on reasonably
Modern x86-64 CPUs and 25-30 on reasonably modern AArch64 CPUs.
2. Since all supported TurboVNC host platforms now contain new enough libraries.
to build xorg-server 1.20.x, the TurboVNC Server is now dynamically linked
Against the system-supplied versions of these libraries rather than statically
Linked against in-tree versions. The `TVNC_SYSTEMLIBS` and `TVNC_SYSTEMX11`
CMake variables have been removed, and the build system now behaves as if those
Variables are always on. A new CMake variable (`TVNC_ZLIBNG`) can be used on
X86 platforms to disable the in-tree SIMD-accelerated zlib-ng implementation
And build against the system-supplied zlib implementation.
3. The TurboVNC Server now supports the DRI3 X extension when using open source.
GPU drivers. This enables GPU acceleration in a TurboVNC session without
VirtualGL, although the performance will be better with VirtualGL. Refer to
The description of the `-drinode` option in the Xvnc man page for more details.
4. The default X startup script (`xstartup.turbovnc`) now throws an error.
Rather than trying to execute xinitrc or twm, if a session desktop file for
The default window manager cannot be found.
5. Configuration of the TurboVNC Viewer has been improved in the following.
Ways:
- Advanced param
Apache c vnc rdp remote-desktop 3d tightvnc cross-platform java
TurboVNC is a performance-oriented version of the VNC remote desktop connection protocol, based on TightVNC, x4vnc, TigerVNC, and X.org. It provides 3D rendering and VirtualGL compression, works well on video and image-intensive connections. It remains fully compatible to other implementations, but often requires less than a fifth processing power.
A Java-based VNC viewer is also available
minor feature: ===.
### Significant changes relative to 3.2 beta1:
1. a regression introduced by 3.0.3 7 that, under rare circumstances if.
Automatic desktop resizing was enabled, caused the viewer to deadlock while
Resizing its window in response to a remote desktop size change.
3.2 beta1.
### Significant changes relative to 3.1.4:
1. The TurboVNC Server now incorporates zlib-ng, which accelerates zlib.
Encoding significantly on x86, Arm, and PowerPC CPUs. Relative to TurboVNC
3.1.x, this improves the encoding performance of the Lossless Tight + Zlib
Encoding method, and of non-JPEG (low-color-depth) subrectangles encoded with
One of the Tight + JPEG encoding methods, by approximately 10-15 on reasonably
Modern x86-64 CPUs and 25-30 on reasonably modern AArch64 CPUs.
2. Since all supported TurboVNC host platforms now contain new enough libraries.
to build xorg-server 1.20.x, the TurboVNC Server is now dynamically linked
Against the system-supplied versions of these libraries rather than statically
Linked against in-tree versions. The `TVNC_SYSTEMLIBS` and `TVNC_SYSTEMX11`
CMake variables have been removed, and the build system now behaves as if those
Variables are always on. A new CMake variable (`TVNC_ZLIBNG`) can be used on
X86 platforms to disable the in-tree SIMD-accelerated zlib-ng implementation
And build against the system-supplied zlib implementation.
3. The TurboVNC Server now supports the DRI3 X extension when using open source.
GPU drivers. This enables GPU acceleration in a TurboVNC session without
VirtualGL, although the performance will be better with VirtualGL. Refer to
The description of the `-drinode` option in the Xvnc man page for more details.
4. The default X startup script (`xstartup.turbovnc`) now throws an error.
Rather than trying to execute xinitrc or twm, if a session desktop file for
The default window manager cannot be found.
5. Configuration of the TurboVNC Viewer has been improved in the following.
Ways:
- Advanced param
Apache c vnc rdp remote-desktop 3d tightvnc cross-platform java
TurboVNC is a performance-oriented version of the VNC remote desktop connection protocol, based on TightVNC, x4vnc, TigerVNC, and X.org. It provides 3D rendering and VirtualGL compression, works well on video and image-intensive connections. It remains fully compatible to other implementations, but often requires less than a fifth processing power.
A Java-based VNC viewer is also available
minor feature: ===.
### Significant changes relative to 3.2 beta1:
1. a regression introduced by 3.0.3 7 that, under rare circumstances if.
Automatic desktop resizing was enabled, caused the viewer to deadlock while
Resizing its window in response to a remote desktop size change.
3.2 beta1.
### Significant changes relative to 3.1.4:
1. The TurboVNC Server now incorporates zlib-ng, which accelerates zlib.
Encoding significantly on x86, Arm, and PowerPC CPUs. Relative to TurboVNC
3.1.x, this improves the encoding performance of the Lossless Tight + Zlib
Encoding method, and of non-JPEG (low-color-depth) subrectangles encoded with
One of the Tight + JPEG encoding methods, by approximately 10-15 on reasonably
Modern x86-64 CPUs and 25-30 on reasonably modern AArch64 CPUs.
2. Since all supported TurboVNC host platforms now contain new enough libraries.
to build xorg-server 1.20.x, the TurboVNC Server is now dynamically linked
Against the system-supplied versions of these libraries rather than statically
Linked against in-tree versions. The `TVNC_SYSTEMLIBS` and `TVNC_SYSTEMX11`
CMake variables have been removed, and the build system now behaves as if those
Variables are always on. A new CMake variable (`TVNC_ZLIBNG`) can be used on
X86 platforms to disable the in-tree SIMD-accelerated zlib-ng implementation
And build against the system-supplied zlib implementation.
3. The TurboVNC Server now supports the DRI3 X extension when using open source.
GPU drivers. This enables GPU acceleration in a TurboVNC session without
VirtualGL, although the performance will be better with VirtualGL. Refer to
The description of the `-drinode` option in the Xvnc man page for more details.
4. The default X startup script (`xstartup.turbovnc`) now throws an error.
Rather than trying to execute xinitrc or twm, if a session desktop file for
The default window manager cannot be found.
5. Configuration of the TurboVNC Viewer has been improved in the following.
Ways:
- Advanced param
Apache c vnc rdp remote-desktop 3d tightvnc cross-platform java
TurboVNC is a performance-oriented version of the VNC remote desktop connection protocol, based on TightVNC, x4vnc, TigerVNC, and X.org. It provides 3D rendering and VirtualGL compression, works well on video and image-intensive connections. It remains fully compatible to other implementations, but often requires less than a fifth processing power.
A Java-based VNC viewer is also available
minor feature: ===.
### Significant changes relative to 3.2 beta1:
1. a regression introduced by 3.0.3 7 that, under rare circumstances if.
Automatic desktop resizing was enabled, caused the viewer to deadlock while
Resizing its window in response to a remote desktop size change.
3.2 beta1.
### Significant changes relative to 3.1.4:
1. The TurboVNC Server now incorporates zlib-ng, which accelerates zlib.
Encoding significantly on x86, Arm, and PowerPC CPUs. Relative to TurboVNC
3.1.x, this improves the encoding performance of the Lossless Tight + Zlib
Encoding method, and of non-JPEG (low-color-depth) subrectangles encoded with
One of the Tight + JPEG encoding methods, by approximately 10-15 on reasonably
Modern x86-64 CPUs and 25-30 on reasonably modern AArch64 CPUs.
2. Since all supported TurboVNC host platforms now contain new enough libraries.
to build xorg-server 1.20.x, the TurboVNC Server is now dynamically linked
Against the system-supplied versions of these libraries rather than statically
Linked against in-tree versions. The `TVNC_SYSTEMLIBS` and `TVNC_SYSTEMX11`
CMake variables have been removed, and the build system now behaves as if those
Variables are always on. A new CMake variable (`TVNC_ZLIBNG`) can be used on
X86 platforms to disable the in-tree SIMD-accelerated zlib-ng implementation
And build against the system-supplied zlib implementation.
3. The TurboVNC Server now supports the DRI3 X extension when using open source.
GPU drivers. This enables GPU acceleration in a TurboVNC session without
VirtualGL, although the performance will be better with VirtualGL. Refer to
The description of the `-drinode` option in the Xvnc man page for more details.
4. The default X startup script (`xstartup.turbovnc`) now throws an error.
Rather than trying to execute xinitrc or twm, if a session desktop file for
The default window manager cannot be found.
5. Configuration of the TurboVNC Viewer has been improved in the following.
Ways:
- Advanced param
Apache c vnc rdp remote-desktop 3d tightvnc cross-platform java
TurboVNC is a performance-oriented version of the VNC remote desktop connection protocol, based on TightVNC, x4vnc, TigerVNC, and X.org. It provides 3D rendering and VirtualGL compression, works well on video and image-intensive connections. It remains fully compatible to other implementations, but often requires less than a fifth processing power.
A Java-based VNC viewer is also available
minor feature: ===.
### Significant changes relative to 3.2 beta1:
1. a regression introduced by 3.0.3 7 that, under rare circumstances if.
Automatic desktop resizing was enabled, caused the viewer to deadlock while
Resizing its window in response to a remote desktop size change.
3.2 beta1.
### Significant changes relative to 3.1.4:
1. The TurboVNC Server now incorporates zlib-ng, which accelerates zlib.
Encoding significantly on x86, Arm, and PowerPC CPUs. Relative to TurboVNC
3.1.x, this improves the encoding performance of the Lossless Tight + Zlib
Encoding method, and of non-JPEG (low-color-depth) subrectangles encoded with
One of the Tight + JPEG encoding methods, by approximately 10-15 on reasonably
Modern x86-64 CPUs and 25-30 on reasonably modern AArch64 CPUs.
2. Since all supported TurboVNC host platforms now contain new enough libraries.
to build xorg-server 1.20.x, the TurboVNC Server is now dynamically linked
Against the system-supplied versions of these libraries rather than statically
Linked against in-tree versions. The `TVNC_SYSTEMLIBS` and `TVNC_SYSTEMX11`
CMake variables have been removed, and the build system now behaves as if those
Variables are always on. A new CMake variable (`TVNC_ZLIBNG`) can be used on
X86 platforms to disable the in-tree SIMD-accelerated zlib-ng implementation
And build against the system-supplied zlib implementation.
3. The TurboVNC Server now supports the DRI3 X extension when using open source.
GPU drivers. This enables GPU acceleration in a TurboVNC session without
VirtualGL, although the performance will be better with VirtualGL. Refer to
The description of the `-drinode` option in the Xvnc man page for more details.
4. The default X startup script (`xstartup.turbovnc`) now throws an error.
Rather than trying to execute xinitrc or twm, if a session desktop file for
The default window manager cannot be found.
5. Configuration of the TurboVNC Viewer has been improved in the following.
Ways:
- Advanced param
Apache c vnc rdp remote-desktop 3d tightvnc cross-platform java
TurboVNC is a performance-oriented version of the VNC remote desktop connection protocol, based on TightVNC, x4vnc, TigerVNC, and X.org. It provides 3D rendering and VirtualGL compression, works well on video and image-intensive connections. It remains fully compatible to other implementations, but often requires less than a fifth processing power.
A Java-based VNC viewer is also available
minor feature: ===.
### Significant changes relative to 3.2 beta1:
1. a regression introduced by 3.0.3 7 that, under rare circumstances if.
Automatic desktop resizing was enabled, caused the viewer to deadlock while
Resizing its window in response to a remote desktop size change.
3.2 beta1.
### Significant changes relative to 3.1.4:
1. The TurboVNC Server now incorporates zlib-ng, which accelerates zlib.
Encoding significantly on x86, Arm, and PowerPC CPUs. Relative to TurboVNC
3.1.x, this improves the encoding performance of the Lossless Tight + Zlib
Encoding method, and of non-JPEG (low-color-depth) subrectangles encoded with
One of the Tight + JPEG encoding methods, by approximately 10-15 on reasonably
Modern x86-64 CPUs and 25-30 on reasonably modern AArch64 CPUs.
2. Since all supported TurboVNC host platforms now contain new enough libraries.
to build xorg-server 1.20.x, the TurboVNC Server is now dynamically linked
Against the system-supplied versions of these libraries rather than statically
Linked against in-tree versions. The `TVNC_SYSTEMLIBS` and `TVNC_SYSTEMX11`
CMake variables have been removed, and the build system now behaves as if those
Variables are always on. A new CMake variable (`TVNC_ZLIBNG`) can be used on
X86 platforms to disable the in-tree SIMD-accelerated zlib-ng implementation
And build against the system-supplied zlib implementation.
3. The TurboVNC Server now supports the DRI3 X extension when using open source.
GPU drivers. This enables GPU acceleration in a TurboVNC session without
VirtualGL, although the performance will be better with VirtualGL. Refer to
The description of the `-drinode` option in the Xvnc man page for more details.
4. The default X startup script (`xstartup.turbovnc`) now throws an error.
Rather than trying to execute xinitrc or twm, if a session desktop file for
The default window manager cannot be found.
5. Configuration of the TurboVNC Viewer has been improved in the following.
Ways:
- Advanced param
Apache c vnc rdp remote-desktop 3d tightvnc cross-platform java
TurboVNC is a performance-oriented version of the VNC remote desktop connection protocol, based on TightVNC, x4vnc, TigerVNC, and X.org. It provides 3D rendering and VirtualGL compression, works well on video and image-intensive connections. It remains fully compatible to other implementations, but often requires less than a fifth processing power.
A Java-based VNC viewer is also available
minor feature: ===.
### Significant changes relative to 3.2 beta1:
1. a regression introduced by 3.0.3 7 that, under rare circumstances if.
Automatic desktop resizing was enabled, caused the viewer to deadlock while
Resizing its window in response to a remote desktop size change.
3.2 beta1.
### Significant changes relative to 3.1.4:
1. The TurboVNC Server now incorporates zlib-ng, which accelerates zlib.
Encoding significantly on x86, Arm, and PowerPC CPUs. Relative to TurboVNC
3.1.x, this improves the encoding performance of the Lossless Tight + Zlib
Encoding method, and of non-JPEG (low-color-depth) subrectangles encoded with
One of the Tight + JPEG encoding methods, by approximately 10-15 on reasonably
Modern x86-64 CPUs and 25-30 on reasonably modern AArch64 CPUs.
2. Since all supported TurboVNC host platforms now contain new enough libraries.
to build xorg-server 1.20.x, the TurboVNC Server is now dynamically linked
Against the system-supplied versions of these libraries rather than statically
Linked against in-tree versions. The `TVNC_SYSTEMLIBS` and `TVNC_SYSTEMX11`
CMake variables have been removed, and the build system now behaves as if those
Variables are always on. A new CMake variable (`TVNC_ZLIBNG`) can be used on
X86 platforms to disable the in-tree SIMD-accelerated zlib-ng implementation
And build against the system-supplied zlib implementation.
3. The TurboVNC Server now supports the DRI3 X extension when using open source.
GPU drivers. This enables GPU acceleration in a TurboVNC session without
VirtualGL, although the performance will be better with VirtualGL. Refer to
The description of the `-drinode` option in the Xvnc man page for more details.
4. The default X startup script (`xstartup.turbovnc`) now throws an error.
Rather than trying to execute xinitrc or twm, if a session desktop file for
The default window manager cannot be found.
5. Configuration of the TurboVNC Viewer has been improved in the following.
Ways:
- Advanced param
Apache c vnc rdp remote-desktop 3d tightvnc cross-platform java
TurboVNC is a performance-oriented version of the VNC remote desktop connection protocol, based on TightVNC, x4vnc, TigerVNC, and X.org. It provides 3D rendering and VirtualGL compression, works well on video and image-intensive connections. It remains fully compatible to other implementations, but often requires less than a fifth processing power.
A Java-based VNC viewer is also available
minor feature: ===.
### Significant changes relative to 3.2 beta1:
1. a regression introduced by 3.0.3 7 that, under rare circumstances if.
Automatic desktop resizing was enabled, caused the viewer to deadlock while
Resizing its window in response to a remote desktop size change.
3.2 beta1.
### Significant changes relative to 3.1.4:
1. The TurboVNC Server now incorporates zlib-ng, which accelerates zlib.
Encoding significantly on x86, Arm, and PowerPC CPUs. Relative to TurboVNC
3.1.x, this improves the encoding performance of the Lossless Tight + Zlib
Encoding method, and of non-JPEG (low-color-depth) subrectangles encoded with
One of the Tight + JPEG encoding methods, by approximately 10-15 on reasonably
Modern x86-64 CPUs and 25-30 on reasonably modern AArch64 CPUs.
2. Since all supported TurboVNC host platforms now contain new enough libraries.
to build xorg-server 1.20.x, the TurboVNC Server is now dynamically linked
Against the system-supplied versions of these libraries rather than statically
Linked against in-tree versions. The `TVNC_SYSTEMLIBS` and `TVNC_SYSTEMX11`
CMake variables have been removed, and the build system now behaves as if those
Variables are always on. A new CMake variable (`TVNC_ZLIBNG`) can be used on
X86 platforms to disable the in-tree SIMD-accelerated zlib-ng implementation
And build against the system-supplied zlib implementation.
3. The TurboVNC Server now supports the DRI3 X extension when using open source.
GPU drivers. This enables GPU acceleration in a TurboVNC session without
VirtualGL, although the performance will be better with VirtualGL. Refer to
The description of the `-drinode` option in the Xvnc man page for more details.
4. The default X startup script (`xstartup.turbovnc`) now throws an error.
Rather than trying to execute xinitrc or twm, if a session desktop file for
The default window manager cannot be found.
5. Configuration of the TurboVNC Viewer has been improved in the following.
Ways:
- Advanced param
Apache c vnc rdp remote-desktop 3d tightvnc cross-platform java
TurboVNC is a performance-oriented version of the VNC remote desktop connection protocol, based on TightVNC, x4vnc, TigerVNC, and X.org. It provides 3D rendering and VirtualGL compression, works well on video and image-intensive connections. It remains fully compatible to other implementations, but often requires less than a fifth processing power.
A Java-based VNC viewer is also available
minor feature: ===.
### Significant changes relative to 3.2 beta1:
1. a regression introduced by 3.0.3 7 that, under rare circumstances if.
Automatic desktop resizing was enabled, caused the viewer to deadlock while
Resizing its window in response to a remote desktop size change.
3.2 beta1.
### Significant changes relative to 3.1.4:
1. The TurboVNC Server now incorporates zlib-ng, which accelerates zlib.
Encoding significantly on x86, Arm, and PowerPC CPUs. Relative to TurboVNC
3.1.x, this improves the encoding performance of the Lossless Tight + Zlib
Encoding method, and of non-JPEG (low-color-depth) subrectangles encoded with
One of the Tight + JPEG encoding methods, by approximately 10-15 on reasonably
Modern x86-64 CPUs and 25-30 on reasonably modern AArch64 CPUs.
2. Since all supported TurboVNC host platforms now contain new enough libraries.
to build xorg-server 1.20.x, the TurboVNC Server is now dynamically linked
Against the system-supplied versions of these libraries rather than statically
Linked against in-tree versions. The `TVNC_SYSTEMLIBS` and `TVNC_SYSTEMX11`
CMake variables have been removed, and the build system now behaves as if those
Variables are always on. A new CMake variable (`TVNC_ZLIBNG`) can be used on
X86 platforms to disable the in-tree SIMD-accelerated zlib-ng implementation
And build against the system-supplied zlib implementation.
3. The TurboVNC Server now supports the DRI3 X extension when using open source.
GPU drivers. This enables GPU acceleration in a TurboVNC session without
VirtualGL, although the performance will be better with VirtualGL. Refer to
The description of the `-drinode` option in the Xvnc man page for more details.
4. The default X startup script (`xstartup.turbovnc`) now throws an error.
Rather than trying to execute xinitrc or twm, if a session desktop file for
The default window manager cannot be found.
5. Configuration of the TurboVNC Viewer has been improved in the following.
Ways:
- Advanced param
Apache c vnc rdp remote-desktop 3d tightvnc cross-platform java
TurboVNC is a performance-oriented version of the VNC remote desktop connection protocol, based on TightVNC, x4vnc, TigerVNC, and X.org. It provides 3D rendering and VirtualGL compression, works well on video and image-intensive connections. It remains fully compatible to other implementations, but often requires less than a fifth processing power.
A Java-based VNC viewer is also available
minor feature: ===.
### Significant changes relative to 3.2 beta1:
1. a regression introduced by 3.0.3 7 that, under rare circumstances if.
Automatic desktop resizing was enabled, caused the viewer to deadlock while
Resizing its window in response to a remote desktop size change.
3.2 beta1.
### Significant changes relative to 3.1.4:
1. The TurboVNC Server now incorporates zlib-ng, which accelerates zlib.
Encoding significantly on x86, Arm, and PowerPC CPUs. Relative to TurboVNC
3.1.x, this improves the encoding performance of the Lossless Tight + Zlib
Encoding method, and of non-JPEG (low-color-depth) subrectangles encoded with
One of the Tight + JPEG encoding methods, by approximately 10-15 on reasonably
Modern x86-64 CPUs and 25-30 on reasonably modern AArch64 CPUs.
2. Since all supported TurboVNC host platforms now contain new enough libraries.
to build xorg-server 1.20.x, the TurboVNC Server is now dynamically linked
Against the system-supplied versions of these libraries rather than statically
Linked against in-tree versions. The `TVNC_SYSTEMLIBS` and `TVNC_SYSTEMX11`
CMake variables have been removed, and the build system now behaves as if those
Variables are always on. A new CMake variable (`TVNC_ZLIBNG`) can be used on
X86 platforms to disable the in-tree SIMD-accelerated zlib-ng implementation
And build against the system-supplied zlib implementation.
3. The TurboVNC Server now supports the DRI3 X extension when using open source.
GPU drivers. This enables GPU acceleration in a TurboVNC session without
VirtualGL, although the performance will be better with VirtualGL. Refer to
The description of the `-drinode` option in the Xvnc man page for more details.
4. The default X startup script (`xstartup.turbovnc`) now throws an error.
Rather than trying to execute xinitrc or twm, if a session desktop file for
The default window manager cannot be found.
5. Configuration of the TurboVNC Viewer has been improved in the following.
Ways:
- Advanced param
Apache c vnc rdp remote-desktop 3d tightvnc cross-platform java
TurboVNC is a performance-oriented version of the VNC remote desktop connection protocol, based on TightVNC, x4vnc, TigerVNC, and X.org. It provides 3D rendering and VirtualGL compression, works well on video and image-intensive connections. It remains fully compatible to other implementations, but often requires less than a fifth processing power.
A Java-based VNC viewer is also available
minor feature: ===.
### Significant changes relative to 3.2 beta1:
1. a regression introduced by 3.0.3 7 that, under rare circumstances if.
Automatic desktop resizing was enabled, caused the viewer to deadlock while
Resizing its window in response to a remote desktop size change.
3.2 beta1.
### Significant changes relative to 3.1.4:
1. The TurboVNC Server now incorporates zlib-ng, which accelerates zlib.
Encoding significantly on x86, Arm, and PowerPC CPUs. Relative to TurboVNC
3.1.x, this improves the encoding performance of the Lossless Tight + Zlib
Encoding method, and of non-JPEG (low-color-depth) subrectangles encoded with
One of the Tight + JPEG encoding methods, by approximately 10-15 on reasonably
Modern x86-64 CPUs and 25-30 on reasonably modern AArch64 CPUs.
2. Since all supported TurboVNC host platforms now contain new enough libraries.
to build xorg-server 1.20.x, the TurboVNC Server is now dynamically linked
Against the system-supplied versions of these libraries rather than statically
Linked against in-tree versions. The `TVNC_SYSTEMLIBS` and `TVNC_SYSTEMX11`
CMake variables have been removed, and the build system now behaves as if those
Variables are always on. A new CMake variable (`TVNC_ZLIBNG`) can be used on
X86 platforms to disable the in-tree SIMD-accelerated zlib-ng implementation
And build against the system-supplied zlib implementation.
3. The TurboVNC Server now supports the DRI3 X extension when using open source.
GPU drivers. This enables GPU acceleration in a TurboVNC session without
VirtualGL, although the performance will be better with VirtualGL. Refer to
The description of the `-drinode` option in the Xvnc man page for more details.
4. The default X startup script (`xstartup.turbovnc`) now throws an error.
Rather than trying to execute xinitrc or twm, if a session desktop file for
The default window manager cannot be found.
5. Configuration of the TurboVNC Viewer has been improved in the following.
Ways:
- Advanced param
Apache c vnc rdp remote-desktop 3d tightvnc cross-platform java
TurboVNC is a performance-oriented version of the VNC remote desktop connection protocol, based on TightVNC, x4vnc, TigerVNC, and X.org. It provides 3D rendering and VirtualGL compression, works well on video and image-intensive connections. It remains fully compatible to other implementations, but often requires less than a fifth processing power.
A Java-based VNC viewer is also available
minor feature: ===.
### Significant changes relative to 3.2 beta1:
1. a regression introduced by 3.0.3 7 that, under rare circumstances if.
Automatic desktop resizing was enabled, caused the viewer to deadlock while
Resizing its window in response to a remote desktop size change.
3.2 beta1.
### Significant changes relative to 3.1.4:
1. The TurboVNC Server now incorporates zlib-ng, which accelerates zlib.
Encoding significantly on x86, Arm, and PowerPC CPUs. Relative to TurboVNC
3.1.x, this improves the encoding performance of the Lossless Tight + Zlib
Encoding method, and of non-JPEG (low-color-depth) subrectangles encoded with
One of the Tight + JPEG encoding methods, by approximately 10-15 on reasonably
Modern x86-64 CPUs and 25-30 on reasonably modern AArch64 CPUs.
2. Since all supported TurboVNC host platforms now contain new enough libraries.
to build xorg-server 1.20.x, the TurboVNC Server is now dynamically linked
Against the system-supplied versions of these libraries rather than statically
Linked against in-tree versions. The `TVNC_SYSTEMLIBS` and `TVNC_SYSTEMX11`
CMake variables have been removed, and the build system now behaves as if those
Variables are always on. A new CMake variable (`TVNC_ZLIBNG`) can be used on
X86 platforms to disable the in-tree SIMD-accelerated zlib-ng implementation
And build against the system-supplied zlib implementation.
3. The TurboVNC Server now supports the DRI3 X extension when using open source.
GPU drivers. This enables GPU acceleration in a TurboVNC session without
VirtualGL, although the performance will be better with VirtualGL. Refer to
The description of the `-drinode` option in the Xvnc man page for more details.
4. The default X startup script (`xstartup.turbovnc`) now throws an error.
Rather than trying to execute xinitrc or twm, if a session desktop file for
The default window manager cannot be found.
5. Configuration of the TurboVNC Viewer has been improved in the following.
Ways:
- Advanced param
Apache c vnc rdp remote-desktop 3d tightvnc cross-platform java
TurboVNC is a performance-oriented version of the VNC remote desktop connection protocol, based on TightVNC, x4vnc, TigerVNC, and X.org. It provides 3D rendering and VirtualGL compression, works well on video and image-intensive connections. It remains fully compatible to other implementations, but often requires less than a fifth processing power.
A Java-based VNC viewer is also available
minor feature: ===.
### Significant changes relative to 3.2 beta1:
1. a regression introduced by 3.0.3 7 that, under rare circumstances if.
Automatic desktop resizing was enabled, caused the viewer to deadlock while
Resizing its window in response to a remote desktop size change.
3.2 beta1.
### Significant changes relative to 3.1.4:
1. The TurboVNC Server now incorporates zlib-ng, which accelerates zlib.
Encoding significantly on x86, Arm, and PowerPC CPUs. Relative to TurboVNC
3.1.x, this improves the encoding performance of the Lossless Tight + Zlib
Encoding method, and of non-JPEG (low-color-depth) subrectangles encoded with
One of the Tight + JPEG encoding methods, by approximately 10-15 on reasonably
Modern x86-64 CPUs and 25-30 on reasonably modern AArch64 CPUs.
2. Since all supported TurboVNC host platforms now contain new enough libraries.
to build xorg-server 1.20.x, the TurboVNC Server is now dynamically linked
Against the system-supplied versions of these libraries rather than statically
Linked against in-tree versions. The `TVNC_SYSTEMLIBS` and `TVNC_SYSTEMX11`
CMake variables have been removed, and the build system now behaves as if those
Variables are always on. A new CMake variable (`TVNC_ZLIBNG`) can be used on
X86 platforms to disable the in-tree SIMD-accelerated zlib-ng implementation
And build against the system-supplied zlib implementation.
3. The TurboVNC Server now supports the DRI3 X extension when using open source.
GPU drivers. This enables GPU acceleration in a TurboVNC session without
VirtualGL, although the performance will be better with VirtualGL. Refer to
The description of the `-drinode` option in the Xvnc man page for more details.
4. The default X startup script (`xstartup.turbovnc`) now throws an error.
Rather than trying to execute xinitrc or twm, if a session desktop file for
The default window manager cannot be found.
5. Configuration of the TurboVNC Viewer has been improved in the following.
Ways:
- Advanced param
Apache c vnc rdp remote-desktop 3d tightvnc cross-platform java
TurboVNC is a performance-oriented version of the VNC remote desktop connection protocol, based on TightVNC, x4vnc, TigerVNC, and X.org. It provides 3D rendering and VirtualGL compression, works well on video and image-intensive connections. It remains fully compatible to other implementations, but often requires less than a fifth processing power.
A Java-based VNC viewer is also available
minor feature: ===.
### Significant changes relative to 3.2 beta1:
1. a regression introduced by 3.0.3 7 that, under rare circumstances if.
Automatic desktop resizing was enabled, caused the viewer to deadlock while
Resizing its window in response to a remote desktop size change.
3.2 beta1.
### Significant changes relative to 3.1.4:
1. The TurboVNC Server now incorporates zlib-ng, which accelerates zlib.
Encoding significantly on x86, Arm, and PowerPC CPUs. Relative to TurboVNC
3.1.x, this improves the encoding performance of the Lossless Tight + Zlib
Encoding method, and of non-JPEG (low-color-depth) subrectangles encoded with
One of the Tight + JPEG encoding methods, by approximately 10-15 on reasonably
Modern x86-64 CPUs and 25-30 on reasonably modern AArch64 CPUs.
2. Since all supported TurboVNC host platforms now contain new enough libraries.
to build xorg-server 1.20.x, the TurboVNC Server is now dynamically linked
Against the system-supplied versions of these libraries rather than statically
Linked against in-tree versions. The `TVNC_SYSTEMLIBS` and `TVNC_SYSTEMX11`
CMake variables have been removed, and the build system now behaves as if those
Variables are always on. A new CMake variable (`TVNC_ZLIBNG`) can be used on
X86 platforms to disable the in-tree SIMD-accelerated zlib-ng implementation
And build against the system-supplied zlib implementation.
3. The TurboVNC Server now supports the DRI3 X extension when using open source.
GPU drivers. This enables GPU acceleration in a TurboVNC session without
VirtualGL, although the performance will be better with VirtualGL. Refer to
The description of the `-drinode` option in the Xvnc man page for more details.
4. The default X startup script (`xstartup.turbovnc`) now throws an error.
Rather than trying to execute xinitrc or twm, if a session desktop file for
The default window manager cannot be found.
5. Configuration of the TurboVNC Viewer has been improved in the following.
Ways:
- Advanced param
Apache c vnc rdp remote-desktop 3d tightvnc cross-platform java
The qBittorrent project aims to provide an open-source software alternative to µTorrent.
Additionally, qBittorrent runs and provides the same features on all major platforms (Linux, Mac OS X, Windows, OS/2, FreeBSD).
qBittorrent is based on the Qt toolkit and libtorrent-rasterbar library.
minor feature: cannot remove trackers via WebAPI (Chocobo1). : torrent content checkbox state under certain conditions (thalieht). : Hide zero and infinity values in peer list only when that setting is set to. Always (thalieht). : Remove stopped torrent from "error" tracker filter (glassez). WEBUI: memory leak in context menus (skomerko). WEBAPI: Don't trim string parameters (glassez). WINDOWS: Handle Qt style options uniformly (glassez). WINDOWS: NSIS: Update Portuguese translation (Hugo Carvalho). MACOS: Avoid memory leak (Chocobo1).
Apache internet download torrent bittorent file-sharing cpp javascript html python qt
The qBittorrent project aims to provide an open-source software alternative to µTorrent.
Additionally, qBittorrent runs and provides the same features on all major platforms (Linux, Mac OS X, Windows, OS/2, FreeBSD).
qBittorrent is based on the Qt toolkit and libtorrent-rasterbar library.
minor feature: cannot remove trackers via WebAPI (Chocobo1). : torrent content checkbox state under certain conditions (thalieht). : Hide zero and infinity values in peer list only when that setting is set to. Always (thalieht). : Remove stopped torrent from "error" tracker filter (glassez). WEBUI: memory leak in context menus (skomerko). WEBAPI: Don't trim string parameters (glassez). WINDOWS: Handle Qt style options uniformly (glassez). WINDOWS: NSIS: Update Portuguese translation (Hugo Carvalho). MACOS: Avoid memory leak (Chocobo1).
Artistic internet download torrent bittorent file-sharing cpp javascript html python qt
The qBittorrent project aims to provide an open-source software alternative to µTorrent.
Additionally, qBittorrent runs and provides the same features on all major platforms (Linux, Mac OS X, Windows, OS/2, FreeBSD).
qBittorrent is based on the Qt toolkit and libtorrent-rasterbar library.
minor feature: cannot remove trackers via WebAPI (Chocobo1). : torrent content checkbox state under certain conditions (thalieht). : Hide zero and infinity values in peer list only when that setting is set to. Always (thalieht). : Remove stopped torrent from "error" tracker filter (glassez). WEBUI: memory leak in context menus (skomerko). WEBAPI: Don't trim string parameters (glassez). WINDOWS: Handle Qt style options uniformly (glassez). WINDOWS: NSIS: Update Portuguese translation (Hugo Carvalho). MACOS: Avoid memory leak (Chocobo1).
Apache internet download torrent bittorent file-sharing cpp javascript html python qt
The qBittorrent project aims to provide an open-source software alternative to µTorrent.
Additionally, qBittorrent runs and provides the same features on all major platforms (Linux, Mac OS X, Windows, OS/2, FreeBSD).
qBittorrent is based on the Qt toolkit and libtorrent-rasterbar library.
minor feature: cannot remove trackers via WebAPI (Chocobo1). : torrent content checkbox state under certain conditions (thalieht). : Hide zero and infinity values in peer list only when that setting is set to. Always (thalieht). : Remove stopped torrent from "error" tracker filter (glassez). WEBUI: memory leak in context menus (skomerko). WEBAPI: Don't trim string parameters (glassez). WINDOWS: Handle Qt style options uniformly (glassez). WINDOWS: NSIS: Update Portuguese translation (Hugo Carvalho). MACOS: Avoid memory leak (Chocobo1).
Artistic internet download torrent bittorent file-sharing cpp javascript html python qt
|
