In general, the assumption is that you are running the latest version of gPodder 3. Things written here might not exist or work as described in older versions of gPodder. When information applies to older versions of gPodder, this will (should) be explicitly stated.
If you want to try the latest version, see the instructions at: Run from Git
In general, if you get gPodder via Git or the source tarball, simply run it directly from the source checkout and don’t try to install it system-wide (use your distro’s packages for system-wide installation).
gPodder is designed to also run directly from a source checkout (the maintainer uses it like that all the time):
gPodder has numerous configuration options to set its behaviour: how it plays podcasts, handles downloads, and many others.
To change gPodder’s configuration, open the Preferences dialog box by choosing Podcasts > Preferences from the menu bar, clicking the Preferences button on the toolbar, or typing Ctrl-P
. Then click the tab containing the options you want to change.
Click the General tab to see gPodder’s general configuration options.
Audio player: Use this drop-down list of compatible audio players installed on your system to choose the one gPodder uses to play audio podcasts. Currently pre-populated application lists are only supported in Linux. (OS X and Windows users, keep reading!)
You can also click the Edit button next to the list to enter a custom audio player command. For example, you might want to run the player with some additional options, or choose a different player that does not appear on the list.
Video player: Use this drop-down list to choose the video player gPodder uses to play video podcasts. This option works the same as the Audio player option, except that it shows media players capable of playing video files.
gPodder.net is a Web service that helps you synchronize your podcast subscriptions across multiple devices, discover interesting new podcasts and recommend your podcasts to others. Click the gpodder.net tab to set how gPodder interacts with gPodder.net.
Note: To use gPodder.net, you need to register for a user account first.
Synchronize subscriptions and episode actions: Check this box to merge the subscriptions on your computer or device with your subscription list on gPodder.net. These podcast subscriptions are now available to any other devices you sync with gPodder.net.
Username: Enter your gPodder.net username.
Password: Enter your gPodder.net password.
Device name: Enter a meaningful name for your computer, or keep the one gPodder.net assigns. Make sure the name is unique.
Replace list on server with local subscriptions: Click this button to replace the subscription list on gPodder.net with the list on your device.
Caution: Any podcast subscriptions on gPodder.net but not on your local computer will be lost.
Click the Updating tab to see gPodder’s options for updating feeds and downloading new episodes.
Update interval: Drag this slider to choose the frequency that gPodder checks your feeds for new podcast episodes. This time period can be between 10 minutes and 12 hours. If you drag the slider all the way to the left, gPodder will not check for new podcasts automatically, and you will have to update them yourself.
Maximum number of episodes per podcast: Use this spin box to set the maximum number of episodes that gPodder keeps in each podcast feed. Once this maximum is reached, gPodder deletes the oldest episodes in the feed as new ones are added.
When new episodes are found: Use this drop-down list to choose what you want gPodder to do when it finds new podcast episodes on a feed. The available options are:
Click the Clean-up tab to see gPodder’s options for managing old downloaded podcasts.
Delete played episodes: Drag this slider to set the length of time before gPodder automatically deletes old podcasts. This time period can be between one and 30 days. If you drag the slider all the way to the left, podcast episodes will not be deleted automatically, and you will have to manage them yourself.
Remove played episodes even if unfinished: By default, gPodder automatically deletes old played but unfinished episodes. Clear this check box if you would like to keep unfinished episodes until you have played them completely. If you have chosen to delete played episodes manually, this option is not available.
Also remove unplayed episodes: By default, gPodder automatically deletes played episodes but leaves unplayed ones alone. Check this box if you want gPodder to clean up unplayed episodes as well. If you have chosen to delete played episodes manually, this option is not available.
Click the Devices tab to see gPodder’s options for portable media player devices.
Device type: Choose the type of device from this drop-down list that matches your player. The available options are:
Note that as of version 3.2.0, gPodder only supports syncing with filesystem-based devices. Check the user documentation for your device if you’re unsure what kind it is.
Mountpoint: Click this button to choose the mount point where your media player normally appears on your system. For example, on a Windows system it might be drive F:
.
Create Playlists on device: Enable this option to have gPodder create a m3u format playlist on your device during the sychronisation process. This is only supported for filesystem-based media players. If ‘Create Playlists on device’ is enabled, the following settings can also be configured:
After syncing an episode: Choose what you want gPodder to do after it transfers a podcast eposide to your player. The available options are:
Only sync unplayed episodes: Check this box if you want gPodder to ignore episodes that have already been played, when synchronizing podcasts to your device.
Flattr is a microdonation system that allows you to fund online content creators. You pay a small monthly fee (set by yourself), and it is shared between all the online resources you “flattr,” or choose to support. Click the Flattr tab to see gPodder’s options for Flattr.
gPodder comes with a handful of extensions. Check them out or learn how to make one yourself on this page.
Some extensions require external programs to work properly. gPodder searches all directories in the PATH environment variable to find programs. You may have installed a program in a custom location or are using the Mac build which ignores PATH and uses its own set of directories. In that case you can open Preferences, click the Edit config button, and add the custom directory to the path.alternate
setting. Multiple directories can be separated by a ;
on Windows and :
on Mac and Linux.
Do not include the program name or trailing slash in the directory. Set path.alternate
to /opt/homebrew/bin
if on Mac and which ffmpeg
displays /opt/homebrew/bin/ffmpeg
. Set path.alternate
to C:\ffmpeg
if on Windows and where ffmpeg
displays C:\ffmpeg\ffmpeg.exe
.
Several extensions require FFmpeg, such as audio converter, concatenate videos, rockbox convert2mp4, video converter and youtube-dl. Linux users can install it via their distro, while others can visit https://ffmpeg.org/download.html or https://github.com/yt-dlp/FFmpeg-Builds/releases. Mac users with homebrew can run brew install ffmpeg
. See Custom PATH if on a Mac or if FFmpeg was installed to a custom location and is not in PATH.
gPodder has many configuration options that are not all directly accessible through the Preferences dialogue box. Click the Edit config button to access the gPodder Configuration Editor, where you can see and change the full list of configuration options. For an up-to-date list, possible values and the defaults, please see src/gpodder/config.py.
Manually add one at a time using Menu - Subscriptions -> Subscribe to new podcast and paste in the URL of the RSS feed.
gPodder tries to be smart about what you enter in the URL field when adding podcasts to save you some typing:
http://
, as gPodder will automatically add it if the URL does not contain a URL scheme.<link>
tag to the podcast RSS feed, gPodder can (most of the time) autodiscover the feed. So, instead of entering “feeds.feedburner.com/uncontrolledairspace”, you can enter “www.uncontrolledairspace.com”, and gPodder will figure out the feed URL (but see the next hint for another nice shortcut for FeedBurner URLs)The Podcasts menu provides an easy way to save your subscription list to an OPML file. The OPML file contains URLs for all the feeds you are subscribed to. It does not contain the status of episodes. You can re-import OPML files using the Podcasts menu. The OPML file format is a simple XML format that can be used to move feed subscriptions between different RSS-aware applications.
You can also backup the files Database (an SQLite 3 database containing subscription and episode information) and Settings.json (a JSON file containing your settings) in $GPODDER_HOME (defaults to ~/gPodder/).
Export your iTunes podcast subscriptions to an OPML file. Copy it over to your device or computer and load it into gPodder with the Import from OPML file menu item. To export your iTunes podcast subscriptions to an OPML file right click on “podcasts” in your source menu on the right hand side. Select “export” and save as an OPML file. See http://www.apple.com/itunes/podcasts/.
Older versions of gpodder have an Import from OPML file menu item while newer versions may not. If you have the import option, you can select it, browse to your opml file and import it.
At this point you should have a local list of subscriptions. You can push these up to gpodder.net via the Replace list on server with local subscriptions button on the Preferences : gpodder.net tab.
Most of the audio player applications available for the N8x0 do not support bookmarking (so you can resume playing a podcast from a saved point). Panucci is a resuming audiobook and podcast player written by the gPodder people that is available from Maemo Extras. Install the package and set the player variable to panucci (don’t forget to set maemo_allow_custom_player, as stated above).
Most applications will stop the current song/episode and start playing the selected episodes when clicking on Play. You can avoid that by setting a custom command in the settings dialog:
Application |
Command |
Remarks |
---|---|---|
Aqualung |
|
This option loads the files, but does not start playback automatically, you can try adding the -L command for that, but that tends to start playback on the last one loaded. But once the first file is playing, you can load up your play-list from gPodder for hours of listening enjoyment. |
VLC 0.9.4 |
|
This will queue up the file and play the first one and you can add more while you're listening. You may have to click your play button, but once playing it ought to continue to play the created playlist. |
SMPlayer |
|
Adds the files to the current SMPlayer playlist |
Synchronising podcasts to MP3 Players is supported for any media player that can be mounted via gvfs. You can see the list of available mount backends here. This includes mtp devices on Linux. On Windows currently only devices that can be assigned a drive letter can be accessed. There is also support for iPod synchronization.
Before you can synchronise podcasts to your media player, you should ensure that the player has been set up properly in the ‘Device’ tab. See above for details.
To initiate a sync, select ‘Sync to Device’ from the ‘Extras’ menu:
Previous versions of gPodder required you to sync episodes individually - now all episodes are synced at once.
If you have the ‘Create Playlists on device’ option enabled, the m3u playlists will be written to your device and then the episodes will be copied over. You see the current status of the sync from the ‘Progress’ tab of the main gPodder window. From here, you can also control the number of episodes written to your device concurrently via the ‘Limit downlads’ setting, which also applies to device synchronisation. However, the ‘Limit Rate’ setting in the ‘Progress’ tab has no effect on synchronisation speed.
If the ‘Create playlists on device’ option is enabled, gPodder will create playlists on your filesystem-based media player during each sync. One playlist is created per channel. The playlist is created in date order, so that the playlist will always start at the oldest episode and end at the newest. As new episodes are synced to the player, they are automatically added to the playlist. If you delete an episode from within gPodder, it is removed from the playlist.
If you have the ‘Create playlists on device’ option enabled, you can also enable the option ‘Remove episodes deleted on device from gPodder’.
When this feature is enabled, users can delete episodes from gPodder by deleting them from their media player and then performing a sync with gPodder. gPodder uses the m3u playlist to track what episodes were synchronised to the device.
With this feature enabled, if you deleted episodes from your device and then synchronise again, gPodder will present you with a list of deleted episodes. You can choose which of these episodes you wish to delete - all, none or some. See the example below:
Any episodes that you choose not to delete will not be deleted on from gPodder, but will not be restored to your player. In order to sync them back to your player, you will then need to disable this feature from Devices Preferences and those episodes will be copied back at the next synch.
If ‘Remove episodes deleted on device from gPodder’ is not enabled, any episodes deleted from the device will be copied back over during the next sync. You will instead have to manually delete episodes from within gPodder itself.
If your media player does not support playlists or deleting tracks then you can choose to delete tracks that have been removed from gPodder from the player when a synchronization is performed. To enable this check the ‘Remove episodes deleted in gPodder from device’ checkbox in the Device Preferences dialog.
You can use custom file names when synchronising. This makes browsing files on your device much more convenient.
The default value for the custom filename field is {episode.basename}. This will work for most podcasts. However, occasionally you may find a podcast where the producers don’t provide unique information in the tags, which can result in multiple episodes being given the same name (e.g. podcast.mp3), and thus overwriting one another on synchronisation. One workaround to this is to include the {episode.sortdate} data. Multiple fields can be concatenated, e.g.: “{episode.sortdate}_{episode.basename}” which will result in files of the form “2012-01-14_podcast.mp3”.
For podcasts that release multiple episodes on the same day, even this might not be enough. Try also {episode.sortdate}_{episode.title}, or even {episode.sortdate}_{episode.published}
Both playlist creation and the ability to remove episodes from gPodder by deleting them from the device will work with custom file names enabled.
If you wish to keep an episode around you may archive it by right-clicking on the episode and selecting “Archive”. The episode must be downloaded for the “Archive” option to show.
Once an episode has been archived, gPodder will do its best to never delete it:
There are two ways to initiate a search: focus the Podcasts (resp. Episodes) list and start typing or activate the Podcasts (resp. Episodes) > Find Podcast menu item.
You can then enter parts of the title or description to search for.
Episodes can also be queried in more advanced syntax:
Use regular expressions by surrounding your query with slashes:
/[áéíñóúüÁÉÍÑÓÚÜ]/
Arbitrary complex python expressions (surround them with parenthesis) can also be used,
following the Adjectives (downloaded)
and Nouns ('hello' in description)
vocabulary
defined in query.py.
Here are a few examples:
(finished and not deleted)
(downloaded and not played and age > 7)
(downloaded and s('winter', title))
(min > 60)
(rem < min and rem > .95 * min)
(section == 'Audio')
gPodder includes a command-line interface. The command is called gpo
. You can get a list of possible actions by running the command without any parameters.
You can use a HTTP proxy server for downloading episodes and feeds. Newer versions of gPodder provide a way to do so in the GUI:
If the proxy option in the GUI is disabled, gPodder will respect the environment variable http_proxy. How to set the http_proxy environment variable in different operating systems is described here:
You can use a SOCKS proxy server by setting the enronment variable all_proxy. If you want the DNS to be resolved through the proxy, use socks5h://
instead. See urllib3 docs for more details.
export all_proxy=socks5://hostname:port
If you want to use a proxy for gPodder, but don’t want to use a proxy for other applications, you can create a short shell script:
#!/bin/sh
export http_proxy=http://username:password@hostname:port
gpodder
There might be some problems with feeds (see the related bug report) - to fix it, you can try to use Pipes.
Out
;See this pipe for a not broken feed to get an idea of how it should look like.
This service is not afiliated to gPodder in any way. It requires an email registration and currently free for only 3 pipes per user. Maybe a better or free service exists. If so, please let us know!
Original idea used the now defunct Yahoo! Pipes service.
If you have got problems with episode downloads, please follow the instructions on the page about Reporting download bugs.
Making playback slower or faster is generally called time stretching.
See this page for a way to set it up on gPodder.
Here are the default gPodder home folder locations:
To change the download directory or gPodder Home, you can set one (or both) of these two environment variables:
GPODDER_HOME
: The settings and database files are always stored in $GPODDER_HOME
.
Downloads will be saved in the folder Downloads
inside the new Home folder you setGPODDER_DOWNLOAD_DIR
: Downloads will be saved directly in the folder you specify (which does not have to be in the gPodder Home folder)There are various ways of setting these variables, depending on your distro/operating system:
On Windows it’s also possible to set the gPodder Home folder using the registry:
in regedit, add a string value named GPODDER_HOME
to the HKEY_CURRENT_USER\Software\gpodder.org\gPodder
key, with the absolute path you want.
Since gPodder 3.3.0 you can’t change the environment variables for gPodder Home and for the download directory through Preferences > Edit config (see bug 1718). One thing you can do instead is this:
gedit
~/.pam_environment
A text file will open up (it could well be empty). Add one or two of the following lines (depending on whether you want to change both these variables or just one):
If you are using Kubuntu, you must do the following :
kate
~/.kde/env/setgpodder.sh
An empty text file will open (you can name it whatever you want instead of setgpodder,it could be gpodderdirs, etc). Add one or two of the following lines (depending on whether you want to change both these variables or just one):
Read more on persistent environment variables in Ubuntu.
This is the permanent way to change gPodder’s home or downloads location:
~/Library/Application Support/gPodder
folder;gPodder will now use ~/gPodderData
to store settings and subscriptions.
If you don’t want to use symbolic links, you have to set environment variables for gPodder to know where to store data.
Setting environment variables in your .profile
doesn’t apply to gPodder.app. You have to edit the launcher to set these variables.
Show Package Contents
gPodder is very conservative with its on-disk format changes, in order to make it easy to rollback to an older release if something is not to your taste. For instance, there has been no change from December 2016 to July 2022.
Moreover, a backup of the database with the old schema is made on each database schema change.
You can find them in $GPODDER_HOME
directory, alongside the Downloads
folder.
The current database is named Database
. Backups are named Database_upgraded-v<VERSION>_<xxxxxxxxxx>
,
where VERSION
is the old version and xxxxxxxxxx
is the timestamp when the upgrade has been performed
(eg. Database_upgraded-v8_1564240521).
To rollback:
Database
file out of the way (rename, move to a different folder, delete);Database_upgraded-vVERSION_xxxxxxxxxx
of your liking to Database
. Be sure to take the largest timestamp
(ie the newest file) if you have dipped in and out of the new release.