Dilemma - Dropped ball during rundown

[DownTownTonyBrown]

Two of my recent games...

R1 in rundown bewteen 1st and 2nd. Defensive player catches ball and forces the runner toward 2nd (okay so there's the first mistake). The defensive player carries the ball in his ungloved hand for at least 30 feet and then tags the runner in the back. I call an immediate out two steps before the runner reaches 2nd and make the appropriate signal. As the defensive player drops his hand with the ball, he hits something (his own leg?) and the ball drops to the ground. I let the out call stand and said that the dropped ball was a separate act from the tag. No questions from players or coaches but I hear a fan saying "But he dropped the ball."

R3 in run down between 3rd and home. Same defensive mistake - forcing the runner towards home. Again, the defensive player carries the ball 20 feet and tags the runner in the back two to three steps before homeplate. Again, I call an immediate out and begin the signal ... as the ball drops to the ground after touching the runner's back. I change my call and sell the safe call yelling "You dropped the ball. You dropped the ball!!!" Again, no questions from players or coaches and nothing but groans from the fans.

Is there a better mechanic for out and safe calls during a rundown? Should I be waiting longer - to wait would have meant that the runner would have reached their objective (2nd, or home in the last scenario) before I made my call. I really think the immediate call is needed during a rundown but I may be mistaken.

To make the immediate call before they reach the base surely helps sell the call. And to wait until after the runner has reached their objective will surely create some nay sayers that I got the call wrong (when they don't drop the ball).

Maybe it's just a damned if you do and damned if you don't? Comments? Suggestions? Proper mechanic?