Translate
IBU
Consol
|
|
Formats of Audio Video Media
File Systems & Files : Devices
Which file system types & file formats are compatible
with which software Tools & options,
& which hardware.
Index
- Matsui DVD225 - DVD hardware player
- Toshiba TV
40VL743G
-
Iomega High definition
multimedia player
- "Iomega ScreenPlay TV Link
HD Media Player Director Edition" Model SPTVLP
- Dead URL: http :// go . iomega . com / section ?
p = 4760 & amp ; secid = 42740 #
tech_specsItem_tab
- http:// iomega . com Is now a domain squater, so
not linked to;
- https://en.wikipedia.org/wiki/LenovoEMC
says Iomega was swallowed. Looks like it's now
abandoned.
-
Offline copy & notes
-
Humax Freesat+ Satellite HD
Digital Television Recorder Foxsat-HDR
Disk Content HDR -
1000S/GB/1TB Analysed 2017-11-11 with FreeBSD:
SATA 1T Disk
dmesg
da0 at umass-sim0 bus 0 scbus2 target 0 lun 0
da0: <ASMT 2105 0> Fixed Direct Access SCSI-6 device
da0: Serial Number 123456789012
da0: 40.000MB/s transfers
da0: 953869MB (1953525168 512 byte sectors: 255H 63S/T 121601C)
da0: quirks=0x2<NO_6_BYTE>
fdisk da0
******* Working on device /dev/da0 *******
parameters extracted from in-core disklabel are:
cylinders=121601 heads=255 sectors/track=63 (16065 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=121601 heads=255 sectors/track=63 (16065 blks/cyl)
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 131 (0x83),(Linux native)
start 8, size 2,104,504 (1,027 Meg), flag 0
beg: cyl 0/ head 0/ sector 9;
end: cyl 130/ head 254/ sector 60
The data for partition 2 is:
sysid 131 (0x83),(Linux native)
start 2104512, size 1,930,434,656 (942,595 Meg), flag 0
beg: cyl 130/ head 254/ sector 61;
end: cyl 486/ head 254/ sector 56
The data for partition 3 is:
sysid 131 (0x83),(Linux native)
start 1932539168, size 20,980,896 (10,244 Meg), flag 0
beg: cyl 486/ head 254/ sector 57;
end: cyl 768/ head 254/ sector 62
The data for partition 4 is:
<UNUSED>
Current:
/usr/sbin/fstyp /dev/da0s1
/usr/sbin/fstyp /dev/da0s2
/usr/sbin/fstyp /dev/da0s3
9.3-RELEASE:
/usr/local/sbin/fsck_ext2fs /dev/da0s1
e2fsck 1.42.6 (21-Sep-2012)
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix<y> yes
Inode 7301 was part of the orphaned inode list. FIXED.
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found. Create<y> yes
Pass 4: Checking reference counts
Pass 5: Checking group summary information
hmx_int_stor: ***** FILE SYSTEM WAS MODIFIED *****
hmx_int_stor: 20/65808 files (0.0% non-contiguous), 15737/263063 blocks
mount_ext2fs /dev/da0s1 s1
/usr/local/sbin/fsck_ext2fs /dev/da0s2
(Or on Current mount -t ext2fs /dev/da0s1 s1 )
e2fsck 1.42.6 (21-Sep-2012)
hmx_int_stor: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Inodes that were part of a corrupted orphan linked list found. Fix<y> yes
Inode 458753 was part of the orphaned inode list. FIXED.
... more fixed ...
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found. Create<y> yes
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (64736828, counted=64736811).
Fix<y> yes
Free inodes count wrong (60332978, counted=60332977).
Fix<y> yes
hmx_int_stor: ***** FILE SYSTEM WAS MODIFIED *****
hmx_int_stor: 1103/60334080 files (39.8% non-contiguous), 176567521/241304332 blocks
mount_ext2fs /dev/da0s2 s2
/usr/local/sbin/fsck_ext2fs /dev/da0s3
e2fsck 1.42.6 (21-Sep-2012)
hmx_int_stor: recovering journal
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
/lost+found not found. Create<y> yes
Pass 4: Checking reference counts
Pass 5: Checking group summary information
hmx_int_stor: ***** FILE SYSTEM WAS MODIFIED *****
hmx_int_stor: 13/655776 files (0.0% non-contiguous), 80306/2622612 blocks
mount_ext2fs /dev/da0s3 s3
du -k
690,933,200 .
du -m
674740 .
/bin/df
Filesystem 1K-blocks Used Avail Capacity Mounted on
/dev/da0s1 1034408 45104 936692 5% /s4/data/humax/s1
/dev/da0s2 949996988 691049744 210686380 77% /s4/data/humax/s2
/dev/da0s3 10302744 133520 9644704 1% /s4/data/humax/s3
A sample: cd 's2/My Video' ; file TVclip_20170823_0038*
TVclip_20170823_0038.hjm: ASCII text, with very long lines,
with no line terminators
TVclip_20170823_0038.hts: data
TVclip_20170823_0038.nts: DitPack archive data
-rw-r--r-- 1 root wheel 4039 Aug 23 02:37 TVclip_20170823_0038.hjm
-rw-r--r-- 1 root wheel 1792462848 Aug 23 02:37 TVclip_20170823_0038.hts
-rw-r--r-- 1 root wheel 2813120 Aug 23 02:37 TVclip_20170823_0038.nts
All failed:
mplayer TVclip_20170823_0038.hts
MPlayer SVN-r36558-snapshot-3.4.1 (C) 2000-2013 MPlayer Team
Playing TVclip_20170823_0038.hts.
libavformat version 55.22.100 (internal)
TS file format detected.
NO VIDEO! NO AUDIO! (try increasing -tsprobe) NO SUBS (yet)!
No stream found.
Exiting... (End of file)
xine TVclip_20170823_0038.hts
vlc TVclip_20170823_0038.hts
A hardware streamer failed too sumvision
https://forum.videohelp.com/threads/366091-hts-format-used-by-Humax
"It's an encrypted proprietary format for HD recordings"
Probably the key is somewhere on one of those 3 partitions (or buried in a hard to access sector);
Non video recordings are just these few files:
-rw-r--r-- 1 root wheel 7129111 Sep 23 17:10 ./s1/dvbepg/epg.dat
-rw-r--r-- 1 root wheel 3770291 Sep 23 17:10 ./s1/dvbepg/epg_scex.dat
-rw-r--r-- 1 root wheel 1631082 Sep 14 14:09 ./s1/fsatcontentsxml_def/rec_update/recdata.zip
-rw-r--r-- 1 root wheel 921 Sep 14 14:09 ./s1/fsatcontentsxml_def/ver.xml
-rw-r--r-- 1 root wheel 2633 Sep 6 06:08 ./s1/.umount-proc-info
-rw-r--r-- 1 root wheel 2440 Jun 21 2014 ./s2/.umount-proc-info
-rw-r--r-- 1 root wheel 2350314 Apr 16 2014 ./s3/download
I wonder If the key is unique per box or common to all humax freesat
Seems NOT: https://wiki.hummy.tv/wiki/Encryption
If common to all I could copy data to usb media,
to play on another Humax ?
https://wiki.hummy.tv/wiki/FTP_Hi-Def_Content_Using_FOXY
It is possible to use a binary/Hex. editor to edit the HMT file manually,
the Byte at location 0x3DC needs to be changed to 0x04
Perl prog to do location 0x3DC Unix
https://myhumax.org/forum/topic/hb-1000s-will-not-turn-on
|
-
SUMVISION
CYCLONE MICRO2+ (name on metal box)
- Fast boot, good fast forward & rewind on
.ts
-
Manufacturer
-
Retailer: UK/ Maplins:
-
Remote controller battery:
- Not documented in manual or on back of
controller, but I think it needs a
3.5 mm thick CR2032
(225 mAh capacity), not a 2.5mm thick CR2025
(160-165 mAh capacity)
- Twice I've inserted battery carrier wrong way,
with battery it then jams, & I needed to crack
open the plastic halves with a flat screwdriver, so
take care: If keys of controller are upward: The
ridge of the carrier needs to be downward, with
wider part of battery (positive) with all the
writing downward, & the plain smaller
(negative) side upward, so battery is falling out
of carrier as it's inserted (hold in with a
finger).
-
The controllers are
immensely pickey about cells (batteries) !
- p@ noticed this first with his, but he
didn't have a DVM (digital voltmeter) to
measure with.
- j@ then confirmed it.
-
button cells can be fakes (I suppose cheap
cells from eg 1 pound / 1 Euro type shops might
be particularly risky.
-
The controller can take 1 of 2 cells of same
diameter but differing
height
| Battery |
Capacity |
Thickness |
| CR2025 |
160-165 mAh |
2.5 mm |
|
CR2032 |
225 mAh |
3.5 mm |
Manual doesn't say which battery to use, nor
does remote, but there's room for a
CR2032, & I suspect a CR2025 may not
be thick enough to make reliable contact.
- A j@ 3.06 V CR2025 did not work.
- One/ some of p@'s other CR2032
also didnt work, I didn't get time to measure
p@ voltages,
- A j@ sealed Philips CR2032,
previously in store maybe years measured 3.28
V. Manufacturer pack says Philips, but not on
cell. Voltage 3.27 V Thickness 3.04 mm. It did
not work.
- j@ remote controller & streamer work
with a new CR2032,
Manufacturer package says Diall, (cell does not
bear that name), that was bought July 2015
B&Q, TW, UK, 3.31 Volts. Thickness 3.22
mm,
- j@ remote controller with 2 identical cells
from same blister pack bought from 1 euro shop
maybe 6 months back: The cell with 3.10 Volts
worked. The cell with 3.15 volts failed to
work. Not the order one would expect for
supposedly identical cells !
- Maybe some batteries may have the voltage
but not deliver enough current, might be
because inside they are less substantial
fakes.
- I cant usefully weigh the batteries, as my
digital scales only work in multiples of grams.
(I'm thinking of making a lever to add to
scales to make them more sensitive, that or
find & buy more sensitive scales).
- If anyone has more clues, please mail me
- Seems my remote is faulty. I discovered I can
control the streamer by app
Sure on Android
-
Dreambox 800. Runs Linux
- Vu+
does not encrypt to disk :-)
- See Also: Mythtv
Humax
- HTS: Generates triplets of
2017-08-23 Sample: { TVclip_.hjm (4k) TVclip_.hts (1.8G)
TVclip_.nts (2M) } Or older sample: { .ts .nts & .hmt
}.
- Fails to play a .ts file (from Dreambox) - Maybe it needs the full triplet
of files ?
Dreambox
- Generates .ts with several (more than 2) apart from the
.ts
FPS - Frames Per Second
I guess most of the discs in Europe are 25 FPS because PAL TVs
started as 50 FPS, but interlaced, ie 25 real new frames per
sec. I guess the 15 FPS images I tested came from USA, that
has 60 FPS NTSC, presumably also interleaved, & divided
by a further 2 beyond to save space ? Corrections
Digital & Satellite TV Links
Info for a new page later: TV Remotes, Programmable: Many have
same code numbers, read here in German: https://www.fernbedienung-universal.de/
|
|
