[Cambridge Audio EDGE A Pronto Code]

For the toggle commands (Power, Mute) the manual "Edge A & Edge NQ Serial Control Protocol v1.1 " says:

Power/Mute/Volume/Source changes in the Edge unit.

• When the power state, mute state, volume level or source is changed in the Edge unit by any means, for example from an IR remote control button press, a Reply message will be sent indicating the new changed state without the external control equipment needing to poll the unit for the current state.
• Volume change messages are not sent for every volume step, only when the volume has stabilised at a new level.

Is this helpfull?

[Cambridge Audio EDGE A Pronto Code]

And with correct spelling ;-)

Cambridge Audio - EDGE A New.json

[SkipApp-0.9.955 with IR Learning - Alpha 6]

Did some recording today: works great. Thank you!

Little problem with the mapping of the custom button: There is no cursor shown in the editable name of it. A bit difficult to insert / clear characters

[Toggle commands: do they, will they or don't they work?]

Hi Jason

There are so many comments on the toggle function (on / off or play / pause). How does the Skip 1s handle this?

Please explain actual situation and your plans about this topic.

Thank you!

[Cambridge Audio EDGE A Pronto Code]

Great!!

I recorded the input channels of the EDGE A from my old Harmony remote: It has A1 - A3, D1 - D5 and Bluetooth.

Unfortunately the D3 Input does not exist on my Harmony remote. Maybe you have another remote with inputs from Cambridge Audio, so I could test, if any command works with Input D3. Or you can reproduce the logic from this list of the channels

All other Inputs are tested and work, so you can add these commands to the existing EDGE A.json.

Thank you

Cambridge Audio - EDGE A New 2.json

[Cambridge Audio EDGE A Pronto Code]

1 hour ago, taeb said:

Hi Jason

Great job for making it possible to record commands :-)

I recorded the following commands with the original remote from Cambridge Audio - see attached file:

NEXT INPUT (RIGHT): works, please replace it in the existing .json for the EDGE A

PREVIOUS INPUT (LEFT): works, please replace it in the existing .json for the EDGE A

POWER TOGGLE: Would work, if you press another button in between pressing it for the next time (Power ON - press any button - Power OFF works). I don't know if a work around for this issue could be to add a delayed code with no effect after powering on / off to make the toggle function work??

MUTE TOGGLE: Would work, if you press another button in between pressing it for the next time (Mute ON - press any button - Mute OFF works). I don't know if a work around for this issue could be to add a delayed code with no effect after muting on / off to make the toggle function work??

Thank you for having a look at it. I'm looking forward to your feedback

Cambridge Audio - EDGE A New.json 7.12 kB · 0 downloads

I just renamed the buttons correctly

Cambridge Audio - EDGE A New.json

[Cambridge Audio EDGE A Pronto Code]

Hi Jason

Great job for making it possible to record commands :-)

I recorded the following commands with the original remote from Cambridge Audio - see attached file:

NEXT INPUT (RIGHT): works, please replace it in the existing .json for the EDGE A

PREVIOUS INPUT (LEFT): works, please replace it in the existing .json for the EDGE A

POWER TOGGLE: Would work, if you press another button in between pressing it for the next time (Power ON - press any button - Power OFF works). I don't know if a work around for this issue could be to add a delayed code with no effect after powering on / off to make the toggle function work??

MUTE TOGGLE: Would work, if you press another button in between pressing it for the next time (Mute ON - press any button - Mute OFF works). I don't know if a work around for this issue could be to add a delayed code with no effect after muting on / off to make the toggle function work??

Thank you for having a look at it. I'm looking forward to your feedback

Cambridge Audio - EDGE A New.json

[Controlling Apple devices with iospirit Remote Buddy]

Another month gone by. Is there any news from iospirit's Felix?

[Cambridge Audio EDGE A Pronto Code]

I created the .json file for the EDGE A. POWER TOGGLE I removed, because POWER ON/OFF work as they should.

MUTE ON/OFF work correctly. To use the button MUTE on the Skip 1s either MUTE TOGGLE (which doesn't work) would be needed, or the button on the remote should be devided in 2 parts as the POWER button on the Skip 1s. Is one or the other solution possible? That's why MUTE TOGGLE is still in the .json file.

With IR Debugging I recorded again INPUT NEXT / PREVIOUS, because it didn't work. I can't understand, why there are always new combinations with every new pressing the button on the original remote. I attached 8 variants of each command, that I recorded. There I need your support.

On 10/27/2023 at 10:26 PM, taeb said:

Another problem: I assigned Power on for the EDGE A and the T+A and after that Programmable Button 1 of EDGE A (so the Amp knows which input to take) to the Power Button of the Skip 1s. In between I set a pause of 10s. Still the 3rd command Programmable Button 1 is not carried out. How come?

This problem I "solved" with reducing the pause in between the commands. Maybe I wasen't patient enough.

Thank you for looking over it.

Cambridge Audio - EDGE A.json Input next:previous.rtf

[Cambridge Audio EDGE A Pronto Code]

I tested the remote again for the Cambridge Audio EDGE A:

Previous and Next Input do not work properly: The 1st time pressing the button works perfect. Next time pressing the same button does not work - after pressing 4 times it works then. Pressing Next and after that Previous works perfect.

I recorded the codes with the original remote in debug mode of Flirc for the codes not working. Can you please check with the attached config file, if everything is setup fine?

Another problem: I assigned Power on for the EDGE A and the T+A and after that Programmable Button 1 of EDGE A (so the Amp knows which input to take) to the Power Button of the Skip 1s. In between I set a pause of 10s. Still the 3rd command Programmable Button 1 is not carried out. How come?

commands Cambridge Audio EDGE A.rtf config skip 1s.rtf

[Cambridge Audio EDGE A Pronto Code]

Nice. Is there a manual how to use it?

[Cambridge Audio EDGE A Pronto Code]

Hi Jason

Thank you for working on it.

I have already 2 Flirc USB. An idea of me is, that Flirc USB could listen to my Harmony Remote or any other and produce a Pronto code we could use for the Skip 1s.

[Recording commands with original remote]

It's some time ago that there was the question, if there is a possibility to record commands with an original remote to produce .json files for devices.

Is it possible, if yes, how?

If no, is it planed and when will it be possible?

Thank you!

[Cambridge Audio EDGE A Pronto Code]

Does anybody has the Pronto Code of the EDGE A?

Since months I'm not able to use my Skip 1s.

[T+A DAC 8 not in your list]

Hi Jason

I know, you work hard. But my requests are unanswered for months now. Should I ask you every day the get answer?

[Controlling Apple devices with iospirit Remote Buddy]

Hi Jason

I know, you work hard. But my requests are unanswered for months now. Should I ask you every day the get answer?

[Controlling Apple devices with iospirit Remote Buddy]

Hi Jason

I would like to use the Skip 1s. On my Mac I use Audirvana for music playback. This app needs Remote Buddy. Without that, the Skip 1s is not able to control Audirvana. When will this be possible?

[Cambridge Audio EDGE A support]

Hi there

My remote is near my Mac, because I hope I can use it soon after an update.

Until now it's for months not possible to use it, because my amp can't be controlled with the Skip 1s. There are several commands missing. Whan can I hope to use my remote?

[T+A DAC 8 not in your list]

Hi Jason

Did you find a solution?

[Wizzard shouldn't remove manually assigned commands from buttons]

SkipApp 09.92: When I change an activity with the wizzard, all manually assigned commands are removed from the buttons. This makes only sense for removed devices, but not for still existing devices. Please save the manually assigned commands, so we don't have to assign them again and again.

[Remote does nothing after syncing]

I notice the same problem: batteries are empty very soon with very little use. Does it use current, when it's not used?

[T+A DAC 8 not in your list]

Hi Jason

I just tested the new .json file: Thank you!

The Volume works now.

The Power Toggle works not yet as it should.

What I found out: When I press the Power button once, it works. Pressing it the second time, it doesn't work. But it works if I press another button before pressing the Power button the second time. It seems to me, that the T+A needs something like a clearing to be able to work with the toggle command for the second time.

Thought about the toggle function in general: The Power button on the remote is divided in On and Off. Would it be possible to give this option to every button? This would solve the problem of flipping back and forth with other commands, as we have it for the T+A and maybe other devices. The second function of a button would only be executed, if there exists a command. If empty, the button works normal.

Looking forward to your answer.

[Buttons Panel: more detailed icon for central wheel]

Hi there

In the buttons panel, we have 1 icon for 5 buttons. To make easier to see where a command is assigned to, I propose 5 different icons that put the button in gray, that is used for a specific command.

[Controlling Apple devices with iospirit Remote Buddy]

Have you any news from Felix?

[Skip app - CMD-Q]

I already asked the same question. All shortcuts on Mac are grayed out and don't work.