Thread: Re: [Linux1394] libavc
Brought to you by:
aeb,
bencollins
From: Andreas M. <mi...@fo...> - 2000-04-26 08:56:19
|
Hi, On Tue, Apr 25, 2000 at 11:23:00PM -0400, Bruce McDonald wrote: > I'm new here so go easy. I am very interested in developing a dvcam tape > scanning application that produces a batch capture list on output (at the > very least). I am approaching this from the bottom-up so I am trying to > abstract the AV/C & libraw funcations into a "libavc". I have noticed > that gscanbus & and the sdpavc (from k-3d) both have their own api's (not > in library form). I need to redo this existing overlap, so a library > might be useful. I thought this to and actually I am planning to seperate the AV/C code from gscanbus into a seperate library. However it would just be a libsimpleavc, so just go ahead and build a "real" AV/C library if you need it. I would happily adopt it for gscanbus and focus on something else. My simple AV/C implementation is quite handy for sending a command to a device and receiving the response code. However I have not spent a single thought on how to deal with input- / output-plugs and the whole issue of isochronous stream management. This would probably be the hardest part of a real AV/C implementation (and personally, I realy don't need that at the moment). > 0. Is the name, libavc, correct, or would libavc1394 (or other > variant) be more correct? Both are correct. I would prefer libavc1394 because a beginner can than easily figure out which parts belong to 1394. > 1. Would it be useful to develop a libavc which would implement the AV/C > command set on top of libraw1394 in a standard way? Certainly. > (as an aside:- I tend to prefer C/asm for systems work and OO [c++/Java] > languages for applications, so libavc would, most likely, be a C library) A C library would probably the best basis. A C++ / Java library on top of the C library, or even better a CORBA binding would be nice to have later on. :-) Btw.: Can someone please put a gateway between the mailinglists at eclipt and sourceforge, or shut down the list at eclipt completely? It is quite confusing to have two seperate lists for the same subject. bye... Andreas Micklei |
From: Bruce M. <br...@tr...> - 2000-04-27 03:06:45
|
On Wed, 26 Apr 2000, Andreas Micklei wrote: Andreas, Thanks for the response, I was certainly going to address the functionality covered first. I really want to understand more before coding but I must admit that I have pulled the avc code from gscanbus. I intend to provide at least the simpleavc levels of service. I would like to include avc functions from the C++ of k-3d. I would however like to include sufficient functionality so that complete dvcam (ultimate end, really) support is available. My moves now are: 1. autoconf support (for which I will look at libraw1394) 2. iterative development for target app attempting to abstract api. The name will be libavc1394 and will rely on libraw1394. The specification document (1996/8/13) is: (http://www.1394ta.org/Download/Technology/Specifications/1394_AVC.pdf) Is there any libraw1394 documentation out there or is that an open item? functionality in rough order of implementation 0. immediate transactions. 1.5. device query operations. 1. stop/play(speeds)/wind/record/pause. 2. deferred transaction management. 4. date and timecode operations. 5. seek operations. 6. plug, mic and analog audio stuff (dunno much here) Input? Bruce. > Hi, > > On Tue, Apr 25, 2000 at 11:23:00PM -0400, Bruce McDonald wrote: > > I'm new here so go easy. I am very interested in developing a dvcam tape > > scanning application that produces a batch capture list on output (at the > > very least). I am approaching this from the bottom-up so I am trying to > > abstract the AV/C & libraw funcations into a "libavc". I have noticed > > that gscanbus & and the sdpavc (from k-3d) both have their own api's (not > > in library form). I need to redo this existing overlap, so a library > > might be useful. > > I thought this to and actually I am planning to seperate the AV/C code from > gscanbus into a seperate library. However it would just be a libsimpleavc, so > just go ahead and build a "real" AV/C library if you need it. I would happily > adopt it for gscanbus and focus on something else. > > My simple AV/C implementation is quite handy for sending a command to a device > and receiving the response code. However I have not spent a single thought on > how to deal with input- / output-plugs and the whole issue of isochronous > stream management. This would probably be the hardest part of a real AV/C > implementation (and personally, I realy don't need that at the moment). > > > 0. Is the name, libavc, correct, or would libavc1394 (or other > > variant) be more correct? > > Both are correct. I would prefer libavc1394 because a beginner can than > easily figure out which parts belong to 1394. > > > 1. Would it be useful to develop a libavc which would implement the AV/C > > command set on top of libraw1394 in a standard way? > > Certainly. > > > (as an aside:- I tend to prefer C/asm for systems work and OO [c++/Java] > > languages for applications, so libavc would, most likely, be a C library) > > A C library would probably the best basis. A C++ / Java library on top of the > C library, or even better a CORBA binding would be nice to have later on. :-) > > Btw.: Can someone please put a gateway between the mailinglists at eclipt and > sourceforge, or shut down the list at eclipt completely? It is quite confusing > to have two seperate lists for the same subject. > > bye... > Andreas Micklei > |
From: Bruce M. <br...@tr...> - 2000-05-05 00:50:19
|
On Wed, 26 Apr 2000, Andreas Micklei wrote: all, I have the first version of libavc1394 ready. Where can I post it? Bruce. > Hi, > > On Tue, Apr 25, 2000 at 11:23:00PM -0400, Bruce McDonald wrote: > > I'm new here so go easy. I am very interested in developing a dvcam tape > > scanning application that produces a batch capture list on output (at the > > very least). I am approaching this from the bottom-up so I am trying to > > abstract the AV/C & libraw funcations into a "libavc". I have noticed > > that gscanbus & and the sdpavc (from k-3d) both have their own api's (not > > in library form). I need to redo this existing overlap, so a library > > might be useful. > > I thought this to and actually I am planning to seperate the AV/C code from > gscanbus into a seperate library. However it would just be a libsimpleavc, so > just go ahead and build a "real" AV/C library if you need it. I would happily > adopt it for gscanbus and focus on something else. > > My simple AV/C implementation is quite handy for sending a command to a device > and receiving the response code. However I have not spent a single thought on > how to deal with input- / output-plugs and the whole issue of isochronous > stream management. This would probably be the hardest part of a real AV/C > implementation (and personally, I realy don't need that at the moment). > > > 0. Is the name, libavc, correct, or would libavc1394 (or other > > variant) be more correct? > > Both are correct. I would prefer libavc1394 because a beginner can than > easily figure out which parts belong to 1394. > > > 1. Would it be useful to develop a libavc which would implement the AV/C > > command set on top of libraw1394 in a standard way? > > Certainly. > > > (as an aside:- I tend to prefer C/asm for systems work and OO [c++/Java] > > languages for applications, so libavc would, most likely, be a C library) > > A C library would probably the best basis. A C++ / Java library on top of the > C library, or even better a CORBA binding would be nice to have later on. :-) > > Btw.: Can someone please put a gateway between the mailinglists at eclipt and > sourceforge, or shut down the list at eclipt completely? It is quite confusing > to have two seperate lists for the same subject. > > bye... > Andreas Micklei > |
From: Bruce M. <br...@tr...> - 2000-05-13 03:31:02
|
All, I have completed the first release of libavc1394. Sorry about the delay but one thing led to another... you know how it goes ;) Well, anyway download it from the url below. Note that it is completely undocumented - so use the source. The functions available are listed in avc.h. (not working now) http://home.triphop.org:8080/~bruce/libavc1394-0.0.1.tar.gz (working) http://home.carolina.rr.com/triphop/libavc1394-0.0.1.tar.gz I am trying to get the timecode code working - please test (run testavc) on your equipment (don't worry it does not record!). Bruce. |
From: Sven Nguyen-N. <sv...@st...> - 2000-06-08 15:31:58
|
Is this list still active? I haven't received any mailings in over a month. Sorry about the spam... |
From: Andreas B. <and...@mu...> - 2000-06-08 21:14:52
|
On Thu, Jun 08, 2000 at 11:35:39AM -0400, Sven Nguyen-Northcott wrote: > Is this list still active? I haven't received any mailings in over a month. > Sorry about the spam... You don't seem to be subscribed at your mail address. Go to http://lists.sourceforge.net/mailman/listinfo/linux1394-devel to subscribe again. -- Andreas E. Bombe <and...@mu...> DSA key 0x04880A44 http://home.pages.de/~andreas.bombe/ http://linux1394.sourceforge.net/ |