Great Michael,

I'll try to use it with the italian translation. I'll follow what happens.

Regards

Luke

Hi Michael,

sorry, but only now I've saw your updates on the page of the wiki related to the translation with all the modification to mysql server.

Best regards

Luke

Hi Stefan,

I think me too that all the vdr files will be visible in the video files list selection. But actually could be only a supposition from my opinion, I had to make many tests on it to give a correct response.

Regards

Luke

Hi Michael,

you did a really great job.

Could you please confirm me in which part of my.cnf this string are inserted ? Client, server or other part of the file configuration.

Best regards and congratulation

Luke

Hi Jimbo,

thanks for your references , that was I'm thinking about. Because all the other types of media like music or video are stored there and from any MDs you can play it and manage.

I need to investigate where are all the part involved in start scripts for VDR and change the part related to store recordings in which directory.

Thanks for your info.

Regards

Luke

Hi Stefan,

thanks for your reference. I have already use it. But for me it's necessary to understand which is the mechanism to see a recording made by the core/hybrid from any MDs .

I think that the problem could be related to the default directory in which the recordings were stored that is  /var/lib/video.00 for the actual VDR installation in 0810 . And this directory isn't visible from the MDs I think.

But I'm not sure about that, I'm tring to investigate on it. Could someone else encounter this or not?

Regards

Luke

Dear all,

I would like to understand something about the actual method used by vdr for the recordings.

In this moment I have a distributed installation with one core/hybrid and only one MD at the moment.
All of them are working correctly with live TV using both DVB-T and DVB-S from the core.

When vdr went released in 0710 I don't had much time to spent on it. Now I need to know if it's possible or not to see recordings from MD made by the core or not?

Actually if I schedule a recording from vdr-admin portal web, then I can naturally see them from the core.
But if I went on rec from MD I can't see nothing ?

For VDR configuration in 0810 I still continue use the instruction from 0710 VDR Manual Install from this link http://wiki.linuxmce.org/index.php/VDR_Manual_Install

Is it correct or not ?

For the MD configuration this parameter streamdev-client.StreamFilters must be 0 or 1 ? Because in other post sometimes is set to 0 or to 1 .

If other give the solution, but I can't be able to find it in the forum , please send me the link.

Best regards,

Luke

No problem, please let me know if all will be fixed.

Regards,

Luke

Hi Charles,

the package that is referenced is present on the standard server that we use to install the linuxmce system from scratch with the installer. As you can see :

Code:

http://deb.linuxmce.org/ubuntu/dists/intrepid/lmce-alpha-latest-updates/binary-i386/pluto-slim-server-streamer_2.0.0.44.09093022343_i386.deb

The package is completely public. There is also a reference on the svn server about the last modification on the script to lauch the correct service for the squeezebox server.

Then if you are still missing only this package you can install it from CLI via apt-get install or download and install it again.

I had do it and no problems from there

Hoping that this would help you 

Regards

Luke

Hi Charles,

sorry for the delay. When I 've installed the squeezebox server the pluto-slim-server-streamer and the squeezecenter were removed.

Then I've reinstalled the pluto-slim-server-streamer with this procedure :

Code:

dpkg -i --ignore-depends=squeezecenter pluto-slim-server-streamer_2.0.0.44.09072122164_i386.deb

The problem was that the pluto-slim-server-streamer still had the dependes to squeezecenter, and when you try to do aptitude update and aptitude dist-upgrade you receive some errors for the deps ....

But actually there is a new package as I wrote that resolve the deps problem the version could be :

Code:

                pluto-slim-server-streamer                 2.0.0.44.09093022343

Then you can configure the squeezebox server like the squeezecenter using the HTTP web interface.
Thats all

Best regards

Luke

Hi Emanuele,

actually I think they are still working on it.

Also me, I have the latest version installed, but sometime still happen.
The only think to do, is to kill the PID related to the orbiter and wait for the restart process and all will go well.

Regards

Luke

Hi all,

I would like to thank you someone, because today I saw that is present a new package related to slim server streamer:

Code:

        pluto-slim-server-streamer                 2.0.0.44.09093022343

Actually I don't have the dependences problem.

There is only necessary to modify the /usr/pluto/bin/LaunchSlimServer.sh in this way :

Code:

#!/bin/bash

Params=("$@")
for ((i = 0; i < ${#Params[@]}; i++)); do
        case "${Params[$i]}" in
        -d) ((i++)); DeviceID="${Params[$i]}" ;;
        esac
done
                               

PORT="9090"
PARAMS="--cliport $PORT --audiodir /home/public/data/audio"

sed -ri "s,SLIMOPTIONS=.*,SLIMOPTIONS=\"$PARAMS\",g" /etc/default/squeezeboxserver

invoke-rc.d squeezeboxserver restart

./Slim_Server_Streamer -d $DeviceID

But I think this last modification can still remain like before until the package deps in the webadmin will be modified and updated. As Thom said before in this post.

Best regards

Luke

Hi, as I told the fix is related to the kdm , kde manager.

Hi all,

at the end of the mce install the kde will be automatically bypassed by the launchmanager and the UI selected during the wizard.

Regards

luke

Hi,
it's really strange. If you follow the avwizard wizard, at the end you will be able to use the UI that you select during the wizard.

Take a look to this file :  /etc/pluto.conf

Verify if this keys are correct or not :

Code:

UseVideoWizard = 1
#<-mkr_b_videowizard_e->
AutostartCore=1
AutostartMedia=1
PlutoVersion = 2.0.0.44.09092222331
FirstBoot = false
AVWizardOverride = 0
AVWizardDone = 1
DesktopActivated = 1
DVDKeysCache = /home/.dvdcss
LastSearchTokenUpdate=1254331715
DisableFirewall=0

With this keys I have the UI working well.

Also you can check this file /var/log/mce-installer-20090829_170721.log

Keep the correct file with the correct timestamp, that is related to your installation.

For me is the first time to hear about this kind of situation post a new installation from scratch

Best regards,

Luke