Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - colinjones

Pages: 1 [2] 3 4 ... 201
16
Users / Re: Linksys SPA-3102
« on: December 29, 2009, 09:19:29 pm »
I'm a bit confused by exactly what you are trying to achieve with this device - connecting to a VoIP provider or connecting Asterisk to a POTS service, it can do either, but your description seems to be attempting both, which doesn't make much sense to me.

Either way, don't be fooled by the QoS features of these devices. For QoS to be effective it must be enforced at every interface between a higher speed network and a lower one - when in-line on your home LAN both sides of the network are most likely the same speed, and so it will not offer any significant benefit over the QoS enforcement that LMCE's core does for VoIP traffic anyway. Moreover, both will not provide the full benefit of QoS unless you setup QoS on your ADSL router as well, anyway!

By all means use this device to connect LMCE's Asterisk system to a POTS provider, but in this configuration QoS is irrelevant, and you don't need to connect the device to the ADSL modem, only to the LMCE network. Or use it as an ATA on the LMCE internal network, to convert an analogue phone into a VoIP phone for LMCE, but in this configuration QoS is even more irrelevant as the core and the modem are doing the prioritisation. If an ATA is what you want, then any old cheap ATA will do for LMCE.

Background: QoS is usually split into 2 parts, marking/colouring and enforcement. The marking process merely uses rules to select particular traffic and set flags the indicate how they should be treated by later devices in the routing path, but doesn't actually perform any prioritisation or other changes to the flows. Enforcement is the actual process of reordering packets to give some priority over others - this can be done based on the flags set during the marking process performed by previous devices (or even the source) or more often based on marking done by the same device as is doing the enforcement.

17
Users / Re: network is unstable
« on: December 28, 2009, 09:21:34 pm »
you should at least try sharing out a folder on another system (eg a Windows box), letting LMCE add that as another media source, then dropping one of the media files you have had problems with onto that share. Now you can play the same media, with the same MD using the same GB switch, but completely eliminating the NAS (NIC, file system, drives, samba implementation, etc). This is a quick way of eliminating the problem, as if you have the same problem again, you can say with authority it isn't the NAS. Then you can turn your attention to the MD and networking (MD NIC and switch)....

18
Users / Re: DVB Cards info needed for Templates
« on: December 28, 2009, 09:12:41 pm »
if you're getting device busy while vdr is running, that is why :) ... vdr is using the tuners, you have to stop it first so that scan can use them. check out the instructions on the wiki as this is explained.

19
Users / Re: HDHomeRun DVB-T in 810?
« on: December 26, 2009, 11:15:44 pm »
There were some bugs that where found preventing the HDHR from getting properly detected and installed, this has been fixed and will be rolled out within the next few updates.


Mandingo


with the DVB or ATSC version? or doesn't it matter (the drivers are different, so I assumed you would have to distinguish and install the appropriate one)

20
Installation issues / Re: Black screen after installation is finished
« on: December 26, 2009, 11:12:13 pm »
hacking LMCE so that it works with only 1 NIC isn't solving problems, its creating them! please use it as it was designed, with 2 NICs, otherwise you are breaking a lot of its functionality and it certainly will not be supportable by the community... for the sake of a $15 NIC, its not worth it!

21
Installation issues / Re: LinuxMCE constantly scanning network share.
« on: December 26, 2009, 10:42:03 pm »
certainly an option.... but don't forget, besides power consumption and perhaps a little noise, drives running regularly (not even constantly) is not that big an issue... most drives are built to be hammered 24/7 for years at a time without issues

22
Installation issues / Re: LinuxMCE constantly scanning network share.
« on: December 25, 2009, 08:34:53 pm »
not presently, UpdateMedia does not appear to have any external scheduling either using at/cron or within the UpdateMediaDaemon or UpdateMediaDaemonControl scripts. So I assume that the sleep for 2 mins is actually within the UpdateMedia binary, so would require the code to be changed and recompiled. Quite frankly, given the daemon structure and the ability to spawn UpdateMedia processes at will, I don't think it is very elegant to have the UM binary just continue scanning indefinitely, just with 2 min sleeps built into the code ... it would be better that the daemon provided the scheduling in the script, spawned UM periodically for a single pass then exit. Or even a cron task calling the daemon with an option set to trigger it to do the spawn, thus retaining the enabled/disabled/status functionality... but that's just not how it currently works. So to change this requires someone with a dev env, and I doubt this is anywhere on people's priorities.

23
Installation issues / Re: LinuxMCE constantly scanning network share.
« on: December 25, 2009, 12:46:31 pm »
its accessing the drive because (as with any media centre) it regularly scans the folders to check for new media and add them to the database.... you really don't want to disable this, as it is incredibly inconvenient having manually to scan in every piece of new media you add.

24
Users / Re: LinuxMCE in action?
« on: December 22, 2009, 08:43:58 pm »
its certainly something that LinuxMCE could be used to do, and along with the Asterisk integration, tell the house automatically to call your neighbours or emergency services. However, that's not proof-positive, as there are plenty of other systems that could have been used to do the same thing. If the term "video feed" is acurate, then it probably wasn't LMCE...

25
Users / Re: Auto Tagging media
« on: December 22, 2009, 08:23:24 pm »
The MP3s are easy - to do these in bulk, use a 3rd party ID3 tag program such as mp3tag. This will allow you to make bulk changes (such as set the Album/Year/Artist atributes for all files in a folder, useful when doing an album), it also allows you to set tags based on a matching pattern using the file name, and to query online databases.

Once the ID3 tag is set inside the MP3 file, LMCE's updatemedia scanner will read these tags into the LMCE library database and you are done. Unfortunately, doing the same for DVDs isn't possible, as there is no embedded ID3 tag, the data is stored in a .id3 file next to the main file, so you will probably need to use the web admin/online tools. Worst case you can set any attribute manually for any media file in the web admin by going to the Media File Sync option menu, then navigating to the file using the left and right panes, once displaying the files properties in the right pane, you can add/delete/modify any attribute from there.

26
Users / Re: DVB Cards info needed for Templates
« on: December 22, 2009, 01:22:04 pm »
sorry can't help, I've never tried to get that card working with MythTV. However, I'm certain that totallymaxed's crew has!

27
Users / Re: Video Files: Need advice
« on: December 20, 2009, 08:45:19 pm »
yes, .iso and .dvd are treated the same (since 0710), just put the files in a LMCE video folder and it will scan them in. As Sambucca says, you will want to tag them to make them easier to sort through.

pretty much by definition reducing the size of a video file will reduce its quality. However if you use a decent program, get the settings right and use a good codec you can minimise this loss of quality - perhaps Handbrake. BTW, if you already have 300 .iso files, I wouldn't worry about the size of the odd .avi file, an .iso file is almost always going to be massive per hour of video compared with just about anything else! You are probably focusing on the wrong size issue

28
Users / Re: Magical dissappearing media!
« on: December 19, 2009, 10:28:44 pm »
obviously I'm not the one for that, but perhaps a kludge, interim solution would be to force mount all devices immediately prior to UM running, ugly but would probably work for now.

Looking at the autofs config it looks like the timeout is 30 seconds. Looking at the auto.master config and our autofs script in /etc/auto.PlutoStorageDevices reveals a pretty hefty script which includes SQL queries, etc to identify the correct LMCE devices to mount.... I'm assuming that running this script is causing the race condition you refer to, its non-deterministic whether the script completes and the mount finishes before UM actually looks at the path and sees there are no files.... I guess that means that UM does indeed think the device/drive is mounted but that the files have gone missing (rather than the device simply not being available) and that would cause a significant amount of SQL activity, marking all those files as missing, rather than just the device being off line....

29
Users / Re: Magical dissappearing media!
« on: December 19, 2009, 10:05:28 pm »
thom - wouldn't the UpdateMedia process itself cause autofs to remount the drive, and therefore be visible as UM scans? The impression I got was that when autofs umounts a drive, the drive still appears to be there in the path, but just not actually mounted, and it only physically disappears from the path when you actually disconnect the drive. So wouldn't UM think it is still there, attempt to scan it, and that action of 'touching' the drive path remounts it in time for UM?

So is UM thinking the drive is there and mounted, as the path exists, but manages to scan the path and see there are no files before autofs remounts the drive (rather than UM thinking the drive is actually fully unmounted)? Or is something else happening here I haven't understood?

30
Users / Re: DVB Cards info needed for Templates
« on: December 19, 2009, 09:54:14 pm »
I have the Nova-T-500 which is a USB connection through the PCI interface. I couldn't see a specific PCI entry for it, but I suspect it is the VIA USB card (as I don't think I have any other VIA in the system, the mobo chipset is nVidia)

Code: [Select]
01:09.0 0c03: 1106:3038 (rev 62) (prog-if 00 [UHCI])
        Subsystem: 1106:3038
        Flags: bus master, medium devsel, latency 64, IRQ 21
        I/O ports at cc00 [size=32]
        Capabilities: [80] Power Management version 2

01:09.1 0c03: 1106:3038 (rev 62) (prog-if 00 [UHCI])
        Subsystem: 1106:3038
        Flags: bus master, medium devsel, latency 64, IRQ 19
        I/O ports at c800 [size=32]
        Capabilities: [80] Power Management version 2

01:09.2 0c03: 1106:3104 (rev 65) (prog-if 20 [EHCI])
        Subsystem: 1106:3104
        Flags: bus master, medium devsel, latency 64, IRQ 18
        Memory at fd2fe000 (32-bit, non-prefetchable) [size=256]
        Capabilities: [80] Power Management version 2

from lsusb -vv

Code: [Select]
Bus 003 Device 002: ID 2040:9941 Hauppauge
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  idVendor           0x2040 Hauppauge
  idProduct          0x9941
  bcdDevice            1.00
  iManufacturer           1 Hauppauge
  iProduct                2 WinTV Nova-DT
  iSerial                 3 4028962000
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength           46
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower              500mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           4
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass      0
      bInterfaceProtocol      0
      iInterface              0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x01  EP 1 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x82  EP 2 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               1
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x83  EP 3 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0200  1x 512 bytes
        bInterval               1
Device Qualifier (for other device speed):
  bLength                10
  bDescriptorType         6
  bcdUSB               2.00
  bDeviceClass            0 (Defined at Interface level)
  bDeviceSubClass         0
  bDeviceProtocol         0
  bMaxPacketSize0        64
  bNumConfigurations      1
Device Status:     0x0000
  (Bus Powered)

v4l2-ctl didn't work, its looking for a device here, /dev/video which doesn't exist (running 0710) there is a device under /dev/dvb... several directories and devices for 2 "adapters" etc, but using the --device= option just reports:

ioctl: VIDIOC_ENUMINPUT

I didn't have to compile anything, however I am not using this DVB card right at the moment.

hth

Pages: 1 [2] 3 4 ... 201