libdv-announce

[libdv-announce] 4 mono chanel audio from rawdv

[Georg v. K. <g.v...@un...>]

Hey my name is george,

 

I am a user of libdv in several programs and I have found that is
impossible to extract the 4 channel audio out of a rawdv file.

The only way is (and I do a lot of testing with transcode vlc mplayer
memcoder etc...) to take ffmpeg and then sox .

Ffmpeg extracted 2 stereo waves in two runs, sox extracted 4 mono waves
in 4 runs....

 

I think the people that work at the software shut be now that there is
something not ok.

 

We are TV-Professionals and working often with 4 channel audio in dv
(encoding from embedded SDI with canopus avc 1000) and in my mention is
that the Problem of 4 channel audio in dv,

Isn't a consumer problem and so nobody now it.

 

If  I am only to stupid to find the right commandline or are the libs
not ok I don't know....

 

If you want a test file

 

Host: storyhotel.de

User: 144907-georg

Pwd:  LQmKd1pzJ7

Port:      21 

 

 

Greetings

george 

[libdv-announce] DV50!

[Satish R. <Sat...@ce...>]

Hello ,
 I downloaded libdv from sourceforge and seeing it's working.
But i could use it to play only DV25 dv video . It looks as it does not
support DV50.
Can i get any light over this if i want to have a same functionality for a
DV50 video.
Do i need to write a complete codec for that or can i use libdv in a
customized way.
suggestions over this are eagerly awaited.
Thanks
 Satish.

[libdv-announce] libdv 0.98 released

[Charles 'B. K. <kr...@ac...>]

New release is out.  Check the ChangeLog for details.

-- Buck

[libdv-announce] Doubt on extracting DV frame and converting it.

[Prabhu K. <pra...@wi...>]

hi,
	we have our own 1394 stack which can receive iso data. now i get
iso data (DV data). i want to convert the iso data into a avi file. how 
should i form the full DV frame. should i just put the data i'm receiving
into a file and give it to dvgrap and convert it or should i remove first 3
quadlet ( as dvgrab says the data starts at the 4th quadlet and form a
frame..) ... 

Is there any means by which i can identify the dv packet is as
proper dv packet.. 

Thanks,
prabu

[libdv-announce] Re: [Kino-dev] Compile error in video1394.c (was Re: Announcing Kino 0.42)

[Dan D. <dde...@co...>]

The problem is the missing replacement video1394.h file. It is attached,
and it will be included with 0.43, which will be coming sooner rather than
later now :-).

On Fri, 01 Jun 2001 17:53:08 Alastair Mayer wrote:
> Dan Dennedy wrote:
> 
> > Also, this version requires an updated video1394 driver that is
> supplied
> > with this distribution. You must replace the existing driver in your
> > Linux kernel sources, recompile the modules, and reload the video1394
> > module.
> 
> I get a compile error in the video1394.c file (included with the
> kino 0.42 tarball).
> 
>    video1394.c: In function `video1394_ioctl':
>    video1394.c:931: structure has no member named `syt_offset'
> 
> Which given that the structure is a totally different type is
> unsurprising.
> Probably a typo, since the struct variable is 'v' rather than the 'd'
> I see used elsewhere, but I couldn't figure out any obvious fix.
> 
> (And yes, I copied the file to the right place in the linux drivers
> source.)
> 
> -- Alastair
> 
> _______________________________________________
> Kino-dev mailing list
> Kin...@li...
> http://lists.sourceforge.net/lists/listinfo/kino-dev
> 

[libdv-announce] Compile error in video1394.c (was Re: Announcing Kino 0.42)

[Alastair M. <am...@pe...>]

Dan Dennedy wrote:

> Also, this version requires an updated video1394 driver that is supplied
> with this distribution. You must replace the existing driver in your
> Linux kernel sources, recompile the modules, and reload the video1394
> module.

I get a compile error in the video1394.c file (included with the
kino 0.42 tarball).

   video1394.c: In function `video1394_ioctl':
   video1394.c:931: structure has no member named `syt_offset'

Which given that the structure is a totally different type is
unsurprising.
Probably a typo, since the struct variable is 'v' rather than the 'd'
I see used elsewhere, but I couldn't figure out any obvious fix.

(And yes, I copied the file to the right place in the linux drivers
source.)

-- Alastair

[libdv-announce] Announcing Kino 0.42 for GNU/Linux IEEE 1394 and libdv

[Dan D. <dde...@co...>]

V. 0.42
Improved DV export for NTSC users. Thanks to Yamazaki Makoto for pointing
out an error in the 50/60 flag in the 1394 isochronous CIP headers.

V. 0.41
****************************************************************************
IMPORTANT: 
From this version on, libavc1394 and librom1394 are required.
You can get them from http://sourceforge.net/projects/libavc1394/.
Also, this version requires an updated video1394 driver that is supplied
with this distribution. You must replace the existing driver in your
Linux kernel sources, recompile the modules, and reload the video1394
module.
****************************************************************************

Dan Dennedy has contributed this version as Arne is quite busy lately.
This version's goals include componentization, user interface improvements,
and most importantly empowering users to tune DV export. Hopefully, we will
hear more success stories about DV export for NTSC users.

I, Dan Dennedy, am working on a number of components for linux1394.
The first of these is libavc1394 and librom1394. These
replace some code that was in Kino because the code was originally borrowed
from gscanbus. Also, the dvcont utility borrowed the AV/C and raw1394util
code from gscanbus. Therefore, it makes sense to turn these functions into
a shared object library. This version of Kino uses these components.

Kino 0.41 includes several user interface improvements. Most noticeable, 
audio playback is implemented now but only through OSS. It can be disabled 
in the display options tab of the preferences dialog. Please do not ask
for other audio playback methods (e.g., esd, ALSA) unless you want to
contribute them. We are looking at porting to the gstreamer framework,
which is very capable of accomodating many needs including different
audio playback methods. Next, key repeat is disabled to prevent the 
event queue from filling up on slow machines thereby forcing you to wait
for each frame update to occur. Only certain keyboard navigation commands
repeat until the key is released: next and previous frame, next and
previous
second. Along with that feature, the Stop button in the main window toolbar
now works. Any keystroke also stops playback. You may find that if Kino 
crashes, key repeat is disable for the entire desktop until X is restarted.
Also, the current directory is remembered between file dialogs--no need to
keep changing to your project directory. Finally, preferences are saved to
~/.gnome/kino so you do not need to set them evey time you start Kino!

DV export continues to be a sore spot for NTSC users. Some PAL users have
experienced issues as well that were easy to cleanup once they were told
what changes to try in the source code. Well, this version makes some
minor improvements to the DV export algorithms at all levels including
the video1394 kernel driver. Furthermore, this version of Kino makes these
timing values that need to be adjusted available to the end user through
the preferences dialog. This helps greatly so you do not have to recompile
code, reload a driver module, and launch Kino with a video clip just to
test a tweak one of these values. Now, you can simply adjust and try the
export again!

My NTSC camera (Panasonic PV-DV910) works great with a fairly broad
range of values. Therefore, I estimate that these values, editable in
the IEEE 1394 Options tab of the preferences dialog represent the
limits that most any device could support:

Timing (NTSC users only): 1000-3300, the default is 2436.
SYT Offset (NTSC and PAL): 10000-23000, the default is 11000.

Yours in Freedom,
+-DRD-+

[libdv-announce] Problems building 0.8 release

[<pin...@ya...>]

I get the following errors when trying to build this
release under RedHat 6.1 on a K6-2

gcc -DHAVE_CONFIG_H -I. -I. -I.. -g -O2 -I . -I ..
-Wall -O2 -g -I/usr/lib/glib/include
-I/usr/lib/glib/include -I/usr/X11R6/include
-I/usr/include/SDL -D_REENTRANT -c encode_x86.S -o
encode_x86.o
/tmp/ccutH2Ls.s: Assembler messages:
/tmp/ccutH2Ls.s:76: Error: operands given don't match
any known 386 instruction
/tmp/ccutH2Ls.s:144: Error: operands given don't match
any known 386 instruction


Any ideas.. I have tried to build with configure
--disable-asm but I get other error messages then

Steve

=====
--
If you listen very carefully you can sometimes hear the dolphins sing

pin...@ya...

____________________________________________________________
Do You Yahoo!?
Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk
or your free @yahoo.ie address at http://mail.yahoo.ie

[libdv-announce] libdv 0.8

[Charles 'B. K. <kr...@ac...>]

I've just cut the 0.8 release.   

Heads up to developers:  I've re-organized the source tree!

There are now subdirectories for libdv, playdv, and encodedv.

This helps a lot with include file handling and autotools.

Makefile.vanilla is broken by this. 

--  Buck

[libdv-announce] libdv 0.7 released.

[Charles 'B. K. <kr...@ac...>]

Version 0.7 is out. 

There are encoder improvements from Peter.  Also some compilation
fixups for non-x86 and non-Xv builds.

-- Buck

[libdv-announce] libdv 0.6

[Charles 'B. K. <kr...@ac...>]

More changes to the encoder:  speedups, and bugfixes especially for
NTSC.

Also some compilation fixups for --disable-asm

-- Buck

[libdv-announce] 0.5 release

[Charles 'B. K. <kr...@ac...>]

Version 0.5 is available.  It contains various bug fixes.  Also
substantial encoder improvements submitted by Peter Schlaile.

-- Buck

[libdv-announce] libdv 0.4 release

[Charles 'B. K. <kr...@ac...>]

I've just finished going through the various patches submitted while I
was away last week.  They're substantial enough that I cut a new
release (0.4).

-- Buck