2. tech-talk
  3. 155720-104029

Weird problem noticed today...

This has never happened before but in my Bluesound Node 2i today there is - I can it descrbe is as - bass slap or pop, I think just coming from the left Maggie. I pretty much only play loud. My subs are right behind the Maggie (16" or so) and it's definitely coming from the Maggie. Now the DAC on the Bluesound has a lot more boomy bass than the CD player DAC - Yamaha Aventage BD-A1060. So I am thinks my it's signal-related but perhaps it's the Maggies only they are not being driven hard in those frequencies enough to make that horrible sound. BluOs just did an update that is only major change to system today. I probably hadn't played music on a couple weeks and BluOs asked me to do update then I noticed problem - could be coincidental though could this be an amp or preamp issue?
Thoughts?
Cheers
John
jkf011
jkf011 OP
268 posts
 
1.7i
mofimadness's avatar
mofimadness
4,933 posts
 
When you asked "if the ribbon "slapping" is fatal"?  I assumed you had a separate ribbon tweeter, (like a 3.6/3.7/20.7) which would be weird if that was slapping.

The 1.7i is a quasi ribbon panel, not a full separate driver, so no, Maggies will slap if over driven.  You really should try to avoid that, but it's not fatal.
jkf011 OP
268 posts
 
Well that's the weird part. We'll see gotta do that testing. As it wasn't being driven any more than it has for 2yrs and suddenly slapping. 
mofimadness's avatar
mofimadness
4,933 posts
 
Also weird is you said that it doesn't do it with CD, right?  Do you have any other source to try?  I'm sure the Node2i and the CD don't have the exact same output voltage, but they should be close.

If you have a sound pressure meter, maybe measure the output with both sources to make sure they are matched.  You might just be over driving the speaker with the Node2i as the source or maybe with the update, they somehow increased the output a little?

Logic tells us, (thanks Spock) that if the only source that is causing this to happen is the Node2i, the issue's gotta be with that source...
jetter
2,952 posts
 
I would also add that as with the poster above the recent Node2i update resulted in no negative consequences at this end.
More to discover