Luke 37094 Posted September 11, 2018 Author Share Posted September 11, 2018 No, you cannot go back and forth between beta and stable. What you can do is report your issue so that it can be looked at. Thanks. Link to comment Share on other sites More sharing options...
sectune 9 Posted September 12, 2018 Share Posted September 12, 2018 (edited) Dear Luke, I am experiencing playback (to be more precise transcoding issues) since .38 beta. Problem only persists if not on DirectPlay and only (as far as I could test) with the WMAV codec. Please find below attached logs including mediainfo of the video file. I am on the actual latest beta as of today (.40). I cleared the logs, navigated to the video in question and tried playing (via transcoding). Issue persists not only on chrome on windows but also in the emby app on android. WindowsStore emby theatre app played this file fine (as this was DirectPlaying). And yes, I am sure that this file played perfectly fine (while transcoding) before some betas back My guess is on the last line of the fftranscode log: "Decoder (codec wmav2) not found for input stream" Hope this helps to find the issue and please let me know if you need any more details! Thank you for all your hard work, you are awesome! EmbyServer.txt fftranscode.txt MediaInfo.txt Edited September 12, 2018 by sectune Link to comment Share on other sites More sharing options...
Luke 37094 Posted September 12, 2018 Author Share Posted September 12, 2018 Thanks we'll take a look. Link to comment Share on other sites More sharing options...
Luke 37094 Posted September 14, 2018 Author Share Posted September 14, 2018 Dear Luke, I am experiencing playback (to be more precise transcoding issues) since .38 beta. Problem only persists if not on DirectPlay and only (as far as I could test) with the WMAV codec. Please find below attached logs including mediainfo of the video file. I am on the actual latest beta as of today (.40). I cleared the logs, navigated to the video in question and tried playing (via transcoding). Issue persists not only on chrome on windows but also in the emby app on android. WindowsStore emby theatre app played this file fine (as this was DirectPlaying). And yes, I am sure that this file played perfectly fine (while transcoding) before some betas back My guess is on the last line of the fftranscode log: "Decoder (codec wmav2) not found for input stream" Hope this helps to find the issue and please let me know if you need any more details! Thank you for all your hard work, you are awesome! This should be resolved in the latest beta package, thanks. 1 Link to comment Share on other sites More sharing options...
sectune 9 Posted September 22, 2018 Share Posted September 22, 2018 (edited) Dear Luke, since the .44 or so beta there is no option anymore under library > display > group movies into collections. Is it on purpose and will this option be coming back? Didn't find it anywhere else in the newest versions. Thanks! Edited September 22, 2018 by sectune Link to comment Share on other sites More sharing options...
wangbo 6 Posted September 22, 2018 Share Posted September 22, 2018 beta 3.6.0.46 Installed and after a day have to stop and restart emby server via QNAP app installer to be able access my emby server. Think we had this once before with a earlier beta version and may have returned again. Link to comment Share on other sites More sharing options...
Luke 37094 Posted September 23, 2018 Author Share Posted September 23, 2018 Dear Luke, since the .44 or so beta there is no option anymore under library > display > group movies into collections. Is it on purpose and will this option be coming back? Didn't find it anywhere else in the newest versions. Thanks! Hi @@sectune. The answers are in the the testing area of the community: https://emby.media/community/index.php?/forum/102-emby-server/ If you are running beta releases then you will want to follow that section of the community. Thanks. Link to comment Share on other sites More sharing options...
Luke 37094 Posted September 23, 2018 Author Share Posted September 23, 2018 beta 3.6.0.46 Installed and after a day have to stop and restart emby server via QNAP app installer to be able access my emby server. Think we had this once before with a earlier beta version and may have returned again. @@wangbo, let's look at an example. Please attach the information requested in how to report a problem. thanks. Link to comment Share on other sites More sharing options...
wangbo 6 Posted September 26, 2018 Share Posted September 26, 2018 tried it again and now can't repeat it so guessing my server had a hick up or something but am getting ready to try the 3.6.0.49 beta . Will see if it does it again. If it does will try to capture screens etc for you. Link to comment Share on other sites More sharing options...
Luke 37094 Posted September 27, 2018 Author Share Posted September 27, 2018 Thanks for the update. Link to comment Share on other sites More sharing options...
wangbo 6 Posted September 27, 2018 Share Posted September 27, 2018 Im using the qpkg 3.6.0.49 Beta Emby and after a short period of time my server shuts down on its on and this is the unhandled log from that same problem again was using my ipad when it did it this time but earlier it did it while i was using my desktop ( Linux mint 18.3) if i enter my admin dashboard in QNAP then using the icon in the App store to restart server it restarts again until the next time it does a uncommanded shut down after a short period of time. I am unable to restart it using the web address for the Emby connect. So suspect something with QNAP but the firmware has not been updated in some time as no new updates and im using the stable firmware. Any more info required let me know and will try to provide. System.IO.IOException: Unable to read data from the transport connection: Connection reset by peer.Source: System.Net.SocketsTargetSite: Void ThrowException(System.Net.Sockets.SocketError)at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error)at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.GetResult(Int16 token)at System.Net.FixedSizeReader.ReadPacketAsync(Stream transport, AsyncProtocolRequest request)at System.Net.Security.SslState.ThrowIfExceptional()at System.Net.Security.SslState.CheckThrow(Boolean authSuccessCheck, Boolean shutdownCheck)at System.Net.Security.SslState.CheckOldKeyDecryptedData(Memory`1 buffer)at System.Net.Security.SslState.HandleQueuedCallback(Object& queuedStateRequest)at System.Net.Security.SslState.FinishHandshakeRead(Int32 newState)at System.Net.Security.SslState.FinishHandshake(Exception e, AsyncProtocolRequest asyncRequest)at System.Net.Security.SslState.RehandshakeCompleteCallback(IAsyncResult result)at System.Net.LazyAsyncResult.Complete(IntPtr userToken)at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr userToken)at System.Net.AsyncProtocolRequest.CompleteUserWithError(Exception e)at System.Net.FixedSizeReader.ReadPacketAsync(Stream transport, AsyncProtocolRequest request)at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)--- End of stack trace from previous location where exception was thrown ---at System.Threading.ThreadPoolWorkQueue.Dispatch()InnerException: System.Net.Sockets.SocketException: Connection reset by peerSource:TargetSite: 62° Link to comment Share on other sites More sharing options...
Luke 37094 Posted September 27, 2018 Author Share Posted September 27, 2018 Hi there @@wangbo, please attach the complete emby server log, thanks. Link to comment Share on other sites More sharing options...
wangbo 6 Posted September 27, 2018 Share Posted September 27, 2018 The Log I gave you is the log generated when it shut down named unhandeled for the server log generated after restarting the server would prefer to send to you private as it has my ip listed in several places throughout and have no wish to give invitation to attackers just let me know best way to accomplish sending to you privately. Thanks. Link to comment Share on other sites More sharing options...
wangbo 6 Posted September 27, 2018 Share Posted September 27, 2018 Also I did not edit that log that is all there was. Link to comment Share on other sites More sharing options...
Luke 37094 Posted September 28, 2018 Author Share Posted September 28, 2018 Ok yes you can send it to me privately. Thanks. Link to comment Share on other sites More sharing options...
wangbo 6 Posted September 28, 2018 Share Posted September 28, 2018 tried to pm it to you don't know if it went through or not as no indication if it did let me know. if nothing else as admin you have my private email contact me via and will send that way Link to comment Share on other sites More sharing options...
Luke 37094 Posted September 28, 2018 Author Share Posted September 28, 2018 I don't have any PM's from you. How did you try and do that? Link to comment Share on other sites More sharing options...
wangbo 6 Posted September 28, 2018 Share Posted September 28, 2018 By logging in to my forum acct and clicked on you name/avatar and tried to leave you a message or am i doing it wrong or is there another way? Link to comment Share on other sites More sharing options...
Luke 37094 Posted September 28, 2018 Author Share Posted September 28, 2018 Im using the qpkg 3.6.0.49 Beta Emby and after a short period of time my server shuts down on its on and this is the unhandled log from that same problem again was using my ipad when it did it this time but earlier it did it while i was using my desktop ( Linux mint 18.3) if i enter my admin dashboard in QNAP then using the icon in the App store to restart server it restarts again until the next time it does a uncommanded shut down after a short period of time. I am unable to restart it using the web address for the Emby connect. So suspect something with QNAP but the firmware has not been updated in some time as no new updates and im using the stable firmware. Any more info required let me know and will try to provide. System.IO.IOException: Unable to read data from the transport connection: Connection reset by peer. Source: System.Net.Sockets TargetSite: Void ThrowException(System.Net.Sockets.SocketError) at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.ThrowException(SocketError error) at System.Net.Sockets.Socket.AwaitableSocketAsyncEventArgs.GetResult(Int16 token) at System.Net.FixedSizeReader.ReadPacketAsync(Stream transport, AsyncProtocolRequest request) at System.Net.Security.SslState.ThrowIfExceptional() at System.Net.Security.SslState.CheckThrow(Boolean authSuccessCheck, Boolean shutdownCheck) at System.Net.Security.SslState.CheckOldKeyDecryptedData(Memory`1 buffer) at System.Net.Security.SslState.HandleQueuedCallback(Object& queuedStateRequest) at System.Net.Security.SslState.FinishHandshakeRead(Int32 newState) at System.Net.Security.SslState.FinishHandshake(Exception e, AsyncProtocolRequest asyncRequest) at System.Net.Security.SslState.RehandshakeCompleteCallback(IAsyncResult result) at System.Net.LazyAsyncResult.Complete(IntPtr userToken) at System.Net.LazyAsyncResult.ProtectedInvokeCallback(Object result, IntPtr userToken) at System.Net.AsyncProtocolRequest.CompleteUserWithError(Exception e) at System.Net.FixedSizeReader.ReadPacketAsync(Stream transport, AsyncProtocolRequest request) at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) --- End of stack trace from previous location where exception was thrown --- at System.Threading.ThreadPoolWorkQueue.Dispatch() InnerException: System.Net.Sockets.SocketException: Connection reset by peer Source: TargetSite: 62° Hi, the log you provided doesn't contain this error. can you try to find the right one? thanks. Link to comment Share on other sites More sharing options...
wangbo 6 Posted September 28, 2018 Share Posted September 28, 2018 (edited) Did you get the one i sent last night by pm I think the reason before it wouldnt go through was i butted up against the number of character limitation ( i tried cut and paste of the log file into the body of the message when I first tried to PM you) but was able to attach a txt file with the other log as well as screenshot showing what the logs were. Edited September 28, 2018 by wangbo Link to comment Share on other sites More sharing options...
Luke 37094 Posted September 29, 2018 Author Share Posted September 29, 2018 I did, but I don't see the above error inside that log file. Link to comment Share on other sites More sharing options...
wangbo 6 Posted September 29, 2018 Share Posted September 29, 2018 If you look at the screen shot i sent you you will see the second log .txt from the top titled unhandled it is log file i originally posted which is the one that was the un-commanded shutdown the second log.txt i sent via Pm is the top file in same screenshot after I restarted the server you will notice there are a couple of unhandled logs and all of them had the same inside them of what i originally posted . What I posted was the entire contents of that file. other than that there isn't anymore i can provide. On a side note QNAP just updated the server firmware to 4.3.5.0713 latest version updated to it and will see if the same still continues to happen if so will send you every one of the log files if you want me to. Could be something peculiar to the NAS firmware. Link to comment Share on other sites More sharing options...
Luke 37094 Posted October 4, 2018 Author Share Posted October 4, 2018 Is this still happening with the new QNAP firmware? Link to comment Share on other sites More sharing options...
wangbo 6 Posted October 4, 2018 Share Posted October 4, 2018 Sorry didn't want to jinx myself by speaking to early with the new firmware it isn't doing it and also upgraded to the 3.6.51 pkg and it is working also have tried different means of accessing ie Iphone, Ipad, Linux, Roku, Windows , Emby Theatre all work without a hiccup so I'm guessing it was something with the previous firmware but as to what I have no idea as I had also checked my logs on the NAS itself and wasn't seeing anything to indicate what the issue was. Other than it indicating that the Emby server had stopped there was nothing else that i could find. The firmware also cleared up another problem but it didn't have anything to do with Emby so no reason to suspect it had anything to do with the problem As up to this recent date have had no more issues with it and everything seems to be working good. Link to comment Share on other sites More sharing options...
Luke 37094 Posted October 4, 2018 Author Share Posted October 4, 2018 Thanks for the feedback ! Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now