(09-01-2014 06:21 PM)BDKJMU Wrote:  I can't get a 2nd look because the BTN f'ing blows. I had set to record Saturday on the secondary BTN non HD network the JMU game. It said in the guide "Maryland hosts James Madison.....from Capital One Field at Byrd Stadium..". I turn on the recording and its FAU @ Nebraska. Don't list one game then air a different one. Amateur network..

Edit- I'm in the Philly area with Verizon Fios.

I had the same thing happen. Set to record the 3:00AM replay and apparently the schedule changed. I usually watch more of the skill position players during the live feed and then like to watch the line play more on the 2nd viewing.

(09-02-2014 08:37 AM)Bawlmer Duke Wrote:  

(08-31-2014 11:57 AM)DoubleDDuke Wrote:  MD second watch observations:
- I guess the question of whether D'Andre Smith is still on the team has been answerd - No

Thought he played? JMUSports game participation report says he did too...

That's weird. I guess because I didn't see him and Tapley had his number I assumed he wasn't with the team. That's odd that a transfer would come in and get a guy's number. I always thought Smith was a good player. I would have expected him to get more PT.

(09-02-2014 09:42 AM)DoubleDDuke Wrote:  

(09-02-2014 08:37 AM)Bawlmer Duke Wrote:  

(08-31-2014 11:57 AM)DoubleDDuke Wrote:  MD second watch observations:
- I guess the question of whether D'Andre Smith is still on the team has been answerd - No

Thought he played? JMUSports game participation report says he did too...

That's weird. I guess because I didn't see him and Tapley had his number I assumed he wasn't with the team. That's odd that a transfer would come in and get a guy's number. I always thought Smith was a good player. I would have expected him to get more PT.

Good point -- forgot Smith was #6 last year and now has #9

The Terps are actually a very talented team. Had it not been for a plethora of injuries to key players the previous two seasons, they would've done more damage than they did in the ACC. Don't be surprised if this team wins 8 or 9 games this season. A good litmus test for them will be WVU in two weeks, a game that is shaping up to be very meaningful to both teams from the looks of it.

As far as we go, I hardly think this was our worst performance in recent memory. People forget WVU in 2012 was up by 28 after one and change and probably could've scored about 80-100 if they really wanted to. The difference here is that Mickey's strategy was to burn as much time off the clock as possible while Withers and Mehringer stuck to the script of the fast paced offense which was necessary.

I think Lehigh will have some trouble defending the fast paced offense.

(09-02-2014 10:51 AM)All Dukes_All Day Wrote:  The Terps are actually a very talented team. Had it not been for a plethora of injuries to key players the previous two seasons, they would've done more damage than they did in the ACC. Don't be surprised if this team wins 8 or 9 games this season. A good litmus test for them will be WVU in two weeks, a game that is shaping up to be very meaningful to both teams from the looks of it.

As far as we go, I hardly think this was our worst performance in recent memory. People forget WVU in 2012 was up by 28 after one and change and probably could've scored about 80-100 if they really wanted to. The difference here is that Mickey's strategy was to burn as much time off the clock as possible while Withers and Mehringer stuck to the script of the fast paced offense which was necessary.

I think Lehigh will have some trouble defending the fast paced offense.

This guy wins the internet. He gets it.
The fans on the ledge should take note and come back to reality.

By 'piling up' the score last weekend, Maryland was sending a message to their new 'pals' in the BIG10, that they are legitimate members of their P5 conference.

This weekend, we should handle Lehigh easily, but I doubt that we will be 'piling up' the score. It is not in keeping with the JMU tradition of fair play.

(09-02-2014 10:51 AM)All Dukes_All Day Wrote:  The Terps are actually a very talented team.

I just didn't see that.

CJ Brown may be a worse passer than Vad Lee. It was close, they both sucked. The Turtles looked like they were moving at, well, turtle speed, much of the time. Granted, they were laughing at us and kinda' taking it easy, but still, they have a tough Big Ten schedule coming up, and having seen many of those teams play, I just don't see the Terps in that class, at least right now. I hope they prove me wrong, but Michigan State or the Buckeyes they are not, both of whom are on their schedule.

I see 3 realistic wins on Maryland's conference schedule. I figure they will finish the season around, most likely under, .500.

(09-05-2014 01:41 AM)bulldogg Wrote:  

(09-02-2014 10:51 AM)All Dukes_All Day Wrote:  The Terps are actually a very talented team.

I just didn't see that.

CJ Brown may be a worse passer than Vad Lee. It was close, they both sucked. The Turtles looked like they were moving at, well, turtle speed, much of the time. Granted, they were laughing at us and kinda' taking it easy, but still, they have a tough Big Ten schedule coming up, and having seen many of those teams play, I just don't see the Terps in that class, at least right now. I hope they prove me wrong, but Michigan State or the Buckeyes they are not, both of whom are on their schedule.

I see 3 realistic wins on Maryland's conference schedule. I figure they will finish the season around, most likely under, .500.

I agree about Brown but they are really good at basically every other position. Their lines can and will match up with most of the B1G and if they get what the think they will out of Diggs, they will be a solid team in the conference.

So I am finally rewatching this game and I timed on a stopwatch the time between the fair catch signal and the contact. It was about 1.5 seconds. The defender clearly didn't have time to stop.

Home cooking.

edit: wow another late hit penalty when the player is hit while in bounds and still in play... this is some bull.sh.it. when you take away all the nonsense, we really didn't have that many penalties.

(09-05-2014 09:32 AM)Potomac Wrote:  So I am finally rewatching this game and I timed on a stopwatch the time between the fair catch signal and the contact. It was about 1.5 seconds. The defender clearly didn't have time to stop.

Home cooking.

edit: wow another late hit penalty when the player is hit while in bounds and still in play... this is some bull.sh.it. when you take away all the nonsense, we really didn't have that many penalties.

Based on your 1.5 second lead time and assuming a 40 time of 4.5 seconds, he was 13 yards away when the signal was made. More than enough time to veer off and avoid contact.

(09-05-2014 09:32 AM)Potomac Wrote:  So I am finally rewatching this game and I timed on a stopwatch the time between the fair catch signal and the contact. It was about 1.5 seconds. The defender clearly didn't have time to stop.

Home cooking.

edit: wow another late hit penalty when the player is hit while in bounds and still in play... this is some bull.sh.it. when you take away all the nonsense, we really didn't have that many penalties.

that late hit on the sidelines was complete bs, I also thought the PI on Reynolds was a bad call as well, but when you lose by 45 it is hard to complain about calls.

(09-05-2014 10:18 AM)PGJMU Wrote:  

(09-05-2014 09:32 AM)Potomac Wrote:  So I am finally rewatching this game and I timed on a stopwatch the time between the fair catch signal and the contact. It was about 1.5 seconds. The defender clearly didn't have time to stop.

Home cooking.

edit: wow another late hit penalty when the player is hit while in bounds and still in play... this is some bull.sh.it. when you take away all the nonsense, we really didn't have that many penalties.

that late hit on the sidelines was complete bs, I also thought the PI on Reynolds was a bad call as well, but when you lose by 45 it is hard to complain about calls.

we would've lost by 28 if they didn't hand them 2-3 scoring drives on a series of horseshit calls. the home cooking was plentiful in this matchup.
I can't wait for a real game this week with hopefully better officiating.

(09-05-2014 10:03 AM)AllForDukes Wrote:  

(09-05-2014 09:32 AM)Potomac Wrote:  So I am finally rewatching this game and I timed on a stopwatch the time between the fair catch signal and the contact. It was about 1.5 seconds. The defender clearly didn't have time to stop.

Home cooking.

edit: wow another late hit penalty when the player is hit while in bounds and still in play... this is some bull.sh.it. when you take away all the nonsense, we really didn't have that many penalties.

Based on your 1.5 second lead time and assuming a 40 time of 4.5 seconds, he was 13 yards away when the signal was made. More than enough time to veer off and avoid contact.

looking at it again at the moment the fair catch was called, the MD player was on the 25, while the JMU defender was on the 34. a 9 yard difference.
IMO, the replay shows he didn't have adequate time to stop. he did make an effort to move but their knees collided.
the second similar penalty, it is not clear if they waved for a fair catch before the camera panned over to the returner. however, when you see the first visible signal, the MD player is on the 38 and the JMU player is on the 46. 8 yards. It was about 1 or slightly more than 1 second.

The two flags I thought were BS were of course that late hit on Marlowe as well as I think the PI on Reynolds (looked like total incidental contact of legs getting tangled.

(09-05-2014 10:35 AM)Potomac Wrote:  

(09-05-2014 10:03 AM)AllForDukes Wrote:  

(09-05-2014 09:32 AM)Potomac Wrote:  So I am finally rewatching this game and I timed on a stopwatch the time between the fair catch signal and the contact. It was about 1.5 seconds. The defender clearly didn't have time to stop.

Home cooking.

edit: wow another late hit penalty when the player is hit while in bounds and still in play... this is some bull.sh.it. when you take away all the nonsense, we really didn't have that many penalties.

Based on your 1.5 second lead time and assuming a 40 time of 4.5 seconds, he was 13 yards away when the signal was made. More than enough time to veer off and avoid contact.

looking at it again at the moment the fair catch was called, the MD player was on the 25, while the JMU defender was on the 34. a 9 yard difference.
IMO, the replay shows he didn't have adequate time to stop. he did make an effort to move but their knees collided.
the second similar penalty, it is not clear if they waved for a fair catch before the camera panned over to the returner. however, when you see the first visible signal, the MD player is on the 38 and the JMU player is on the 46. 8 yards. It was about 1 or slightly more than 1 second.

Even if he doesn't call fair catch at all you can't just run into him. You have to break down and give him a chance to make the catch.

(09-05-2014 10:49 AM)DoubleDDuke Wrote:  

(09-05-2014 10:35 AM)Potomac Wrote:  

(09-05-2014 10:03 AM)AllForDukes Wrote:  

(09-05-2014 09:32 AM)Potomac Wrote:  So I am finally rewatching this game and I timed on a stopwatch the time between the fair catch signal and the contact. It was about 1.5 seconds. The defender clearly didn't have time to stop.

Home cooking.

edit: wow another late hit penalty when the player is hit while in bounds and still in play... this is some bull.sh.it. when you take away all the nonsense, we really didn't have that many penalties.

Based on your 1.5 second lead time and assuming a 40 time of 4.5 seconds, he was 13 yards away when the signal was made. More than enough time to veer off and avoid contact.

looking at it again at the moment the fair catch was called, the MD player was on the 25, while the JMU defender was on the 34. a 9 yard difference.
IMO, the replay shows he didn't have adequate time to stop. he did make an effort to move but their knees collided.
the second similar penalty, it is not clear if they waved for a fair catch before the camera panned over to the returner. however, when you see the first visible signal, the MD player is on the 38 and the JMU player is on the 46. 8 yards. It was about 1 or slightly more than 1 second.

Even if he doesn't call fair catch at all you can't just run into him. You have to break down and give him a chance to make the catch.

then in the case of both penalties, you could say they didn't let the returner catch the ball first. in that case, they're correct.