I have noticed that quite a few other modern VST3 plugins (which I would expect would have 64-bit float processing) are also being recognised as just 32-bit float processing, and am now wondering whether this is being reported accurately - and whether it is worth switching on 64-bit float for internal processing, or just leaving at 32-bit float. Is there a reason whereby the Ozone VST3 interface code may be causing this to be the case.However, after some investigation and a few more days of use, I realized Ozone 9 is impressive because Ozone 8 is impressive Therefore, my first inclination (referenced in the following video) that the scale-able GUI was the most impressive new. Is WaveLab mis-recognising this and the VST3 versions will only be used at 32-bit float Until I realized Izotope Ozone 8 has the same features as Ozone 9, I thought Ozone 9 was terrific.using 64-bit float, assuming I have selected this in WaveLab) Is WaveLab mis-recognising this, and the VST3 versions will actually work fine (i.e.they are both using 64-bit float processing) so I am confused as to what exactly is happening in WaveLab and am trying to understand which I should use and why… Having talked to iZotope, the internals of both is the same (i.e. Ozone 8 VST3 plugins crash in WaveLab, but the Ozone 9 VST3 plugins do not. The Ozone 8 and 9 VST3 plugins are all recognised by WaveLab as being 32-bit float (whilst they are internally 64-bit float), whilst the very same VST2 plugins are being recognised (correctly) as being 64-bit float. Izotope Ozone 8 and Ozone 9 plugins have some “interesting” behaviours in WaveLab…
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |