I am developing an app that creates podcasts. They are just .m4a files. However, even though I am setting the album name in the file, I cant seem to get them to group together as a podcast when I load them onto a device. I also set the artist, composer, genre, title, and a couple of other fields. They group properly in iTunes, but seem to all get lumped together in one big generic group on an iPad; the album is being ignored.
Is there a specific tag that needs to get set so iOS will group them in the Podcasts app?
Well, if you're talking about creating what amounts to a Playlist for iOS 6, the new Podcast app does not support that functionality at this time. A quick search shows lots of people complaining about this, so I would say the hope is that this functionality will become available again in a future update. I wish I had better news for you.
Some reference:
https://discussions.apple.com/thread/4312284?start=0&tstart=0
https://discussions.apple.com/thread/4262881?start=30&tstart=0
Related
I'm doing my final project for a coding school that will be a deep song search app that returns every detail about a song (composer, personnel on the track, lyrics, studio, media uses, images, etc). I'm using React frontend/Rails backend API. I'm new to API's and have tried Discogs and Musicbrainz but find the Mediawiki to be the easiest to traverse. Messing with their sandbox using Query, I feel like I'm getting closer but wondering if anyone with more experience out there could help me get precisely what I need.
I would like a music search to return a list of matches (could be same title but different songs or same title but different recordings). A user can click on the results to see the details. I would like the API to return links and hopefully images (album cover, etc). Does anyone know the best way to go about this?
I've also tried using the Ruby Gem wrapper Mediawikitory https://github.com/molybdenum-99/mediawiktory. I like the clean interface but can't quite find the right parameters.
The closest I've come to what I'm looking for in the Mediawiki sandbox is an example like this for the All Star (Smash Mouth):
https://en.wikipedia.org//w/api.php?action=query&format=json&prop=&list=search&continue=-%7C%7C&srsearch=star%20(song)&srlimit=5&sroffset=15&srqiprofile=engine_autoselect&srwhat=text&srinfo=totalhits%7Csuggestion%7Crewrittenquery&srinterwiki=1
This gives a list of songs (I'll have to concatenate '(song)' in every search unless there's a specific category parameter I don't know about).
So with further research I was able to drill down to specific song searches (and this will work for any thing this specific). You have to use srsearch and then search option in lists. So an example for a list of songs based on a given title:
https://en.wikipedia.org/w/api.php?action=query&formatversion=2&format=json&prop=info%7Cpageimages&generator=search&inprop=url&piprop=thumbnail%7Cname&gsrsearch=I%20love%20you%20(song)&gsrwhat=text
Make sure you choose version 2 as it gives you a better formatted Object to map over.
The Mediawiki API is very robust. You just have to spend a little time with it. The sandbox is great.
I must do the following:
a user chooses a photo using the share functionality in the Photos app;
just like, eg., WhatsApp, the photo "reaches" the app;
the app does something with the photo;
The photo must NOT be uploaded instantly: it must receive the photo and store it (then, IF the user wants, he can upload the photo).
I was thinking to use Share Extensions when I red the following:
Make sure that the Share extension point is appropriate for your purpose. The best Share extensions make it easy for users to share content with websites. If you want to create an extension that lets users perform a different task with their content or that gives users updates on information they care about, the Share extension point is not the right choice.
(source: https://developer.apple.com/library/content/documentation/General/Conceptual/ExtensibilityPG/Share.html#//apple_ref/doc/uid/TP40014214-CH12-SW1)
Problem is, now, I don't know anymore if Share Extensions can do what I need to do. Moreover, any online tutorial (and the original docs too) talks about a Share Extension Template that must have been removed from XCode 8.1 (I see everywhere screenshots of a template I can't use).
The Share Extension was what I needed: it's absolutely up to you what to do with the file you are sharing. That is: you can freely create an App Group and store it to send it at a later time, no need for an instant upload. Moreover, you can change the appearance of the controls and perform validation of your content. So, in a smaller number of cases, share extension can be used with a slightly different purpose than intended.
what is the approach to store multiple videos from an author in his named folder, but then there are 1-n videos from this author?
YouTube has for every video a complete different URL with an ID. Casual/Older users don't know where they are.
News sites seem use /topic/title-id123
Cnn uses /yyyy/mm/dd/title
To keep this question answerable: What URL structure would you recommend for me?
- every person has some videos without interesting title we could use
- the date from start day to end day is more likely important (2005-12-12 to 2005-12-17)
- every video should be social media shareable, so I think they all need a single URL and can't just be all embedded in /videos/name
Store them however is the best for the backend editor workflow (you didn't mention, how and when new videos are added), in 6.2 you have file abstraction layer, so each file in fileadmin has assigned ID. If you want to make your videos nicely social media sharable, you need to provide additional metadata such as video name and thumbnail etc, so I would suggest building a plugin for this which would take the video ID from the URL and display it with all the additional data necessary.
If you are using EXT:realurl (which I hope you are), you can configure to the video title in the URL, which would look like: /somepage/video/video-title/ or even /somepage/video-title/ . Adding /yyyy/mm/dd/ in the URL only makes sense if you are producing multiple videos every day, otherwise it feels pointless.
for building unique URLs with realurl for news you find solutions to include the uid of the news.
As TYPO3 handles all files with FAl you might use the unique file_sys:uid in your video URL. You might use realurl to generate and resolve URLs like:
/videos/123/title_of_video/
My school newspaper recently switched from print to digital, and I wanted to make an app so that the newspaper is more accessible.
As of right now, students can only access it via this website, and articles are largely ignored because no one bothers to check it.
I have a moderate amount of experience with making apps in Swift (through bitfountain and Ray Wenderlich), but I'm not sure how to start this project. If possible, how can I fetch articles from the website above and display them on an app? As of now, I'm not looking to mimic the site with a sports feed, comment sections, polls, etc, but I do want to be able to:
Get the text of the article, as well as the title, author, and date
Get the category that the article is filed under (News, Sports, Features, etc)
Get the picture(s) included in the article (this is not crucial)
I'm really stumped on how I can access this information and create an app that can continually fetch new articles when they are posted and update itself to show them. Is this a feasible endeavor, and if so, how can I start?
Check out this post from W3schools. This is a PHP script that grabs the feed url and renders it in HTML.
I think this will be perfect for your project.
http://www.w3schools.com/php/php_ajax_rss_reader.asp
I want to get all artist name in iTunes.
I look this page but did not find any solution.
http://www.apple.com/itunes/affiliates/resources/documentation/itunes-store-web-service-search-api.html
Is it possible to get list of Artist Name in iTunes Music store?
I do not believe this is possible with the current API. You might be able to "fake" it depending on what you are trying to implement with multiple calls to search but you most likely won't be able to compose a complete list.
Keep in mind the search limit is 200 so you will probably be interested in the cache architecture at the bottom of the documentation: http://www.apple.com/itunes/affiliates/resources/documentation/itunes-store-web-service-search-api.html