Jump to content
hackbart

DVBViewer Media Server Announcement

Recommended Posts

hackbart

Advance information for our customers:

This year we will release two new major versions: DVBViewer Pro 6.0 and DVBViewer Media Server 2.0 (former Recording Service).

The most important change: In contrast to the Recording Service the DVBViewer Media Server will not be a beta version anymore Using it will require another licence in addition to the DVBViewer licence:

  • Customers who already have a DVBViewer licence will get a Media Server licence for € 19,-.
  • Customers who want to use the DVBViewer Media Server, but don't have a DVBViewer licence yet additionally need to purchase DVBViewer for € 20,-, yielding a total of € 39,-.

This means, we will offer the Media Server like the Recording Service as a DVBViewer-based add-on.

The new versions will provide several enhancements and new features. In the last months the development focussed on streaming. DVBViewer and the Media Server will be able to handle streaming sources as channels in the channel list. Several network protocols carrying a transport stream or MP3/AAC audio stream are supported. In other words: Internet TV and Radio are integrated as a new virtual tuner type that enables to handle the channels like DVB channels, which means, they can be added to the favourites list, recorded, shown as PiP etc. A selection of other enhancements:

  • The iOS web interface of the DVBViewer Media Server can also be used on Android mobile devices. It's still under construction, but already usable.
  • The Sat>IP Server of the Media Server additionally provides HTTP output and supports displaying a remote CAM menu in DVBViewer.
  • Increased maximum number of simultaneous live streaming clients (now 10 for the Live Streaming Server and Sat>IP Server each). Please contact bhackbart@cmuv.de if you need a licence for professional purpose that supports more than 10 live streaming clients at the same time.
  • DVBViewer 6.0 allows to configure the main window appearance in a more flexible way and supports a frameless style.

Please note that the DVBViewer Media Server will not support the out-dated Unicast DVB Server anymore, since its functionality is fully covered by the RTSP/Sat>IP server. If the Unicast DVB Server is essential for some reason please stay with version 1.33.2 beta.

Answers to questions that you may want to ask:

  • Why do I need a DVBViewer licence for the DVBViewer Media Server? I want to use another media player.

The DVBViewer Media Server requires suitable facilities for maintenance, monitoring and trouble-shooting. DVBViewer Pro and powerful tools like TransEdit and TSPlayer, that are included in the DVBViewer licence, are tailored for this task.

We have considered to offer a stand-alone package containing the Media Server plus tools “outsourced” from the DVBViewer environment (e.g. a channel list editor). However, this would cause a lot of extra work, yielding the same or an even higher price than for the DVBViewer & Media Server combo without any advantage for users. Therefore we have decided to keep the Media Server as DVBViewer add-on.

  • Can I still use Recording Service 1.33.2 for free?

Yes. Recording Service versions earlier than the DVBViewer Media Server 2.0 will remain free of charge, which means, they will not require an additional licence besides a DVBViewer licence. Recording Service 1.33.2 will still be available for some time in the “Older Versions” section of the download area.

  • Can I use the new DVBViewer Pro 6.0 in combination with the last free Recording Service version 1.33.2?

You can, in the sense of “it will not be disabled or prohibited”. However, there is already one major drawback. Recording Service 1.33.2 and earlier will regard Internet TV / Radio channels stored by DVBViewer 6.0 in a shared channel list as unknown objects and delete them. Since the incompatibilities will increase in future, we strongly recommend to also stay with DVBViewer Pro 5.6.4 if you want to stay with Recording Service 1.33.2.

  • Does the licence allow to use the DVBViewer Media Server on more than one PC?

We tolerate it under certain conditions, as for the DVBViewer. Please read more about it here (point 3.)

  • Will updates for the DVBViewer Media Server be free of charge?

Basically yes. Currently there are no plans to deviate from our line. However, things must be viewed realistically. Updates are limited to the lifespan of the product, of course. This applies to the Media Server and DVBViewer. Furthermore we cannot exclude that we may come to a point where an update fee for future major releases becomes inevitable in order to enable further development. If it comes to that we will inform about it early in the forum.

However, looking at the past suggests that this will not happen in the foreseeable future. Though there were always people predicting that DVBViewer will be dead and gone soon, we have managed to continue development and provide free updates and tools for 14 years by now. We want to go on with it as long as circumstances allow us to do so.

  • Like 1

Share this post


Link to post
Guest
This topic is now closed to further replies.

  • Similar Content

    • jookee
      By jookee
      Über den Media Server 2.1.1 via Upnp fehlen plötzlich einzelne Verzeichnisse bzw. es werden nicht alle Verzeichnisse angezeigt. Woran kann es liegen?
    • Falo
      By Falo
      Hallo, nach dem Einspielen der Windows Update KB4033417 auf einen Windows Server 2k12r2 mit DVBViewer Pro 6.0.4.0 + Media Server 2.0.4.0 gibt es Probleme beim Media Server Zugriff.
      (Microsoft .NET Framework 4.7.1-Sprachpakete für Windows 8.1 und Windows Server 2012 R2 für x64 (KB4033417))
       
      Der Zugriff auf den Webserver ist nicht mehr möglich. Dienst und Server-Neustart bringen keine Verbesserung erst eine Deinstallation des Updates stellt den Zugriff wieder her.

       
    • bounguine
      By bounguine
      There's a question I cannot answer myself.
      I have two physical servers in one subnet with recording services installed (ports are changed to be different) .
       
      DVBViewer on server 1 sees channels from local cards without recording service and channels from recording service on server 1 and 2.
      DVBViewer on server 2 sees channels from local cards without recording service and channels from recording service on server 2. But not from recording service on server 1.
      Logs show no tries of connection.
       
      Why?
    • Nucleorion
      By Nucleorion
      Hi,
      I change to windows 10, and now DVBViewer Recording Service icon not appear where clock area. They work fine but I don't know if is record or not. Is possible fix it?
    • Indy06
      By Indy06
      Hallo!
       
      Mir ist etwas aufgefallen, was möglicherweise gar nicht generell etwas mit dem DMS zu tun hat, aber ich möchte es trotzdem einmal an dieser Stelle beschreiben. Ich betreibe einen HTPC (hostname: htpc) mit Windows 7 und DMS in einem Heimnetz mit Fritz!Box 7362 SL an einem 1&1 (also Telekom) 50 MBit/s VDSL-Anschluss. Die IP-Adressen vergibt die Fritz!Box per DHCP für alle Stationen automatisch und zwar sowohl IPv4- als auch IPv6-Adressen. Die aktuellen IP-Adressen für den htpc kann ich z.B. via "nslookup htpc" herausbekommen. Dabei sehe ich dann auch, dass der HTPC sowohl eine IPv4- als auch eine IPv6-Adresse zugewiesen bekommen hat. Alle Instanzen von DVBViewer, DVBViewer Controller für Android oder auch der KODI-Erweiterung für den DMS im Heimnetz habe ich mit der Server-URL htpc:8089 konfiguriert und das funktioniert auch alles einwandfrei und schnell.
       
      Wenn ich an einem PC mit Windows 10 und Firefox mit http://htpc:8089 das Webinterface des DMS aufrufe, dann dauert es beim ersten Zugriff unverhältnismäßig lange (min. 30 sec) bis das Webinterface tatsächlich lädt. Rufe ich das Webinterface dagegen mit http://<IPv4-Adresse>:8089 auf, funktioniert auch der erste Zugriff immer rasend schnell und das Webinterface lädt quasi sofort. Meine Vermutung wäre jetzt, dass bei http://htpc:8089 der HTPC via IPv6 angesprochen wird, während im anderen Fall der Zugriff via IPv4 erfolgt. Wie könnte es dann sein, dass der Zugriff via IPv6 so langsam ist? In Ermangelung anderer Dienste auf dem HTPC kann ich jetzt nicht sagen, ob der Unterschied in meinem Heimnetz zwischen IPv4 und IPv6 immer so ist, oder nur beim DMS.
       
      Nicht, dass es wirklich wichtig wäre, aber es wäre einfach interessant herauszufinden, warum das so ist und ob z.B. Windows 10 schon standardmäßig IPv6 verwendet?
       
      Gruß,
      Indy
       
       
       
       
       
       
       
       
×