Opened 11 years ago

Closed 9 years ago

#6376 closed enhancement (duplicate)

Patch to save transcoded recordings

Reported by: cizek@… Owned by: cpinkham
Priority: minor Milestone: 0.24
Component: MythTV - Mythtranscode Version: unknown
Severity: medium Keywords:
Cc: Ticket locked: no

Description

Currently if you transcode a recording and have the "Save original files after transcoding" option checked, the original file is moved to a file suffixed by .old:

(i.e. 1021_20090319110800.mpg -> 1021_20090319110800.mpg.old)

The attached patches change this functionality as follows:

  • Create a new, valid filename (i.e. 1021_20090319110801.mpg)
  • Copy the recording info and markup data to reference the new filename
  • Set this new recording to be "Deleted"
  • Transcode the file
  • Move the original file to the new name (i.e. 1021_20090319110800.mpg.old -> 1021_20090319110801.mpg)

The end result is that the original recording, along with the seektable and any cutpoints, still exists as a "Deleted" recording. It can be watched, undeleted, re-transcoded, whatever. If it didn't transcode right, you can delete the transcoded file, undelete the original, adjust the cutpoints and try again.

This works for me, hopefully it'll work for you too.

Attachments (2)

142-savetranscode.fixes.patch (11.4 KB) - added by anonymous 11 years ago.
Patch for 0.21-fixes
142-savetranscode.trunk.patch (11.3 KB) - added by anonymous 11 years ago.
Patch for Trunk

Download all attachments as: .zip

Change History (6)

Changed 11 years ago by anonymous

Patch for 0.21-fixes

Changed 11 years ago by anonymous

Patch for Trunk

comment:1 Changed 11 years ago by cpinkham

Owner: changed from Isaac Richards to cpinkham
Status: newassigned

comment:2 Changed 10 years ago by cpinkham

Milestone: unknown0.23

Changing this ticket milestone to 0.23, but this functionality will probably be accomplished as part of a much larger rework to better integrate MythTV and MythVideo?? and allow for more code sharing between the two.

comment:3 Changed 10 years ago by cpinkham

Milestone: 0.230.24

Moving some things to 0.24 since we're almost at the 0.23 feature freeze.

comment:4 Changed 9 years ago by cpinkham

Resolution: duplicate
Status: assignedclosed

I'm going to close this ticket as a 'duplicate' like the other two tickets that I closed last week related to storage of filenames in the database. We are working on a larger reorg of database tables which will allow this functionality to be achieved in just a few lines of code rather than the large changes introduced in this patch. The concept of the patch is good, but the new table structure will allow us to associate both the original and newly transcoded files with the same exact 'recording' so the user can choose which to play or delete if they do not delete the original when transcoding.

Note: See TracTickets for help on using tickets.