TITAM - Technical issues that affected me

AVI files are pretty passe by now, but I'm certain there are people out there (like me) who have gotten used to Virtualdub. Sadly, Virtualdub will load most anything (with the appropriate plugin) but cannot save much of anything.  So, unless you really like everything in AVI format, you'll need a new editor. The question is: which one? If you like Virtualdub for it's good keyboard support, easy clipping against keyframes, processing speed, ability to clip without transcoding, or anything else, you are probably going to want an editor that works like that for .mp4 files. Fortunately, I only had to look around for a bit.  -  I looked for Windows Live Movie Maker, but it only comes bundled with a bunch of other stuff, and I did not like that.  I didn't even bother trying to install it. -  I tried Filmora Video Editor.  Looks like a good editor for "real" video editing, where you merge multiple video streams and so forth.  But the interface an...

Problem:  CS510 series won't pull paper from any available tray automatically.  Instead, it says something like "Load Tray 1 Plain A4", even though Tray 2 has paper in it.  Or, maybe, vice versa. Related:  You've loaded the all trays / the only tray with paper, but the printer says you need to load it again, saying something like "Load Tray 1 Plain A4" or similar. Solution:  The CS510 doesn't auto-detect the loaded paper size(s) from the trays directly.  Instead, you have to go to Settings/Paper Menu in the printer web server to set the paper sizes.  It will then "know" that one or more trays are holding the correct paper size for your print job.  It will then stop complaining that you need to load a particular tray with a particular size. This will also fix cases where you've loaded letter and print to letter, but the printer "thinks" the tray holds A4, or similar mix-ups. This will obviously not work if a multi-tray pr...

This information would be good to know for anyone considering this system, but does not seem to be available. I measured two sensor samples as follows: -  Standby (active):  25 uA max -  Detect:  16.2 mA max for about 2 seconds It's not actually 16 mA for the full 2 seconds, but that's close enough.  Especially since the 2 seconds might be anywhere from 1 to 3 seconds - I did not bother to measure more accurately than that. The sensors run on AAA cells, which I personally hate because of their relatively low capacity.  But, running the numbers, the effective capacity of AAAs should run these sensors for a very long time. Assumptions: -  Due to self-discharge and temperature effects, cells will only deliver 75% of their rated capacity. -  I estimated alarm consumption at 16 mA for 4 seconds.  This is twice as conservative as the ~2 seconds I estimated from observing the unit current. These work out as follows: Using 1000 mAh ...