Sonar Platinum Memory Leak and dropout issues (22.06 and 22.07)

2016/08/05 06:29:34

fireberd

Sonar Platinum does not need to be run in a Compatibility Mode. Whoever posted that is all wet. It is fully Win 10 compatible. I've been running it in Win 10 for over a year.

2016/08/05 07:14:53

pwalpwal

Soulburned
UPDATE:
Alright... last trick up my sleeve. Someone in the Cakewalk Sonar User Group on Facebook mentioned they noticed when they happened to do a Compatibility check in Windows 10, that Windows suggested to run in Compatibility mode for Windows 8.

Just now testing this... Dunno why I didn't think of it sooner.

HOLY CRAP. NO MORE MEMORY LEAK! NO MORE STATIC CREEP!!! That just solved everything.

Going through and re-enabling as much as I can just to test drive and I'm able to have my complete processing chain live without issues. So odd.

i just ran the compatibility checker, with no such result, ie, windows didn't set a compatibility mode (win10pro, sonar04.2016) - could it be driver compatibility? is win10 up to date?

2016/08/05 07:20:10

pwalpwal

maybe the latest driver will fix it (3118 is newer than the one you posted)? drivers were updated recently https://www.rme-audio.de/en/downloads/driver/fireface.php

2016/08/05 07:45:21

Hatstand

probably a dumb suggestion as you seem to be extremely thorough, but have you run LatencyMon?

2016/08/05 07:59:57

Soulburned

Hatstand
probably a dumb suggestion as you seem to be extremely thorough, but have you run LatencyMon?

Haven't used LatencyMon in ages but I'll give it a shot again.

pwalpwal
maybe the latest driver will fix it (3118 is newer than the one you posted)? drivers were updated recently https://www.rme-audio.de/en/downloads/driver/fireface.php

Double checked it. Windows Device Manager reports 3.1.18 while the Fireface.exe (systemdir) still shows 3.1.16, hence the version mentioned above. I check their drive page weekly so I knew I had the latest downloaded. That indeed may be an issue but so far Sonar is running completely stable in Compatibility mode for Win8.

I also went through every driver model available, switching from ASIO to WASAPI, to WDM/KS and never saw the stability return, the RTL just went through the roof (which would be fine if I were mixing).

2016/08/05 08:12:01

Soulburned

UPDATE: wiped the Drivers for the Fireface and clean installed 3.118. Running SPlat normally (as administrator of course) still yields the memory climb and static creep. Compatibility mode is certainly what seems to do the trick to getting everything running smoothly again. My processing chain barely pushes my CPU past 13% under load so it doesn't make any sense why playback audio stream gets so much glitch/static drop-out behavior aside from the fact that it apparently is a memory address issue when the memory climbs up to 18+gigs and constantly dumps and refills - continually degrading the playback quality.

2016/08/05 08:13:01

pwalpwal

still puzzled as to why win10 recommends compatibility mode - firewire chipset? (& driver?) bios? weird...

2016/08/05 08:19:12

dcumpian

I will say, running plugins while tracking is a recipe for disaster. I understand why you are doing it, but I would strongly suggest that you use hardware for that until the raw tracks are recorded. Once everything is in the box, that's when you can start adding plugins to begin the mixing process.

Regards,
Dan

2016/08/05 08:21:56

pwalpwal

dcumpian
I will say, running plugins while tracking is a recipe for disaster. I understand why you are doing it, but I would strongly suggest that you use hardware for that until the raw tracks are recorded. Once everything is in the box, that's when you can start adding plugins to begin the mixing process.

while that's generally true, the op's issue only appeared after the 07 update

2016/08/05 08:29:31

Soulburned

Me too. It's an onboard FW 400 port. VIA chipset is reported (Driver version 10.0.14393.0).

Sonar Platinum Memory Leak and dropout issues (22.06 and 22.07)

Use My Existing Forum Account

Use My Social Media Account