Sync’d Amps on dektop versions PC/Mac

  • I use the Bias Amp Pro Version on a PC and a Mac. It’d be great if I could log in to each and see the same amps.

    Besides working on a private-mode for the Tonecloud it would be great to make the main-path to the BIAS-folder customizable, to choose where the settings are stored. This way one could choose a cloud-service, for a automatic sync of the amp-presets.

  • Why not just point the sync service to the native directories? I go to those places and copy the files every time I update Bias/FX. I also make a new working directory (within My Documents - and yes my drive is partitioned), and then move the previous one to a backup archive.

  • @tannhauser It'd be great if this could be done between the iOS app and the desktop as well.

  • Probably a simple script could be written to do it however you want. For that matter, a pretty simple one could be written to do what I do manually when I update the app - though it would need some processing, as the file name needs two dates and the version number being replaced. No, wait, just adding the current date to the existing file name, and then some character interpolation. But I don't make things, I just think them up.

  • WARNING: Do not use any sync services like Google Drive & Backup (or other cloud-sync) to keep your actual settings in the cloud for downloads to your other desktop-device!

    I tried a sync with Google Drive & Backup and shredded my installation of BIAS Amp Pro to a point, I needed support via Teamviewer. There is something strange going on underneath the visual parts of the sync and your license could be corrupted.

  • I'd checked the behavior now and my suggestion for a multi-device backup is…

    Backup your presets

    • Identify the path to the Bias-Folder, where your presets are stored, using this official helpfile…
    • Duplicate the Bias-Folder using Copy & Paste or the duplicate-option of your OS
    • Generate a container like a .zip-file from out the duplicated folder
    • Move your container-file to a safe and accessable location like a cloud-service

    Restore your presets

    • Copy your container-file backup to your local disk and leave the original backup-container in the cloud
    • Unpack the container-file (source) to a folder on your HD and open the new generated folder
    • make your OS show all invisible files (starting with a set point) especialy ".license" and ".pgbias"
    • move every visible (!) content from your backup to your local Bias-folder (target)
    • leave all invisible files in the source-folder / backup, especialy ".license" and ".pgbias"
    • start your Bias Software and check all changes you liked to transfer to your Bias installation

    This suggestion is based on my personal experiences and investigations. It seems to be the safest way for a backup. When you let ".license" and ".pgbias" stay untouched in your target-folder not copying it over from the backup-source prevents bad overwriting or weird stuff which could be caused by oddities of file-systems. Using a ZIP-container protects all files within the backup-file, too.

  • Does anyone elso have problems restoring multi-platform backups?

    Sometimes, in my case even with the latest version of BIAS Amp Pro, the order of the restored amps is wrong and some amps are missing completely :(

    I use the PC version as my master for tweakings and restore to 2 Macs as target.
    There are amp icons missing too but that's a problem even in the source banks, which appears after tweaking and saving amp settings.

  • @sascha-ballweg said in Sync’d Amps on dektop versions PC/Mac:

    I use the Bias Amp Pro Version on a PC and a Mac. It’d be great if I could log in to each and see the same amps.

    More than anything else I still like the idea, to keep my offline presets in sync somehow!
    It would be perfect, if one could mark a preset or a complete bank for synchronisation to exclude some for testings and comparison reasons.

    It is a PITA to keep your presets at the latest, if you use different computers and iOS devices and I am pretty sure this could be solved as a hidden process within the existing tonecloud-features.