You can also copy them over a network but my 1000T uses Samba 1.0, which Windows 10 disabled in a recent update as it’s a security exposure. I’ll just list the steps as I got it working & others may find this of use. You can install Samba 1.0, but probably wise to revoke it when finished, Samba 3 or later is fine but the PVR won’t talk to it (I think the current version is 5). Samba is used for Linux & Microsoft systems to talk to each other, Linux to Linux doesn’t require it (the Humax OS is some form of Linux).

Windows 10 Samba 1 removed in 2019 update

Oddly, both old & new versions of Windows Media Player loads the content over the network without Samba, even though a file expolorer rejects the Samba version. This is handy to identify filenames. The Win10 media player is called ‘Film & TV’ and while it will play the rfiles form the Humax, it doesn’t provide file properties, so the older version is more useful.

I’d recommend copying your files & then switch back to only a later version of Samba. I have a QNAP NAS and this is quite easy to toggle. I copied the files using a NAS tool (DownloadStation) but this might also work with an FTP or SSH client. After a bit of experimenting, I found the files to be in two formats and could be copied using the address:

For *.hum file properties in Windows Media Player, copy the name from properties up to the ‘?’, ignore from the ‘?’ on. Then paste the path but remove the ‘.HUM’ extension and change it to ‘.ts’.

eg If the PVR address is 192.168.1.20, Media player propeties for a recording were

http://192.168.1.20/web/media/0_2781.HUM?WMHME=etc..etc..[/CODE]

So to copy, use:
[CODE]http://192.168.1.20/web/media/0_2781.ts[/CODE]

The other format were dlna file names and you can use the above format and substitue the file number found in the properties. eg Media Player properties of a recording were:

[CODE]dlna-playsingle://uuid:etc..etc..:ContentDirectory&iid=0_0189874&WMQ=etc ..etc..[/CODE]

You only need the 3 or 4 digit number from this, 9874 in this example:
[CODE]http://192.168.1.20/web/media/0_9874.ts[/CODE]

I’m unclear what the other numbers are, so some testing may be needed for larger libraries etc. GB files copied over the home lan to the NAS in a few minutes. The QNAP NAS has built in hardware transcoding but wasn’t needed here, unless you want it to cut the resolution (& file size) down for you automatically.

FYI there have been legions of issues & complaints over the past few years with issues in retaining Windows user drive mapping to Linux/Unix network servers & NAS hosts, and these issues are largely related to mixed Samba versions. If you have these issues, the Samba note from MS is worth bookmarking.

[CODE]http://192.168.1.20/web/media/0_2781.HUM?WMHME=etc..etc..[/CODE]

So to copy, use:

http://192.168.1.20/web/media/0_2781.ts%5B/CODE%5D

The other format were dlna file names and you can use the above format and substitue the file number found in the properties. eg Media Player properties of a recording were:

[CODE]dlna-playsingle://uuid:etc..etc..:ContentDirectory&iid=0_0189874&WMQ=etc ..etc..[/CODE]

You only need the 3 or 4 digit number from this, 9874 in this example:
[CODE]http://192.168.1.20/web/media/0_9874.ts[/CODE]

I’m unclear what the other numbers are, so some testing may be needed for larger libraries etc. GB files copied over the home lan to the NAS in a few minutes. The QNAP NAS has built in hardware transcoding but wasn’t needed here, unless you want it to cut the resolution (& file size) down for you automatically.

FYI there have been legions of issues & complaints over the past few years with issues in retaining Windows user drive mapping to Linux/Unix network servers & NAS hosts, and these issues are largely related to mixed Samba versions. If you have these issues, the Samba note from MS is worth bookmarking.

[CODE]http://192.168.1.20/web/media/0_2781.ts[/CODE]

The other format were dlna file names and you can use the above format and substitue the file number found in the properties. eg Media Player properties of a recording were:

dlna-playsingle://uuid:etc..etc..:ContentDirectory&iid=0_0189874&WMQ=etc ..etc..[/CODE]

You only need the 3 or 4 digit number from this, 9874 in this example:
[CODE]http://192.168.1.20/web/media/0_9874.ts[/CODE]

I’m unclear what the other numbers are, so some testing may be needed for larger libraries etc. GB files copied over the home lan to the NAS in a few minutes. The QNAP NAS has built in hardware transcoding but wasn’t needed here, unless you want it to cut the resolution (& file size) down for you automatically.

FYI there have been legions of issues & complaints over the past few years with issues in retaining Windows user drive mapping to Linux/Unix network servers & NAS hosts, and these issues are largely related to mixed Samba versions. If you have these issues, the Samba note from MS is worth bookmarking.

[CODE]dlna-playsingle://uuid:etc..etc..:ContentDirectory&iid=0_0189874&WMQ=etc ..etc..[/CODE]

You only need the 3 or 4 digit number from this, 9874 in this example:

http://192.168.1.20/web/media/0_9874.ts%5B/CODE%5D

I’m unclear what the other numbers are, so some testing may be needed for larger libraries etc. GB files copied over the home lan to the NAS in a few minutes. The QNAP NAS has built in hardware transcoding but wasn’t needed here, unless you want it to cut the resolution (& file size) down for you automatically.

FYI there have been legions of issues & complaints over the past few years with issues in retaining Windows user drive mapping to Linux/Unix network servers & NAS hosts, and these issues are largely related to mixed Samba versions. If you have these issues, the Samba note from MS is worth bookmarking.

[CODE]http://192.168.1.20/web/media/0_9874.ts[/CODE]

I’m unclear what the other numbers are, so some testing may be needed for larger libraries etc. GB files copied over the home lan to the NAS in a few minutes. The QNAP NAS has built in hardware transcoding but wasn’t needed here, unless you want it to cut the resolution (& file size) down for you automatically.

FYI there have been legions of issues & complaints over the past few years with issues in retaining Windows user drive mapping to Linux/Unix network servers & NAS hosts, and these issues are largely related to mixed Samba versions. If you have these issues, the Samba note from MS is worth bookmarking.

Mr345 – 1 hour ago  » 

You can also copy them over a network but my 1000T uses Samba 1.0, which Windows 10 disabled in a recent update as it’s a security exposure.

Please could you clarify exactly which model of Humax box you have?

Mr345 – 1 hour ago  » 

HMS-1000T (4tune)

Bought in June 2015. Currently not displaying any video at all, hence my need to copy recordings remotely, a network connection is the only way I can see what’s going on.

No wonder the confusion. The Thread is about the Foxsat-HDR which is a UK based satellite pvr using the UK based Freesat epg.

Samba 1.0 can be installed on Windows 10. I have it on my laptop that has the latest Windows 10 update,

https://www.windowscentral.com/how-access-files-network-devices-using-smbv1-windows-10

The HDR-1100S mentioned is a UK based 2nd generation freesat satellite pvr.

Pretty sure the HMS-1000T is a Humax pvr sold in Australia. You are unlikely to find a member of a UK based forum has this box and it’s unlikely to work here at all due to differences in the Digital broadcasting system between the UK and Australia (eg the channel spacing is different).

Thanks Graham, I knew the boxes were different but wouldn’t have thought they’d change the Linux file structure of their basic OS port, but an assumption on my part so apologies for any confusion.

I noted above you can install earlier Samba version, but not a good idea to leave it up unless you’re well firewalled etc. It’s pretty antique & a well know security. Thanks for the feedback.