New Plugin: DboxRecorder Plugin

[Rayman]

ggrab from the command line works fine ( well had some trouble depending on channels selction - but thats a ggrab / parameter issue I think - ive seen the same issue with vlc streaming too.)

so confirmed - it works -
happy to assist -
able to do testing for you if required -

Regards
Rayman

[alibert]

Hi,

happy to assist -
able to do testing for you if required -

Thanks for your help. I've attached a version with basic enigma support. Please try it out and tell me how it's working.

I have also flashed an enigma image, but i will switch back to neutrino soon. By the way, are there still images available where you can choose the gui at boot-time?

-alibert

[Rayman]

alibert -
i like look of features to come - in particular the directshow filter useage -
as pumping the data straight to the xcard is attractrive to me.

I ran it on my box at work and an early thing to note -
if there is no dreambox / ip that is reachable around and the interface is set to enigma - it just locks up - doesnt look like the catchall timeout is active in that case.

When I get home tonight I'll give it a whirl on the real situation with the dreambox and post an update.

Excellent on the quick turn around by the way.

Regards
Rayman

[Rayman]

some success and some failures.

was able to connect and fetch channels -
large channel numbers but just seems the top byte indicates something. - eg
310000bc0 = TVSN.

now when I try to change to a channel it fails -
see attached logs.

Upon investigating with the normal web interface + ethereal and the plugin I found
plugin log =
"TO DBOX: http://192.168.0.103/cgi-bin/zapTo?path=...00:0:0:0:0"

but from the web interface - packet is
"http://192.168.0.103/cgi-bin/zapTo?path=1:0:1:bc0:3:1000:6180000:0:0:0"

manual entry confirms the 6180000 doesnt appear to be significant at this point and is the same for all channels.

HOWEVER the leading 0 on the 0bc0 is causing the problem - with the 0 no go , without it the channel is changes (manually testing).

Im usung a pi2 image - not sure which one you used - hydra or original ?
http://www.users.on.net/~rdekens/dboxRecorderLog.zip

Regards
Rayman

[alibert]

Hi,

was able to connect and fetch channels -
large channel numbers but just seems the top byte indicates something. - eg
310000bc0 = TVSN.

For internal compatibility reasons, the channel ids shown in the config app are formatted by the plugin like they would be used in neutrino. When communicating with ehttp (the enigma http interface), they are split again into three parts: service-id, transponder-id and onid.

manual entry confirms the 6180000 doesnt appear to be significant at this point and is the same for all channels.

I'm also not sure about this one, from the docs it should be the 'namespace', but i also came to the conclusion that it's not really needed to change channels.

HOWEVER the leading 0 on the 0bc0 is causing the problem - with the 0 no go , without it the channel is changes (manually testing).

I've attached a new version that will remove leading zeros from the path.

Im usung a pi2 image - not sure which one you used - hydra or original ?

Sorry, to be honest I've never heard of images named 'pi2' or hydra'. I used the latest release from http://www.jackthegrabber.de, and here it has worked so far.

-alibert

[Rayman]

damn
It appears i was wrong on the 6180000. looks like it needs to be there -
I'm not sure if you just removed leading 0s - what happens for a number below 100h
- i think it actually needs to be left 0 padded but only to a maximum of 3 digits.
This is based based upon my experience with videolan and the values used for the vpids and apids on the command
line with that program.


Please see the PM I sent.

Regards
Rayman

[Rayman]

Alibert -
just an update - didnt get much time on the wekend really -
but - changed to include the 6180000 and extended the timeout on pids retrieval (takes a fair bit longer for the pids to become valid if the keys are not local to the dreambox being referenced).

So I have success in regard to channel changing and recording -
I'm currently looking into the issue as to why I cant watch live - get a frame
and it freezes - but carries on recording ok.

This may be codec / directshow graph issue and I dont think has to do with the plugin.

Regards
Rayman

[alibert]

Hi,

I've just uploaded a development release of the plugin. Some of the changes:

• Support for 'FM' Radio. You can add radio stations from your dbox to GBPVR, they'll be available through the built-in FM Radio module of GBPVR.
  
• Timer events thread only started from within the GBPVR recording service process - there was a bug that started the thread also when called from GBPVR.exe in earlier versions.
  
• Configurable timeouts for different setups. Those timeouts are applied especially when waiting for valid pids after a channel change, and also in various other situations.
  
• Special option 'debug mode' which will add valuable log messages if you should have problems.
  
• Rewritten the configuration part of the plugin. Settings are now saved in binary format. However, I've included an automatic update from the old config files.
  

Some features are still disabled, including Enigma-support. But I think that it will be working soon - thanks rayman for your help.

You can download it directly from here.

-alibert

[RattyDAVE]

I am using the 4/12 dbox plug in and am having problems.

I can configure correctly - get all the channels downloaded.
It changes channels.
And get stuck at the Starting timeshift Mode TV Please Wait

Enclosed is my Log.

DAVE

[alibert]

Hi,

from your attached logfile it seems that the http request

Code:

http://192.168.1.114/control/zapto?getpids

is never answered by the dbox.

Can you enter this line into a browser and look if there is any reply?

-alibert