I just played on my MIDI piano some sick tunes to test its finest quality (and functioning). The obvious issue The Soft Synth plug-in “SampleTank 2.x” was not found or did not load properly.
Next thing, throwing all the VST Plugins at it with excitement to kick of my fresh DAW by pushing some tunes through my “Microsoft Sound Mapper”, it complains about certain VST plugins not being loaded or installed properly. So it was finally time to make the big step for human kind hop onto the hip train of Windows 10!Įasy peasy, install Windows 10, install drivers, install ACID Pro 7.0e!
Obviously I was way out of date with my Windows 7 steam machine. Wait, what was I writing about again? Ah yes. But I hold up by, what DVD drive would ever consume my non-existent Win7 Pro Installation Media? “Just slide in the Windows 7 DVD and let it heal itself” some might argue. But I thought that those times were over. wouldn’t be the first time to witness Windows shooting itself for good. Casualties happen, and what else could ‘ve happened except for finally giving up … rrright, the Windows 7 update. Pretty sure after running it on flashing SMART events since over a year already. Uncertain about the real cause, thus definitely certain about the Windows 7 repair start up tool not finding any operating systems on the plate from where Windows 7 tries to diagnose itself … stop right there! My Windows 7 based DAW shot itself by updating. Not an unusual view in Sony’s / MAGIX’ ACID Pro What happened Even the Sony to Magix transition you can neglect with minor path adaptation. This solution might work for all versions of ACID, as I assume they kept the caching method throughout its lifetime.
0 kommentar(er)
