Library Manager and GA 6

Just installed GA 6.

All content went to my vstsound file locations. Clicking on the individual vstsound files from my installer location opens the pop up in the Library manger states files all installed.

However clicking on the detail tab in the Library Manager for the files shows different file sizes to that which are installed.

eg GA6 version of FCP_SMT_773_GA_The_Kit_Samples.vstsound is 14.69GB but Library manager detail tab reports it as V1 13.68GB

The version number of the vstsound file also looks suspect (why would an install of a new GA6 library overwriting a GA5 library content still show the library as version 1 and not version 2)

Is this simply an index update error in the Library manager data and if so how do I correct / refresh this?

Thanks

David

Where do you see 14.69GB?

Probably because would not need to be overwritten if the same file is part of GA6. On my Windows 11 system it was not changed by installing GA6 over GA5.

N.B. GA6 replaces GA5, the versions do not exist side-by-side.

1 Like

Yes GA6 replaces GA5. You can’t go back. I guess not a big deal. So Far I havent seen a problem.

File size is reported by Mac finder listing in the vstsound folder.

David

Yes but it’s a vstsound file used by the program. It was part of the GA6 installer so is overwriting the prev file of same name used by GA5. So whilst it could be V1 for a GA6 use it’s an odd way of doing versioning. In addition file size of old and new differ.

David

If you’re looking at the file size in bytes, you need to remember converting to gigabytes is not just moving the decimal point, as one gigabyte is equal to 1024 x 1024 x 1024 bytes. For example, on (Windows here), the file size is reported by Windows Explorer as being “14,344,182 KB”, and if I look at the details of the file I see the size, in bytes, as being 14,688,441,936

14688441936 / (1024 x 1024 x 1024) = 13.67967756092548 … or rounded to two digits, 13.68 GB.

Furthermore, the date of the most recent modification of that file is 28-Jun-2019. On my system, built last summer, that file was created in June 2025, which would be the time I installed GA5 on the new system, so, at least on my system, that file was not overwritten by installing GA6, which I did two days ago.

… which would make sense, and would be needed for systems that did not previously have GA5 installed.

They don’t, for reasons explained above, so the installer had no need to copy it again.

I’m going to assume that these are internal version numbers that shouldn’t concern users under normal circumstances, so it may seem odd to use alright, I’m not seeing any problem here.

Did something go wrong during the installation, or is something not working for you?

1 Like

Thanks for this. I had assumed that the calculations for file size was done by the computer for both the file on disk and the reporting detail inside the Library program as both were displaying file size size in GB. The Library manager program is using your method Mac OSX appears to be rounding.

This is how Mac was presenting it (SMT_773)

Kind: VSTSound File
Size: 14,688,441,936 bytes (14.69 GB on disk)

FCP_SMT_773_GA_The_Kit_Samples.vstsound 14.69 GB VSTSound File

FCP_SMT_774_GA_The_Kit_Samples_Eco.vstsound 7.45 GB VSTSound File
FCP_SMT_772_GA_The_Kit_Presets.vstsound 159.9 MB VSTSound File

And this from Steinberg Library manager

FCP_SMT_772_GA_The_Kit_Presets.vstsound v6 152.48 MB
FCP_SMT_774_GA_The_Kit_Samples_Eco.vstsound v1 6.94 GB
FCP_SMT_773_GA_The_Kit_Samples.vstsound V1 13.68 GB

Anyway all now makes sense. So thanks.

And far as using GA6 haven’t got that far lol. I was just concerned at the data difference which Id thought id investigate before diving in.

David

David

Windows, by comparison, for the identical file size:

The confusion occurs because of the difference between decimal and binary interpretations of “GB”.

Think the programmers need to meet lol.

David

I beg to differ on this small point. Uninstall GA6, install GA5.

1 Like