id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc	mlocked
10048	failure to restart recording after crash for certain recordingtypes	xunspam-sususu@…	gigem	"I'm not certain if this is a bug or a feature, however its annoying. 

'''current behaviour:'''
After cancellation of recording e.g. by backend-crash, power failure, thunderstorm or whatever once the system is back online recording is not restarted. 
Sometimes the next reairing is scheduled if available. 

I guess thats a bug, since when there is no find (singlerecord) recording restarts once backend is running again. 

'''proposed behavior:''' 

'''restart recording in any case''', keeping the the previously scheduled order is better than rearranging everything even if there was  another (low priority) recording to fill that spot. 
however adding the alternative airing to scheduling queue should be done additionally.  



----------------------------------------------------------------------
MythTV Version   : v0.24.1-1-g347cd24
MythTV Branch    : fixes/0.24
Network Protocol : 63
Library API      : 0.24.20110505-1
QT Version       : 4.6.2
Options compiled in:
 linux debug using_alsa using_oss using_pulse using_pulseoutput using_backend using_bindings_perl using_bindings_python using_directfb using_dvb using_firewire using_frontend using_hdhomerun using_hdpvr using_iptv using_ivtv using_joystick_menu using_lirc using_mheg using_opengl_video using_opengl_vsync using_qtdbus using_qtwebkit using_v4l using_v4l2 using_x11 using_xrandr using_xv using_bindings_perl using_bindings_python using_mythtranscode using_opengl using_vdpau using_ffmpeg_threads using_live using_mheg
"	Bug Report - General	closed	minor	unknown	MythTV - Scheduling	0.24-fixes	medium	Invalid	recording recorder failure error scheduling rescheduling		0