MANTRASKY
Max Output Level: -87 dBFS
- Total Posts : 170
- Joined: 2009/01/31 18:11:40
- Location: Cleveland, Ohio
- Status: offline
Problem after upgrading to 2016.04
Hello, after upgrading to 2016.04 it seems that my "Addictive Drums" have major Drop Outs? When I try to load Cakewalk LP EQ or MB, onto a dedicated Bus the drums drop-off and on through out the song. I've tried both on a track or bus and the same thing happens, the rest of the song (s) is not effected. I was hoping if anyone else had this happen and was able to resolve the issue?
Help is much appreciated!
Thank You.
|
Re: Problem after upgrading to 2016.04
2016/04/27 17:15:43
(permalink)
☼ Best Answerby MANTRASKY 2016/04/27 17:44:33
Hey MANTRASKY, If you press the Expert button one the EQ or MB and switch the precision to "Nonlinear" do you still get these missed notes?
|
MANTRASKY
Max Output Level: -87 dBFS
- Total Posts : 170
- Joined: 2009/01/31 18:11:40
- Location: Cleveland, Ohio
- Status: offline
Re: Problem after upgrading to 2016.04
2016/04/27 17:32:28
(permalink)
The Nonlinear "WORKED!!!!!"
Thank You Very Much.
|
microapp
Max Output Level: -77 dBFS
- Total Posts : 653
- Joined: 2013/10/31 12:21:31
- Location: Wondervu, CO
- Status: offline
Re: Problem after upgrading to 2016.04
2016/04/27 17:46:54
(permalink)
☄ Helpfulby Thedoccal 2016/04/27 18:29:23
What you are doing is reducing the load on the PC to the point where it has enough time to process the midi.
The non-linear mode of the linear phase vsts is not so processor intensive.
A better solution is to increase the 'prepare using milliseconds' to 1000 in the midi settings.
When midi notes are dropped, this is usually the solution.
Then you should be able to use LP mode in the vsts.
Sonar Platinum, Cubase Pro 8.5, Reaper 5, Studio One 2Melodyne Studio 4, Finale 2012I7-5820K 4.5GHz, 32 GB DDR4-2800,3 monitors,Win 10 ProToshiba P75-A7100,l7-4900 2.4 Ghz/8MB Win 8.1 ProTascam FW-1884, Emu 0404USB, CMC-AI,Axiom 61Yamaha HS-50's, Sony SA-W2500, Sennheiser RS170's, ATH-M50Ibanez Jem7VWH, RG-1570Jackson DK2-S(Sustainiac),Les Paul CustomDigitech Valve-FX, GFX-1,TSR-24,RP-90
|
Thedoccal
Max Output Level: -85 dBFS
- Total Posts : 290
- Joined: 2014/10/12 16:43:08
- Location: Joshua Tree, CA
- Status: offline
Re: Problem after upgrading to 2016.04
2016/04/27 18:12:25
(permalink)
"A better solution is to increase the 'prepare using milliseconds' to 1000 in the midi settings."
Just changed my 250 setting to 1000 and I think my unrelated stability problems were just solved...thnx.
|
orangesporanges
Max Output Level: -84 dBFS
- Total Posts : 342
- Joined: 2007/02/22 16:13:05
- Status: offline
Re: Problem after upgrading to 2016.04
2016/04/28 00:36:28
(permalink)
Great thread. I was experiencing some glitchy problems with the new eq and even opened the expert mode, didn't look for the non linear, button. Takes some of the load off, thanks.
Sonar Platinum, Windows 10 64bit, 3.4ghz i7CPU, 16gigs RAM, 1x 1TB SSD system drive 1 x 1TB HDD ( audio only)
|
skitch_84
Max Output Level: -81 dBFS
- Total Posts : 480
- Joined: 2012/09/23 07:14:47
- Location: Okayama, Japan
- Status: offline
Re: Problem after upgrading to 2016.04
2016/04/28 00:38:13
(permalink)
Isn't the linear phase functionality part of what differentiates this EQ from a standard EQ and makes it more suited to mastering? If you switch to non-linear mode, is it still suited for a mastering situation?
Chris Porter www.cportermusic.comListen to my original work on Soundcloud and YouTubeGet my original soundtracks on Bandcamp Sonar Platinum "2017.04", Windows 10 64-bit, ASUS Z170-A, i7 6700K (4.0GHz), 32GB DDR4 RAM, 250GB SSD 850 EVO (OS/Sonar/Plugins), 1TB SSD 850 EVO (Sample Libraries), 3TB WD Black HDD (projects/audio), Noctua NH-D14 Cooling Unit, PreSonus AudioBox USB Interface, M-AUDIO Oxygen49
|
JoeHans
Max Output Level: -88 dBFS
- Total Posts : 149
- Joined: 2011/05/03 07:59:54
- Status: offline
Re: Problem after upgrading to 2016.04
2016/04/28 01:42:36
(permalink)
skitch_84
Isn't the linear phase functionality part of what differentiates this EQ from a standard EQ and makes it more suited to mastering? If you switch to non-linear mode, is it still suited for a mastering situation?
You should use the lp mode when mastering. I think it is good idea to make the mastering in a different project so you have more CPU to deal with the heavy plugins like LP EQ.
Sonar Platinum running on: Intel i7-2600k, ASUS P8Z68-V Pro, Kingston V300 SSD 240GB + OCZ 60GB SSD + Samsung 1TB HDD, 16GB Ram, E-MU 0404 USB
|
sjd
Max Output Level: -89 dBFS
- Total Posts : 52
- Joined: 2010/01/08 06:47:12
- Location: Fife, Scotland
- Status: offline
Re: Problem after upgrading to 2016.04
2016/04/28 09:28:33
(permalink)
Hi
I experienced drop outs with AD2 also using the new LP MB after swapping out the older LP64 MB in a project to 'play around' with the new plugin.
If I swap back to the old LP64 MB the drop outs stop.
Therefore conclusion is the new plugin causes this.
Not switching off LP mode as that is the whole point of the plugin!
I haven't had to change the 'prepare using milliseconds' MIDI settings before. Increasing does fix the drop outs. (now 500 from 250)
Are there any repercussions for increasing this setting? I use a lot of virtual instruments.
Cheers
SJD ------------------------------------------------------------ SPLAT, Win 10 x64, i7 4GHz, 16GB RAM
|
Re: Problem after upgrading to 2016.04
2016/04/28 09:59:43
(permalink)
Hey guys, This doesn't have to do with the plugins themselves. This is a product of all plugins with high latency. These mastering plugins on the Linear Phase modes have very high latency induced which is why you see this problem.
The prepare using milliseconds midi setting can be used to remedy this.
The reason I asked if the nonlinear mode fixed this is because the nonlinear mode does not induce any latency.
|
microapp
Max Output Level: -77 dBFS
- Total Posts : 653
- Joined: 2013/10/31 12:21:31
- Location: Wondervu, CO
- Status: offline
Re: Problem after upgrading to 2016.04
2016/04/28 12:34:05
(permalink)
Logan,
Yes I understand this as my first reply indicates.
Why did you not reference the midi buffer fix ?
It is fairly well known on this forum.
SJD,
prior to Platinum the default 'prepare using' was 500.
Cake changed it to 250 in Platinum.
I and many others simply set it to 1000 and be done with it.
To my knowledge , 1000 has caused no issues.
Why the default value of 250 remains is a mystery to me.
It seems like such a simple thing to change and causes much grief.
Sonar Platinum, Cubase Pro 8.5, Reaper 5, Studio One 2Melodyne Studio 4, Finale 2012I7-5820K 4.5GHz, 32 GB DDR4-2800,3 monitors,Win 10 ProToshiba P75-A7100,l7-4900 2.4 Ghz/8MB Win 8.1 ProTascam FW-1884, Emu 0404USB, CMC-AI,Axiom 61Yamaha HS-50's, Sony SA-W2500, Sennheiser RS170's, ATH-M50Ibanez Jem7VWH, RG-1570Jackson DK2-S(Sustainiac),Les Paul CustomDigitech Valve-FX, GFX-1,TSR-24,RP-90
|
microapp
Max Output Level: -77 dBFS
- Total Posts : 653
- Joined: 2013/10/31 12:21:31
- Location: Wondervu, CO
- Status: offline
Re: Problem after upgrading to 2016.04
2016/04/28 12:54:23
(permalink)
skitch_84
Isn't the linear phase functionality part of what differentiates this EQ from a standard EQ and makes it more suited to mastering? If you switch to non-linear mode, is it still suited for a mastering situation?
Yes, LP mode is primarily for mastering due to the high latency introduced in the linear phase intensive calculations. LP mode is not as important in the mix where EQ is more for getting a particular sound or making room for other instruments in the mix. The non-linear mode introduces (sometimes drastic) phase shifts in and near the pass band. THe phase shifts can wreak havoc on a carefully tuned low end or subtle stereo placement. Most EQ's are non-linear. Hardware EQ's actually work by manipulating phase. But once your mix is sounding good, you don't want to dirty up the phase relationships in the mastering step. So use non-linear for mixing. Linear for mastering.
Sonar Platinum, Cubase Pro 8.5, Reaper 5, Studio One 2Melodyne Studio 4, Finale 2012I7-5820K 4.5GHz, 32 GB DDR4-2800,3 monitors,Win 10 ProToshiba P75-A7100,l7-4900 2.4 Ghz/8MB Win 8.1 ProTascam FW-1884, Emu 0404USB, CMC-AI,Axiom 61Yamaha HS-50's, Sony SA-W2500, Sennheiser RS170's, ATH-M50Ibanez Jem7VWH, RG-1570Jackson DK2-S(Sustainiac),Les Paul CustomDigitech Valve-FX, GFX-1,TSR-24,RP-90
|
sjd
Max Output Level: -89 dBFS
- Total Posts : 52
- Joined: 2010/01/08 06:47:12
- Location: Fife, Scotland
- Status: offline
Re: Problem after upgrading to 2016.04
2016/04/28 12:58:12
(permalink)
Thanks microapp.
Advice much appreciated.
I'll change to 1000 from now on.
Cheers
SJD ------------------------------------------------------------ SPLAT, Win 10 x64, i7 4GHz, 16GB RAM
|
jpetersen
Max Output Level: -61 dBFS
- Total Posts : 1499
- Joined: 2015/07/11 20:22:53
- Status: offline
Re: Problem after upgrading to 2016.04
2016/04/30 17:42:11
(permalink)
microapp
Why the default value of 250 remains is a mystery to me.
It seems like such a simple thing to change and causes much grief.
IIRC, the default IS higher but only on fresh installs. (I don't know what the default value is) When users install over existing versions they mostly elect to keep the existing configuration values and for this reason the old default is taken over, version-for-version. It would be pretty annoying if a user needed it set at 2000 and with every upgrade it was set down to, say, 500 again.
|
scook
Forum Host
- Total Posts : 24146
- Joined: 2005/07/27 13:43:57
- Location: TX
- Status: offline
Re: Problem after upgrading to 2016.04
2016/04/30 18:03:01
(permalink)
The MIDI prepare buffer default was changed from 500 to 250 with X1. The default value has not changed since then. FWIW, for years Noel has recommended not allowing SONAR to use previous version settings when updating. Fortunately it is not an issue with monthly updates.
|