Cedar dns one hasp key issue

[Cryos]

I thought I did, I'm willing to try it again that's for sure.

ill keep you posted.

[Cryos]

Follow up regarding distortion issue when using LM setting:

I trashed absolutely everthing regarding CEDAR, prefs, caches etc....in user library and main root library.

Problem seems to still exist. When I put the CEDAR into the LM mode the moment I raise the threshold when all the other faders are down it starts to give me crackle. It's worse on certain types of material than on others. I've fiddled with every parameter that's available in the mode and it doesn't seem to make a difference.
Major drag cause the LOW MID setting is great for removing tons of scrap in that frequency range.

I'll have to notify CEDAR, this could strictly be limited to the Mcabook pro I'm using or not.

[Basstian]

could not make it happen here in l&M Mode.

works as exspected

[bad jitter]

^ What's I&M mode?

DNS One is most prone of any of my (very many) plug-ins to stop working after any OSX updates or other changes in my system. It's a pity, because it's one of my most needed plug-ins. Sometimes I miss my DNS2000.

[Cryos]

"L&M" Mode is the Low+Mid selector on the DNS ONE specifically affects frequencies between 20Hz and 6kHz.

I'ld love to hear back from more folks using the new DNS ONE update whether their experiencing crackly audio when passing audio thru in the L&M mode.

I'm wondering if this is somehow related to my hasp key? Or is this MacBook pro related?

[Cryos]

The good folks at CERAR have sent me a new HASP key in an effort to hopefully solve my recurring HASP KEY disconnect issue. I'm crossing my fingers this solves it.
Cheers

[Brandonx1]

Have you tied a powered USB hub? Also I was having the clicking/crackling issue as well and 4.3 solved the issue 100% for me. When I was having the cracking issue, I could disable and the enable the plug in to make it stop. Hope this help.
Best
Brandon

[Cryos]

follow up: the great folks at CEDAR swapped the HASP Key for a new one, (I'm not sure whats different since the last time they did that for me), nevertheless all timeout issue seem to be fully resolved.

Cheers

[Cryos]

Just came across a new error... Hasp Sentinel Runtime SRM error message when launching protools.. ( This is happening on a Mac mini with an Elgato hub attached) I discovered that the hasp key wasn't being seen when the elgato thunderbolt device was attached... Apparently there are thunderbolt and hasp key issues which cedar is aware of... I came across this error months back when trying to run a deck link black magic card via a thunderbolt chassis... I abandoned the whole idea of doing this since I kept getting the same error regardless of installing a new sentinel driver nothing changed.... CEDAR input to the whole issue was nominal. Apperantly this is all due to the hasp key copy protection software where iloks don't cause this issue at all.
I've been I touch with CEDAR tech support and I was told the standard story: "it's not us but the 3rd party peripheral driver" .. However what's truly interesting is the Elgato doesn't need a driver, it's built into to mac OS!! Same foe all the other thunderbolt devices I ha e attached.. I was later informed I'm not alone experiencing this issue and according to text support there is a NEW HASP KEY that supposedly resolves this issue.... However I'd have to pay for the new key....

What I find irksome is that they know the issue exists... They Never send out bulletins to end users and then want us to pay for a new key... Without may I add, a guarantee this will resolve the issue... Anyways I'll keep you posted as to what happens and how it goes down... Perhaps it's a $30 fix which I'll be happy to pay for a new key without issues or maybe not