DVB-Cube <<< Das deutsche PC und DVB-Forum >>>

Diverse DVB Software für verschiedene Karten => # SmartDVB => Thema gestartet von: jackjavo am 12 Dezember, 2015, 15:04

Titel: New test builds
Beitrag von: jackjavo am 12 Dezember, 2015, 15:04

Hi again here,

How's everyone doing? If anyone here is still willing to test i'm busy with a new build atm. Main focus at this moment is the blindscan/dx side of the application since that needs an upgrade. If so just drop me a note and we'll continue this through pm or here whatever is preferred. Btw i'm not sending installs at this moment but just file replacements in archives for things that are changed since this works somewhat quicker for me allowing me to concentrate on fixing stuff first. The setup can be tested at a more appropriate moment closer to release...
best regards,
jack

Titel: Re: New test builds
Beitrag von: dada am 15 Dezember, 2015, 00:36

Hello Jack,
good to see you again. Just moved to W10 and Smart is working fine. I am ready to test what I can, but both of my cards can't do blindscan. Anything else I am willing to test.

Titel: Re: New test builds
Beitrag von: jackjavo am 15 Dezember, 2015, 12:20

Hi dada,
Ok thanks i'll send you a test version through pm here with some instructions..
I gather that most here are not blindscan enabled :). There are some other modifications and changes internally to the app to try to make it quicker. It also supports some simple .m3u http queries this allows iptv tools to use the HTTP streaming to view/switch the channels. For me this works somewhat on android IPTV tools, but this still could be extended to for example allow for xmltv epg retrieval if it works good enough and there's demand for such things. Also some scheduler bugs and additional recording options are added (record specific transport stream PIDS, like NIT/BAT etc, DVBSUBS). Also scheduled recordings from multiple instances was buggy should work better now some people have already tested this.
btw: is sdvb noticeably slower on w10 for u?

Titel: Re: New test builds
Beitrag von: Snoop am 15 Dezember, 2015, 13:19

With the stable version I had some problems with tuning - especially HD channels, tuning overall took very long. So I'm willing to test also.

Gesendet von meinem GT-I9505 mit Tapatalk

Titel: Re: New test builds
Beitrag von: dada am 15 Dezember, 2015, 14:27

no, I didn't notice any major difference in speed. W10 only forces me to start Smart "as administrator". After that w10 tells me that the source of the soft is unknown and if I really want to start....
W10 iis stuffed with "oversecurity". I will have to sniff in the various settings to get rid of this.

Titel: Re: New test builds
Beitrag von: Snoop am 15 Dezember, 2015, 19:31

I meant the stable version, edited my posting.

Gesendet von meinem GT-I9505 mit Tapatalk

Titel: Re: New test builds
Beitrag von: jackjavo am 15 Dezember, 2015, 20:26

hi snoop thanks for the support i've just sent you the url to the archive too. Btw it's certainly possible you had tune issues with the 0.4.0 stable release, i've had reports of that too there seemed to be some issues there, mainly i think because i tried to patch that version with delays here and there to prevent driver lockups with certain devices, but reverted that now somewhat, let's see :) btw as i mention in the pm better make sure you backup the files you replace form this archive which contains smartdvb.exe/smartexec.exe/blindscan.dev/bda.dev/graph.dll, the *.dev files of course should be copied manually to the devices folder, let me know if it works out and i've not made any mistaked concerning the archive..

Titel: Re: New test builds
Beitrag von: Snoop am 15 Dezember, 2015, 20:38

Hi Jack,

works!  ;D

But the problems at switching are still there. They mostly appear at programme start. When I try to do a first change to a HD channel, it needs a lot of time or even does not work. When I then change to an SD channel, I can afterwards switch to HD channels.

Titel: Re: New test builds
Beitrag von: jackjavo am 15 Dezember, 2015, 22:25

hi Snoop,

oh ok, Is this worse or the same as previous versions. Sounds like some driver issue for your device which is a terratec specific device? I dont have any special bda info on that, when you look at bda.log how is the device detected? (apologies if we had this discussion before :)).

Titel: Re: New test builds
Beitrag von: jackjavo am 16 Dezember, 2015, 11:12

hi snoop. Could you look at bda.log and see if have a 'status: locked' entry for those failed HD tunes and if so is there a large delay between the settuner and 'status: locked' message? If not then it's a tune issue otherwise we need to look further.? I've searched on the net and there are quite some people with issues with the cinergy s2 usb but mostly seem related to diseqc settings, but if i remember correctly you don't use diseqc? Please send me a bda.log/smartdvb.log or generate a report and post it to me (you can export reports to save them to file in the report dialog). I'll try have a better look. If sure it's some terratec device i could try to write the manufacturer about this if it's some generic card/diseqc problem..

Titel: Re: New test builds
Beitrag von: Snoop am 16 Dezember, 2015, 16:04

Where do I find the "bda.log"  ???

Titel: Re: New test builds
Beitrag von: jackjavo am 16 Dezember, 2015, 16:28

ohh ok. If a default install it should be in your local application data path (otherwise if data is installed in program files with w7 etc administrative privileges are required). For example c:\users\your name\appdata\local\smartdvb\logs. Otherwise it's in the devices folder where smartdvb.exe is in the program files folder. It's also described in the basic help file under section 'local application data files'. If you don't mind running smartdvb with admin privilegs you should better install the app using the second option (so all files in the program files install directory or some other directory). The latter allows for multiple instances with seperate settings, would also be better for testing. The help file also describes how the app looks for settings.ini in the local application data path, if there essentially multiple intances would use the same data path which is undesirable. So when using mutilple folder with multiple instances it's better to delete this settings.ini or rename it at least. But for your situation never mind the latter. Just look for it in your local app data path..

Titel: Re: New test builds
Beitrag von: Snoop am 16 Dezember, 2015, 16:36

Found the place of the log, started Smart and switched channels until a HD did not started:

Spoiler

16:32:23 0 - StartDevice()  dwDeviceNo:0
16:32:23 0 - >> DeviceGetList
16:32:23 0 - - Filter [CINERGY S2 USB BOX]
16:32:23 0 - << DeviceGetList
16:32:23 0 - Creating graph
16:32:23 515 - Tuner path \\?\usb#vid_0ccd&pid_0105#000000031#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{bae3794d-d7c2-44a1-9599-26ffcd90cf34}
16:32:23 515 - BDA Device Name: [CINERGY S2 USB BOX]      (Tuner Type:0)
16:32:23 515 - Using Direct tuning
16:32:23 515 - ConnectFilters: trying connection
16:32:23 531 - Connect Ok
16:32:23 531 - Adding callback filter
16:32:23 531 - ConnectFilters: trying connection
16:32:23 531 - Connect Ok
16:32:23 531 - Successfully connected sample grabber to tuner
16:32:23 531 - running control
16:32:25 2218 - In tevii_find_card
16:32:25 2234 - Tuner name CINERGY S2 USB BOX
16:32:25 2234 - name: CINERGY S2 USB BOX
16:32:25 2250 - BDA2: BuildGraph: found TeVii DiSEqC interface
16:32:25 2250 - remote control ok
16:32:25 2250 - Tevii card found
16:32:25 2250 - BDACardType: (tevii)
16:32:25 2250 - In tevii init
16:32:25 2250 - GetTunerInterfaces: Pin types (2) :
16:32:25 2250 - GetTunerInterfaces:      Pin 0 Type = 0
16:32:25 2250 - GetTunerInterfaces:      Pin 1 Type = 1
16:32:25 2250 - GetTunerInterfaces: Node types (2):
16:32:25 2250 - GetTunerInterfaces:      Node 0 Type = 0
16:32:25 2250 - GetTunerInterfaces:      Node 1 Type = 1
16:32:25 2250 - GetTunerInterfaces: Node interfaces:
16:32:25 2250 - GetTunerInterfaces:    Interfaces on NodeType 0   (5 interfaces):
16:32:25 2250 - GetTunerInterfaces:       {992CF102-49F9-4719-A664-C4F23E2408F4} IID_IBDA_LNBInfo           
16:32:25 2250 - GetTunerInterfaces:       {71985F47-1CA1-11D3-9CC8-00C04F7971E0} IID_IBDA_FrequencyFilter   
16:32:25 2250 - GetTunerInterfaces:       {1347D106-CF3A-428A-A5CB-AC0D9A2A4338} IID_IBDA_SignalStatistics 
16:32:25 2250 - GetTunerInterfaces:       {16FAAC60-9022-D420-1520-D9EB716F6EC9} Unknown Interface           - QueryInterface FAILED ! - hr = 0x80004002
16:32:25 2250 - GetTunerInterfaces:       {F84E2AB0-3C6B-45E3-A0FC-8669D4B81F11} Unknown Interface         
16:32:25 2250 - GetTunerInterfaces:    Interfaces on NodeType 1   (2 interfaces):
16:32:25 2250 - GetTunerInterfaces:       {EF30F379-985B-4D10-B640-A79D5E04E1E0} IID_IBDA_DigitalDemodulator
16:32:25 2250 - GetTunerInterfaces:       {1347D106-CF3A-428A-A5CB-AC0D9A2A4338} IID_IBDA_SignalStatistics 
16:32:25 2250 - StartDeviceDirect()    OK
16:32:25 2250 - ----------------------------------------------------------------------------
16:32:25 2250 -
16:32:25 2562 - SetTransponder: lock 5000, lnbtype 0, lof1 9750000, lof2 10600000, sw 11700000
16:32:25 2562 -
16:32:25 2562 - SetTuner() 12187000, H, 27500000   LOF:10600000  22Khz:1
16:32:25 2562 - Modulation used 20
16:32:28 4812 - In tevii_get_tuner_state 0
16:32:28 4812 - tevii_get_tuner_state ok strengh 100, quality 87
16:32:28 4812 - getting specific tuner state with timeout 5000
16:32:28 4812 - Status: Locked
16:32:28 4812 - Adding filter 110
16:32:28 4812 - Removing filter 8193
16:32:28 4812 - Adding filter 104
16:32:28 4812 - Adding filter 163
16:32:28 4812 - Adding filter 18
16:32:28 4812 - Adding filter 768
16:32:28 4812 - Adding filter 1089
16:32:28 4812 - Adding filter 3002
16:32:28 4812 - Adding filter 3003
16:32:30 6890 - In tevii_get_tuner_state 0
16:32:30 6890 - tevii_get_tuner_state ok strengh 100, quality 87
16:32:31 8343 - In tevii_get_tuner_state 0
16:32:31 8343 - tevii_get_tuner_state ok strengh 100, quality 87
16:32:33 9797 - In tevii_get_tuner_state 0
16:32:33 9797 - tevii_get_tuner_state ok strengh 100, quality 87
16:32:34 11312 - In tevii_get_tuner_state 0
16:32:34 11312 - tevii_get_tuner_state ok strengh 100, quality 87
16:32:36 12765 - In tevii_get_tuner_state 0
16:32:36 12765 - tevii_get_tuner_state ok strengh 100, quality 87
16:32:37 14218 - In tevii_get_tuner_state 0
16:32:37 14218 - tevii_get_tuner_state ok strengh 100, quality 87
16:32:38 15672 - In tevii_get_tuner_state 0
16:32:38 15672 - tevii_get_tuner_state ok strengh 100, quality 87
16:32:39 16156 - Removing filter 163
16:32:39 16156 - Removing filter 104
16:32:39 16187 - SetTransponder: lock 5000, lnbtype 0, lof1 9750000, lof2 10600000, sw 11700000
16:32:39 16187 -
16:32:39 16187 - SetTuner() 11493000, H, 22000000   LOF:9750000  22Khz:0
16:32:39 16187 - Modulation used 27
16:32:41 17734 - In tevii_get_tuner_state 0
16:32:41 17734 - tevii_get_tuner_state ok strengh 79, quality 86
16:32:41 17734 - getting specific tuner state with timeout 5000
16:32:41 17734 - Status: Locked
16:32:41 17734 - Removing filter 110
16:32:41 17734 - Removing filter 8193
16:32:41 17734 - Adding filter 5102
16:32:41 17734 - Adding filter 5101
16:32:41 18172 - In tevii_get_tuner_state 0
16:32:41 18172 - tevii_get_tuner_state ok strengh 79, quality 86
16:32:43 19968 - In tevii_get_tuner_state 0
16:32:43 19968 - tevii_get_tuner_state ok strengh 79, quality 86
16:32:44 21422 - In tevii_get_tuner_state 0
16:32:44 21422 - tevii_get_tuner_state ok strengh 79, quality 86
16:32:46 22859 - In tevii_get_tuner_state 0
16:32:46 22859 - tevii_get_tuner_state ok strengh 79, quality 86
16:32:47 24312 - In tevii_get_tuner_state 0
16:32:47 24312 - tevii_get_tuner_state ok strengh 78, quality 86
16:32:49 25765 - In tevii_get_tuner_state 0
16:32:49 25765 - tevii_get_tuner_state ok strengh 78, quality 86
16:32:50 27047 - Removing filter 5101
16:32:50 27047 - Removing filter 5102
16:32:50 27047 - SetTransponder: lock 5000, lnbtype 0, lof1 9750000, lof2 10600000, sw 11700000
16:32:50 27047 -
16:32:50 27047 - SetTuner() 11361000, H, 22000000   LOF:9750000  22Khz:0
16:32:50 27047 - Modulation used 27
16:32:51 28500 - In tevii_get_tuner_state 0
16:32:51 28500 - tevii_get_tuner_state ok strengh 72, quality 87
16:32:51 28500 - getting specific tuner state with timeout 5000
16:32:51 28500 - Status: Locked
16:32:51 28500 - Removing filter 8193
16:32:51 28500 - Adding filter 6120
16:32:51 28500 - Adding filter 6110
16:32:53 30593 - In tevii_get_tuner_state 0
16:32:53 30593 - tevii_get_tuner_state ok strengh 72, quality 87
16:32:55 32047 - In tevii_get_tuner_state 0
16:32:55 32047 - tevii_get_tuner_state ok strengh 72, quality 87
16:32:55 32515 - Removing filter 6110
16:32:55 32515 - Removing filter 6120
16:32:55 32547 - SetTransponder: lock 5000, lnbtype 0, lof1 9750000, lof2 10600000, sw 11700000
16:32:55 32547 -
16:32:55 32547 - SetTuner() 11582000, H, 22000000   LOF:9750000  22Khz:0
16:32:55 32547 - Modulation used 27
16:32:58 35312 - FAILED: property_set_set_tuner()
16:32:58 35312 - FAILED: SetTuner()
16:32:58 35312 - Failed sending tunerequest
16:32:58 35312 - In tevii_get_tuner_state 0
16:32:58 35312 - tevii_get_tuner_state ok strengh 0, quality 85
16:32:58 35312 - getting specific tuner state with timeout 5000
16:32:58 35312 - Status: Locked
16:32:58 35312 - Removing filter 8193
16:32:58 35312 - Adding filter 5202
16:32:58 35312 - Adding filter 5201
16:33:00 37406 - In tevii_get_tuner_state 0
16:33:00 37406 - tevii_get_tuner_state ok strengh 79, quality 85
16:33:02 38968 - In tevii_get_tuner_state 0
16:33:02 38968 - tevii_get_tuner_state ok strengh 79, quality 85
16:33:03 40531 - In tevii_get_tuner_state 0
16:33:03 40531 - tevii_get_tuner_state ok strengh 79, quality 85
16:33:05 42109 - In tevii_get_tuner_state 0
16:33:05 42109 - tevii_get_tuner_state ok strengh 79, quality 85
16:33:06 43687 - In tevii_get_tuner_state 0
16:33:06 43687 - tevii_get_tuner_state ok strengh 78, quality 85
16:33:08 45250 - In tevii_get_tuner_state 0
16:33:08 45250 - tevii_get_tuner_state ok strengh 78, quality 85
16:33:10 46812 - In tevii_get_tuner_state 0
16:33:10 46812 - tevii_get_tuner_state ok strengh 78, quality 85
16:33:11 48390 - In tevii_get_tuner_state 0
16:33:11 48390 - tevii_get_tuner_state ok strengh 78, quality 85
16:33:13 49953 - In tevii_get_tuner_state 0
16:33:13 49953 - tevii_get_tuner_state ok strengh 78, quality 85
16:33:14 51515 - In tevii_get_tuner_state 0
16:33:14 51515 - tevii_get_tuner_state ok strengh 78, quality 85
16:33:16 53328 - StopDevice()
16:33:16 53328 - StopDevice before stopping mediacontrol 66811281
16:33:16 53328 - StopDevice after stopping mediacontrol 66811281
16:33:17 54093 - BDACleanup 1
16:33:17 54093 - BDACleanup 2
16:33:17 54093 - BDACleanup 3
16:33:17 54093 - BDACleanup 4
16:33:17 54093 - BDACleanup 5
16:33:17 54093 - BDACleanup 6
16:33:17 54093 - BDACleanup 7
16:33:17 54093 - BDACleanup 13 before freeing graph 66812046
16:33:17 54093 - free_graph releasing rot 66812046
16:33:17 54093 - free_graph releasing graph 66812046
16:33:17 54093 - free_graph releasing mediacontrol 66812046
16:33:17 54093 - free_graph done 66812046
16:33:17 54093 - BDACleanup 8
16:33:17 54093 - BDACleanup 10 before ftlNetworkProviderDirect 66812046
16:33:17 54093 - BDACleanup 9 before deleting networkprovider instance 66812046
16:33:17 54093 - BDACleanup 11 before deleting callback 66812046
16:33:17 54093 - BDACleanup before deleting callback instance 66812046
16:33:17 54093 - BDACleanup 13 after freeing graph 66812046
16:33:17 54093 - BDACleanup end

[close]

Titel: Re: New test builds
Beitrag von: jackjavo am 16 Dezember, 2015, 19:39

Hi Snoop. Seems the device is deteceted as tevii which doesn''t totally surprise me as i read somehere it's technically the same as a tevii660 .  Still could've been different driver extensions i imagined but perhaps not. Iooking at the logs the first thing i notice you're using direct tuning mode, is there a reason for doing so? Could you change the tuning mode from direct to standard mode. I see from the log there's avtualke a tuning error when it fails which is good at least there a reference point to start from. Normally standard tune mode should present the more stable tune method albeit perhaps slower. You can change the tune mode at tools device settings for bda.dev. btw there is some old tevii code in bdas.dev so if all fails you could try that too.

Titel: Re: New test builds
Beitrag von: Snoop am 16 Dezember, 2015, 20:23

Hi Jack,

I changed to direct tuning to gain speed in changing channels, but it did not help ... I just forgot to set it back to default.
Did so right now and got again a "hang up":

Spoiler

20:15:22 0 - StartDevice()  dwDeviceNo:0
20:15:22 0 - >> DeviceGetList
20:15:22 0 - - Filter [CINERGY S2 USB BOX]
20:15:22 0 - << DeviceGetList
20:15:22 15 - Creating graph
20:15:23 515 - Tuner path \\?\usb#vid_0ccd&pid_0105#000000031#{71985f48-1ca1-11d3-9cc8-00c04f7971e0}\{bae3794d-d7c2-44a1-9599-26ffcd90cf34}
20:15:23 515 - BDA Device Name: [CINERGY S2 USB BOX]      (Tuner Type:0)
20:15:23 515 - Using standard tuning
20:15:23 515 - Tunertype 0
20:15:23 515 - Creating networkprovider
20:15:23 562 - Loading tuningspace
20:15:23 562 - TuningSpace Name: 'Antenna'  NetworkType: {00000000-0000-0000-0000-000000000000}
20:15:23 562 - TuningSpace Name: 'ATSC'  NetworkType: {0DAD2FDD-5FD7-11D3-8F50-00C04F7971E2}
20:15:23 562 - TuningSpace Name: 'ATSCCable'  NetworkType: {0DAD2FDD-5FD7-11D3-8F50-00C04F7971E2}
20:15:23 562 - TuningSpace Name: 'AuxIn1'  NetworkType: {00000000-0000-0000-0000-000000000000}
20:15:23 562 - TuningSpace Name: 'Cable'  NetworkType: {00000000-0000-0000-0000-000000000000}
20:15:23 562 - TuningSpace Name: 'Digital Cable'  NetworkType: {143827AB-F77B-498D-81CA-5A007AEC28BF}
20:15:23 562 - TuningSpace Name: 'DVB-S'  NetworkType: {FA4B375A-45B4-4D45-8440-263957B11623}
20:15:23 562 - TuningSpace Name: 'DVB-T'  NetworkType: {216C62DF-6D7F-4E9A-8571-05F14EDB766A}
20:15:23 562 - TuningSpace Name: 'FM Radio'  NetworkType: {00000000-0000-0000-0000-000000000000}
20:15:23 562 - TuningSpace Name: 'ISDB-S'  NetworkType: {B0A4E6A0-6A1A-4B83-BB5B-903E1D90E6B6}
20:15:23 562 - TuningSpace Name: 'ISDB-T'  NetworkType: {95037F6F-3AC7-4452-B6C4-45A9CE9292A2}
20:15:23 562 - TuningSpace Name: 'SMART DVB-S'  NetworkType: {FA4B375A-45B4-4D45-8440-263957B11623}
20:15:23 562 - Enumeration found 12 tuning spaces
20:15:23 562 - Found TuningSpace
20:15:23 562 - Initializing tuningspace
20:15:23 562 - Connecting network provider
20:15:23 562 - ConnectFilters: trying connection
20:15:23 578 - Connect Ok
20:15:23 578 - Creating grabber
20:15:23 578 - ConnectFilters: trying connection
20:15:23 578 - Connect Ok
20:15:23 578 - Successfully connected grabber to tuner
20:15:23 578 - create demuxer end
20:15:23 578 - ConnectFilters: trying connection
20:15:23 578 - Connect Ok
20:15:23 578 - connect sample grabber demuxer end
20:15:23 578 - create tif end
20:15:23 578 - ConnectFilters: trying connection
20:15:23 578 - Connect Ok
20:15:23 578 - connect demuxer tif end
20:15:24 2250 - after run
20:15:24 2250 - In tevii_find_card
20:15:24 2250 - Tuner name CINERGY S2 USB BOX
20:15:24 2250 - name: CINERGY S2 USB BOX
20:15:24 2281 - BDA2: BuildGraph: found TeVii DiSEqC interface
20:15:24 2281 - remote control ok
20:15:24 2281 - Tevii card found
20:15:24 2281 - BDACardType: (tevii)
20:15:24 2281 - GetTunerInterfaces: Pin types (2) :
20:15:24 2281 - GetTunerInterfaces:      Pin 0 Type = 0
20:15:24 2281 - GetTunerInterfaces:      Pin 1 Type = 1
20:15:24 2281 - GetTunerInterfaces: Node types (2):
20:15:24 2281 - GetTunerInterfaces:      Node 0 Type = 0
20:15:24 2281 - GetTunerInterfaces:      Node 1 Type = 1
20:15:24 2281 - GetTunerInterfaces: Node interfaces:
20:15:24 2281 - GetTunerInterfaces:    Interfaces on NodeType 0   (5 interfaces):
20:15:24 2281 - GetTunerInterfaces:       {992CF102-49F9-4719-A664-C4F23E2408F4} IID_IBDA_LNBInfo           
20:15:24 2281 - GetTunerInterfaces:       {71985F47-1CA1-11D3-9CC8-00C04F7971E0} IID_IBDA_FrequencyFilter   
20:15:24 2281 - GetTunerInterfaces:       {1347D106-CF3A-428A-A5CB-AC0D9A2A4338} IID_IBDA_SignalStatistics 
20:15:24 2281 - GetTunerInterfaces:       {16FAAC60-9022-D420-1520-D9EB716F6EC9} Unknown Interface           - QueryInterface FAILED ! - hr = 0x80004002
20:15:24 2281 - GetTunerInterfaces:       {F84E2AB0-3C6B-45E3-A0FC-8669D4B81F11} Unknown Interface         
20:15:24 2281 - GetTunerInterfaces:    Interfaces on NodeType 1   (2 interfaces):
20:15:24 2281 - GetTunerInterfaces:       {EF30F379-985B-4D10-B640-A79D5E04E1E0} IID_IBDA_DigitalDemodulator
20:15:24 2281 - GetTunerInterfaces:       {1347D106-CF3A-428A-A5CB-AC0D9A2A4338} IID_IBDA_SignalStatistics 
20:15:24 2281 - In tevii init
20:15:24 2281 - StartDevice()    OK
20:15:24 2281 - ----------------------------------------------------------------------------
20:15:24 2281 -
20:15:25 2578 - SetTransponder: lock 5000, lnbtype 0, lof1 9750000, lof2 10600000, sw 11700000
20:15:25 2578 -
20:15:25 2578 - SetTuner() 11493000, H, 22000000   LOF:9750000  22Khz:0
20:15:25 2578 - Modulation used 27
20:15:26 4078 - In tevii_get_tuner_state 0
20:15:26 4078 - tevii_get_tuner_state ok strengh 0, quality 0
20:15:26 4078 - getting specific tuner state with timeout 5000
20:15:26 4078 - Status: Locked
20:15:26 4078 - Removing filter 8193
20:15:26 4078 - Adding filter 5102
20:15:26 4078 - Adding filter 5101
20:15:26 4125 - Adding filter 18
20:15:26 4125 - Adding filter 768
20:15:26 4125 - Adding filter 1089
20:15:26 4125 - Adding filter 3002
20:15:26 4125 - Adding filter 3003
20:15:27 4500 - In tevii_get_tuner_state 0
20:15:27 4500 - tevii_get_tuner_state ok strengh 75, quality 85
20:15:28 6297 - In tevii_get_tuner_state 0
20:15:28 6297 - tevii_get_tuner_state ok strengh 75, quality 85
20:15:30 7750 - In tevii_get_tuner_state 0
20:15:30 7750 - tevii_get_tuner_state ok strengh 75, quality 85
20:15:31 8859 - Removing filter 5101
20:15:31 8859 - Removing filter 5102
20:15:31 8875 - SetTransponder: lock 5000, lnbtype 0, lof1 9750000, lof2 10600000, sw 11700000
20:15:31 8875 -
20:15:31 8875 - SetTuner() 11361000, H, 22000000   LOF:9750000  22Khz:0
20:15:31 8875 - Modulation used 27
20:15:33 10937 - In tevii_get_tuner_state 0
20:15:33 10937 - tevii_get_tuner_state ok strengh 68, quality 86
20:15:33 10937 - getting specific tuner state with timeout 5000
20:15:33 10937 - Status: Locked
20:15:33 10937 - Removing filter 8193
20:15:33 10937 - Adding filter 6120
20:15:33 10937 - Adding filter 6110
20:15:35 13031 - In tevii_get_tuner_state 0
20:15:35 13031 - tevii_get_tuner_state ok strengh 68, quality 86
20:15:36 14484 - In tevii_get_tuner_state 0
20:15:36 14484 - tevii_get_tuner_state ok strengh 68, quality 86
20:15:37 14984 - Removing filter 6110
20:15:37 14984 - Removing filter 6120
20:15:37 15031 - SetTransponder: lock 5000, lnbtype 0, lof1 9750000, lof2 10600000, sw 11700000
20:15:37 15031 -
20:15:37 15031 - SetTuner() 11582000, H, 22000000   LOF:9750000  22Khz:0
20:15:37 15031 - Modulation used 27
20:15:40 17703 - FAILED: property_set_set_tuner()
20:15:40 17703 - Failed sending tunerequest
20:15:40 17703 - In tevii_get_tuner_state 0
20:15:40 17703 - tevii_get_tuner_state ok strengh 77, quality 85
20:15:40 17703 - getting specific tuner state with timeout 5000
20:15:40 17703 - Status: Locked
20:15:40 17703 - Removing filter 8193
20:15:40 17703 - Adding filter 5202
20:15:40 17703 - Adding filter 5201
20:15:42 19765 - In tevii_get_tuner_state 0
20:15:42 19765 - tevii_get_tuner_state ok strengh 77, quality 85
20:15:43 21344 - In tevii_get_tuner_state 0
20:15:43 21344 - tevii_get_tuner_state ok strengh 77, quality 85
20:15:45 22922 - In tevii_get_tuner_state 0
20:15:45 22922 - tevii_get_tuner_state ok strengh 77, quality 85
20:15:46 24484 - In tevii_get_tuner_state 0
20:15:46 24484 - tevii_get_tuner_state ok strengh 78, quality 85
20:15:48 26047 - In tevii_get_tuner_state 0
20:15:48 26047 - tevii_get_tuner_state ok strengh 77, quality 85
20:15:50 27609 - In tevii_get_tuner_state 0
20:15:50 27609 - tevii_get_tuner_state ok strengh 77, quality 85
20:15:51 29172 - In tevii_get_tuner_state 0
20:15:51 29172 - tevii_get_tuner_state ok strengh 77, quality 85
20:15:54 31828 - StopDevice()
20:15:54 31828 - StopDevice before stopping mediacontrol 11305984
20:15:54 31828 - StopDevice after stopping mediacontrol 11305984
20:15:55 32578 - BDACleanup 1
20:15:55 32578 - BDACleanup 2
20:15:55 32578 - BDACleanup 3
20:15:55 32578 - BDACleanup 4
20:15:55 32578 - BDACleanup 5
20:15:55 32578 - BDACleanup 6
20:15:55 32578 - BDACleanup 7
20:15:55 32578 - BDACleanup 13 before freeing graph 11306734
20:15:55 32578 - free_graph releasing rot 11306734
20:15:55 32578 - free_graph releasing graph 11306734
20:15:55 32578 - free_graph releasing mediacontrol 11306734
20:15:55 32594 - free_graph done 11306750
20:15:55 32594 - BDACleanup 8
20:15:55 32594 - BDACleanup 10 before ftlNetworkProviderDirect 11306750
20:15:55 32594 - BDACleanup 9 before deleting networkprovider instance 11306750
20:15:55 32594 - BDACleanup 11 before deleting callback 11306750
20:15:55 32594 - BDACleanup before deleting callback instance 11306750
20:15:55 32594 - BDACleanup 13 after freeing graph 11306750
20:15:55 32594 - BDACleanup end

[close]

After restart I changed to bdas.dev the tuning is a little bit faster overall and I get no hang ups an the moment. Thanks for your help! :D

Titel: Re: New test builds
Beitrag von: dada am 17 Dezember, 2015, 22:32

I did some tests with the new build. The blindscan  stuff I could not test, because my cards do not supprort blindscan. A few days ago I upgraded to w10, so I made a backup copy of sdvb before I copied the new files to sdvb. It ran normally right from the start. I had the impression that sdvb reacted even quicker (compared to w7)  but I did not do any specific tests. I tested fairly intensively the new possibility of controlling sdvb from clients with vlc via http. This works excellently! Via an m3u playlist it is possible from clients to change channels (right now only the Astra sats are implemented). Channel change is very fast and even on my aged system HD channels get through without stuttering.
Will do more tests on other improvements...

Titel: Re: New test builds
Beitrag von: jackjavo am 17 Dezember, 2015, 23:01

Hi dada. Thanks for the feedback, sounds good i also did some tests with that and yes you're not the only one reporting that the app seems snappier i've been looking at that too (without risking too much compatibility issues, which is always like walking a tight rope). Good to know the streaming works ok, i tested this myself of course and still lots can be done to return a more customized .m3u list perhaps compared to right now only favorites etc one could imagine it's not much work. Besides that as you mentioned implementing other protocols besides http might be something for the future too..

@Snoop: i'm looking still at the cinergy box issues you have, now that i know it's a tevii device essentially i have something to look at. Oddly enough bda.dev uses tevii sdk so i'm surprised the sdk calls seem less stable and slower compared to some old basic bda code from bdas.dev which doesn't really use the sdk, just some specific extensions for diseqc (which i'm not even sure would be fully implemented with bdas.dev so still worth the trouble to investigate the bda.dev issues some more).

Titel: Re: New test builds
Beitrag von: Snoop am 18 Dezember, 2015, 16:37

Thanks in advance!  ;Beifall

Titel: Re: New test builds
Beitrag von: jackjavo am 18 Dezember, 2015, 16:44

btw snoop after some reading if you're device is truly tevii compatible you should be able to use the blindscan.dev device also instead of bdas.dev. Not sure of the channel switch and stability of that (not concerning crazycat's implementation but more mine blindscan.dev has hardly not been used by myself or tested with regards to channel switching and stability etc). But it might even be quicker since crazycats implementation usually is superior. You might have a look i wonder if it would work..

Titel: Re: New test builds
Beitrag von: Snoop am 18 Dezember, 2015, 19:19

Don't get a picture with blindscan although I can select it ...

Titel: Re: New test builds
Beitrag von: jackjavo am 18 Dezember, 2015, 20:56

ahh ok. Now i think of it i read tevii enabled blindscan for their drivers with their more recent drivers, and your device is essentially a tevii 660 (the components are even on the same place i read). So it probably won't work without specific manufacturer driver modifications. But i would not advice you try installing tevii drivers for your device i presume you've installed drivers you found specific for this cinergy s2 usb box. (i'll search if someone has done that, but doubt it, would have remembered if i had read that). You did replace your previous blindscan.dev with the one provided in the .zip archive? It's a shame you almost had a blindscan device after all :). You don't get a picture but you do see signal/quality/ tune changes with the device?
edit: probably never will work due to different usb identifications btw using other drivers (even if the drivers essentially might be the same)..

Titel: Re: New test builds
Beitrag von: Snoop am 18 Dezember, 2015, 22:13

I replaced all the files with the ones in the zip and I don't get signal and quality

Titel: Re: New test builds
Beitrag von: Snoop am 23 Dezember, 2015, 16:50

Thanks for the new test build, it's working pretty well on first glance, I will test the scheduler the next days.

Merry Christmas to you, Jack!  :)

Titel: Re: New test builds
Beitrag von: jackjavo am 23 Dezember, 2015, 23:34

ok good to know. Btw if you really downloaded that archive i sent you quickly, please make sure it  includes streamreader.dll. I modified some header stuff there and forgot to add streamreader.dll to the initial archive but was able to correct that within a couple of minutes

thanks and merry christmas to all here too of course..

Titel: Re: New test builds
Beitrag von: jackjavo am 28 Dezember, 2015, 16:42

hi i've bit the bullet and released a new beta for those interested. This time it's an install, but still beta so beware:

https://dl.dropboxusercontent.com/u/51980102/SmartDVB045beta1tst.zip

thanks and have a good new year..

Titel: Re: New test builds
Beitrag von: Snoop am 28 Dezember, 2015, 16:50

 :jb ;Beifall  :jo
Any changes to our "internal" last version?

Also a happy new year to you!  :rauch

Titel: Re: New test builds
Beitrag von: jackjavo am 28 Dezember, 2015, 18:57

No snoop i just consolidated the release. Mainly blindscan/dx fixes. Some small changes to the install  the transponder  .ini files are unpacked instead of installed, also the satellite files themselve are updated to more current frequency lists

Thanks appreciated

Titel: Re: New test builds
Beitrag von: ioosis am 10 Januar, 2016, 17:31

it reads v 0.4.0.24  is that the latest beta

Titel: Re: New test builds
Beitrag von: jackjavo am 11 Januar, 2016, 21:22

Yes indeed thats the current beta

Titel: Re: New test builds
Beitrag von: ioosis am 04 März, 2016, 08:23

no new latest version plz

Titel: Re: New test builds
Beitrag von: ioosis am 19 August, 2016, 10:16

any hope new version