|
|
Post by jpwoodbu on Dec 22, 2023 1:42:27 GMT -5
For those enrolled in the closed beta, to get the latest version which I just uploaded, you'll probably need to open the app in the Play Store, leave the beta, and rejoin the beta. The beta stuff should be near the bottom of the app's page on the Play Store.
This is probably because I'm moving to an open beta model rather than the closed beta Google required me to use initially. I was hoping that removing everyone from the closed beta myself in the Play Console would automatically move people to the open beta, but that doesn't appear to be the case.
Apologies for the inconvenience.
|
|
|
|
Post by danielb on Dec 22, 2023 9:33:02 GMT -5
I would have liked to try the app, unfortunately I can't download the app, the Play Store doesn't allow it: This article is not available in your country
Country/Region: Switzerland/Europe
|
|
|
|
Post by jpwoodbu on Dec 22, 2023 9:54:12 GMT -5
I would have liked to try the app, unfortunately I can't download the app, the Play Store doesn't allow it: This article is not available in your country Country/Region: Switzerland/Europe Thanks for letting me know. I've requested Switzerland be added to the app's list of countries. I've been reluctant to add countries to the list since the Google Play Console, for some countries, was showing warnings about local requirements for apps that looked like paperwork might need to be filed. But it doesn't appear Switzerland needs anything like that. |
|
|
|
Post by danielb on Dec 22, 2023 10:54:24 GMT -5
Thanks for letting me know. I've requested Switzerland be added to the app's list of countries. I've been reluctant to add countries to the list since the Google Play Console, for some countries, was showing warnings about local requirements for apps that looked like paperwork might need to be filed. But it doesn't appear Switzerland needs anything like that. Google has already activated it. I have installed it and also tried it out. The app is much faster than the IOS App :-) Would it also be possible to select the mode (User, Dirac 1, Dirac2, Dirac3) in the presets? |
|
|
|
Post by geebo on Dec 22, 2023 11:45:34 GMT -5
I just went through leaving and rejoining the beta (very simple) and installed the latest version. Everything seems to work fine and it's nice to have OSD mirroring active.
Thanks!
|
|
|
|
Post by jpwoodbu on Dec 22, 2023 11:52:22 GMT -5
Thanks for letting me know. I've requested Switzerland be added to the app's list of countries. I've been reluctant to add countries to the list since the Google Play Console, for some countries, was showing warnings about local requirements for apps that looked like paperwork might need to be filed. But it doesn't appear Switzerland needs anything like that. Google has already activated it. I have installed it and also tried it out. The app is much faster than the IOS App :-) Would it also be possible to select the mode (User, Dirac 1, Dirac2, Dirac3) in the presets? I'll look into that. There is a "dirac" API command in the API docs that's described as "Select speaker DIRAC". I skipped over it because it wasn't clear to me what it would do. But I'll give it a try. I suspect it cycles through the DIRAC configurations. |
|
|
|
Post by geebo on Dec 22, 2023 12:01:53 GMT -5
Google has already activated it. I have installed it and also tried it out. The app is much faster than the IOS App :-) Would it also be possible to select the mode (User, Dirac 1, Dirac2, Dirac3) in the presets? I'll look into that. There is a "dirac" API command in the API docs that's described as "Select speaker DIRAC". I skipped over it because it wasn't clear to me what it would do. But I'll give it a try. I suspect it cycles through the DIRAC configurations. I must be missing something. I am able to choose from the different Dirac filters from within the speaker preset just as I can from the Emotiva OSD. Choose a preset then Equalization and you can choose between User, Dirac 1,2 and 3. |
|
|
|
Post by jpwoodbu on Dec 22, 2023 12:06:52 GMT -5
I'll look into that. There is a "dirac" API command in the API docs that's described as "Select speaker DIRAC". I skipped over it because it wasn't clear to me what it would do. But I'll give it a try. I suspect it cycles through the DIRAC configurations. I must be missing something. I am able to choose from the different Dirac filters from within the speaker preset just as I can from the Emotiva OSD. Choose a preset then Equalization and you can choose between User, Dirac 1,2 and 3. That makes sense to me. If I remember correctly, at least on my RMC-1L, I have a particular DIRAC config associated with speaker preset 1 and no DIRAC config on speaker preset 2. Maybe changing the DIRAC config in real-time requires changing the speaker preset. But maybe that "dirac" API command will change which DIRAC config is assigned to the current preset with a single button? It could also be an API command that only makes sense on older processors. |
|
|
|
Post by geebo on Dec 22, 2023 12:15:27 GMT -5
I must be missing something. I am able to choose from the different Dirac filters from within the speaker preset just as I can from the Emotiva OSD. Choose a preset then Equalization and you can choose between User, Dirac 1,2 and 3. That makes sense to me. If I remember correctly, at least on my RMC-1L, I have a particular DIRAC config associated with speaker preset 1 and no DIRAC config on speaker preset 2. Maybe changing the DIRAC config in real-time requires changing the speaker preset. But maybe that "dirac" API command will change which DIRAC config is assigned to the current preset with a single button? It could also be an API command that only makes sense on older processors. Being able to change it in the Main Zone menu would be cool but I have my doubts if it's possible. But it's still easy enough to change through Setup. |
|
|
|
Post by danielb on Dec 22, 2023 12:29:59 GMT -5
I must be missing something. I am able to choose from the different Dirac filters from within the speaker preset just as I can from the Emotiva OSD. Choose a preset then Equalization and you can choose between User, Dirac 1,2 and 3. That makes sense to me. If I remember correctly, at least on my RMC-1L, I have a particular DIRAC config associated with speaker preset 1 and no DIRAC config on speaker preset 2. Maybe changing the DIRAC config in real-time requires changing the speaker preset. But maybe that "dirac" API command will change which DIRAC config is assigned to the current preset with a single button? It could also be an API command that only makes sense on older processors. There is a default setting in each of the presets, this can be User, or one of the 3 Dirac settings. What I would like is a direct selection option (one keystroke) for one of the 4 settings (per Preset) without having to go through the Emotiva settings menu (Menu > Setup Speaker > Preset > Equalization > ... ). Apart from that, the switching process is also agonizingly slow. Or do I simply not know the better/simpler way? |
|
|
|
Post by AudioHTIT on Dec 22, 2023 12:34:11 GMT -5
Would it also be possible to select the mode (User, Dirac 1, Dirac2, Dirac3) in the presets? I’d like that feature in the iOS app too, I’ll be interested to see if there are control codes for selecting those, and if they’ve been exposed in the API. One basic feature I’d like to see is a Dirac On/Off, and this would be one way of accomplishing it. I hope this App can provide some motivation (competition?) to update the Official iOS App for the G3P/G4P. An interesting idea would be to use the unused ‘Dirac’ preset (leftover from the XMC-1), as a switch to turn Dirac on and off, but that would likely require an API change, and could break the remotes use with the XMC-1. |
|
KeithL
Administrator 
Posts: 10,256
|
Post by KeithL on Dec 22, 2023 12:36:21 GMT -5
A lot of people seem to have very specific hopes and expectations... I think what a lot of people are looking for is the ability to choose between those presets WITHOUT having to go into the Setup Menu. (You could do that with a single button if you had set up a macro in something like a Logitech Harmony...) We kind of assume that the majority of our customers are going to have only one or two filter sets that they will switch between most of the time. I'll look into that. There is a "dirac" API command in the API docs that's described as "Select speaker DIRAC". I skipped over it because it wasn't clear to me what it would do. But I'll give it a try. I suspect it cycles through the DIRAC configurations. I must be missing something. I am able to choose from the different Dirac filters from within the speaker preset just as I can from the Emotiva OSD. Choose a preset then Equalization and you can choose between User, Dirac 1,2 and 3. |
|
|
|
Post by danielb on Dec 22, 2023 12:43:26 GMT -5
(You could do that with a single button if you had set up a macro in something like a Logitech Harmony...) It's just not that simple, as this is not bidirectional - the macro doesn't know which setting is currently active. A macro can only switch +x or -x but not directly to the desired setting. |
|
KeithL
Administrator
Posts: 10,256
|
Post by KeithL on Dec 22, 2023 12:50:52 GMT -5
I'm afraid I don't know all of the fine details of the API... But I CAN offer a bit of insight there... The API was originally developed to go with the XMC-1. And, on the XMC-1, there are four presets: User1, User2, User3, and Dirac (So, on the XMC-1, you could select each of those directly, or cycle between them.) Whereas on the newer processors, there are two presets, but one User and three Dirac filters in EACH. And, to be honest, I'm not sure exactly how the old API was ported over to the new processors in the context of those options. You can always do anything through the Setup Menu... but some of the "legacy direct access codes" may not work as expected. (It makes sense that the option you mentioned would cycle through the Dirac filter sets in the preset you're currently in... but I wouldn't bet on it.) As I mentioned elsewhere... We did not expect the vast majority of customers to be doing a lot of switching between many different presets. (We figured you'd be setting up one preset for "movies" and one preset for "music"... and then picking the filter you prefer for each.) HOWEVER it is also worth mentioning that, because our menu system is extremely flexible, there are often multiple ways of doing things. For example, if you only listen to music using two speakers, but sometimes prefer room correction, and sometimes "pure stereo direct from the source"... You can set up Preset 2 as your "music" preset... configure it to only use your main front speakers... and select a Dirac Filter set for that preset. And you can then toggle between "Dirac" and "no room correction" while listening to music by switching to Reference Stereo mode... (Because Reference Stereo disables all processing - including Dirac Live.) Google has already activated it. I have installed it and also tried it out. The app is much faster than the IOS App :-) Would it also be possible to select the mode (User, Dirac 1, Dirac2, Dirac3) in the presets? I'll look into that. There is a "dirac" API command in the API docs that's described as "Select speaker DIRAC". I skipped over it because it wasn't clear to me what it would do. But I'll give it a try. I suspect it cycles through the DIRAC configurations. |
|
|
|
Post by leejohn on Dec 22, 2023 19:25:05 GMT -5
The app is working very well for me. Is there a way to choose between processors if you have more than 1?
|
|
|
|
Post by AudioHTIT on Dec 22, 2023 21:59:17 GMT -5
That makes sense to me. If I remember correctly, at least on my RMC-1L, I have a particular DIRAC config associated with speaker preset 1 and no DIRAC config on speaker preset 2. Maybe changing the DIRAC config in real-time requires changing the speaker preset. But maybe that "dirac" API command will change which DIRAC config is assigned to the current preset with a single button? It could also be an API command that only makes sense on older processors. without having to go through the Emotiva settings menu (Menu > Setup Speaker > Preset > Equalization > ... ). Apart from that, the switching process is also agonizingly slow. Or do I simply not know the better/simpler way? I wen't back and looked at the API command set and it doesn't look like that granularity is exposed. |
|
|
|
Post by jpwoodbu on Dec 22, 2023 22:08:14 GMT -5
The app is working very well for me. Is there a way to choose between processors if you have more than 1? Not yet. But there's at least two people now that have said they need it so I'm planning to take a shot at implementing it. |
|
|
|
Post by jpwoodbu on Dec 22, 2023 22:14:05 GMT -5
The app is working very well for me. Is there a way to choose between processors if you have more than 1? Not yet. But there's at least two people now that have said they need it so I'm planning to take a shot at implementing it. A work around, which is crappy, is to put them all into lower power stand-by. The Android app won't be able to turn them on, but you can manually turn on (e.g. with the IR remote) only the processor you wish to control and it should work. |
|
|
|
Post by AudioHTIT on Dec 23, 2023 9:14:38 GMT -5
Not yet. But there's at least two people now that have said they need it so I'm planning to take a shot at implementing it. A work around, which is crappy, is to put them all into lower power stand-by. The Android app won't be able to turn them on, but you can manually turn on (e.g. with the IR remote) only the processor you wish to control and it should work. I looked at the v3 of the docs again when you started this thread, it’s been a while, I was wondering about something the iOS app does with multiple channels, need to look again. I did notice this which you’ve probably seen this, I know there’s at least one user of the iOS app with multiple XMC’s, the user will have to have a different ‘Friendly Name’ for each device. Each emotiva device on the network will respond to the remote device on UDP port 7001. The response packet format is as follows:
<?xml version="1.0"?>
<emotivaTransponder>
<model>XMC-1</model>
<revision>2.0</revision>
<name>Living Room</name>
<control>
<version>2.0</version>
<controlPort>7002</controlPort>
<notifyPort>7003</notifyPort>
<infoPort>7004</infoPort>
<setupPortTCP>7100</setupPortTCP>
<keepAlive>10000</keepAlive>
</control>
</emotivaTransponder> |
|
|
|
Post by jpwoodbu on Dec 23, 2023 9:34:38 GMT -5
A work around, which is crappy, is to put them all into lower power stand-by. The Android app won't be able to turn them on, but you can manually turn on (e.g. with the IR remote) only the processor you wish to control and it should work. I looked at the v3 of the docs again when you started this thread, it’s been a while, I was wondering about something the iOS app does with multiple channels, need to look again. I did notice this which you’ve probably seen this, I know there’s at least one user of the iOS app with multiple XMC’s, the user will have to have a different ‘Friendly Name’ for each device. Each emotiva device on the network will respond to the remote device on UDP port 7001. The response packet format is as follows:
<?xml version="1.0"?>
<emotivaTransponder>
<model>XMC-1</model>
<revision>2.0</revision>
<name>Living Room</name>
<control>
<version>2.0</version>
<controlPort>7002</controlPort>
<notifyPort>7003</notifyPort>
<infoPort>7004</infoPort>
<setupPortTCP>7100</setupPortTCP>
<keepAlive>10000</keepAlive>
</control>
</emotivaTransponder>That's a good point about the friendly name. Maybe I should also display their IP address to disambiguate in that case. A bit of a spoiler, but I'm working on another remote app for Oppo UDP-20X Blu-ray players. And I've started it out with the ability to select any number of devices on the network. So I might borrow some of that code for the Emotiva remote. The current discovery model in the Emotiva remote is to send out a broadcast ping to discover a device and the first one to respond back with a transponder packet wins. My main concern with supporting multiple devices was that I didn't want to force someone with only a single device to go through a selection screen. But since each device on the network will very likely respond within just a few milliseconds, I think what I'll do is "scan" for 1 or 2 seconds, and if only a single device responds, automatically select it. Otherwise, I'll present a list of devices to choose from. |
|
