I'm using get-iplayer 3.22 under Linux Mint 19.2

After much experimentation I have to accept that I cannot get get-iplayer to accept my setting for outputradio in the --prefs-add command. The content of 'options'  in the .get_iplayer hidden folder in my $Home directory is set as I request but the downloaded files are saved to the default ($Home) directory. This happens even if I specify the required download directory using the --outputradio parameter in the --get request. However if I specify my desired download location using the -o option, then downloads are saved to my requested directory.

I am also using get_iplayer 3.22 under Win 10. There things work exactly as I expect: I update my preferences using the --prefs-add option and thereafter downloads are placed in the requested location.

What am I doing wrong in Linux?

Follow our instructions to provide a proper report so we can see what is happening on your system.

Thanks for the clear instructions and beg pardon for not following them in the first place. Responding as per the numbered requirements in your Instructions page:

1. Satisfied by original post
2. Ditto
3. Here is the response, showing that the prefs appear to be correct:
"tony@Studio-Mint:~$ get_iplayer --show-prefs
Options in '/home/tony/.get_iplayer/options'
outputradio = /home/tony/LJ_Downloads
4. Satisfied by original post
5. Using Mint 19.2 Cinnamon
6.1. Using this command:
"tony@Studio-Mint:~$ get-iplayer --type=radio --get 39049"
results in the file being written to the '/home/tony' directory, with the above prefs set. The verbose output log file it attached.
6.2. Using the command:
"tony@Studio-Mint:~$ get-iplayer --type=radio --get 39049  -o "/home/tony/LJ_Downloads""
results in the file being written to the requested directory (no verbose log file supplied)
6.3. Using the command:
"tony@Studio-Mint:~$ get-iplayer --type=radio --get 39049  --ouputradio  "/home/tony/LJ_Downloads""
results in the file being written to the '/home/tony'  directory (for obvious reasons, so no verbose log file supplied)
6.4. Using the command:
"tony@Studio-Mint:~$ get-iplayer --type=radio --get 39049  --outputradio  "/home/tony/LJ_Downloads""
results in the file being written to the requested directory (no verbose log file supplied)
7. I'm downloading the following item:
https://www.bbc.co.uk/programmes/m0008pvm

BBC Radio 3 Late Junction Thursday 26th September 2019 "Radio Ping-Pong"
8. Don't think this applies.
9. Attached 'Get_322_log.txt' as requested

No log file attached.

6.3 and 6.4 imply you ran an identical command with different results. In the unlikely event that is the case, you have bigger problems.

If you haven't already, back up and delete the "options" file in your profile directory and re-create it with --prefs-add.

Check --show-prefs with both get_iplayer and get-iplayer (underscore vs. hyphen). Since you have mixed them, it is worth checking. It is difficult, but not impossible, to get them out of sync, and we have no way of knowing what you have done on your machine.

Hmm, not sure why you were unable to 'see' the log-file: I thought the procedure to attach a file to a post was clear enough for me to understand and I thought I followed it correctly. I'll try attaching here, too. Please let me know if I have followed the procedure correctly this time.

Aha! I see you fell into the same trap as me in my items 6.3 and 6.4: they are not identical commands; one of them is in error and this error explains part of the problem I was having, as described in my original post. The error is in the spelling of 'ouputradio'. I must have read this part of the command line I was using dozens of times without noticing the error on input or the error message from get_iplayer on output.

As stated in 6.4, getting the spelling correct results in my getting the expected results. This effect is the natural consequence of a person with perceptual  and age-related issues being required to use a CLI - but that's not a discussion to be opened here.

The inconsistencies between the use of 'get-iplayer' and 'get_iplayer' are, I believe, limited to my typing in this forum and not to my actual usage of the product, but I will try your suggestion of resetting the options file, which has, in my case, very basic contents.
Output log.txt

Thanks for the pointer to the spelling of 'get_iplayer' being a possible source of problems. Being incapable for finding a more suitable source of 'get_iplayer' Version 3.22 for Linux, I used a Snap version, at

"https://snapcraft.io/get-iplayer"

and did not notice that this instalsl 'get-iplayer' 3.22 and not 'get_iplayer'. I continued to use the syntax 'get_iplayer' when setting prefs and trying to find/download programs..

Having now changed to 'get-iplayer' 3.22, and set prefs appropriately, I find that the problems in my OP no longer exist.

I must say I find this all very frustrating and would like to 'complain' to somebody - anybody (to avoid kicking the cat).. I am not by any stretch of the imagination a programmer, developer, Linux expert or indeed any sort of expert. But I do like to listen to music available from the BBC in my own time. This issue resulting from 2 different spellings of 'get_iplayer' has cost me some days of frustration - days which are critical to me since, being almost in my 8th decade, I am extremely time poor.

Can somebody sort this out?

Thanks for the log. We could have saved some time if you had told us you were using the snap version of get_iplayer. As you can see from the log, --outputradio has not been set. As you can also see from the log - and as the documentation warns you - the profile directory for the snap version is not $HOME/.get_iplayer, but $HOME/snap/get-iplayer/common/.get_iplayer ($SNAP_USER_COMMON/.get_iplayer in snap environment). As the documentation also tells you, we don't support the snap version, or any Linux package, and this is one reason why - packagers change things to suit the distro. That said, the spelling difference (which stems from Debian > Ubuntu > Mint package naming rules) doesn't matter if everything is installed correctly. If not, then your installation is screwed up in some way that we can't possibly know, and it would be a mutual waste of time to drill down into it. It's the sort of thing you can only unpick yourself. If you want to complain, take it up with the snap packager. get_iplayer itself is working as it should. Thread closed.

Added: $SNAP_USER_COMMON/.get_iplayer in snap environment is $HOME/snap/get-iplayer/common/.get_iplayer