Messages

16

Developers / Re: Myth backward incompatiblity

« on: May 06, 2008, 06:07:43 pm »

While it does sound cool, I don't know where to begin.  I googled dcegen trying to find some usefull documentation, but found none.  I do know how to program in c++,perl, and vb but in Windows.  I could get a bluetooth headset, but I would need a program like tcpdump to read the raw stream and then decode it.  Then I would have to know communicate with LinuxMCE to tell it about the device.  I assume all the data is stored in the mysql database, but I could be wrong.  Where do I find this kind of documentation??

17

Developers / Re: Myth backward incompatiblity

« on: May 06, 2008, 02:57:23 pm »

Supporting bluetooth headsets was my next question.  How about when I go into my cell phone and click "scan for headset", it find a headset named "LinuxMCE" (or similiar).  In other words a software headset, and therefore LinuxMCE could record entire conversions or just act as an answering machine.  Also if possible use bluetooth to download all phone data ie. (caller id,phonebook,calendar,recent dialed,recent recieved, etc and maybe even backup the internal flash drive). 

18

Developers / Re: Myth backward incompatiblity

« on: May 06, 2008, 05:51:19 am »

Also has anyone considered simulating a bluetooth headset.  Virtually all cell phones support those bluetooth headsets and LinuxMCE could use that to answer your cell phone for you.  Perhaps even allow you to talk to someone without even picking up your cell phone.  A nearby mic and speaker,on any frontend, could be used.  Optionally conversations could be digitally recorded.

19

Developers / Re: Myth backward incompatiblity

« on: May 06, 2008, 05:14:59 am »

Can I manually setup it up???

Do you know what the default Bluetooth pin is and/or where to change it.

20

Developers / Re: Myth backward incompatiblity

« on: May 06, 2008, 04:03:50 am »

Is this plug and play ability initiated by upnp, dhcp server, or what??  I have 3 password protect shares that were not detected, and a Netgear eva8000, network printer, and mythdvr  which were not detected.  However, they are outside the reach of LinuxMCE dhcp server.  The LinuxMCE server has 2 nics, the link to the outside network which links to the outside world, and a private network for home automation.  So far nothing is plugged in to the private home automation NIC.

21

Developers / Re: Myth backward incompatiblity

« on: May 06, 2008, 03:14:07 am »

Now, please let us get back to work, without bothering us with questions that we continually answer from people like you who think they know everything, and fail to look at the whole picture. Thank you.
-------------------

  I don't know everything, in fact I know very little about your product.  If I knew everything I would ask any questions and would do everything my self.  The other thing is my comments seem to be mis-interpreted with an attitude that can not be expressed in the plain text format, and was not intended that way.

   I simply meant to convey an actual users experience so that others realize that this is an issue.  In addition, I went through the trouble of explaining what steps I took to work around the issue so that work would not have to be duplicated, and not to appear to be "rambling".  Also, if I was one the annoying masses I would simply whine and complain without trying to do anything to help.

  I hope to actually use your product once my future house is actually built and not just a 3d model. 
Where can I program "\\mythdvr\sharename (and specify user/pass)" so that LinuxMCE can see automount  the share with hard coding it in the mtab or fstab where the username and password would be stored in clear text.

22

Installation issues / Re: Issues with 0710 RC

« on: May 06, 2008, 02:26:04 am »

----Quote------------
And that has relevance, why?
--End Quote--------

Mythbackend on another computer(using protocol version 40)  has 1100GB (not MB) of media files that I would like view, but the mythtv frontend in LinuxMCE can only speak version 31.

23

Installation issues / Re: Issues with 0710 RC

« on: May 06, 2008, 02:02:52 am »

mythtv verison is way to old
my backend speaks version 40 and your systems speaks protocol version 31.

24

Developers / Myth backward incompatiblity

« on: May 06, 2008, 01:37:48 am »

I previously setup mythtv (svn release) on another box, and have loaded all my media files(video,audio, etc) on to it.  I configured it and attempted to connect(expecting much delight) , but the error says I have protocol version 40 and LinuxMCE uses 31.  After downloading the current release version, resolving dependancy, etc still not happy.  This time its the db schema version.  A couple more hours of downloading and compiling and I got the frontend to work.  However,  I can't tell LinuxMCE that the world viewable share name is \\mythdvr\sharename (and specify user/pass) so it can't actually play the files.  I read that you put a wrapper around mythtv so direct upgrade using (svn and svn update) may not be possible, but is still is desirable.  However, implementing a much newer mythtv is possible.  Also because of the wrapper the main interface still uses the old version. Darn!! 

     Also RC1 was release on April 28, why is it not using the new ubuntu version 8.04 because kubuntu is obviously based on ubuntu.  Some kind of forward compatibility would be nice, possibly using "create view" to create a compatible view of the databases.  Otherwise all frontend and backends have to be identical versions, and I not rolling my version back to some version that an archaeologists dug up.