Using Omnisphere in multiple, seperated instances (I´m one of those who use it that way => freezing etc. works better for me) can lead to a gigantic RAM-waste as the original DLL-sizes are extremely big for a VSTinstrument (1.58d = 80 MB, 2.03d = 120 MB).

The main reason why they are that big lies in the implied "quality" of the PNGs used by Spectraonics. They seem to be in a format that is totally unnecessery as an experiment by myself prooved.

If you are a Photoshop (CC) user, know how to use actions/automations, just try the following:

1. Extract all PNGs from your Omnisphere.dll with RESTORATOR 2007 (1.58d = 555 PNGs, 2.03d = 726 PNGs).
2. Start Photoshop and make a simple action (ultra simple: 1. step "double layer", 2. step "delete layer") in order to be able to make an automation for all PNGs
3. Open all extracted Omnisphere PNGs above the size of 15 KB (important!) in PS and start your automation (or in chunks of 50 PNGs if your PC/notebook has not enough RAM)
4. After all PNGs above 15 KB have been re-saved with the standard-Photoshop-PNG-format you will notice that
a. the quality of the PNGs is absolutely the same as delievered by Omnisphere in the original DLLs
b. the size of your Omnisphere-PNG-folder was reduced to around 33 %, what means that you will save around 50 MB (80 MB in the case of 2.03d) per instance of Omnisphere!
5. Use Restorator 2007 to assign the re-sized PNGs to the DLL (a backup-copy will be saved). The size of your Omnisphere.dll (x64) will shrink to 30 MB (1.58d x64) and 40 MB (2.03d x64).

It is a fact that this procedure has to be done with every new revision of the DLLs that are/will be provided by Spectrasonics (normally the PNGs of version 1 and the new version 2 should stay the same, therefore you only have to assign your previously converted PNGs into the new DLL using Restorator 2007 => just two clicks; the Photoshop-procedure has to be done only once for every version if Spectrasonics do not change the layout, the number of graphics etc.).

Well, if this is to much work for you - good! Just a well-meant tipp for all those who need (wish to have) a smaller Omnisphere.dll and didn´t know that the main reason for its bloated size is the pseudo-quality of the PNGs used by Spectrasonics. I used a resized 1.58d-DLL for quite a white, averything worked well (because you do not touch the source of the DLLs, only replace the bloated PNGs by Photoshops PNG-format).

Best regards.

 

Very interesting, but I don't have this skill.
So, thanks anyway

 

send a mail to Spectrasonics; they will surely appreciate it (at least I would)

 

Good topic EternalNow, but using modern PC with lot of RAM (like 8 GB+), really 120 MB (as total size) isn't huge (IMO), but I agree, it's RAM-waste by using HQ PNGs. Sure this tip may help users who have few RAM on their PC, however.

Strange things discovered in Omnisphere 2:

- No uninstaller (you must delete all manually, folders/files and Registry keys).
- Omnisphere/Omnisphere 2 have ton of emulated synths, but not the Roland D-50. Strange, aren't? Eric Pershing have developed wave ROMs for the real hardware - FYI these waves in ROMs are used during sound "Attack" stage (then followed by synthesis). This guy remains the owner (not Roland) of these ROMs and never accept to publish/sell them!

 

Probably (IMO) many legit Omnisphere customers have reported this problem long time ago (seven years between O1 and O2), but remains unfixed in Omnisphere 2...

 

Heee no! Sure it's unbelievable, but waveforms used in D-50 ROMs are Eric intellectual property, and not Roland! The contract between Mr Pershing and Roland was etablished as is, this was explained by Mr Pershing itself (when he've founded Spectrasonics) and was confirmed (later) by Roland company. During 80's they're great competition between synth manufacturers such Roland, Korg, Kurzweil, Yamaha, Casio and so on (the list is long), it was maybe easier for him to negotiate with these companies (according to "laws of supply and demand").

For any synth designers (hardwares or virtuals) who want to develop (under licence) D-50 emulation, Mr. Pershing always say NO!

For later synths models, maybe Roland have changed their partnership rules.

Finally, I agree, the D-50 is an amazing synth, even today. I was D-50 user during 5 years.

 

I'm willing to bet that if you changed your monitor's settings to the highest dimensions after converting the pngs, you would start to notice degradation...

 

You've got nothing without nothing in counterpart... It's also true about music (difference between pure WAV file and MP3).

Take a look about system requirements for Omnisphere 2, in particular RAM: 4 GB as minimum, 8 GB+ recommended... As I've wrote (above), modern PC & Macintosh have enough RAM and CPU power.

About O2 reduction, I've received one question (on PM) like "to save space on my SSD, can I remove these or these Soundsource files?" really! funny of course, my ironic answer was "Of course! you can remove all Omnisphere 2 files to save space"...

 

Thanks EternalNow, interesting discovery!

 

As stated above, I do not use the multi-outpout feature for a number of reasons (generally I like to have separated instances; freezing Omnisphere tracks in Studio One 2 works better for me with seperated instances). And: Generally you can never have enough RAM available (if you like to compose, gather ideas while being in nature - like I do => my style: Schiller/Enigma - and have a limited amount of RAM available in your notebook it can be very helpful).

Why waste resources if the solution is relatively simple...

As I finished above: "A well-meant tipp", nobody is forced to use/apply it in his "DAW-reality".

 

No, none. I work with Photoshop for over 16 years, have signifikant amount of experience with photos, webdesign, GUI-design, graphics. In the case of Omnisphere 1.58d and 2.03d I looked over a limited number of re-saved graphics (because there are so many => 1.58d = 555 | 2.03d = 726!), zoomed in to the max-level (= pixels) and saw no difference.

Why should there be any? By making an automation like I wrote above (use an apply-save-as-automation with an action: "1. copy original-layer, 2. delete doubled layer") you use the standard-PNG-format provided by Photoshop (CC), is has a great quality. Nothing else is done or applied to the original Omnisphere-PNG (no changes in colors/contrast, no degradation etc.).

As I wrote above: It was an experiment done by myself some months ago with Omnisphere 1.58d x64. I didn´t expect to save over 70 % and have no quality degradation ... I used Omnisphere 1.58d for some months now basically every day on my notebook (1600x900) and had no problems.

Exacly the same can/could be now applied to 2.03d (and coming versions). You will/would save around 80 MB of RAM (120 => 40) for only one instance...

 

Comparison:

 

Surely it's right! I don't have read the contract *no* however. But maybe like patents, they're time limitations (or something like).

 

Really I don't see difference between original and redux, impressive! Maybe the user who have reported degradation don't have apply exactly your process (sorry for faults)

Maybe (I precise I mean "maybe") you can see degradation on high resolution / large size screens or Retinas?

 

there is freeware software it does the same job as Restorator 2007

http://www.angusj.com/resourcehacker/

Download Resource Hacker Version 4.2.4 http://www.angusj.com/resourcehacker/reshacker_setup.exe

Download Resource Hacker Version 4.2.4 Portable Version http://www.angusj.com/resourcehacker/resource_hacker.zip