Perhaps your frequency table is something other than "US-CABLE"? It should be the same as in your mythtv-setup screen for your capture card(ALT-S from the frontend).

You might try commenting out that line of the script- I do not know if it is totally necessary.

Make sure you check your /tmp/changer0.log to see if there are any errors....

-Loco

The delayed_settings.sh script won't run properly with my channel_change.sh script. I've got a fresh install of R5F27 in which everything worked "out of the box" (first time ever) except for this tinny audio issue.

I assume it's something I've copied incorrectly and I've being trying various alterations to the scripts to get them to work. My channel changes to the correct station with "./channel_change.sh xxx" and I get major complaints from "./delayed_settings.sh", but at least the scripts are executable and run.

Here is my channel_change.sh script (which changes channels correctly):


Here is my delayed_settings.sh script (copied from the first post in this thread):


Here is the changer0.log output:


If I alter the first line in the delayed_settings.sh script to #1/bin/bash I get the following output in changer0.log:


Any suggestions will be greatly appreciated.

There are some line breakages that should not be there in the initial post. I could not figure out how to change the size of text with the "code" command, so I posted the delayed_settings.sh with the "quote" command instead. Your script needs to look like:

Quote:

#!/bin/bash
# Uncomment this for debugging
#set -vx

DEVICE=$1
exec >>/tmp/changer$DEVICE.log 2>&1

# controls:
BRIGHTNESS=${2:-127} # Picture brightness, actually the black level. [0 - 255]
HUE=${3:-0} # Hue or color balance. [-128 - 127]
SATURATION=${4:-63} # Picture color saturation or chroma gain. [0 - 127]
CONTRAST=${5:-63} # Picture contrast or luma gain. [0 - 127]
VOLUME=${6:-60000} # Overall audio volume. [0 - 65535]

CTL_OPTS="-d /dev/video$DEVICE"
echo ; echo Settings before:
/usr/local/bin/v4l2-ctl -d /dev/video0 --get-ctrl=brightness,hue,saturation,contrast,volume
for i in 0 2 4 6 8 10 ; do
/usr/local/bin/v4l2-ctl $CTL_OPTS --set-ctrl brightness=$BRIGHTNESS >/dev/null
/usr/local/bin/v4l2-ctl $CTL_OPTS --set-ctrl hue=$HUE >/dev/null
/usr/local/bin/v4l2-ctl $CTL_OPTS --set-ctrl saturation=$SATURATION >/dev/null
/usr/local/bin/v4l2-ctl $CTL_OPTS --set-ctrl contrast=$CONTRAST >/dev/null
/usr/local/bin/v4l2-ctl $CTL_OPTS --set-ctrl volume=$VOLUME >/dev/null

# Add any extra ivtvctl commands here, before the sleep.
/usr/local/bin/v4l2-ctl --set-audio-input 1 -d /dev/video$DEVICE >/dev/null

sleep 2
done
echo ; echo Settings after:
/usr/local/bin/v4l2-ctl -d /dev/video$DEVICE--get-ctrl=brightness,hue,saturation,contrast,volume

Sorry about that. I edited the initial post too. Also, make sure there are no extra spaces at the end the lines......

-Loco

Thanks for that, but there's been no change in results or the changer0.log file. I created your new delayed_settings.sh file in /usr/bin/local, did a chmod u+x as root on it, and I'm still where I was before.

What I can't understand is if I try to run delayed_settings.sh in /usr/local/bin by typing in ./delayed_settings.sh, I get the following error message back:


It seems there's something very basic I'm doing wrong here, but not knowing Linux too well, I can't figure what it is.

Maybe it is still an extra return/space issue. You can try to clean up the file with this command:



Then see if your channel change script works after that.....

Also, the delayed_settings script REQUIRES variables ($DEVICE, etc), that is why the last line of the script has all of those weird slashes and returns. So I do not think just trying to run delayed_settings.sh from your command line will cut it.

Maybe it is working? Run your first channel change script to a random channel once. Then, type


Then, edit your first channel change script and change the "BRIGHTNESS" line value to 166 instead of 127.

Now, Run your first channel change script to a random channel again. Again, type

Did the brightness value change?

It's now fixed. It was the extra space issue. Using the sed command did the trick.

P.S. - I knew that running delayed_settings.sh by itself would not work, but I expected it to do something other than give me a "bad command" error message if it was working properly. Now if I run delayed_settings.sh by itself, the script just waits for input, which would be the expected behavior.

Thanks for the help!

I have RF27 and there is no "delayed_settings.sh" in /usr/local/bin/

I did a find on the entire drive and couldn't find it.

Do I need to create this script? Will it run automatically?

_________________
-hunter

The delayed_setiings script is definitely an "after market add-on".



Weird slashes? That's called "backslash line continuation".

Also it doesn't require the variables, it requires the command arguments they expand to.

When I run the delayed_settings.sh script, I get the following in the changer.log:

Settings before:
brightness: 128
hue: 0
saturation: 63
contrast: 63
volume: 58880
Failed to open /dev/video: No such file or directory
Failed to open /dev/video: No such file or directory
Failed to open /dev/video: No such file or directory
Failed to open /dev/video: No such file or directory
Failed to open /dev/video: No such file or directory
Failed to open /dev/video: No such file or directory
Failed to open /dev/video: No such file or directory
Failed to open /dev/video: No such file or directory
Failed to open /dev/video: No such file or directory
Failed to open /dev/video: No such file or directory
Failed to open /dev/video: No such file or directory
Failed to open /dev/video: No such file or directory

_________________
-hunter

EDIT: I removed this due to erroneous info!

-Loco

Uh, no that would be bad. $0 is the name of the command being run, $1 is the first command line argument. This has been like watching bright kids with no experience and limited understanding of what they're trying to accomplish play plumber with the contents of a fully stocked plumbers truck. Amusing up to a point, before it becomes alarming.

The device number is supposed to be passed to the delayed_settings.sh script as the first command line argument (this is so you can have multiple changers with card specific settings use one common backend script). Based on the error message _no_ command line arguments were being passed, like hunter44102 was running it manually rather than from a changer script with all the command line arguments. Let's get back to basics...

This is the (updated) changer script. It's intended to be used as your external channel changer script(*) specific to a given input connection! It does three important things:

1) It changes the channel.
2) It knows the override settings you want specifically for this input and launches the delayed setting script with them.
3) It exits immediately with a "success" return code (so that MythTV will go about it's business), leaving the delayed setting script waiting in the background to make corrections later.

BTW - This is NOT a perl script so calling it anything ".pl" is a misnomer. It's a shell script so you should use ".sh" if anything as the extension. For example "change_tuner0.sh"



This is the (updated) delayed settings script. It does two important things.

1) It sends the desired settings to the driver for the card in question.
2) It waits and does it again (and again, and ...) this is to make sure that it "gets the last word" with it's settings overriding any settings that MythTV makes after completing it's tuning.



BTW - Running "v4l2-ctl --help | more" and playing with the options is very helpful for understanding what this script does and highly recommended... Using scripts like this without understanding what they're intended to do and at least an outline of how they work, is like "washing" your clothes in a food processor. The results are likely to be less than satisfactory.

(*) You set your external channel changer script in mythtv-setup under "Input Connections". External channel changers are an "escape" mechanism to tune devices like cable boxes which MythTV can't control directly. We're abusing that escape mechanism, using it for a device that MythTV could control directly, so that we can apply other settings along with each channel change.

TJC, thanks for your kind inputs in here. I believe it is with the attempts and support of everyone in the community The product only gets better.
I know you have certainly steered me down the right roads and helped me bunches.

So, my question, I have a PVR -150 My main tuner that exhibits the Tinny Audio problem occasionally. IT is the oldest of all my tuners as far as firmware, so there may be a correlation there.

I am trying to determine based on the posts here what is the correct files to put in. This is my MBE and only has one tuner /dev/video0 and I use the S-Video inputs on it.

I control Dish Network boxes and here is my change_channel.sh script.


This script works flawlessly for changing my channels. As long as Blaster is working I have not had a misfire.

Can you please provide assistance as to how I can attempt to fix the Tinny Audio it sounds like this script fixes it, I jut am not sure how to apply it.

TIA.

TJC - Thanks.. My problem was that I was calling it from my .pl channel changing script. I will try to put it in "Input Connections" instead.

_________________
-hunter

Maybe a stupid question but is there a reason that the v4l2-ctl command cound not just be put into a cron job to run every minute? I suppose you could wind up with up to a minute of tinny sound but it would straighten itself out after that.
Am I missing something?

_________________
LINHES 8.6.1 BE/FE - MSI K9N6SGM-V with AMD A64 X2 4600+, 4GB Ram. 1.5TB WD. HDHR Prime. Nvidia GT210. MCE remote.
FrontEnd - Dell Vostro 400 3.0GHz Core2Duo NVidia GeForce210. MCE Remote

It could glitch the recording. Not big deal for the first 20 seconds but every 60 seconds for the duration of the recording is a much bigger exposure.