Print

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

[milknkukis]

Hi All

I'm looking for a little help getting my renderer working correctly. It's a Pure Jongo T2 and has it's own control app which works ok, it's just not as good as Gizmo. Gizmo is able to control the device fine apart from one aspect which is it can't change the volume level.

I've used Whitebear DMR Analyser to generate the attached report but I'm not sure what I'm looking for. It seems to indicate it should be able to handle setting the volume over DLNA but changing the volume in Gizmo doesn't make any difference. Any ideas?

Grateful for any help
regards
Mark

[AndrewFG]

It's a bit late tonight, but I will get back to you tomorrow.

[AndrewFG]

The renderer report shows nothing out of the usual.

Did you check that the MC Audio Settings are not set to "Disabled Volume" ??  (see screen shot)

[milknkukis]

Thanks Andrew, I only get those options under my local zone (Living Room), if I select the Jongo as the Zone in the top window I just get:
Configure audio using Options > Media Network > Add or configure DLNA servers...

For Living Room it is set to System. Do I need to configure a new zone in any way?

cheers
Mark

[AndrewFG]

Not sure...

You could try another test with my DMR Anlayzer; before you select the renderer first turn on HTTP logging, then select the renderer, and finally post the HTTP log file here..

[milknkukis]

ok, see if there is anything useful in here

Thanks
Mark

[AndrewFG]

The HTTP log shows that your renderer is accepting the SetVolume & SetMute commands sent from the DMRA tool without any errors. It is also accepting the GetVolume & GetMute commands without any errors and returning the value that had been set via the prior Setxx command. In other words as far as it looks over the LAN it is working fine. However obviously there is no way to guarantee that it is actually doing what it claims to be doing (i.e. actually changing its audible volume setting).

So just to make sure we are talking about the same thing, can you please advise if your problem is that when you press the MC volume buttons, either a) the actual audible volume on the renderer does not change, or b) you don't see anything happening to the visible position of the volume bar display in MC, or c) both..

[milknkukis]

Hi Andrew
Sorry for the delay, busy weekend!

If I select the Jongo in Playing Now then the slider button on the volume bar disappears.
If I use Gizmo on my phone to play from the server to the Jongo then adjusting the volume makes no difference to the sound level of the Jongo. I can change the volume to 0% or 100% and the Jongo will just keep playing at the same volume. The Jongo has it's own app (Pure Connect) and in this I can see the volume stays the same. Controlling the volume from the Pure Connect app works fine.

I'm also having problems with the desktop dropping it's wireless connection but I don't think it's related to this. What's odd though is i'm seeing MC crashing quite a bit which is something it never used to do before I got this Jongo. I've tried both MC18 and MC21 and both have problems so I suspect it might be hardware related. I'm using an ancient XP box for this which probably isn't helping, is DLNA particularly demanding on resources? I was assuming it shouldn't be...

regards
Mark

[AndrewFG]

The behavior you describe sounds very strange. I built a new version of my DMRA tool that does a bit more checking concerning the SetVolume and GetVolume methods. So perhaps you could download and run this new version? Please turn on HTTP logging and then select the Jongo. And then please post both the Renderer report and the HTTP log. Thanks in advance..

[milknkukis]

ok, here's the files from the newer version.

[AndrewFG]

Hi.

Thank you for trying the new version.

Actually it seems to show that your renderer is doing everything that it ought to do, and just fine.

So I am beginning to think that this might indeed be an issue with MC. My suspicion is that when MC SUBSCRIBE's to the RenderingControl event notifications, it is not properly parsing the NOTIFY responses. Below is an example of (some of) what the Pure Jongo sends in its NOTIFY message, and underneath it is what MC's own renderer sends in its NOTIFY message. I am guessing that MC expects other renderers to send NOTIFY's similar to what it sends itself, and it may be getting overwhelmed trying to parse what the Jongo sends. Just an assumption on my side though..


Pure Jongo - RenderingControl Event Notification

<InstanceID val="0"><AllowedTransformSettings val="<?xml version="1.0" encoding="UTF-8"?><TransformList xmlns="urn:schemas-upnp-org:av:AllowedTransformSettings" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:schemas-upnp-org:av:AllowedTransformSettings http://www.upnp.org/schemas/av/AllowedTransformSettings.xsd"><transform name="BandEq_65_1040" shared="1"><friendlyName>Bass</friendlyName><allowedValueRange scale="Linear"><minimum>0</minimum><maximum>10</maximum><step>1</step></allowedValueRange></transform><transform name="BandEq_1250_20000" shared="1"><friendlyName>Treble</friendlyName><allowedValueRange scale="Linear"><minimum>0</minimum><maximum>10</maximum><step>1</step></allowedValueRange></transform></TransformList>"/><TransformSettings val="<?xml version="1.0" encoding="UTF-8"?><TransformSettings xmlns="urn:schemas-upnp-org:av:TransformSettings" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="urn:schemas-upnp-org:av:TransformSettings http://www.upnp.org/schemas/av/TransformSettings.xsd"><transform name="BandEq_65_1040"><Value>5</Value></transform><transform name="BandEq_1250_20000"><Value>5</Value></transform></TransformSettings>"/><PresetNameList val="FactoryDefaults, InstallationDefaults"/><Mute channel="Master" val="0"/><Volume channel="Master" val="24"/></InstanceID>

Media Center - RenderingControl Event Notification

<InstanceID val="0">
<Volume val="39" channel="Master"/>
</InstanceID>

EDIT: there are three main differences that I notice between these two NOTIFY's:

• The Jongo includes a lot more attributes (this is unnecessary , but in principle it is not wrong)
• The Jongo escapes the quote characters " as " (this is unnecessary , but in principle it is not wrong)
• The Jongo puts channel before val in the Volume element, whereas MC does it the other way round..

[bob]

Since the volume slider in MC is not usable when set to the Jongo zone we can assume that MC doesn't think the volume control works.
IIRC, the only thing that could make that volume slider look disabled would be if GetVolume() failed.
It's called with the InstanceID set to 0 and the Channel set to Master.

[AndrewFG]

Since the volume slider in MC is not usable when set to the Jongo zone we can assume that MC doesn't think the volume control works.
IIRC, the only thing that could make that volume slider look disabled would be if GetVolume() failed.
It's called with the InstanceID set to 0 and the Channel set to Master.

Hi bob,

Here is the GetVolume call from my DMRA. It looks fine to me. Any reasons why you think it would fail on MC ??

17:27:33.871 Client Connected.

POST /Control/org.mpris.MediaPlayer2.mansion/RygelRenderingControl HTTP/1.1
Connection: close
Content-Type: text/xml; charset=utf-8
Content-Length: 448
SOAPACTION: "urn:schemas-upnp-org:service:RenderingControl:1#GetVolume"
Host: 192.168.2.86:39883
Accept: text/xml
Accept-Encoding: identity
User-Agent: Whitebear/1.0, UPnP/1.0, RendererAnalyser/1.0

<?xml version="1.0" encoding="UTF-8" ?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<s:Body>
<u:GetVolume xmlns:u="urn:schemas-upnp-org:service:RenderingControl:1">
<InstanceID>0</InstanceID>
<Channel>Master</Channel>
</u:GetVolume>
</s:Body>
</s:Envelope>

HTTP/1.1 200 OK
Date: Fri, 02 Jan 1970 20:43:33 GMT
Content-Type: text/xml; charset="utf-8"
Ext:
Server: Linux/3.3.0 UPnP/1.0 GUPnP/0.18.2
Content-Length: 309

<?xml version="1.0"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:GetVolumeResponse xmlns:u="urn:schemas-upnp-org:service:RenderingControl:1"><CurrentVolume>24</CurrentVolume></u:GetVolumeResponse></s:Body></s:Envelope>

17:27:33.909 Client Disconnected.
17:27:33.909 Success: Http 200 Ok

[bob]

Hi bob,

Here is the GetVolume call from my DMRA. It looks fine to me. Any reasons why you think it would fail on MC ??

17:27:33.871 Client Connected.

POST /Control/org.mpris.MediaPlayer2.mansion/RygelRenderingControl HTTP/1.1
Connection: close
Content-Type: text/xml; charset=utf-8
Content-Length: 448
SOAPACTION: "urn:schemas-upnp-org:service:RenderingControl:1#GetVolume"
Host: 192.168.2.86:39883
Accept: text/xml
Accept-Encoding: identity
User-Agent: Whitebear/1.0, UPnP/1.0, RendererAnalyser/1.0

<?xml version="1.0" encoding="UTF-8" ?>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<s:Body>
<u:GetVolume xmlns:u="urn:schemas-upnp-org:service:RenderingControl:1">
<InstanceID>0</InstanceID>
<Channel>Master</Channel>
</u:GetVolume>
</s:Body>
</s:Envelope>

HTTP/1.1 200 OK
Date: Fri, 02 Jan 1970 20:43:33 GMT
Content-Type: text/xml; charset="utf-8"
Ext:
Server: Linux/3.3.0 UPnP/1.0 GUPnP/0.18.2
Content-Length: 309

<?xml version="1.0"?><s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><u:GetVolumeResponse xmlns:u="urn:schemas-upnp-org:service:RenderingControl:1"><CurrentVolume>24</CurrentVolume></u:GetVolumeResponse></s:Body></s:Envelope>

17:27:33.909 Client Disconnected.
17:27:33.909 Success: Http 200 Ok

Hi Andrew,
It looks fine to me too. I was just looking in the DMRA logs also. It's also possible that it doesn't work if GetMute() fails but that looks good to me too.
I'd like to verify with him that the slider pointer for volume is NOT SHOWING for sure.
Perhaps a log from MC would help as well.

I don't think the events have anything to do with the volume slider being disabled but it is possible they could be causing a crash. I wouldn't think so but that is different from all of the other devices I've seen.

[milknkukis]

Hi Bob

Thanks for taking a look. Attached is a screenshot of the volume control.

Let me know if you want me to do anything specific for the log, I've just turned it on for now and will continue to use it normally.

Mark

[bob]

Hi Bob

Thanks for taking a look. Attached is a screenshot of the volume control.

Let me know if you want me to do anything specific for the log, I've just turned it on for now and will continue to use it normally.

Mark

Right-click on the speaker on the left of the slider, what do you see then?

[milknkukis]

It doesn't do anything. If I right click on my normal zone it mutes the system.

[AndrewFG]

I don't think the events have anything to do with the volume slider being disabled but it is possible they could be causing a crash. I wouldn't think so but that is different from all of the other devices I've seen.

Yes it is a bit "cute" -- I particularly like this bit in their SCPDs  


<!--============================================================Title: UPnP AV AV-Transport Service (AVT) TemplatePurpose:To identify the required/optional actions and state variablesand the required allowed values defined by this service type.Note:This file uses tabs (not spaces) for block indentation.Any updates to this file should maintain this convention.This includes disabling any automatic tab-to-space conversionfeature provided by your editor.================================================================-->

[bob]

It doesn't do anything. If I right click on my normal zone it mutes the system.

You don't get a little dropdown menu when you right-click?

[bob]

Yes it is a bit "cute" -- I particularly like this bit in their SCPDs  


<!--============================================================Title: UPnP AV AV-Transport Service (AVT) TemplatePurpose:To identify the required/optional actions and state variablesand the required allowed values defined by this service type.Note:This file uses tabs (not spaces) for block indentation.Any updates to this file should maintain this convention.This includes disabling any automatic tab-to-space conversionfeature provided by your editor.================================================================-->

Oops ;-)

[milknkukis]

You don't get a little dropdown menu when you right-click?

Nope.

Log file so far... (Nothing playing through MC right now)

[milknkukis]

You don't get a little dropdown menu when you right-click?

Hi Bob, I was trying to work out what menu you might have been referring to, did you mean this one? (see image) This is what I get if I right click on the Jongo, not the speaker symbol.

[AndrewFG]

Bob was asking what happens if you right click in the little speaker icons on the volume control bar..

[milknkukis]

Hi Andrew,
Yeah, is just wondering if there was a misunderstanding as right clicking on the small speaker icon doesn't do anything in either of my zones or in either of the versions of MC I have installed at the moment. What's supposed to happen? (It just mutes the system for me)
Cheers
Mark

[AndrewFG]

It is supposed to bring up a menu. However if MC has somehow decided that the volume slider is disabled then you won't /don't see that menu. So the next step is to find out why MC has decided that the volume slider is disabled...

[milknkukis]

But I don't get a menu even in my normal zone which works correctly, or does the menu only appear for DLNA devices?

[AndrewFG]

On your local sound output you should see the right click menu below that has a lot of options. And on a UPnP renderer you should see the menu below that has fewer options.

[milknkukis]

Thanks Andrew, now I understand.

The issue with the menu is actually just a bug in the Z skin, I have tried a few others and they all display the menu as expected.

Attached is the menu for the Jongo, none of the buttons have any effect on the volume being played, not even mute. I tried toggling Bitstreaming but it didn't make any difference (I don't know what this does).

cheers
Mark

[AndrewFG]

Can you please try a standard skin like "Noire". That way we can separate out whether the issue is a user interface issue or a UPNP issue. As mentioned in my prior posts, my own tests indicate that the UPNP part of the story should work just fine. At least as far as HTTP transactions over the wire are concerned.

[milknkukis]

Hi Andrew

Screenshot using Noire attached, it's the same behaviour as I described in the previous post - still no volume control.

regards
Mark

[AndrewFG]

Ok. So we have three facts now:

1) When MC sends GetVolume / SetVolume, the MC renderer returns valid results, and the MC UI is NOT disabled.
2) When my DMRA sends GetVolume /SetVolume, the renderer returns valid results too.
3) When the renderer receives SetVolume, either from MC or from DMRA, it does not actually change its volume.

This looks to me like a renderer problem, and not an MC problem.

[JimH]

This is more fun than watching Judge Judy.

[milknkukis]

3) When the renderer receives SetVolume, either from MC or from DMRA, it does not actually change its volume.

Adding to the Judge Judy theme, how would i know if the commands from DMRA are working or not? Is there a way I can trigger DMRA to send a command such as mute and hear if it works?

BTW: I'm not judging, I'd just like MC and Jongo to get along! I've been using MC for a long time and think it would be great if I could continue to use it with my new toys.

[AndrewFG]

During the initial test, the DMRA sends a series of GetVolume, SetVolume, GetMute, and SetMute commands to check that the renderer responds with a proper command acknowledgement. Your renderer does respond with proper command acknowledgements in all cases. The DMRA does not yet have a feature for testing what you can actually hear though..

[AndrewFG]

The DMRA does not yet have a feature for testing what you can actually hear though..

UPDATE:  I made a new build of the DMRA that allows you to test your hearing of volume changes. After selecting the renderer, go to the Renderer Tests page, select a (longish) track to play. And then use the Mute checkbox and Volume slider as you would expect.

[milknkukis]

Hi Andrew

I finally had a chance to test the new version you put together, thank you so much for taking the time to do that!

I can confirm DMRA changes the volume and mutes the sound while playing the sound file, logs attached.

How do I add a different media file to DMRA for it to play? I tried putting a mp3 in the same folder as 28s.mp3 but it doesn't show up. (And what is the 28s clip anyway?? I know it's from the start of films but I can't place it, is it Viacomm??)

regards
Mark

[AndrewFG]

I can confirm DMRA changes the volume and mutes the sound while playing the sound file, logs attached.

Ok that means the Jongo is working fine. And it is definitely a problem with MC. You need to get an answer from Bob about whether he can fix it.

How do I add a different media file to DMRA for it to play? I tried putting a mp3 in the same folder as 28s.mp3 but it doesn't show up.

You have to follow the naming syntax of the other files. On the DMRA website there is a link which allows you to download other test files following the same naming syntax.

[bob]

Does the progress bar work during playback?
Can you seek?

[milknkukis]

Hi Bob

Yep, both of those work fine, both from MC and from Gizmo.

Andrew, thanks for the help.

[bob]

Hi Bob

Yep, both of those work fine, both from MC and from Gizmo.

Andrew, thanks for the help.

I think this is weird enough that I ordered one to test here.

[milknkukis]

wow, that's great, it will be interesting to see what you discover!

[bob]

Ok that means the Jongo is working fine. And it is definitely a problem with MC. You need to get an answer from Bob about whether he can fix it.

Hey Andrew,
The rendering control service is RenderingControl:3 !
That looks pretty weird (and it's why it doesn't work since we detect version 2 and 1 but not 3).
Is there even a version 3 of the spec and why would that be the only service on :3

[bob]

So I made a change that will make this work.

It is a pretty sluggish device, must be a pretty low power processor in it but it seems to work OK on mp3's and waves. 41 or 48k it says.
I can't seem to get it to work with L16 though it claims support for it.

[AndrewFG]

Hey Andrew,
The rendering control service is RenderingControl:3 !
That looks pretty weird (and it's why it doesn't work since we detect version 2 and 1 but not 3).
Is there even a version 3 of the spec and why would that be the only service on :3

Hi Bob,

I have several comments...

• Any UPNP device that supports a higher version, must also support lower versions
• And indeed the Jongo does also support lower versions too
• So if MC wants to talk to a particular version you need to SSDP search for that version (only)
• My DMRA only searches for v1 & v2, and so I tested against v2, whereas you tested against v3
• RenderingControl v3 added a few additional methods for video transforms, mostly irrelevant for MC
• However the RC v3 methods for Volume and Mute did not change..
• For MC, more important than the RC v3 added features, are the AVTransport v2/3 added features..
• The AVT v2/3 added features include SyncPlay; if you have two Jongos you could try testing that in MC

[bob]

Hi Bob,

I have several comments...

• Any UPNP device that supports a higher version, must also support lower versions
• And indeed the Jongo does also support lower versions too
• So if MC wants to talk to a particular version you need to SSDP search for that version (only)
• My DMRA only searches for v1 & v2, and so I tested against v2, whereas you tested against v3
• RenderingControl v3 added a few additional methods for video transforms, mostly irrelevant for MC
• However the RC v3 methods for Volume and Mute did not change..
• For MC, more important than the RC v3 added features, are the AVTransport v2/3 added features..
• The AVT v2/3 added features include SyncPlay; if you have two Jongos you could try testing that in MC

Hi Andrew,
Looking in device spy, I don't see a service point for the RenderingControl versions 1 and 2, just v3.
There aren't any v2/3 AVT entrypoints either as far as I can see.

[milknkukis]

So I made a change that will make this work.

Hi Bob, I really appreciate you taking a look at this, thanks for your efforts (and Andrew)! I guess this change will be in 21.0.51?

It is a pretty sluggish device, must be a pretty low power processor in it but it seems to work OK on mp3's and waves. 41 or 48k it says.
I can't seem to get it to work with L16 though it claims support for it.

As you see a lot of these devices how does it compare to something like a ChromeCast Audio? I have to admit I have been a bit frustrated and disappointed by its performance but there aren't many options  for multi-room other than Sonos and that doesn't seem like it will play nicely with MC anytime soon.

cheers
Mark

[milknkukis]

]The AVT v2/3 added features include SyncPlay; if you have two Jongos you could try testing that in MC[/li][/list]

I now have 2 Jongos, I was torn between buying a ChromeCast Audio and a Jongo A2. At £14 the ChromeCast seemed like a no brainer but then I found the Jongo A2 for £19 so being able to control both devices from one app tipped the balance. It only arrived this morning but I have to say the syncing between the two devices is very impressive, I wouldn't want to make any adjustment to it. I remember years ago (10 years?) when I was using MC11 with multiple sound cards and amps, trying to balance the output timings it took a bit of time to get it right whereas this needed no work straight out of the box. I've been floating between houses for several years but it's nice to see the tech move on.

I have only been using the Jongo app so far but if there is anything you want me to test with the 2 Jongos just let me know. The first thing I need to work out is creating a new zone to play to both of them.

cheers
Mark

[AndrewFG]

Hi Andrew,
Looking in device spy, I don't see a service point for the RenderingControl versions 1 and 2, just v3.
There aren't any v2/3 AVT entrypoints either as far as I can see.

I don't have the device in my possession, but the logs that the OP did with my DMRA did definitely show v1 and v2 support. And indeed my DMRA would definitely not have found any v3 features because it is hard coded to look for only v1 & v2. So perhaps you can run the DMRA yourself? Start the DMRA, ignore the first device search, turn on HTTP logging, run a second device search, and post the HTTP log....


EDIT: you could even click on the SCPD and DDD urls in my DMRA to open up those documents in your browser...

[bob]

I don't have the device in my possession, but the logs that the OP did with my DMRA did definitely show v1 and v2 support. And indeed my DMRA would definitely not have found any v3 features because it is hard coded to look for only v1 & v2. So perhaps you can run the DMRA yourself? Start the DMRA, ignore the first device search, turn on HTTP logging, run a second device search, and post the HTTP log....

Here it is.
Weird that I see RenderingControl:1 in your log and nowhere in the device or service xml files.

[bob]

Here it is.
Weird that I see RenderingControl:1 in your log and nowhere in the device or service xml files.

Are you reading the service descriptions to get the service points or trying the service points and seeing if they work?
I suspect that it may ignore the version number and use the functions if it exists. We do require the device to tell us proper service descriptions and we weren't looking for version 3.