ARCHIVED FORUM -- March 2012 to February 2022READ ONLY FORUM
This is the second Archived Forum which was active between 1st March 2012 and 23rd February 2022
Short story: took two weeks to get Playmaker to play. It now works fine, but it took the weirdest trick in order to get it to work.
Ordered a brand new Playmaker together with some "demo" BeoLab 4's from a B&O corporate-owned store. Connected directly to the Playmaker, gave it the password to our home network (which uses a full-size Apple AirPort/Time Capsule router). The Playmaker connected to our home network. Went to an iPhone, hit Airplay, the status lights on the BL 4's went from red to green... and silence.
You could see the song "playing" on the iPhone, as the timer continued to run. You could hear the BL 4's make slight noise as the volume was increased from a Beo4. But no song was played.
Tested the BL 4's on our home Master Link network (2 audio masters, three rooms), those work fine.
Connected the Playmaker to a pair of BeoLab 6000, same symptom: status light went from red to green when "playing", but no sound. Mute/volume sensors on Playmaker seemed to work, but to no effect.
Dealer blamed the AirPort! Said they use Cisco. Well, guess what, we have a Cisco RV220W at the boat, so on the weekend I went and got it.
Exact same thing happened: green light on AirPlay play, but no sound.
Tried called the dealer on a Sunday, got voicemail.
At this point, I was pretty upset. But I still wanted to listen to the new setup. So I plugged an RCA Line-In from an iPad and into the Playmaker.
The Playmaker sputtered for a couple of seconds... and started to play. Well, I removed the RCA and hit AirPlay... and it played.
Feeling on a roll, I reset the Playmaker and again had it join our normal home AirPort... and it plays!
Look, I was very methodical and tried every possible option. I find it ridiculous that the software or the hardware had some sort of bug and it took an RCA connection to get the thing to work.
I still wonder... why did the Playmaker sputter when the Line-In came in? It's a digital device. "Sputtering" should never be part of the equation.
Hello Sir
I think you accidently hit the center touch Mute function on the Playmaker.
BEOCET: I think you accidently hit the center touch Mute function on the Playmaker.
You raise a possible scenario. But in fact one of my several tests was, in fact, to turn on the mute button and afterwards to unmute it, of which there are three ways, if I now recall correctly:
1. Press it again (unmutes)
2. Increase the volume by touching the touch wheel (unmutes)
3. Increase the volume by increasing the volume on the Beo4 (unmutes).
So I do not think that the mute button was the problem.
I am struggling right now too with the playmaker.
Noted It is clearly some sort of incompatibility with my wireless hotspot that I recently changed out but am not willing to update that thing again I rather reboot mi playmaker daily then jumping through hoops.
That just seems to be the nature of the game these days. stuff just doesnt always work. i started buying less and less for that reason, is just not worth going through the hassle for a lot of things.
Enjoy your playmaker, glad it worked out for you.
cheers
JK
The problem here lies with Airplay and not the Playmaker. So in that sense your dealer is correct blaming the wifi router.
The amount of data needed to be transferred during Airplay is quite large, so when using a wireless play device (iPhone) and playback device(Playmaker), then the stress on the network is doubled compared to a hard wired Playmaker.
Glitch free Airplay requires a really stable and high bandwidth capable wifi network. This is rarely easy to achieve! Often it requires setting a fixed IP for the devices used, and give them priority on the network. Its also really important to use the bands with the least amount of interference. This is especially important when living in an urban environment where wifi-networks overlap big time.
I too had some really annoying problems with my A9 using Airplay. Changed my router, and tweaked my setup. This almost eliminated the problems, but not entirely. After Spotify Connect was introduced to the A9, I've never had any problem with playback. Which again points to Airplay as the culprit!
An easy solution would be if Apple released a N-network enabled Airplay chip. Currently this is only possible for Apples own devices, and all Airplay products from 3rd-party manufactures are forces to use the same Airplay chip, which at the moment only supports the much overcrowded and bandwidth limited g-network.
Beovision Eclipse gen2 (GX) w/ floorstand, Beolab 14.2, 4 speaker Shape and ATV4/Chromecast.
Beoplay A9mk4 GVA, Beosound 1 GVA, H2, H3, H8, E6, Beoplay EQ
Mikael: The problem here lies with Airplay and not the Playmaker. So in that sense your dealer is correct blaming the wifi router. The amount of data needed to be transferred during Airplay is quite large, so when using a wireless play device (iPhone) and playback device(Playmaker), then the stress on the network is doubled compared to a hard wired Playmaker. Glitch free Airplay requires a really stable and high bandwidth capable wifi network. This is rarely easy to achieve! Often it requires setting a fixed IP for the devices used, and give them priority on the network. Its also really important to use the bands with the least amount of interference. This is especially important when living in an urban environment where wifi-networks overlap big time. I too had some really annoying problems with my A9 using Airplay. Changed my router, and tweaked my setup. This almost eliminated the problems, but not entirely. After Spotify Connect was introduced to the A9, I've never had any problem with playback. Which again points to Airplay as the culprit! An easy solution would be if Apple released a N-network enabled Airplay chip. Currently this is only possible for Apples own devices, and all Airplay products from 3rd-party manufactures are forces to use the same Airplay chip, which at the moment only supports the much overcrowded and bandwidth limited g-network.
First of all you don't need a fixed IP for AirPlay to work. AirPlay doesnt even rely on IP-adresses but instead multicast DNS (Apple Bonjour) so just scratch that idea. Apple released the first AirPort Express in 2004, it featured the same wifi audio which was then called AirTunes, now AirPlay. It was a 802.11g (54Mbit) unit with a quite slow processor. And it worked GREAT. I have used several for many years without any issues what so ever. Now we have both 802.11g and 802.11ac with up to gigabit wifi speeds and now, ten years later people have problems with the Playmaker. No, the problem is not the router (if it is a Time Capsule/AirPort Extreme for example, which I use myself and that works great). The problem is very much probably in the Playmaker - or of course related to distance to the router, thick walls or such. I have a Beolit 12 and it features a very old 802.11g chips and probably has quite a small buffer for the streamed music so it can easily hick up but usually works quite good. Biggest problem is that it can lower the speed of the overall network (all my devices is 802.11n or 802.11ac today except for the beolit).
Apple don't design wifi chips and they have moved on to 802.11ac in their computers. AirPlay is software. I guess B&Os implementation of it is poor. You say that Spotify Connect works good - this makes this assumption even more realistic since Spotify Connect is a program running directly on your A9 instead of your iPhone sending the music (just controlling it). The best solution I can recommend is to connect the playmaker to ethernet instead of wifi or exchange it for perhaps an Airplay express connected via A.AUX to a Beosound-unit. B&O retailers often rely on telling people to replace their routers with a Cisco router. I think they should fix their hardware and software instead of telling people to buy new routers.
Beolab 50, Beolab 8000 x 2, Beolab 4000 x 2, BeoSound Core, BeoSound 9000, BeoSound Century, BeoLit 15, BeoPlay A1, BeoPlay P2, BeoPlay H9 3rd Gen, BeoPlay H6, EarSet 3i, BeoVision Eclipse Gen 2 55", BeoPlay V1-40, BeoCom 6000 and so much else :)
That might be true, but the fixed IP are needed if you want to prioritise some device on the network.
Since 2004 the quality of streaming and number of features have change drastically. You can't really compare a 2004 protocol with a 2014 protocol.
Im not saying the Airport router is the problem, but the setup (setup also included distance to devices etc.). I too use a Airport Extreme and that have fixed most of my issues. As I mentioned in my previous post, Airplay devices doesn't support N or AC, only G. The only exception to this are the AppleTV and Airport Express. Every manufacture of 3rd party Airlplay devices are forces to use the same Airplay chip. It's true that Apple doesn't make the chips, but if you want that "Airplay" badge on your package, then you have no choice.
When I still used Airplay to stream music to my A9 there was a huge difference is stability between my iPhone 5 and laptop. My iPhone had serious hick ups in the sound, while it never happened when using my laptop. So blaming the Playmaker is just too easy! And don't jump to the conclusion that the Playmaker is the culprit just by hard wiring it to the network. This might seem as the case, but remember that you at the same time half the amount of data transferred over wifi.
The main difference between Spotify Connect and Airplay is the amount of data needed to be transferred over WIFI. Spotify Connect allows the A9 to stream the music directly from Spotify, while Airplay requires the music to be streamed to the iPhone and then pushed to the A9, i.e. double traffic. Everything I've seen points to bandwidth problems.
Mikael: The problem here lies with Airplay and not the Playmaker. So in that sense your dealer is correct blaming the wifi router.
Thank you for your extended comments.
Unfortunately, I cannot agree with your comments. The Playmaker now works flawlessly with our AirPort Base Station/Time Capsule router; but for two weeks, it refused to perform at all under this same setup.
Also, the Playmaker failed to work with our Cisco RV220W wireless that I brought from the boat on the advice of B&O. The Playmaker only began to work on the Cisco after an Aux-In was plugged into the Playmaker. Immediately after sound was first produced via the Aux-In, AirPlay on the Playmaker subsequently began to work on the Cisco RV220W.
And afterwards, AirPlay on the Playmaker has worked just fine on our regular AirPort Base Station/Time Capsule router.
I do not agree to the above.
From personal experience my conclusion is that these are Playmaker issues, and not general Airplay issues. Maybe when you are lucky, and live in a free standing house with cardboard walls and no neighbours, you are able to get it working reasonably stable. But I haven't succeeded, as a network professional, with enterprise class cisco wireless equipment. Migrated to Sonos, no issues whatsoever. Also using an Appletv, airplay without any issues, exactly the same environment, never lost one single connection, and never had the airplay button unavailable on any device. It just works. And that should be the case with the playmaker also.
Regarding the fixed ip-address, tried that, although knowing it could not make a difference, and it didn't. Only thing that helped whas rebooting the Playmaker (again)
I spent a few months troubleshooting the issues. My advice now would be to spend max a week on issues, and migrate to something that works if not solved completely. Playmaker has very basic functionality, and there are plenty alternativs.
Joost
BeoVision 11-55, BeoLab 8000, BeoRemote One BT, AppleTV 4, 2x BeoPlay A2, BeoPlay A1
Michael: Apple released the first AirPort Express in 2004, it featured the same wifi audio which was then called AirTunes, now AirPlay. It was a 802.11g (54Mbit) unit with a quite slow processor. And it worked GREAT. I have used several for many years without any issues what so ever. Now we have both 802.11g and 802.11ac with up to gigabit wifi speeds and now, ten years later people have problems with the Playmaker.
Apple released the first AirPort Express in 2004, it featured the same wifi audio which was then called AirTunes, now AirPlay. It was a 802.11g (54Mbit) unit with a quite slow processor. And it worked GREAT. I have used several for many years without any issues what so ever. Now we have both 802.11g and 802.11ac with up to gigabit wifi speeds and now, ten years later people have problems with the Playmaker.
I agree with this. As much as I like my Playmaker, I never had any streaming issues with the previous Airport Express, in the same environment, as I do with my Playmaker. The sound quality is certainly improved on the PM, but I get all kinds of dropouts, particularly when two of us are in the same room (seriously...).
I live in a high rise so my wifi bandwidth is certainly crowded. I do not have issues with drop outs and sound quality is good.
And I second that the Apple TV that I use in my other home works without glitches too.
WISA should certainly improve things, but those guys have no multi room yet and leave open the connection from "device" to the transceiver
Cheers
To be honest, I bought one of the first Playmakers in Australia when it was released, and I never managed to make it work in wi-fi!
I gave up and used an Ethernet cable, and in less than a minute, all was working perfectly, and I've never had to change any setting since day 1.
Besides, the wired option makes updates much more possible! Not to mention the absence of dropouts.
I've never gone wireless on most of my devices, because it is so frustrating when it works on Monday and stops working on Tuesday without any reason.Still a lot to improve in my opinion.
.
Christophe : To be honest, I bought one of the first Playmakers in Australia when it was released, and I never managed to make it work in wi-fi! I gave up and used an Ethernet cable, and in less than a minute, all was working perfectly, and I've never had to change any setting since day 1. Besides, the wired option makes updates much more possible! Not to mention the absence of dropouts. I've never gone wireless on most of my devices, because it is so frustrating when it works on Monday and stops working on Tuesday without any reason. Still a lot to improve in my opinion.
I've never gone wireless on most of my devices, because it is so frustrating when it works on Monday and stops working on Tuesday without any reason. Still a lot to improve in my opinion.
Page 11 of the PM manual (English) states that this is the most preferable way to setup the PM.
Chipping in, my view is that for my setup, Wni8.1/WMP12/PM and an old (2010 modem) WMP12 with "play to" works perfectly, zero drop-out and crystal clear clarity. The functionality though needs a Beo4 and "Play to" is clunky.
Using same combo for PC/Modem but using Beoplayer/Airfoil, Beoplayer works perfectly (especially with the touch-screen), the quality is however not so good and there are few drop-outs from time to time.
My conclusion it is the quality of the streaming software driving this
Update:-
Just loaded TuneBlade on to my PC and dropped Airfoil for a while. This uses Airplay rather than DNLA streaming. PM of course picks this up no issues.
1. Sound quality of TuneBlade is much better than that of Airfoil.
2. No crackling on heavy bass lines
3. No drop-outs - even with "Real time streaming" (5 to 350ms delay) so the +2 second delay is gone.
4. Clunky volume control - cant integrate on existing PC system controls.
5. Got to mute system volume as sound still plays from the PC speakers.
6. Beoplayer works fine but without the sound control. Cannot control PM with Beo4
Usual stuff remains; indifferent qualities of software, unable to control the basics, clunky interfaces of a non-thought-out system in a digital realm of break-neck speed and low quality.
I sit in anticipation that some one somewhere will fix al this one day.