Autor Thema: Windows Network Driver 26. July 2015  (Gelesen 29372 mal)

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8512
    • Profil anzeigen
Windows Network Driver 26. July 2015
« am: März 19, 2012, 07:12:54 Vormittag »
Setup:
http://www.sundtek.de/media/SundtekInstaller.zip (always links to the latest version)

This driver allows to use the device via network, the device can be attached to any MacOSX or Linux PC (NAS, Settopbox) and currently stream DVB-T, DVB-S to Windows Mediacenter and DVB-C to DVBViewer. As we are moving forward quickly with this it's work in progress, if you have any issues with it please let us know!

* Version 15-07-26
- http://www.sundtek.de/media/SundtekInstaller_150726.zip
- added DVB-S2 support
- added DISEQC support
- added option for directly entering the IP address

* Using new version number from now on (Version 150719)
- http://www.sundtek.de/media/SundtekInstaller_150719.zip
- tested DVB-C via network using the latest drivers
- moved to new build system



* Version 0.2.7.9
- http://www.sundtek.de/media/SundtekInstaller_140610.zip
- Update new Network API

* Version 0.2.7.8
- http://www.sundtek.de/media/SundtekInstaller_140225.zip
- Update new network API

* Version 0.2.7.7
- http://www.sundtek.de/media/SundtekInstaller_130303.rar
- Supporting multiple devices

* Version 0.2.7.6
- http://www.sundtek.de/media/SundtekInstaller_130117.zip
- Bugfix, Crash on some systems

* Version 0.2.7.3
- http://www.sundtek.de/media/SundtekInstaller_121114.zip
- DVB-C and DVB-T are using the new tuning mechanism

* Version 0.2.7.2
- http://www.sundtek.de/media/SundtekInstaller_121108.zip
- Polarization is now supported via diseqc

* Version 0.2.7.1
- http://www.sundtek.de/media/SundtekInstaller_121106.zip
- Use of different control interface to support Pos/Opt

* Version 0.2.7
- http://www.sundtek.de/media/SundtekInstaller_121106.zip
- DVB-S/S2 Pos/Opt Diseqc Controls are supported
- Faster DVB-C zapping
 
* Version 0.2.6
- http://www.sundtek.de/media/SundtekInstaller_120404.zip
- Updated network protocol to support routers like TP-Link WR1043ND, Netgear WNDR3700 etc.

* Version 0.2.5
- http://www.sundtek.de/media/SundtekInstaller_120323.zip
- buxfix network buffer
- initial DVB-S support (S2 will be available within the next update)
- DVB-T and DVB-S are supported with Windows Mediacenter
- DVB-S is tested with Windows Mediacenter and DVBViewer

* Version 0.2.1
- http://www.sundtek.de/media/SundtekInstaller_120318.zip
- Bandwidth filter for DVB-C is supported now, this allows to stream DVB-C via Wifi in your home network
- Reworked installer a little bit.

* Version 0.2
- http://www.sundtek.de/media/SundtekInstaller_120317.zip
- Installer now contains Microsoft Support libraries
- First version which includes support for DVB-C with DVBViewer
- Switching between DVB-C and DVB-T is now possible with Sundtek Streamline Scanner
- Windows Mediacenter is currently not supported with DVB-C, WMC DVB-C Support is scheduled for version 0.3
- Started to integrate DVB-S/S2 support, although first support is scheduled for version 0.3
- experimental build
- DVB-C channel switching time is around 2 seconds via network

* Version 0.1
- http://www.sundtek.de/media/SundtekInstaller_120306.zip
- first version which supports DVB-T via network with Windows Mediacenter
- DVB-T channel switching time is around 2 seconds via network


DVBViewer, Einstellungen, Optionen, Hardware


please ensure that the marked options are not selected, the first option is for lowering the network bandwidth utilization, the second one must not be checked to be able to use the tuner.





Doubleclick onto the selected device is enough for connecting to it.






CPU usage on the server during streaming (0%!):


Configured PID filters Windows 7 Mediacenter
« Letzte Änderung: Juli 28, 2015, 01:46:47 Nachmittag von Sundtek »
Failure is a good thing! I'll fix it

gergomez

  • Newbie
  • *
  • Beiträge: 40
    • Profil anzeigen
Re:Windows Network Driver 23. March 2012
« Antwort #1 am: März 23, 2012, 03:06:41 Nachmittag »
Does this driver also supports USB Stick directly connected to the Windows machine??

Regards,

- german

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8512
    • Profil anzeigen
Re:Windows Network Driver 23. March 2012
« Antwort #2 am: März 24, 2012, 08:20:20 Vormittag »
After talking with our Engineer, it should be possible in near future as the code for it has already been written. Maybe we can push out some experimental version for DVB-T only (as this is the easier one) within the next 1-2 weeks.
Failure is a good thing! I'll fix it

WalVos

  • Newbie
  • *
  • Beiträge: 1
    • Profil anzeigen
Re:Windows Network Driver 04. April 2012
« Antwort #3 am: April 26, 2012, 02:45:05 Nachmittag »
Hi,

I have a question, will it be possible in the near future to use windows media player in combination with DVB-C functionality and by when? Will the stick work in a 100% windows 7 environment (I'm reading about Linux)?

I'm planning to attach the stick to my NAS (D-link sharecenter pulse DNS-320). Is there any way to control the stick through a media player (by using windows media player or DVBviewer)?

Thank you.

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8512
    • Profil anzeigen
Re:Windows Network Driver 04. April 2012
« Antwort #4 am: April 26, 2012, 03:02:47 Nachmittag »
DVBViewer already works with DVB-C via Network

Windows Mediacenter will also work in near future, we only need to help Windows Mediacenter to set the correct Symbolrate (by default it does not give us that information that's the only reason why it's not supported with DVB-C right now, DVB-T and DVB-S works with it)

Our Engineers are currently only finishing some Settopbox and new device integration work afterwards they will be back to that topic (should be around 1-2 weeks hopefully)
Failure is a good thing! I'll fix it

roel

  • Newbie
  • *
  • Beiträge: 4
    • Profil anzeigen
Switching between different modulations slow on dvb-c
« Antwort #5 am: Mai 14, 2012, 10:34:02 Nachmittag »
Hi,

As DVB server i'm using linux with the current linux driver.
tested with both the mini-pci-express and the usb media tv pro tuner.

As client i'm using windows 7 , with the latest dvbviewer pro.
Current sundtek network driver for windows.

My cable provider is delivering two different types of transponders.
Most of the transponders are modulated witch QAM64
Some transponders are migrated to QAM256.

On DVBvieuwer switching between channels with the same modulation works fine.
But when switching between channels witch different modulations (QAM64 -> QAM256 or the other way around) is very slow.

Some more investigation on the linux DVB server learns that the DVBviewer client (or just the network plugin on windows) isn't directly tuning to the right modulation after tuning to a channel with a different modulation.

I think it has to do with the windows network client because it seems to still requests the modulation, of the previous tuned channel/transponder.
But maybe it's the dvb-c server on the linux side , which is not detecting the modulation change.




Log of Linux DVB-C server (switching between same modulation tranponder):

SIGNAL: [.................................] (100%)  BER:      0 FREQ: 412000000  Hz LOCKED: YES MER: 357 SYM: 6875000 MOD: QAM256
SIGNAL: [.................................] (100%)  BER:      0 FREQ: 412000000  Hz LOCKED: YES MER: 356 SYM: 6875000 MOD: QAM256
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 404000000  Hz LOCKED: YES MER: 355 SYM: 6875000 MOD: QAM256
SIGNAL: [.............                    ] ( 40%)  BER:  41248 FREQ: 404000000  Hz LOCKED: YES MER: 355 SYM: 6875000 MOD: QAM256
SIGNAL: [.............                    ] ( 40%)  BER:  41248 FREQ: 404000000  Hz LOCKED: YES MER: 357 SYM: 6875000 MOD: QAM256
SIGNAL: [.............                    ] ( 39%)  BER:  41248 FREQ: 404000000  Hz LOCKED: YES MER: 355 SYM: 6875000 MOD: QAM256
SIGNAL: [.............                    ] ( 39%)  BER:  41248 FREQ: 404000000  Hz LOCKED: YES MER: 352 SYM: 6875000 MOD: QAM256
SIGNAL: [.............                    ] ( 39%)  BER:     75 FREQ: 404000000  Hz LOCKED: YES MER: 352 SYM: 6875000 MOD: QAM256
SIGNAL: [..............................   ] ( 90%)  BER:     75 FREQ: 404000000  Hz LOCKED: YES MER: 352 SYM: 6875000 MOD: QAM256
SIGNAL: [..............................   ] ( 90%)  BER:      0 FREQ: 404000000  Hz LOCKED: YES MER: 352 SYM: 6875000 MOD: QAM256
SIGNAL: [.................................] (100%)  BER:      0 FREQ: 404000000




Log of Linux DVB-C server (switching between different modulation tranponder):



SIGNAL: [.................................] (100%)  BER:      0 FREQ: 404000000  Hz LOCKED: YES MER: 352 SYM: 6875000 MOD: QAM256
SIGNAL: [.................................] (100%)  BER:      0 FREQ: 404000000  Hz LOCKED: YES MER: 352 SYM: 6875000 MOD: QAM256

< Here the logging pauzes for about 5 seconds >

SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 372000000  Hz LOCKED:  NO MER: 0 SYM: 6875000 MOD: QAM256
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 372000000  Hz LOCKED:  NO MER: 0 SYM: 6875000 MOD: QAM256
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 372000000  Hz LOCKED:  NO MER: 0 SYM: 6875000 MOD: QAM256
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 372000000  Hz LOCKED:  NO MER: 0 SYM: 6875000 MOD: QAM256
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 372000000  Hz LOCKED:  NO MER: 0 SYM: 6875000 MOD: QAM256
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 372000000  Hz LOCKED:  NO MER: 0 SYM: 6875000 MOD: QAM256
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 372000000  Hz LOCKED:  NO MER: 0 SYM: 6875000 MOD: QAM256
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 372000000  Hz LOCKED:  NO MER: 0 SYM: 6875000 MOD: QAM256
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 372000000  Hz LOCKED:  NO MER: 0 SYM: 6875000 MOD: QAM256
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 372000000  Hz LOCKED:  NO MER: 0 SYM: 6875000 MOD: QAM256
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 372000000  Hz LOCKED:  NO MER: 0 SYM: 6875000 MOD: QAM256
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 372000000  Hz LOCKED:  NO MER: 0 SYM: 6875000 MOD: QAM256
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 372000000  Hz LOCKED:  NO MER: 0 SYM: 6875000 MOD: QAM256
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 372000000  Hz LOCKED:  NO MER: 0 SYM: 6875000 MOD: QAM256
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 372000000  Hz LOCKED:  NO MER: 0 SYM: 6875000 MOD: QAM256
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 372000000  Hz LOCKED:  NO MER: 0 SYM: 6875000 MOD: QAM256
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 372000000  Hz LOCKED:  NO MER: 0 SYM: 6875000 MOD: QAM256
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 372000000  Hz LOCKED:  NO MER: 0 SYM: 6875000 MOD: QAM256
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 372000000  Hz LOCKED:  NO MER: 0 SYM: 6875000 MOD: QAM256
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 372000000  Hz LOCKED:  NO MER: 0 SYM: 6875000 MOD: QAM256
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 372000000  Hz LOCKED:  NO MER: 0 SYM: 6875000 MOD: QAM256
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 372000000  Hz LOCKED:  NO MER: 0 SYM: 6875000 MOD: QAM256
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 372000000  Hz LOCKED:  NO MER: 0 SYM: 6875000 MOD: QAM256
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 372000000  Hz LOCKED:  NO MER: 0 SYM: 6875000 MOD: QAM256
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 372000000  Hz LOCKED:  NO MER: 0 SYM: 6875000 MOD: QAM256
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 372000000  Hz LOCKED:  NO MER: 335 SYM: 6875000 MOD: QAM256
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 372000000  Hz LOCKED: YES MER: 333 SYM: 6875000 MOD: QAM64
SIGNAL: [                                 ] (  0%)  BER:  41248 FREQ: 372000000  Hz LOCKED: YES MER: 335 SYM: 6875000 MOD: QAM64
SIGNAL: [.............                    ] ( 40%)  BER:  41248 FREQ: 372000000  Hz LOCKED: YES MER: 336 SYM: 6875000 MOD: QAM64
SIGNAL: [.............                    ] ( 40%)  BER:  41248 FREQ: 372000000  Hz LOCKED: YES MER: 333 SYM: 6875000 MOD: QAM64
SIGNAL: [..............................   ] ( 92%)  BER:     59 FREQ: 372000000  Hz LOCKED: YES MER: 331 SYM: 6875000 MOD: QAM64
SIGNAL: [..............................   ] ( 92%)  BER:     59 FREQ: 372000000  Hz LOCKED: YES MER: 331 SYM: 6875000 MOD: QAM64


Kind regards,

Roel

Sundtek

  • Administrator
  • Hero Member
  • *****
  • Beiträge: 8512
    • Profil anzeigen
Re:Windows Network Driver 04. April 2012
« Antwort #6 am: Mai 15, 2012, 08:40:12 Vormittag »
The commands aren't sent as a complete transaction, rather than single commands. This is something that should be updated in the windows network driver on our side, we put it onto our todo list (unfortunately there are some other topics on our list right now... best would be to subscribe to this posting and we'll come back with a solution as soon as possible).
Failure is a good thing! I'll fix it

Tryon

  • Newbie
  • *
  • Beiträge: 41
    • Profil anzeigen
auto-detect the language of the OS
« Antwort #7 am: Februar 22, 2016, 02:05:48 Vormittag »
As we are moving forward quickly with this it's work in progress, if you have any issues with it please let us know!
Hi!
Maybe it would be good idea to use translated version when detected OS language is not DE?