• The forum software that supports hummy.tv will be upgraded to XenForo 2.3 on Wednesday the 20th of November 2024 starting at 7pm

    There will be some periods where the forum is unavailable, please bear with us. More details can be found in the upgrade thread.

Extract program metadata from downloaded HMT file

I've updated the Linux and Solaris versions to match the native version just released.
I built the Solaris one on an Illumos system but it /should/ work on Solaris - let me know if not and I'll dig out a Solaris system.
 
It's definitely 2.0.6, could it be cached?
Code: 
# strings hmt-linux | grep 2.0
2.0.6
 
af123 said:
It's definitely 2.0.6, could it be cached?
Click to expand...
<sigh>
Yes. With Wget, the header returns this, which looks perfectly reasonable:
Last-Modified: Fri, 04 Sep 2015 21:52:35 GMT
so why are flamin' browsers so unreliable with this stuff?
</sigh>
 
So, poking at the browser debugging:
Code: 
Request URL: http://hpkg.tv/misc/hmt-linux

Request headers:
Host: hpkg.tv
User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:40.0) Gecko/20100101 Firefox/40.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-GB,en;q=0.5
Accept-Encoding: gzip, deflate
Connection: keep-alive

Response headers:
Accept-Ranges: bytes
Content-Length: 22408
Date: Mon, 31 Aug 2015 12:34:31 GMT
Etag: "5788-5177c1598a3ba"
Last-Modified: Mon, 01 Jun 2015 22:09:49 GMT
Server: Apache
And with Wget:
Code: 
wget -d http://hpkg.tv/misc/hmt-linux
DEBUG output created by Wget 1.15 on linux-gnu.

URI encoding = ‘UTF-8’
--2015-09-04 23:48:19--  http://hpkg.tv/misc/hmt-linux
Resolving hpkg.tv (hpkg.tv)... 89.248.55.75, 2a00:5600:1600::50
Caching hpkg.tv => 89.248.55.75 2a00:5600:1600::50
Connecting to hpkg.tv (hpkg.tv)|89.248.55.75|:80... connected.
Created socket 3.
Releasing 0x0000000002233bd0 (new refcount 1).

---request begin---
GET /misc/hmt-linux HTTP/1.1
User-Agent: Wget/1.15 (linux-gnu)
Accept: */*
Host: hpkg.tv
Connection: Keep-Alive

---request end---
HTTP request sent, awaiting response...
---response begin---
HTTP/1.1 200 OK
Date: Fri, 04 Sep 2015 22:48:19 GMT
Server: Apache
Last-Modified: Fri, 04 Sep 2015 21:52:35 GMT
ETag: "c445-51ef2eae96db1"
Accept-Ranges: bytes
Content-Length: 50245
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive

---response end---
200 OK
Registered socket 3 for persistent reuse.
Length: 50245 (49K)
Saving to: ‘hmt-linux’

100%[================================================>] 50,245  --.-K/s  in 0.07s   

2015-09-04 23:48:19 (694 KB/s) - ‘hmt-linux’ saved [50245/50245]
I'm none the wiser really...
 
Set pref. "browser.cache.check_doc_frequency" to "1" on Firefox (about:config) to stop all this stupidity.
It's probably set to "3" by default, which looks like it should do the right thing, but obviously doesn't.
 
Could I request an update to 2.0.8 for hmt-linux at some convenient point please?
 
A request, please, for af123 & raydon:

would you please consider either:

- merging this hmt (for FOX-T2) with the hmt for FOXSAT-HDR?

- having a wee scripty that identifies the type of hmt file, and runs the correctly-named existing hmt binary for that platform?

I could do the latter myself, if there were a unique identifying byte sequence to tell me which is which?

I archive my recordings, from both types of Humax recorder, in the same area on the telly, and always have to try both hmt binaries.

I could store the two types of files separately, but that seems silly, as they are both MPEG-TS files (the video files, at least) and both play fine using the same utilities - so having separate dir hierarchies, solely to tell me which flavour of hmt binary to use, doesn't seem sensible either.

thanks much indeed for considering...
 
You must log in or register to reply here.
Back
Top