![]() To get the receiever demo working on your system (for editing purposes, ** if you just want to mix music with your video and have it able to be cast to chromecast devices, it is sufficient to just use our reciever id, which will point to our latest working receiver, in your app. The Chromecast receiver app ID, which the sender uses is: 37FFD8F7, and can be used without development chromecast IDs (published).Ĭurrently this demo implements a custom feed SDK (for pause and stop, and momentarily during skip) We are working on a bug that when feed audio stops, the video audio stops. Skip, Pause, Play Stop and volume control for the feed audio stream are implemented. ![]() Clicking the cast button will allow you to cast a video to your device, and start playing an associated station with it. We have created a live demo sender and receiver application. There is a published public receiver that can be used by Feed.fm clients (for an example sender application, ), unmodified, for simple integrations, or clients can access the source code for our receiver and create their own custom receiver with their own desired functionality. The receiver will respond to messages that control Feed.fm music playback, such as play, pause, and change station. We have created a custom chromecast receiver that will play Feed.fm music in tandem with a full screen video and its associated audio. Go figure.Chromecast-demo feed media group chromecast sender and receiver. As I mentioned above, unfortunately all the methods here did NOT work for me, and again, the receiver just suddenly appeared as a device. When I removed the DN1080 from my Home a few months ago, I removed the room it was assigned to as well.Īnyway - that's a list of things to try. This may have had something to do with it because it was shortly after this (and multiple other attempts) that it reappeared magically. re-added "Office" room, where my DN1080 is and what it was assigned to originally. I have 3 Nest Minis, I renamed and moved them around to their rooms (kids like to swap sometimes so the names/rooms don't match) tried to Add Device countless times, chromecast and speaker switched both receiver and phone from 2.4ghz wifi to 5ghz I have an Asus AiMesh wireless setup, so I tried moving both my phone and receiver to different routers, the same router, etc. added a second "test" home (didn't seem to work) factory reset DN1080 (does not revert to original firmware btw) fully removed DN1080 from device list and "unused devices" in google home So it wasn't me choosing to Add Device or anything that made it appear. ![]() Ironically, it would appear I didn't do anything to actively add/see the receiver, it just showed up on the list of devices. Unfortunately, I don't really know what specifically fixed the problem. One final update for everyone - I was able to add the receiver again! Just aside, I think linking the receiver to Spotify direct gives a better sound, but that's just my opinion So I now have two groups 1 with Just the Chromecast Audio units and 1 with all three devices. I had to reassign my Chromecast audio units to rooms to be able to add them to the same group as the receiver. It seems that each device has to be assigned to a room otherwise it cannot be added to a group. ![]() (It is here where you can unlink the device). First I clicked on the receiver device, then clicked on the gearwheel and then the home heading and added the receiver to the home. After some hours of pulling my hair out I finally found a way to get them all in the same group. Basically I could cast to the receiver alone and I could cast to my Chromecast audio units which are in a group and plugged into portable speakers. ![]() I followed some of the solutions on this forum but none seemed to solve my problem. Suddenly my Sony Receiver wouldn't work in the group setup from the Home app. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |