Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[DarkPenguin]

So,

It likes to crash on device settings. Not always. Not sure if there is commonality to the crashes.

The list of devices is largely insane and the options make 0 sense.

Theaterview likes to be somewhat unresponsive at times. Not sure what is happening when it occurs. It mostly doesn't do this. Just every now and again. I did just import 9000 files on a mobile 2.5" HD that is about as big a slug as there is. So, you know, maybe that has something to do with it.

Takes like 30 seconds to close.

Otherwise it all works and sounds great.

As an aside if you have a DAC running on the edge or, rather just over the edge, of the USB power output putting it on a USB 3 port will make life much better as it is like 900mA instead of 500mA.

[bob]

So,

It likes to crash on device settings. Not always. Not sure if there is commonality to the crashes.

The list of devices is largely insane and the options make 0 sense.

Theaterview likes to be somewhat unresponsive at times. Not sure what is happening when it occurs. It mostly doesn't do this. Just every now and again. I did just import 9000 files on a mobile 2.5" HD that is about as big a slug as there is. So, you know, maybe that has something to do with it.

Takes like 30 seconds to close.

Otherwise it all works and sounds great.

As an aside if you have a DAC running on the edge or, rather just over the edge, of the USB power output putting it on a USB 3 port will make life much better as it is like 900mA instead of 500mA.

Device settings crash is fixed the most recent build.

The device list is the list of hints that ALSA provides to describe the capabilities and device location of the device.

Theaterview is really dependent on the capabilities of the video card and will also be sluggish if MC is doing background processing (i.e. thumbnailing).

When MC closes it does proper notifications to all DLNA devices that it's going away. If you have a lot of devices or one that's stuck in a foobar state it will take longer.

[DarkPenguin]

Device settings crash is fixed the most recent build.

The device list is the list of hints that ALSA provides to describe the capabilities and device location of the device.

Theaterview is really dependent on the capabilities of the video card and will also be sluggish if MC is doing background processing (i.e. thumbnailing).

When MC closes it does proper notifications to all DLNA devices that it's going away. If you have a lot of devices or one that's stuck in a foobar state it will take longer.

Thanks, Bob.

I'll do an apt-get update.

As to the closing delay I had no servers running. I think. I've solved the problem by just not closing the app.

[Awesome Donkey]

When MC closes it does proper notifications to all DLNA devices that it's going away. If you have a lot of devices or one that's stuck in a foobar state it will take longer.

Interesting, so that explains why MC is slow to close when Media Network is enabled. Once disabled, it closes pretty quickly. I suppose nothing can be done about speeding that process up?

[bob]

Interesting, so that explains why MC is slow to close when Media Network is enabled. Once disabled, it closes pretty quickly. I suppose nothing can be done about speeding that process up?

A proper shutdown requires unsubscribing from all events and sending bye-byes to all services seen. The protocol specifies multiple notifications and a delay between packets sent because it's UDP which is not guaranteed delivery. When you add up the number of services and events and the duplicated notifications you end up with a lot of time. We did look at shortening it but I think it's down about as far as it can get and still be within the specifications of the protocol.

[Awesome Donkey]

Thought so, I VERY rarely used media network from macOS or Linux (since I use Windows 95% of the time with JRemote) so I just disabled there for Arch Linux, Ubuntu and macOS (there was no issue with macOS MC closing, but I rarely used it).

[globetrotters1]

wouldn't it be better to show a little window with "please wait..." so that the poor guy in front of the monitor doesn't think it might be frozen again...?

today I waited for more than 10 minutes until the program closed...

[bob]

wouldn't it be better to show a little window with "please wait..." so that the poor guy in front of the monitor doesn't think it might be frozen again...?

today I waited for more than 10 minutes until the program closed...

That sounds like a good idea.
10 minutes is way too long though. I wouldn't think that was possible even with a misbehaving DLNA device on your network.
If you can consistently reproduce that, a log would be nice.