Print

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

[eba]

Hi,

I've just got myself a Mission Aero speaker, which I've been using MC21 to play to via DLNA.

MC seems to get confused as to what's playing, and hence repeats tracks:
At the end of the first track, the second track starts playing on the speaker, however MC's display jumps back to the start of the first track.  Then when it gets to the end of the second track, MC moves onto the second, and this track gets repeated on the speaker.

I've had the same problem occasionally when playing to a Samsung TV, but then it was a rare event, whereas with the Mission it's every time!

Possibly related: while experimenting, I've found that If I manually try to seek towards the end of a track on MC, it goes ok to the point requested, but then a few seconds later, MC will jump back to an earlier point, while the speaker will continue from the point seeked to.  When it gets to the end of the track, the speaker plays the next track, but MC's display will continue on with the previous, ultimately showing an elapsed time greater than the track length e.g 4:01/3:42 - and then when the track does finish, it's repeated, as above.

I've done some searching and seen some similar problems, but no obvious solutions.
http://yabb.jriver.com/interact/index.php?topic=94626.0
http://yabb.jriver.com/interact/index.php?topic=101498.0

I've tried running AndrewFG's renderer analyser (log attached), and played about with settings accordingly, but with no joy.

Playing via Windows Media Player gives the same seeking display issue, but corrects itself once it gets to the next track, and hence doesn't repeat.

Any ideas?
Thanks,
Ben

[AndrewFG]

Right click the renderer, DLNA settings, ignore transport events.


PS thanks for sending the renderer report

[eba]

Right click the renderer, DLNA settings, ignore transport events.


PS thanks for sending the renderer report

Hi,

Thanks for the suggestion, but doesn't appear to have had any effect

[bob]

Hi,

Thanks for the suggestion, but doesn't appear to have had any effect

Try disabling setNext support for the renderer (next to the transport events disable in the Zone->DLNA controller options.

[eba]

After setting a few more things according to the analyser, I seem to have now got the right combination!  Not quite sure what I did (and not daring to touch anything again for the moment...) but it currently appears to be working  

Possibly the combination of ignore transparent events and Disable SetNext.

Thanks again Andrew!

Edit:  Cheers also Bob, think you're right!

[AndrewFG]

Possibly the combination of ignore transparent events and Disable SetNext.

Yes. Both are necessary.

[AndrewFG]

Hi Bob. We see so many renderers that fail in this way. The common denominator is that the event subscription either fails entirely, or else fails to deliver a valid initial event on time. This is such a common occurrence that I think that when you (MC) detects such an error, you ought to, by default, disable both transport events and SetNext support. That way I reckon you could avoid 95% of such calls.

[eba]

From someone who is fairly new to this stuff, and knows very little about the technical side of DLNA (and, ok, not that much about the non-technical side either - if there even is one )...

Correct me if I'm wrong, but judging from the faff of trying to get it to work properly, and the disablements I needed to do, and that gapless still doesn't work, it seems that my speaker isn't highly DLNA capable, despite being a fairly expensive piece of kit that is theoretically purposefully designed for wireless playback.

Is it something that could be potentially improved with a firmware update?  Or is it hardware-limited?  I'm particularly interested in gapless here, and also zone-syncing ability, which at the moment seems to work but results in a long pause at the start of each track while it sorts itself out.  I note that the firmware it comes with is over three years old, and although there is an update option, I can't seem to find any new (or even old) version - although their website is a little lacking beyond telling you how good it apparently is.  If it could help, I'll try asking them - though judging from facebook it seems responding to customers isn't particularly high on their priorities 

[AndrewFG]

Improved firmware could fix your problem. So yes do write to the manufacturer about it.

Many manufacturers buy their (faulty) software from third parties. In your case it looks to be from WinAmp..