headers
Valentina Messeri | 4 Jun 2006 14:30
Favicon

problem with HDR-HC1

Hi,

my camera new HDR-HC1 can't display in kino (on dv mode) , only VRC av/c
actually works, while it works nop with dvgrab.

I had same problems a couple of times before, but it was with other people
camera so i dindn't post to the list, but this is mine so i can feedback to
hopefully solve problems.

thx

Vale

----------------------------------------------------------------
This message was sent via Slackmail, web mail from Psand.net.
Permalink | Reply | 2 comments |
headers
Dan Dennedy | 4 Jun 2006 20:30
Favicon

Re: Kino fourcc for quicktime

On Sunday 04 June 2006 05:01, Andraz Tori wrote:
> I am glad to see you implement Quicktime .mov loading, which seems to be
> the most reliable method to get DV material from cinelerra to Kino.
>
> But what you have forgotten to add is "dvcp" fourcc code for identifying
> DV material...
>
> "dvc " is correct quicktime code for DV NTSC material, and apple
> mandates "dvcp" to be used for DV PAL material... Apple Quicktime player
> won't play PAL material which has "dvc " fourcc, that's why i've just
> fixed cinelerra to properly set the fourcc, but now the files produced
> by cinelerra cannot be loaded into Kino.
>
> So can you add "dvcp" fourcc to Kino for identifying DV inside
> quicktime?

Thank you for bringing it to my attention. I just added it for open as well as 
create when PAL. While looking into this, I noticed QuicktimeForLinux and 
libquicktime(.sf.net) have diverged with respect to DV fourcc coverage. Q4L 
defines QUICKTIME_DV25 as well as QUICKTIME_DVSD, but not lqt's quicktime.h. 
Meanwhile,  lqt defines QUICKTIME_DV_AVID and QUICKTIME_AVID_A (which 
corresponds to dvcp). Not a big deal, but just thought I'd mention it.
Permalink | Reply | 5 comments |
headers
Dan Dennedy | 4 Jun 2006 20:42
Favicon

Re: problem with HDR-HC1

On Sunday 04 June 2006 05:30, Valentina Messeri wrote:
> my camera new HDR-HC1 can't display in kino (on dv mode) , only VRC av/c
> actually works, while it works nop with dvgrab.
>
> I had same problems a couple of times before, but it was with other people
> camera so i dindn't post to the list, but this is mine so i can feedback to
> hopefully solve problems.

Lucky for you to own such a lovely new camera! This is an HDV camera, and HDV 
is actually MPEG-2 video codec and MPEG-2 Transport Stream format and not DV 
codec and stream format. That is a very big difference, and Kino is a humble 
DV-only editor. I do not plan to change that anytime in the near future due 
to coming-of-age of other more ambitious projects.

So, how in the hell did you capture HDV with dvgrab? That does not make sense. 
Most people capture HDV with test-mpeg2 that comes with libiec61883 or 
mpg1394grab. Can you explain what options you used with dvgrab and how you 
validated the capture worked OK?

As for editing HDV, I recommend to give Cinelerra a shot. I have not used it 
for that, but I have some same format footage captured from my cable box, and 
I will try it sometime--borken lib dependency stopping from trying it right 
now :-(.
Permalink | Reply | 1 comment |
headers
Valentina Messeri | 4 Jun 2006 22:57
Favicon

Re: problem with HDR-HC1

Quoting Dan Dennedy <dan <at> dennedy.org>:

> On Sunday 04 June 2006 05:30, Valentina Messeri wrote:
> > my camera new HDR-HC1 can't display in kino (on dv mode) , only VRC av/c
> > actually works, while it works nop with dvgrab.

sorry, I forgot to say i was using this camera DV mode, this way i can easily
capture from dvgrab but can't capture with kino, neither export, obviously.

(i'm running kino from kino-0.8.1 tarball on amd64 debian inestable)

thx

Vale

> >
> > I had same problems a couple of times before, but it was with other people
> > camera so i dindn't post to the list, but this is mine so i can feedback to
> > hopefully solve problems.
>
> Lucky for you to own such a lovely new camera! This is an HDV camera, and HDV
> is actually MPEG-2 video codec and MPEG-2 Transport Stream format and not DV
> codec and stream format. That is a very big difference, and Kino is a humble
> DV-only editor. I do not plan to change that anytime in the near future due
> to coming-of-age of other more ambitious projects.
>
> So, how in the hell did you capture HDV with dvgrab? That does not make
> sense.
> Most people capture HDV with test-mpeg2 that comes with libiec61883 or
> mpg1394grab. Can you explain what options you used with dvgrab and how you
(Continue reading)

Permalink | Reply | 0 comments |
headers
Valentina Messeri | 6 Jun 2006 13:37
Favicon

Re: problem with HDR-HC1

ma
>
> Things to try or answer that would help us:
>
> Is it capture or capture preview that is broken?

when i start capture kino freezes, and that's what appears in the shell behind:

>> Starting Capture
>> AV/C Activado
>>> Using raw1394 capture
>>> AVC enabled
>> Constructing File Capture tracker
>> AV/C Desactivado
>> AV/C Activado
>>> AVC enabled

dmesg gives me:

ohci1394: fw-host0: AT dma reset ctx=0, aborting transmission
ieee1394: Node suspended: ID:BUS[0-01:1023]  GUID[0800460104a6fc68]
ieee1394: Node resumed: ID:BUS[0-01:1023]  GUID[0800460104a6fc68]

> In Preferences/Display, is "Enable preview during capture" enabled? If so,
> try
> without it.

i tried both

> Finally, have you tried a 32 bit version?
(Continue reading)

Permalink | Reply | 1 comment |
headers
Dan Dennedy | 6 Jun 2006 18:29
Favicon

Kino 0.9.0 released

Kino 0.9.0 Release Notes
http://www.kinodv.org/

* Bugfixes to Export as a result of resampling changes in v0.8.1.

* Added third generation, simplified IEEE 1394 I/O via libiec61883.
  (dv1394 is still available when libiec61883 is not detected at configure
  step of build process. Also, one can force the usage of dv1394 rather
  than libiec61883 by using configure --with-dv1394.)

NOTE: some build configure options have changed slightly:
Use --enable-quicktime instead of --with-quicktime.
Use --enable-hotplug-script-dir instead of --with-....
Use --enable-hotplug-usermap-dir instead of --with-....
Permalink | Reply | 3 comments |
headers
Dan Dennedy | 6 Jun 2006 18:43
Favicon

Re: problem with HDR-HC1

On Tuesday 06 June 2006 4:37 am, Valentina Messeri wrote:
> >
> > Is it capture or capture preview that is broken?
>
> when i start capture

OK, I was hoping to learn if the problem happens when switching to Capture 
mode or when clicking the Capture button in Capture mode. I will assume you 
mean simply going into Capture mode since that is where most people have 
problems when problems exist.

> kino freezes, and that's what appears in the shell behind: 
> >> Starting Capture
> >> AV/C Activado
> >>
> >>> Using raw1394 capture
> >>> AVC enabled
> >>
> >> Constructing File Capture tracker
> >> AV/C Desactivado
> >> AV/C Activado
> >>
> >>> AVC enabled
>
> dmesg gives me:
>
> ohci1394: fw-host0: AT dma reset ctx=0, aborting transmission

This is bad. This indicates something wrong happening in the hardware perhaps 
as a result of bad driver behavior. I have a hard time believing it is result
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jean-Luc Coulon (f5ibh | 7 Jun 2006 15:34
X-Face
Picon
Gravatar

Fwd: 0.9.0 SIGSEGV if compiled with --enable-quicktime [jean-luc.coulon <at> wanadoo.fr]

Le 07.06.2006 15:24:41, Jean-Luc Coulon (f5ibh) a écrit :
Hi,

I've built kino 0.9.0 with --eneble-quicktime and got a segfault.
Removing this configure option allows kino to run.

Thereafter the message when I launch kino and a gdb backtrace.

Regards

Jean-Luc

Kino experienced a segmentation fault.
Dumping stack from the offending thread

Obtained 3 stack frames.
kino(__gxx_personality_v0+0x342) [0x433d0a]
/lib/libc.so.6 [0x2b161cb27e90]
/lib/libpthread.so.0(__pthread_mutex_trylock+0) [0x2b161c021e10]

Done dumping - exiting.

(gdb) run
Starting program: /usr/bin/kino
[Thread debugging using libthread_db enabled]
[New Thread 47344700457984 (LWP 4579)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 47344700457984 (LWP 4579)]
0x00002b0f4b094e10 in pthread_mutex_trylock () from /lib/libpthread.so.0
(Continue reading)

Permalink | Reply | 0 comments |
headers
sean | 13 Jun 2006 04:34
Picon

Re: Kino 0.9.0 released

Dan Dennedy wrote:
> Kino 0.9.0 Release Notes
> http://www.kinodv.org/
> 
> * Bugfixes to Export as a result of resampling changes in v0.8.1.
> 
> * Added third generation, simplified IEEE 1394 I/O via libiec61883.
>   (dv1394 is still available when libiec61883 is not detected at configure
>   step of build process. Also, one can force the usage of dv1394 rather
>   than libiec61883 by using configure --with-dv1394.)
> 

Is libiec61883 the preferred 1394 linux driver? Don't I 
remember that libiec61883 was meant for pro-grade cams, and 
dv1394 for comsumer-grade - like the panasonic I have?

Do all cams work with libiec61883? What character device is 
used?

I've looked at www.linux1394.org and didn't see much. Am I 
looking in the wrong places, as usual?

Thanks for all the great work on kino!

sean
Permalink | Reply | 2 comments |
headers
Robin Rosenberg | 18 Jun 2006 20:15
Favicon

Site looks wrong in konqueror

Hi all,

I got a new DV camera and am delighted to see it working out of the box with 
kino. Kino is really simple. Excellent work!

The website however looked very strange in my web browser, Konqueror, they 
layout is bad and the PayPal link is there. The errors are only a few simple 
ones:

- The xml tag must start at the beginning of line 1; remove the two empty 
lines
at the start.

- A number of unterminated <span>; replace </small> with </span>

- A nested comment which XML does not allow with confused the browser. This 
what really messes up the layout and content.

- Duplicate ID's, not sure what the consequence is.

-- robin
Permalink | Reply | 1 comment |

Gmane