The problems with the edge are 1) too close for crash-boom and 2) almost surely would be spotted so close to walkway behind Charlie. But given that the walkway source was by far closest to the shot, and it gets progressively further away as sources shift more south really points to that area.
1 Like
Did you watch video where it is explained that Dairy Queen does not exists any more?
FYI,
The Shaffer security detail stopped working with Charlie Kirk in 2022. Greg Shaffer, who oversaw Kirk’s security from 2015 to 2022, confirmed this in multiple reports about the security arrangements before Kirk’s assassination in 2025
1 Like
Wrong, there is another ‘Youtuber’ cant remember his name, he went to the scene. He said where that pedestrian walked the path goes down at an angle. Thats why he appears to disappear.
2 Likes
Thanks for clarifying the difficulty in capturing a ‘bullet’ rather than a ‘smear’ on a 30 fps camera, but I still have a question: does a 30 fps camera take EACH frame over the full 1/30th of second (which would produce your 100ft long smear), or does it take a much faster exposure 30 times per second? (which could therefore capture a much shorter part of the bullets flight?)
1 Like
We discussed shutter issues here:
Global shutter takes a snapshot at once, but the cheap rolling shutter does it line by line.
Someone says there is another DQ.
1 Like
My results from live-is-driving. Shooter was between 40 and 100 meters.
1st: 0.049 sec
echo: 0.133 sec (45 m)
Oh, I converted it to .wav file first. Maybe there is a direct way…
FFmpeg (specifically
ffprobe) can extract audio data and output it in CSV format. You can analyze audio levels like RMS volume per frame and save the results to a spreadsheet-compatible file.
How to Extract Audio Stats to CSV with FFmpeg
To extract audio metrics such as RMS levels and timestamps, use
ffprobewith theastatsfilter and CSV output formatting:
ffprobe -f lavfi -i “movie=input.mp4,astats=metadata=1:reset=1”
-show_entries frame=pkt_pts_time:frame_tags=lavfi.astats.Overall.RMS_level,lavfi.astats.1.RMS_level,lavfi.astats.2.RMS_level
-of csv=p=0 > audio_stats.csv
Have you seen this analysis yet?
https://drive.google.com/drive/folders/17tevnZsbVxGKyoar-J4vjv2NhWGj0-J5
3 Likes
The bullet never exited, the wound to the front of his neck was without and doubt the entrance wound. The bullet was recovered from his body during the autopsy. Yes, an autopsy was in fact performed.
1 Like
I’m not big on Paramount Tactical, but I’m posting this to bring it to Chris’s attention.
That is incorrect. Go to Shaffer Security Group website and go to the current team group picture. You will EASILY see the guy on Charlie’s right side. He is with Shaffer Security Group. And furthermore, I have never seen any video of the CEO Shaffer saying they weren’t protecting Charlie.
Read for yourself. Maybe its not the same guy, or, he doesnt work for the Shaffer Security Team anymore.
Possible time line medical examiner, autopsy, to mortician.
at 14:30 Utah does not have to release the autopsy as a public record.
Jeff Ostroff has a good 30 minute long video debunking many of the ridiculous claims in the Charlie Kirk shooting.
- debunks the shadow in the video
- debunks the police investigation and the police tapes
- debunks the shot from behind theory
reinforces the bullet remained inside the body and there was no exit wound.
There is some video in this presentation that I had not seen previously.
Recommended.
Thanks for the supplementary documentation. There are subsequent videos about 5 recorded audio analysis.
I will study it “1 Charlie Kirk Audio Forensics.pdf”
1 Charlie Kirk Audio Forensics.pdf (1.2 MB)
Therefore, the combined evidence — impact → bang timing, TDoA bearings, and reflection geometry — converges on a shooter location in the south courtyard/corner sector, at a distance of ~50–95 m from Charlie. The Losee Center can be confidently ruled out as the origin, as it is incompatible with both the timing and geometric reflection patterns observed across all recordings.
When the range annulus from Charlie is overlaid with the bearing corridors from the microphone baselines, the two sets of constraints intersect in a single azimuthal sector. This zone falls in the south courtyard/corner sector, consistent with both timing analysis and reflection geometry.
The late ~600 ms “Losee” return (>100 m from the mics) confirms that the distant building surfaces only acted as higher-order reflectors, ruling them out as direct shot origins.
South? That is Charlie’s right?
@cmartenson But if the bullet came from his right, how the shotwound is on his left?
@sonjax6 I feel like another case of Texar’s revenge - where evidences contradict each other.
@offtheback, @greg_n Probably we should talk about group delay of signal processing. Maybe it affects the bearing/direction.
(Let me reveal my point of view. My educated people stubbornly ignore the delay caused by different signal filters - when compare two devices, when we don’t even know the filter type, nor the parameters. It is willful ignorance or deliberate avoidance.)
Here we don’t know what the recording devices were, what audio filters were applied. And the microphone itself is a filter to begin with.
Your suspicion is that group delay introduced by filters — possibly the microphone itself or subsequent signal path filters — may be skewing the timing, thus corrupting the bearing estimation.
A nonlinear group delay across frequency components (especially in wideband signals) can shift the apparent arrival time at each microphone differently, leading to incorrect bearing estimates — sometimes wildly so, depending on signal content and filter characteristics.
The Realities You’re Facing:
You’re dealing with:
- Unknown devices (phones of different brands and models)
- Unknown filters (mic characteristics, pre-processing, compression)
- No calibration
- Post-event analysis (from footage)
And if you’re comparing recordings from different phones, this group delay error is:
- Unpredictable
- Device-dependent
- Frequency-dependent
- Impossible to estimate accurately without metadata or lab measurements
This is the perfect storm for group delay mismatch, which directly affects TDoA and therefore bearing estimation.
So, To Be Very Clear:
- Your direction-finding results are unreliable if you’re using TDoA on unmatched, unknown, or uncharacterized devices.
- The more heterogeneous the devices (e.g., iPhone vs. Android, or even different models of Android), the worse this gets.
- Group delay, sample alignment, codec effects, and sampling rate drift all come into play.
Bottom Line:
Yes, your directional detection is very likely flawed — potentially deeply compromised — due to unknown and inconsistent group delays across different recording devices.
Suggested Framing (for reporting or internal discussion):
“Given the uncontrolled nature of the recording devices — including likely differences in microphone design, pre-processing filters, and unknown group delays — any directional inference derived via TDoA methods must be considered speculative. The risk of bearing distortion due to unaccounted-for group delay variations is high, and may render precise localization invalid.”
2 Likes
https://x.com/realgeorgewebb1/status/1974534871596069107?s=46
George continues to make a decently strong case for a Patsy involvement and it’s interesting hearing him say the FBI went to the dumpster behind where the car was seen in the parking lot 20 minutes after the shooting on the day they said they had no leads… how are they already tracking that vehicle?
Also I saw a post on here about the Dairy Queen there are two Dairy Queen‘s one by UVU one by Utah State George thanks the dismantled Dairy Queen is the real meeting point and they just keep pointing to the one still in operation saying see search the cameras there’s nothing here. The cameras that would actually show anything are part of the dismantled Dairy Queen that was closed down immediately after the shooting.
1 Like
Warren Smith interviews Officer Tatum who says he saw the autopsy information.
(28m15s)
A few takeaways that caught my attention that Tatum claimed:
- Neck wound you see is an entrance wound
- Round did hit Charlie’s spine
- Gun does not appear to have been disassembled
- Evidence points to him carrying the gun off the roof and jumped down with it
- Shoes matching shooter left impression at the jump down spot
He also made claims about digital forensics that are somewhat inaccurate. He mentions that sound like you cannot delete data on a phone. That’s not quite accurate. Most systems delete by erasing the fact the space is used for something important, then it ignores that spot, rather than deleting it. That spot could be used for real data, later, so it’s not actually guaranteed to recover data since the beginning of time, but you can recover more than you’d think. There’s also logs on remote servers/phones/computers.
Per AI summary:
Title: Autopsy Confirms Bullet Entry and FBI Evidence
Lead: The speaker asserts that an autopsy was performed, detailing the bullet’s path and confirming extensive forensic evidence held by the FBI.
Body:
- The autopsy identified the entry wound, bullet trajectory from neck downward, and fragmentation details.
- The bullet remains lodged in the body; investigators can specify what tissue was severed.
- Autopsies are mandatory for investigatory deaths in the United States, with no known exceptions aside from natural‑cause cases.
- FBI investigators collected shoe impressions, DNA on a towel and gun, and matched them to the suspect.
- The FBI’s Salt Lake City division handled evidence collection, chain of custody, and laboratory analysis separate from the DC office.
- Claims that no autopsy occurred are labeled as ignorant or conspiratorial by the speaker (claims).
- The defense reportedly waived a preliminary hearing, acknowledging sufficient prosecutorial evidence (asserts). (Per John Goodwin: Listening to video, he walked this point back)
- The speaker warns that public dissemination of investigative details could taint jury perception and affect admissibility.
- He emphasizes reliance on official forensic findings rather than online speculation for understanding the case.
5 Likes
Not being disrespectful, but keeping all options on the table:
Could this have been a prosthetic neck piece with a squib?
There are many reasons why a martyr is helpful to causes. Isn’t it a law that the government can present misinformation publicly, if it is considered of national security interest?
So let’s say CK was being threatened. Maybe he needed witness protection. Whatever the reason, arranging it for a public event kills multiple birds with one stone.
It highlights political violence. It creates an environment to push through legislations. It instantly creates the martyr effect. It gives CK an out.
If you look at the energy around the shot: it’s bulging at the upper back and upper chest. There’s actually a puff of gas observed from the collar. The necklace and the ear bud wire are displaced as if from an explosion below them.
The wound doesn’t make sense for exit or entry. The wound doesn’t make sense for a high powered rifle. The claim that the bullet was just under the skin doesn’t make sense. The trajectory doesn’t make sense. The alleged perpetrator narrative doesn’t make sense.
None of the information is cohesive. If it doesn’t make sense, it probably isn’t true.
However, if it was faked, everything fits better. Something is wrong about the whole thing.
1 Like
Wow You may be right the projectile does make a line from the back and through the knees except a trick of the film almost looks like that projectile is coming up from the floor. I wonder if the bullet or projectile went through the floor or ground hence the reason the paved over it so quickly.
YOU make very valid points and observations. It could be any intel from USA or another country, or they did it Together. I do not think it was his religious beliefs but exactly what you said, and I’ll add too many people involved with Epstein and he was speaking out about that. What a great way to make the JE files go away. Murder Charlie and distract us. We keep on we are not distracted.