VirtualTV Plugin and Next Gen

[Mookdog 90]

Hey @quickmic

 

I have had the virtualtv plugin on my emby for almost a year and it works great in Emby for android. It works pretty darn good in Next Gen for Kodi. My question is is there a setting I have to setup to get the guide info up on Next gen ? Channels work but no info for EPG.

 

Thanks brother hope all is well

Mook

[quickmic 1486]

I need detailed info about virtual TV settings. There are several modes. Settings screenshot please.

[pünktchen 1288]

@quickmic The VirtualTV plugin just uses the regular live tv guide of Emby.

@MookdogYou can also export the VirtualTV channels as m3u and the epg as xmltv file via a scheduled task to a file share for use in Kodi's IPTV pvr addon.
Or you can even access that data directly in the Kodi pvr addon via some http api. See the link in the export settings of the VirtualTV plugin.

[quickmic 1486]

1 minute ago, pünktchen said:

@quickmic The VirtualTV plugin just uses the regular live tv guide of Emby.

Yep, last time I tested it worked perfect. I'll perform another test.

[quickmic 1486]

@pünktchen

Is VirtualTV compatible with Emby server version 4.8.X (beta).

 

[pünktchen 1288]

Yes.
The version for Emby 4.7.x

Edited August 26, 2022 by pünktchen

[Mookdog 90]

Hey guys

Here is my settings in the plugin export section

 

[pünktchen 1288]

Okay, but what is it that you want to say?

[Mookdog 90]

Just now, pünktchen said:

Okay, but what is it that you want to say?

I need the guide to show up in Next Gen. When I click the api portion of the export section it comes up with an error opening openapi. I mean it works great in Android tv app but with Next Gen channels will play but the guide doesnt show me whats on

 

Mook

 

[quickmic 1486]

1 hour ago, pünktchen said:

Yes.
The version for Emby 4.7.x

Also with ffmpeg version 5.1 (native installed) but seems Emby uses 4.5.0

 

2022-08-26 10:59:46.064 Error Server: Error processing request
	*** Error Report ***
	Version: 4.8.0.8
	Command line: /opt/emby/EmbyServer.dll
	Operating system: Linux version 5.15.35-1-pve (build@proxmox) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP PVE 5.15.35-2 (Thu
	Framework: .NET 6.0.8
	OS/Process: x64/x64
	Runtime: usr/share/dotnet/shared/Microsoft.NETCore.App/6.0.8/System.Private.CoreLib.dll
	Processor count: 24
	Data path: /opt/programdata
	Application path: /opt/emby
	Emby.Server.MediaEncoding.Unified.Ffmpeg.FfRunException: Emby.Server.MediaEncoding.Unified.Ffmpeg.FfRunException: Error starting ffmpeg
	10:59:45.929 ffmpeg version 4.5.0-emby_2021_11_16 Copyright (c) 2000-2021 the FFmpeg developers and softworkz for Emby LLC
	10:59:45.930   built with gcc 8.3.0 (crosstool-NG 1.24.0)
	10:59:45.930 Execution Date: 2022-08-26 10:59:45
	10:59:45.957 Input #0, mpegts, from 'http://127.0.0.1:80/LiveTv/LiveStreamFiles/a8693906575e4ac7b85a2f0f867f5143/stream.ts':
	10:59:45.957   Duration: N/A, start: 1.400000, bitrate: N/A
	10:59:45.957   Program 1 
	10:59:45.957     Metadata:
	10:59:45.957       service_name    : Service01
	10:59:45.957       service_provider: FFmpeg
	10:59:45.957   Stream #0:0[0x100]: Video: h264 (High) ([27][0][0][0] / 0x001B), yuv420p(tv, bt709, progressive), 1280x720 [SAR 1:1 DAR 16:9], Level 31, 23.98 fps, 23.98 tbr, 90k tbn, Start-Time 1.483s
	10:59:45.958   Stream #0:1[0x101](und): Audio: aac (LC) ([15][0][0][0] / 0x000F), 48000 Hz, stereo, fltp, 4 kb/s, Start-Time 1.400s
	10:59:45.975 Stream mapping:
	10:59:45.975   Stream #0:0 -> #0:0 (h264 (native) -> vp8 (libvpx))
	10:59:45.975   Stream #0:1 -> #0:1 (aac (native) -> vorbis (libvorbis))
	10:59:45.975 Press [q] to stop, [?] for help
	10:59:46.002 [libvorbis @ 0x248ad80] encoder setup failed
	10:59:46.002 Error initializing output stream 0:1 -- Error while opening encoder for output stream #0:1 - maybe incorrect parameters such as bit_rate, rate, width or height
	10:59:46.008 Conversion failed!
	10:59:46.008
	   at Emby.Server.MediaEncoding.Api.BaseStreamingService.StartFfMpeg(StreamState state, String outputPath, CancellationToken cancellationToken, Boolean acquireResources)
	   at Emby.Server.MediaEncoding.Api.Progressive.BaseProgressiveStreamingService.GetStreamResult(StreamState state, IDictionary`2 responseHeaders, Boolean isHeadRequest, CancellationToken cancellationToken)
	   at Emby.Server.MediaEncoding.Api.Progressive.BaseProgressiveStreamingService.ProcessRequest(StreamRequest request, Boolean isHeadRequest)
	   at Emby.Server.Implementations.Services.ServiceController.GetTaskResult(Task task)
	   at Emby.Server.Implementations.Services.ServiceHandler.ProcessRequestAsync(HttpListenerHost appHost, IRequest httpReq, IResponse httpRes, RestPath restPath, String responseContentType, CancellationToken cancellationToken)
	   at Emby.Server.Implementations.HttpServer.HttpListenerHost.RequestHandler(IRequest httpReq, ReadOnlyMemory`1 urlString, ReadOnlyMemory`1 localPath, CancellationToken cancellationToken)
	Source: Emby.Server.MediaEncoding
	TargetSite: Void MoveNext()

 

 

I'll check what's the problem. Maybe my "very custom" Emby server has an issue.

 

EDIT:

Upgraded to ffmpeg Emby version 5.1. Still same issue. Continue review... Most likly not a VirtualTV issue!! I think problem on my installation.

Edited August 26, 2022 by quickmic

[pünktchen 1288]

2 hours ago, Mookdog said:

When I click the api portion of the export section it comes up with an error opening openapi.

You mean the CORS error of the Swagger API? Just replace "localhost" or your IP with "127.0.0.1" in the URL.

[pünktchen 1288]

To simplify things, just use this and replace the curly braces with your own values

Channels:

http://{ip or hostname}:{port}/emby/VirtualTV/Channels?StreamType=EmbyNextGen&RealLiveTv=true

EPG:

http://{ip or hostname}:{port}/emby/VirtualTV/Guide?StreamType=EmbyNextGen&RealLiveTv=true

 

[quickmic 1486]

2 hours ago, pünktchen said:

To simplify things, just use this and replace the curly braces with your own values

Channels:

http://{ip or hostname}:{port}/emby/VirtualTV/Channels?StreamType=EmbyNextGen&RealLiveTv=true

EPG:

http://{ip or hostname}:{port}/emby/VirtualTV/Guide?StreamType=EmbyNextGen&RealLiveTv=true

 

Doesn't even work via Emby's WebUI, but I'll come back to you if I can confirm it's a VirtualTV plugin issue what I currently not expecting. I'll repeat the test it on my second Emby server with regular Windows installation.

[Mookdog 90]

On 8/26/2022 at 10:19 AM, quickmic said:

Doesn't even work via Emby's WebUI, but I'll come back to you if I can confirm it's a VirtualTV plugin issue what I currently not expecting. I'll repeat the test it on my second Emby server with regular Windows installation.

Hey @quickmicHave u figured this out yet ? Still cant get the guide to show on mine. No biggie atm I was just wondering

 

Mook

[quickmic 1486]

Not yet, I was quite busy last days.

[quickmic 1486]

Now I've checked EPG for VirtualTV. Works perfect.

Check if EPG is available in Emby's WebUI. If not there, it's an issue with your VirtualTV config.

Edited August 30, 2022 by quickmic

[JoyriderLP 1]

Gibt es auch einen direkt link zu der xml datei

anstatt

Quote

EPG:

http://{ip or hostname}:{port}/emby/VirtualTV/Guide?StreamType=EmbyNextGen&RealLiveTv=true

weil ich bräuchte für meinen Enigma2 Receiver einen direkten link zur xml datei, damit ich das EPG auch am Receiver nutzen kann

[quickmic 1486]

31 minutes ago, JoyriderLP said:

Gibt es auch einen direkt link zu der xml datei

anstatt

weil ich bräuchte für meinen Enigma2 Receiver einen direkten link zur xml datei, damit ich das EPG auch am Receiver nutzen kann

Bin mir nicht sicher was du machen willst.

Das plugin holt die Daten IMMER vom Emby server. Wenn du also dem Emby server deine EPG von Enigma "beibringst" bzw einliest (keine Ahnung ob dein XML kompatibel ist), kann das plugin die EPG Daten vom Server holen. Ich hab das mit meinem Neutrino Receiver so gemacht, aber da mussten die Daten geparst werden damit Emby server die lesen kann.

Ansonsten kannst du versuchen das plugin aussen vor zu lassen, und simple ip TV direkt zu konfigurieren. Das hatte ich frueher so gemacht als der Import vom Emby server noch nicht verfuegbar war.

Edited December 31, 2022 by quickmic

[pünktchen 1288]

2 hours ago, JoyriderLP said:

Gibt es auch einen direkt link zu der xml datei

anstatt

weil ich bräuchte für meinen Enigma2 Receiver einen direkten link zur xml datei, damit ich das EPG auch am Receiver nutzen kann

Willst du VirtualTV auf dem Enigma2 Receiver nutzen oder was meinst du?

[JoyriderLP 1]

ich möchte einen direkt link zur xml datei wie als beispiel:
 

{ip or hostname}:{port}/emby/VirtualTV/guide.xml

 

das man die direkt laden kann ohne indirekte weiterleitung

 

Wie ich es in Enigma2 importiere und das EPG den sender zuweise das weiss ich aber ich brauche einen direkt link zur Datei ohne weiterleitung

 

z.B.: bei ErsatzTV ist es http://{ip or hostname}:{port}/iptv/xmltv.xml

wäre schön wenn es bei VirtualTV auch irgendwie gehen würde als Direktlink und nicht als versteckte weiterleitung wie es im moment ist

Edited December 31, 2022 by JoyriderLP

[pünktchen 1288]

Das ist weder eine indirekte, noch eine versteckte Weiterleitung. Es ist schon ein Direktlink! Ich habe auch verschiedenste IPTV Apps damit getestet und keiner hatte Probleme.
Wenn das EPG-Import-Plugin bei Enigma unbedingt eine Dateiendung in der URL benötigt um die xml herunterzuladen, solltest du eigentlich dessen Entwickler anschreiben.
Naja egal. Ich schau mal, ob ich was machen kann.

[pünktchen 1288]

@JoyriderLP 
Probier mal:  

Wie gewünscht:

http://{ip or hostname}:{port}/emby/VirtualTV/channels.m3u
http://{ip or hostname}:{port}/emby/VirtualTV/guide.xml

Edited July 29, 2023 by pünktchen
removed attachement

[pünktchen 1288]

@JoyriderLP Feedback?