On 1/10/07, stuart <[EMAIL PROTECTED]> wrote: > > > G C wrote: > > On 1/9/07, stuart <[EMAIL PROTECTED]> wrote: > >> Very interesting... I have the same problem. I just thought I had done > >> yet something else wrong w/my back end. But, now that you mention it, > >> it all started after I added a KWorld ATSC110 tuner card. > >> > >> I don't know if your dump is complete enough to help. I didn't write > >> the MythTV code - but it (and my dump) didn't look very interesting. I > >> then invoked mvpmc w/the -M option and got dumped on big time. Here is > >> the end of the dump with the boring parts changed to "....": > > > > I went back and did a more complete dump. I ended up with a text file > > over 1MB. I'll e-mail the complete file to a developer if needed. > > But here's the short version... I saw the backend begin to enumerate > > all of my recordings and the details for them. Somewhere in the > > middle, it looks like things begin to go off the rails. > > Interestingly, it looks like the same return value is tripping up both > > of us (per your most recent post). I took a look at the last > > recording that was enumerated and I believe the next recording it > > would have done was the very first recording made on Tuner 2, the new > > digital tuner I installed. Is it the same in your case? > > How can you tell? After poking around for 10 minutes I see (maybe) the > file names of recorded shows, but I also see a lot of other text > strings. Some I can not figure out where from. Can someone comment on > the transaction between the mythtvbackend and mvpmc so we might be able > to pick out the cause of this problem. > > ...thanks
Just a wild guess. Is the file size for the recording that fails greater than 32 bits (4 Gig)? Does mvpmc handle file sizes that large? >From Rick's log, it seems like there is an out of range value: __cmyth_rcv_string: string received '4294967295' __cmyth_rcv_long: long long out of range: '4294967295' __cmyth_rcv_proginfo: cmyth_rcv_long() failed (34) The value printed is 2^32-1, which seems odd, but I haven't looked at the code. The high def recordings are going to be much larger, so I could see a bug just being noticed when HD recordings are present. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Mvpmc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mvpmc-users mvpmc wiki: http://mvpmc.wikispaces.com/
