Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: MythTV: Mythtvnz

Upgrading to 0.25 from 0.23

 

 

MythTV mythtvnz RSS feed   Index | Next | Previous | View Threaded


dmoo1790 at ihug

Apr 26, 2012, 9:01 PM

Post #1 of 3 (409 views)
Permalink
Upgrading to 0.25 from 0.23

I was finally forced to upgrade from 0.23 due to the audio glitch on
Prime. Could have patched 0.23 I suppose but decided to bite the bullet
and go to 0.25. Works fairly well as far as I have tested so far. Thanks
to fellow listers for setup/bugfix clues and myth devs for rapid repairs
to code.

I am seeing incorrect video lengths on some old recordings. Annoying. I
have noticed in the past that this could be a seek table issue. I found
in the past that using mythcommflag to rebuild the seek table for some
recordings produced incorrect time codes. Forget the details but had to
divide seek table entries by two to fix.

_______________________________________________
mythtvnz mailing list
mythtvnz [at] lists
http://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/


steven at openmedia

Apr 26, 2012, 9:44 PM

Post #2 of 3 (387 views)
Permalink
Re: Upgrading to 0.25 from 0.23 [In reply to]

On Fri, April 27, 2012 4:01 pm, David Moore wrote:
> I was finally forced to upgrade from 0.23 due to the audio glitch on
> Prime. Could have patched 0.23 I suppose but decided to bite the bullet
> and go to 0.25. Works fairly well as far as I have tested so far. Thanks
> to fellow listers for setup/bugfix clues and myth devs for rapid repairs
> to code.
>
> I am seeing incorrect video lengths on some old recordings. Annoying. I
> have noticed in the past that this could be a seek table issue. I found
> in the past that using mythcommflag to rebuild the seek table for some
> recordings produced incorrect time codes. Forget the details but had to
> divide seek table entries by two to fix.


Hi David

I've been using the following to fix seektables. I've found that
mythtranscode was a lot more reliable than mythcommflag and I now have a
user job I can easily select when I've got a broken video file.

http://www.mythtv.org/wiki/Repairing_the_Seektable#Automation_of_mythcommflag_repair_function


--------------------------------------------
Steven Ellis - Technical Director
OpenMedia Limited - The Home of myPVR
email - steven [at] openmedia
website - http://www.openmedia.co.nz

_______________________________________________
mythtvnz mailing list
mythtvnz [at] lists
http://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/


dmoo1790 at ihug

Apr 26, 2012, 10:08 PM

Post #3 of 3 (383 views)
Permalink
Re: Upgrading to 0.25 from 0.23 [In reply to]

On 27/04/12 16:44, Steven Ellis wrote:
>
> On Fri, April 27, 2012 4:01 pm, David Moore wrote:
>> I was finally forced to upgrade from 0.23 due to the audio glitch on
>> Prime. Could have patched 0.23 I suppose but decided to bite the bullet
>> and go to 0.25. Works fairly well as far as I have tested so far. Thanks
>> to fellow listers for setup/bugfix clues and myth devs for rapid repairs
>> to code.
>>
>> I am seeing incorrect video lengths on some old recordings. Annoying. I
>> have noticed in the past that this could be a seek table issue. I found
>> in the past that using mythcommflag to rebuild the seek table for some
>> recordings produced incorrect time codes. Forget the details but had to
>> divide seek table entries by two to fix.
>
>
> Hi David
>
> I've been using the following to fix seektables. I've found that
> mythtranscode was a lot more reliable than mythcommflag and I now have a
> user job I can easily select when I've got a broken video file.
>
> http://www.mythtv.org/wiki/Repairing_the_Seektable#Automation_of_mythcommflag_repair_function
>
>
> --------------------------------------------
> Steven Ellis - Technical Director
> OpenMedia Limited - The Home of myPVR
> email - steven [at] openmedia
> website - http://www.openmedia.co.nz

Hi Steven, Yes, that will be my last resort method. Thing is I don't
think it's necessary as I don't think the actual seek table values get
updated. Makes sense because the files are seekable but just have wrong
durations. I think the fix is in recordedmarkup but need to figure out
how to generate correct values. Reason I think this is I noticed the
files rebuilt had new rows in recordedmarkup. If we can work out the
correct values then a real fast sql patchup would do the trick much
faster than mythcommflag.

_______________________________________________
mythtvnz mailing list
mythtvnz [at] lists
http://lists.ourshack.com/mailman/listinfo/mythtvnz
Archives http://www.gossamer-threads.com/lists/mythtv/mythtvnz/

MythTV mythtvnz RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.