<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:arial,sans-serif;font-size:large;color:rgb(68,68,68)"><br></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Wed, May 20, 2026 at 3:46 PM James Abernathy <<a href="mailto:jfabernathy@gmail.com">jfabernathy@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr"><div style="font-family:arial,sans-serif;font-size:large;color:rgb(68,68,68)"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, May 20, 2026 at 1:14 PM Stephen Worthington <<a href="mailto:stephen_agent@jsw.gen.nz" target="_blank">stephen_agent@jsw.gen.nz</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Wed, 20 May 2026 10:41:08 -0400, you wrote:<br>
<br>
>The wiki has a lot of old ideas about exporting videos but not sure if they<br>
>are the way to go with V36.<br>
><br>
>My desire is to move one year of episodes that are still on an old dormant<br>
>v36 back-end to my new v36 back-end. The old back-end is still running but<br>
>not recording anything new. I would like to hold on to the season/episode<br>
>numbers and maybe the subtitle if possible. The old recordings do have a<br>
>cut list/commercial flags, etc. but it's not critical to preserve them. I<br>
>don't want to take the processing time to transcode these. Just keeping<br>
>them in their MPEG2 .TS file format is fine.<br>
><br>
>My plan B is to use a script I use as a UserJob to cut the commercials,<br>
>transcode to h264 and store is the Storage Group Videos, but that seems<br>
>overkill for this effort.<br>
><br>
>Ideas??<br>
><br>
>Jim A<br>
<br>
If you are wanting to export and import recordings rather than videos,<br>
I do that all the time using mythexport/mythimport. Mythexport uses a<br>
background job that looks for export jobs queued in a database table.<br>
When it sees a new recording in the queue, it dumps the SQL data for<br>
the recording to a .sql file in a designated location and copies the<br>
recording file there also. The location can be any normal path name,<br>
including network paths or a USB stick or an external hard drive. Jobs<br>
are added to the queue using PHP code in Apache2. You use a browser<br>
to access the page <my web server>/mythexport and it produces a list<br>
of all your recordings to select from. At the other end, you just put<br>
the exported recording files and SQL files in a directory of that<br>
MythTV box and run mythimport in that directory. I am still running<br>
v35 and it is working there, but I have not tested it on v36 yet. If<br>
the recording tables have not changed between versions, it will work<br>
in v36. If there are changes, it is usually pretty easy to just add<br>
some new field names to the exported fields list.<br>
<br>
The recording data is all copied, but if the two boxes do not agree on<br>
what the chanid values are for the channels, the wrong channel name<br>
may be displayed, or a #<chanid> number if there is no matching<br>
channel. You do get the full seektable data and commercial flagging<br>
data. I think cut lists will also be copied as they are stored in the<br>
seektable, but as I do not use cut lists, I can not confirm that. The<br>
recordedid values are specific to a MythTV instance, so they are not<br>
preserved and new recordedid values are created on the new box.<br>
<br>
Let me know if you want to try mythexport/mythimport and I will put<br>
all the required files in an archive on my web server. The version<br>
already there is a bit out of date. I use Ubuntu so the systemd file<br>
use to run mythexport is specific to Ubuntu, but should be able to be<br>
adapted to other distros. You do need to have Apache2, PHP, Perl and<br>
Python 3 installed and the MythTV support modules for Perl and Python.<br>
<br>
For doing mass copying of recordings, I also have a utility mythsgu<br>
that will copy all recordings in a directory to another MythTV box<br>
where you can then run mythimport on them, rather than using<br>
mythexport. It is a bit broken at the moment as it uses a Python<br>
library that has been removed from the latest versions of Python, so<br>
you have to install an older Python version and run it with that.<br>
Which is all a bit tricky to set up, so is not recommended at the<br>
moment.<br><br></blockquote><div><br></div><div style="font-family:arial,sans-serif;font-size:large;color:rgb(68,68,68)">Thanks for the explanation. I'm more convinced to just use my sendTVtoNAS script.</div><div style="font-family:arial,sans-serif;font-size:large;color:rgb(68,68,68)"><br></div><div style="font-family:arial,sans-serif;font-size:large;color:rgb(68,68,68)">It uses mythtranscode to honor the cutlist and output to a temp file. Then it uses handbrake-cli to transcode the temp file to mv4 with a high quality setting and creates the filename with the title, subtitle, and season/episode numbers concatenated. Mythutil --scanvideo does a good job pulling in the TVdb info. </div><div style="font-family:arial,sans-serif;font-size:large;color:rgb(68,68,68)"><br></div><div style="font-family:arial,sans-serif;font-size:large;color:rgb(68,68,68)">I watch this all using Leanfront. From a user point of view, a recorded TV program and Video work about the same.</div><div style="font-family:arial,sans-serif;font-size:large;color:rgb(68,68,68)"><br></div><div style="font-family:arial,sans-serif;font-size:large;color:rgb(68,68,68)">Jim A</div><div style="font-family:arial,sans-serif;font-size:large;color:rgb(68,68,68)"><br></div></div></div></blockquote><div><br></div><div style="font-family:arial,sans-serif;font-size:large;color:rgb(68,68,68)" class="gmail_default">Well this was a surprise. I was playing with my recordings and videos and for the first time using the Web App I clicked on the download button on one of my Recorded TV programs and I received into my Downloads folder the .TS file but it had the Title, subtitle, and season/episode number all concatenated as the filename. This file could now be moved to my video directory on the new backend.</div><div style="font-family:arial,sans-serif;font-size:large;color:rgb(68,68,68)" class="gmail_default"><br></div><div style="font-family:arial,sans-serif;font-size:large;color:rgb(68,68,68)" class="gmail_default">This accomplishes what my script did without the transcoding. So much quicker.</div><div style="font-family:arial,sans-serif;font-size:large;color:rgb(68,68,68)" class="gmail_default">Still needed to run mythutil --scanvideos on the backend to make it available in the Watch Videos.</div><div style="font-family:arial,sans-serif;font-size:large;color:rgb(68,68,68)" class="gmail_default"><br></div><div style="font-family:arial,sans-serif;font-size:large;color:rgb(68,68,68)" class="gmail_default">Jim A</div><div style="font-family:arial,sans-serif;font-size:large;color:rgb(68,68,68)" class="gmail_default"><br></div></div></div>