Hello I have a skywalker-1 that has stop working, does anyone know where I can get a power supply for it?
Category: Computer and USB Satellite Receivers and Recording
↧
Skywalker-1
↧
Newtec and TBS6983
Hi guys;
I have TBS6983, i use it to lock frequency on Eutelsat 5 west but i didn't get any thing
even using blindscan by crazycat
11137 V 27572 2/3 DVB-S2 Newtec
what kind of modulation this one, is there a satellite card can lock this kind of signal ?
I have TBS6983, i use it to lock frequency on Eutelsat 5 west but i didn't get any thing
even using blindscan by crazycat
11137 V 27572 2/3 DVB-S2 Newtec
what kind of modulation this one, is there a satellite card can lock this kind of signal ?
Category: Computer and USB Satellite Receivers and Recording
↧
↧
PCs & 4:2:2 Video & Different Apps
I'm experimenting with different PC Software (DVB Dream and ProgDVB) and 4:2:2 video. My PC is an Intel Core 2 quad CPU, 8 GB Ram, Nvidia GTX 460 Video Card running 64-bit Windows 10, connected to an older Samsung LCD 47" via an HDMI cable.
I'm testing with the ESPN Tennis feed on G-19. Here are some observations.
The same settings on either software don't produce the same results. By that I mean some won't render video and the other will. I ended up using the LAV H.264 video codec and the Enhanced Video Render to get the best quality picture on both. I think ProgDVB video is a bit crisper. CPU usage on DVB Dream was between 56 & 64% while ProgDVB was constant 45-46%.
The only issue I see is a regular flutter of the picture that I cannot seem to get rid of and that happens on both applications. Doesn't seem to be CPU related, so I'm not sure what causes that issue. The AZBox plays 4:2:2 flawlessly, but I think the PC pictures are better.
Anyone have better experiences with their setups?
My next test is to try some 4K video off the NASA channel this weekend if time permits.
Thanks.
I'm testing with the ESPN Tennis feed on G-19. Here are some observations.
The same settings on either software don't produce the same results. By that I mean some won't render video and the other will. I ended up using the LAV H.264 video codec and the Enhanced Video Render to get the best quality picture on both. I think ProgDVB video is a bit crisper. CPU usage on DVB Dream was between 56 & 64% while ProgDVB was constant 45-46%.
The only issue I see is a regular flutter of the picture that I cannot seem to get rid of and that happens on both applications. Doesn't seem to be CPU related, so I'm not sure what causes that issue. The AZBox plays 4:2:2 flawlessly, but I think the PC pictures are better.
Anyone have better experiences with their setups?
My next test is to try some 4K video off the NASA channel this weekend if time permits.
Thanks.
Category: Computer and USB Satellite Receivers and Recording
↧
TBS 5990 CI not work blindscan
↧
TBS Open Source Drivers
In another thread I read in a post by crazycat:
Actually it appears those drivers are not just for that one card, but cover several TBS cards, but not all. What I found really interesting was the second link, which made me wonder if TBS is now endorsing open source drivers. Although, those appear to have been forked from the ones in the first link. But anyway, a little bit of searching brought me to this thread in the TBS forum, which gives installation instructions and shows a list of supported cards:
http://www.tbsdtv.com/forum/viewtopic.php?f=86&t=9960
From the comments in that thread I get the impression that they might work with a few additional TBS cards not explicitly mentioned, but I don't know that. However not all cards are supported so if you have an older card in particular it may not work with these drivers.
I have not tried them because of my relative lack of knowledge of Linux, and because the installation instructions seem a bit daunting. My real concern would be that if someone tried to install them and discovered they did not work or that a card they own isn't supported, it might be difficult to roll back to the original TBS drivers.
Still I just wonder if TBS is now officially supporting these, and if there is any real advantage to using these over the original closed source drivers for a person that's not really into programming or Linux. I suspect that just as with the original drivers, they will need to be rebuilt after each Linux kernel update, so unless they offer some real improvement in performance I'm not seeing the advantage here. And if you have a system with an older card and a newer one, I doubt you can mix and match drivers, using the closed source drivers for the older card and the open source drivers for the newer card.
Have any of you guys tried these drivers?
Quote:
Originally Posted by crazycat
P.S. See also linux open-source drivers for si2183 (TBS 6522 only now)
https://github.com/ljalves/linux_media
https://github.com/tbsdtv/linux_media
https://github.com/crazycat69/linux_media
P.S. See also linux open-source drivers for si2183 (TBS 6522 only now)
https://github.com/ljalves/linux_media
https://github.com/tbsdtv/linux_media
https://github.com/crazycat69/linux_media
Actually it appears those drivers are not just for that one card, but cover several TBS cards, but not all. What I found really interesting was the second link, which made me wonder if TBS is now endorsing open source drivers. Although, those appear to have been forked from the ones in the first link. But anyway, a little bit of searching brought me to this thread in the TBS forum, which gives installation instructions and shows a list of supported cards:
http://www.tbsdtv.com/forum/viewtopic.php?f=86&t=9960
From the comments in that thread I get the impression that they might work with a few additional TBS cards not explicitly mentioned, but I don't know that. However not all cards are supported so if you have an older card in particular it may not work with these drivers.
I have not tried them because of my relative lack of knowledge of Linux, and because the installation instructions seem a bit daunting. My real concern would be that if someone tried to install them and discovered they did not work or that a card they own isn't supported, it might be difficult to roll back to the original TBS drivers.
Still I just wonder if TBS is now officially supporting these, and if there is any real advantage to using these over the original closed source drivers for a person that's not really into programming or Linux. I suspect that just as with the original drivers, they will need to be rebuilt after each Linux kernel update, so unless they offer some real improvement in performance I'm not seeing the advantage here. And if you have a system with an older card and a newer one, I doubt you can mix and match drivers, using the closed source drivers for the older card and the open source drivers for the newer card.
Have any of you guys tried these drivers?
Category: Computer and USB Satellite Receivers and Recording
↧
↧
DVBDream and volume
Anyone know how to set the volume to max for the DVBDream app? Seems like every time I change the channel (switch feeds), the volume resets to the minimum setting. Doesn't appear to happen for any other apps. Not fatal, but kind of annoying.
I checked all around in the OS and DVB Dream but can't seem to find any kind of setting.
Using the latest version of DVBDream (just updated yesterday) and Windows 10.
Thanks.
I checked all around in the OS and DVB Dream but can't seem to find any kind of setting.
Using the latest version of DVBDream (just updated yesterday) and Windows 10.
Thanks.
Category: Computer and USB Satellite Receivers and Recording
↧
TBS6908 vs TBS6905
I'm looking to get one of these cards. There is a $100 price difference between them. Anyone have experience with either of these? Is there any difference in picture quality? I want to receive 4:2:2 chans like CBS and some of the new test 4k transponders that are using 16APSK.
Category: Computer and USB Satellite Receivers and Recording
↧
TBS-6925 vs TBS-6983 ???
I've owned a couple TBS-6925 receivers and one TBS-6983.
Even before buying the 6983, I had had success with the 6925 locking transponders with SRs down around 740 (if I remember correctly), however the talk at the time suggested that the 6983 could go down to even lower SR values, which was one of the selling points for my buying that receiver.
Since then, while there have been some features of the 6983 which have made me glad that I bought it, I haven't really noticed any difference with respect to any difference between what one receiver could lock relative to the other.
Recently however, while browsing through the specifications at the TBS web page, I noticed the following:
6925
built in hardware blind scan feature allows scanning of unknown satellite transponder with symbol rate as low as 200ksps
Wide range symbol rates support from 200Ksps to 45Msps
6983
built in hardware blind scan feature allows scanning of unknown satellite transponder with symbol rate as low as 200ksps
Wide range symbol rates support from 1Msps to 45Msps
So, from the specs, it sounds like both can blind scan down to 200 ksps, but that the 6983 apparently doesn't support actually locking transponders below 1000 ksps????
This doesn't make sense. I'm guessing that it's a mistake, however I'm wondering if it could be more related to the ability of software to attain these capabilities.
I can't remember now any examples of transponders I've locked with SR's less than 1000, but I'm pretty certain that I used the Crazyscan blindscan window (ie the one with the constellation display). This window finds the transponder parameters between a frequency bandwidth, then Crazyscan streams that transponder to other programs that can analyze or play the channels. I can't remember ever sucessfully having locked and played channels from a program where you have to enter the parameters directly.
Anyway, I'm just curious whether this is indeed a typo in the specs or is it real, and if real, what differences should be expected in the performance of the two receivers below SRs of 1000.
Even before buying the 6983, I had had success with the 6925 locking transponders with SRs down around 740 (if I remember correctly), however the talk at the time suggested that the 6983 could go down to even lower SR values, which was one of the selling points for my buying that receiver.
Since then, while there have been some features of the 6983 which have made me glad that I bought it, I haven't really noticed any difference with respect to any difference between what one receiver could lock relative to the other.
Recently however, while browsing through the specifications at the TBS web page, I noticed the following:
6925
built in hardware blind scan feature allows scanning of unknown satellite transponder with symbol rate as low as 200ksps
Wide range symbol rates support from 200Ksps to 45Msps
6983
built in hardware blind scan feature allows scanning of unknown satellite transponder with symbol rate as low as 200ksps
Wide range symbol rates support from 1Msps to 45Msps
So, from the specs, it sounds like both can blind scan down to 200 ksps, but that the 6983 apparently doesn't support actually locking transponders below 1000 ksps????
This doesn't make sense. I'm guessing that it's a mistake, however I'm wondering if it could be more related to the ability of software to attain these capabilities.
I can't remember now any examples of transponders I've locked with SR's less than 1000, but I'm pretty certain that I used the Crazyscan blindscan window (ie the one with the constellation display). This window finds the transponder parameters between a frequency bandwidth, then Crazyscan streams that transponder to other programs that can analyze or play the channels. I can't remember ever sucessfully having locked and played channels from a program where you have to enter the parameters directly.
Anyway, I'm just curious whether this is indeed a typo in the specs or is it real, and if real, what differences should be expected in the performance of the two receivers below SRs of 1000.
Category: Computer and USB Satellite Receivers and Recording
↧
Tevii S660 only tuning signals on low band of LNB
Hi,
I am running kernel 4.7.3 and have a Tevii S660 connected through an RG-6 cable directly to a Sharp BS1K2EL100A Single LNB. I am using firmware with the following MD5 checksums:
2946e99fe3a4973ba905fcf59111cf40 dvb-usb-s660.fw
f5d0e999c85d08a229f46e239e9a81b1 dvb-fe-ds3000.fw (the latest version as far as I can tell)
I am not able to tune transponders on the high band properly. My satellite dish is pointing at Hotbird at 13 degrees East in Europe, and I have tried tuning using scan-s2 with an initialization file containing the following:
Unfortunately I don't currently have access to the equipment.
Any ideas on what might be wrong? Has anyone else experienced this or a similar problem? I believe I've tried a few different kernels, and firmwares, but that didn't solve it.
I had problems with the receiver locking up and then not being recognized on reboot, unless the power was disconnected from it too, but that has gone away with the latest kernel, at least for now. Things seem to work ok, except that it still does not tune signals using the high band.
Perhaps it is a driver issue? Something in drivers/media/dvb-frontends/ds3000.c? Could it be a faulty LNB? How likely would that be?
Any help in debugging and solving this would be greatly appreciated.
Thank you in advance
I am running kernel 4.7.3 and have a Tevii S660 connected through an RG-6 cable directly to a Sharp BS1K2EL100A Single LNB. I am using firmware with the following MD5 checksums:
2946e99fe3a4973ba905fcf59111cf40 dvb-usb-s660.fw
f5d0e999c85d08a229f46e239e9a81b1 dvb-fe-ds3000.fw (the latest version as far as I can tell)
I am not able to tune transponders on the high band properly. My satellite dish is pointing at Hotbird at 13 degrees East in Europe, and I have tried tuning using scan-s2 with an initialization file containing the following:
S1 12597000 V 27500000 3/4 35 QPSK
The services I get back are actually from 11727 (which is 12597-10600+9750, hence the conclusion that selection of the high band isn't working).Unfortunately I don't currently have access to the equipment.
Any ideas on what might be wrong? Has anyone else experienced this or a similar problem? I believe I've tried a few different kernels, and firmwares, but that didn't solve it.
I had problems with the receiver locking up and then not being recognized on reboot, unless the power was disconnected from it too, but that has gone away with the latest kernel, at least for now. Things seem to work ok, except that it still does not tune signals using the high band.
Perhaps it is a driver issue? Something in drivers/media/dvb-frontends/ds3000.c? Could it be a faulty LNB? How likely would that be?
Any help in debugging and solving this would be greatly appreciated.
Thank you in advance
Category: Computer and USB Satellite Receivers and Recording
↧
↧
Technisat Skystar eXpress HD Crazycat vs UDL driver
Hello,
I have a problem that drove me crazy for days.
Which is there is no signal for some channels even though those channels are working fine on windows.
I'm using UDL kernel/modules
I was thinking what could be the problem?
I connected the LNB directly to the card without diseqc with no luck.
Today i tried mainline kernel with Crazycat media build,
I was surprised that i got a good signal for those non working channels.
The attached screenshots describes the problem very well
1st 3 screenshots are UDL
4th-5th are Crazycat.
My question, is it me only who face this problem?
How to solve it?
Regards.
I have a problem that drove me crazy for days.
Which is there is no signal for some channels even though those channels are working fine on windows.
I'm using UDL kernel/modules
I was thinking what could be the problem?
I connected the LNB directly to the card without diseqc with no luck.
Today i tried mainline kernel with Crazycat media build,
I was surprised that i got a good signal for those non working channels.
The attached screenshots describes the problem very well
1st 3 screenshots are UDL
4th-5th are Crazycat.
My question, is it me only who face this problem?
How to solve it?
Regards.
Category: Computer and USB Satellite Receivers and Recording
↧
tbs 5990 not work from first time when i running laptop
tbs 5990 not work from first time when i running laptop .
he work after i disconnect usb cable and connect it again or make rest to my laptop .
i try windows 8 and 8.1 and windows 10 64 .. but i still have same problem black screen no signal .
i try connect my device on other pc and i have same problem.
any owner tbs 5990 here have some problem or not ??
i use dvb dream 3.1 with lava code
windows 10 64bit
last tbs5590 driver
my laptop asus g750jh core i7 4700qh - gtx 780m 4gb - 32gb ram ddr3l 2133 mhz
he work after i disconnect usb cable and connect it again or make rest to my laptop .
i try windows 8 and 8.1 and windows 10 64 .. but i still have same problem black screen no signal .
i try connect my device on other pc and i have same problem.
any owner tbs 5990 here have some problem or not ??
i use dvb dream 3.1 with lava code
windows 10 64bit
last tbs5590 driver
my laptop asus g750jh core i7 4700qh - gtx 780m 4gb - 32gb ram ddr3l 2133 mhz
Category: Computer and USB Satellite Receivers and Recording
↧
Packet drops
I have a tbs6908 running on Windows 10 and on average every few hours I get a couple of packet drops. Anyone else get this on any of the tbs cards?
I did the following to rule out some issues. LNB output goes to standalone receiver. Loopout on receiver connects to dvb card. There are no packet drops on the receiver recording at the time that they happen on the dvb recording. I also added a splitter to the loopout to use 2 dvb tuners at the same time and the packet drops happened in both dvbdream and progdvb simultaneously, while not happening in the receiver recording.
I did the following to rule out some issues. LNB output goes to standalone receiver. Loopout on receiver connects to dvb card. There are no packet drops on the receiver recording at the time that they happen on the dvb recording. I also added a splitter to the loopout to use 2 dvb tuners at the same time and the packet drops happened in both dvbdream and progdvb simultaneously, while not happening in the receiver recording.
Category: Computer and USB Satellite Receivers and Recording
↧
Kaffeine 2 - No channels found
Hi all.
I'm trying the latest Kaffeine 2 (2.0.3), built using the instructions at Linuxtv/Kaffeine, but I'm having no luck scanning in channels using either a TBS6220 DVB-T/T2 or TBS6983 pci cards.
I'm trying the latest Kaffeine 2 (2.0.3), built using the instructions at Linuxtv/Kaffeine, but I'm having no luck scanning in channels using either a TBS6220 DVB-T/T2 or TBS6983 pci cards.
I have excellent signal strength and quality on each satellite or terrestrial channels I can receive, w_scan confirms this.
However, I have SNR of 0% when scanning through a satellite with Kaffeine. Signal display shows 85%, (ignorable, as it shows the same % with no cable connected).
I'm using a Universal LNB, no DiSEqC Switch.
Log output from Kaffeine 2.0 -
Code:
28-09-16 10:19:13.254 "Using libVLC with --no-video-title-show"
28-09-16 10:19:13.290 DvbManager::loadDeviceManager: using built-in dvb device manager
28-09-16 10:19:13.410 DvbLinuxDevice::startDevice: found dvb device "P1131716062200002" / "TurboSight TBS 62x0 DVBT/T2 frontend"
28-09-16 10:19:13.412 DvbLinuxDevice::startDevice: found dvb device "P1131716069830001" / "TurboSight TBS 6983 DVBS/S2 frontend"
28-09-16 10:19:13.412 DvbLinuxDevice::startDevice: found dvb device "P1131716069830001" / "TurboSight TBS 6983 DVBS/S2 frontend"
28-09-16 10:19:41.287 QObject::connect: No such slot DvbSLnbConfigObject::reject()
28-09-16 10:19:57.775 DvbRecordingModel::findNewRecordings executed.
28-09-16 10:19:57.775 DvbRecordingModel::removeDuplicates executed.
28-09-16 10:20:14.872 DvbLinuxDevice::setVoltage: ioctl FE_SET_VOLTAGE failed for frontend "/dev/dvb/adapter1/frontend0"
28-09-16 10:20:15.136 tune to: "S 964250 H 22000000 5/6"
28-09-16 10:20:15.136 DvbLinuxDevice::libdvbv5 ERROR Need a LNBf to work
28-09-16 10:20:16.678 DvbDevice::frontendEvent: tuning failed for freq= 964.25 MHz
28-09-16 10:20:16.679 DvbLinuxDevice::setVoltage: ioctl FE_SET_VOLTAGE failed for frontend "/dev/dvb/adapter1/frontend0"
28-09-16 10:20:16.943 tune to: "S 979000 V 22000000 5/6"
28-09-16 10:20:16.944 DvbLinuxDevice::libdvbv5 ERROR Need a LNBf to work
28-09-16 10:20:18.479 DvbDevice::frontendEvent: tuning failed for freq= 979 MHz
28-09-16 10:20:18.480 DvbLinuxDevice::setVoltage: ioctl FE_SET_VOLTAGE failed for frontend "/dev/dvb/adapter1/frontend0"
28-09-16 10:20:18.743 tune to: "S 994000 H 22000000 5/6"
28-09-16 10:20:18.743 DvbLinuxDevice::libdvbv5 ERROR Need a LNBf to work
28-09-16 10:20:20.278 DvbDevice::frontendEvent: tuning failed for freq= 994 MHz
The log shows the silly frequencies tuned in from Astra 28.2E (i.e 964250H, which equates to the correct 10714.25H minus the 9750MHz LO frequency (!). What's that all about?
Needless to say nothing is scanned in during the whole pass of the Astra 28.2 muxes.
The problem seems to lie here - No such slot DvbSLnbConfigObject::reject() - and
DvbLinuxDevice::setVoltage: ioctl FE_SET_VOLTAGE failed for frontend "/dev/dvb/adapter1/frontend0".
Adapter 1 is the TBS6983 tuner I'm using. Any ideas please?
OS is Linux Mint 18
kernel 4.4.0-21 generic
Regards Llew
Category: Computer and USB Satellite Receivers and Recording
↧
↧
Genpix and Kernel 4.4.0 (Ubuntu Xenial 16.04)
Hello all,
Long time Genpix/mythtv user here. I managed to stimble on this forum while looking to resolve some issues. I see some familiar faces from DVBN! I've been using Ubuntu Precise with kernel 3.2.0 for a long while now and I am looking to update to something current. Mostly because I also use the PC for Netflix and the current Chrome browser keeps crashing and I can't install anything new as there are dependency issues.
Anyhow...
I am working with Ubuntu 16.04 and its stock 4.4.0 kernel. Unfortunately the Genpix devices are all locking when I try and use mythtv. Syslog shows the errors
I assume this is because of the old mutex lockup which I thought I had patched the kernel for but I am guessing the patch isn't complete or up to date. Are there any users out there who are in the same boat as me but have figured out what needs to be patched?
Thanks,
Gumby
Long time Genpix/mythtv user here. I managed to stimble on this forum while looking to resolve some issues. I see some familiar faces from DVBN! I've been using Ubuntu Precise with kernel 3.2.0 for a long while now and I am looking to update to something current. Mostly because I also use the PC for Netflix and the current Chrome browser keeps crashing and I can't install anything new as there are dependency issues.
Anyhow...
I am working with Ubuntu 16.04 and its stock 4.4.0 kernel. Unfortunately the Genpix devices are all locking when I try and use mythtv. Syslog shows the errors
Code:
Oct 5 13:20:41 pvr kernel: gp8psk: usb out operation failed.
Oct 5 13:20:43 pvr kernel: gp8psk: usb in 138 operation failed.
I assume this is because of the old mutex lockup which I thought I had patched the kernel for but I am guessing the patch isn't complete or up to date. Are there any users out there who are in the same boat as me but have figured out what needs to be patched?
Thanks,
Gumby
Category: Computer and USB Satellite Receivers and Recording
↧
EBSpro no future ?
hello, anyone know whats the matter with EBS software ? i heard the project has ended ? ![]( "Confused - :confused:")
Category: Computer and USB Satellite Receivers and Recording
↧
manual_media_build.sh
I've put together a bash script that will patch the v4l tree and make it into a v4l-updatelee tree. This allows one to use all the work and improvements that UDL put into v4l-updatelee for kernels of most (maybe not all) kinds. The current kernel for v4l-updatelee is 4.6.0-rc2 and I've successfully ran this script against 4.6.0 release version and 4.4.19. I'm still working on the rejects that happen after the UDL_patch is applied and hope to find a way to eliminate them. If that happens, I can make it a one step process that either compiles the patched tree or exits after patching if there are reject files so they can be dealt with. All comments are welcome.
Jim
-------------------manual_media_build.sh starts below----------------------------------
#!/bin/bash
prep(){
WORKDIR=${WORKDIR:-"/tmp/v4l-`date +%b%d%I%M%P`"}
# test WORKDIR for existance and exit if it does with error message
if ; then
echo "$WORKDIR exists!!! Choose another working place or fix this manually"
echo "and rerun this script."
exit
else
echo ""
echo "First we'll create the work directory and change into it."
echo ""
mkdir $WORKDIR
cd $WORKDIR
fi
}
download(){
echo ""
echo "Now we'll get the source code trees."
echo ""
git clone --depth 1 https://bitbucket.org/updatelee/v4l-updatelee
git clone git://linuxtv.org/media_build.git
}
build1(){
echo ""
echo "Next we build the unpatched v4l modules."
echo ""
cd media_build
./build
}
make_UDL_patch(){
echo ""
echo "Here we build the patch where Updatelee's work is added to the v4l tree."
echo ""
cd linux
tar xf linux-media.tar.bz2
cd ../../
diff -ruP media_build/linux/include/uapi/linux/dvb/ v4l-updatelee/include/uapi/linux/dvb/ > UDL_patch.diff
diff -ruP media_build/linux/drivers/media/ v4l-updatelee/drivers/media/ >> UDL_patch.diff
}
add_patches(){
echo ""
echo "Time to apply the patches."
echo ""
cd media_build
patch -s -f -N -p1 -i backports/api_version.patch
patch -s -f -N -p1 -i backports/pr_fmt.patch
patch -s -f -N -p1 -i backports/debug.patch
patch -s -f -N -p1 -i backports/drx39xxj.patch
patch -s -f -N -p1 -i ../UDL_patch.diff > ../../UDL_patch.log
cat UDL_patch.log
echo ""
echo "Fix any errors shown in the reject files above and run 'cd $WORKDIR/media_build; ./build'"
echo ""
echo "If that runs successfully, run:"
echo " 'make install' as root."
echo " 'cp -R linux/include/uapi/linux/dvb/* /usr/include/linux/dvb/'"
echo " 'cp -R ../v4l-updatelee/firmware/* /lib/firmware/'"
echo ""
echo ""
}
show_help(){
cat << EOF
Running this script without options will create a work directory in the
/tmp directory, download the v4l and v4l-updatelee trees, and patch
the v4l tree with Updatelee's improvements. After the patching process
is complete; you'll need to finish the compilation manually.
Pay attention to the message you'll receive after the patching so you can
finish the compilation.
If you wish to specify a work directory, the format is:
media_build_script.sh your_desired_location
The only other valid options are -h or --help which both display this message.
EOF
}
case "$1" in
'')
prep
download
build1
make_UDL_patch
add_patches
;;
'-h'|'--help')
show_help
;;
*)
WORKDIR=$1
prep
download
build1
make_UDL_patch
add_patches
;;
esac
Jim
-------------------manual_media_build.sh starts below----------------------------------
#!/bin/bash
prep(){
WORKDIR=${WORKDIR:-"/tmp/v4l-`date +%b%d%I%M%P`"}
# test WORKDIR for existance and exit if it does with error message
if ; then
echo "$WORKDIR exists!!! Choose another working place or fix this manually"
echo "and rerun this script."
exit
else
echo ""
echo "First we'll create the work directory and change into it."
echo ""
mkdir $WORKDIR
cd $WORKDIR
fi
}
download(){
echo ""
echo "Now we'll get the source code trees."
echo ""
git clone --depth 1 https://bitbucket.org/updatelee/v4l-updatelee
git clone git://linuxtv.org/media_build.git
}
build1(){
echo ""
echo "Next we build the unpatched v4l modules."
echo ""
cd media_build
./build
}
make_UDL_patch(){
echo ""
echo "Here we build the patch where Updatelee's work is added to the v4l tree."
echo ""
cd linux
tar xf linux-media.tar.bz2
cd ../../
diff -ruP media_build/linux/include/uapi/linux/dvb/ v4l-updatelee/include/uapi/linux/dvb/ > UDL_patch.diff
diff -ruP media_build/linux/drivers/media/ v4l-updatelee/drivers/media/ >> UDL_patch.diff
}
add_patches(){
echo ""
echo "Time to apply the patches."
echo ""
cd media_build
patch -s -f -N -p1 -i backports/api_version.patch
patch -s -f -N -p1 -i backports/pr_fmt.patch
patch -s -f -N -p1 -i backports/debug.patch
patch -s -f -N -p1 -i backports/drx39xxj.patch
patch -s -f -N -p1 -i ../UDL_patch.diff > ../../UDL_patch.log
cat UDL_patch.log
echo ""
echo "Fix any errors shown in the reject files above and run 'cd $WORKDIR/media_build; ./build'"
echo ""
echo "If that runs successfully, run:"
echo " 'make install' as root."
echo " 'cp -R linux/include/uapi/linux/dvb/* /usr/include/linux/dvb/'"
echo " 'cp -R ../v4l-updatelee/firmware/* /lib/firmware/'"
echo ""
echo ""
}
show_help(){
cat << EOF
Running this script without options will create a work directory in the
/tmp directory, download the v4l and v4l-updatelee trees, and patch
the v4l tree with Updatelee's improvements. After the patching process
is complete; you'll need to finish the compilation manually.
Pay attention to the message you'll receive after the patching so you can
finish the compilation.
If you wish to specify a work directory, the format is:
media_build_script.sh your_desired_location
The only other valid options are -h or --help which both display this message.
EOF
}
case "$1" in
'')
prep
download
build1
make_UDL_patch
add_patches
;;
'-h'|'--help')
show_help
;;
*)
WORKDIR=$1
prep
download
build1
make_UDL_patch
add_patches
;;
esac
Category: Computer and USB Satellite Receivers and Recording
↧
Noob-whole Ku/Ka system, lots of questions
Noob here
Getting ready to pull the trigger for a Ku/Ka band system. My purpose is to see/observe all signals on the satellites (other bands will come later). Not just video but beacons, data and radio/audio etc. I want my system to pick up both K bands from bottom to top (example. 10.7 to 12.75GHz) covering such a wide IF (950Mhz to 2,XXX) will not be a problem for non video signals as I will tap w/DC block, an SDRadio into the line, it covers 70Mhz to 6Ghz w/56Mhz BW. Be gentle, I know the info is out there, I have read wikis, RTFM'd and searched posts here. But I am getting brain overload. So if I am getting more that I need or can eventually use, missing something, let me know. Also, I will be using this on an ARCH Linux system so I can look up if the card is supported by V4L and other great Linux utilities (unless you know already).
1) I see that Rick has for the TS/Video, a TBS6983. This will not cover the wider IF. Is there a TBS/other card that can do better? Will Rick carry it? The TBS6522 looks good but does not specify everything (IF coverage etc). Will this one do all the video/TS streams, VCM… QPSK APSK etc? (SDR (hopefully) for everything the card can't do). Does the card power the dish positioner and LNB or do I need a separate box? Everything I have read is mixing in with my 25 years of out-of-date C-band knowledge.
I want to try and do this right the first (or second) time.
Going to post on " Dish Setup, Hardware, Wiring & Setup Installation Help > Noob-whole Ku/Ka system, lots of questions" about Dish/Feed/Positioner etc questions.
Thanks and good night.
Dom
Category: Computer and USB Satellite Receivers and Recording
↧
↧
OS upgrade
I am currently running my PC with an intel core duo E8400 @3ghz... My OS is XP with service pack 3. I would like to know if I can go from my 32 bit xp to a 64 bit windows 7 OS. Don't be bashful about jumping in here.
Dave
Dave
Category: Computer and USB Satellite Receivers and Recording
↧
Fta over local network
Does anyone have any experience with this? I have an hdhomerun on the way for atsc, would like to be able to do the same with satellite. I will be streaming to android TV, thanks in advance
Category: Computer and USB Satellite Receivers and Recording
↧
Audio Surround Questions
Have been unable to get audio from either the Side L/R surround, Back L/R surround, or Center/subwoofer surround outputs on my PC, on any FTA Ku satellite channel ... I only get Front L/R. An unrelated output test program verifies that all PC surround outputs are functional.
Am using a TBS 6925 DVB-S2 satellite tuner card, and primarily DVB Dream viewer software.
Assuming that surround sound audio is present somewhere, has anyone received surround sound on any Ku channels ? If so, which ones ?
If so, are you able to use the PC surround output jacks ? Or is an optical or digital coaxial audio output connection required ?
If so, what audio Codec(s) are you using ?
If so, what satellite DVB viewer software are you using ?
Am using a TBS 6925 DVB-S2 satellite tuner card, and primarily DVB Dream viewer software.
Assuming that surround sound audio is present somewhere, has anyone received surround sound on any Ku channels ? If so, which ones ?
If so, are you able to use the PC surround output jacks ? Or is an optical or digital coaxial audio output connection required ?
If so, what audio Codec(s) are you using ?
If so, what satellite DVB viewer software are you using ?
Category: Computer and USB Satellite Receivers and Recording
↧