P5 Changelog

What's new in P5 7.2.1

Feb 19, 2024

Assure S3 bucket idle timer is always honoured.
Fixed container online retrieval for Glacier/Deep-Archive restore.
Fixed handling timeouts for filewalker. (Bug#1936)
Fixed pool in use error. (Bug#1935)

New in P5 7.1.7 (Nov 24, 2023)

New in P5 7.1.6 (Aug 7, 2023)

New in P5 7.1.5 (May 27, 2023)

New in P5 7.1.4 (Mar 6, 2023)

New in P5 7.1.3 (Jan 17, 2023)

New in P5 7.1.2 (Dec 12, 2022)

New in P5 7.1.1 (Nov 22, 2022)

New in P5 7.1.0 (Sep 21, 2022)

New in P5 7.0.7 (Jun 7, 2022)

New in P5 7.0.6 (Dec 20, 2021)

New in P5 7.0.5 (Nov 16, 2021)

New in P5 7.0.4 (Oct 8, 2021)

New in P5 7.0.3 (Sep 13, 2021)

New in P5 7.0.2 (Aug 9, 2021)

New in P5 7.0.1 (Jul 24, 2021)

New in P5 7.0.0 (Jul 20, 2021)

NEW 'CONTAINER' STORAGE ENGINE FOR DISK AND CLOUD:
A real milestone in the evolution of P5, this brand new storage format, moving away from the virtual tape concept, multiple volumes are now replaced with single 'Storage Containers' in order to access disk and cloud storage. These containers are elastic, growing in size to accommodate data as needed, and optimized for interacting against cloud object storage.
They support multiple write/read streams in parallel without compromising performance. Additionally, they support fine-grained recycling of backup data over time, resulting in best-of-breed backup to cloud with cost saving through lower cloud storage space usage. Full details available here.
Simplified & Improved Storage Management:
The administration required to configure disk and cloud storage is now much reduced, with a tab based storage manager consolidating tape, disk and cloud storage setup in one place.
Bare-Metal Recovery Fully Supported for Disk/Cloud:
When using new container volumes, all P5 setup/config and backup indexes are automatically stored on disk/cloud with every job that runs. Full recovery of P5 server from disk/cloud storage now just a few clicks in the GUI.
A tab-based storage manager consolidates tape, disk and cloud storage setup in one place.
Fully recover the P5 server from disk/cloud storage within a few clicks.
Minimal Local 'Cache' Storage Usage When Writing to Cloud:
Backup and archive to cloud object storage will now require a small fraction of the disk space previously required. Local disk space used only for preparation of data for upload.
Space is freed up at first opportunity for both writing and reading to cloud storage.
Enhanced compression with LZ4:
P5 now uses this modern compression algorithm when writing to disk/cloud storage, resulting in smaller sizes, faster performance and less cloud storage being used. 2x 3x compression benefit.
Improved S3 Glacier/Deep Archive Support:
When archiving or backing up to S3, the 'Deep Archive' option is now fully supported. When restoring data, P5 will request all required objects at once and wait for cloud objects to become available.
P5 ARCHIVE:
Import of Foreign LTFS Volumes:
This feature brings huge benefits for users with data stored on LTFS tapes. Manage LTFS tapes by importing them into P5 Archive, they will appear in the index of your choice, with full search across all volumes. Supports LTFS tapes written by P5 or 3rd party LTFS software. P5 will scan LTFS tape volumes, and add contents to the P5 archive index, data can then be restored across multiple tapes via the archive index. Supports tape libraries for import across multiple slots.
Easier Use of Cloud-Vendors Data-Transport Devices:
When seeding archive data using an AWS Snowball, B2 Fireball or similar, P5 now provides a checkbox to suppress writing of data to the cloud object store directly. This removes previous attach/detach workflow and simplifies use of these devices.
LTFS Exchange Support on All Platforms:
Simple formatting, reading and writing of LTFS volumes for import/export now available on all our supported P5 platforms, including MS Windows and FreeBSD.
Very Fast Verification of Written Data:
Using xxHash 64 and 128-bit algorithms. Speeds up verification using checksums by 3x.
Saved Searches in Mini-MAM:
When switching between search results in the archive index and browsing, previously executed search is retained, easing location of the data you're looking for. Previous 10 searches available from drop-down menu.
Locate saved searches using P5 Archive's mini-MAM archive.
P5 BACKUP:
True Incremental Cloud Backup:
Full backups are no longer necessary when writing to cloud and disk storage. With P5 version 7, full backups are only required when writing to tape, to allow whole LTO tapes to be recycled and reused. When writing to cloud/disk storage using our new container volume storage, we have fine-grained removal of expired files and re-use of storage. The 'progressive' backup technique can be used indefinitely, resulting in faster and more efficient backup to cloud object storage.
Perform Dry-Run of a Backup:
P5 will compare storage to be backed up with index and report total number of new/changed/moved files. Allows anticipation of the length of the required backup window and number of tapes/storage that will be required for the backup to complete.
Limit Backup Size on Target Storage:
P5 Version 7 introduces a new option to limit the backup size on the target. This can be used to create a limited backup on a transfer appliance, such as Amazon Snowball, Backblaze Fireball or Wasabi Ball. This is necessary if the total backup size is more than one unit on the transfer appliance.
Rename Detection:
Track renamed folders without re-save of contents:
P5 Backup is now able to identify renamed folders with unchanged files inside and update index with new folder position without necessitating re-saving of files/folders contained within.
For example, if a top-level folder on a piece of storage were to be renamed, we avoid needing to re-save potentially many TB's inside, saving time and storage costs.
Perform a dry run of a backup.
Track renamed folders without re-save of contents.
P5 SYNCHRONIZE:
SCHEDULED SPEED THROTTLING:
Scheduler now permits per-event throttling. Throttle network bandwidth use during working hours, and allow full use of bandwidth overnight. Get your data replicated as fast as possible.

New in P5 6.1.2 (Mar 22, 2021)

New in P5 6.1.0 (Jan 25, 2021)

New user and group administration:
In previous versions of P5, the user and password were authenticated by the operating system. As of version 6, authentication takes place against users and passwords stored in the P5 configuration. Therefore passwords must be set within the P5 administration after an upgrade.
The new 'admin' account:
If it doesn't already exist, a user named 'admin' with password 'admin' is added following an upgrade to version 6. The login screen prompts to use this account initially. New installations also include this 'admin' user. Logging in as 'admin' allows creation of new users and groups.
Change this default password directly after the update. Within the P5 admin GUI, you can change the password for the current user via the 'P5' menu - top right.
Passwords for existing users:
All users already created in version 5.x are still available after updating to version 6. Any username previously used to login will have been added to the user list. Passwords for each of these users should be set by double clicking on the user in the list.
P5 server-client authentication:
Since the new user management is also used for P5 client/server connections, any P5 clients that your P5 server connects to will also need to have a password set on the client side, and the client connection setting updated on the server.
Login to the P5 admin GUI on each P5 client using the 'admin' user after upgrade. Select 'Agent Setup' from the 'P5' menu and then 'User Preferences' to the left. Set a password for the user used by the server to connect. Update the client settings on the server to use this new password.
From version 6 on, the original owners, groups and access permissions are recovered during restore. In comparison, in version 5 the GUI user was entered as owner and groups. (If the GUI user was known as a user on the target system of the restore.)
The automatic P5 client update function has been removed. Clients must now be updated manually.
The possibility of a specified or dedicated restore path has been removed from the user and client settings. These configuration items have been moved to the group settings.
The operating system groups in the login areas and archive plans are created as new groups in P5 during the update. The users already created are assigned to these new groups.

New in P5 6.0.2 (Jun 30, 2020)

New in P5 6.0.1 (Apr 14, 2020)

New in P5 5.6.6 (Dec 16, 2019)

New in P5 5.6.5 (Sep 10, 2019)

New in P5 5.6.4 (Sep 10, 2019)

New in P5 5.6.3 (Apr 18, 2019)

New in P5 5.6.2 (Jan 9, 2019)

Re-introduced FreeBSD/amd64 port for FreeBSD V11.
Deprecated: SCSI device support.
Re-introduced Solaris/Intel port for Solaris 10+.
Deprecated: SCSI device support.
FR#930: Adding metadata in P5 archive.
Added more clever logic: per-job metadata can be overriden by non-empty per-file metadata. One can mix both but one cannot combine/merge values.
FR#929: Backup of nested filesystems.
In order to support backup of large/deep hierarchicalfilesystems (like for example ZFS) one can now enablecrossing filesystem boundary while walking the filesystem tree and looking for changed files. To do that, one needs to edit config/lexxsrv.<PORT> file (where <PORT> is the value assigned during the installation; default = 8000), and put those two lines somewhere at the end of the file:
ns_sect ns/server/$server/module/Backup/CLIENT
ns_param crossFilesystemBoundary true
where CLIENT is the name of the P5 client.
Default value for crossFilesystemBoundary is "false", which means that file walk will not cross filesystem boundary.
After changing the file, P5 needs to be restarted for changes to become active.
FR#895: volumes with backing cloud-stores can now be manually synced-up with the cloud storage, regardles of their internal state. This aids in cleaning-up the volume cache for volume data stored in cloud only.
FR#875: sending e-mail is now more persistent in case of mail-server connection problems.
FR#874: added CLI command "Volume jobs" that lists job names of all the jobs that were writing to the volume.
FR#861: added tunable size for disk IO operations.
To change disk IO size, edit the config/lexxsrv.<PORT> file (where <PORT> is the value assigned during the installation; default = 8000) and put those two lines somewhere at the end of the file:
ns_sect ns/server/$server/module/jobex/CLIENT
ns_param bioSize SIZE
where CLIENT is the name of the P5 client and SIZE is a value in bytes, aligned to 512.
After changing the file, P5 needs to be restarted for changes to become active.
Added multithreading support for Sync cycle creation on filesystems w/o snapshot option.
To enable MT, one needs to edit config/lexxsrv.<PORT> file (where <PORT> is the value assigned during the installation; default = 8000), and put those two lines somewhere at the end of the file:
ns_sect ns/server/$server/module/Sync
ns_param cycleThreadCount 1
Default value for cycleThreadCount is 1 (one). Increasing number of threads for cycle generation might speed up this (lenghtly) operation if target filesystem is located on SSD device or on a very fast RAID system.
After changing the file, P5 needs to be restarted for changes to become active.
Fixed B2Go connection losses after 3 minutes waiting for the next changed file (Bug#928).
Fixed entering old-style licenses (Bug#925).
Fixed timeouts in Sync during long snapshot creation (Bug#923).
Fixed mail delivery when two or more e-mails were sent within one second interval (Bug#921).
Fixed cleanup of backup indexes containing large number of recycled volumes (Bug#918).
Fixed handling of Mac resource forks for HFS+ -> HFS+ copies (Bug#915).
Added "ignore cleaning flag" for special applications.
To ignore the cleaning flag for selected drives, edit the config/lexxsrv.<PORT> file (where <PORT> is the value assigned during the installation; default = 8000) and put those two lines somewhere at the end of the file:
ns_sect ns/server/$server/module/medmgr
ns_param dontClean "DEV1 DEV2 ... DEVn"
where DEV1, DEV2, etc. are names of the tape devices as shown in the P5 GUI.
After changing the file, P5 needs to be restarted for changes to become active.
Fixed write-speed issues for large-file archives (Bug#913).
Fixed auto-recognition of EtherShare volumes (Bug#907).
Fixed crashes on archives to cloud when jobs terminate unexpectedly or get cancelled manually (Bug#904).
Fixed crashes on Mac (and possibly other platforms) when rebuilding indexes after the backup.
Reduce number of warnings in GUI about Sync plans running in transfer mode (Bug#900).
Fixed restore entry for Sync plans when there is only one Sync license configured (Bug#989).
Fixed mode of resource sub-directories created during the restore within EtherShare volumes to 0777 (Bug#892).
Fixed spurious virtual tape driver errors claiming the volume being written has no label attached (Bug#891).
Fixed loading the LTFS driver for IBM LTO drives (Bug#890).
Fixed Sync file-event handling when source of events is not the localhost computer (Bug#888).
Fixed "Back Arrow" side-effects in GUI after log-in (Bug#885).
Added missing Client2Client manual Sync option (Bug#884).
Removed Cancel button from log-out pane (Bug#882).
Fixed Backup job lock-out after Volume recycle (Bug#877).
Added Application-Key support for BackBlaze cloud (Bug#858).
Fixed resource fork handling during restore to non-HFS filesystems resulting in IO-error messages (Bug#901).
Fixed generic install script on Unix to ignore Synology install options (Bug#842).
Removed scanning files before arhive and backup.
This feature was simply consuming resources and did not provide any realy useful information.
Fixed label of cloud volumes in case of upload errors (Bug#820).
Improved bandwidth throttle code to handle 10Gbps ethernet links (Bug#143).

New in P5 5.6.1 (Oct 24, 2018)

New in P5 5.5.6 (Jul 31, 2018)

New in P5 5.5.5 (May 16, 2018)

New in P5 5.5.4 (Apr 11, 2018)

New in P5 5.5.3 (Dec 27, 2017)

New in P5 5.5.2 (Nov 9, 2017)

New in P5 5.5.1 (Oct 20, 2017)

New in P5 5.5.0 (Sep 17, 2017)

32-Bit support has been discontinued for P5 Version 5.5. The new version is compatible with 64-bit operating systems only.
New features:
Backup to the Cloud:
For quick backup, restore and improved accessibility, Archiware P5 version 5.5 provides a new feature allowing users to back up data to the cloud. In addition to disk and tape, the P5 Backup module now offers "Cloud Storage" as an option for the backup target (see screenshot below).
The cloud service is easily configured in the P5 Backup module. A volume pool is created to which the selected service is attached. To monitor storage use, the P5 Backup Overview indicates the available storage under "Pool Usage" (see screenshot below).
Supported cloud integrations include Amazon S3, Amazon Glacier, Generic S3 and Backblaze.
Extended Cloud Support for P5 Archive:
In P5 version 5.4, Archiware introduced the cloud as a new archive target. Archiware P5 version 5.5 now extends cloud support for P5 Archive to Amazon Glacier, Generic S3 and Backblaze.
These integrations are additions to the already supported Amazon S3 cloud service. As of version 5.5, the P5 Archive Cloud Enabler is included as part of P5 Archive. A separate expansion is no longer required.
Archive Using Pool or Object Format:
Version 5.5 of P5 Archive provides the choice between two archiving modes: the Pool Format and Object Format.
The Pool Format includes all the familiar, powerful features of P5 (cloning, migration, etc.). This standard procedure assigns archived data to a Pool consisting of a flexible number of Volumes, e.g. a pool of data from 2016 comprising a range of LTO6 tapes (Volumes). The organization and bundling of data into Pools and Volumes creates manageable entities. These can be subjected to the same operational procedures, such as the cloning of Volumes for increased data security or migration of data to a different storage location.
In the Pool Format, data is exclusively restored through P5. Supported storage formats include tape, disk and the cloud.
The Object Format allows single-file access without P5 and share-ability for cooperative workflows. In this format, archived data are stored as individual objects (Files). This mode provides applications and users the option of directly accessing and restoring data archived to the cloud without P5. To enable direct data access, P5 stores data in its original format in the cloud. The link-addresses required for external access are logged by P5. This storage format is only supported in the cloud (Amazon S3, Backblaze, Generic S3).
Client-to-Client Sync:
To speed up data transfer between two P5 client machines, Archiware P5 version 5.5 now offers a Client-to-Client sync option for P5 Synchronize. By configuring a synchronize plan on the P5 server, data can easily be replicated between clients.
The added flexibility eliminates the need for server involvement during data transfer. The main server load is alleviated and intermediate storage is no longer required. To use the Client-to-Client sync option, a separate server agent license is required for each client.
Automatic Backup of Archive Indexes:
As of Archiware P5 version 5.5, Archive Indexes in the Archive module are automatically backed up at regular intervals. To back up indexes, a P5 client is selected in the Archive Index as a target.
After configuration, Archive Indexes are copied daily to the selected location on the client. The user determines the time at which each index is backed up. For a successful backup, a P5 client license is required.
CLI Features / P5 Interface / OS Support:
New features in the CLI include post-archive preview and clip handling, as well as automatic identification and sorting of cloned volume sets. This saves time and simplifies the modification and handling of volumes and assets.
In the P5 user interface, version 5.5 now enables users to grant operating privileges and assign separate passwords to selected individuals (see screenshot below).
Privileged users can access specific data, exchange library media, start/stop backup jobs and label/unload tapes. This optimizes the management of data by specific groups.
For Backup and Archive to the cloud, supported Operating Systems include macOS X, Windows, FreeBSD, Linux and Synology.

New in P5 5.4.4 (Sep 17, 2017)

New in P5 5.4.3 (Mar 9, 2017)

New in P5 5.4.2 (Jan 13, 2017)

New in P5 5.4.1 (Jan 4, 2017)

New in P5 5.4 (Jan 4, 2017)

Archive to the Cloud:
Cloud storage is a cost-effective and flexible alternative for businesses, saving hardware and administration cost. Plus, it grows with your requirements - additional TBs of storage space are easily added.
Archiware P5 version 5.4 now offers "Cloud Storage" as an option for the archive target, the third option next to the existing disk and tape targets (see screenshot below). Simply chose the new target when setting up your Archive plan.
In the P5 Archive Overview, the use of available cloud storage (according to the license) is shown for better insight (see screenshot below).
To use cloud storage as an archive target, a P5 Archive Cloud Enabler license is required. Once this license is registered, the option to configure cloud services is activated in the user interface. Archiware P5 version 5.4 supports Amazon S3 cloud services only. In future versions, more cloud services and providers will be added continously.
Preview Creation using FFmpeg & ImageMagick:
To give users more options when creating proxy videos or image previews, Archiware P5 version 5.4 now offers a direct integration with FFmpeg and ImageMagick. It is now easy to create low-resolution, full-length previews for video: simply select resolution and data rate for video and audio (or resolution for images).
The configuration of both tools can now be done within the settings of P5 Archive, no scripting required.
For increased browser compatibilty and performance, the display method for previews has been changed to HTML5.
Synology NAS integration (as of 5.3.3):
From Version 5.3.3, Archiware P5 supports Synology NAS devices without restrictions. Data from Synology devices is stored in a platform neutral format including user authorisations - identical to all other supported platforms.
Synology NAS can serve as a data source or target for P5 Synchronize, P5 Backup and P5 Archive. The Archiware P5 application can now be installed on the Synology NAS itself.
Thanks to the snapshot capability of the DSM platform, powerful enterprise Synology NAS devices can also be used as repository for Backup2Go. This setup opens the possibility of introducing a professional data security solution at an affordable price point.
Restore links / Source selection in P5 Archive:
To support co-operative workflows, P5 Archive now offers the possibility to send a link to an asset via e-mail. The recipient just clicks the link to watch the preview, view and edit metadata, restore or simply approve the choice of video for an edit.
Another simplification in P5 Archive has been implemented in the source selection: The tree structure now immediately displays the user directory and all mounted volumes, saving the user several clicks when selecting files or folders to archive from their file system.
Data integrity checks / List display / OS support:
The data integrity check options have been expanded for Archive to disk and tape. The following checksum types are available: MD5, SHA-224, SHA-256, SHA-384, SHA-512. Additionally, compare content can be selected as verification method.
For a comprehensive overview of Backup and Synchronize jobs, the Backup/Synchronize plan lists now display the next scheduled run.
Lastly, as of version 5.4, Archiware P5 officially supports macOS 10.12 Sierra and Windows Server 2016.

New in P5 5.3.3 (Oct 12, 2016)

New in P5 5.3.2 (Mar 16, 2016)

New in P5 5.3.1 (Mar 16, 2016)

New in P5 5.3 (Mar 16, 2016)

New in P5 5.2.3 (Mar 16, 2016)

New in P5 5.2.2 (Mar 16, 2016)

New in P5 5.2.1 (Mar 16, 2016)

New in P5 5.2 (Mar 16, 2016)

Full 64-Bit support:
The 64-Bit version delivers optimal use of the main memory. This can increase data throughput in enterprise installations where multiple parallel data streams are backed up or archived simultaneously.
Archiware P5 release 5.2 supports both 64-Bit and 32-Bit Operating Systems. With 32-Bit, the storage assignment for each application is limited to 4GB. Therefore, the best allocation of cache as temporary storage is only possible for a limited number of jobs and devices. Archiware P5 64-Bit makes maximum use of server hardware. P5 5.2 delivers more bandwidth and increased scalability, while at the same time better exploiting the available hardware resources. Compatibility between 32-Bit and 64-Bit versions is assured
Archive Index Management:
P5 Release 5.2 enables users to modify the structure of the Archive Index. An Archive is built over a period of years, which often makes it necessary to adapt the index structure to current requirements. Similar to a conventional file system, P5 now supports moving and renaming of index elements as well as creating folders. To ensure that the history of the structure is preserved and changes remain traceable, modifications are saved in snapshots. A snapshot is an image of the index structure at a specific point in time. This way, the Archive can be adjusted to meet current requirements while retaining previous structures.
Storable Searches in the Archive Index:
Archiware P5 Release 5.2 lets users store search criteria in order to find data quickly and easily. This is especially helpful when P5 Archive is used as an integral part of the workflow and data from the Archive is required frequently. For instance, data from specific productions can be collected in a search and the search stored for quicker restore processes.
Archive Job Protocol:
Archiware P5 Release 5.2 compiles a list of files that were archived successfully. This list can serve as documentation and therefore as a protocol of the Archiving process. After Archiving, the protocol is sent automatically as an e-mail.
Mailserver Authentication:
The use of P5 within a production workflow or as a cloud service requires secure communication with the central mailserver. To achieve this, P5 is equipped with the industry standard for mailserver authentication. The P5 server authenticates itself with a user name and password and the communication is SSL/TSL encrypted.

New in P5 5.1.9 (Mar 24, 2015)

New in P5 5.1.8 (Mar 11, 2015)

New in P5 5.1.7 (Nov 18, 2014)

New in P5 5.1.6 (Sep 17, 2014)

New in P5 5.1.5 (Jul 26, 2014)

New in P5 5.1.4 (Jun 6, 2014)

New in P5 5.1.3 (Apr 25, 2014)

New in P5 5.1.2 (Apr 25, 2014)

New in P5 5.1.1 (Feb 25, 2014)

New in P5 5.1.0 (Jan 14, 2014)

New in P5 5.0.7 (Dec 18, 2013)

New in P5 5.0.6 (Nov 20, 2013)

New in P5 5.0.5 (Nov 13, 2013)

New in P5 5.0.4 (Sep 10, 2013)

New in P5 5.0.3 (Aug 19, 2013)

New in P5 5.0.2 (Jul 19, 2013)

New in P5 5.0.1 (Jun 3, 2013)

New in P5 5.0.0 (May 25, 2013)

LTFS Support:
P5 integrates with MediaLTFS, a tool designed to manage LTFS tapes. Through this integration, P5 can label, mount or un-mount tapes and allows users to read and write to or from the medium. P5 also handles the management of a designated tape drive within a tape library, keeping archive tapes as well as LTFS tapes cleanly separated.
In addition to the native LTFS support, P5 adds the option to restore files from P5 Backup and Archive to a designated LTFS tape. LTFS tapes are primarily a means of transportation between different sites, possibly with the sender or receiver not owning a P5 license.
Cloud Support:
P5 integrates with WingFS, the universal cloud connector. This tool enables P5 Synchronize to replicate files to and in between popular cloud services, such as Amazon S3, Google Drive and Google Cloud Storage. Just as importantly, P5 Synchronize can backup data from the cloud to a local storage. Backup your cloud and preserve ownership of your assets!
Technology:
The new P5 engine based on SQLite changes how the index is generated. The 4GB index size limit is now a thing of the past. P5 is ready for the future, with a new index that scales indefinitely.
Snapshot capabilities within P5 Backup and Archive enable point in time restores. This lets users go back to specific points within any given project.
Archive & Asset-Management:
Incremental Archive is an archive option that only moves data that has been altered. This feature is analog to the incremental option in P5 Synchronize and made possible by the new snapshot capability.
Altering a file triggers a new version that will then be included in the file’s overview screen
Archive overview screen:
A newly designed overview screen within the P5 Archive restore section makes for a great new browsing experience. Included within the same overview screen is the file structure, a chosen asset, its meta-data,
as well as a thumbnail. One additional click also gives access to a file’s versions (see incremental archive).
The display of previews can be customized by changing display size within the P5 Archive overview screen.
The new option to generate SQL queries makes third party integrations possible, especially for MAM/DAM.
Pre-definable meta-data fields:
Pre-definable meta-data fields allow user to specify mandatory meta-data for the assets being archived. While archiving, mandatory dropdown menus can be presented to the user, ensuring a homogenous use of meta-data throughout the archive.
Pagination & Search:
The pagination functionality within P5 Archive speeds up browsing, as only a limited number of assets are loaded for each page. This significantly improves browsing speed for large data sets.
An improved search algorithm, together with the new engine, improve speed and add search functionalities as well as thumbnails within the search. Quick switches between browse- and search-mode are easy, while staying within the same window.

New in P5 4.4.8 (Apr 11, 2013)

New in P5 4.4.7 (Apr 11, 2013)

New in P5 4.4.6 (Dec 6, 2012)

New in P5 4.4.5 (Oct 22, 2012)

New in P5 4.4.4 (Sep 21, 2012)

New in P5 4.4.3 (Jul 27, 2012)

New in P5 4.4.2 (Jul 14, 2012)

New in P5 4.4.1 (Jul 14, 2012)

New in P5 4.3.7 (Jul 14, 2012)

New in P5 4.3.6 (Jul 14, 2012)

New in P5 4.3.5 (Jul 14, 2012)

New in P5 4.3.4 (Jul 14, 2012)

New in P5 4.3.2 (Jul 14, 2012)

New in P5 4.3.1 (Jul 14, 2012)

New in P5 4.3 (Jul 14, 2012)

New in P5 4.2.4 (Oct 12, 2011)

New in P5 4.2.3 (Oct 12, 2011)

New in P5 4.2.2 (Oct 12, 2011)

New in P5 4.2.1 (Jun 29, 2011)

New in P5 4.2.0 (May 18, 2011)

New in P5 4.1.4 (Feb 2, 2011)

New in P5 4.1.3 (Nov 26, 2010)

New in P5 4.1.1 (Oct 27, 2010)

New in P5 4.0.3 (Oct 22, 2010)

New in P5 4.0.2 (Oct 22, 2010)

New in P5 4.0.1 (Oct 22, 2010)

New in P5 3.2.6 (Oct 22, 2010)

New in P5 3.2.5 (Oct 22, 2010)

New in P5 3.2.4 (Oct 22, 2010)

New in P5 3.2.3 (Oct 22, 2010)

New in P5 3.2.2 (Oct 22, 2010)

New in P5 3.2.1 (Oct 22, 2010)

New in P5 3.1.5 (Oct 22, 2010)

New in P5 2.3.123 (Oct 24, 2007)

New in P5 2.3.10 (Jul 9, 2007)