[Official] NFL 2010


Recommended Posts

So happy that football is BACK! The Saints Vikings game was a hard fought game, but I'll take a win over a loss.

Houston dominating Indy was a fun site to see. Typically I root for the Colts, and even though I picked them to win, I was pleased to see Texans win. Only their second time in the last nine years (17 games) they have beaten the Colts. If the Texans can continue to play that way for most of the season, winning the AFC South isn't so far fetched, much less reaching the playoffs. It's also the first time in the last seven to ten years that the Colts won't have won their first 12 or more games.

Chad Johnson's non-TD catch was a great catch, and it was only due to the technicality of the rule that it wasn't, which sucks for him and the Lions. I picked Chicago for that game, so no harm for me.

As for Kolb, he's got potential, but he's got really big shoes to fill (despite what most Eagles fans say, McNabb was a winning QB). Vick is in an ideal position with an ultimately untested QB starting. 175 yards passing, 103 yards rushing, that's what Vick so good for the Falcons. With Kolb suffering a concussion, Vick see even more playing time.

And lastly, I don't care if the Cowboys D and some of their players are among my fantasy teams. I want them crushed.

So happy that football is BACK! The Saints Vikings game was a hard fought game, but I'll take a win over a loss.

That was an awesome first game of the season, favre just couldn't get anything going with his receivers. AP is a beast though.

Houston dominating Indy was a fun site to see. Typically I root for the Colts, and even though I picked them to win, I was pleased to see Texans win. Only their second time in the last nine years (17 games) they have beaten the Colts. If the Texans can continue to play that way for most of the season, winning the AFC South isn't so far fetched, much less reaching the playoffs. It's also the first time in the last seven to ten years that the Colts won't have won their first 12 or more games.

I love watching the colts lose. It makes me happy seeing payton cry.

As for Kolb, he's got potential, but he's got really big shoes to fill (despite what most Eagles fans say, McNabb was a winning QB). Vick is in an ideal position with an ultimately untested QB starting. 175 yards passing, 103 yards rushing, that's what Vick so good for the Falcons. With Kolb suffering a concussion, Vick see even more playing time.

Vick was awesome today, my boy did well :) He had a TD on top of that too.

And lastly, I don't care if the Cowboys D and some of their players are among my fantasy teams. I want them crushed.

die cowboys die!!!!

Meh, Dallas haters.

Their O-line was horrible and the penalties killed them. Their offense couldn't get it done when they finally got within range, and they need a kicker desperately -- quit trying to save a damn roster spot by using the place kicker.

They'll still make it to the playoffs, but that was a pretty crappy loss.

Oh, and the Lions got screwed out of a victory.

Calvin Johnson's non-TD catch was a great catch, and it was only due to the technicality of the rule that it wasn't, which sucks for him and the Lions. I picked Chicago for that game, so no harm for me.

If that was a correct ruling they need to alter or get rid of that rule because their expectations of what you need to do in order for a catch in the end zone to count is rediculous. He had complete control of the ball from the second he touched it, he then put two feet down, sat down in the endzone, and then started getting up. Because the ball left his hand at that point its not a catch?

If that was a correct ruling they need to alter or get rid of that rule because their expectations of what you need to do in order for a catch in the end zone to count is rediculous. He had complete control of the ball from the second he touched it, he then put two feet down, sat down in the endzone, and then started getting up. Because the ball left his hand at that point its not a catch?

Not just because of that. It has to do with him catching the ball and "completing" whatever fall or hit happens with the possession. The argument could be made that his turning and using the ball to push himself up could be considered a second movement or act; if that were the case, it would have been ruled a complete pass, but the entire process of going up and landing, rolling, etc., the player must maintain possession. Here's a good read on the whole situation. It should have been a catch.

Yeah, I think they should just drop the whole "complete act" thing, if he has posession and comes down in bounds in the end zone why do they need anything else? It's not like he was juggling the ball or anything, if he follows through the catch rolling over, turning, or anything why should that act now be somehow bound to the catch? If that had happened in the open field and he wasn't touched and ruled down that would have been a fumble not an incompletion.

He had COMPLETE control of the ball. The only thing they seem to be bitching about is that he leg go of it when he was celebrating. Even when he had it in one hand, he had CONTROL of it. How that can be questioned is beyond me.

His feet were firmly planted, and when they were firmly planted, he had possession of the ball. Even when falling, the ball was securely in his hand. What happens after that SHOULD NOT MATTER. He caught it, was clearly in the end zone, and then fell AFTER catching it. But even WHILE falling, he had control of the ball. The issue seems to be that he let the ball touch the ground and let go of it. Why does that matter at all?

He had COMPLETE control of the ball. The only thing they seem to be bitching about is that he leg go of it when he was celebrating. Even when he had it in one hand, he had CONTROL of it. How that can be questioned is beyond me.

i just watched it again about 5 times, i completely agree with the call, you have to show you have completely control, the catch doesn't stop until you are completely down or out of bounds, he was neither when the ball came loose.

He's a idiot...mostly bad luck, but still a bonehead.

The ball touching the ground wouldn't have been a problem as long as the officials could clearly see he maintained possession, which he did up to the point of getting off the ground. Had he gotten up with the ball in hand instead of letting go, this wouldn't have been an issue.

i just watched it again about 5 times, i completely agree with the call, you have to show you have completely control, the catch doesn't stop until you are completely down or out of bounds, he was neither when the ball came loose.

He's a idiot...mostly bad luck, but still a bonehead.

He was completely down, though. He maintained position through the catch, to the ground, and when he was getting back up, he let the ball go. It was a very bad call and some ref should be on the brink of losing his job.

I'm over the moon about that Cowboys loss though. The Redskins still suck, but apparently the Cowboys are even worse. :laugh:

Also, I hate Vick (because I hate what he did and I also hate his alma mater, Virginia Tech [which had an absolutely hilarious loss to JMU, an FCS team, this weekend :D]), but he really should be starting for Philly. Kolb was complete ****.

He was completely down, though. He maintained position through the catch, to the ground, and when he was getting back up, he let the ball go. It was a very bad call and some ref should be on the brink of losing his job.

...

It was NOT a bad call at all! The ref made the call as the current rule states - blame the rulebook not the ref. I am all about refs making bad calls, but it was dead on. ESPN / FOX clearly showed the rule in its entirety and it was properly called. I'm sure this will raise questions as Calvin clearly did have possession and control - just not as the league defined it in this situation.

The ball touching the ground wouldn't have been a problem as long as the officials could clearly see he maintained possession, which he did up to the point of getting off the ground. Had he gotten up with the ball in hand instead of letting go, this wouldn't have been an issue.

You just admitted the exact opposite of what you're arguing. He maintained possession of the ball through the entire process of the catch. When he hit the ground, he clearly had possession of the ball, so him getting up and letting go of the ball is a nonissue. Furthermore, they reviewed it and clearly had the opportunity to see what you just stated. The NFL for some reason has decided that the review process is a joke now based on all the televised games I saw, as they almost never reverse a call now.

You just admitted the exact opposite of what you're arguing. He maintained possession of the ball through the entire process of the catch. When he hit the ground, he clearly had possession of the ball, so him getting up and letting go of the ball is a nonissue. Furthermore, they reviewed it and clearly had the opportunity to see what you just stated. The NFL for some reason has decided that the review process is a joke now based on all the televised games I saw, as they almost never reverse a call now.

I did no such thing. Let me explain it a bit more clearly: the ball can hit the ground and the pass be completed so long as the player has possession during and after the ball makes contact with the ground. Johnson let go of the ball while it was on the ground and by rule, that's an incomplete pass. This is one of rare catches that illustrates the problem with the ruling, but in nearly all other cases, the rule properly dictates the outcome.

Like I said before, had he gotten up with the ball rather than letting it go when it was on the ground, this wouldn't have been an issue for debate.

I did no such thing. Let me explain it a bit more clearly: the ball can hit the ground and the pass be completed so long as the player has possession during and after the ball makes contact with the ground. Johnson let go of the ball while it was on the ground and by rule, that's an incomplete pass. This is one of rare catches that illustrates the problem with the ruling, but in nearly all other cases, the rule properly dictates the outcome.

Like I said before, had he gotten up with the ball rather than letting it go when it was on the ground, this wouldn't have been an issue for debate.

That is not, by rule, an incomplete pass. The ground can't cause a fumble, just like it can't cause an incomplete pass when you have control of the ball when hitting the ground. What happened after he hit the ground is relevant to the situation unless you argue he didn't have control, and it seems pretty clear to me that he did, in fact, have control. Just because he had the ball in one hand doesn't mean he didn't have control. He was down, the ball was controlled securely in his hand.

To quote the rule, "if the regains control of the ball prior to the ball touching the ground, the pass is complete." So, even if you want to argue he lost control, he clearly had it secured in his hand before hitting the ground. At what point are you saying he lost control? Because that's the issue. His legs were clearly down, he clearly had control of the ball, and then it came out after making the catch. This isn't like the other instances where the receivers lost control of the ball or weren't properly handling it. He doesn't need two hands on the ball to have control.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • expected when they force you by having to use TPM and secure boot for anti cheat crap, and lazy developers only test on windows 11.
    • The fact I need to use "Show more" like 99% of the time is so annoying. Or why I have 7-zip under 3 submenus when it could be in top. And Microslop keeps saying how they'll improve Start and I've not seen ANY improvement yet. In MONTHS. WTF?! I'll believe any of it when they actually deliver anything.
    • LosslessCut 3.69 by Razvan Serea LosslessCut aims to be the ultimate cross platform FFmpeg GUI for extremely fast and lossless operations on video, audio, subtitle and other related media files. The main feature is lossless trimming and cutting of video and audio files, which is great for saving space by rough-cutting your large video files taken from a video camera, GoPro, drone, etc. It lets you quickly extract the good parts from your videos and discard many gigabytes of data without doing a slow re-encode and thereby losing quality. Or you can add a music or subtitle track to your video without needing to encode. Everything is extremely fast because it does an almost direct data copy, fueled by the awesome FFmpeg which does all the grunt work. Features Lossless cutting of most video and audio formats Losslessly cut out parts of video/audio (for cutting away commercials etc.) Losslessly rearrange the order of video/audio segments Lossless merge/concatenation of arbitrary files (with identical codecs parameters, e.g. from the same camera) Lossless stream editing: Combine arbitrary tracks from multiple files (ex. add music or subtitle track to a video file) Losslessly extract all tracks from a file (extract video, audio, subtitle, attachments and other tracks from one file into separate files) Batch view for fast multi-file workflow Remux into any compatible output format Take full-resolution snapshots from videos in JPEG/PNG format Manual input of cutpoint times Apply a per-file timecode offset (and auto load timecode from file) Change rotation/orientation metadata in videos View technical data about all streams Timeline zoom and frame/keyframe jumping for accurate cutting around keyframes Saves per project cut segments to project file View FFmpeg last command log so you can modify and re-run recent commands on the command line Undo/redo Give labels to cut segments View segment details, export/import cut segments as CSV Import segments from: MP4/MKV chapters, Text file, YouTube, CSV, CUE, XML (DaVinci, Final Cut Pro) Video thumbnails and audio waveform Edit file metadata and per-stream metadata Edit per-stream disposition Cut with chapter marks Annotate segments with tags View subtitles Example lossless use cases Cut out commercials from a recorded TV show (and re-format from TS to MP4) Remove audio tracks from a file Extract music track from a video and cut it to your needs Add music to a video (or replace existing audio track) Combine audio and video tracks from separate recordings Include an external subtitle into a video Quickly change a H264/H265 MKV video to MOV or MP4 for playback on iPhone Import a list of cut times from other tool as a EDL (edit decision list, CSV) and run these cuts with LosslessCut Export a list of cut times as a CSV EDL and process these in another tool Quickly cut a file by its MP4/MKV chapters Quickly cut a YouTube video by its chapters (or music times from a comment) Change the language of a file's audio/subtitle tracks Attach cover art to videos Change author, title, GPS position, recording time of a video Fix rotation of a video that has the wrong orientation flag set Great for rotating phone videos that come out the wrong way without actually re-encoding the video. Loop a video / audio clip X times quickly without re-encoding LosslessCut 3.69.0 changelog: Add lossless cropping & aspect ratio override via bitstream and container metadata #643 Alow shifting tracks for each file (-itsoffset) #216 Add "decimate video" tool to filter away all non-keyframes #2111 Add Windows ARM 64 native build with native ffmpeg Move timecode out of timeline and make it copy-able #2592 #2691 #2800 #483 #2808 Upgrade Electron to latest Add new "opposing" align mode #2654 Add FFmpeg -hwaccel auto setting for hardware acceleration of certain operations Add API events export-start and export-complete Allow deleting track metadata #2819 Improve shift segments dialog #2839 Show keyboard shortcuts inside button tooltips in UI Warn if trying to cut with too few keyframes around cutpoint #516 #2780 #2756 (Linux) include app name in notification #2794 Pull latest translations Other notable changes: Advanced output directory selector #2101 #2115 #2755 increase max file name length to 250 (truncation) #2779 don't reset playback speed when using special playback modes #2889 preserve chapters when merging files that already have chapters don't merge adjacent segments in combineOverlappingSegments #2896 don't transfer segment name when filling gaps #2754 always scroll up to zoom in #2703 #2786 increase max keyframes to 10000 Don't bind ctrl/cmd+c by default (they interfer with copying text) Many other improvements and fixes Download: LosslessCut 3.69.0 | ARM64 | ~100.0 MB (Open Source) Links: LosslessCut Website | Other Operating Systems | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Doesn't even need a UI for point 2 - use some sort of JSON/XML container - because MOST users won't even bother.
  • Recent Achievements

    • Conversation Starter
      FBSPL earned a badge
      Conversation Starter
    • Week One Done
      I2D earned a badge
      Week One Done
    • Week One Done
      Dr Jared Dental Studio earned a badge
      Week One Done
    • Week One Done
      RG INVESTMENT GROUP earned a badge
      Week One Done
    • Very Popular
      The Norwegian Drone Pilot earned a badge
      Very Popular
  • Popular Contributors

    1. 1
      +primortal
      488
    2. 2
      PsYcHoKiLLa
      263
    3. 3
      Skyfrog
      85
    4. 4
      FloatingFatMan
      64
    5. 5
      Michael Scrip
      62
  • Tell a friend

    Love Neowin? Tell a friend!