• SONAR
  • X3e/Concrete Limiter: Clicking CL's blue power button makes scratchy noise. Confirm? (p.2)
2014/06/03 13:54:02
Beepster
John
Are you playing back when you turn on the CL? 
 
 
Edit: Just tried it to confirm for me. No click or any other noise and I can't recall a sound when ever using the CL.




Hiya, John. How ya doin'? Thanks for checking and yes it's while playback is running. Like I said it's an a/b'ing issue. For this particular plug I guess it's not a HUGE deal unless I'm only using it really lightly and need to hear a nuance but I reported it in Alex' thread and he asked for a new thread. Still scritchy scratchys bug me and reminds me of the old days on my XP system when it seemed like everything did that. Drives me nuts.
 
CakeAlexS
Thanks I'll check it out. What's that setting in preferences? I'll do the test again if it's different (I'm running full scandisk right now so I'm out of action).



I've been procrastinating since my weatherstripping failure earlier but I'll fire up the rig to test this out again and I'll find the setting. I think it's under recording/playback. I don't see how it could effect the PC modules but it is a really nice option.
 
Leadfoot
Maybe you need to spray some contact cleaner on it? Sorry... I know that wasn't helpful.



Lol... and that's pretty much exactly what it sounds like. Fortunately it's not ear blastingly loud.
 
And one Helpful vote goes to LF. lol
2014/06/03 14:00:35
tKx5050
There was an 1.1 update/patch to CL soon after it came out. Might check that your account doesn't have two versions. Don't know how they sell it now.
2014/06/03 14:09:58
Beepster
tKx5050
There was an 1.1 update/patch to CL soon after it came out. Might check that your account doesn't have two versions. Don't know how they sell it now.




Interesting. There were two entries for the CL in my account after I purchased it. I can't recall exactly what happened but IIRC both had download links but one of the entry's dl link caused an error. After about ten minutes my s/n and reg codes showed up on the other one and that's the one I dl'd and installed.
 
That may be it... maybe. Firing up the rig now to see if perhaps the problem disappeared. If no one else is experiencing this though then I may have other issues... and perhaps I am on the wrong version.
 
Thanks for the heads up. Cheers.
2014/06/03 14:28:16
Splat
Right click any empty grey area in the CL and select about in the context menu. I get 1.0.1 which I think it the latest?
 
I searched for the setting under X3 preferences not sure which one.

Thanks...
2014/06/03 14:31:56
John
Really good point I also have the 101 update. It came out not long after CL was offered. It is an important update. 
2014/06/03 14:32:11
Beepster
CakeAlexS
Thanks I'll check it out. What's that setting in preferences? I'll do the test again if it's different (I'm running full scandisk right now so I'm out of action).



The setting is in Preferences > Audio - Playback and Recording: Fade On Start/Fade On Stop
 
Anyone not aware of this setting, especially those who use high gain stuff like I do, REALLY should play around with it. It is an ear/monitor saver.
 
I have my Fade On Start set to 30ms and Fade On Stop set to 10ms. I do not experience and crunchiness when starting/stopping playback even with tons of heavily distorted guit tracks and blasting drums or whatever at these settings. If I turned it off it would be really freaking bothersome.
2014/06/03 14:55:48
Beepster
Okay... this just got about a million times weirder and it has reminded me of another "bug" that has been annoying the hell out of me for ages... but I'll leave that bug for last.
 
First off I AM on the 1.0.1 release so that's good (thanks for pointing that out though).
 
So I'm using my Pre Master for this test. I feed everything into this and treat it like my master except do my whole mix processing there, instead of the master. Well I inserted the CL and started clicking away at the power button. I was getting a little glitch but not the scritchy scratchy. It was more of a skip like my latency settings were too low so I opened the Scarlett panel and changed them. That totally screwed up Sonar and gave me like heavy digital distortion munchkin playback (changing the ASIO buffer from the panel with Sonar open has always caused problems so I usually close Sonar before doing it but never had the munchkin thing before).
 
Anyway I close Sonar and reopened and tried again with the lowered ASIO buffer setting. I started clicking the power button on the CL and it was still giving me that little skip (but not the scritchy scratchy). So I wanted to test out Alex's thing to see if the other modules would make noise when clicking the power button and they DID!!! I had never had that before and I was totally flipping out!
 
THEN I realized the Prochannel Strip's MAIN POWER BUTTON wasn't even ON!!! Those glitches were happening with the PC COMPLETELY TURNED OFF!!! When I turned the PC strip back on... get this... when I would click on the power buttons of the OTHER modules that had just been making noise with the strip OFF (Quad Curve, Console Emu, CA2A, etc...) they no longer made ANY noise when clicking their power buttons! WTF?! So I tried the Concrete Limiter's power button and the scritchy scratchy noise came BACK (when it was a skip noise with the whole strip turned off) except there was a new sound like an old cassette deck being turned on/stopped in a weird way (like the tape noise of it being played back ultra fast or something). SO I think MAYBE that has something to do with an instance of the tape sim I introduced somewhere else in the chain the last time I worked on the project.
 
Wow. Crazy. I'll have to do some more tests and go back to a version without the Tape Sim. This may actually be a TS problem.
 
Could that thing actually mimic the sound of a bad start/stop of physical tape? Because that is a really dumb thing to emulate. lol
2014/06/03 15:03:46
Beepster
Oh and that old bug I was talking about is the fact that the Page Up/Down buttons do NOT work in the Prochannel Inspector for scrolling as they should unless I click on empty space in the Quad Curve or one of the older compressor modules. If I have to scroll using Page up/Down (which I always do for reasons I'll explain later) and I only have the CA2A or the CL or the CE or any of the newer stuff it refuses to scroll.
 
Now I have been told many times to simply use the scroll wheel BUT I use a fancy trackball on my DAW and the scrollwheel is screwed up and doesn't actually scroll anymore. So I rely on keyboard scrolling instead. Otherwise I need to attach a mouse to the DAW specifically for scrolling which is annoying and stupid. I work around this by always trying to find grayspace on one of the modules that do allow PgUp/Dn scrolling in the PC but if those modules are offscreen I have to collapse something to gain access to them. It kind of sucks. Also if I click on the wrong spot I can accidentally activate a control on the module and my PgUp/Dn screws up a parameter. but I've gotten good at avoiding that.
 
So... yeah, maybe the PC PgUp/Dn thing is a bug.
 
These things are all workable though. I just figured as long as I had the bug accountant here I might as well mention these things.
 
Cheers.
 
2014/06/03 15:15:25
scook
Beepster
I use a fancy trackball on my DAW and the scrollwheel is screwed up and doesn't actually scroll anymore.

Have you tried cleaning the scrollwheel?
2014/06/03 15:22:23
Beepster
scook
Beepster
I use a fancy trackball on my DAW and the scrollwheel is screwed up and doesn't actually scroll anymore.

Have you tried cleaning the scrollwheel?




I need to buy some contact cleaner for the DX-7 at some point anyway so there are a ton of other things that need some TLC... I'll add the the trackball to the list but I think it is too far gone at this point.
 
I have another base of the same model but it had button issue IIRC. Seriously I just need to buy another one but they are like $100. Awesome device though and the trade off between this PC issue or having to use an actual mouse (which I despise... especially for audio) doing the workarounds is easier.
 
I'm probably the only one who has this issue but I should report it I guess. It is indeed a bug. Just not a major one.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account