![]() ![]() I’ve already reinstalled cubase twice and windows once, in order to fix cubase issues. As soon as it hits the first note of the song in realtime export I get the cpu-overload message, non real time export results in notes off time, missing time ect as stated above 9,000 times. and rendering it in some autistic down-syndrome manner. So technically there are two issues now I guess. However there are a few points where the song is getting “spliced” - not asio peaks, not overloads, just missing time of the song around quarter note-ish length so…yeah unacceptable sounds off time and stupid just like the non-realtime export, which makes sense since it’s a freezing is essentially the same thing, a non-realtime export… Start a new project, import said tracks, export stereo mix down. And I thought phase issues where going to be my problem today…Ī work around would be to freeze the tracks. ![]() I’m about 3 hours deep into solving this problem. ![]() I’m a gamer also so my computer (windows settings/bios settings) is optimized for performance. Froze it, still overload.ĭecreased export to 8 bit just for a laugh, cpu overload.īefore anyone asks or recommends to me…here is how I’ve been working with cubase:Īctivate steinberg audio power scheme = UNCHECKED I deleted EVERYTHING but 1 single vst/intrument/track. I tried freezing tracks then exporting, cpu overload. This had the exact same affect during PLAYBACK as the non-realtime export, notes off-time, legato not triggered ect, restarted cubase playback at 2048 sound correct. I changed buffer size to 2048 (using ur22) from 1024. Non-realtime export results in off time notes and some midi data not being triggered (ie legato of my strings). I’ve tried every work around and encountered the same issue or a new one.įor example realtime export results in cpu overload message. I use a DEDICATED 7200rmp WD black drive for my sample libraries. I have 16 gigs of ram, this project is barely using any. In real time play back CPUID HWMonitor is showing I never go above 20% cpu usage on any core (AMD FX8350). I don't think the fresh install resolved anything.I have a song that I’m working on which is all vst instruments and a few reverb plugins as well. My conclusion then is that the focusrite control panel and Resolve can't work it out amongst themselves the proper samples, and maybe 17.1.1 also addressed some of the issues. ![]() Then, I decided to uninstall the focusrite drivers, restarted the PC, opened resolve, and did a stress test on a full edit with 9 video tracks and 7 audio tracks at full res HD, and I am happy to report that it's recording fine.I plugged the 2i2 with focusrite drivers installed, 48khz and 512 samples, and I was still having pops and cracks.I plugged in ATR 2100 only, patched it, and audio was recording fine.Support made it sound like some of the bugs fixed in the latest version are around the audio issues we have all been reporting, so I did another set of tests: I did a fresh reinstall deleting all user prefs in the process as suggested by the support team, but I was still having crackle issues. Hi I've been in touch with the resolve support team (and continuing the discussion over the fact that I can't select multiple audio interfaces as inputs), and it seems that I've finally got my 2i2 3rd gen working properly with Resolve Studio 17.1.1 on windows ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |