-
The forum software that supports hummy.tv has been upgraded to XenForo 2.3!
Please bear with us as we continue to tweak things, and feel free to post any questions, issues or suggestions in the upgrade thread.
[webif] Web Interface 1.2.x
- Thread starter af123
- Start date
Ezra Pound
Well-Known Member
For the Sutton Coldfield region (W.M. Network), all MUXs have a corresponding MUX ID, after a re-scan to remove BBC THREE / BBC THREE HD
Black Hole
May contain traces of nut
Is there an easy way for the software to tell the difference between an audio-extracted peudo-mp3 and an ffmpeg-converted real mp3? It would be nice to have a flag icon in the WebIF media browser to indicate which is which.
MymsMan
Ad detector
I'm confused - audio extraction is by ffmpeg
Black Hole
May contain traces of nut
It's not all that confusing - the difference is whether the audio extraction is set for fast (just the MP2 audio stream sent as-is into a .MP3 file, but it isn't really MP3) or slow (properly transcoded to real MP3). The setting is on the Settings page of the WebIF.
Ezra Pound
Well-Known Member
Yes, ffmpeg will shows this (on the last line) "Audio: mp2 /Audio: mp3 ":-
Code:
humax# ffmpeg -i my.mp3
ffmpeg version 0.10 Copyright (c) 2000-2012 the FFmpeg developers
built on Feb 29 2012 10:25:07 with gcc 4.2.0 20070124 (prerelease) - BRCM 11ts-20090508
configuration: --cross-prefix=mipsel-linux- --enable-cross-compile --arch=mipsel --target-os=linux --enable-gpl --enable-libmp3lame --disable-static --enable-shared --disable-asm --prefix=/mod --extra-cflags=-fPIC
libavutil 51. 34.101 / 51. 34.101
libavcodec 53. 60.100 / 53. 60.100
libavformat 53. 31.100 / 53. 31.100
libavdevice 53. 4.100 / 53. 4.100
libavfilter 2. 60.100 / 2. 60.100
libswscale 2. 1.100 / 2. 1.100
libswresample 0. 6.100 / 0. 6.100
libpostproc 52. 0.100 / 52. 0.100
[mp3 @ 0x42bc00] max_analyze_duration 5000000 reached at 5016000
Input #0, mp3, from 'my.mp3':
Metadata:
title : Pet Squad
album : CBBC Channel
date : 2012
Duration: 00:11:30.50, start: 0.000000, bitrate: 256 kb/s
Stream #0:0: Audio: mp2, 48000 Hz, stereo, s16, 256 kb/s
Code:
humax# ffmpeg -i Track01.mp3
ffmpeg version 0.10 Copyright (c) 2000-2012 the FFmpeg developers
built on Feb 29 2012 10:25:07 with gcc 4.2.0 20070124 (prerelease) - BRCM 11ts-20090508
configuration: --cross-prefix=mipsel-linux- --enable-cross-compile --arch=mipsel --target-os=linux --enable-gpl --enable-libmp3lame --disable-static --enable-shared --disable-asm --prefix=/mod --extra-cflags=-fPIC
libavutil 51. 34.101 / 51. 34.101
libavcodec 53. 60.100 / 53. 60.100
libavformat 53. 31.100 / 53. 31.100
libavdevice 53. 4.100 / 53. 4.100
libavfilter 2. 60.100 / 2. 60.100
libswscale 2. 1.100 / 2. 1.100
libswresample 0. 6.100 / 0. 6.100
libpostproc 52. 0.100 / 52. 0.100
[mp3 @ 0x42bc00] max_analyze_duration 5000000 reached at 5015510
[mp3 @ 0x42bc00] Estimating duration from bitrate, this may be inaccurate
Input #0, mp3, from 'Track01.mp3':
Metadata:
title : Everyone's At It
artist : Lily Allen
album : It's Not Me, It's You
track : 01/12
TLEN : 258706
creation_time : 2010-11-13T11:18
encoded_by : Exact Audio Copy (Burst mode)
encoder : lame.exe -p -h -b 128
Duration: 00:04:19.03, start: 0.000000, bitrate: 128 kb/s
Stream #0:0: Audio: mp3, 44100 Hz, stereo, s16, 128 kb/s
prpr
Well-Known Member
Fix for the EPG page showing row 00:00 after row 23:00 which is MEGA-confusing:
Hmm, it screws up the final column, for reasons I haven't looked into, but it's certainly less confusing...
And who knows what would happen at DST changes. Maybe this is the wrong fix, but a fix is certainly needed it seems.
Code:
humax /mnt/hd2/mod/webif/html/epg # diff -u service.jim~ service.jim
--- service.jim~
+++ service.jim
@@ -21,7 +21,7 @@
set service [cgi_get service 4170]
set records [epg dbfetch dump \
-service $service \
- -sort "strftime('%%H%%J', start, 'unixepoch'), strftime('%%M', start, 'unixepoch')" \
+ -sort "strftime('%%H%%J', start, 'unixepoch', 'localtime'), strftime('%%M', start, 'unixepoch')" \
-debug 0
]Hmm, it screws up the final column, for reasons I haven't looked into, but it's certainly less confusing...
And who knows what would happen at DST changes. Maybe this is the wrong fix, but a fix is certainly needed it seems.
Last edited:
Ezra Pound
Well-Known Member
While playing around with the RS improved conflict detection, I noticed that the Web-If schedule screen was not highlighting (in pink) a conflict in the same manor as it does on the RS schedule screen, as I missing something?
Black Hole
May contain traces of nut
Have the RS improvements been ported to the WebIF yet? If not, there's your answer.
OP
No, and in fact webif has never done any conflict detection. I recently added basic alerting to the EPG popups but that's all.
Ezra Pound
Well-Known Member
I thought the Web-If did this in the past, I must be mistaken
Ezra Pound
Well-Known Member
Ah, possibly, I did capture this for the WiKi :-
http://wiki.hummy.tv/wiki/Diary-recorded-2B.png
http://wiki.hummy.tv/wiki/Diary-recorded-2B.png
prpr
Well-Known Member
Auto-unprotect has stopped working.
There is nothing recent in the activity.log file.
The recmon.log file contains this:
There are two lock files in /var/lock :
-rw-rw-rw- 1 root root 0 Apr 24 20:04 .webiflock_dlnahelper
-rw-rw-rw- 1 root root 0 Apr 25 18:05 .webiflock_webif_auto
I would guess deleting these will fix it, but how do we work out why it happened?
There is nothing recent in the activity.log file.
The recmon.log file contains this:
Code:
143 /mod/etc/recmon.d/autotrigger:27: Error: /mod/webif/lib/bin/auto:816: Error: Lock not held.
144 at file "/mod/webif/lib/bin/auto", line 816
145 at file "/mod/etc/recmon.d/autotrigger", line 27
146 /mod/etc/recmon.d/autotrigger:27: Error: /mod/webif/lib/bin/auto:816: Error: Lock not held.
147 at file "/mod/webif/lib/bin/auto", line 816
148 at file "/mod/etc/recmon.d/autotrigger", line 27
149 Cannot acquire exclusive lock, terminating.-rw-rw-rw- 1 root root 0 Apr 24 20:04 .webiflock_dlnahelper
-rw-rw-rw- 1 root root 0 Apr 25 18:05 .webiflock_webif_auto
I would guess deleting these will fix it, but how do we work out why it happened?
MymsMan
Ad detector
The lock files are not deleted when the lock is released (they are removed by a reboot)
You could use lsof to find which process, if any, has the file inuse - ie is holding the lock
prpr
Well-Known Member
Nothing.
OP
Ah.. that's to do with the new locking mechanism.. autotrigger passes the 'auto' lock to the auto script. That would have worked before but not now as they are different processes. That means that the locking will not be working properly although I can't see how it would lead to things stopping working altogether.
MymsMan
Ad detector
The problem of recmon occasionally terminating for no obvious reason with no visible diagnostics pre-dates the changes to the logging.
I don't think failure of any of the spawned tasks causes recmon itself to fail (I have created enough failures in the past!)
I have turned on recmon debugging level 1 in the hope that I might see some clue
I don't think failure of any of the spawned tasks causes recmon itself to fail (I have created enough failures in the past!)
I have turned on recmon debugging level 1 in the hope that I might see some clue