after the latest stable vdr version got released these days, i wonder
which direction vdr development will take in the near and far future.
have you, klaus, planned major feature and/or design changes and
thought about a roadmap up to version 2.0 or further?
what i would like to see for myself, is better support for a
client-server vdr architecture. that means i'm planning to distribute
the recording and the replaying part of vdr to different maschines. the
server should house all dvb cards and store the recordings. the clients
will get equiped with a replay device (dvb card, dxr3, tvout or
something else), should be able to view/cut/delete recordings and
manipulate timers. i know this should be allready possible with the
current vdr version, but there are some flaws. for example no protection
of different timers/recordings made by different clients.
also i do not see the point of having the dvb card support built into
vdr directly. IMHO this should be moved to a plugin like all other
devices. i love generic solutions. :-)
I agree. There shouldn't be any need to compile against DVB-driver (VDR
should include all necessary code to interface to DVB-API, e.g. in case
you run kernel-drivers ...).