Jump to content

External Player stopped working


shawnf

Recommended Posts

Hi

 

In Emby Theater 3.0.10 my external player setup has just stopped working. It was working a few days ago.

(Looks like the latest version has stopped this working as I see that was released on 1 November)

 

I use Power DVD to play all my mkv's and other files.

I have the path setup as..

c:\Program Files (x86)\CyberLink\PowerDVD18\pdvdlp.exe

 

I have {path} in command line arguments.

 

When I use a command prompt it works file with c:\Program Files (x86)\CyberLink\PowerDVD18\pdvdlp.exe {path}

({path} keyed in manually to the path of the file.)

 

What I am actually trying to find, is where does Emby Theater write into a log file the argument it is using to launch the application and file?

It isn't in the Emby Theater log file as there is nothing in there.

 

I have even done a complete search of all files looking for the text "c:\Program Files (x86)\CyberLink\PowerDVD18\pdvdlp.exe" to see if it has written to another place.

Edited by shawnf
Link to comment
Share on other sites

Hi,

 

have a look at "%appdata%\Emby-Theater".

 

You will find a folder logs in it.

 

Also, in config\system.xml you can enable the EnableDebugLevelLogging option, which should give more (maybe too much) information in the log files.

 

Ciao, Alfred

Link to comment
Share on other sites

Hi,

 

have a look at "%appdata%\Emby-Theater".

 

You will find a folder logs in it.

 

Also, in config\system.xml you can enable the EnableDebugLevelLogging option, which should give more (maybe too much) information in the log files.

 

Ciao, Alfred

 

Hi

 

I did find those log files but there isn't much in there just about 15-20 lines.

I tried as suggested by change then EnableDebugLevelLogging from false to true and it didn't produce any more information after a reboot..

Link to comment
Share on other sites

What do you mean by stored m stopped working?

 

Hi Luke

 

sorry, I don't follow your question. 

PowerDVD no longer opens and runs the file I have selected to play since the update on 1 November. It opens powerdvd and that is all it does now.

 

So I can't use emby to watch anything at the moment. I have to navigate and launch the files from file explorer.

Link to comment
Share on other sites

Have you checked your command line arguments configuration?

Yes as I mentioned in the initial e-mail.

It is all exactly the same as it was before the update.

 

I even deleted the record and created a new one.

That was why I was trying to track down a log entry to see what Emby Theater was executing.

Link to comment
Share on other sites

bluejoe247

ya, I am also having an issue with external player

 

I wrote my own perl script, converted it to exe; so my external player (video) is c:\tools\mountdvd.exe, with {path} as a parameter

 

but when I play a movie, .mkv, .mp4, .avi, the player isn't executed.  I have the exe writing debug info to a log file.... log file isn't being written to

 

running manually from command line produces debug info (from exe) into log file.

Link to comment
Share on other sites

Guest asrequested

I'm not sure if this is related, but I was testing using mpv as an external player. It launches and plays, but after a short time, it closes. Looking at the mpv log there are no errors, and playback isn't being closed, it just ends. Which means the stream from the server just goes away. So something funky is going on. Obviously this doesn't happen if I manually play something in mpv.

Link to comment
Share on other sites

bluejoe247

Oh my gosh, so frustrating;  This was working once, but no more;  EMBY premier member, running server on a server, and theater on a w10 desktop;  external player, exe;  {path} as parameter, printing that parameter when player called; 

 

server movie path = M:\Mux (mapped drive)

optional network path M:\Mux (same mapped drive)

 

w10 desktop also has same mapped drive m:\Mux

 

but the {path} parameter is:

 

http://172.21.99.5:8096/emby/Videos/157566/stream.mp4Static=true&mediaSourceId=56c7b69a3c1455f1f754026d4c95dcba&deviceId=Jupiter&api_key=ceffb26d38f6412daa9b48808fd21070

 

I don't understand?

@@bluejoe247

Link to comment
Share on other sites

Hi, what does "not working" mean? What exactly is happening? 

http://172.21.99.5:8096/emby/Videos/157566/stream.mp4Static=true&mediaSourceId=56c7b69a3c1455f1f754026d4c95dcba&deviceId=Jupiter&api_key=ceffb26d38f6412daa9b48808fd21070

If this is getting passed into the external player instead of the direct file path, then it means the machine running Emby Theater does not have direct access to the M: path.

 

I realize you're coming in here frustrated assuming it's an Emby problem, but that's the reason why that would happen.

Link to comment
Share on other sites

I actually just went through this over PM with another user recently who initially swore it was a problem with the software, and then after review, realized they needed to adjust their file sharing.

 

Rather than repeat that whole process I'm happy to add you to that conversation so that you can step through all of the same things.

 

Edit; I went ahead and added you both to the PM. @ fyi

Link to comment
Share on other sites

Hi Luke

 

sorry, I don't follow your question. 

PowerDVD no longer opens and runs the file I have selected to play since the update on 1 November. It opens powerdvd and that is all it does now.

 

So I can't use emby to watch anything at the moment. I have to navigate and launch the files from file explorer.

 

What exactly happens?

Link to comment
Share on other sites

Guest asrequested

I actually just went through this over PM with another user recently who initially swore it was a problem with the software, and then after review, realized they needed to adjust their file sharing.

 

Rather than repeat that whole process I'm happy to add you to that conversation so that you can step through all of the same things.

 

Edit; I went ahead and added you both to the PM. @ fyi

I don't see the PM.

Link to comment
Share on other sites

It just open PowerDVD just like it would if I clicked on a desktop icon.

 

Before it would open and play the selected video.

Still works if I manually type in a command prompt the executable and then the path to a file.

 

I see you have merged a couple of threads.

Where or how do I find what is being passed into the player. I can't see anything in log files.

Link to comment
Share on other sites

I actually just went through this over PM with another user recently who initially swore it was a problem with the software, and then after review, realized they needed to adjust their file sharing.

 

Rather than repeat that whole process I'm happy to add you to that conversation so that you can step through all of the same things.

 

Edit; I went ahead and added you both to the PM. @ fyi

 

Path looks fine for it in emby.

\\mediacenter\d\english\TV Shows\11.22.63 (2016)\Season 01\11.22.63 - S01E01 - The Rabbit Hole.mkv

 

From what I have read on other messages I can't roll back to 3.0.9?

Edited by shawnf
Link to comment
Share on other sites

bluejoe247

Hi, what does "not working" mean? What exactly is happening? 

http://172.21.99.5:8096/emby/Videos/157566/stream.mp4Static=true&mediaSourceId=56c7b69a3c1455f1f754026d4c95dcba&deviceId=Jupiter&api_key=ceffb26d38f6412daa9b48808fd21070

If this is getting passed into the external player instead of the direct file path, then it means the machine running Emby Theater does not have direct access to the M: path.

 

I realize you're coming in here frustrated assuming it's an Emby problem, but that's the reason why that would happen.

 

yeah, sorry about that, i know you try to help a lot of people;

 

from my server:

 

C:\Users\thor>dir "M:\Mux\American Made (2017)\American Made (2017).mp4"
 Volume in drive M is Media
 Volume Serial Number is 0A0C-3467
 
 Directory of M:\Mux\American Made (2017)
 
11/03/2019  07:04 AM    21,970,854,716 American Made (2017).mp4
               1 File(s) 21,970,854,716 bytes
               0 Dir(s)  64,035,825,713,152 bytes free
 
C:\Users\thor>
 
from desktop running et
C:\Users\Havak>dir "M:\Mux\American Made (2017)\American Made (2017).mp4"
 Volume in drive M is Media
 Volume Serial Number is 0A0C-3467
 
 Directory of M:\Mux\American Made (2017)
 
11/03/2019  07:04    21,970,854,716 American Made (2017).mp4
               1 File(s) 21,970,854,716 bytes
               0 Dir(s)  64,035,825,713,152 bytes free
 
C:\Users\Havak>
 
Link to comment
Share on other sites

Path looks fine for it in emby.

\\mediacenter\d\english\TV Shows\11.22.63 (2016)\Season 01\11.22.63 - S01E01 - The Rabbit Hole.mkv

 

From what I have read on other messages I can't roll back to 3.0.9?

 

That's what the user in the PM said as well. Please read through it. Thanks.

Link to comment
Share on other sites

Guest asrequested

Well, I can see what my issue is. It looks like the same as playing an in progress recording. I'll have to test with the beta server.

2019-11-06 18:35:29.613 Info HttpServer: HTTP Response 200 to 10.1.1.13. Time: 1ms. http://10.1.1.15:8096/emby/Users/6a8eb582a4af42d1bcef357a756df9b8
2019-11-06 18:35:29.614 Info App: User policy for Peter. EnablePlaybackRemuxing: True EnableVideoPlaybackTranscoding: True EnableAudioPlaybackTranscoding: True
2019-11-06 18:35:29.614 Info App: RemoteClientBitrateLimit: 3000000, RemoteIp: 10.1.1.13, IsInLocalNetwork: True
2019-11-06 18:35:29.614 Info App: RemoteClientBitrateLimit: 3000000, RemoteIp: 10.1.1.13, IsInLocalNetwork: True
2019-11-06 18:35:29.614 Info App: RemoteClientBitrateLimit: 3000000, RemoteIp: 10.1.1.13, IsInLocalNetwork: True
2019-11-06 18:35:29.614 Info HttpServer: HTTP Response 200 to 10.1.1.13. Time: 3ms. http://10.1.1.15:8096/emby/Items/1046363/PlaybackInfo?UserId=6a8eb582a4af42d1bcef357a756df9b8&StartTimeTicks=0&IsPlayback=false&AutoOpenLiveStream=false&MaxStreamingBitrate=120000000&DirectPlayProtocols=File%2CHttp%2CRtp%2CRtmp%2CRtsp%2CFtp
2019-11-06 18:35:29.623 Info PlaybackReporting - EventMonitorEntryPoint: Removing Old Key from playback_trackers : HTPC-6a8eb582a4af42d1bcef357a756df9b8-1046363
2019-11-06 18:35:29.627 Info HttpServer: HTTP GET http://10.1.1.14:8096/emby/System/ActivityLog/Entries?startIndex=0&limit=4&minDate=2019-10-31T02%3A35%3A29.963Z&hasUserId=false. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.87 Safari/537.36
2019-11-06 18:35:29.627 Info HttpServer: HTTP GET http://10.1.1.14:8096/emby/System/ActivityLog/Entries?startIndex=0&limit=7&minDate=2019-11-06T02%3A35%3A29.963Z&hasUserId=true. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.87 Safari/537.36
2019-11-06 18:35:29.663 Info HttpServer: HTTP Response 200 to 10.1.1.13. Time: 36ms. http://10.1.1.14:8096/emby/System/ActivityLog/Entries?startIndex=0&limit=4&minDate=2019-10-31T02%3A35%3A29.963Z&hasUserId=false
2019-11-06 18:35:29.665 Info HttpServer: HTTP GET http://10.1.1.14:8096/emby/System/ActivityLog/Entries?startIndex=0&limit=7&minDate=2019-11-06T02%3A35%3A30.002Z&hasUserId=true. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.87 Safari/537.36
2019-11-06 18:35:29.665 Info HttpServer: HTTP GET http://10.1.1.14:8096/emby/System/ActivityLog/Entries?startIndex=0&limit=4&minDate=2019-10-31T02%3A35%3A30.002Z&hasUserId=false. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.87 Safari/537.36
2019-11-06 18:35:29.698 Info HttpServer: HTTP Response 200 to 10.1.1.13. Time: 71ms. http://10.1.1.14:8096/emby/System/ActivityLog/Entries?startIndex=0&limit=7&minDate=2019-11-06T02%3A35%3A29.963Z&hasUserId=true
2019-11-06 18:35:29.736 Info HttpServer: HTTP Response 200 to 10.1.1.13. Time: 71ms. http://10.1.1.14:8096/emby/System/ActivityLog/Entries?startIndex=0&limit=4&minDate=2019-10-31T02%3A35%3A30.002Z&hasUserId=false
2019-11-06 18:35:29.783 Info HttpServer: HTTP Response 200 to 10.1.1.13. Time: 117ms. http://10.1.1.14:8096/emby/System/ActivityLog/Entries?startIndex=0&limit=7&minDate=2019-11-06T02%3A35%3A30.002Z&hasUserId=true
2019-11-06 18:35:45.415 Info HttpServer: HTTP GET http://10.1.1.14:8096/emby/Users/6a8eb582a4af42d1bcef357a756df9b8. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.87 Safari/537.36
2019-11-06 18:35:45.416 Info HttpServer: HTTP Response 200 to 10.1.1.13. Time: 1ms. http://10.1.1.14:8096/emby/Users/6a8eb582a4af42d1bcef357a756df9b8
2019-11-06 18:35:45.491 Debug App: ScheduledTasksWebSocketListener stop transmitting over websocket to [::ffff:10.1.1.13]:55357
2019-11-06 18:35:45.492 Info HttpServer: HTTP GET http://10.1.1.14:8096/emby/System/Logs. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.87 Safari/537.36
2019-11-06 18:35:45.493 Info HttpServer: HTTP GET http://10.1.1.14:8096/emby/System/Configuration. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.87 Safari/537.36
2019-11-06 18:35:45.504 Info HttpServer: HTTP Response 200 to 10.1.1.13. Time: 12ms. http://10.1.1.14:8096/emby/System/Logs
2019-11-06 18:35:45.512 Info HttpServer: HTTP Response 200 to 10.1.1.13. Time: 20ms. http://10.1.1.14:8096/emby/System/Configuration
2019-11-06 18:35:50.713 Info HttpServer: HTTP GET http://10.1.1.14:8096/emby/System/Logs/embyserver.txt. UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.87 Safari/537.36

So it's not related to the issue these guys have.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...