Hi!
There seems to be a problem with PIP recording and plugins. Here's what I tried, and what also works:
dreamstart /chname='VT4' /renderless=on
dreamstart /startpiprec_chname='VT4'
However, this doesn't work:
dreamstart /chname='VT4' /renderless=on
dreamstart /startpiprec_chname='KANAALTWEE'
I'm using Acamd to decode the TV Vlaanderen channels with my smartcard. In the first set of commands I can see that Acamd gets the channelchange and starts decoding the channel:
19:53:13: Ch: 953 - VT4
19:53:13: Incomming PackageSize [184]
19:53:15: 0x03B9 0x31E5 0x0100 0x0000006C 0x03CD 0x00B6 11010010
In the second set of commands Acamd initializes fine, but never seems to get the channel change.
I did notice that Acamd starts to decode the channel even when I only use:
dreamstart /chname='VT4' /renderless=on
So a PIP recording of this same channel works since it's already being tuned to and decoded. A pip recording of another channel fails since the pip01, pip02,... plugins never get notified of a channel change!
Does this make any sense?
Thanks for looking at this problem!
Problem with dreamstart and recording
Moderators: Dreamer, FredB, X05
-
- Just popping in
- Posts: 8
- Joined: Fri Mar 30, 2007 7:20 am
I also see this bug
Hi,
I can confirm I also see this bug. It also happens if you use it directly (w/o command line)
Here is another way of reproducing it:
1) run dvbdream
2) tune to a scrambled channel, for example VT4
3) right-click "Record On"
-> recording of the channel starts OK
4) right-click PIP, and select another scrambled PIP on the same TP, for example VTM
-> the PIP window opens, but there is no video. The newcamd server does not see a login for the 2nd (PIP) client !!!
5) right-click "Record On" in the PIP window
-> a file is created but as expected, it does not play.
Now: close dvbdream, and do the following sequence:
(be sure to exit dvbdream after the previous test)
1) run dvbdream
2) tune to a scrambled channel, for example VT4
3) right-click PIP, and select another scrambled PIP on the same TP, for example VTM
-> now you do see video in the PIP
4) right-click "Record On" in the main window
-> recording of the channel starts OK
5) right-click "Record On" in the PIP window
-> recording of the 2nd channel runs OK and simulatenously
So: once a recording of a scrambled channel is going on, additional PIP that use an MD plugins don't work anymore...
This problem does not happen if the PIP channels are FTA.
Note I also saw such a problem in v1.04h; the version I tested before that (don't recall which one that was) did not have this problem.
Hope this is clear, please let me know if I can provide more info.
Thanks,
Johan.
I can confirm I also see this bug. It also happens if you use it directly (w/o command line)
Here is another way of reproducing it:
1) run dvbdream
2) tune to a scrambled channel, for example VT4
3) right-click "Record On"
-> recording of the channel starts OK
4) right-click PIP, and select another scrambled PIP on the same TP, for example VTM
-> the PIP window opens, but there is no video. The newcamd server does not see a login for the 2nd (PIP) client !!!
5) right-click "Record On" in the PIP window
-> a file is created but as expected, it does not play.
Now: close dvbdream, and do the following sequence:
(be sure to exit dvbdream after the previous test)
1) run dvbdream
2) tune to a scrambled channel, for example VT4
3) right-click PIP, and select another scrambled PIP on the same TP, for example VTM
-> now you do see video in the PIP
4) right-click "Record On" in the main window
-> recording of the channel starts OK
5) right-click "Record On" in the PIP window
-> recording of the 2nd channel runs OK and simulatenously
So: once a recording of a scrambled channel is going on, additional PIP that use an MD plugins don't work anymore...
This problem does not happen if the PIP channels are FTA.
Note I also saw such a problem in v1.04h; the version I tested before that (don't recall which one that was) did not have this problem.
Hope this is clear, please let me know if I can provide more info.
Thanks,
Johan.
-
- Just popping in
- Posts: 8
- Joined: Fri Mar 30, 2007 7:20 am
here are some logs from my system
Hi,
I have done some tests to reproduce and document this issue.
FYI: my plugins are CSC 4.0.0.2, connecting to a newcamd server with a phoenix card reader.
1) LOG1 :
* I manually start DD, tune to VTM, then select PIP -> VT4
=> both (scrambled) main channel and PIP show correct video
2) LOG2 :
* I manually start DD, tune to VTM, then start recording, then select PIP -> VT4
=> VTM shows fine, there is no video in the PIP !
=> I can also see that there was no login for the PIP on the newcamd server
3) LOG3 :
* similar, but from the command line:
dreamstart.exe /renderless=on /chname=VTM
dvbdream.exe /startpiprec_chname=VT4
dvbdream.exe /startpiprec_chname=VTM
=> both channels record fine.
4) LOG4 :
* again from the command line:
dreamstart.exe /renderless=on /chname=VTM
dvbdream.exe /startpiprec_chname=VTM
dvbdream.exe /startpiprec_chname=VT4
=> VTM records fine, VT4 is a scrambled recording and cannot be played back!
(the difference between log 3 and 4 is the order in which the recording was started. After recording of VTM (=main video) is started, PIP recording no longer works)
I hope these logfiles help you debug this. I am building a PVR system based on DD but this is really a showstopper.
Other than this issue, DD has proven to be very reliable to work with.
Of all software that I have tested, it really is the best I have seen.
Thanks!
I have done some tests to reproduce and document this issue.
FYI: my plugins are CSC 4.0.0.2, connecting to a newcamd server with a phoenix card reader.
1) LOG1 :
* I manually start DD, tune to VTM, then select PIP -> VT4
=> both (scrambled) main channel and PIP show correct video
2) LOG2 :
* I manually start DD, tune to VTM, then start recording, then select PIP -> VT4
=> VTM shows fine, there is no video in the PIP !
=> I can also see that there was no login for the PIP on the newcamd server
3) LOG3 :
* similar, but from the command line:
dreamstart.exe /renderless=on /chname=VTM
dvbdream.exe /startpiprec_chname=VT4
dvbdream.exe /startpiprec_chname=VTM
=> both channels record fine.
4) LOG4 :
* again from the command line:
dreamstart.exe /renderless=on /chname=VTM
dvbdream.exe /startpiprec_chname=VTM
dvbdream.exe /startpiprec_chname=VT4
=> VTM records fine, VT4 is a scrambled recording and cannot be played back!
(the difference between log 3 and 4 is the order in which the recording was started. After recording of VTM (=main video) is started, PIP recording no longer works)
I hope these logfiles help you debug this. I am building a PVR system based on DD but this is really a showstopper.
Other than this issue, DD has proven to be very reliable to work with.
Of all software that I have tested, it really is the best I have seen.
Thanks!
- Attachments
-
- dvbdream_4.log.txt
- LOG4
- (12.05 KiB) Downloaded 317 times
-
- dvbdream_3.log.txt
- LOG3
- (13.16 KiB) Downloaded 327 times
-
- dvbdream_2.log.txt
- LOG2
- (15.31 KiB) Downloaded 325 times
-
- dvbdream_1.log.txt
- LOG1
- (16.33 KiB) Downloaded 318 times
-
- Just popping in
- Posts: 8
- Joined: Fri Mar 30, 2007 7:20 am
comparing log1 and log2:
Log 1:
log2 :
Does this help/make sense ?
Thanks!
Log 1:
[4/03/2008 16:51:16 : 25468] >>>>: ShowPip(chid:3146)
[4/03/2008 16:51:16 : 25468] pips[1].tempMDAPIwindow handle:00040402
[4/03/2008 16:51:16 : 25468] [MDAPI] Loading : cs1.dll
[4/03/2008 16:51:16 : 25468] [MDAPI] Loaded OK. cs1.dll is an MD v9.0 (API 3.00) plugin
[4/03/2008 16:51:16 : 25484] [MDAPI]Event (DD=>Plugin) ChangeChannel(chid:3146)
[4/03/2008 16:51:16 : 25484] >>>>: [MDAPI] GetCurrentChannelMD9Info()
[4/03/2008 16:51:16 : 25484] <<<<: [MDAPI] GetCurrentChannelMD9Info()
[4/03/2008 16:51:16 : 25484] [DS_MNG]:VideoCodec/GUID:Gabest Mpeg2dec/{39F498AF-1A09-4275-B193-673B0BA3D478}
[4/03/2008 16:51:16 : 25500] [DS_MNG]:AudioCodec/GUID:Gabest MPEG/AC3/{3D446B6F-71DE-4437-BE15-8CE47174340F}
[4/03/2008 16:51:16 : 25531] DS:OK
[4/03/2008 16:51:16 : 25531] pips[1].ds.StartGraph;
[4/03/2008 16:51:16 : 25531] >>>>: TDS.StartGraph()
[4/03/2008 16:51:16 : 25546] <<<<: TDS.StartGraph()
[4/03/2008 16:51:16 : 25546] <<<<: ShowPip(chid:3146)
[4/03/2008 16:51:16 : 25546] >>>>: [MDAPI] Command (Plugin=>DD) MDAPI_START_FILTER
[4/03/2008 16:51:16 : 25546] <<<<: [MDAPI] Command (Plugin=>DD) MDAPI_START_FILTER result:1
[4/03/2008 16:51:16 : 25546] >>>>: [MDAPI] Command (Plugin=>DD) MDAPI_START_FILTER
[4/03/2008 16:51:16 : 25546] <<<<: [MDAPI] Command (Plugin=>DD) MDAPI_START_FILTER result:1
[4/03/2008 16:51:16 : 25546] >>>>: [MDAPI] Command (Plugin=>DD) MDAPI_START_FILTER
[4/03/2008 16:51:16 : 25546] <<<<: [MDAPI] Command (Plugin=>DD) MDAPI_START_FILTER result:1
[4/03/2008 16:51:16 : 25562] >>>>: [MDAPI] Command (Plugin=>DD) MDAPI_STOP_FILTER
[4/03/2008 16:51:16 : 25562] <<<<: [MDAPI] Command (Plugin=>DD) MDAPI_STOP_FILTER result:1
[4/03/2008 16:51:17 : 26437] >>>>: [MDAPI] Command (Plugin=>DD) MDAPI_STOP_FILTER
[4/03/2008 16:51:17 : 26437] <<<<: [MDAPI] Command (Plugin=>DD) MDAPI_STOP_FILTER result:1
[4/03/2008 16:51:17 : 26437] >>>>: [MDAPI] Command (Plugin=>DD) MDAPI_START_FILTER
[4/03/2008 16:51:17 : 26437] <<<<: [MDAPI] Command (Plugin=>DD) MDAPI_START_FILTER result:1
[4/03/2008 16:51:25 : 34359] Signal Level: 57% Continuity Errors: 2 Received TS: 431617
[4/03/2008 16:51:34 : 42781] >>>>: HidePip(chid:0)
log2 :
-> it appears like log 1 calls a procedure "ShowPip(chid:3146)" where log2 calls "StartMultipleRec(chid:4320)". The "ShowPip" clearly does "[MDAPI] Command"s after loading cs1.dll, but "StartMultipleRec" does not do that.[4/03/2008 16:53:00 : 22782] StartMultipleRec(chid:4320)
[4/03/2008 16:53:00 : 22797] Rec Handle:0
[4/03/2008 16:53:08 : 31328] >>>>: ShowPip(chid:3146)
[4/03/2008 16:53:08 : 31344] pips[1].tempMDAPIwindow handle:00060404
[4/03/2008 16:53:08 : 31344] [MDAPI] Loading : cs1.dll
[4/03/2008 16:53:08 : 31344] [MDAPI] Loaded OK. cs1.dll is an MD v9.0 (API 3.00) plugin
[4/03/2008 16:53:08 : 31344] [MDAPI]Event (DD=>Plugin) ChangeChannel(chid:3146)
[4/03/2008 16:53:08 : 31344] >>>>: [MDAPI] GetCurrentChannelMD9Info()
[4/03/2008 16:53:08 : 31344] <<<<: [MDAPI] GetCurrentChannelMD9Info()
[4/03/2008 16:53:09 : 31360] [DS_MNG]:VideoCodec/GUID:Gabest Mpeg2dec/{39F498AF-1A09-4275-B193-673B0BA3D478}
[4/03/2008 16:53:09 : 31360] [DS_MNG]:AudioCodec/GUID:Gabest MPEG/AC3/{3D446B6F-71DE-4437-BE15-8CE47174340F}
[4/03/2008 16:53:09 : 31407] DS:OK
[4/03/2008 16:53:09 : 31407] pips[1].ds.StartGraph;
[4/03/2008 16:53:09 : 31407] >>>>: TDS.StartGraph()
[4/03/2008 16:53:09 : 31407] <<<<: TDS.StartGraph()
[4/03/2008 16:53:09 : 31422] <<<<: ShowPip(chid:3146)
[4/03/2008 16:53:12 : 35078] Signal Level: 58% Continuity Errors: 0 Received TS: 485889
[4/03/2008 16:53:26 : 49188] Signal Level: 58% Continuity Errors: 0 Received TS: 802817
[4/03/2008 16:53:40 : 63297] Signal Level: 58% Continuity Errors: 0 Received TS: 1119745
[4/03/2008 16:53:45 : 67375] >>>>: HidePip(chid:0)
Does this help/make sense ?
Thanks!
For The Record released!
Bad news: nobody ever took any notice of the bug reported in this thread
Good news: we found a reasonable workaround to support DVB Dream so I am proud to announce For The Record has been released!
Discover everything there is to know about this advanced rule-based TV scheduling and recording solution at http://www.4therecord.eu .
Good news: we found a reasonable workaround to support DVB Dream so I am proud to announce For The Record has been released!
Discover everything there is to know about this advanced rule-based TV scheduling and recording solution at http://www.4therecord.eu .
Technotrend S2-3200
FloppyDTV2
FloppyDTV2
Who is online
Users browsing this forum: No registered users and 1 guest