INTERACT FORUM

Networks and Remotes => Media Network => Topic started by: GaryG45 on June 26, 2019, 09:13:04 am

Title: Where is SetNextAVtransport setting located?
Post by: GaryG45 on June 26, 2019, 09:13:04 am
I'm using MC25 and I'm having the same issue as described in topic:
https://yabb.jriver.com/interact/index.php/topic,112206.msg775434.html#msg775434

I cannot find the SetNextAVtransport setting.  Maybe it has been replaced in MC25 with another setting.  I believe the problem is due to Bose's proprietary code for DLNA and not on the MC side.

Gary
Title: Re: Where is SetNextAVtransport setting located?
Post by: JimH on June 26, 2019, 09:44:27 am
Under Playing Now, right click on the Renderer. 
Title: Re: Where is SetNextAVtransport setting located?
Post by: Scobie on June 26, 2019, 07:34:54 pm
Right click on the renderer itself for DLNA options, refer attachment.


Title: Re: Where is SetNextAVtransport setting located?
Post by: GaryG45 on June 27, 2019, 02:10:04 pm
Thanks Scobie.  Your attachment is exactly what I see for the Bose Soundtouch 20.  I checked "Disable SetNext Support", and it didn't make a difference.

I tried Whitebear's DLNA Media Renderer Analysis tool and found the following message in the log.
Play test file result=Play failed => Start Ok / Time out / Subscribe error

When running the audio tests of the tool, I received the following message for each test.
Play failed=> Command "SetNextAVTransportURI" failed.

I believe Bose would have to make a code change for this to work and because they are no longer developing the Soundtouch products I doubt if anything will be done.

Title: Re: Where is SetNextAVtransport setting located?
Post by: AndrewFG on June 27, 2019, 05:14:31 pm
You have two separate issues..

1) The SetNext issue. => You should disable SetNext support as previously suggested.

2) The Subscribe issue. => This may be either a problem with your renderer; in which case try the Ignore Transport Events setting in MC (next to the Disable SetNext setting). Or it may be a problem with your LAN setup; in which case make sure that there is no firewall or av software blocking incoming HTTP connections to your PC, and ensure that your router is set to route TCP traffic in both directions between the renderer and the PC.
Title: Re: Where is SetNextAVtransport setting located?
Post by: Scobie on June 27, 2019, 06:20:46 pm
I've had a quick look online and found the same information that I'm sure you have come across that states that this Bose device doesn't fully support DLNA.

Looks as if some have had success associating a DLNA server but using the native Bose app to control it:

https://community.bose.com/t5/SoundTouch-Archive/SoundTouch-20-as-wireless-home-music-service/td-p/4351

https://community.bose.com/t5/SoundTouch-Archive/Full-DLNA-Support-WHEN/td-p/51094

is this the setup you are trying (with JRiver not Plex obviously)?



Title: Re: Where is SetNextAVtransport setting located?
Post by: GaryG45 on June 28, 2019, 10:06:43 am
Scobie,
I had found another post in the Bose forum that also mentioned the Soundtouch 20 wasn't fully DLNA compatible.  I've checked the user manual, and there is nothing in it that mentions assigning media servers.  When I look at the app on my iPhone, I see the Plex media server that is on my laptop.  I've stopped Plex and restarted the app and the JRiver media server doesn't get picked up.  I've seen where people have tried to use the Plex media server and have had problems; probably due to the DLNA compatibility issues.

The app is terrible.  My music library resides on my WDMyCloudMirror NAS in a share with FLAC and ALAC subfolders.  When setting up the NAS with the app I couldn't pick the NAS share for the music; only the NAS.  I had to modify the Twonky media server on the NAS to get things setup properly.  If I didn't have the Twonky media server on the NAS, I might not have been able to use the NAS.  Looks like I'll have to use the app to play my music from this speaker.  At least JRiver works fine with my Sonos Play 3 speaker.

Because of the DLNA compatibilty issue I'm not going to pursue this any further.  Thanks for everyone's help with this issue.

Gary