Requiring cron to be run via CLI isn't drupal-norm and will eventually cause problems for someone.

It's been bugging me that with video module I'm having to run cron via the command line, and not cron.php as designed. I understand the premise of why this is needed but it's has some inherent problems. For instance;

• If this is a multisite config, it wont work... any sites other than what's in the "default" sites folder won't/can't be processed using the current method.
• I'm pretty sure that there are basic variables that are not going to be configured correctly by running from command line. For example, $base_url. (What if elsewhere in another module, cron sends an email that uses base_url to include a link to my site?)

I think, if you are sensitive to the implied issues (such as multi-site configs), you could still run your video_scheduler.php file through CLI, but I worry about doing cron that way.

I did some digging, and found this related post:
http://drupal.org/node/802110

Damien seems to caution that this is not a supported process, but points out a possible alternative: using the drupal.sh wrapper. I have never tried or played with that, but trust that he knows what he's talking about. Might be worth trying, and altering the documentation if it works??