Video4Linux2 developer needed for H.264/MPEG-4 capture cards

2011-06-22 Thread Curtis Hall
We are actively seeking a developer for our line of H.264 / MPEG-4
capture cards.  The driver is mostly mature, but several tweaks and
enhancements are still needed, along with continued support to our
customers.  This position would work closely with our team of
developers working on our Linux surveillance application.

You *must* have previous experience with MPEG-4 / H.264 video formats.
 Previous gstreamer experience would be useful.

Information about the card and features of the driver can be found here:

http://support.bluecherrydvr.com/entries/235174-using-the-bluecherry-hardware-compression-open-source-linux-drivers-mpeg-4-h-264
https://github.com/bluecherrydvr/solo6x10

Technically we do not have a requirement on *where* you live, as this
position is a telecommuting position.  We would however like for your
to be available during the times that our US developers are working.

Being that Video4Linux developers are pretty unique, I figured I would
post on this forum first, before we started targeting various job
boards.

We have positions for part and full-time, so please send inquires to
j...@bluecherrydvr.com

Thanks!

-- 
Curtis Hall (c...@corp.bluecherry.net)
Bluecherry - www.bluecherrydvr.com
(877) 418-3391 x 283
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Job posting] Linux software developer with experience with the Video4Linux2 API / ALSA

2010-11-17 Thread Curtis Hall
Note, before posting this I asked in the #v4l channel on freenode if a 
(single) announcement for a job posting would be acceptable.  I was told 
that it should be okay, so if it's against the policy let me know (I do 
apologize if it is).


We are looking for a Linux software developer for our Linux based 
surveillance application (www.bluecherrydvr.com).  This reason I'm 
posting this on the linux-media mailing list is because our application 
uses the Video4Linux and ALSA APIs for accessing video / audio.  We 
recently released a open source MPEG-4 / H.264 driver (see links below), 
and since our application uses this driver we are in need of developers 
with extensive knowledge with Video4Linux and ALSA to extend our 
application.  This position would also handle IP camera integration, 
which is not directly related to the V4L.


The complete job posting with more specific requirements is here: 
http://jobview.monster.com/Linux-video-surveillance-software-developer-Video4Linux-ALSA-Job-Fulton-MO-US-91967697.aspx?fwr=true


If you have any questions please email me off-list (email address is 
below) as not to crowd up the mailing list.


Telecommuting is an option for this position.

Thanks!

Links:

http://git.kernel.org/?p=linux/kernel/git/bcollins/solo6x10-staging.git;a=summary
http://linux.slashdot.org/story/10/06/17/1929230/Bluecherry-Releases-GPLd-MPEG-4-Driver
http://support.bluecherrydvr.com/entries/235174-using-the-bluecherry-hardware-compression-open-source-linux-drivers-mpeg-4-h-264

--
--
Curtis Hall (c...@bluecherry.net)
Bluecherry - www.bluecherrydvr.com
(877) 418-3391 x 283 / (573) 642-6161

--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[bttv] Auto detection for Provideo PV- series capture cards

2010-02-26 Thread Curtis Hall
I'm writing concerning the Provideo PV-149, PV-155, PV-981-* and 
PV-183-*.   These cards, for the most part, are drop in and 'just work' 
with the bttv driver.


However the PV-149 / PV-981 / PV-155 is auto detected as the Provideo 
PV-150, which is not a valid Provideo part number.  The PV-183-* is 
detected as 'Unknown / Generic' and requires setting 
card=98,98,98,98,98,98,98,98.


I believe the text concerning 'detected: Provideo PV150A-1' should be 
changed to 'detected: Provideo PV149 / PV981 / PV155'


I've attached outputs from the bttv kernel logs for the PV-149 / PV-981 
/ PV-183.  If there's something I'm missing please let me know and I'll 
get it for you.


Just for reference the PV-149 / PV-981 / PV-183 series cards are:

PV-149 - 4 port, 4 BT878a chips - no forced card setting required
PV-155 - 16 port, 4 BT878a chips - card=77,77,77,77  (Shares the same 
board and PCI ID / subsystem as the PV-149)


PV-183-8: 8 port, 8 BT878a chips - card=98,98,98,98,98,98,98,98
PV-183-16: 16 port, 8 BT878a chips - card=98,98,98,98,98,98,98,98 
(Shares the same board and PCI ID / subsystem as the PV-183-8)


PV-981-4: 4 port, 4 BT878a chips - no modprobe setting required
PV-981-8: 8 port, 4 BT878a chips  - no modprobe setting required (Shares 
the same board as the PV-981-4)
PV-981-16: 16 port, 4 BT878a chips - card=98,98,98,98,98,98,98,98 
(Shares the same board and PCI ID / subsystem as the PV-981-4)



Thanks!

--
Curtis Hall (c...@bluecherry.net)
Bluecherry - www.bluecherry.net
(877) 418-3391 x 201 

[   10.287287] bttv: driver version 0.9.17 loaded
[   10.287289] bttv: using 8 buffers with 2080k (520 pages) each for capture
[   10.287336] bttv: Bt8xx card found (0).
[   10.287345] bttv :04:08.0: PCI INT A - GSI 22 (level, low) - IRQ 22
[   10.287354] bttv0: Bt878 (rev 17) at :04:08.0, irq: 22, latency: 64, 
mmio: 0xfdfff000
[   10.287367] bttv0: detected: Provideo PV150A-1 [card=98], PCI subsystem ID 
is aa00:1460
[   10.287369] bttv0: using: ProVideo PV150 [card=98,autodetected]
[   10.287392] bttv0: gpio: en=, out= in=00ff [init]
[   10.287810] bttv0: tuner absent
[   10.287893] bttv0: registered device video0
[   10.287925] bttv0: registered device vbi0
[   10.287946] bttv0: PLL: 28636363 = 35468950 ..6hda_codec: Unknown model 
for ALC662, trying auto-probe from BIOS...
[   10.316095]  ok
[   10.316109] bttv: Bt8xx card found (1).
[   10.316125] bttv :04:09.0: PCI INT A - GSI 23 (level, low) - IRQ 23
[   10.316137] bttv1: Bt878 (rev 17) at :04:09.0, irq: 23, latency: 64, 
mmio: 0xfdffd000
[   10.316190] bttv1: detected: Provideo PV150A-2 [card=98], PCI subsystem ID 
is aa01:1461
[   10.316193] bttv1: using: ProVideo PV150 [card=98,autodetected]
[   10.316219] bttv1: gpio: en=, out= in=00ff [init]
[   10.316272] bttv1: tuner absent
[   10.316320] bttv1: registered device video1
[   10.316354] bttv1: registered device vbi1
[   10.316375] bttv1: PLL: 28636363 = 35468950 .. ok
[   10.348096] bttv: Bt8xx card found (2).
[   10.348112] bttv :04:0a.0: PCI INT A - GSI 20 (level, low) - IRQ 20
[   10.348123] bttv2: Bt878 (rev 17) at :04:0a.0, irq: 20, latency: 64, 
mmio: 0xfdffb000
[   10.348160] bttv2: detected: Provideo PV150A-3 [card=98], PCI subsystem ID 
is aa02:1462
[   10.348163] bttv2: using: ProVideo PV150 [card=98,autodetected]
[   10.348197] bttv2: gpio: en=, out= in=00ff [init]
[   10.348258] bttv2: tuner absent
[   10.348302] bttv2: registered device video2
[   10.348337] bttv2: registered device vbi2
[   10.348360] bttv2: PLL: 28636363 = 35468950 .. ok
[   10.380043] bttv: Bt8xx card found (3).
[   10.380058] bttv :04:0b.0: PCI INT A - GSI 21 (level, low) - IRQ 21
[   10.380069] bttv3: Bt878 (rev 17) at :04:0b.0, irq: 21, latency: 64, 
mmio: 0xfdff9000
[   10.380128] bttv3: detected: Provideo PV150A-4 [card=98], PCI subsystem ID 
is aa03:1463
[   10.380131] bttv3: using: ProVideo PV150 [card=98,autodetected]
[   10.380157] bttv3: gpio: en=, out= in=00ff [init]
[   10.380217] bttv3: tuner absent
[   10.380267] bttv3: registered device video3
[   10.380299] bttv3: registered device vbi3
[   10.380319] bttv3: PLL: 28636363 = 35468950 .. ok

[   13.438351] bttv :02:04.0: PCI INT A - Link[APC2] - GSI 17 (level, 
low) - IRQ 17
[   13.438363] bttv0: Bt878 (rev 17) at :02:04.0, irq: 17, latency: 32, 
mmio: 0xd510
[   13.438412] bttv0: subsystem: 1830:1540 (UNKNOWN)
[   13.438414] please mail id, board name and the correct card= insmod option 
to video4linux-l...@redhat.com
[   13.438416] bttv0: using:  *** UNKNOWN/GENERIC ***  [card=0,autodetected]
[   13.438453] bttv0: gpio: en=, out= in=00ff [init]
[   13.474501] bttv0: tuner type unset
[   13.474503] bttv0: i2c: checking for MSP34xx @ 0x80... not found
[   13.476477] bttv0: i2c: checking for TDA9875 @ 0xb0... not found
[   13.477175] bttv0: i2c: checking for TDA7432 @ 0x8a... not found
[   13.477963] bttv0

Re: [bttv] Auto detection for Provideo PV- series capture cards

2010-02-26 Thread Curtis Hall

Devin,

I saw his email and I've been in private communication between him and 
Provideo trying to get the information he needs.  However his request 
was for the PV-947D against the IVTV driver.  These cards are using the 
bttv driver.  I was hoping a bttv maintainer could look at the 
information I posted first to make sure this information wasn't duplicated.


Thanks!

--
--
Curtis Hall (c...@bluecherry.net)
Bluecherry - www.bluecherry.net
(877) 418-3391 x 201 


--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


Re: [bttv] Auto detection for Provideo PV- series capture cards

2010-02-26 Thread Curtis Hall

Mauro Carvalho Chehab wrote:

Let's go by parts:

The entry for PV-150 were added at -hg tree by this changeset:
changeset:   784:3c31d7e0b4bc
user:Gerd Knorr
date:Sun Feb 22 01:59:34 2004 +
summary: Initial revision

Probably, this is a discontinued model, but I don't know for sure.
  
We have been Provideo's US distributor since late 2004 and I've not 
heard of a PV-150 part number, and isn't not a current part number.

This one is easy:
  
[   13.438412] bttv0: subsystem: 1830:1540 (UNKNOWN)


As this PCI ID is not known, it is just a matter of associating the PV-183
ID's with card 98.
  


I figured, thanks

Just for reference the PV-149 / PV-981 / PV-183 series cards are:

PV-149 - 4 port, 4 BT878a chips - no forced card setting required
PV-155 - 16 port, 4 BT878a chips - card=77,77,77,77  (Shares the same
board and PCI ID / subsystem as the PV-149)
  


Hmm... PV-155 shares the same PCI ID as PV-149, but require a different
entry, then we shouldn't add it to the PV-150 autodetection code.
  
Okay.  You can easily access four ports on the PV-155 / PV-981, but to 
access the sub (/dev/videoX,1-3) channels you need to add the modprobe line.

The better would be to check with the manufacturer if is there a
way to detect between those two boards (maybe reading eeprom?).

  
I can find out, but getting technical data from Provideo can be more 
painful then pulling teeth.
Why do you need the card= parameter, if it shares the same subsystem 
ID as the other PV-981 models?


I think I explained that about with the sub channels, if I'm missing 
something let me know.


Thanks!

--
--
Curtis Hall (c...@bluecherry.net)
Bluecherry - www.bluecherry.net
(877) 418-3391 x 201 


--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[no subject]

2010-02-20 Thread Curtis Hall
Subscribe 
--
Sent from my Android phone with K-9. Please excuse my brevity.
--
To unsubscribe from this list: send the line unsubscribe linux-media in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html