scoot:
i've done similar (much longer) events with my old powerbook/dp4.61/lacie external usb2 drive/traveler. they were fairly simple, just took an aux send off of the board, and hit go as necessary. started new files at breaks. each recording ran 2-3 hours a pop, for a total of 10-12 hours per day, for 3 days. i did not particularly enjoy the editing/burning of such a long event (editing speeches you've already sat through is a whole new definition of tedious!), but it went without a hitch.
for this event though, they didn't have a nicer mixer budgeted, so...
i ran the two wireless mics (a handheld and a headworn) directly into the traveler. i then used cuemix and created 3 separate mix busses.
one bus went to a marantz tape deck (backup recording), the second went to the house pa (overhead speakers), the third went to headphones for monitoring.
each mic got its own track in metro. oh, and the recording rig was at the back of the room, away from prying eyes/curious fingers, and the front row remote was safely locked up in the office!
i usually record 44.1/24 rather than 16 because i typically end up using some eq and compression after the fact to "even out" the overall sound across different mics and presenters. also, since i track at pretty low levels (to try and avoid clipping as best i can), i use the compressors to kick up the end levels. so since i'm using effects, etc, i just keep at 24 bit to preserve as much as i can. it's more a matter of me being anal than any kind of real necessity dictated by the program material. after the editing, compression, and eq, i bounce/dither, then take the final aiff, and slice it up into the various tracks for burning.
i'm pleased to report that the recording went well this morning...i really need to read the manual...i found it disconcerting that the graphic editor/channels window waveform displays did not update as things were recording, but only after i hit stop...
the only real serious glitches i've run into thus far, were unrelated to metro itself:
the first anomoly was during a test run prior to the event, i got a couple of "device has been disconnected without being ejected...some data may have been lost" warnings. the scary part was that the lacie had NOT been disconnected. all connections were snug, etc. needless to say, i ended up tracking to the macbook's internal drive.
the second anomoly was a couple of clips as the second speaker got settled in, but i'm not sure what they're from (perhaps they bumped the mic, adjusting it?). here's the waveform of one of them:
fortunately, neither such clip was during a necessary part of the presentation, so they can be edited out without issue.
otherwise, it went smooth as glass.
now, to editing...and another identical session tomorrow!