#v4l 2019-03-07,Thu

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)

WhoWhatWhen
***lexano has quit IRC (Ping timeout: 245 seconds) [00:27]
.......... (idle for 47mn)
mchehab has quit IRC (Ping timeout: 252 seconds) [01:14]
...... (idle for 27mn)
jernej has quit IRC (Quit: Free ZNC ~ Powered by LunarBNC: https://LunarBNC.net)
blinky42 has quit IRC (Ping timeout: 246 seconds)
[01:41]
iive has quit IRC (Quit: They came for me...) [01:58]
......... (idle for 40mn)
shuah has quit IRC (Quit: Leaving) [02:38]
...................... (idle for 1h48mn)
b-rad has quit IRC (*.net *.split)
hverkuil has quit IRC (*.net *.split)
lucaceresoli has quit IRC (*.net *.split)
mmattice has quit IRC (*.net *.split)
paul3741 has quit IRC (*.net *.split)
ezequielg has quit IRC (*.net *.split)
pfallenop has quit IRC (*.net *.split)
evalenti has quit IRC (*.net *.split)
darvon has quit IRC (*.net *.split)
[04:26]
..... (idle for 21mn)
juvenal has quit IRC (Read error: Connection timed out) [04:47]
.............................. (idle for 2h28mn)
nsaenz has quit IRC (Ping timeout: 245 seconds) [07:15]
.................. (idle for 1h29mn)
hfr has quit IRC (Quit: Leaving.) [08:44]
Marex has quit IRC (Ping timeout: 259 seconds) [08:57]
........ (idle for 35mn)
hverkuilpinchartl: I posted v3 of my 'Various core and virtual driver fixes' series. Can you take a quick look at my updated 'release' callback documentation? If it is OK, then I plan on making a pull request for this series.
Thank you very much for reviewing this series!
[09:32]
pinchartlI'll have a look
you're welcome
[09:36]
............. (idle for 1h3mn)
***jmleo has quit IRC (Ping timeout: 255 seconds) [10:39]
...................... (idle for 1h46mn)
hverkuilmchehab: ping [12:25]
mchehabhverkuil: pong [12:25]
hverkuil:-)
I'm testing shuah's patch series with my au0828.
[12:26]
mchehabok [12:26]
hverkuilI know how to test v4l, but not dvb. I have nothing connected to the device (I don't have a dvb signal). [12:27]
mchehabwell, in order to test DVB, you need a signal :-) [12:27]
hverkuilI would like to use the dvb utils from v4l-utils to test this: i.e. put the device in dvb mode, check that I can't switch to v4l and vice versa. [12:27]
mchehabyou could start a dvbv5-scan process, seeking for channels [12:28]
hverkuilI don't need to capture dvb, I only need to put the device's tuner in dvb mode (and keep it there) [12:28]
mchehabwhile it is doing that, it should be using both the tuner and the demux
so, it should be locked for analog mode
get a channel file from https://git.linuxtv.org/dtv-scan-tables.git/
it would take ~4-5 seconds trying to tune into a channel
so, the more entries the file you get have, the longer it will be in DVB mode
[12:28]
hverkuilOK, that sounds perfect. [12:30]
mchehabwhat DTV standard does the device you have support? [12:30]
hverkuilI'm not sure, but I would expect DVB-C at least [12:30]
mchehabwhat's the device you have? [12:30]
hverkuilau0828 [12:31]
mchehab(I guess most au0828 are atsc) [12:31]
hverkuilHauppauge something [12:31]
mchehabyou need the exact device model [12:31]
hverkuil(sorry, it's at home and I'm in the office) [12:31]
mchehabor you can run dvb-fe-tool
$ dvb-fe-tool
...
Supported delivery systems:
[DVBC/ANNEX_A]
DVBC/ANNEX_C
DVBT
...
once you check what it supports, you get a file from:
https://git.linuxtv.org/dtv-scan-tables.git/tree/
[12:31]
hverkuilI'll test this tomorrow. I think I should be able to test with this information. [12:33]
mchehabdvb-c for DVBC annex A or C, dvb-s for DVB-S, dvb-t for DVB-T or atsc for ATSC
for example, if your device is ATSC, you could use this file: https://git.linuxtv.org/dtv-scan-tables.git/tree/atsc/us-ATSC-center-frequencies-8VSB
then run dvbv5-scan <file>
in the specific case of the random device I plugged:
$ dvbv5-scan ~/dtv-scan-tables/dvb-t/au-GoldCoast
ERROR command BANDWIDTH_HZ (5) not found during retrieve
Cannot calc frequency shift. Either bandwidth/symbol-rate is unavailable (yet).
Scanning frequency #1 767500000
(0x00) Signal= 100.00%
Scanning frequency #2 585500000
...
btw, you can also pass a value to the command line in order to force a higher delay. For example, to make each channel scan to last ~40 seconds:
$ dvbv5-scan /devel/v4l/dtv-scan-tables/dvb-t/au-GoldCoast -T 40
[12:33]
hverkuilThat's nice for this test. [12:37]
mchehabhmm... actually, this will wait a lot more than 40 seconds... 40 is a multiply factor
(the tuning time actually depends on the device - that's why we use a multiply factor instead of seconds here)
I got confused because dvbv5-zap uses seconds as timeout
anyway, I guess that, for what you need, just dvb-fe-tool and dvbv5-scan should be enough
[12:37]
sailusAhoy!
I've posted a few sets on ImgU warnings fixes as well as on fwnode improvements (including driver fixes).
There's more to come on the fwnode front.
I intend to send pull requests once we have rc1... otherwise it's been quiet.
[12:41]
mchehabhverkuil: I'm almost sure your device is ATSC
looking at drivers/media/usb/au0828/au0828-dvb.c, all devices use the integrated 8522 demod
[12:44]
hverkuilmchehab: you are almost certainly right :-) [12:45]
mchehabit supports only SYS_ATSC, SYS_DVBC_ANNEX_B
(e. g. ATSC and QAM encoding, used for Cable in US)
the US center file should be enough for you to test it with dvbv5-scan
this file has a lot of frequencies already... it should take a while for the dvbv5-scan to complete
if you want a short time, just copy the first entry of it
A file with just this would be the minimal waiting time:
[CHANNEL]
DELIVERY_SYSTEM = ATSC
FREQUENCY = 57028615
[12:45]
***bparrot has quit IRC (Remote host closed the connection) [12:49]
.................. (idle for 1h29mn)
hverkuilkoike: ping [14:18]
............. (idle for 1h2mn)
sailusjmondi: The multiplexed stream patchset starts looking pretty good.
There are a few trivial bits to fix, plus the last patch which needs either a change in the APIs or a rewrite.
I'd prefer a rewrite --- the has_route() op really should not return an error.
[15:20]
***prabhakarlad has quit IRC (Ping timeout: 245 seconds) [15:25]
.... (idle for 18mn)
benjiG has left [15:43]
jmondisailus: Hi Sakari
sailus: Yes, the last patch should be rewritten indeed
[15:49]
....................... (idle for 1h53mn)
koikehverkuil: pong [17:43]
......... (idle for 40mn)
vtnewbHeyy ya'll - I'm trying to sort out an issue with PCI-E Mini board that converts 8 analog streams to h264 from Advantech for my Ubuntu 16.04 Up Squared single board computer. It uses Techwell tw6816, and I get 8 nice /dev/video hooks. Problem is, when I display video I get this: https://i.imgur.com/PqcZyZh.png
also, strangely guvcview won't display the video
I have to modprobe tw68 to get the video hooks, but all looks clean on lspci and dmesg
It's also worth noting, I'm more broadly looking for a solution that can grab 4 analog streams and bring it into Ubuntu for me to use with gstreamer and opencv, I don't need to use this solution, but I'm having a real hard time finding alternatives
[18:23]
................................................... (idle for 4h14mn)
ndufresnevtnewb, interesting ;-P did you try with qv4l2, with various resolution/rate/colorformats ?
I would start investigating with that
guvc is for UVC stuff, this it not
Ubuntu 16.04 is really ancient, you should test on newer OS in case it's already fixed
[22:41]
vtnewbndufresne, Hi ndufresne I'm unfortunately locked into 16.04 with kernel 4.14 for GPU reasons - IntelMedia SDK hardware acceleration for gstreamer encoders/decoders (yikes)
I will try qv4l2 and report back - I'm unfamiliar with that software - glad to branch out
[22:53]
..... (idle for 21mn)
alright ndufresne I installed qv4l2, and saw the board was stuck in PAL, switching to NTSC fixed it
I THOUGHT That was the problem, but didn't see these changes exposed in v4l2-ctl
need to figure out how to do these controls via scripts and I'll be set
thanks for your help
[23:15]

↑back Search ←Prev date Next date→ Show only urls(Click on time to select a line by its url)