A short time ago I realized that with S1 I am yet again playing "Guess.". I have repeatedly reinstalled the plugins in question with their latest versions from their respective publishers, rescanned VSTs dozens of times, reset the blacklist dozens of times, removed ttings from the Roaming profile, and rebuilt the song from scratch.
CUBASE 10 PRO ACOUSTIC FEEDBACK NOT WORKING WINDOWS
I have examined the Studio One.log for anomalies, and the Windows Event log for warnings or errors.
It's fast and the CPUs are always idling. This is a dual Xeon E5-2620 with a 1TB drive C, 512GB M.2 (drive E), 4TB drive F, four 28" displays running 128GB RAM, Avid Eleven Rack for sound (via USB), and a partridge in a pear tree. Please don't request how much RAM, or do I have enough disk space, yada. Unless anyone can shed any light on this issue I'm going to try Cubase again (I've absolutely had it with Avid/Pro Tools). I purchased S1 Pro last week and was excited with all of the wonderfull features but have spent so much time futzing around to just get a project going that I'm done. I do this to relax, have sunk thousands of dollars into gear and (mostly) software, but all of the current mainstream DAWs leave me flummoxed saying "what the h***?" What the heck's the matter with a few of these big guys? Reaper and Reason run rock, rock, rock solid. I spend more time troubleshooting DAWs than making any music. I feel that yet again I must play "guess what's wrong". One of the most painful things with Pro Tools is the way the Avid dev team makes you play "guess what happened" and bails requiring a system reboot with no inkling as to the cause. I am a Pro Tools user of sixteen years and am very impressed with Studio One 3 and want to make the switch. Over the last four days I am up to 5e and am calling it quits. I save my sessions (backup) using a numbering technique - Song 1a, Song 1b. I have the latest Studio One (3 3.1.1) installed, all O/S patches are current as of this moment (Win 8.1 圆4). To summarize, I have no problem adding plugins when only using a few tracks, but as the track count grows, VSTs suddenly do nothing when added using the "plus" or dragged and dropped as an insert on an existing track or to a new track. The plugins that behave this way are everything from Slate Virtual Tape Machines to Sonnox Suppressor to FabFilter Pro-MB to UAD EMT 140, and a half dozen others. I have methodically cut out half the tracks repeatedly to zero in on the "culprit" but only after getting my ~50 tracks, folders, and busses down to a single track, can I finally instantiate the plugin. I fought with S1 for the past four days trying to determine what plugin or track is corrupting the project to no avail. I have scoured the Internet for any one else reporting this problem but came up empty handed. I open my song and most work but then some suddenly won't add. I open a new song file, and have no problem inserting the plugin. I created my first song, imported the multi-tracks, created folders and busses, and then.
0 kommentar(er)
