On Fri, 30 May 2008, Roger Heflin wrote: >> Hi, >> >> Sorry for replying so late, kinda forgot about this thread... :) >> >> Anyway, I just got a H3 wireless MVP and am seing the same problems >> (not just when deleting). I'm up to 1900 movies/episodes on my MythTV >> backend and moving around in the mvpmc menus is an excersice in >> patience... selecting MythTV->Watch Recordings takes a long time to >> end up in a usable state. > > I am up to 720 and so far it is not that bad. > > I have noticed that it takes 3-5 seconds to load the shows, I am wondering if > it > would be faster to read in from a binary file located on NFS that contained > the show data, or put a binary file on NFS that at least contains the more > troublesome data and retrieve it as necessary (when one selects show info).
This sounds like a bit of a cludge, we'd be better off accessing the data directly over SQL than requiring some extra server-side functionality/files. If we had to resort to SQL for normal recordings then we might want to make it optional. It's nice that at the moment SQL access is only required for LiveTV. > From some looking around with the current method that mvpmc uses it is not > possible to grab a single recording's information. It may be possible if we > were using the xml method that is in the 0.21 and newer myth, and then it > would > be possible to not load/ignore the information that is not often used and > retrieve as necessary. > > Here is the current proginfo structure: > [snip large proginfo structure] > > So about 200 bytes per program before anything is allocated to any of the char > *. If something is allocated to the char *'s then there are a number of > bytes > for the reference counters for overhead for each allocation, plus the bytes > allocated. > > I suspect that a number of the entries aren't used anywhere except show_info > and > a number of the entries even if they are used in show_info aren't of any use > to > a person so could probably be ignored. It's worth noting that a (re-encoded) version of the data in this structure is passed back to MythTV to request playback of a recording, so you also need to determin what data in this structure MythTV uses/needs for file i/o. > I need to figure out a way to gauge how much memory is being used so I can get > an idea of how much is being saved. > >> >> Also, watching recordings through the MythTV interface simply doesn't >> work when I use the wireless network - if I start to watch something >> it takes a few minutes until anything appears, and then only in short >> bursts. I can see on the router lights and statistics that only a few >> packets every few seconds are actually transmitted... >> However, if I watch the same recording by selecting the .mpg file >> through the file browser it plays just fine, and I can see that the >> wireless traffic flows perfectly. Could this be because there is much >> more free (and less fragmented) memory when playing that way? My guess would be that this is related to the different block sizes in use for the MythTV protocol connection compared to the NFS connection, and them travelling better over NFS. Luckily for you you should be able to tell mvpmc to use NFS to play the file whilst still browsing through the MythTV interface. Simply add the -r /path/to/mythtv/mpegs to the command line options for mvpmc in your dongle.bin.config >> >> Finally, I wanted to ask if anything came from this discussion. Did >> anyone manage to test the proposed changes? If not, how long does it >> take to get to the point where I can play around with the code myself? >> I make my living as a codemonkey but haven't done much private coding >> in years except for a few private hacks in mythfilldatabase... >> >> / Niklas (op) >> It should be very easy. The normal build environment automatically downloads (into ~/downloads) everything required, and then automatically builds all the toolchains required (into ~/toolchains). The 2 major pre-requisits are the git version control system, and the scons "makefile replacement". On a debian system you can get both of these by doing an: apt-get install git-core git-gui scons Whilst the version of git in debian etch does work, it's a little old and lacks some of the functionality you may want, so if you're a debian user then I'd recommend getting the version from http://www.backports.org. Once you have git and scons installed you should be able to simply do: git clone git://git.mvpmc.org/repos/mvpmc.git and then: make And everything necessary should be downloaded/compiled. I think part of the toolchain build process still errors when it has succeeded, so you may find you have to run make a couple of times to get all the way through. Cheers, Simon ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Mvpmc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mvpmc-users mvpmc wiki: http://mvpmc.wikispaces.com/
