madsilence Posted January 8, 2017 Share Posted January 8, 2017 Hello. Posting in bug section, because it definitely fits more here than in any other section.... I'm a legal user since around 2010 (just to skip Q/A about same problem in crkd versions, not the case) and till now I had no idea about this artificial, on-purpose handmade limitation. Why did you implement such a limitation at all? Using NTFS system nobody will reach a maximum filesize for this file system never. When olympic games in London took place I recorded around 12-18h (but always less than 23.59h) of FullHD olympic channels obtaining entire files sized around 60-80GB. There is absolutely no problems with cutting later these huge files into separate volleyball matches with VideoRedo TV Suite 4.21.6.674 on x32 and x64 windows OS, also no viewing problems were noticed. Now I am recording mpeg2 stream continuously and filesize for 23.59h is around 25-30GB, VideoRedo TV Suite manages such a small files perfectly. So.....why at all you implemented limitations for recording? Other (your competitor's) programs have at least a "split recorded files into XXX MB/Gb", thats in case if DVBViewer itself manages more than 30GB files with some difficulties (hipoteticaly). But shut off recording its a little bit ugly for a normal user, don't you think? Best regards. Quote Link to comment
madsilence Posted January 11, 2017 Author Share Posted January 11, 2017 any reply from developers? Quote Link to comment
Griga Posted January 11, 2017 Share Posted January 11, 2017 Why at all you implemented limitations for recording? It has been done many years ago (not be me). Unfortunately it can't be changed easily due to the underlying data structures and a lot of dependencies inside and outside DVBViewer. Will be a future project. Also see here. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.