Seekbar Question about TuneBrowser using DIDL-Lite

[storaid]

Hi Tiki,

I have question..

Does TuneBrowser currently use the duration from DIDL-Lite metadata (<res duration=”…”>)?

When I inspected the UPnP traffic, it seemed that TuneBrowser retrieves DIDL metadata returned in GetPositionInfo, and may be using the duration attribute from the <res> element. It’s right?

Denon support responded to my inquiry and stated the following:

The seekbar should be rely on AVTransport values such as TrackDuration and RelTime / AbsTime.
DIDL metadata should not be used for seekbar calculation, because DIDL duration is only descriptive metadata and may not match the renderer’s actual playback behavior.

This matches the UPnP AV, which classify DIDL <res> attributes (including duration) as optional descriptive metadata, while playback state and timeline information must come from AVTransport.

https://upnp.org/specs/av/UPnP-av-ContentDirectory-v1-Service.pdf

Page 9, res is not required, but multiple values is valid.

[Tiki]

Hello.

Does TuneBrowser currently use the duration from DIDL-Lite metadata (<res duration=”…”>)?

Yes, TuneBrowser is using it from AVTransport event and GetPositionInfo SOAP command.

I found from your comment that res is not required. However, TuneBrowser requires DIDL res information when importing unknown musics. And you know, duration is a static information of music file, so it is stored in database. Elapsed time like RelTime is a dynamic information and it is checked and updated each time during playback. As app for managing music files in a database, these are different nature.

[storaid]

Hi Tiki,

Thank you for your explanation.

Elapsed time like RelTime is a dynamic information and it is checked and updated each time during playback.

Yes, RelTime is dynamic, but TrackDuration is not, right?

Actually, one reason I am concerned about relying on the DIDL-Lite metadata for seekbar duration is that, in practice, the content of DIDL from various vendors is not standardized.

Each device or server can provide very different structures, attributes, or even omit certain metadata fields. For example, the <res duration> attribute is optional and often implemented inconsistently.

Because DIDL is so flexible and open to vendor-specific extensions, using it for playback control (such as the seekbar’s total duration) can sometimes lead to compatibility problems—especially when there are multiple <res> tags or unexpected attribute values.

That’s why I think using TrackDuration from the AVTransport, which is designed to provide the accurate total time of the currently playing track, is more robust and reliable for seekbar control.

Is it possible to use TrackDuration as the total duration of the seekbar?

Thanks..

[Tiki]

Thank you for sharing your thoughts.

I’d like to consider what can I do.

[Tiki]

Hello storaid,

I have tried using TrackDuration in 1817. Please try it when you have time.

Thank you.

[storaid]

Hi,

Thank you for implementing TrackDuration support in TuneBrowser 1817.

I have tested it with both ifi-audio ZenStream (very OLD volumio) and Denon Home Speaker (HEOS).

Previously, due to inconsistent or nested DIDL structures and missing duration metadata, the seekbar was unreliable and often failed.

After updating, the seekbar now works consistently and correctly in my environment.

I appreciate your effort and responsiveness!

Thanks

[Tiki]

Great. Thank you for confirming.

[storaid]

Hi, Tiki

I’ve been testing this for about a week and I think I may have found something worth checking.

For some Japanese DMRs (especially Denon/Marantz), the reported TrackDuration often has small precision errors, which seems to affect their internal EOF detection. As a result, even when playback has actually finished, the device sometimes does not move on to the next track.

This made me wonder:
Does TuneBrowser currently monitor the AVTransport LastChange event?

During testing, I noticed that although the device sometimes fails to advance the track on its own, it does correctly send:

6:15 PM Denon Home 350/urn:upnp-org:serviceId:AVTransport LastChange

<Event xmlns="urn:schemas-upnp-org:metadata-1-0/AVT/"><InstanceID val="0"><TransportState val="STOPPED"/></InstanceID></Event>

in the LastChange event.

So I’m thinking that subscribing to LastChange and using TransportState=STOPPED as a trigger might help handle these cases.

I’m not sure if TuneBrowser already uses this mechanism, so I wanted to ask in case this observation is useful.

Thank you as always for your great work.

[Tiki]

Hi,

TuneBrowser is subscribing events including AVTransport.

Thanks.

[storaid]

Hi, Tiki

Thank you for your reply.

I did notice that even when playback is finished (for example, 251 sec / 251 sec, playback actually stopped), the seek bar remains at the end and the next track does not automatically start.

It seems to be related to the DMR’s internal EOF detection.

For reference:

251 sec / 251 sec
251 sec / 251 sec
251 sec / 251 sec
251 sec / 251 sec
251 sec / 251 sec

I have confirmed in my log that the DMR does send TransportState=STOPPED in LastChange.

Does TuneBrowser’s current event handling trigger next-track/track advance logic on TransportState=STOPPED (from LastChange), or does it only rely on position polling something internal logic?

It looks like in this case, manual intervention is required to go to the next track, so I guess the event may not be used for this scenario.

Thank you very much for your help!

[storaid]

Tested Devices and Results:

ifi-audio Zen Stream (old: v3): Works as expected
Volumio (new): Works as expected
moOde: Works as expected
Holo RED: Works as expected
WiiM Plus (Linkplay): Works as expected
DENON Device: For some tracks, does not move on to the next track (likely due to internal EOF detection caused by TrackDuration’s small precision errors), but does send TransportState=STOPPED in the LastChange event when playback is completed.
Marantz Device: Same behavior as DENON

Thank you for your attention and your great support.

If you need any further details or logs, I’d be happy to provide them.

[Tiki]

Does TuneBrowser’s current event handling trigger next-track/track advance logic on TransportState=STOPPED (from LastChange), or does it only rely on position polling something internal logic?

Event STOPPED is trigger to the next track when device is under control.

You can save a log file by toolbar button of the Log View (This log file contains several files shown in Log View tabs). Please attach this file. I’d like to check it in a few days.

[storaid]

Hello Tiki,

I used Wireshark to analyze TuneBrowser’s UPnP event behavior with different DMR devices.
During testing, I noticed that devices based on upmpdcli (Volumio, moOde, RED OS, etc.) tend to behave more leniently with UPnP event subscriptions — even if the controller does not renew the subscription, these devices often continue sending LastChange events without interruption.

However, when testing with Denon/Marantz devices, I observed a different behavior that seems strictly aligned with the UPnP Eventing specification:

1. Timeout handling
TuneBrowser sends TIMEOUT: Second-360, but Denon/Marantz responds with TIMEOUT: Second-300, which is valid per UPnP specifications.

2. No SUBSCRIBE renewal observed
In Wireshark, I did not see TuneBrowser sending a SUBSCRIBE renewal with the assigned SID before the 300-second timeout returned by the DMR.

3. Subscription expiration
Exactly at 300 seconds, Denon/Marantz stops sending AVTransport LastChange events.
When a track is longer than 300 seconds, TuneBrowser does not receive the final TransportState=STOPPED, which prevents automatic track advance.

Does TuneBrowser currently implement automatic renewal of AVTransport subscriptions based on the TIMEOUT value returned by the DMR (rather than the value sent by TuneBrowser)?

If renewal is already implemented, perhaps Denon’s strict timeout behavior requires a slightly different handling.

Denon/Marantz devices seems like to follow the specification very strictly. Orz

Thank you very much for your excellent work on TuneBrowser!

UPnP Log:

2025/12/31 21:07:41,512: UL43712: T01df8: UPnP_M: USNID_03 is new. Poll description to device: uuid:aedc4ed9-0c85-48c5-8cf8-a7ff09ab5b7d::urn:schemas-upnp-org:device:WANConnectionDevice:2
2025/12/31 21:07:41,512: UL43713: T01df8: UPnP_M: *** Processing USNID_02 by NOTIFY from: 10.1.1.15 : [uuid:aedc4ed9-0c85-48c5-8cf8-a7ff09ab5b7c::urn:schemas-upnp-org:device:WANDevice:2]
2025/12/31 21:07:41,512: UL43714: T01df8: UPnP_M: This is TargetURN: NT: [urn:schemas-upnp-org:device:WANDevice:2]
2025/12/31 21:07:41,512: UL43715: T01df8: UPnP_M: ProcDeviceUSN: USNID_02 STAY ( 1): [IPv4]: FN:[] USN:[uuid:aedc4ed9-0c85-48c5-8cf8-a7ff09ab5b7c::urn:schemas-upnp-org:device:WANDevice:2]
2025/12/31 21:07:41,512: UL43716: T01df8: UPnP_M: USNID_02 is new. Poll description to device: uuid:aedc4ed9-0c85-48c5-8cf8-a7ff09ab5b7c::urn:schemas-upnp-org:device:WANDevice:2
2025/12/31 21:07:41,514: UL43718: T03694: UPnP_M: Poll device to: 10.1.1.15 [http://10.1.1.15:46721/rootDesc.xml]
2025/12/31 21:07:41,528: UL43719: T02774: UPnP_M: Description contains 2 devices.
2025/12/31 21:07:41,528: UL43720: T02774: UPnP_M: - deviceType(URN) is TargetURN: [urn:schemas-upnp-org:device:WANDevice:2]
2025/12/31 21:07:41,528: UL43721: T02774: UPnP_M: Not interested service 1: urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1
2025/12/31 21:07:41,528: UL43722: T02774: UPnP_M: No interested services found.
2025/12/31 21:07:41,528: UL43723: T02774: UPnP_M: - deviceType(URN) is TargetURN: [urn:schemas-upnp-org:device:WANConnectionDevice:2]
2025/12/31 21:07:41,528: UL43724: T02774: UPnP_M: Not interested service 1: urn:schemas-upnp-org:service:WANIPConnection:2
2025/12/31 21:07:41,528: UL43725: T02774: UPnP_M: Not interested service 2: urn:schemas-upnp-org:service:WANIPv6FirewallControl:1
2025/12/31 21:07:41,528: UL43726: T02774: UPnP_M: No interested services found.
2025/12/31 21:07:41,529: UL43727: T02774: UPnP_M: - NOT Target device: 10.1.1.15 [10.1.1.15]
2025/12/31 21:07:41,529: UL43728: T02774: UPnP_M: - DeviceType : [urn:schemas-upnp-org:device:WANConnectionDevice:2]
2025/12/31 21:07:41,529: UL43729: T02774: UPnP_M: - Location : [http://10.1.1.15:46721/rootDesc.xml]
2025/12/31 21:07:41,529: UL43730: T02774: UPnP_M: - USN : [uuid:aedc4ed9-0c85-48c5-8cf8-a7ff09ab5b7b::urn:schemas-upnp-org:device:InternetGatewayDevice:2]
2025/12/31 21:07:41,529: UL43731: T02774: UPnP_M: - USNID : [USNID_04]
2025/12/31 21:07:41,530: UL43733: T02774: UPnP_M: Poll device to: 10.1.1.15 [http://10.1.1.15:46721/rootDesc.xml]
2025/12/31 21:07:41,533: UL43734: T02774: UPnP_M: Description contains 2 devices.
2025/12/31 21:07:41,533: UL43735: T02774: UPnP_M: - deviceType(URN) is TargetURN: [urn:schemas-upnp-org:device:WANDevice:2]
2025/12/31 21:07:41,534: UL43736: T02774: UPnP_M: Not interested service 1: urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1
2025/12/31 21:07:41,534: UL43737: T02774: UPnP_M: No interested services found.
2025/12/31 21:07:41,534: UL43738: T02774: UPnP_M: - deviceType(URN) is TargetURN: [urn:schemas-upnp-org:device:WANConnectionDevice:2]
2025/12/31 21:07:41,534: UL43739: T02774: UPnP_M: Not interested service 1: urn:schemas-upnp-org:service:WANIPConnection:2
2025/12/31 21:07:41,534: UL43740: T02774: UPnP_M: Not interested service 2: urn:schemas-upnp-org:service:WANIPv6FirewallControl:1
2025/12/31 21:07:41,534: UL43741: T02774: UPnP_M: No interested services found.
2025/12/31 21:07:41,534: UL43742: T02774: UPnP_M: - NOT Target device: 10.1.1.15 [10.1.1.15]
2025/12/31 21:07:41,534: UL43743: T02774: UPnP_M: - DeviceType : [urn:schemas-upnp-org:device:WANConnectionDevice:2]
2025/12/31 21:07:41,534: UL43744: T02774: UPnP_M: - Location : [http://10.1.1.15:46721/rootDesc.xml]
2025/12/31 21:07:41,534: UL43745: T02774: UPnP_M: - USN : [uuid:aedc4ed9-0c85-48c5-8cf8-a7ff09ab5b7c::urn:schemas-upnp-org:device:WANDevice:2]
2025/12/31 21:07:41,534: UL43746: T02774: UPnP_M: - USNID : [USNID_02]
2025/12/31 21:07:41,754: UL43747: T01df8: UPnP_M: *** Processing USNID_02 by NOTIFY from: 10.1.1.15 : [uuid:aedc4ed9-0c85-48c5-8cf8-a7ff09ab5b7c::urn:schemas-upnp-org:device:WANDevice:2]
2025/12/31 21:07:41,762: UL43748: T01df8: UPnP_M: This is TargetURN: NT: [urn:schemas-upnp-org:device:WANDevice:2]
2025/12/31 21:07:41,762: UL43749: T01df8: UPnP_M: ProcDeviceUSN: USNID_02 STAY ( 1): [IPv4]: FN:[] USN:[uuid:aedc4ed9-0c85-48c5-8cf8-a7ff09ab5b7c::urn:schemas-upnp-org:device:WANDevice:2]
2025/12/31 21:07:41,762: UL43750: T01df8: UPnP_M: USNID_02 is new. Poll description to device: uuid:aedc4ed9-0c85-48c5-8cf8-a7ff09ab5b7c::urn:schemas-upnp-org:device:WANDevice:2
2025/12/31 21:07:41,762: UL43752: T02774: UPnP_M: Poll device to: 10.1.1.15 [http://10.1.1.15:46721/rootDesc.xml]
2025/12/31 21:07:41,764: UL43753: T01df8: UPnP_M: *** Processing USNID_03 by NOTIFY from: 10.1.1.15 : [uuid:aedc4ed9-0c85-48c5-8cf8-a7ff09ab5b7d::urn:schemas-upnp-org:device:WANConnectionDevice:2]
2025/12/31 21:07:41,764: UL43754: T01df8: UPnP_M: This is TargetURN: NT: [urn:schemas-upnp-org:device:WANConnectionDevice:2]
2025/12/31 21:07:41,764: UL43755: T01df8: UPnP_M: ProcDeviceUSN: USNID_03 STAY ( 1): [IPv4]: FN:[] USN:[uuid:aedc4ed9-0c85-48c5-8cf8-a7ff09ab5b7d::urn:schemas-upnp-org:device:WANConnectionDevice:2]
2025/12/31 21:07:41,764: UL43756: T01df8: UPnP_M: USNID_03 is new. Poll description to device: uuid:aedc4ed9-0c85-48c5-8cf8-a7ff09ab5b7d::urn:schemas-upnp-org:device:WANConnectionDevice:2
2025/12/31 21:07:41,764: UL43757: T01df8: UPnP_M: *** Processing USNID_04 by NOTIFY from: 10.1.1.15 : [uuid:aedc4ed9-0c85-48c5-8cf8-a7ff09ab5b7b::urn:schemas-upnp-org:device:InternetGatewayDevice:2]
2025/12/31 21:07:41,764: UL43758: T01df8: UPnP_M: This is TargetURN: NT: [urn:schemas-upnp-org:device:InternetGatewayDevice:2]
2025/12/31 21:07:41,764: UL43759: T01df8: UPnP_M: ProcDeviceUSN: USNID_04 STAY ( 1): [IPv4]: FN:[] USN:[uuid:aedc4ed9-0c85-48c5-8cf8-a7ff09ab5b7b::urn:schemas-upnp-org:device:InternetGatewayDevice:2]
2025/12/31 21:07:41,764: UL43760: T01df8: UPnP_M: USNID_04 is new. Poll description to device: uuid:aedc4ed9-0c85-48c5-8cf8-a7ff09ab5b7b::urn:schemas-upnp-org:device:InternetGatewayDevice:2
2025/12/31 21:07:41,771: UL43761: T02774: UPnP_M: Description contains 2 devices.
2025/12/31 21:07:41,771: UL43762: T02774: UPnP_M: - deviceType(URN) is TargetURN: [urn:schemas-upnp-org:device:WANDevice:2]
2025/12/31 21:07:41,772: UL43763: T02774: UPnP_M: Not interested service 1: urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1
2025/12/31 21:07:41,772: UL43764: T02774: UPnP_M: No interested services found.
2025/12/31 21:07:41,772: UL43765: T02774: UPnP_M: - deviceType(URN) is TargetURN: [urn:schemas-upnp-org:device:WANConnectionDevice:2]
2025/12/31 21:07:41,772: UL43766: T02774: UPnP_M: Not interested service 1: urn:schemas-upnp-org:service:WANIPConnection:2
2025/12/31 21:07:41,772: UL43767: T02774: UPnP_M: Not interested service 2: urn:schemas-upnp-org:service:WANIPv6FirewallControl:1
2025/12/31 21:07:41,772: UL43768: T02774: UPnP_M: No interested services found.
2025/12/31 21:07:41,772: UL43769: T02774: UPnP_M: - NOT Target device: 10.1.1.15 [10.1.1.15]
2025/12/31 21:07:41,772: UL43770: T02774: UPnP_M: - DeviceType : [urn:schemas-upnp-org:device:WANConnectionDevice:2]
2025/12/31 21:07:41,772: UL43771: T02774: UPnP_M: - Location : [http://10.1.1.15:46721/rootDesc.xml]
2025/12/31 21:07:41,772: UL43772: T02774: UPnP_M: - USN : [uuid:aedc4ed9-0c85-48c5-8cf8-a7ff09ab5b7c::urn:schemas-upnp-org:device:WANDevice:2]
2025/12/31 21:07:41,772: UL43773: T02774: UPnP_M: - USNID : [USNID_02]
2025/12/31 21:07:41,772: UL43775: T02774: UPnP_M: Poll device to: 10.1.1.15 [http://10.1.1.15:46721/rootDesc.xml]
2025/12/31 21:07:41,774: UL43776: T02774: UPnP_M: Description contains 2 devices.
2025/12/31 21:07:41,774: UL43777: T02774: UPnP_M: - deviceType(URN) is TargetURN: [urn:schemas-upnp-org:device:WANDevice:2]
2025/12/31 21:07:41,774: UL43778: T02774: UPnP_M: Not interested service 1: urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1
2025/12/31 21:07:41,774: UL43779: T02774: UPnP_M: No interested services found.
2025/12/31 21:07:41,774: UL43780: T02774: UPnP_M: - deviceType(URN) is TargetURN: [urn:schemas-upnp-org:device:WANConnectionDevice:2]
2025/12/31 21:07:41,774: UL43781: T02774: UPnP_M: Not interested service 1: urn:schemas-upnp-org:service:WANIPConnection:2
2025/12/31 21:07:41,774: UL43782: T02774: UPnP_M: Not interested service 2: urn:schemas-upnp-org:service:WANIPv6FirewallControl:1
2025/12/31 21:07:41,774: UL43783: T02774: UPnP_M: No interested services found.
2025/12/31 21:07:41,774: UL43784: T02774: UPnP_M: - NOT Target device: 10.1.1.15 [10.1.1.15]
2025/12/31 21:07:41,774: UL43785: T02774: UPnP_M: - DeviceType : [urn:schemas-upnp-org:device:WANConnectionDevice:2]
2025/12/31 21:07:41,774: UL43786: T02774: UPnP_M: - Location : [http://10.1.1.15:46721/rootDesc.xml]
2025/12/31 21:07:41,774: UL43787: T02774: UPnP_M: - USN : [uuid:aedc4ed9-0c85-48c5-8cf8-a7ff09ab5b7d::urn:schemas-upnp-org:device:WANConnectionDevice:2]
2025/12/31 21:07:41,775: UL43788: T02774: UPnP_M: - USNID : [USNID_03]
2025/12/31 21:07:41,776: UL43790: T02774: UPnP_M: Poll device to: 10.1.1.15 [http://10.1.1.15:46721/rootDesc.xml]
2025/12/31 21:07:41,778: UL43791: T02774: UPnP_M: Description contains 2 devices.
2025/12/31 21:07:41,778: UL43792: T02774: UPnP_M: - deviceType(URN) is TargetURN: [urn:schemas-upnp-org:device:WANDevice:2]
2025/12/31 21:07:41,778: UL43793: T02774: UPnP_M: Not interested service 1: urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1
2025/12/31 21:07:41,778: UL43794: T02774: UPnP_M: No interested services found.
2025/12/31 21:07:41,778: UL43795: T02774: UPnP_M: - deviceType(URN) is TargetURN: [urn:schemas-upnp-org:device:WANConnectionDevice:2]
2025/12/31 21:07:41,779: UL43796: T02774: UPnP_M: Not interested service 1: urn:schemas-upnp-org:service:WANIPConnection:2
2025/12/31 21:07:41,779: UL43797: T02774: UPnP_M: Not interested service 2: urn:schemas-upnp-org:service:WANIPv6FirewallControl:1
2025/12/31 21:07:41,779: UL43798: T02774: UPnP_M: No interested services found.
2025/12/31 21:07:41,779: UL43799: T02774: UPnP_M: - NOT Target device: 10.1.1.15 [10.1.1.15]
2025/12/31 21:07:41,779: UL43800: T02774: UPnP_M: - DeviceType : [urn:schemas-upnp-org:device:WANConnectionDevice:2]
2025/12/31 21:07:41,779: UL43801: T02774: UPnP_M: - Location : [http://10.1.1.15:46721/rootDesc.xml]
2025/12/31 21:07:41,779: UL43802: T02774: UPnP_M: - USN : [uuid:aedc4ed9-0c85-48c5-8cf8-a7ff09ab5b7b::urn:schemas-upnp-org:device:InternetGatewayDevice:2]
2025/12/31 21:07:41,779: UL43803: T02774: UPnP_M: - USNID : [USNID_04]
2025/12/31 21:07:41,826: UL43804: T03694: UPnP_M: Description contains 2 devices.
2025/12/31 21:07:41,826: UL43805: T03694: UPnP_M: - deviceType(URN) is TargetURN: [urn:schemas-upnp-org:device:WANDevice:2]
2025/12/31 21:07:41,827: UL43806: T03694: UPnP_M: Not interested service 1: urn:schemas-upnp-org:service:WANCommonInterfaceConfig:1
2025/12/31 21:07:41,827: UL43807: T03694: UPnP_M: No interested services found.
2025/12/31 21:07:41,827: UL43808: T03694: UPnP_M: - deviceType(URN) is TargetURN: [urn:schemas-upnp-org:device:WANConnectionDevice:2]
2025/12/31 21:07:41,827: UL43809: T03694: UPnP_M: Not interested service 1: urn:schemas-upnp-org:service:WANIPConnection:2
2025/12/31 21:07:41,827: UL43810: T03694: UPnP_M: Not interested service 2: urn:schemas-upnp-org:service:WANIPv6FirewallControl:1
2025/12/31 21:07:41,827: UL43811: T03694: UPnP_M: No interested services found.
2025/12/31 21:07:41,827: UL43812: T03694: UPnP_M: - NOT Target device: 10.1.1.15 [10.1.1.15]
2025/12/31 21:07:41,827: UL43813: T03694: UPnP_M: - DeviceType : [urn:schemas-upnp-org:device:WANConnectionDevice:2]
2025/12/31 21:07:41,827: UL43814: T03694: UPnP_M: - Location : [http://10.1.1.15:46721/rootDesc.xml]
2025/12/31 21:07:41,827: UL43815: T03694: UPnP_M: - USN : [uuid:aedc4ed9-0c85-48c5-8cf8-a7ff09ab5b7d::urn:schemas-upnp-org:device:WANConnectionDevice:2]
2025/12/31 21:07:41,827: UL43816: T03694: UPnP_M: - USNID : [USNID_03]
2025/12/31 21:07:42,327: UL43818: T06a3c: UPnP_P: [Proc:RelTime ] <POL>: Elapsed: 00:05:18 -> 318.0 / 318.0 sec
2025/12/31 21:07:43,326: UL43820: T06a3c: UPnP_P: [Proc:RelTime ] <POL>: Elapsed: 00:05:18 -> 318.0 / 318.0 sec
2025/12/31 21:07:44,326: UL43822: T06a3c: UPnP_P: [Proc:RelTime ] <POL>: Elapsed: 00:05:18 -> 318.0 / 318.0 sec
2025/12/31 21:07:45,325: UL43824: T06a3c: UPnP_P: [Proc:RelTime ] <POL>: Elapsed: 00:05:18 -> 318.0 / 318.0 sec
2025/12/31 21:07:46,324: UL43826: T06a3c: UPnP_P: [Proc:RelTime ] <POL>: Elapsed: 00:05:18 -> 318.0 / 318.0 sec
2025/12/31 21:07:47,322: UL43828: T06a3c: UPnP_P: [Proc:RelTime ] <POL>: Elapsed: 00:05:18 -> 318.0 / 318.0 sec
2025/12/31 21:07:48,322: UL43830: T06a3c: UPnP_P: [Proc:RelTime ] <POL>: Elapsed: 00:05:18 -> 318.0 / 318.0 sec
2025/12/31 21:07:49,321: UL43833: T06a3c: UPnP_P: [Proc:RelTime ] <POL>: Elapsed: 00:05:18 -> 318.0 / 318.0 sec
2025/12/31 21:07:50,319: UL43837: T06a3c: UPnP_P: [Proc:RelTime ] <POL>: Elapsed: 00:05:18 -> 318.0 / 318.0 sec
2025/12/31 21:07:51,318: UL43850: T06a3c: UPnP_P: [Proc:RelTime ] <POL>: Elapsed: 00:05:18 -> 318.0 / 318.0 sec
2025/12/31 21:07:52,317: UL43852: T06a3c: UPnP_P: [Proc:RelTime ] <POL>: Elapsed: 00:05:18 -> 318.0 / 318.0 sec
2025/12/31 21:07:53,316: UL43860: T06a3c: UPnP_P: [Proc:RelTime ] <POL>: Elapsed: 00:05:18 -> 318.0 / 318.0 sec

[Tiki]

Please attach a log file saved by Toolbar button of Log View.

[storaid]

Hi,

Here is the log file!

Thanks

Attachments:

1. TuneBrowserLog.tblgz

[Tiki]

Thank you.

[Tiki]

Hello storaid.

Thank you for your analysis and attaching the log file.

As you mentioned, TuneBrowser does not re-subscribe to events after a timeout. I understood that this needs to be implemented, so I will consider addressing it in a release in the (near) future.

Thank you.

[投稿者]

投稿