I run a script that transcodes new shows every night that I developed for Plex DVR and EyeTV. It works well, doesn’t slow down my server, and gives me great archival quality mp4/m4v h.264 files (using HandBrakeCLI) that stream well across the internet. Given that Plex seems to be compatible with the Channels DVR file structure, I was thinking it would be useful to just keep the new recordings in the same structure. However, I’m uncertain as to how that might affect the database, especially if the show is deleted. I tried it out on a show I was going to delete, placed an identically-named show in the same folder albeit with a different suffix (mp4), and then deleted the show from within the Channels DVR interface to see what would happen. To my surprise, nothing did, i.e. it was removed from the Apple TV interface, but nothing was removed from the file structure. In short, I don’t know how Channels DVR handles deletion of files and whether using the Channels DVR file structure for transcoded data is even viable.
Is there any way to replace the recorded show with an Apple TV compatible mp4/m4v file with the same name (different suffix) and still be able to view it in Channels DVR? If so, would that also preserve the very effective commercial skipping data?
Could you explain why, when I delete a show, it doesn’t remove files from the drive? Is it perhaps queued? How is deletion implemented server-side?
Do you have plans in the near-future to integrate transcoding? I notice the .ffsplit files, which will prove useful if your comskip method is as successful as it has been so far. If so, do you already have guidelines as to how to manage the transcoded copy?