Messages

1531

Developers / Re: Exporting Device Templates - ignoring sqlCVS for the moment

« on: March 07, 2010, 12:26:59 am »

It has occurred to me that when inserting devicetemplates into a new system that records should be linked on psc_id, where it exists, not by PK_ as the PK_ could be different where the psc_id should be identical across systems.  The script is still maintaining links by PK_ which could create problems where a DT depends on a table row added by an sqlCVS update.  I'll change this functionality to work on psc_id where it exists.

I'm only testing on 0810 but can I assume that psc_id's are not reused and a psc_id for a device under 0710 will still describe the same device in 0810?

J.

1532

Developers / Re: Exporting Device Templates - ignoring sqlCVS for the moment

« on: March 06, 2010, 11:45:49 pm »

Sure.  Here's a slightly updated version exporting and import viewing work well.  I need to scrub my virtual machine and test some more imports with the updates.  Simple IR based AV devices seem to work on native databases.

Changes:
 * 2010-03-06 - Changes by phenigma phenigma@hotmail.com
 * - fixed updates all entries' FK's for new PK entries after initial inserts
 * - fixed string escaping using mysql function (utf friendly?)
 * - fixed tables gets a unique fakeID when previewing rather than all related tables=-3
 * Known Issues:
 * - does not export/import any files/scripts - only DB entries
 * - does not import DTs marked 'old', use &forceExportType=new during export to test importing
 * - exports redundant data with &forceExportType=new
 * - may create duplicate rows when importing 'old' DTs exported with &forceExportType=new
 * - I'm sure there's lots more...
 
As I learn more about the database/sqlCVS and php/mysql I'm finding more to implement and better ways of doing things... 

J.

1533

Developers / Re: Exporting Device Templates - ignoring sqlCVS for the moment

« on: March 04, 2010, 10:11:38 pm »

I think this is an important abiltity to have and a presents a great learning opportunity to become more familiar with LinuxMCE, PHP, & MySQL.  Over the last couple days I've got the script more or less working to export and import basic user generated device templates.  I have tested this with a few IR A/V devices and I have also tried the PLCBUS template, programmed IR codes and ruby commands are exporting and importing .  The following is a list of some updates and issues:

Changes:
 * - fixed - quotes around field names are gone
 * - fixed - stores all rows from related tables rather than last row only
 * - fixed - updates DeviceTemplate FK's for new related table PK entries after inserts are done
 * - fixed - strings are escaped before inserting to db (ruby looks okay to me)
 * - added - preview insert/update statements before importing to DB
 * Known Issues:
 * - when previewing these are placeholder values PK_DeviceTemplate=-3, PK_InfraredGroup=-2
 * - does not set FK_Manufacturer, FK_DeviceCategory properly in related tables if new
 *   Manufacturer or DeviceCategory entries are inserted by the script
 * - does not export/import DHCPDevice PnpDetectionScript scripts - only DB entries
 * - does not import DTs marked 'old', use &forceExportType=new during export to be able to import
 * - no validation of data can create duplicate rows in tables when importing 'old' as 'new'
 * - I'm sure there's more...

Thanks posde and merkur2k I'm learning lots.  It has a ways to go to deal with all possibilities, and could be a little prettier, but it's in a state where it is worth doing some testing with.  I'd like to rename it at some point (posde?) as it no longer generates a PHP script.  DeviceTemplateRevolver (DTR) or DeviceTemplateXchanger (DTX)... or something.  I expect to tackle the issues mentioned above, feel free to add to the list if you find specific issues.  Backup your data before using.

Use:
 Exporting - the script will display the serialized data and ask you to confirm the export after which it will present the file download dialog.
 Importing - View or Import.  Default is View.  Choosing view will parse the selected file and display the generated insert/update statements without executing any of them.  Choosing Import will immediately execute the insert/update statements and display them at the same time.  Choose view the first time, verify the insert/update statements, hit the back button and choose Import to import the device.

Grab the updated script from: http://filebin.ca/mftsyp/DeviceTemplate2php.tar.gz

J.

1534

Users / Re: TV input always gets set to MD input rather than selected device's input...

« on: March 03, 2010, 05:15:07 pm »

Thanks Posde.  I am aware of that issue and I do see that happening with 2 of my external devices (ps3 and wii templates), when it does I use the orbiter to switch the device off and then select it again from the orbiter and the inputs are set correctly.  This is the issue that davegravy was describing earlier in this thread and I have always seen this behaviour.

My issue seems to be happening with only one of my external devices regardless of whether LMCE thinks the display is on or off. 

Seperate from the inputs not being set properly all of my orbiters show my television is always on the MD's input (resend AV codes screen), even when LMCE has properly set it to another input...  I'm going to keep investigating.

J.

1535

Users / Re: TV input always gets set to MD input rather than selected device's input...

« on: March 02, 2010, 09:30:38 pm »

When I select PVR a 'Turn on' command is sent to the MD (Zotac ION) after LinuxMCE has changed the inputs on the television (this is what is setting the inputs back).  When I select Wii or PS3 a 'Turn On' command is *not* sent to the MD (Zotac ION).  

A noticable difference is that the following line shows for the Wii & PS3 but does not appear in the DCERouter.log when I select the PVR:

Code: [Select]

05      03/02/10 14:45:00.086           Media_Plugin::StartMedia() function call completed with honors! <0x86fdcb90>
So...  It appears that something might be failing when I select PVR which then causes an MD 'on' command to be sent... no orbiter and no PSS because the rest of the system thinks the PVR is showing (no stop media command has been sent).

I'm hoping someone has an insight into this...  anyone?

J.

1536

Users / Re: TV input always gets set to MD input rather than selected device's input...

« on: March 02, 2010, 08:37:19 pm »

So I've done some checking of the DCERouter.log here's what I'm seeing, the inputs actually switch exactly how the DCERouter.log says:

For my television (using the TV input names):
OrbiterSelection     DCERouter.logShows:     ResendAVCodesShows:
Wii                            Component 1                      PC
PS3                           HDMI1                               PC
PVR                           HDMI2 *then* PC                PC

For my Receiver (using the Receiver input names):
OrbiterSelection     DCERouter.logShows:     ResendAVCodesShows:
Wii                            CD                                     CD
PS3                           DVD                                   DVD
PVR                           CBL/SAT *then* MD             CBL/SAT

My system is switching exactly as the log says it is.  The resend AV codes screens on all orbiters show PC input on my TV under all conditions (even when it is not).  The orbiter shows the correct values for what my Receiver *should* be set to.  LinuxMCE is out to lunch when I select my PVR.  The orbiter buttons show the Wii and PS3 are of type 'Game' and the PVR is 'LiveTV' <- could this be the issue?  EDIT: Nope, I changed it to type 'Game' and no difference.

J.

1537

Users / Re: TV input always gets set to MD input rather than selected device's input...

« on: March 02, 2010, 07:23:41 pm »

Code: [Select]

johanr: I will have another look through the templatesIt's not in the templates.

Nope havn't touched the Media Providers section then.

Do a tail -f when testing and you will hopefully see something.

That's next.  Thanks for the suggestions!

J.

1538

Users / Re: TV input always gets set to MD input rather than selected device's input...

« on: March 02, 2010, 12:57:08 am »

johanr: I will have another look through the templates

davegravy: that sounds similar to what I'm seeing here.  I too have created my Wii, PS3 and PVR as IR devices.

J.

1539

Users / TV input always gets set to MD input rather than selected device's input...

« on: March 01, 2010, 11:13:45 pm »

I'm having trouble with LinuxMCE selecting the inappropriate input on my television.  LinuxMCE is always selecting the MD input on my TV rather than the selected AV device's input.  I created device templates for my AV Equipment then used the Connection Wizard to setup A/V pipes.  LinuxMCE properly switches the TV input and then immediately switches it back to the MD input.  If I remove the video pipe from the MD to the television LinuxMCE switches the TV inputs properly (except for back to the MD input of course). The audio pipes are all connected (including the MD) and are switching properly.  This was working properly for me before xmas, I did a reinstall in Jan. sometime and this hasn't been working properly since.

Example:  My MD is connected to the 'PC' input on my television and the MiniDisc input on my receiver.  My PVR is connected to 'HDMI2' on my television and 'DTV/CBL' on my receiver.  If I select the PVR from an orbiter the receiver switches properly, but the television switches to 'HDMI2' and then immediately back to the 'PC' input.  

If I remove the MD's video pipe to the television then selecting PVR from my orbiter switches the receiver and television properly, of course it can't switch back because the MD video pipe doesn't exist.  I have deleted the television device and recreated it but with the same results.  Anyone have any ideas?

J.

1540

Installation issues / Re: NVIDA H264 Codec

« on: March 01, 2010, 07:29:56 pm »

FireMail:  I am seeing stuttering on 1080P material in LMCE now, I was not getting this before and I do not get this when playing the same titles from the command line.

The only problems remaining are:
1) fast forward: for some files it does not work (no effect, even when displayed SPEED X  4.00)
2) fast back: not working.
3) stopping watching the m2ts file make the last screen remain as the backgoung image.

I see similar issues on 1 & 2 here, pause is also not working.  The orbiter doesn't return when the media ends and the PSS doesn't restart when media ends nor when media is stopped manually.

For AAC audio over SPDIF only the following two lines in ~/.mplayer/config are required.

Code: [Select]

channels=6
af=scaletempo,lavcac3enc=1:640:3
J.

1541

Installation issues / Re: NVIDA H264 Codec

« on: March 01, 2010, 02:02:09 pm »

MPEG2 content should be vdpau accelerated through either xine or mplayer.  What container format (File extension) are the files?

The AAC re-encode configuration is not included with the vdpau update, you will still need some portions of the config file I posted for AAC audio over SPDIF.

J.

1542

Installation issues / Re: NVIDA H264 Codec

« on: February 28, 2010, 11:00:01 pm »

What i am doing? Trying to install the package Phenigma created.
I do have mplayer-player, but with no vdpau support.

The changes are in svn so the next beta update, which the wiki says is building now, should include the new mplayer-player package.  Wait for the update to finish and do an apt-get update/apt-get upgrade on your system.

J.

1543

Installation issues / Re: NVIDA H264 Codec

« on: February 28, 2010, 10:48:06 pm »

Vdpau support is committed into lmce svn. An updated den Will be available soon.
/niz23

Thanks Niz!  I know you've been busy.

J.

1544

Installation issues / Re: NVIDA H264 Codec

« on: February 28, 2010, 05:33:20 pm »

It says you're missing package dependencies, like mplayer itself.  I`m not sure why it's not installing automatically for you.  It explains why you are getting the mplayer errors you described in a earlier post.

I didn't have to do anything extra on my MD.  You could try installing the missing packages with apt-get and then dpkg -i the mplayer-player package again.

I'd be nice to know why mplayer is not installed on your fresh system though.

J.

1545

Installation issues / Re: 2 Problems after 810B2 update from 2/23/2010

« on: February 28, 2010, 06:48:02 am »

Myth just launches just doesn't seem to communicate, I would really like to avoid a rebuild, is there a way to re-run the previous scripts?  If the one didn't run, what other scripts do I need to rerun?

It's not that a script didn't run, it's that the /usr/pluto/bin/Diskless_CreateTBZ.sh script takes a long time to run and is often run only when the core is first installed.  It is currently left to the user to run the above script it if he/she wants to install an MD (some people use only a hybrid and have no need to wait for the initial MD image to build).  The script can be run again to update the initial MD image.

I don't think you'll need to re-install your system, your core works... so it must be a myth config issue or a network issue.  I havn't been running myth lately.... been watching HD olympics (I've no way, currently, to get HD tv into LMCE). 

J.