Forum Replies Created
-
Posts
-
The strange characters embedded in the filenames of non-freesat recordings are unicode control characters.
† Dagger 0x86 (134) – control character: START OF SELECTED AREA
‡ Double Dagger 0x87 (135) – control character: END OF SELECTED AREA
With regard to the ‘i7’ text. This occurs only at the head of some text strings within an .hmt file.
Although I must say, I’ve never seen a recording made on the HDR with an ‘i7’ included as part of the filename, only as a string header embedded within the .hmt file.
Text strings in the .hmt file are preceded by a header byte. This is usually 0x15 (21). However if this header byte is 0x10 (16) then two extra characters are prepended to the text string.
These characters are 0x69 (105) and 0x37 (55) which equate to the ascii text string ‘i7’.
And they don’t just occur at the beginning of the recording title, they can also precede the channel Name for i-Plate, channel name for media list, and the program synopsis text in each EPG block.
However, it’s a simple matter when parsing text strings from the hmt file, to test the value of the header byte and adjust the read offset accordingly.
The reasons why these unicode characters appear in non-freesat recordings filenames, and why some text strings in the hmt file have an additional two characters prepended is known only to Humax, and unfortunately they are not telling.
technogoat – 11 hours ago »
Hi
Unless I drag only only one or two mp3 files at once, I get a message that the operation can’t be done as there isn’t enough free space, which is clearly not the case. If I do one at a time, no problem, but this would take an age. Can anyone advise?
It’s because the folder sizes under the samba ‘Media’ share are being being wrongly reported as 61MB. See this post for details
http://www.avforums.com/forums/15577158-post256.html
The fix is to install a new samba config file with separate shares defined for Music, Photo and Video. See this post for details
Dysanovic – 1 hour ago »
If I try streaming a HD recording I just get a black screen.
I realize that this is due to these recordings being encrypted. What I want to know is if there is a way to sucessfully stream these recordings, as I don’t want to copy these big files to my PC. Surely it must be possible as we have the encryption key on the Humax box (in the .hmt file?)
Has anyone achieved this? If so how?
Unfortunately, it’s not that simple. If it was that easy it would have been done already. The encryption key is not in the .hmt file, it is hidden somewhere in the box’s hardware and is unique to each box. You can’t even play an encrypted recording on another HDR, so unless you are a reverse engineering genius you’ll just have to be happy with what you’ve got. Sorry !
ZeroRam – 1 day ago » …. so it seems I may have to delve into the box myself and see what I can find out – I may be gone some time!
There are no separate images as such for the HDR’s GUI. All images are stored in large library files in Humax’s own proprietary format. These files can be found in the /usr/image folder. They would need to be decoded, modified, re-encoded, then a new firmware built to include the mods. Sure you still want to go there ?
pbeckett – 4 hours ago »
I have file transfer working (using samba) and it it excellent apart from the speed. Transferring from my PC to my HDR maxes out at around 48Kb so everything takes forever. Is this low speed expected?
No, I get 5.5MB per second using homeplugs to connect my HDR to the router.
Looking at your PuTTY screen capture your attempting to connect to the HDR on port 9000 which is the one used by TwonkyMedia web interface. You must use port 23 to connect via telnet.
paulburke – 1 day ago »
Guys,
Don’t know if this can be of any use:
Paragon HFS+ 9.0 for Windows Special Edition
Free fully licensed version today only!
Off topic !
Martin Liddle – 59 minutes ago »
Tim – 6 minutes ago »
I know that Humax have their own Dongle but I thought I would try one which I already have. It’s an Edimax EW-7717Un which works perfectly with my PC.
I have read that some people are using the Edimax EW-7711 series and would have thought the 7717 would work just as well if not better.
I would guess that the issue is that the 7717 probably uses a different chip set to the 7711. The Humax will only work with a single chip set and hence you need to use a dongle that uses the same chip set as the Humax supplied one.
Chipset is Ralink RT3070. Check out the thread on hummy.tv for more details on compatible dongles.
http://hummy.tv/forum/threads/hdr-fox-t2-wireless-dongle.127/
And be aware that as well as having a compatible dongle plugged in, there must be no ethernet cable connection to the rear RJ45 socket before the wifi option is enabled.
Martin Liddle – 32 minutes ago »
Always worth reading the FAQs. See http://myhumax.org/forum/topic/details-of-some-of-the-icons
FAQ’s are for the on-screen icons. OP requested info on LCD display.
sloppyjoe – 30 minutes ago »
I have installed the firmware and also Mediatomb, which all works brilliant, however I want to check the start-up options.
So I HTTP’d into http://Foxsat-HDR:49152, but I cannot seem to see where to check the options. I can see all the folders, including MediaTomb and Config, what next ?
Read the MediaTomb documentation available from here: http://mediatomb.cc/pages/documentation
Thanks for that info Graham. I suspected that the copy option would not decrypt SD recordings, but it’s good to have it confirmed.
Thanks for the explanation of the mechanism of the client/server relationship. However, that wasn’t exactly what I asked. i.e. How do two people with the exact same setup get different results? Your client can see .flac files in the HDR’s media list and and attempt to play them. I can’t even list them. Anyway, I’ll just leave it at that. Good luck with your endeavours.
In the light of my experience with Whitebear I’m curious to know how your client managed to get the HDR T2 to even list the non-MP3 audio files. Very strange…
1. Correct
2a. Correct, and they are playable.
2b. Correct.
3. Correct. So yes, 2a would apply, and no, they are not playable. When I tried it yesterday I didn’t notice it had skipped from the renamed FLAC to a genuine MP3 in the same folder which contained the same audio content. (I was not looking for this as your first post did not fully explain the nature of the problem)
