Hi, let's make it more complicated, just for fun. What should be possible: I record from 8pm. to 9pm. At 8:15 I start watching the channel. The correct way would be to start with the recording, but ater 9pm. the recording should still run, maybe the user wants to watch after the recording, too. But the file stored from the recording should only be between 8 and 9.
How to solve this. Multicast may be a way, maybe unicast to different clients what they want to see now. Maybe a simple file system solution. My idea: start a recording too foo.mpg. You can play it when you want. Live tv will also be dumped to a file. E.g. the live tv after foo.mpg will be foo.mpg.ltv.0001 counting up in 10 MB blocks. A streaming client could request this data from the server, but maybe the client only uses the files in the filesystem. What we need: mplayer needs to be able to read the additional files of a recording (we talk about deleting the tmp files later). And please, mplayer should be prevented from stopping at EOF when seeking at this point. We need a mplayer patch, I see no correct way around this. Only one (bad) idea: but a webserver in the recordserver and mplayer plays a http stream. By that ugly solution we can combine the parts and prevent mplayer from reading after EOF. And IIRC mplayer can also seek in http streams if the server has support for that. But this is a bad hack, I'm afraid the protocol police will come and execute me when we do that :) Dischi -- I've already told you more than I know.
pgpEzh8YqkC80.pgp
Description: PGP signature
