Quote Originally Posted by Darren King View Post
I did not know that. I had an email from someone who said they had distorted and/or no sound through the PAL tuner using the OzTiVo palmod and found there was a modded version for South Africa on the TiVoZA image which fixed things
The TivoZA image is a modified version of the OzTiVo 1.4 image and contains the oztivo palmod 3.1.

Quote Originally Posted by thomson View Post
If you have a look at line 470 (palmod.c) of the attached code (in particular the few lines commented out before it) then you will see what could be done to fix the situation. There are basically two options... we could sit in a loop trying to autodetect, or default to NICAM.
Sitting in an autodetect loop may be worthwhile as in areas where there is a poor signal this could help the situation but I think the simpler and possibly better option would be to allow the user to specify their format (using palmod_config as per Peters suggestion) and when the autodetect fails, rather then defaulting to Zweiton Stereo, it could default to the users specified format. Another option could be to allow the users to specify a forced option or alternatively select autodetect which would then run in a loop.

Quote Originally Posted by thomson View Post
I think the whole PAL-B/G (5.5MHz offset) versus PAL-I (6.0MHz offset) is a red herring as this is only required for the RF Output support.
It's only when using RF that the audio drop-outs occur.

Quote Originally Posted by thomson View Post
Although if you wish to have a PAL-I (6.0MHz offset) RF Output signal then a change on line 714 (palmod.c) from 0x8a480004 to 0x8a500004 would be required.
It would be nice to be able to set the preferred setting (e.g. PAL-I, PAL-B, etc) via palmod_config. If we were to have a list of available PAL formats, could we base the audio selection on this or would it be best to leave that as a separate setting?

Quote Originally Posted by thomson View Post
I can recompile the source with these changes if required.
I'm more then happy to help with the compilation but if you're happy to do it then yes please as you're far more familiar with palmod than me.

Just as an aside, would it not be worth pulling out the "tuner_chans.h" file and storing the each countries settings in a separate text file? Going this route would mean that palmod doesn't need to be recompiled whenever new channels are added and users could automatically receive channel updates via the 'upgrade_oztivo' script. The palmod_config could then be adjusted to allow users to specify the file containing the tuner settings for their area.

Quote Originally Posted by petestrash View Post
To make version control easier, would it not be possible just to have the one palmod for all regions with the offsets controlled by palmod_config ?
I think a unified version for all countries with the necessery settings configurable via palmod_config would be a great idea.

It looks like thompson has a different version to the current oztivo palmod 3.2, would be interesting to know what differences there are aside from the "Mark 2" adjustments and the "tuner_chans.h" file. Something else I spotted in thompson's palmod (not sure if it's in palmod 3.2) is the ability to set the widescreen setting via palmod_config