Print

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

[Belarathon]

I looked at the MC Core command wiki page, but didn't see anything.  I am wondering if it is possible to toggle EQ presets, or at least toggle the equalizer on/off from a remote control.  I use an Emotiva XDA-2 as a preamp, and have no means to adjust tone.

Help?

[Matt]

The equalizer is not currently exposed through MCWS.  You can access it through the COM SDK, but that's pretty involved.

I'll consider adding support in the future.  Please +1 if you want it too.

[bblue]

+1

[Matt]

Next build:
NEW: Added MCWS/v1/DSP/Set function for turning a DSP on or off.

[Belarathon]

+1

You are the best!  I somehow get the feeling that a hardware EQ, with its numerous pots and opamps, would be more lossy than your internal EQ.

[fitbrit]

+1

And a +1 to the notion that you (guys at JRiver) are the best!

[Hilton]

+1 - wanted this a long time ago as well as the ability to toggle other DSPs on/off by remote to make it more family friendly.

[mwillems]

If this will be able to target specific DSP modules (i.e. turn convolution on or off), it could be used for ABX testing, which would be neat. 

+1 regardless.

[rec head]

Awesome

[ken-tajalli]

+1

[Belarathon]

I see you've included the change in your latest build.  Any documentation yet, or too early?

[Matt]

I see you've included the change in your latest build.  Any documentation yet, or too early?

MCWS is self-documenting.  Visit it in a browser.  On your local browser it'll be:
http://localhost:52199

[bblue]

MCWS is self-documenting.  Visit it in a browser.  On your local browser it'll be:
http://localhost:52199

Under DSP->Set->Examples->Click Here

I get

<Response Status="Failure"/>

[Matt]

Under DSP->Set->Examples->Click Here

I get

<Response Status="Failure"/>

You need to add DSP and On.

For example:
http://localhost:52199/MCWS/v1/DSP/Set?DSP=Equalizer&On=1

[Belarathon]

MCWS is self-documenting.  Visit it in a browser.  On your local browser it'll be:
http://localhost:52199

I'm at work now, but can't wait to get home to check it out.

Nice to have you back Matt!

[retro]

+1

[bblue]

You need to add DSP and On.

For example:
http://localhost:52199/MCWS/v1/DSP/Set?DSP=Equalizer&On=1

Ok. 

1. Since status of DSP's is specific to a zone, shouldn't we have a method of setting the zone:
            Parameters:
               Zone: The zone the command is targetted for. (default: -1)
               ZoneType: The type of value provided in 'Zone' (ID: zone id; Index: zone index; Name: zone name). (default: ID)
    Currently it seems to respond only to the first zone defined.

2. as well as a function to list the DSP's and their current state in that zone?  (including VST's)

3. A command given without a Set=x is taken as 0 (off).  Is that correct behavior?  I may do that on all Sets, I don't usually leave them out.

4. It looks like the on/off status of a given DSP is not shown in the DSP Studio panel unless you open it fresh or until you close/reopen it.  At the very least this would come in handy if you were monitoring the state of changes at they were being made for debugging or whatever.

5. Also, it does not recognize VST's that are installed in the DSP Studio.  Can those be added?

And more in the wishlist department might be the ability to select a preset of a given DSP, and include the active preset in the DSP list (if possible).

Thanks for adding this capability.  One step closer to Nirvana!

[Belarathon]

If this is still Greek to you, I was able to add two new button assignments to my learning remote with the following command lines:

[Belarathon]

Strangely enough, the changes don't take effect until there's been some sort of windows state change...minimizing, maximizing, etc.  You can open the DSP and verify that it's been toggled/untoggled, but no change in sound until a window change.

[Belarathon]

FIXED.   

[bblue]

Ok. 

1. Since status of DSP's is specific to a zone, shouldn't we have a method of setting the zone:
            Parameters:
               Zone: The zone the command is targetted for. (default: -1)
               ZoneType: The type of value provided in 'Zone' (ID: zone id; Index: zone index; Name: zone name). (default: ID)
    Currently it seems to respond only to the first zone defined.

2. as well as a function to list the DSP's and their current state in that zone?  (including VST's)

3. A command given without a Set=x is taken as 0 (off).  Is that correct behavior?  I may do that on all Sets, I don't usually leave them out.

4. It looks like the on/off status of a given DSP is not shown in the DSP Studio panel unless you open it fresh or until you close/reopen it.  At the very least this would come in handy if you were monitoring the state of changes at they were being made for debugging or whatever.

5. Also, it does not recognize VST's that are installed in the DSP Studio.  Can those be added?

And more in the wishlist department might be the ability to select a preset of a given DSP, and include the active preset in the DSP list (if possible).

Thanks for adding this capability.  One step closer to Nirvana!

First, thanks to JR for the addition of #1 above regarding zones, and also #4 showing the status as it changes.

At the very least, what about VST plugins?  Are there plans to support them similarly to the other DSP plugins (my #5)?  Sure would be a help.  My other VST related suggestions may require more work than they're worth, but are they even a possibility?

--Bill