linux1394-user Mailing List for IEEE 1394 for Linux (Page 417)
Brought to you by:
aeb,
bencollins
You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(29) |
Nov
(36) |
Dec
(46) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(60) |
Feb
(82) |
Mar
(46) |
Apr
(50) |
May
(89) |
Jun
(60) |
Jul
(80) |
Aug
(130) |
Sep
(104) |
Oct
(105) |
Nov
(123) |
Dec
(107) |
2002 |
Jan
(142) |
Feb
(105) |
Mar
(63) |
Apr
(117) |
May
(136) |
Jun
(75) |
Jul
(105) |
Aug
(103) |
Sep
(149) |
Oct
(149) |
Nov
(98) |
Dec
(144) |
2003 |
Jan
(161) |
Feb
(100) |
Mar
(118) |
Apr
(126) |
May
(157) |
Jun
(173) |
Jul
(156) |
Aug
(89) |
Sep
(83) |
Oct
(106) |
Nov
(84) |
Dec
(69) |
2004 |
Jan
(119) |
Feb
(233) |
Mar
(232) |
Apr
(104) |
May
(113) |
Jun
(132) |
Jul
(87) |
Aug
(129) |
Sep
(186) |
Oct
(88) |
Nov
(148) |
Dec
(180) |
2005 |
Jan
(223) |
Feb
(176) |
Mar
(148) |
Apr
(193) |
May
(188) |
Jun
(236) |
Jul
(144) |
Aug
(89) |
Sep
(44) |
Oct
(86) |
Nov
(114) |
Dec
(89) |
2006 |
Jan
(94) |
Feb
(97) |
Mar
(57) |
Apr
(117) |
May
(46) |
Jun
(63) |
Jul
(51) |
Aug
(72) |
Sep
(50) |
Oct
(142) |
Nov
(70) |
Dec
(52) |
2007 |
Jan
(60) |
Feb
(67) |
Mar
(80) |
Apr
(81) |
May
(78) |
Jun
(52) |
Jul
(64) |
Aug
(55) |
Sep
(40) |
Oct
(87) |
Nov
(70) |
Dec
(44) |
2008 |
Jan
(80) |
Feb
(12) |
Mar
(82) |
Apr
(64) |
May
(33) |
Jun
(53) |
Jul
(41) |
Aug
(26) |
Sep
(35) |
Oct
(21) |
Nov
(30) |
Dec
(42) |
2009 |
Jan
(17) |
Feb
(32) |
Mar
(10) |
Apr
(19) |
May
(19) |
Jun
(28) |
Jul
(41) |
Aug
(14) |
Sep
(5) |
Oct
(46) |
Nov
(23) |
Dec
(20) |
2010 |
Jan
(46) |
Feb
(13) |
Mar
(9) |
Apr
(2) |
May
(19) |
Jun
(28) |
Jul
(37) |
Aug
(23) |
Sep
(5) |
Oct
(32) |
Nov
(19) |
Dec
(18) |
2011 |
Jan
(23) |
Feb
(9) |
Mar
(19) |
Apr
(38) |
May
(83) |
Jun
(30) |
Jul
(46) |
Aug
(32) |
Sep
(6) |
Oct
(3) |
Nov
(25) |
Dec
(31) |
2012 |
Jan
(21) |
Feb
(12) |
Mar
(19) |
Apr
(7) |
May
(27) |
Jun
(7) |
Jul
(2) |
Aug
(15) |
Sep
(8) |
Oct
(11) |
Nov
|
Dec
(3) |
2013 |
Jan
|
Feb
|
Mar
(2) |
Apr
(1) |
May
(1) |
Jun
(14) |
Jul
(1) |
Aug
(3) |
Sep
(4) |
Oct
(5) |
Nov
|
Dec
|
2014 |
Jan
(14) |
Feb
(2) |
Mar
(1) |
Apr
(3) |
May
(2) |
Jun
(7) |
Jul
(2) |
Aug
(1) |
Sep
|
Oct
(14) |
Nov
(5) |
Dec
(18) |
2015 |
Jan
(3) |
Feb
(1) |
Mar
(3) |
Apr
(5) |
May
|
Jun
(3) |
Jul
(4) |
Aug
|
Sep
(2) |
Oct
(11) |
Nov
(2) |
Dec
|
2016 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
(5) |
Jul
(1) |
Aug
(1) |
Sep
(2) |
Oct
(2) |
Nov
|
Dec
|
2017 |
Jan
|
Feb
(5) |
Mar
(7) |
Apr
|
May
(4) |
Jun
|
Jul
(1) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
|
2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
(1) |
Mar
(2) |
Apr
|
May
(1) |
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(6) |
2021 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Felix T. <ta...@ee...> - 2001-02-14 23:37:26
|
---------- Forwarded message ---------- Date: Wed, 14 Feb 2001 18:35:08 -0500 From: James Fung <fu...@ey...> To: Felix Tang <ta...@ey...> Subject: Sony Vaio C1VE 1394 compat Has anyone tried Linux on the C1VE Vaio, or know what type of controller it has? If so, does the 1394 controller work with the linux1394 drivers (is it a CXD3222?) -James |
From: Stefan L. <Ste...@sn...> - 2001-02-14 20:08:46
|
On Mit, 14 Feb 2001, Eugene Kuznetsov wrote: > Hello Dan, > > Tuesday, February 13, 2001, 8:57:44 AM, you wrote: > > DD> A DV AVI codec that uses libdv and works with the gstreamer framework is on > DD> my list of things to do, but not a high priority. > > I recently received a patch for avifile that enabled decoding of DV > AVI files. It used Windows DirectShow filter ( dll name qdv.dll ). > I'll put it in one of future releases. I don't think that this is the future of linux video applications, because that would force me to get MS-windows XYVZ or so. :-((((((((((((((((((((((. -- mfg Stefan Lucke (Ste...@sn...) |
From: Eugene K. <di...@eu...> - 2001-02-14 02:43:05
|
Hello Dan, Tuesday, February 13, 2001, 8:57:44 AM, you wrote: DD> A DV AVI codec that uses libdv and works with the gstreamer framework is on DD> my list of things to do, but not a high priority. I recently received a patch for avifile that enabled decoding of DV AVI files. It used Windows DirectShow filter ( dll name qdv.dll ). I'll put it in one of future releases. -- Best regards, Eugene mailto:di...@eu... |
From: Dan D. <dde...@co...> - 2001-02-13 14:57:15
|
Yes, DV grab creates DV AVI files, which means you need a DV codec in order to view them. The avifile page which lists the included codecs is at http://divx.euro.ru/formats.htm. A DV codec does not come with AVIfile. If you have a Windows DV codec, you can put it into /usr/lib/win32 and try it. I have not tried that yet. Canopus has a free decoder only DV Windows AVI codec on their web site at http://www.canopuscorp.com/pages/download.php3, but the FOURCC code for it is cdvc whereas dvgrab sets FOURCC to dvsd, which is a Pinnacle version according to http://www.webartz.com/fourcc/. The Microsoft page to which webartz refers indicates, however, that dvsd is a generic type governed by the Specification of Consumer-Use Digital VCRs (Blue Book). I know I have one on a Windows box where I was able to view an AVI. When I get home, I'll determine which codec it is and see if it is redistributable. If you have access to a Windows box, install the Windows video editing software that came with your 1394 host adaptor. It will likely install a DV codec. You can see a list of video codecs installed in windows through the registry. Good luck ;-) An easier way to look this up on Windows, is to use the free program VirtualDub. From the menu, select Video/Compression....You can also use Graph Edit, a utility that is part of the DirectX SDK, by choosing Graph/Insert Filter... Graph Edit can also be obtained through a number of the DivX portals out there. A DV AVI codec that uses libdv and works with the gstreamer framework is on my list of things to do, but not a high priority. ----- Original Message ----- From: "Michael Spiceland (aka Mike Spice)" <mi...@mi...> To: <lin...@li...>; <av...@pr...> Sent: Tuesday, February 13, 2001 12:25 AM Subject: .avi files created by dvgrab (DV avi's) > This is a followup to my email last week about the .avi files created by > dvgrab (I think we have been calling them DV type AVI's). In my last email I > included many links from the dvgrab homepage. > > I uploaded a few sample type 1 and type 2 avi's created by dvgrab. These are > NOT playable with avifile. The audio will play on the type 2 avi's. > > http://knoxvilleshops.com/dv/ > > Please let me know if I can help in any way (providing more clips, testing, > etc). > > -- > Thank you in advance, > Mike Spice (Michael Spiceland) - http://www.mikespice.com > KLUG President (Knoxville Linux User Group) - http://web.utk.edu/~klug > IgWig Solutions (owner) - http://www.mikespice.com/igwig/ > > _______________________________________________ > mailing list Lin...@li... > http://lists.sourceforge.net/lists/listinfo/linux1394-user > |
From: Michael S. (a. M. S. <mi...@mi...> - 2001-02-13 05:33:38
|
This is a followup to my email last week about the .avi files created by dvgrab (I think we have been calling them DV type AVI's). In my last email I included many links from the dvgrab homepage. I uploaded a few sample type 1 and type 2 avi's created by dvgrab. These are NOT playable with avifile. The audio will play on the type 2 avi's. http://knoxvilleshops.com/dv/ Please let me know if I can help in any way (providing more clips, testing, etc). -- Thank you in advance, Mike Spice (Michael Spiceland) - http://www.mikespice.com KLUG President (Knoxville Linux User Group) - http://web.utk.edu/~klug IgWig Solutions (owner) - http://www.mikespice.com/igwig/ |
From: Damien D. <ddo...@te...> - 2001-02-12 15:51:00
|
Hi, Does anybody knows where I could find a little app to decode DV files into YUV files? Libdv looks great, but a little complex... Thanks, Damien -- Damien Douxchamps URL : http://www.tele.ucl.ac.be/MEMBERS/Douxchamps_Damien_e.html |
From: Rodney S. <ro...@bi...> - 2001-02-11 11:46:07
|
Hi! Thought some of you might be interested in the following article: http://www.kuro5hin.org/?op=displaystory;sid=2001/1/31/18749/1930 Regards, -- Rodney |
From: Dan D. <dde...@co...> - 2001-02-09 16:45:59
|
From: "Ken Offer" > Hi Andreas (et. al), > > I'm looking for an explanation of the parameters for this routine: > > int raw1394_start_iso_write(struct raw1394_handle *handle, > unsigned int channel, > unsigned int tag, > unsigned int sy, > unsigned int speed, > size_t length, > quadlet_t *data, > unsigned long rawtag); > > Please correct me if I'm wrong in these assertions: > > The "handle" parameter is returned from > raw1394_get_handle(). Yes > The "channel" parameter is the isochronous channel to use > during transmission. It ranges from 0 to 63? Yes > The tag parameter should be either: > > a. some register offset from CSR_REGISTER_BASE > (perhaps CSR_REGISTER_BASE+CSR_FCP_COMMAND?) No > b. some value which distinguishes the packet type from > other packet types? > > c. something else? Specific to the protocol. It can indicate the inclusion of CIP headers in the iso data packet. > The "sy" parameter is a complete mystery to me. Is it the > "Z" parameter that the 1394 Open Host Controller Interface > Specification references? No, the Z field is part of the DMA command descriptor. The Sy is specific to the protocol too. For example, DV does not use it; it always 0. Uncompressed video via Digital Camera sets this to 1 to indicate the start of a new frame. > The "speed" parameter should be 1 for 100Mbits/sec, 2 for > 200Mbits/sec and 3 for 400Mbits/sec (this I gleaned from the > 1394 Open Host Controller Interface Specification referenced > from the links page). Yes > The "length" parameter is the size of whatever data points to. Yes > The "data" parameter is: > > a. A pointer to a buffer of raw data to send Yes > b. A pointer to some "DMA data-structure/program" that is described > in the 1394 Open Host Controller Interface Specification. No > c. Something altogether different. > > d. An android serving on a starship in the 24th century. :) > > The "rawtag" parameter is another mystery. Is it the same value as > tag? Hmm... I don't recall that parameter. It is a full quadlet, so perhaps it allows one to completely format the iso header and access some reserved areas? > Any pointers you could offer would be greatly appreciated. > > -- > ______________________________________________________________ > Kenneth Ray Offer, II > Sr. Systems Analyst > Applied Research Laboratories/SDD > University of Texas at Austin > Office (512) 835-3859 FAX (512) 835-3259 > > Any opinions expressed above are mine and not necessarily > those of my employer. > > _______________________________________________ > mailing list Lin...@li... > http://lists.sourceforge.net/lists/listinfo/linux1394-user > |
From: Ken O. <ko...@ar...> - 2001-02-09 15:13:01
|
Hi Andreas (et. al), I'm looking for an explanation of the parameters for this routine: int raw1394_start_iso_write(struct raw1394_handle *handle, unsigned int channel, unsigned int tag, unsigned int sy, unsigned int speed, size_t length, quadlet_t *data, unsigned long rawtag); Please correct me if I'm wrong in these assertions: The "handle" parameter is returned from raw1394_get_handle(). The "channel" parameter is the isochronous channel to use during transmission. It ranges from 0 to 63? The tag parameter should be either: a. some register offset from CSR_REGISTER_BASE (perhaps CSR_REGISTER_BASE+CSR_FCP_COMMAND?) b. some value which distinguishes the packet type from other packet types? c. something else? The "sy" parameter is a complete mystery to me. Is it the "Z" parameter that the 1394 Open Host Controller Interface Specification references? The "speed" parameter should be 1 for 100Mbits/sec, 2 for 200Mbits/sec and 3 for 400Mbits/sec (this I gleaned from the 1394 Open Host Controller Interface Specification referenced from the links page). The "length" parameter is the size of whatever data points to. The "data" parameter is: a. A pointer to a buffer of raw data to send b. A pointer to some "DMA data-structure/program" that is described in the 1394 Open Host Controller Interface Specification. c. Something altogether different. d. An android serving on a starship in the 24th century. :) The "rawtag" parameter is another mystery. Is it the same value as tag? Any pointers you could offer would be greatly appreciated. -- ______________________________________________________________ Kenneth Ray Offer, II Sr. Systems Analyst Applied Research Laboratories/SDD University of Texas at Austin Office (512) 835-3859 FAX (512) 835-3259 Any opinions expressed above are mine and not necessarily those of my employer. |
From: Dan D. <dde...@co...> - 2001-02-08 22:14:05
|
From: "Marcel Janssen" > Hi, > > Regarding the DV-AVI formats produced by dvgrab (dv1 dv2), is there a way to > convert it to a different format (divx,mpeg) ? Not yet. There are some Linux/Open Source projects that have plugin architectures for audio and video codecs (e.g. gstreamer). However, I am not aware of any that have a plugin for a DV-encoded AVI. Obviously, something like this would be nice to integrate into, um... say... Kino. > Is there a way to control the image resolution that is read in from a sony > video camera ? I really don't need 720*576. No, but a video scaling filter for gstreamer would help. Check out http://www.gstreamer.net/. I am surprised it does not already include a DV plugin since one of the developers is also a developer on the libdv project (omegahacker). Note, also that gstreamer includes a LADSPA filter to do all sorts of audio processing as well, including freeverb. > thanks, > Marcel Janssen > > _______________________________________________ > mailing list Lin...@li... > http://lists.sourceforge.net/lists/listinfo/linux1394-user > |
From: Aleksandr M. <n6...@mi...> - 2001-02-08 22:07:53
|
When I was first surfing around the linux1394 pages, I thought I saw a link to a piece of software that simulated a DV deck. Now, I can't find it. Was I hallucinating, or could someone toss me a link? Thanks, Zandr -- --------------------------------------------------------------------- Aleksandr Milewski N6MOD n6...@mi... http://www.milewski.org/ |
From: Ken O. <ko...@ar...> - 2001-02-08 18:43:00
|
Hi all, I'm looking for a source code example using libraw1394 to transmit data "isochronously". I found an example for the read side of the equation in dvgrab. At the very least I am looking for a more thorough explanation of the parameters for "raw1394_iso_write" and "raw1394_start_iso_write". -- ______________________________________________________________ Kenneth Ray Offer, II Sr. Systems Analyst Applied Research Laboratories/SDD University of Texas at Austin Office (512) 835-3859 FAX (512) 835-3259 Any opinions expressed above are mine and not necessarily those of my employer. |
From: Marcel J. <mph...@ho...> - 2001-02-08 17:47:56
|
Hi, Regarding the DV-AVI formats produced by dvgrab (dv1 dv2), is there a way to convert it to a different format (divx,mpeg) ? Is there a way to control the image resolution that is read in from a sony video camera ? I really don't need 720*576. thanks, Marcel Janssen |
From: Aleksandr M. <n6...@mi...> - 2001-02-06 20:58:06
|
At 12:49 PM -0500 on 2/6/01, Dan Dennedy commanded the electrons to create a missive titled "Re: MPEG-2 Capture?": |From: "Aleksandr Milewski" <n6...@mi...> |> This is the right thing to do. I'll look at the source, but I have a |> suspicion that commenting out large pieces of dvgrap might be the way |> to go. | |There is a test mode of dvgrab and corresponding function that you should |look at for the case that is closest to yours. It will be a couple of weeks before I can get that machine built (too many commitments at work) but when I get that running I'll take a good look at dvgrab and both test and raw modes. I read the docs last night, and I rather got the impression that test mode would include the 1394 headers in the file. I guess I don't understand the difference between test mode and raw mode. |The IEC-61883-4 spec describes MPEG2-TS over 1394. Can you confirm that your |device conforms with this? The spec description says it is related to DVB, |in which case one should look strongly at the DVB API and source code at |http://www.linuxtv.org/. I'm fairly sure that they aren't that sophisticated, but at this point we're speculating. Probably the best thing for me to do is build up a machine with 2.4 and linux1394, and make a test mode file available to those who know more than I do. |What devices support this that might convince me to buy one--a digital TV? At the moment, there's nothing on the market. The first generation of D-VHS decks all had one form or another of this, although things were somewhat proprietary. Hughes and RCA DirecTV receivers would play with each other, and Panasonic did their own thing. I think the tape format was the same (14.1Mbps MPEG2-TS) but the 1394 implemenations were (deliberately?) incompatible. The Hughes/RCA devices were SD only, but the Panasonic PV-HD1000 DVHS VCR can record all 18 ATSC formats. The way these thing worked was that the bitstream would get sent down the 1394 to the VCR during record, and back up the 1394 to the MPEG2 decoder in the set top during playback. You could dub from tape to tape by connecting two machines over 1394. All of these got yanked off the market over the past six months, presumably under pressure from the MPAA. There's a new generation of D-VHS machines that were announced at CES this year, but with some form of copy protection to keep Hollywood happy. I want to be able to capture from a D-VHS deck to a file so I can edit the programs, and then burn to DVD-R for archiving. -Zandr -- --------------------------------------------------------------------- Aleksandr Milewski N6MOD n6...@mi... http://www.milewski.org/ |
From: Marcel J. <mph...@ho...> - 2001-02-06 20:25:42
|
HI, I've got things running with the 2.4.0 kernel. I downloaded the patch at : http://www.schirmacher.de/arne/kino/index_e.html Probably it's different from the current CVS, I haven't checked yet. -- Marcel Janssen |
From: Dan D. <dde...@co...> - 2001-02-06 20:23:05
|
I am using a CVS snapshot from Jan 22 with kernel 2.4.0. There has only been changes to the Makefile and a change in one line in ieee1394_core.c since then. Everything is working great for me. (I know you wanted to hear that ;-) 2.4.1 does not include the latest stable code because evidently the submissions by our project master have been overlooked by the kernel maintainers. ----- Original Message ----- From: "Marcel Janssen" <mph...@ho...> To: <lin...@li...> Sent: Tuesday, February 06, 2001 1:49 PM Subject: Re: kernel hangs when powering up DV-camera > Hi, > > I'm still stuck with the same problem. After being busy for about 5 hours, I > still get my box to lock completely and get real sick of fsck :-( > I would like to know wether anyone tried the latest code with kernel 2.4.0 > with any succes. And, how about the latest 2.4.1 kernel (?), is the code in > there ok ? > > -- > Marcel Janssen > > > > _______________________________________________ > mailing list Lin...@li... > http://lists.sourceforge.net/lists/listinfo/linux1394-user > |
From: Dan D. <dde...@co...> - 2001-02-06 20:21:38
|
I am using a CVS snapshot from Jan 22 with kernel 2.4.0. There has only been changes to the Makefile and a change in one line in ieee1394_core.c since then. Everything is working great for me. (I know you wanted to hear that ;-) 2.4.1 does not include the latest stable code because evidently the submissions by our project master have been overlooked by the kernel maintainers. ----- Original Message ----- From: "Marcel Janssen" <mph...@ho...> To: <lin...@li...> Sent: Tuesday, February 06, 2001 1:49 PM Subject: Re: kernel hangs when powering up DV-camera > Hi, > > I'm still stuck with the same problem. After being busy for about 5 hours, I > still get my box to lock completely and get real sick of fsck :-( > I would like to know wether anyone tried the latest code with kernel 2.4.0 > with any succes. And, how about the latest 2.4.1 kernel (?), is the code in > there ok ? > > -- > Marcel Janssen > > > > _______________________________________________ > mailing list Lin...@li... > http://lists.sourceforge.net/lists/listinfo/linux1394-user > |
From: Marcel J. <mph...@ho...> - 2001-02-06 18:57:37
|
Hi, I'm still stuck with the same problem. After being busy for about 5 hours, I still get my box to lock completely and get real sick of fsck :-( I would like to know wether anyone tried the latest code with kernel 2.4.0 with any succes. And, how about the latest 2.4.1 kernel (?), is the code in there ok ? -- Marcel Janssen |
From: Dan D. <dde...@co...> - 2001-02-06 17:49:15
|
From: "Aleksandr Milewski" <n6...@mi...> > At 1:03 AM -0500 on 2/6/01, Dan Dennedy commanded the electrons to > create a missive titled "Re: MPEG-2 Capture?": > |Aleksandr Milewski wrote: > |> > |> Has anyone done any work on MPEG-2 capture from 1394? > | > |Not that we are aware of. Most us are capturing DV and uncompressed > |video. > > Uncompressed? From what source? Mostly closed circuit CCD-type Sony cameras for machine vision and industrial applications. However, several people have the Orange Micro iBot or Pyro WebCam cheap desktop cameras. > |> I admit that I haven't built linux1394 yet, so if this is as simple as > |> > |> cat /dev/video1394 >> file.mpeg > | > |Not that simple until someone brings video1394 up to video4linux > |compliancy. However, you can certainly call a few ioctls and dump the > |iso packets to disk. If it is that braindead, then maybe it will be as > |simple as that, but I would not be so optimistic. > > I'm reasonably sure it is that braindead. According to one source, > each iso packet contains either one or two 188-byte Mpeg2 TS packets, > "with header and timestamp." Sounds braindead to me. Well, then I strongly recommend the libraw API's functions as video1394 is rather tricky when dealing with variable-size packets because packets will split across the boundaries of the buffers. > In any case... > > At 1:18 AM -0500 2/6/01, Dan Dennedy wrote: > |Also, you could just use libraw's iso read functions. It is more > |universal, popular and simple. You can view the source of dvgrab to see > |how to use it. Access dvgrab at http://www.schirmacher.de/arne/dvgrab/. > > This is the right thing to do. I'll look at the source, but I have a > suspicion that commenting out large pieces of dvgrap might be the way > to go. There is a test mode of dvgrab and corresponding function that you should look at for the case that is closest to yours. > Of course, the reason I asked this on the user list is that I'm far > more user than developer, so if someone would like to lead the way... The IEC-61883-4 spec describes MPEG2-TS over 1394. Can you confirm that your device conforms with this? The spec description says it is related to DVB, in which case one should look strongly at the DVB API and source code at http://www.linuxtv.org/. What devices support this that might convince me to buy one--a digital TV? > -Zandr > -- > --------------------------------------------------------------------- > Aleksandr Milewski N6MOD > n6...@mi... http://www.milewski.org/ > > _______________________________________________ > mailing list Lin...@li... > http://lists.sourceforge.net/lists/listinfo/linux1394-user > |
From: Aleksandr M. <n6...@mi...> - 2001-02-06 08:25:22
|
At 1:03 AM -0500 on 2/6/01, Dan Dennedy commanded the electrons to create a missive titled "Re: MPEG-2 Capture?": |Aleksandr Milewski wrote: |> |> Has anyone done any work on MPEG-2 capture from 1394? | |Not that we are aware of. Most us are capturing DV and uncompressed |video. Uncompressed? From what source? |> I admit that I haven't built linux1394 yet, so if this is as simple as |> |> cat /dev/video1394 >> file.mpeg | |Not that simple until someone brings video1394 up to video4linux |compliancy. However, you can certainly call a few ioctls and dump the |iso packets to disk. If it is that braindead, then maybe it will be as |simple as that, but I would not be so optimistic. I'm reasonably sure it is that braindead. According to one source, each iso packet contains either one or two 188-byte Mpeg2 TS packets, "with header and timestamp." Sounds braindead to me. In any case... At 1:18 AM -0500 2/6/01, Dan Dennedy wrote: |Also, you could just use libraw's iso read functions. It is more |universal, popular and simple. You can view the source of dvgrab to see |how to use it. Access dvgrab at http://www.schirmacher.de/arne/dvgrab/. This is the right thing to do. I'll look at the source, but I have a suspicion that commenting out large pieces of dvgrap might be the way to go. Of course, the reason I asked this on the user list is that I'm far more user than developer, so if someone would like to lead the way... -Zandr -- --------------------------------------------------------------------- Aleksandr Milewski N6MOD n6...@mi... http://www.milewski.org/ |
From: Herbert W. <Herbert@Wengatz.DE> - 2001-02-06 08:19:17
|
Hi there! I'm rather new to all that stuff, even into video, so please don't get angry when I start asking obvious stuff... I bought a couple of months ago a Sony TRV 110 because I went on a trip to Egypt. I took several cassettes but all in 16:9 format. - Will I be able to fetch them from the camcorder? ( I also have the Pinnacle Studio DV Card) - Can I cut them under Linux? Can anybody help me with that? Best regards, Herbert Wengatz |
From: Tom B. <tb...@ba...> - 2001-02-06 07:15:48
|
On Tue, 6 Feb 2001, Marcel Janssen wrote: > On Tuesday 06 February 2001 07:26, Dan Dennedy wrote: > > With the camera off, obviously, pager /proc/ohci1394 and what is the > > node count? It should be 1 for the host adapter itself. If it is zero, > > then your card is not operating properly on the PCI bus. > > > > Have you disabled PnP OS in the BIOS? Turn that off if you have not. You > > still have PnP, but it will be controlled by BIOS and not the OS. > > I had PnP OS disabled in the BIOS. I've attached the output of > /proc/ohci1394, note count is 1. > > thanks, > Marcel Janssen > > > [root@korgull libraw1394-0.8.2]# cat /proc/ohci1394 > IEEE-1394 OHCI Driver status report: > bus number: 0x3ff Node ID: 0x0 > > ### Host data ### > node_count: 1 node_id : 0000FFC0 > irm_id : 0000FFC0 busmgr_id : 0000FFC0 > initialized > root iso_res_mgr bus_mgr can someone explain what the above flags are? my similar system (2.2.16 kernel though) has similar symptoms (locks up), except that I recover control when the the camera is turned off or disconnected... and I don't have the bus_mgr flags, and the busmgr_id is ffff ### Host data ### node_count: 1 node_id : 0000FFC0 irm_id : 0000FFFF busmgr_id : 0000FFFF initialized root is that just something new? my data is from late december... I was thinking that it was just that the Dlink DFW-500 card was bad, but someone reported success with it just recently... -Tom |
From: Marcel J. <mph...@ho...> - 2001-02-06 07:06:23
|
On Tuesday 06 February 2001 07:26, Dan Dennedy wrote: > With the camera off, obviously, pager /proc/ohci1394 and what is the > node count? It should be 1 for the host adapter itself. If it is zero, > then your card is not operating properly on the PCI bus. > > Have you disabled PnP OS in the BIOS? Turn that off if you have not. You > still have PnP, but it will be controlled by BIOS and not the OS. I had PnP OS disabled in the BIOS. I've attached the output of /proc/ohci1394, note count is 1. thanks, Marcel Janssen [root@korgull libraw1394-0.8.2]# cat /proc/ohci1394 IEEE-1394 OHCI Driver status report: bus number: 0x3ff Node ID: 0x0 ### Host data ### node_count: 1 node_id : 0000FFC0 irm_id : 0000FFC0 busmgr_id : 0000FFC0 initialized root iso_res_mgr bus_mgr ---Iso Receive DMA--- Current buf: 0 offset: 0 ---Async Receive DMA--- Ar req current buf: 0 offset: 16 AR resp current buf: 0 offset: 0 ---Async Transmit DMA--- AT req prg: 0 sent: 0 free: 32 branchAddrPtr: 00000000 AT req queue: first: 00000000 last: 00000000 AR resp prg: 0 sent: 0 free: 32 branchAddrPtr: 00000000 AT resp queue: first: 00000000 last: 00000000 ### HC Register dump ### Version : 01010000 GUID_ROM : 00000000 ATRetries : 00000822 CSRData : 00000000 CSRCompData : 00000000 CSRControl : 80000000 ConfigROMhdr: 04040bd7 BusID : 31333934 BusOptions : f07da002 GUIDHi : 00506256 GUIDLo : 00008e43 ConfigROMmap: 07311000 PtdWrAddrLo : 00000000 PtdWrAddrHi : 00000000 VendorID : 00000000 HCControl : 000e0000 SelfIDBuffer: 0a084000 SelfIDCount : 0001000c IRMuChMaskHi: 00000000 IRMuChMaskLo: 00000000 IntEvent : 00100000 IntMask : 840300ff IsoXmIntEvnt: 00000000 IsoXmIntMask: 00000000 IsoRcvIntEvt: 00000000 IsoRcvIntMsk: 00000001 FairnessCtrl: 00000000 LinkControl : 00300200 NodeID : c000ffc0 PhyControl : 0000017f IsoCyclTimer: 2302b8b6 AsRqFilterHi: ffffffff AsRqFilterLo: ffffffff PhyReqFiltHi: ffffffff PhyReqFiltLo: ffffffff PhyUpperBnd : 00000000 AsRqTrCxtCtl: 00000000 AsRqTrCmdPtr: 00000000 AsRsTrCtxCtl: 00000000 AsRsTrCmdPtr: 00000000 AsRqRvCtxCtl: 00008409 AsRqRvCmdPtr: 0739b001 AsRsRvCtxCtl: 00008400 AsRsRvCmdPtr: 081d3001 IntEvent : 00100000 IsoRCtxCtl00: d0008400 IsoRCmdPtr00: 014c2001 IsoRCxtMch00: f0000000 IsoRCtxCtl01: 00000000 IsoRCmdPtr01: 00000000 IsoRCxtMch01: 00000000 IsoRCtxCtl02: 00000000 IsoRCmdPtr02: 00000000 IsoRCxtMch02: 00000000 IsoRCtxCtl03: 00000000 IsoRCmdPtr03: 00000000 IsoRCxtMch03: 00000000 IsoTCtxCtl00: 00000000 IsoTCmdPtr00: 00000000 IsoTCtxCtl01: 00000000 IsoTCmdPtr01: 00000000 IsoTCtxCtl02: 00000000 IsoTCmdPtr02: 00000000 IsoTCtxCtl03: 00000000 IsoTCmdPtr03: 00000000 IsoTCtxCtl04: 00000000 IsoTCmdPtr04: 00000000 IsoTCtxCtl05: 00000000 IsoTCmdPtr05: 00000000 IsoTCtxCtl06: 00000000 IsoTCmdPtr06: 00000000 IsoTCtxCtl07: 00000000 IsoTCmdPtr07: 00000000 [root@korgull libraw1394-0.8.2]# |
From: Dan D. <dde...@co...> - 2001-02-06 06:16:17
|
With the camera off, obviously, pager /proc/ohci1394 and what is the node count? It should be 1 for the host adapter itself. If it is zero, then your card is not operating properly on the PCI bus. Have you disabled PnP OS in the BIOS? Turn that off if you have not. You still have PnP, but it will be controlled by BIOS and not the OS. Marcel Janssen wrote: > > Hi, > > This is my first try with ieee1394 and I seem to get my card going. > My card is a Texas Instruments OHCI campliant one and I use kernel 2.4.0 with > the CVS fix (05-02-2001). > > When I leave the camera switched off, the modules load fine. When I power up > the camera, my whole box hangs (no mouse/keyboard/network etc). No matter if > I first load the modules and power up the camera afterwards or the other way > round. > > I've got no idea where to start looking for a solution. Since my box locks > immediately after switching on the camera, I have no report to my log files. > > I included the kernel log of my modules (when camera switched off) at the > bottom of this mail. > > My camera is a sony DCR-PC5E. > > Can the use of devfs be a problem ? > > thanks, > Marcel Janssen > > Feb 5 19:00:44 korgull kernel: ieee1394: registered ohci1394 driver, > initializing now > Feb 5 19:00:44 korgull kernel: ohci1394: looking for Ohci1394 cards > Feb 5 19:00:44 korgull kernel: PCI: Found IRQ 9 for device 00:0a.0 > Feb 5 19:00:44 korgull kernel: ohci1394_0: remapped memory spaces reg > 0xcd8d0000 > Feb 5 19:00:44 korgull kernel: ohci1394_0: allocated interrupt 9 > Feb 5 19:00:44 korgull kernel: ohci1394_0: soft reset finished > Feb 5 19:00:44 korgull kernel: ohci1394_0: max packet size = 2048 bytes > Feb 5 19:00:44 korgull kernel: ohci1394_0: 4 iso receive contexts available > Feb 5 19:00:44 korgull kernel: ohci1394_0: 8 iso transmit contexts available > Feb 5 19:00:44 korgull kernel: ohci1394_0: Receive DMA ctx=0 initialized > Feb 5 19:00:44 korgull kernel: ohci1394_0: Receive DMA ctx=1 initialized > Feb 5 19:00:44 korgull kernel: ohci1394_0: AT dma ctx=0 initialized > Feb 5 19:00:44 korgull kernel: ohci1394_0: AT dma ctx=1 initialized > Feb 5 19:00:44 korgull kernel: ohci1394_0: Receive DMA ctx=2 initialized > Feb 5 19:00:44 korgull kernel: ohci1394_0: resetting bus on request > Feb 5 19:00:44 korgull kernel: ieee1394: detected 1 ohci1394 adapter > Feb 5 19:00:44 korgull kernel: ohci1394_0: SelfID process finished (phyid 0, > root) > Feb 5 19:00:44 korgull kernel: ohci1394_0: selfid packet 0x807f8c56 rcvd > Feb 5 19:00:44 korgull kernel: ohci1394_0: This node self-id is 0x807f8c56 > Feb 5 19:00:44 korgull kernel: ohci1394_0: calling self-id complete > Feb 5 19:00:44 korgull kernel: ohci1394_0: Got phy packet ctx=0 ... discarded > Feb 5 19:00:56 korgull kernel: devfs: devfs_register(): device already > registered: "raw1394" > Feb 5 19:00:56 korgull kernel: raw1394: /dev/raw1394 device initialized > Feb 5 19:01:00 korgull CROND[6021]: (root) CMD (run-parts /etc/cron.hourly) > Feb 5 19:01:01 korgull kernel: ohci1394_0: Bus reset > Feb 5 19:01:01 korgull kernel: ohci1394_0: SelfID process finished (phyid 0, > not root) > Feb 5 19:01:01 korgull kernel: ohci1394_0: selfid packet 0x807f8c94 rcvd > Feb 5 19:01:01 korgull kernel: ohci1394_0: This node self-id is 0x807f8c94 > Feb 5 19:01:01 korgull kernel: ohci1394_0: selfid packet 0x813f08c2 rcvd > Feb 5 19:01:01 korgull kernel: ohci1394_0: calling self-id complete > Feb 5 19:01:01 korgull kernel: ohci1394_0: Bus reset > Feb 5 19:01:01 korgull kernel: ohci1394_0: SelfID process finished (phyid 0, > not root) > Feb 5 19:01:01 korgull kernel: ohci1394_0: selfid packet 0x807f8c94 rcvd > Feb 5 19:01:01 korgull kernel: ohci1394_0: This node self-id is 0x807f8c94 > Feb 5 19:01:01 korgull kernel: ohci1394_0: selfid packet 0x813f08c2 rcvd > Feb 5 19:01:01 korgull kernel: ohci1394_0: calling self-id complete > Feb 5 19:01:01 korgull kernel: ohci1394_0: Got phy packet ctx=0 ... discarded > > _______________________________________________ > mailing list Lin...@li... > http://lists.sourceforge.net/lists/listinfo/linux1394-user |
From: Dan D. <dde...@co...> - 2001-02-06 06:08:06
|
Dan Dennedy wrote: > > Aleksandr Milewski wrote: > > > I admit that I haven't built linux1394 yet, so if this is as simple as > > > > cat /dev/video1394 >> file.mpeg > > Not that simple until someone brings video1394 up to video4linux > compliancy. However, you can certainly call a few ioctls and dump the > iso packets to disk. If it is that braindead, then maybe it will be as > simple as that, but I would not be so optimistic. Also, you could just use libraw's iso read functions. It is more universal, popular and simple. You can view the source of dvgrab to see how to use it. Access dvgrab at http://www.schirmacher.de/arne/dvgrab/. +-DRD-+ |