Trying to run armhf on arm64 - crash on uknown codec

[GreatLord 1]

Hi 

I did think it was a dietpi problem only I try on rasberry pi and pine64

 

with armhf linux dist on pi and pine64 arm64 linux dist

 

It crash or frezz it when it come to unkown codec.

 

no crash log or anything.

 

any idea

 

here is the log

 

ug 17 16:27:22 pine64 emby-server[17010]: Unsupported codec with id 98304 for input stream 3

Aug 17 16:27:22 pine64 emby-server[17010]: Unsupported codec with id 98304 for input stream 4

Aug 17 16:27:22 pine64 emby-server[17010]: Unsupported codec with id 98304 for input stream 5

Aug 17 16:27:22 pine64 emby-server[17010]: Unsupported codec with id 98304 for input stream 6

Aug 17 16:27:22 pine64 emby-server[17010]: Unsupported codec with id 98304 for input stream 7

Aug 17 16:27:22 pine64 emby-server[17010]: Unsupported codec with id 98304 for input stream 8

Aug 17 16:27:22 pine64 emby-server[17010]: Unsupported codec with id 98304 for input stream 9

Aug 17 16:27:22 pine64 emby-server[17010]: Unsupported codec with id 98304 for input stream 10

Aug 17 16:27:22 pine64 emby-server[17010]: Unsupported codec with id 98304 for input stream 11

Aug 17 16:27:22 pine64 emby-server[17010]: Unsupported codec with id 98304 for input stream 12

Aug 17 16:27:22 pine64 emby-server[17010]: Unsupported codec with id 98304 for input stream 13

Aug 17 16:27:22 pine64 emby-server[17010]: Unsupported codec with id 98304 for input stream 14

Aug 17 16:27:22 pine64 emby-server[17010]: Unsupported codec with id 98304 for input stream 15

[Luke 42077]

Since you're running this on arm64 which we haven't tested, I'm afraid that right now I don't know the answer to this. This is something we just haven't tried before. The more information you can supply though, the better. Thanks.

[GreatLord 1]

The log does not give me any clude either what it can be.

it seam it is random it frezz on unkown codecc. 

some times it work (after exame the log close) and after while it freze on unknown codec.

[GreatLord 1]

I did found a workaround the issue. No freze any more on unkown codecc

 

 

What I change

 

1. Settings - Automatic Updates to OFF

2. DLNA - Enable DLNA server to OFF

3. DLNA - Blast alive messages to OFF

 

it solv the freze problem for unkown codecc.

but I do not known which change solv it.

Edited August 17, 2018 by GreatLord

[Kiina 4]

 

I did found a workaround the issue. No freze any more on unkown codecc

 

 

What I change

 

1. Settings - Automatic Updates to OFF

2. DLNA - Enable DLNA server to OFF

3. DLNA - Blast alive messages to OFF

 

it solv the freze problem for unkown codecc.

but I do not known which change solv it.

 

 

Yeah, DLNA seem painfully broken. I had crashes after like 20 minutes, after reinstall only once a day but after disabling DLNA it seems everything is kinda fine. No logs no nothing. And as it's impossible to build the project now there isn't anything you can really do to debug it

[GreatLord 1]

I try avoid using DLNA so I do not care if it off or not. 

I got PS4, xbox one and LG Smart TV and I runing the emby client on my lg tv.

after shut dlna server off no issue at all. 

the server have run now 24hours without any crash at all.

 

So it is something with their DLNA server I got issue with. 

any way I do not care about DLNA server. 

Least I got something that work 100% as I wanted. 

But I wish some time that Pine64 memory card was faster to write data to. 

it is the slowers part when you doing the scan of media. 

 

It is frist time I got a stable media server that does not crash or have issue with subtile and dlna profiles. 

 

[Luke 42077]

Thanks for the feedback.

[Luke 42077]

@@GreatLord, what is your install process on DietPi?

[Luke 42077]

Emby Server for Arm64 is now available !

 

https://emby.media/community/index.php?/topic/65476-emby-server-for-arm64-now-available/

 

Thanks.