Post Record action advice?

[mvallevand]

If the script is open it is still running. Several minutes would be a good copy of 10GB.

Kodi and other files will play the original file until the script finishes completed. If they have it open they can corrupt the transfer. One of the downsides of an active move is you can't watch in progress recordings.

Martin

[three6zerocool]

Tried dropping another couple of recording on test.bat

This time the CMD windows closed after transferring the files, and it created a logfile.

So, seems to be working.
I do notice that a folder of each recorded show is left behind on the NVME 'TV Recordings' folder, at although all the right files seem to have moved, a folder for each show is still present, and each folder contains a .map file)

[three6zerocool]

I think I messed up.

Nscripthelper apparently needs the server pin, which I did not have configured inside the script.

Also when manually testing the script, I did not remove the 'rem' comment as mentioned.

Testing again...

[three6zerocool]

(grin)  I think I messed things up even more.

Everything is working as it should.  (I think)
The problem is that I nuked my record path, and set it to the NVME drive, and used same path name as before, except now on local drive  'D:\TV Recordings'

Then when I could not see my existing recordings, I added the old path back in '\\TrueNAS\TV Recordings'

When I activated the postpocessing.bat, it seems to have worked and copied all the files, however the database results were mixed, and I could not see all of the shows I recorded listed.

I discovered what has happened,  further down the list of existing recordings, I now have a folder called 'TV Recordings' (inside my NAS located TV Recordings folder), and it contains all of the new recorded shows, and a couple of them are also in the original list of recorded shows. (perhaps from when  I was test dropping TS files on the test.bat)

So, I think having the same name for both record paths seems to have caused this?

I have reverted my system back in the meantime to just using the NAS,  and will create a new VM and mess around further.

[three6zerocool]

Oh,  I started looking at speed of my NAS, but not quite sure what I am doing there.
One suggestion was to use iperf3, but need to read some stuff before messing with it.

My understanding is that you enable one machine as a server, and another as a client, then test.

As I use TrueNAS Scale,  I discovered that one of the available apps is something called OpenSpeedTest (or something similar)
I tried it, and it downloaded files, and then uploaded files, and reported a fraction under 2500 mbit.

The Nas pool is comprised of six  Ultrastar datacenter series drives in a Z2 configuration.
(meaning 2 drives can fail before data loss)

Not sure what kind of thruput would be considered normal for the above configuration?

[three6zerocool]

Currently, I have the NVME configured as the timeshift location, and I notice that channel changes etc seem faster and more snappy.

In regards to timeshift location and buffer settings in the Kodi pvr addon,  are there any recommended settings for using in 'timeshift' as Live TV Method.
ie.  I have these settings currently set:

Pre Buffer Time in seconds 2
Live TV Chuck size             64
Recording Chunk Size         32

And I have 'enable direct streams' deactivated.

I have messed around a bit with different settings.
If I set the buffer to 0,  then kodi will start buffering shortly after playback begins.

[mvallevand]

The Kodi defaults should be fine, options are for user testing for their use cases.

Channel changes in Kodi in timeshifting will probably not be too different because of data buffering.

[gEd]

I discovered what has happened,  further down the list of existing recordings, I now have a folder called 'TV Recordings' (inside my NAS located TV Recordings folder), and it contains all of the new recorded shows, and a couple of them are also in the original list of recorded shows. (perhaps from when  I was test dropping TS files on the test.bat)

yep. that's why in post #6 I said

Just keep in mind that how it works at the moment is that it copies the entire folder name minus the driver letter. so if the existing recording is on c:\TV Recordings\show_name and you want the destination will end up as \\TRUENAS\TV Recordings\show_name set set destPath=\\TRUENAS \%~p1.

(and not s[i]et destPath=\\TRUENAS\TV Recordings %~p1. )[/i]

btw, I'm out of town for a few days. Good luck with it.

[three6zerocool]

Update:

I think I have the postprocessing script working now.
Had issues getting the database to update, then realized I had to enter pin number and the IP/Port of the NextPVR server to use nscripthelper.


I have just the NVME drive set as the record path in NextPVR settings.
It records the show to the NVME drive, and then starts copying the file to the NAS.

When complete it uses nscripthelper to rename the file to point to the NAS.

I test playback, and it works fine, and is playing from the NAS, cause the show is deleted on the NVME drive.

I have one issue tho, and that is that when the process is complete, I am left with an empty folder of the recorded show name.

eg.  If I recorded the show 'The Simpsons'     I end up with an empty folder called 'The Simpsons' on the NVME drive.

Attached is the script that is working, but leaving the empty folders behind.

[three6zerocool]

Update 2:

Found I could avoid the folder left behind issue by turning off <AutoCreateFolders> in config.xml.
However, from an organizational perspective it maybe is messy for some to do this. (including myself)

Also discovered that these xcopy switches  /z /j /y /i /h    in the script make my NAS go mental and make the loudest seeking noises imaginable and takes an eternity to actually copy the files.
I changed them to /e /f /J /Y and the file copy is now virtually silent, and it copies the files super-fast. (like a 16GB recording in less than 30 seconds)

As Martin pointed out, watching show whilst recording prevents the script from shifting to the NAS.

But, I found if I drop the NVME .ts file on the batch file, that it moves it to the NAS.
Of course it still leaves the folder behind, so, that's the one little issue to clean up.