mount receptor Rev C on macbook pro retina mavericks?
-
- KVRer
- 4 posts since 29 Jun, 2007
Hi
I have a brand new macbook running mavericks and a old receptor 1 Rev C with the blue facia. The OS is up to date (I think) - 1.7.20080616.
I'm trying to mount it on my desktop with the Receptor drive function in remote control but it won't connect. The error message says the version of the server I'm trying to connect to is not supported.
Also - I was hoping to make uniwire work too, but when I click enable uniwire on the receptor it just clicks off again.
Am I simply just trying to connect one decade to another? Do I need a time machine?
Most support docs I can find seem to stop at around OS 10.5
I should mention that all this has worked in the past on my knackered old G5.
Any ideas?
Much appreciated.
I have a brand new macbook running mavericks and a old receptor 1 Rev C with the blue facia. The OS is up to date (I think) - 1.7.20080616.
I'm trying to mount it on my desktop with the Receptor drive function in remote control but it won't connect. The error message says the version of the server I'm trying to connect to is not supported.
Also - I was hoping to make uniwire work too, but when I click enable uniwire on the receptor it just clicks off again.
Am I simply just trying to connect one decade to another? Do I need a time machine?
Most support docs I can find seem to stop at around OS 10.5
I should mention that all this has worked in the past on my knackered old G5.
Any ideas?
Much appreciated.
-
- KVRer
- Topic Starter
- 4 posts since 29 Jun, 2007
Thanks for your reply hopkihc, but its exactly the same problem. Server not supported.
I wonder if there's some protocol I need to download in order for Mavericks to support the receptors server?
I wonder if there's some protocol I need to download in order for Mavericks to support the receptors server?
-
- KVRist
- 209 posts since 18 Aug, 2009
Oh dang... Yeah I think this is an issue for older receptors, where the protocol isn't compatible with apple's implementation.
I have no idea if this will work, but
http://hints.macworld.com/article.php?s ... 2083837447
I have no idea if this will work, but
http://hints.macworld.com/article.php?s ... 2083837447
-
- KVRist
- 209 posts since 18 Aug, 2009
I'd also refer you to this thread:
http://www.kvraudio.com/forum/viewtopic.php?t=336094
and this technology backgrounder:
http://www.zdnet.com/mavericks-smb2-pro ... 000022519/
which re-states the above suggested solution.
Hope this works for you!
http://www.kvraudio.com/forum/viewtopic.php?t=336094
and this technology backgrounder:
http://www.zdnet.com/mavericks-smb2-pro ... 000022519/
which re-states the above suggested solution.
Hope this works for you!
-
Bryan@MuseResearch Bryan@MuseResearch https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=9067
- MUSEician
- 618 posts since 18 Sep, 2003 from Silicon Valley
In our defense, it is the MacBook that discarded support for earlier versions of Samba, not the other way around. Unfortunately, you can no longer connect to your Rev 1 Receptor with a new Mac due to the changes in their OS, but you can certainly connect using a Windows machine, or an older Mac OS version. We didn't change a thing.
We're not alone... dozens of NAS (network attached storage) systems use Samba, and you can't connect to those with the new Macs either.
Maybe Apple will introduce a fix to re-instate connectivity with previous versions of Samba? Reminds me of a Supertramp song: "Dreamer... You know you are a Dreamer... "
Bryan
We're not alone... dozens of NAS (network attached storage) systems use Samba, and you can't connect to those with the new Macs either.
Maybe Apple will introduce a fix to re-instate connectivity with previous versions of Samba? Reminds me of a Supertramp song: "Dreamer... You know you are a Dreamer... "
Bryan
-
- KVRist
- 209 posts since 18 Aug, 2009
Bryan,
Apologies. I realize my post reads as if the Receptor was the issue here, which was not my intent. And yeah, that's one of those Apple decisions that's kind of a head-scratcher.
-John
Apologies. I realize my post reads as if the Receptor was the issue here, which was not my intent. And yeah, that's one of those Apple decisions that's kind of a head-scratcher.
-John
-
Bryan@MuseResearch Bryan@MuseResearch https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=9067
- MUSEician
- 618 posts since 18 Sep, 2003 from Silicon Valley
Actually, someone did come up with a great suggestion to install Windows on the Mac using Bootcamp, and boot in to that when you need to connect to the Receptor. Clever? Yes. Practical? Perhaps not.
And I'm sorry if I came off offended, but to be perfectly honest, no one from Apple contacted me to see if it would be okay if they changed their OS, so well, maybe I am a little honked-off about this...
Bryan
And I'm sorry if I came off offended, but to be perfectly honest, no one from Apple contacted me to see if it would be okay if they changed their OS, so well, maybe I am a little honked-off about this...
Bryan
- KVRAF
- 6113 posts since 7 Jan, 2005 from Corporate States of America
Teah, well, I'm honked-off that original Receptor owners have no upgrade path to newer Receptor operating systems...
- dysamoria.com
my music @ SoundCloud
my music @ SoundCloud
-
Bryan@MuseResearch Bryan@MuseResearch https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=9067
- MUSEician
- 618 posts since 18 Sep, 2003 from Silicon Valley
I don't know what to tell you, Jace. Rev Cs are now 6+ years old, and you simply can't run the more modern OS on the older HW. Believe me, if it was possible, we'd make it available. Even if you COULD run the new OS on the old HW, you'd still have tons of plugin compatibility issues since a lot of the new plugins require dual core processing and 4GB of RAM. So it doesn't make sense to try to get the new OS working in the old hardware.
I have an older MacBook sitting in my desk drawer that I paid $3000 for. It can't be upgraded. I can't trade it in. I can't run any modern software on it, so it's basically worthless. At least your RECEPTOR Rev C is worth $400 towards the purchase of a new VIP. Or, you could have the unit "repaired" with Receptor 2 parts and bring it up to modern standards that way. However, given the choice of spending $1000 to get a Rev C up to Receptor 2 spec, I'd rather trade my in and get into the 64-bit OS that is in the VIP. So you do have options available.
Bryan
I have an older MacBook sitting in my desk drawer that I paid $3000 for. It can't be upgraded. I can't trade it in. I can't run any modern software on it, so it's basically worthless. At least your RECEPTOR Rev C is worth $400 towards the purchase of a new VIP. Or, you could have the unit "repaired" with Receptor 2 parts and bring it up to modern standards that way. However, given the choice of spending $1000 to get a Rev C up to Receptor 2 spec, I'd rather trade my in and get into the 64-bit OS that is in the VIP. So you do have options available.
Bryan
- KVRAF
- 6113 posts since 7 Jan, 2005 from Corporate States of America
Mine is a revision B. doesn't matter how old it is now. It was abandoned only a couple years after I bought it. $400 discount on trade-in isn't enough to make it worthwhile for me, since I'm poor.
If the OS were upgradable (which Muse claimed was the case back when a drive exchange program was being talked about here on KVR... and then quietly shelved), I'd at least have network compatibility with my Macs. I don't care about plugins that require dual core, etc. If I use my Receptor at all, at this point, it'll be for running Windows-only plugs I can't use on my Macs. But since it doesn't support mono VST plugins, and since the thing is so loud (as loud as, or louder than, my Akai S6000), I rarely have it running anyway.
Overall, I think I wasted my money on it, because it doesn't really serve as a "Windows-only VST player" for my Mac music environment. Continued OS upgrade support was the last line of hope there, and that ended with 1.7. I start it up now and then to keep the drive functioning, or to try out sounds on older plugs, but I lose interest fast with the fan noise. Since the uniwire plugin was dumped, my plan to relocate the Receptor to another room and use it from a distance has also been trashed. Knowing the hard drive can't be user-replaced when it fails... I'm not too eager to rely on it either.
In my experience, Receptor is just another proprietary computer that punishes owners with upgrade/software incompatibility. Not a piece of independent hardware. Lesson learned.
If the OS were upgradable (which Muse claimed was the case back when a drive exchange program was being talked about here on KVR... and then quietly shelved), I'd at least have network compatibility with my Macs. I don't care about plugins that require dual core, etc. If I use my Receptor at all, at this point, it'll be for running Windows-only plugs I can't use on my Macs. But since it doesn't support mono VST plugins, and since the thing is so loud (as loud as, or louder than, my Akai S6000), I rarely have it running anyway.
Overall, I think I wasted my money on it, because it doesn't really serve as a "Windows-only VST player" for my Mac music environment. Continued OS upgrade support was the last line of hope there, and that ended with 1.7. I start it up now and then to keep the drive functioning, or to try out sounds on older plugs, but I lose interest fast with the fan noise. Since the uniwire plugin was dumped, my plan to relocate the Receptor to another room and use it from a distance has also been trashed. Knowing the hard drive can't be user-replaced when it fails... I'm not too eager to rely on it either.
In my experience, Receptor is just another proprietary computer that punishes owners with upgrade/software incompatibility. Not a piece of independent hardware. Lesson learned.
- dysamoria.com
my music @ SoundCloud
my music @ SoundCloud
