Suchergebnisse

Is it possible to provide a version with English messages? I really like the additions over original multiquickbutton version but I cannot understand Dutch. Maybe you can internationalize the plugin by using .po messages and then we can provide translation for several languages. Thank you

Why you ask for a new VU model? I am very happy with VU Duo when it comes to hardware performance, what I miss is some improvements that are mostly software related (for example AAC+/DD+ audio)

Thank you all!

Are we going to get the latest drivers in VTI image via online update? If yes, when is this planned? If not, I'll try install them manually. edit: Also please consider for next release to add some of the online EPG import patches to enigma2 (oudeis patch, pli EPG patch, crossepg patch v2) in order to be able to import external EPG (via crossepg or xmltv-import) without restarting enigma2.

Zitat: „Original von xener Zitat: „Originally posted by malakudi So, the CPU runs only at 220MHz? At that speed, it's computing performace would be about 350 DMIPS, much lower even from DM800 (which has a computing power of 450 DMIPS, according to Broadcom). At 333MHz the computing performance is 525 DMIPS according to Broadcom. VU Duo and DM500HD have a computing performance of 1100 DMIPS, so this is a very big difference!“ yes, when you plan to run seti on your satbox. anyone else using sat re…

So, the CPU runs only at 220MHz? At that speed, it's computing performace would be about 350 DMIPS, much lower even from DM800 (which has a computing power of 450 DMIPS, according to Broadcom). At 333MHz the computing performance is 525 DMIPS according to Broadcom. VU Duo and DM500HD have a computing performance of 1100 DMIPS, so this is a very big difference!

I am reviewing a VU+ Solo receiver. In BCM 7325 specs we can read that it is a dual threaded cpu (as BCM7335 of VU+ Duo is), running up to 333Mhz. ( broadcom.com/products/Satellit…Top-Box-Solutions/BCM7325 ) However, both original and VTI image for VU+ Solo don't excibit dual thread smp functionality, and /proc/cpuinfo reports the CPU runs at 220MHz. Why is this? Can we expect an image with smp dual threaded support soon? And what about the 220MHz reported in /proc/cpuinfo? Is this correct? If i…

xmltvimport plugin works in VTI image, but it can't update the EPG data on the fly (it requires an enigma2 restart). In order to support on the fly import, enigma2 must be patched with oudeis patch or pli epg patch. Source for both are available. It would be great if VTI team include at list oudeis patch in the build process of their image. Here is the details of EPG importing (from rytec.be site) Explanation of different kind of EPG patches in images: - No patch used: The box (Enigma2) needs to…

Zitat: „Original von xener ssd disk add 0 °C and 0 dB to system noise and heat. its a best storage for embedded systems.“ Paying 350 euros to get 128GB of storage can't be the "best" option, especially if we are talking about a satellite receiver that costs 420 euros. 128 GBs is only capable to store about 24 hours of HD content. That's only 12 movies or 12 football games. Getting a 2,5 inch disk which generates minimal noise and temperature is a good option. I am using a Samsung 500GB 3,5 drive…

Zitat: „Original von xener Zitat: „Originally posted by nghozzi Hi everybody, I'm buying a HDD for my brand new VU+ DUO. I wonder what will be the best format to go with: 3,5", 2,5" internals or eSata?? My issues are: noise & noise & noise, and then ofcourse performance.. I had a relook 400S and I was incerdibally annoyed by the Disk and the fan noise. So if I opt for a 2,5, does this considerabally lower the noise? Does this type permits me to disable the fan completely? Is the fan in VU+ neces…

I can confirm the above mentioned channels cannot be recorded. I checked to see what is different about the above mentioned channels (HBO Adria etc). Those channels have 9 PIDs. 1 video, 4 audio and 4 DVB subs. ESP HD at Hotbird has even more PIDs, about 17, and it can't be recorded too. So the problem is actually the number of recorded PIDs. I have tested with another channel that has 7 PIDs and recorded fine, so the limit is either 8 or 9 PIDs, Hope this helps to track down the problem.

A wild guess, maybe it is a file naming issue? Maybe the recorded filename has some characters (from the EPG title) that cannot be used in the NAS filesystem.

With 4.9 drivers, LBC package at 21,6E tunes immediately, so low SR on DVB-S2 has been fixed. SR < 2000 for DVB-S hasn't been fixed.

The only missing feature from OE 1.6 is the use of Python 2.6. If VU+ changes their Makefile to use Python 2.6, it should be considered as OE 1.6 compatible.

connect lnb1 to 4 to port 1-4 of the first 420. Connect lnb5 to 8 to port 1-4 of the second 420. Get another 420 and connect lnb9 and lnb10 to port 1-2 of the third 420. Set 410 to mode 1 (there is a switch). Connect first 420 to port 1 of 410, second 420 to port 2 of 410 and third 420 to port 3 of 410. Then configure VU+ tuner with advanced configuration, and set uncommited -> commited sequence. For lnbs1-4, set uncommited port 1, commited port AA, AB, BA and BB. For lnbs5-8 set uncommited port…

Zitat: „Original von RealMagic911 DVB-T isn't really a bug. It is a feuture request.“ We don't want VU+ to implement the DVB-T usb support. We want VU to make the closed source binary modules that offers compatible with a kernel that has DVB, INPUT and I2C enabled. All closed source binary modules should be independent from the core linux services. Making binary closed source modules that include and override for example the DVB functionality (dvb-core.ko) is also a GPL violation, since dvb-core…

Someone requested support for USB DVB-T tuners. USB DVB-T tuners can be compiled for VU+. USB DVB-T requires enabling DVB support, INPUT support and I2C support in the kernel Makefile. Unfortunately, the dvb-bcm7335.ko and dvb-core.ko modules provided by VU+ conflict with a kernel that provides the above mentioned modules. VU+ has to make their modules compatible with a kernel that provides DVB, INPUT and I2C. Then, anyone would built the USB DVB-T modules. DM800 binary modules are indeed compat…

Add also the following minor issues: - No BER indication (it is always 4294967295). Can be checked with "dvbsnoop -s signal" - dvbsnoop PID scan doesn't work "dvbsnoop -s pidscan". This command shows all PIDs in a transponder. It works in DM800 etc - Still no greek characters in VFD (maybe a font is needed?)

Zitat: „Original von scope34 Hi, sorry, but the sympton you have mentioned was not placed in the buglist thread (the one with deadline please see: Buglist V4.4), so it won't be fixed for the next releases.“ Should I post it to the Buglist V4.4 thread? I have tested with latest 4.6 (and all previous releases). There's no rush to be fixed immediately. It would be nice if it is fixed sometime in the near future.

My post has nothing to do with receiver response when it can't lock a signal. I am describing two symptoms of the receiver being unable to lock when low symbol rates are used. The specifications of the Broadcom chip mention SR compatibility from 1000 to 45000, so the mentioned frequencies should be receivable, and they are not. DM8000 can receive above mentioned frequencies, but it was unable to receive them in early firmware releases. So some finetuning is needed in the drivers for low SR, some…