[Venton Unibox HDx] button mapping

[antwan]

Hello peeps

on the remote for the venton hdeco there is a timer button which when pressed starts time shift is it possible to change this to as the button suggests to timer over view.
I have tried to reallocate it using user interface >>> button setup this results in both functions operating ie timer overview and time shift. which is really annoying. Any thoughts greatly appreciated.

 

[Trial]

Hi,
you have to delete timeshift option it seems you only added a function in button setup. I have no Venton to check.

ciao

 

[antwan]

thanks for info Ciao can you tell me how to delete options please

 

[abu baniaz]

A second selection of the feature in Button Setup should result in removal.

 

[Larry-G]

thanks for info Ciao can you tell me how to delete options please

Ciao is not his name, it is a Italian greeting meaning both hello or goodbye depending on the context, his forum name is Trial.

Not being picky just for future reference.

 

[antwan]

Ok Thanks for info .. not converse with Italian greetings it looked like a name
... Ciao

Ciao is not his name, it is a Italian greeting meaning both hello or goodbye depending on the context, his forum name is Trial.

Not being picky just for future reference.

 

[antwan]

Thanks Abu, I appreciate what you are saying re second selection.
I have not added any functions in button set up its just that the button says timer on the remote, but when selected it starts Timeshift recording.

I tried to use button set up to correct it but only resulted in 2 functions under same Timer button.

When I select the timer button I would expect seeing timer overview and not timeshift.

 

[abu baniaz]

This would mean the button has been mapped wrong. Any chance of you adding uploading debug log of you pressing the timer button.

 

[antwan]

Abu .. just enabled debug log and sent to vix after using the timer button, is this the part of the log that's req'd .. just pasted from log

KEY: 174 EXIT
action -> InfobarShowHideActions hide
KEY: 174 EXIT
KEY: 174 EXIT
action -> InfobarShowHideActions hide
KEY: 174 EXIT
KEY: 128 STOP
action -> InfobarTimeshiftActions timeshiftStop
unknown action InfobarTimeshiftActions/timeshiftStop! typo in keymap?
action -> InfobarTimeshiftActions timeshiftStop
< 148.443561> [eDVBServicePlay] timeshift
< 148.447953> [eDVBServicePlay] timeshift
< 148.450971> [eDVBServicePlay] timeshift
[SKIN] processing screen MessageBoxSimple:
[SKIN] processing screen MessageBoxSimple_summary:
KEY: 128 STOP
KEY: 128 STOP
KEY: 108 DOWN
action -> DirectionActions down
KEY: 108 DOWN
KEY: 108 DOWN
action -> DirectionActions down
KEY: 108 DOWN
KEY: 352 OK
action -> MsgBoxActions ok
KEY: 352 OK
< 151.501998> [eThread] old thread joined 0
< 151.506492> [eDVBServicePlay] timeshift
< 151.509690> [eDVBServicePlay] SwitchToLive
< 151.510114> [setIoPrio] best-effort level 7 ok
< 151.515375> [eFilePushThread] stopping thread
< 151.515408> [eFilePushThread] STOP
< 151.517109> [eBackgroundFileEraser] deleting '/media/hdd/timeshift/timeshift.mpmH4d.sc.del'
< 151.526932> [eBackgroundFileEraser] deleting '/media/hdd/timeshift/timeshift.mpmH4d.del'
< 151.538400> [eTSMPEGDecoder] decoder state: pause, vpid=ffffffff, apid=ffffffff
< 151.542922> [eDVBVideo0] DEMUX_STOP ok
< 151.549743> [eDVBVideo0] VIDEO_STOP ok
< 151.556267> [eDVBVideo0] destroy
< 151.559383> [eDVBAudio0] AUDIO_STOP ok
< 151.571698> [eDVBAudio0] DEMUX_STOP ok
< 151.576676> [eDVBAudio0] AUDIO_CONTINUE ok
< 151.582470> [eDVBAudio0] destroy
< 151.596125> [eDVBServicePlay] have 1 video stream(s) (044d), and 2 audio stream(s) (044e, 044f), and the pcr pid is 044d, and the text pid is ffffffff
< 151.625948> [eDVBChannel] getDemux cap=01
< 151.640752> [eTSMPEGDecoder] decoder state: play, vpid=044d, apid=044e
< 151.643463> [eDVBPCR0] DMX_SET_PES_FILTER pid=0x044d ok
< 151.648290> [eDVBPCR0] DEMUX_START ok
< 151.653546> [eDVBAudio0] DMX_SET_PES_FILTER pid=0x044e ok
< 151.658391> [eDVBAudio0] DEMUX_START ok
< 151.665693> [eDVBAudio0] AUDIO_SET_BYPASS bypass=1 ok
< 151.670553> [eDVBAudio0] AUDIO_PAUSE ok
< 151.675562> [eDVBAudio0] AUDIO_PLAY ok
< 151.697859> [eDVBVideo] Video Device: /dev/dvb/adapter0/video0
< 151.700594> [eDVBVideo] demux device: /dev/dvb/adapter0/demux0
< 151.703287> [eDVBVideo0] VIDEO_SET_STREAMTYPE 0 - ok
< 151.708318> [eDVBVideo0] DMX_SET_PES_FILTER pid=0x044d ok
< 151.713363> [eDVBVideo0] DEMUX_START ok
< 151.719089> [eDVBVideo0] VIDEO_FREEZE ok
< 151.724259> [eDVBVideo0] VIDEO_PLAY ok
< 151.736072> [eDVBVideo0] VIDEO_SLOWMOTION 0 ok
< 151.741771> [eDVBVideo0] VIDEO_FAST_FORWARD 0 ok
< 151.746708> [eDVBVideo0] VIDEO_CONTINUE ok
< 151.751719> [eDVBAudio0] AUDIO_CONTINUE ok
< 152.055713> [eDVBTeletextParser] Starting!
< 152.058423> [eDVBTeletextParser] disable teletext subtitles page ffffffffffffffff (und)
< 152.061023> [eDVBPESReader] Created. Opening demux
< 152.063507> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 152.066296> [eDVBTeletextParser] created teletext subtitle PES reader!
< 152.069475> [eDVBPESReader] Created. Opening demux
< 152.072204> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
< 152.075182> [eDVBTeletextParser] starting PES reader on pid=ffffffff
< 152.078657> [eDVBServicePlay] timeshift
< 152.083418> [eDVBServicePlay] unpause
< 152.093297> [eDVBServicePlay] timeshift
< 152.096502> [eDVBServicePlay] timeshift
< 152.100751> [eDVBServicePlay] timeshift
< 152.104245> [eDVBServicePlay] timeshift
< 152.109643> [eFilePushThreadRecorder] stopping thread.
< 152.112729> [eDVBRecordFileThread] waiting for aio to complete
< 152.115225> [eDVBRecordFileThread] buffer usage histogram (20 buffers of 188 kB)
< 152.117864> [eDVBRecordFileThread] 0: 7
< 152.120631> [eDVBRecordFileThread] 1: 24
< 152.126168> [eFilePushThreadRecorder] THREAD STOP
< 152.132965> [eDVBServicePlay] remove timeshift files
< 152.136595> [eDVBServicePlay] timeshift
< 152.146799> [eDVBServicePlay] timeshift
KEY: 352 OK
< 152.338269> [eDVBVideo0] VIDEO_GET_EVENT SIZE_CHANGED 720x576 aspect 3
[VideoMode] setting aspect: 16:9
[VideoMode] setting wss: auto
[VideoMode] setting policy: panscan
[VideoMode] setting policy2: letterbox
KEY: 139 MENU
action -> InfobarMenuActions mainMenu
[SKIN] processing screen Menu:
[SKIN] processing screen MenuSummary:
KEY: 139 MENU
KEY: 108 DOWN
KEY: 108 DOWN
KEY: 108 DOWN
KEY: 108 DOWN
KEY: 108 DOWN
KEY: 352 OK
action -> OkCancelActions ok
[SKIN] processing screen Menu:
[SKIN] processing screen MenuSummary:
KEY: 352 OK
KEY: 352 OK
action -> OkCancelActions ok
[SKIN] processing screen Menu:
[SKIN] processing screen MenuSummary:
KEY: 352 OK
KEY: 108 DOWN

 

[abu baniaz]

Pretty sure you log is after timeshift has started. [STRIKE]Please upload with more details as an attachment.[/STRIKE]

EDIT: Just seen your email.

 

[abu baniaz]

Been advised that this is mostt likely a driver issue.

For now, use button setup to configure it. You'll find the Timers/AutoTimers in the "setup" section of Button Setup. Hopefully it should work for you.

 

[antwan]

Thanks abu , yes it does work but it gives me two functions 1 timer overview and 2 timeshift. when selected i firstly see timer overview then after selecting exit, the picture has frozen and timeshift is running. seems very odd.

 

[Trial]

Hi,
that´s why you should delete the entry which is not needed. Go to button setup and press the button you want to remap and now search for the function you do not want and press OK again. I think it is deleted from the list this way.

ciao

 

[antwan]

Hi Trial
I understand what you are saying but I can't delete the default function which is Time shift.
It should be timer overview as indicated by the button on the remote ie Timer.

 

[rossi2000]

press the ch+/- button to go to the right hand side and then click on ok to remove the unwanted option

if it isnt the ch+/- button it'll be the volume button.

 

[antwan]

Thanks rossi2000,
The point I am trying to make is that in button set up I press the button marked Timer on the remote Then I get on screen:- "button setup for :Timeshift" which is wrong it should be " Button setup for :Timer overview" ( I don't have any options on the rhs to delete)
Hoping that better explains my problem

 

[abu baniaz]

You are pressing one button, receiver thinks it is another because of the drivers. The manufacturer needs to adapt drivers. Until then, you will have to workaround the issue.

 

[antwan]

Thanks Abu I thought that would be the issue.
Who initiates the request from the manufacturer and what sort of timescale before fix is in-place.
also may seem a silly question but what is a driver and why only them can do the change.