KVR :: Muse Research and Development » Remote Control broken after Mac OS 10.6.5 [View Original Topic]
There are 22 posts in this topic.

---

wurlie - Sun Nov 14, 2010 5:05 pm

---

Has anyone else been able to connect to their Receptor 2 via remote control after updating Mac OS to 10.6.5?

Not 100% saying that the OS update is what caused it, but after updating when I launch Receptor Remote Control, my receptor is not being recognized and consequently I'm not able to connect to the drive or the remote viewer.

If someone chimes in who IS able to connect after the 10.6.5 update, let me know so I can focus my troubleshooting efforts elsewhere.

(for the record everything in my setup was working fine before the update)

thanks in advance





MacBook Pro 10.6.5 2.66 GHx Intel Core 2 Duo 4 GB ram Receptor 2 PRO sys vers. 1.8.20100924
Receptor Tools vers. 1.3.20090817

---

TWB121234 - Sun Nov 14, 2010 7:37 pm

---

I just updated, read this, and tried to load the Receptor viewer - no go. I wish I had read this prior to updating. Hopefully Muse will get on this quickly.

---

Kevin@MuseResearch - Mon Nov 15, 2010 10:49 am

---

Receptor users should NOT update their MAC OS right now, no matter which version of Mac os they're using (10.4, 10.5, or 10.6) It looks like this is a security update released for all mac platforms.

if you already installed the update you can connect to Receptor viewer using this third party app:

http://sourceforge.net/projects/cotvnc/

Just type in Receptor's ip address and the password "Receptor". (please note the capitalization). The rest of the default settings for profile and display do not need to be changed. If you want the system will save your Receptor's ip connection and password info.

There is not a work around for Direct Install at this time.
We are working on a solution as fast as possible.

- Kevin

---

TWB121234 - Mon Nov 15, 2010 12:42 pm

---

Thanks Kevin -

---

Kevin@MuseResearch - Mon Nov 15, 2010 12:56 pm

---

For those who want a little bit more thorough explanation of how to use this (with pictures!) you can check out the following help desk article: http://www.plugorama.com/kb.php?id=440

---

wurlie - Mon Nov 15, 2010 3:32 pm

---

Kudos to Kevin for being on this immediately!!!

I was perplexed over the weekend when I noticed this had happened.

Kevin's solution, for me, worked perfectly and without incident. Uniwire working as expected as well.

Shoulda known better than to immediately update my OS.

Oh well, all good for now.

---

batgab - Fri Dec 03, 2010 11:29 pm

---

In order to get this to work on a Receptor 1 Rev C, it seems you need to enter an "abbreviated" version of your Receptor's IP address; e.g, 18.0.3.5:5901 instead of exactly what the Receptor front panel display shows (e.g. 018.000.003.005).

Also, for Receptor 1 users only, don't forget to append the :5901 (like I did )!

---

rexrecord - Tue Jan 11, 2011 3:56 pm

---

any news about this issue???a really need the direct install

---

rexrecord - Mon Jan 17, 2011 12:45 pm

---

toc,toc...i'm totally stopped here;i need to see the receptor on my mac to do my job...not for fun.
please find a solution

---

Kevin@MuseResearch - Mon Jan 17, 2011 5:04 pm

---

rexrecord,

Did you see the link for the workaround:

http://www.plugorama.com/kb.php?id=440

This uses a 3rd party vnc app wo you can still see Receptor while we work on a fix. If you have any trouble figuring out how this works just open a support ticket at our help desk.

- Kevin

---

rexrecord - Tue Jan 18, 2011 1:17 am

---

i can see receptor by the apps you posted but
i can't use direct install and cubase doesn't see receptor as uniwire plugin....

---

Kevin@MuseResearch - Tue Jan 18, 2011 12:55 pm

---

This may be an unrelated issue, or easily solveable. If Uniwire isn't showing up in Cubase, then perhaps Cubase isn't looking in the correct directory for the plugin, or needs to have it's plugin list refreshed.

If Uniwire IS showing up in cubase and displaying "no receptors found" when you try to use it then manually entering the ip address may work. You can do this by clicking on the grey box that says "no receptors found" and selecting "Manual IP". Then find Receptor's IP by going to the "Setup" page on Receptor viewer.

- Kevin

---

aerodisccorp - Sun Feb 06, 2011 5:53 am

---

Fix for Receptor Remote Control Broken after 10.6.5 update:

Here's an easy fix that worked for me.

Open the applications folder containing Receptor Remote Control. Either Control-Click or Right-Click on the Receptor Remote Control application icon. Select Get Info.

Under the "General" tab near the top (if General is not open click on the triangle to its left) click so there is a checkmark next to "Open using Rosetta". The next time you open the Receptor Remote Control application, you should be able to use it again normally.

---

batgab - Sun Feb 06, 2011 3:10 pm

---

Hey, how 'bout that - it does work! It appears this is a Mac-only solution, right? Just want to mention that in case Windows users are trying to figure out what you're talking about.

---

JayVee - Sun Feb 06, 2011 6:41 pm

---

Nice ~ okay, what about accessing the Receptor Hard Drive, does it that option also?

---

aerodisccorp - Mon Feb 07, 2011 3:00 pm

---

Yes! By changing the application to "Open using Rosetta" (as I explained above) I am able to click on "Receptor Drive" to open up a Mac Finder window and view the Receptor Hard Drive contents just like always. I haven't tested doing a plugin install yet but I have no reason to think it won't work. I HAVE VERIFIED that I can drag files in and out of folders on the Receptor.

Obviously, I can also view the Receptor Screen on the Mac as well.

Try It!

—Jeff
(Mac OS 10.6.6)

---

JayVee - Tue Feb 08, 2011 5:38 pm

---

Great!
Thanks!
Tell the techs @ Muse.

---

Kevin@MuseResearch - Tue Feb 22, 2011 10:58 am

---

For all those affected by this bug:

There is a new update to Receptor tools for mac that fixes this problem. It can be found at www.museresearch.com/updates.php

Thanks for your patience over the past few months as we developed the fix for this problem.

- Kevin

---

looneytunes - Wed Feb 23, 2011 4:02 pm

---

Hi Kevin,

I get a couple of privilege dialog boxes when trying to invoke the Receptor viewer (asking permission to look at some cotvnc ("Chicken of the VNC") files. Selecting allow on all these dialogs, the viewer will eventually come up. DirectInstall also seems to launch.

If I hit the button to for "Receptor Drive", I get an error saying "Unable to find the Receptor drive. Please check your connections and try again." (Not too big a deal, I can still get to my drive via Samba).

I did verify that I was running the correct version.

This is on Mac OS 10.6.6

Glad to see this 'mostly' working!

Thanks,
Kevin L

---

looneytunes - Fri Feb 25, 2011 5:07 pm

---

Hi Everyone,

I think (for whatever reasons) this was an installation issue. After rebooting my Mac, I tried to connect to my Receptor Drive from the remote software again today, and this time it came up without issue.

Everything looks back to normal now.

Kevin L

---

Jace-BeOS - Mon May 07, 2012 9:14 am

---

So, on a MacBook Pro... Not only does the Receptor Remote Control app still do nothing on 10.6.8, because Muse hasn't updated the thing at all to fix the problem (dudes, you're several operating systems LATE on both platforms), i also cannot seem to get Chicken of the VNC to access it either ("Connection refused: connect()"). WTH? Crossover ethernet cable. UniWire works in Logic, but of course i can't view the Receptor interface. Mac OS can access the drive through the usual file sharing methods, but no freaking remote control. (There's no firewall blocking the app)

The follow-through on this thing reminds me of Alesis' Fusion (great idea, never finished, sold anyway, users abandoned). i'm an expert at buying products like this.

---

Jace-BeOS - Thu May 10, 2012 11:42 am

---

UPDATE: MY FAULT on Chicken of the VNC connection failure. Wrong port (Receptor 1). Sorry! (but the Receptor Remote Control software still doesn't work)

i'm grouchy about this because of the OS updates having stopped at 1.7 on this model, so whenever i have issues, that comes out.

---

There are 22 posts in this topic.