<br><br><div><span class="gmail_quote">On 9/1/05, <b class="gmail_sendername">Brian Stults</b> <<a href="mailto:bstults@crim.ufl.edu">bstults@crim.ufl.edu</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Nick wrote:<br>> On 9/2/05, Brian Wallen <<a href="mailto:brian_wallen@hotmail.com">brian_wallen@hotmail.com</a>> wrote:<br>><br>>>I'm using a remote frontend, and samba to watch the recordings from the<br>
>>backend. I'm doing this because its the only way I know to share files over<br>>>a network, although I know it can be done with NFS. When I skip forward in<br>>>a recording, the length of the recording fluctuates. So if a recording is
<br>>>say, 30 minutes, when I hit the skip button it will fluctuate wildly between<br>>>about 29:30 and 30:30. Would this happen if I used NFS?<br>><br>><br>> I doubt it would, they're the same files in the end. I'd make sure
<br>> your database tables are all OK firstly, as this is known to cause<br>> oddities in reported recording length and issues when navigating<br>> through a file. Also, what type of recordings are these? DVB, HDTV or
<br>> capture card source? I normally have no problems with DVB files, but<br>> ivtv files sometime have really erratic recording lengths displayed.<br>><br><br>Be sure that your remote frontend is able to access the mysql database
<br>on the backend. Check the mythtv documentation for mention of the<br>"skip-innodb" option in my.cnf.<br><br></blockquote></div><br>
If it couldn't then he'd have bugger problems.<br>