Snapping sound on LAPD Citywide Dispatch feed? - Page 2

kma371 · #21 (**permalink**) 12-30-2012, 12:16 AM

Quote:

Originally Posted by parallax

And the crackling has once again returned. It's been there most of the day.

I'm sorry but is it affecting your monitoring that much that you need to update the rest of us? I'm not trying to sound like a jerk but I still don't understand the point of all this.

I don't hear anything. if its only happening on this one feed on your end, then contact them and let them know.

parallax · #22 (**permalink**) 12-30-2012, 4:06 PM

Quote:

Originally Posted by kma371

I'm sorry but is it affecting your monitoring that much that you need to update the rest of us? I'm not trying to sound like a jerk but I still don't understand the point of all this.

I don't hear anything. if its only happening on this one feed on your end, then contact them and let them know.

The point: I've been waiting for someone to reply (while I'm hearing the crackling) who says either: "Yes, I'm also hearing the crackling on BigEvil's Citywide LAPD feed." Or, "No, I don't hear any artifacts on this particular feed during the periods you are claiming to hear them."

I'll even attempt to make it clearer for you. My objective has been to learn whether these crackling artifacts are stemming from a problem at the feed's source itself, or whether they are symptomatic of a condition specific to my route path to said source (e.g., perhaps some type of intermittency relating to one of the hops between myself and the feed). It makes little sense to contact the feed provider before I'm armed with confirmation that this is likely a problem originating at the source or otherwise related to something under the provider's control. That's why I've been reporting the artifacts whenever I notice their presence and have been hoping for some confirm/deny feedback from others while I'm hearing them. Despite that they are appearing on a hugely popular feed, no one (including you) ever seems to respond and say anything relating to whether or not they hear the same crackling at the appropriate times.

So that's why I've continued to post status updates about the crackling on this feed. I think it's fairly straight forward. I have to say that I'm rather amazed you've had some difficulty understanding my obvious intent concerning my updates. It's a logical thing as I see it.

And by the way, the crackling vanished late last evening and remains nonexistent today. You or others will have to check for it and reply reasonably soon after I next report its presence, or after someone else does. That's the only way this can work and that we should involve the feed provider. I'm sure if it ends up being a problem on the provider's end, he will appreciate our efforts.

Kingscup · #23 (**permalink**) 12-30-2012, 4:33 PM

I checked the feed archives from yesterday and it appears to have a subtle popping/crackling noise. Here is your conformation. Now go ahead and report it to the feed provider.

kma371 · #24 (**permalink**) 12-30-2012, 5:07 PM

Well now there's no reason to get your panties all in a bunch. I myself have said TWICE that I wasn't hearing anything when you said you were, so that wasn't enough for you?

I have understood your intent all along but I think your being an little anal about it honestly.

Looks like I'm the only one that's even been attempting to communicate with you on this issue, no one else seems to care, wonder why....oh wait, I know. It's because it's not that big of a deal.

Quote:

Originally Posted by parallax

The point: I've been waiting for someone to reply (while I'm hearing the crackling) who says either: "Yes, I'm also hearing the crackling on BigEvil's Citywide LAPD feed." Or, "No, I don't hear any artifacts on this particular feed during the periods you are claiming to hear them."

I'll even attempt to make it clearer for you. My objective has been to learn whether these crackling artifacts are stemming from a problem at the feed's source itself, or whether they are symptomatic of a condition specific to my route path to said source (e.g., perhaps some type of intermittency relating to one of the hops between myself and the feed). It makes little sense to contact the feed provider before I'm armed with confirmation that this is likely a problem originating at the source or otherwise related to something under the provider's control. That's why I've been reporting the artifacts whenever I notice their presence and have been hoping for some confirm/deny feedback from others while I'm hearing them. Despite that they are appearing on a hugely popular feed, no one (including you) ever seems to respond and say anything relating to whether or not they hear the same crackling at the appropriate times.

So that's why I've continued to post status updates about the crackling on this feed. I think it's fairly straight forward. I have to say that I'm rather amazed you've had some difficulty understanding my obvious intent concerning my updates. It's a logical thing as I see it.

And by the way, the crackling vanished late last evening and remains nonexistent today. You or others will have to check for it and reply reasonably soon after I next report its presence, or after someone else does. That's the only way this can work and that we should involve the feed provider. I'm sure if it ends up being a problem on the provider's end, he will appreciate our efforts.

parallax · #25 (**permalink**) 12-30-2012, 5:11 PM

Quote:

Originally Posted by Kingscup

I checked the feed archives from yesterday and it appears to have a subtle popping/crackling noise. Here is your conformation. Now go ahead and report it to the feed provider.

Answer me this: From what point is the audio for the archive obtained? That's important. If it's taken from a remote location then the issue could still be routing-related.

parallax · #26 (**permalink**) 12-30-2012, 5:34 PM

Quote:

Originally Posted by kma371

Well now there's no reason to get your panties all in a bunch. I myself have said TWICE that I wasn't hearing anything when you said you were, so that wasn't enough for you?

Each time you reported hearing nothing I replied and expressed to you that the artifacts had disappeared and the signal was clean. As such, your comments weren't timely enough to be of much help. I suggest you go back in the thread and re-read a bit.

Quote:

Originally Posted by kma371

I have understood your intent all along but I think your being an little anal about it honestly.

As if your judgment is the ultimate standard on what's 'anal' and what's not. Give me a break. I know your type. People like you lay and wait for someone to pounce on with criticism in order to somehow make yourself feel high, mighty, and elite. That's kind of pathetic, bud.

Quote:

Originally Posted by kma371

Looks like I'm the only one that's even been attempting to communicate with you on this issue, no one else seems to care, wonder why....oh wait, I know. It's because it's not that big of a deal.

That's one of my main points. This is supposed to be a support category for feed listeners, yet some of them (like you) are pretty rude, and many of the others seem apathetic - it obviously doesn't bother them one way or the other. But the feed provider may not feel the same about that. Quit being so damn selfish and learn some common sense skills about troubleshooting!

kma371 · #27 (**permalink**) 12-30-2012, 6:42 PM

Quote:

Originally Posted by parallax

Each time you reported hearing nothing I replied and expressed to you that the artifacts had disappeared and the signal was clean. As such, your comments weren't timely enough to be of much help. I suggest you go back in the thread and re-read a bit.

As if your judgment is the ultimate standard on what's 'anal' and what's not. Give me a break. I know your type. People like you lay and wait for someone to pounce on with criticism in order to somehow make yourself feel high, mighty, and elite. That's kind of pathetic, bud.

That's one of my main points. This is supposed to be a support category for feed listeners, yet some of them (like you) are pretty rude, and many of the others seem apathetic - it obviously doesn't bother them one way or the other. But the feed provider may not feel the same about that. Quit being so damn selfish and learn some common sense skills about troubleshooting!

oh you know me so well I'm sure. I've been around these boards years and years and have helped plenty of people. without the need to make myself feel "elite" haha.

I was trying to help you if you re-read through the thread but then I wasn't sure why I continued.

really don't think I was rude at all but for someone as sensitive as you, I guess I can understand.

parallax · #28 (**permalink**) 12-30-2012, 7:43 PM

Quote:

Originally Posted by kma371

really don't think I was rude at all but for someone as sensitive as you, I guess I can understand.

Sensitive? I'm not sensitive, heh... I simply like to deal with facts.

So, lets see whether you've been rude or not...
In your very first reply to the thread, your wrote:

Quote:

Originally Posted by kma371

Sending a post to everyone doesn't help much

Based upon your above statement, you didn't even attempt to grasp what I was doing or why I was doing it. You simply made an uninformed snap judgment. A judgment which demonstrated your cluelessness fairly well.

Then later came your sarcasm...

Quote:

Originally Posted by kma371

I'm sorry but is it affecting your monitoring that much that you need to update the rest of us?

That's a sarcastic way of saying "we don't give a rat's a$$ about the noises you're hearing." I think a reasonable person would agree that you made a fairly rude remark there.

Then came more objection from you based upon your claim that you couldn't see any point in my efforts to elicit feedback...

Quote:

Originally Posted by kma371

I'm not trying to sound like a jerk but I still don't understand the point of all this.

In your above statement you again claim not to understand my point - which you proceeded to contradict in a subsequent post claiming that you understood my "intent" all along (that was after I clarified my intent for you, I might add). So which is it? You did understand what I was trying to do but claimed you didn't? Or you didn't understand what I was doing but suddenly realized you should have after I explained it to you?

Then finally, it certainly takes no Harvard Scholar to see that your "panties all in a bunch" and your "being anal about it" remarks were blatantly sarcastic as well as antagonistically rude. Be mindful, though, that this doesn't bother me in the slightest... I'm simply pointing out what an arse you've been ;-)

kma371 · #29 (**permalink**) 12-30-2012, 8:19 PM

and i see you like to drag things out too, just like your "snapping noise" issue haha.

parallax · #30 (**permalink**) 12-30-2012, 8:40 PM

Quote:

Originally Posted by kma371

and i see you like to drag things out too, just like your "snapping noise" issue haha.

Not really. I was just setting the record straight ;-) And, again, my artifact updates were because I wanted someone to confirm their presence while I was hearing them. I've since concluded that's not likely to happen here any time soon, though.

parallax · #31 (**permalink**) 01-09-2013, 1:22 PM

The crackling sounds have returned. They started at about 10:50 AM PST this morning. The stream was already active here when they began (it had been running all night long).

If you would rather not post confirmation that you currently hear the crackling sounds as well (it will be helpful if you do though), please simply ignore this post. Criticism helps no one.

Thank you.

Kingscup · #32 (**permalink**) 01-09-2013, 1:54 PM

Don't worry. I submitted the report for you. Hopefully, the feed provider will respond to your problem and the problem can be fixed.

mule1075 · #33 (**permalink**) 01-09-2013, 1:59 PM

I have listened on three different players on my pc and also the scanner radio app on my tablet.I am not hearing the crackling you describe.

BigEvil · #34 (**permalink**) 01-09-2013, 2:00 PM

Thanks for the comments, as the feed provider I figured I'd chime in here to see if we can't all find a solution here. I have noticed the intermittent popping/crackling sound at times (usually when a feed problem report is filed) but I can say with certainty it is not coming from the scanner. It appears to somehow start happening up randomly after running for a long while. I've began troubleshooting the cause and have tried different sound cards, different, cables, and it doesn't seem to stop the intermittent crackling from happening after the feed is up and running without interruption for days/weeks. The easiest, quickest, and failsafe way to fix it every time is simply to restart the machine providing the feed and somehow, poof, it goes away and is back clear as day. I'd imagine if you listen right now it's perfect (I just reset the machine remotely).

This is a brand new iMac with the latest software, using high quality streaming software, and the crackles (when present) ARE observed locally as well as remotely. I can't honestly tell you whether its software, server, or audio related but I appreciate the help in troubleshooting and strive to get you guys the best feed with the best sounding audio. Feel free to let me know how else I can improve it.

parallax · #35 (**permalink**) 01-09-2013, 2:11 PM

Thanks BigEvil. The crackling indeed vanished once you reset the equipment. I had not submitted a report to you personally because I was first hoping to get confirmation of the artifacts being heard elsewhere during the times I was hearing them. That proved a bit difficult to do, though.

I appreciate your attention to the matter. I enjoy your feed a great deal!