Re: [Freevo-users] Very large files encoded by mencoder
On 1/14/06, Davide dada Carboni [EMAIL PROTECTED] wrote: Hi, I notice that the TV recordings are really large files. One hour uses more or less 1GB of disk. I'm surprised because the resolution I'm using is very poor (256,192). I think that the encoding could be more efficient (I've seen high quality Divx movies in less than 800MB). Is there any fine tuning to my VCR_CMD I can perform to make smaller files? I'm using the same settings as yours, except for the video bitrate: I think that your (2048) is too high! I use 1200 and I obtain ever a good quality. with such setting I use about 600mb every hour of recording. bye antani -- keep in mind the power of antani antani at gmail dot com www.orangeek.org --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37alloc_id865op=click ___ Freevo-users mailing list Freevo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-users
Re: Freevo 1.5.4, python2.4 ivtv crash Was: [Freevo-users] Re: ivtv not working
On Fri, 2006-01-13 at 18:49 +0100, Robert Winder wrote: Jason and Gerrit Hannaert already looked into it. Both provided a patch on the userlist at 10/11 june 2005. Both patches didn't make it in python 2.4 bugfix release freevo 1.5.4 I did have a private correspondence with Geert Decorte who experienced the following python 2.4 error Assuming by both patches you mean the two patches you attached that were posted here some time ago, both of those _did_ make it into the Freevo 1.5.4 bugfix release. It would definitely have been a major SNAFU if they didn't, because the entire point of the 1.5.4 release was to include these fixes. :) Just to make sure I wasn't losing my sanity, I redownloaded the 1.5.4 tarball from sf.net and indeed these patches were correctly included. r = fcntl.ioctl(self.device, long(QUERYCAP_NO), val) OverflowError: long int too large to convert to int This line of code doesn't exist anywhere in Freevo 1.5.4. It shouldn't happen. and after applying the attached patches provided by Jason and Gerrit it worked again. Although i haven't looked if there are more instances which could trigger this error within Freevo. I did do a search for all instances of ioctl in the code in order to determine of the request identifier needed to be wrapped in i32(). But I might have missed some. Here's a patch that I've done for this problem: http://www.linuxowl.com/patches/freevo-1.5.4-v4l2.py.patch Python was using 'L' for 64bit ints and the interface wanted 32bit ints. dischi/rshortt -- how does this patch look to you? It seems sensible to me (in terms of logic), but there are many places in v4l2.py where 'L' is used in the struct format, and many cases that Duncan didn't modify that might require it. Maybe Duncan could comment as well. If everything is good, I'll merge this patch with both the 1.5 and trunk branches. def getfmt(self): -val = struct.pack( FMT_ST, 1L,0,0,0,0,0,0,0) +val = struct.pack( FMT_ST, 0,0,0,0,0,0,0,0) r = fcntl.ioctl(self.device,GET_FMT_NO,val) return struct.unpack( FMT_ST, r ) Given that this is the code now present in trunk, I've committed this fix to the 1.5 branch as well. Are there any other issues with Freevo 1.5.4 and Python 2.4? How about with AMD64? Considering Freevo 2.0 won't be out for many months, it might be a good idea to fix some more of these bugs and release a 1.5.4.1. dischi? Cheers, Jason. signature.asc Description: This is a digitally signed message part
Re: Freevo 1.5.4, python2.4 ivtv crash Was: [Freevo-users] Re: ivtv not working
A short clarification from my side could shine a light onto the case. I have a epia MII1000 Nehemiah mobo with a Hauppage MCE500 and went for the epios distribution as the tool for the job. (epios is a gentoo based distro with specific epia motherboard optimalisations) This was the snapshot I've used for the install http://www.epios.net/viewtopic.php?t=339 Basicly installing would be as simple as emerging and configuring ivtv and freevo. This should be enough for resolving dependencies. The portage tree of epios has only freevo 1.5.2 available, but this should do the trick for most dependencies. Afterwards, I've downloaded 1.5.4 directly from sourceforge, unpacked it, and installed. Didn't see any error in the install. Now I checked .../freevo-1.5.4/build/lib/freevo/tv/v4l2.py And as Jason stated, it didn't contained the obstructing line. But the installed version did contain it. /usr/lib/python2.4/site-packages/freevo/tv/v4l2.py So it should be the v4l2.py version installed by 1.5.2 which didn't get up to date after installing 1.5.4 The only problem should be in updating 1.5.4 from a prior (unused?) version or something specific with the distro I'm using. I've followed the installation instructions literaly To install Freevo, run 'python setup.py install' as root. So if there are files who didn't went up-to-date probably I need to copy them manualy from the build directory? Is there a clear way to check these out? This is the output when rebuilding the setup of 1.5.4 epios freevo-1.5.4 # python setup.py install checking for mmpython... found checking for pygame... found checking for Image... found checking for twisted...found running install running build running build_py running build_scripts running install_lib byte-compiling /usr/lib/python2.4/site-packages/freevo/tv/ivtv.py to ivtv.pyc byte-compiling /usr/lib/python2.4/site-packages/freevo/tv/v4l2.py to v4l2.pyc byte-compiling /usr/lib/python2.4/site-packages/freevo/plugins/mixer.py to mixer.pyc running install_scripts changing mode of /usr/bin/freevo to 755 running install_data Geert On Fri, 2006-01-13 at 18:49 +0100, Robert Winder wrote: Jason and Gerrit Hannaert already looked into it. Both provided a patch on the userlist at 10/11 june 2005. Both patches didn't make it in python 2.4 bugfix release freevo 1.5.4 I did have a private correspondence with Geert Decorte who experienced the following python 2.4 error Assuming by both patches you mean the two patches you attached that were posted here some time ago, both of those _did_ make it into the Freevo 1.5.4 bugfix release. It would definitely have been a major SNAFU if they didn't, because the entire point of the 1.5.4 release was to include these fixes. :) Just to make sure I wasn't losing my sanity, I redownloaded the 1.5.4 tarball from sf.net and indeed these patches were correctly included. r = fcntl.ioctl(self.device, long(QUERYCAP_NO), val) OverflowError: long int too large to convert to int This line of code doesn't exist anywhere in Freevo 1.5.4. It shouldn't happen. http://gedeco.no-ip.org -- This message has been scanned for viruses and dangerous content by OpenProtect(http://www.openprotect.com), and is believed to be clean. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ Freevo-users mailing list Freevo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-users
Re: Freevo 1.5.4, python2.4 ivtv crash Was: [Freevo-users] Re: ivtv not working
A short clarification from my side could shine a light onto the case. I have a epia MII1000 Nehemiah mobo with a Hauppage MCE500 and went for the epios distribution as the tool for the job. (epios is a gentoo based distro with specific epia motherboard optimalisations) This was the snapshot I've used for the install http://www.epios.net/viewtopic.php?t=339 Basicly installing would be as simple as emerging and configuring ivtv and freevo. This should be enough for resolving dependencies. The portage tree of epios has only freevo 1.5.2 available, but this should do the trick for most dependencies. Afterwards, I've downloaded 1.5.4 directly from sourceforge, unpacked it, and installed. Didn't see any error in the install. Now I checked .../freevo-1.5.4/build/lib/freevo/tv/v4l2.py And as Jason stated, it didn't contained the obstructing line. But the installed version did contain it. /usr/lib/python2.4/site-packages/freevo/tv/v4l2.py So it should be the v4l2.py version installed by 1.5.2 which didn't get up to date after installing 1.5.4 The only problem should be in updating 1.5.4 from a prior (unused?) version or something specific with the distro I'm using. I've followed the installation instructions literaly To install Freevo, run 'python setup.py install' as root. So if there are files who didn't went up-to-date probably I need to copy them manualy from the build directory? Is there a clear way to check these out? This is the output when rebuilding the setup of 1.5.4 epios freevo-1.5.4 # python setup.py install checking for mmpython... found checking for pygame... found checking for Image... found checking for twisted...found running install running build running build_py running build_scripts running install_lib byte-compiling /usr/lib/python2.4/site-packages/freevo/tv/ivtv.py to ivtv.pyc byte-compiling /usr/lib/python2.4/site-packages/freevo/tv/v4l2.py to v4l2.pyc byte-compiling /usr/lib/python2.4/site-packages/freevo/plugins/mixer.py to mixer.pyc running install_scripts changing mode of /usr/bin/freevo to 755 running install_data Geert On Fri, 2006-01-13 at 18:49 +0100, Robert Winder wrote: Jason and Gerrit Hannaert already looked into it. Both provided a patch on the userlist at 10/11 june 2005. Both patches didn't make it in python 2.4 bugfix release freevo 1.5.4 I did have a private correspondence with Geert Decorte who experienced the following python 2.4 error Assuming by both patches you mean the two patches you attached that were posted here some time ago, both of those _did_ make it into the Freevo 1.5.4 bugfix release. It would definitely have been a major SNAFU if they didn't, because the entire point of the 1.5.4 release was to include these fixes. :) Just to make sure I wasn't losing my sanity, I redownloaded the 1.5.4 tarball from sf.net and indeed these patches were correctly included. r = fcntl.ioctl(self.device, long(QUERYCAP_NO), val) OverflowError: long int too large to convert to int This line of code doesn't exist anywhere in Freevo 1.5.4. It shouldn't happen. http://gedeco.no-ip.org -- This message has been scanned for viruses and dangerous content by OpenProtect(http://www.openprotect.com), and is believed to be clean. --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ Freevo-users mailing list Freevo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-users
[Freevo-users] dvb-t card?
Hi. I'll buy a dvb-t card soon. I've been reading the freevo wiki, and also some info at linuxtv.org and others. But I don't know what to buy. I think that the best choice for my would be the wintv nova-t, for price and availability, but I'm not sure. Will it work well out of the box? Does it support all the needed features? I don't know, because I've readed that there might be problems in some cases. I also don't know which are all the needed features. So I'm asking you to get some advice. If this helps, I live in Spain. regards Alberto --- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_id=7637alloc_id=16865op=click ___ Freevo-users mailing list Freevo-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freevo-users
