Mobile Optimized Files, Audio Types & Display Messages
Click Here to see a walkthrough demo of Nokia Podcasting
__________
Some podcasters are wondering why the “Content may not play on your device” warning is popping up for normal audio files. Our development team gives the answers:
The determining factor for whether or not the podcasting app displays this warning is actually not the file extension, but the mime type that is provided in the enclosure tag. (We only use the file extension for display on the UI.)
Whatever content you use, just make sure you provide a MIME type that is supported in our phones.
A complete list of Browser MIME types in Nokia GSM Devices can be found here:
http://www.forum.nokia.com/info/sw.nokia.com/id/444aa596-38d4-473c-81ed-657da920d163/Browser_MIME_Types_in_Nokia_GSM_Devices_v1_8_en.pdf.html
(look in Chapter 7 for S60 3rd edition).
One exception to this is MP4 (video and audio mp4 content). Because MP4 is a container format and we have no idea if the content within the MP4 container will be played correctly, for audio/mp4 or video/mp4 content we display the warning “might not display properly” and don’t auto-download these episodes.
If your audio show is in aac format, the best MIME type would be “audio/aac” - that doesn’t display any warnings.
And when creating an audio podcast specifically for a mobile audience, I would recommend to use AAC (or better yet, eAAC+) because of the smaller filesize and/or better quality at the same file size, compared to MP3.
The Nokia Music Manager from the Nokia PC Suite (download here) is able to convert your mp3 files into eAAC+.
NOTE: If you want your video podcast optimized for mobile (size, playback compatibility and no warning), use the format 3gp. (Most compatible devices are able to play frames per second (fps), newer devices like N95, N81, N93, etc can play 30 fps)
HACK!
OK….I realize you shouldnt need a workaround, but if you know your video format is compatible with the Nokia devices and you want to make sure the warning message doesnt come up, here is a way to “cheat”.
If you have an MP4 video file in a format that for sure plays on our devices, you can set file extension to “.mpeg” and the mime type in the enclosure to “video/3gpp” to avoid that warning message and to allow auto-downloads 
… a bit hacky, but works nicely. Please note that the .mpeg extension is important, too.
Here’s an example
Hi Steven
Are there any plans for upgrading the Podcasting application? The current version is, well, fairly “early adopter”-ish. I use it daily but it’s not a slick experience. A lot of things could be done to make it better integrated into the phone and more friendly to the mainstream consumer.
Hi,
Any chance that an option can be implemented to override these settings?
The way i see it, some people are never going to implement a change for their podcast, either technical skill, bureaucratic or for personal reasons. Generally i will subscribe to a podcast and try it before keeping it permanently, so you generally know whether it is compatible or not.
Regards
Rene Castberg
I just uninstalled this worthless application. After setting up all my RSS feeds that I know work on my N95 to automatically download off of my wifi every night, it refuses to download them because this shitty application has decided that the video is not compatible with my N95 even though it is.
Thanks for wasting my time!
matt, sorry you felt this was a worthless app. Our development team is working a solution to disable the warning when autodownload is used. The warnings are specifically because not all video is compatible, and there really is no way to know if the mp4 container is going to work or not. (other than the hack for creators in the post above) Our #1 concern is that whenever there are large data transfers, that the user doesnt spend the time/money to download something that may not play unless it is a conscious choice. The original scope of the Podcasting app was for audio files which should work fine for autodownload.
But like I said, we are looking for a way to disable the warning for autodownloads for a future release. Hope you give it another try then.
S
Steve,
Glad to know that you guys are going to be removing that (or at least adding an option to disable it.)
However, your answer confuses me. You even say yourself:
“The warnings are specifically because not all video is compatible, and there really is no way to know if the mp4 container is going to work or not.”
OK, great, I understand that, but if there is NO WAY TO TELL, then why even add the warning and prevent the download? How does that make any sense? Regardless, please get rid of that stupid warning. I have to download everything manually still… Most apps that “feel the need to warn people of the old 1980 pay-by-the-minute data plans” usually have a disclaimer at the start that has the option to “never show this again.” I think that would have been a much better option considering anyone who has a smart phone, most likely knows how to get on an unlimited data plan, or use their home wifi.
Anyway, sorry for the venting… regardless, glad to know you are considering removing it. Will it be available in the N95’s download! section once a new update is out?
In answer to above:
Not all video files are incompatible and many download fine without showing the message.
Other files are completely incompatible (mov) so unless the user just wants to download OTA to sideload back to PC, then there is no point.
Its just the mp4 files which are tricky. Some work. Some dont. The average user wants to be notified before download that they cant be sure the file will work.
Now, since you’ve read the above article about tagging, you know that content creators are able to tag their RSS to make sure that the error message doesnt come up. Feel free to send an email to your favourite shows to notify them if its important to you. Proactivity!
But seriously, we are working on the solutions you mentioned because in auto download, users cant really see the message anyway, so its useless. It just take a bit of time to prioritize, recode, and resign the app (as well as check with our legal team).
But barring some unforseen problem, when its fixed, it should be able to be redownloaded and installed.
Hope that helps ease the current pain at least a bit.
Not sure if this is quite the right place for a feature request, but how about a PC software component to podcasting that will download and convert video for subsequent loading onto the mobile in a guaranteed-compatible format?
Not sure if this is quite the right place for a feature request, but how about a PC software component to podcasting that will download and convert video for subsequent loading onto the mobile in a guaranteed-compatible format?
Hi Steven.
Any news about an upgrade to this app?
I just bought a n95 and I sold a Zune so I want to use the n95 as a podcast client.
If you plan to release an update soon then I’ll wait, if not I have to find other way to get my podcast on my Nokia.
TIA. Sebastian.
The Nokia PC Suite is the same for all devices?
Looks like Nokia doesn’t care much about updating phone software and podcasting software..
I was a nokia supporter for many many years, but looks like i am going to be switching to Android, as soon as it comes out. At least, there is an open source community behind it.
sorry. I need the hack part very much b/c I want to autodownload badly. Could you explain in detail how to hack? I don’t know what is MIME and so on, so a step-by-step guide would be the best!
to be honest, I have no problem if the file could be played with Nokia player or not b/c I use coreplayer for everything.
For anyone who had just gotten hold of a brand new PSP, learning how to put psp game downloads to PSP is something that should be learned. Learning how to do so can help a person enjoy his PSP to the fullest, explore all of its features and maximize its use.
Hi there… on the off chance one of the elves is still monitoring this. I have to admit I don’t udnerstand the instructions above:
If you have an MP4 video file in a format that for sure plays on our devices, you can set file extension to “.mpeg” and the mime type in the enclosure to “video/3gpp” to avoid that warning message and to allow auto-downloads
… a bit hacky, but works nicely. Please note that the .mpeg extension is important, too.
Here’s an example entry from an RSS feed:
Does this mean we need to somehow change the way the podcast is created to change these variables, have them rename their files as .mpeg, and change the mime type as well? Or is this something we can do on the phone? Anyone with a clue let me know.
also, is it just me, or does there appear to be *nothing* where one might expect that example entry?