Good call golgoj4!

I went in and looked. the first tuner (device 99) has variables defined in pipes.
However we see here that the second tuner (device 100) does not.

See images below.

I will set the second tuner pipes to look like the first, and post back my results. Have to wait a few to reload the router, family is busy utilizing the system at the moment.

Thanks, and Best Regards,

Seth

 
Hi all. I have recently been finding myself using MythTV less and simply watching the "LiveTV <insert device here>" streams lately.
Here is what I have set up:
I have 2 Dish Network receivers
Receiver 1 - using codeset 1 - hooked into the first s-video/white/red of a PVR500 card.
Receiver 2 - using codeset 2 - hooked into the second or daughter card s-video/white/red of the PVR500.

Now when I select LiveTV-SAT-1 I can see the streaming image of the first receiver no problem. Whatever remote I am using works swimmingly.
But....when I try to watch the second receiver, all I get is a black screen.

Now when I use MythTV, both receivers function well. So it is not a connection issue.

I am wondering where I can look to see why the stream from the second receiver is not playing?

Any insight as to where to start digging would be greatly appreciated.

When the Dish PVR I have direct connected to my Living Room TV is recording two events, the wife might like to watch something while I am watching Game of Thrones, and this would cause a great deal of angst, as I am hopelessly addicted to that show. If she fires up MythTV while I am watching a LiveTV stream from the effective Tuner 1 in my setup, I would lose Game of Thrones, and she would take over the tuner. And she hardly ever uses MythTV so this would be a bad thing.


Thanks in Advance, and as always,
Best regards,

Seth

 
You should manage your connections at the core level.

Log into your core. Change to user root:

Code:

sudo -i

Then as root user ssh to the MD. 1st find the MD number, either via webadmin or look in /usr/pluto/diskless. After you have it, and we will use 100 as a random number:

Code:

ssh moon100

From there you should already be connected as user root, and you can continue from here.

A good place to read:

http://wiki.linuxmce.org/index.php/Logging_In

Best Regards,

Seth

 
I just wanted to say. I was looking for something like this for a while. The ability to simply pull up my phone to work the lights in my house, without the need for an orbiter, is truely amazing.

I have already made 2 Desktops full of widgets on my android phone, one for upper level of my home, and one for the lower level of my home.

And my 10.1 inch Archos tablet. Forget about it. I have 2 full screens of widgets on that one, again one for the upper level and one for the lower level.

Amazing stuff here.

Outstanding work.

Best Regards,

Seth

It could be that the 11.4 Live Disk partitioned the hard drive using ext4. Perhaps there is some incompatibility there. You could try running the 11.4 disk again, this time choosing to create the partitions using the ext3 file system.

If you have already done this. Please ignore this post.   

Best regards,

Seth

 
You're welcome.
I can not contribute much to this project, but anything I can do to help, I am more than happy to oblige.

Glad it worked for you.

Best Regards,

Seth

Hi there.
I had this issue as well. Here is what I did to resolve it:

ssh to your core and become root

Code:

sudo -i
identify your media director number - ls -l /usr/pluto/diskless
ssh moonXX - subbing the X's with number of MD
add-apt-repository ppa:ubuntu-x-swat/x-updates
sudo apt-get update
apt-get install nvidia-current

This will update your nvidia driver to 290, which is what is most current. After this completes it will have unloaded the 260 driver and built the new dkms modules for 290.
When it has completed you will need to reboot the Media Director. However, before you do so, you must prevent LinuxMCE from re-installing the 260 driver.
Do this by editing the file nvidia-install.sh

So while still in the Media Director:

Code:

vi /usr/pluto/bin/nvidia-install.sh

right below the #!/bin/bash line add - exit 1

keystrokes for those who do not speak vi:

o  (the letter O)
exit 1
press escape
:wq! - shift+colon wq shift+1

Now you should reboot. Upon reboot, you should be good to go. I tested this last night and after playing MythTV for several hours, there was not an artifact to be seen.   

I am running MythTV with VDPAU Normal setting on a Zotac ION Media Director - GeForce 9400M built in over HDMI. Using HDMI audio as well.


Best Regards,

Seth

 
I will begin a video on my home and LinuxMCE usage this weekend.
I start my Holidays after today, so I will have time to capture many pieces of how I use the system, as well as how it gets used daily by my family, as we are Full-On converted. LinuxMCE is a part of our house.

Cover some media bits, some lighting bits, and some of the cooler media and lighting features of the system.

I will be using one of those digital camcorders, and then I can put them on youtube as well as send you the files directly or put them out on my file server.
Whatever is easiest for you.

I really wish I could come over there and help you, but the $$$ needed to pull it off, are not as easy to come by, this close to Holiday.

Best Regards,

Seth

 
Hi there.
Someone already covered the fix for it here. It is a bug, but this is a temporary workaround:

http://forum.linuxmce.org/index.php/topic,12176.0.html

Best Regards,

Seth

 
Hey there. I may have an answer to your question.

There are really 2 ways to resolve this issue.
One completely removes the lighting function from Showtime event, or any event. This is kind of an ugly hack.
The other will allow you to further customize what it does, when the Showtime event is fired.

To start either way, to modify how an event is responded to, go to:
Advanced > Configuration > Scenarios     from the top of the webadmin:
Then in the left hand column, you will see a list of nested scenarios, the one you want to expand is:

"Scenarios for Event Handlers" and then click the "Watching: <insert room here>"

*** See image below ***

After that the window on the right will show you:

*** See image below ***

Here in this image we see it executes command 245, which is the auto-generated Showtime scenario for my Living Room.

You can either delete this command - Kinda hacky, but possibly not. Or you can modify that scenario by scrolling up in the current left pane, to "Lighting Scenarios" and modify the existing scenario.

Or, you can create a whole new lighting scenario. I did this option, because I wanted to create a lighting scenario that would only fire at NIGHT.
After creating this new scenario, I just changed the number in the "Watching - Living Room, Living Room" scenario, and then I made another one to do nothing with the lights, for use in DAY scenarios. I did this for both "Watching - Living Room, Living Room" and "Not Watching - Living Room, Living Room"

If you play with the scenarios and the call functions, you can do all kinds of crazy stuff.

But the short answer is option One. Either delete the command group from the "Watching - <insert room here>", or modify directly the appropriate Lighting Scenario from the same portion of the web admin page.

Hope this helps. I intend on doing a Wiki entry for advanced scenarios, while on Holidays next two weeks.

Best Regards,

Seth

Wow! 

You know I never noticed that there before.

Thanks!

That is one of the reasons I love this platform so much. Always an opportunity to learn, and members of the community always willing to provide the source of sadi learning.

 

Best Regards,

Seth

I just updated over the weekend. And Now I too am seeing that the sort option is set into filename mode by default. This after a router reload as well as boot up.

I will do some investigation. Not sure if this is ticket worthy or not.

As I have my media stored, series especially, in directories based on seasons. So filename is how I usually sort. But if a ticket should be cut. Let me know. I will do so.

Best Regards,

Seth

 
Hi!

Have you tried changing the Sort Option. I think it might be set to "filename"

Have a look there.

Regards,

Seth

Looks like it is only seeing 1 network interface.

Could you post the output of

Code:

sudo ifconfig

We can see if it is plumbing up a virtual interface off of a single NIC card, and then maybe we can see if you are having a driver issue for the second NIC card not to load, or perhaps there is a bad NIC suspect, so could you also post the output of:

Code:

sudo lspci -v|grep Ethernet

I had this happen to me both because of a driver and because I had a bad NIC card. On two separate installations.

See if we can get it sorted out.

Best Regards,

Seth

I noticed artefacts appearing after watching TV for a while, getting out of mythtv, running the screensaver or watching a video, then they appear. Reboot of the MD fixes that. Nvidia drivers 260 are installed.

I noticed this as well running opengl or vdpau for the Media Director under the Hardware Acceleration option.

Changing this to "auto" resolved the issue. I am running 10.04 using the nVidia graphics on my Zotac ION MD. It uses the GeForce 9400M graphics chip.

After setting the acceleration to "auto" and rebooting the MD, the artifacting went away.

Perhaps this may help. I am running stock 10.04 nVidia drivers, I believe it is 260.

Best regards,

Seth