My app integrates Google cast. The app is similar to Google Photos app. It allows user to browse files, then cast to chrome cast devices. Following this link: https://github.com/googlecast/CastVideos-android.
I setup local http url for my file like this: http://192.168.1.45:8989/local/storage/emulated/0/DCIM/AnyRestore/20200908_113828.mp4
Video can cast, but it is interrupted, lag even can't load the very big videos
I tried hardcoding to change the url look similar this one: https://commondatastorage.googleapis.com/gtv-videos-bucket/CastVideos/mp4/BigBuckBunny.mp4 like sample app above. Magically it works.
I would like to know the issue is local http url can't cast, right?. And anyone can give me know Google Photos is using https like demo app or local http like me.
I also used to Youtube, Netflix to cast. It's can cast even app is closing or force close. But Google Photos is not, cast is stoped right away if close the app. Can you explain this?
Finally, I want implement google cast function for my app like Google Photos app. Please give me any suggest.
Related
App not installed. Clicking to firebase dynamic link lead to browser and open web content.
I am using this dynamic link: https://market.page.link/?link=https://market.kz/cabinet
I followed this doc: https://firebase.google.com/docs/dynamic-links/create-manually
I tried specify afl and apn but it didnt help.
The reason seems not be under developpers control. I had this problem too because i was always testing with the same app when opening the firebase dynamic link (Skype mobile).
I could not tell you exactly which app are causing this problem, but i can tell you that if you open a firebase dynamic link using skype in your Android device (strangely, it works fine with iOs), it will redirect to your browser at the Google play page.
You should try using another mobile app and open the link and see if it works. I tried facebook messenger and telegram and it works fine.
See more here : https://github.com/firebase/flutterfire/issues/2828
Problem:
Youtube Music sucks for playing back music you have uploaded for years. The app sucks, and the Android Auto app sucks. I've contacted the YT Music team many times, but they don't seem to listen to music ever so they don't even understand the problem(s).
Solution:
Create my own app to play back my own music that lives in Google/Youtube Music. I'm an Android app developer so might as well fix this my own way.
Are there APIs for Youtube Music? I know there's an unofficial Youtube Music API, but that's phython, it doesn't build at the moment (Feb 2022), and it seems to focus on paid music, not my own uploaded library.
Would Google drive APIs do this? If so, is there documentation on how to use it? I can figure out the OAuth part, but I don't know where to get the data for the parameters in this sample api
Is there a better way for this? I just need to download the music files, and then create a player around them.
Thank you!
I was looking for something similar but the closest I got was ytmusicapi in python. It works for me and I installed it via pip install ytmusicapi. Its source is hosted on https://github.com/sigma67/ytmusicapi there, perhaps, you can see the YTM protocol. Authentication works by simply copying cookies from your browser after authenticating with YTM manually. That worked for me as well.
Another option is Kodi and a plugin they have: https://forum.kodi.tv/showthread.php?tid=360827 (but that did not seem to work for me after 3 minutes I spent on it).
If you are serious about it and you can't get YTM protocol via the source of ytmusicapi, then you can perhaps reverse-engineer the protocol using your browser. Firefox's Tools->Browser Tools->Web Developer Tools is your best friend. After you authenticate to YTM, open the "tools", click on "Library" on YTM webpage, then in "tools" tab, go to Network and look for a POST similar to https://music.youtube.com/youtubei/v1/browse?key=... right click on it and Copy->Copy as Curl. You will be able to see what auth-headers it sends and also what's the protocol for showing up your YTM Library.
I am attempting to integrate Google Cast into my app. I am using the CastCompanionLibrary. Integrating it is simple. ActionBar is updated with the Cast Icon. I can connect to my Chromecast devices. However, when I attempt to invoke playback, I get one of two results:
VideoCastControllerActivity starts but a spinning Loading icon displays and no video is played on the Chromecast. Only option is to hit the back button.
Only after step 1 above, Attempting to play a video just produces a Toast stating "Faile to load media"
What I can't seem to determine is if this is a problem with the App, if it resides in the content, or if it is a problem with the receiver in Google Cast Dev Console. My content is stored on a MythTV Backend and it can be HLS, MP4, MKV, AVI or 3GPP. I don't get any exceptions in the logs, not in my code or in the CastCompanionLibrary.
Any ideas on how to debug this issue?
Anyone know of a test tool that I can plug a url in to verify if the content will cast correctly on a Chromecast?
I suggest you start with simple MP4 content to first make sure that your app is set up correctly. Once you are able to play mp4, you can move to more sophisticated formats. The media formats that Chromecast supports is listed on our documentation site, so you need to limit your content to that list. The next thing to do to debug your issue, for supported formats, is to make sure that the server that is serving the content provides CORS headers since that is a requirement for almost all (but mp4) content. Finally, if that is satisfied as well, take a look at your receiver logs (turn on logging on the receiver side through the chrome console) and that should give you additional information as to why your content is not playing. To access the receiver logs/console, you need to be running your own custom receiver or your own styled receiver.
This is a short question:
I'm using "YouTube Data API", and I've noticed that if the YouTube app isn't installed, all demos of the sample just show a dialog telling the user to install the app.
I'd like to have a different fallback, so that the video will still play.
I assume I can use WebView, but is there a better way? Maybe a VideoView ?
What's the best alternative, without any libraries (using just the framework) for when YouTube app isn't installed?
I did a Google search for opening spotify URLs/URIs on native app, and found the following URI scheme to open the links in the native app.
spotify://spotify:artist:12Chz98pHFMPJEknJQMWvI
This above link seems to be working fine on ios devices, but i am not able to open this on android device(HTC One). Any suggestions ?
Have you tried entering just the spotify:artist:12Chz98pHFMPJEknJQMWvI in android. I believe the spotify:// may be directing it towards the app, but i think android directs its apps with a different command. Also, just in case it is the same for android, you need to have the app installed on your phone if you dont already have it for the directing command to work properly.
android refer this link
ios refer this link
some reference from above link
have run into a similar need in an app. My solution was to create a client that hits the Spotify API to return either XML or JSON of the search. For instance, if you want Muse, you would hit the API with the following URL:
http://ws.spotify.com/search/1/artist?q=muse
From the XML or JSON, you'll be able to extract the link to the particular artist within their URL scheme:
spotify:artist:12Chz98pHFMPJEknJQMWvI
Chop off the spotify:artist: portion and append that onto a Spotify artist link:
http://open.spotify.com/artist/12Chz98pHFMPJEknJQMWvI
Then, using the Spotify URL scheme and UIApplication, you can open the Spotify app to that particular artist's page:
[[UIApplication sharedApplication] openURL:
[NSURL URLWithString:
#"spotify://http://open.spotify.com/artist/12Chz98pHFMPJEknJQMWvI"]];
Note, using URL schemes to access features of another app is generally undocumented and can be a fragile endeavor. If Spotify in the future decides to change anything about this, it will break this functionality without warning.
The quick fix I made was to directly call the uri with any modification on the original uri.
which is 'spotify:artist:4gzpq5DPGxSnKTe4SA8HAU' or 'spotify:track:1dNIEtp7AY3oDAKCGg2XkH'