Jump to content

iNate

Members
  • Posts

    74
  • Joined

  • Last visited

Everything posted by iNate

  1. The preview performance in this version is basically the same as 18, which is basically the same as 16. I refunded this and will upgrade SpectraLayers Pro, instead. I can use VP18 in the same way and for the same reasons, and I will not really be missing anything of note from this version - except more overbearing sheparding towards VEGAS Hub and stuff like that. Plus, VP18 integrates with the Humble Bundled HitFilm Pro 16, so there is also that benefit, in case I need it (e.g. for Mocha Tracking, etc.). The VST3 support is quite nice, but I am tired of eating costs for upgrades that aren't really worth it at all... so I'm clamping down and asking for my money back (which they happily obliged). Nice price, but just doesn't deliver enough. I think they're kind of screwing themselves by giving it away, particularly given how laggard the development pace for this software is.
  2. Buy a 2TB Crucial PCIe 4 NVMe drive for $85 and just install everything. Put it in a cheap enclosure and just install to that. Use what you want to use when you have need of it. If you have a desktop, you can just add a 2TB SATA3 SSD, label it "Native Instruments" and dedicate that drive to their stuff so you have room to accomodate any future releases you acquire. You don't really need NVMe, unless you're using it externally, so you can saturate a 10Gb/s USB 3.2 port (or Thunderbolt). Needs can change, so whether you use a specific instrument today can change in 4-6 months (we all say and think it never will ?). It's annoying to have to download multi-GB libraries on-demand when you figure you have need for it. Also, if you collaborate with anyone else, they may use things that you don't use, so having it there and ready for when you have to open a project file that uses the library or instrument is useful. As for why the Violin and some other instruments weigh a lot... It's because they're actually trying to deliver good quality instruments that are usable up and down the market. Ripping out Mic Positions, Round Robins, Dynamic Layers and Articulations just so it can stay under 5GB (or whatever) is not the route to that destination. All premium orchestral instruments weigh a lot, unless you're using a Lite SKU of the product - where those aforementioned things are done to create disparity with the Pro SKU. Compare the size of BBCSO Core (~20GB) to BBCSO Pro (~700GB). Or Session Horns/Strings to Session Horns/Strings Pro. Or Symphony Essentials (~19GB Total) to Symphony Series: Collection (~167 GB Total). That is how this all works. There is no Cremona Quartet Essentials. The only instruments that exist are those that would fall into the Pro SKU. They're heavy libraries, but making them lighter would actually decrease the value of them... so in the end you probably wouldn't want to install it for that reason if that were done. Komplete isn't designed to have everything appeal to everyone, anyways. It's designed to have enough that appeals to any one person to justify investing in the bundle. There are tons of Expansions that I will probably never use because they are Genre-Targeted and I don't produce e.g. EDM, Trance or Drum & Bass music. Get more storage while the prices are heavily depressed. Prices have a way of rebounding at the most inopportune times ?
  3. Humble Bundle is usually 2 versions behind. New version probably on the horizon. That's usually how MAGIX does things. EDIT: Would also add that at this price the Edit version is probably worth the upgrade, especially if you use VEGAS Pro 18 (or prior) and plan to sit on it for a while (or never upgrade beyond it - VEGAS is a decent NLE to have for low spec/older machines that cannot run other software that well) because the VST3 Support is kind of worth it. I'm probably going to get it to put on my Windows Notebook, and then move my Resolve Studio License over to my MBP. I will never upgrade it again, though, since this is likely the last PC Laptop that I will ever own (technically the M1 Pro MBP was an upgrade, but I still use both). If I ever have to travel and there is a legitimate risk of theft, damage, etc. to my laptop I will just take the PC since it's disposable, at this point, and use VEGAS on it for Video Editing.
  4. Sonic SE 3 is out of development and unsupported. It was replaced by Sonic 7. Sonic 7 is free. Its the default for all SKUs of Cubase and Dorico. Flux was not updated.
  5. Everything I look for is in a standardized area of the registry. It has been this way since Windows 3.1x. You're projecting the issues with the INI system onto the registry, where you didn't know if the INI file was in the Application, User or Windows Directory. And where application settings were often left vulnerable to changes from other processes with no security measures in place. Honestly, if someone is that bad with pattern recognition, there is nothing Microsoft can do to mitigate their issues with the Registry.
  6. Windows has nothing to do with bad ASIO drivers, though... Higher end equipment will have less stable WASAPI drivers because less effort will be put into them. The users buying that hardware also won't be focusing on testing the WASAPI support, so any issues there tend to be underreported (if reported at all). It has nothing to offer them. Most of the lower end audio interfaces are class compliant, anyways. WASAPI is nice on laptops for mobile use, but I've found lots of laptops have speakers tuned for multimedia use and are terrible when used for this, and the headphone jacks aren't shielded that well. I have 5 consumer interfaces here and none of them actually need a driver for Windows Audio support. They're all class compliant. You plug them in and they just work. The ASIO drivers are where the problems tend to crop up. Focusrite Scarlett had chronic buffer underrun issues that they didn't fix for a long time until they finally implemented a safe mode in their driver, which increases RT Latency. Ancient hardware has a habit of not working on platforms they are literally decades newer than it. And some audio software only supports ASIO, so there's no way to avoid it on Windows unless you severely limit yourself there. Others only support legacy audio support (as Windows applications tend to lag the platform - on average - due to the existence of ASIO).
  7. Except you're wrong? Registry has a standardized organization.
  8. The great thing about dongle is that your license is a physical product that you actually own. They're not the most convenient devices, but owning Cubase 11 on a Dongle is no different than owning an MPC One or a MacBook Pro. If Steinberg dies and shuts down their servers, I will still be able to simply plug it in and run the software. eLCC doesn't need their servers to validate a dongle license. I reckon iLok would work similarly.
  9. It doesn't. Basically just installation status and install locations. I've looked at this myself. Wi does doesnt use PLIST files. The Registry is where this stuff goes. Do we really want to go back to tens of thousands of .INI files scattered across the system? Maybe time has erased the memories of how awful that was. The FUD in this thread is a bit out of control, LOL. Also, if you have Replica XT and Supercharger GT then there is literally no point in installing Replica or Supercharger. The other versions are a superset, and render them redundant. That's why Replika is in Komplete Standard, but only Replika XT is in Komplete Ultimate/Collectors.
  10. I have personally not seen this. Usually it is less "audio interface driver incompatibilities" and more along the lines of "your interface's ASIO driver is crap, and is being exposed." But frankly I think Microsoft needs to put more work into Pro Audio so that we can divorce ourselves from dependence on ASIO drivers - or at least start to. ASIO driver bugs can masquerade as DAW bugs or even OS bugs, and can be incredibly hard to troubleshoot (moreso when it looks like something other than it is - like if only specific software is crashing with the driver selected).
  11. Windows 7 is not a viable gaming platform, unless you only play legacy titles from GOG or something. It's dead for AAA gaming as those are increasingly web-connected and it is negligent to support a dead platform when your users accounts/data/etc. are put at risk due to unpatched exploits racking up on that platform. It makes no sense. Microsoft is not going to go back and patch Windows 7... not for consumer gaming. That would be one step forward and two steps back. Besides, new hardware increasingly requires newer Windows OSes, so the people still on Windows 7 likely aren't really in the target market of any new games being released. ----- Also not sure what the OP is referring to. Sounds like a conspiracy theory.
  12. Updated Components: Padshop 2 - v2.2.0 (Instrument) Content Set Patches Granular Guitars MPE Sounds Padshop Padshop 2 (Content) Padshop (Factory Content) Zero Gravity Padshop 2.2.0 Version History: Library Files likely updated to work better with the new MediaBay browser system. (???)
  13. I am not sure what Crucial's track record is with their external drives, but my 1TB Samsung T5 has almost 95% Endurance after 2.5 years of use, and I've copied a LOT of data onto that drive. My guess is you can probably get a good decade or more out of it, assuming relatively normal usage and no defects that affect its lifespan.
  14. Speaking for myself. I don't. I uninstall and move on. There are material risks in continuing to use it in projects. This is especially true if you don't have a good system for stemming things out and archiving the audio. If you rely primarily on your ability to access Archived DAW Project Files, then it's a good idea to simply cease using out of development products.
×
×
  • Create New...