On Sunday 25 July 2004 18:09, Rob Hare wrote:
> Hey,
>
> The first patch works fine. The second patch did not take.
>
>
> I have also started working on the clip properties dialog. The layout is
> basically in place and now dockable, although it could use some tweaking.=
I
> have hard coded some dummy data for appearance.=A0 See,=A0
> http://www.nocturnalatl.com/index.html=A0=A0 for a screenshot.=A0 Based o=
n the
> architecture, I'm guessing Piave will supply the clip information. What
> information is available? and,
> How is it accessible?
> I looked back thru the archives and didn't find any discussion on this
> dialog. Are there any other things I should be aware of?
The krender.h/cpp files contain all communication between kdenlive and piav=
e.=20
There is a VEML command that get's sent to piave via the getFileProperties(=
)=20
method (line 263 in my krender.cpp sourcefile), and piave replies with=20
detailed info about the file in question (line 525 in krender.cpp)
Note that all communication is asyncrhonous - you should fire off the reque=
st=20
for the information you want, and then do other things until the result=20
happens to arrive - don't hang around waiting for piave to reply :-)
This is an example reply from piave, which should give you an idea of what=
=20
info is available :
<reply command=3D"getFileProperties" duration=3D"13.080000"=20
filename=3D"/home/uchian/video/kdenlivepromo/promo002.dv" status=3D"ok">
<stream duration=3D"13.080000"=20
filename=3D"/home/uchian/video/kdenlivepromo/promo002.dv">
<container format=3D"rawdv">
<codec aspect=3D"1.333333" format=3D"DV" fps=3D"25.000000"=20
height=3D"576" name=3D"libdv_decoder" system=3D"PAL" type=3D"video" width=
=3D"720" />
<codec bitspersample=3D"16" channels=3D"0" emphasis=3D"on"=20
format=3D"PCL" frequency=3D"1280" name=3D"libdv_decoder" quantization=3D"0"=
=20
sampling=3D"2" type=3D"audio" />
</container>
</stream>
</reply>
The signal emitted by krender at the moment does not parse or pass on any o=
f=20
this info - it reads the filename and duration which until now has been all=
=20
it needed to do. It will need to be extended.
If you take a look at the family of avformat*.h/cpp classes, they are the=20
current attempt to describe the various file formats and the information in=
=20
them (The classes are used for passing a file format to piave when renderin=
g,=20
and for dynamically constructing an interface that allows the user to set t=
he=20
file type and codecs, etc.). I am unsure if they are reusable for the clip=
=20
properties page but it's worth a look.
My guess is that the best thing to do - whether using the avformat classes =
or=20
not - would be to store the extra information in DocClipBase or DocClipAVFi=
le=20
so that we can store it at the same time the duration information is reciev=
ed=20
from piave.=20
Hope that helps, let me know if you need more info :-)
Cheers,
Jason
p.s. will have another go at applying the second patch.
Cheers,
Jason
=2D-=20
Jason Wood
Homepage : http://www.uchian.pwp.blueyonder.co.uk

On Sunday 25 July 2004 19:09, Rob Hare wrote:
> Hey,
>
> The first patch works fine. The second patch did not take.
>
>
> I have also started working on the clip properties dialog. The layout =
is
> basically in place and now dockable, although it could use some tweakin=
g. I
> have hard coded some dummy data for appearance.=A0 See,=A0
> http://www.nocturnalatl.com/index.html=A0=A0 for a screenshot.=A0 Based=
on the
> architecture, I'm guessing Piave will supply the clip information.
Right.
> What information is available?
That depends on the file. Piave has a plugin architecture and what=20
information is provided for a specific file is completely in the=20
responsebility of the plugin. In principle you can't expect anything, not=
=20
even on the number of frames, since something like SVG doesn't have frame=
s.=20
The only thing that is certain, is that piave provides a certain number o=
f=20
<key>--<value> pairs describing the stream/file.
> and, How is it accessible?
The communication with the renderer is handled by krender.{h,cpp}
The communication is asynchron, i.e. there is one method emitting the req=
uest=20
to piave (e.g. KRender::getFileProperties) and another set of handlers to=
=20
parse the XML reply from piave ( KRender::reply_getFileProperties_XXXXX ).
> I looked back thru the archives and didn't find any discussion on this
> dialog. Are there any other things I should be aware of?
We (Jason and myself) thought about the different parts of the prokoll of=
=20
communication for quite a while. However, it usually turnes out, that in=
the=20
we need to change things when we really used certain parts of the protoko=
ll. =20
So in the likely case that you find some things that don't work or don't =
make=20
sense, let us know.
Cheers, Rolf
--=20
contacts: http://www.physi.uni-heidelberg.de/~dubitzky

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Hey,<br>
<br>
The first patch works fine. The second patch did not take. <br>
<br>
<br>
I have also started working on the clip properties dialog. The layout
is basically in place and now dockable, although it could use some
tweaking. I have hard coded some dummy data for appearance.&nbsp; See,&nbsp; <a
href="http://www.nocturnalatl.com/index.html">http://www.nocturnalatl.com/index.html&nbsp;</a>&nbsp;
for a screenshot.&nbsp; <br>
Based on the architecture, I'm guessing Piave will supply the clip
information. <br>
What information is available? and, <br>
How is it accessible?<br>
I looked back thru the archives and didn't find any discussion on this
dialog. Are there any other things I should be aware of?<br>
<br>
thanks all,<br>
<br>
Rob<br>
<br>
<br>
<br>
<br>
<br>
<br>
Jason Wood wrote:
<blockquote cite="mid200407222343.29280.jasonwood@..."
type="cite">
<pre wrap="">Hi,
Rob Hare provided me with several patches, which I have applied to cvs and
committed.
The first patch :
Implements the setOpen function of the ListViewItem on add/delete clips to the
project list. This means that when adding/deleting clips, the clip list
remains open.
The second patch fills in more tooltips :
* control buttons now have tips eg: play, stop*
* renderer led shows connected/disconnected
* debug buttons
* timeline combo and slider
* column headers in projectlist window show label name in tooltips instead of
the window tooltip
I'm not sure if I applied the second patch correctly; so please let me know if
there is anything amiss :-)
Cheers,
Jason
</pre>
</blockquote>
<br>
</body>
</html>

Hi,
Rob Hare provided me with several patches, which I have applied to cvs and
committed.
The first patch :
Implements the setOpen function of the ListViewItem on add/delete clips to the
project list. This means that when adding/deleting clips, the clip list
remains open.
The second patch fills in more tooltips :
* control buttons now have tips eg: play, stop*
* renderer led shows connected/disconnected
* debug buttons
* timeline combo and slider
* column headers in projectlist window show label name in tooltips instead of
the window tooltip
I'm not sure if I applied the second patch correctly; so please let me know if
there is anything amiss :-)
Cheers,
Jason
--
Jason Wood
Homepage : http://www.uchian.pwp.blueyonder.co.uk

Newbie wondering if kdenlive is x86_64 compatible yet ?
I tried building kdenlive on gentoo but have errors with
compiling piave, meaning I have not even got to trying
kdenlive yet. I am wondering I should bother at all and
perhaps wait a while longer ?
--markc

Yes, all vital things are in place.
I promised to look into the satatus of the VEML capture interface this weekend
and while doing that I'll check what effect features are working and what is
missing. In the meantime, you can find examples in the examples subdir.
AFAICR all examples work.
Cheers, Rolf
On Wednesday 07 July 2004 09:00, Jason Wood wrote:
> Hi Rolf,
>
> It's been a while since I properly looked at the effects framework; what
> state is piave in for handling parameters and keyframes? Is the relevant
> VEML already in place in piave? All being well, I will try and implement
> something this weekend.
>
> Cheers,
> Jason
--
contacts: http://www.physi.uni-heidelberg.de/~dubitzky

Hi Rolf,
It's been a while since I properly looked at the effects framework; what state
is piave in for handling parameters and keyframes? Is the relevant VEML
already in place in piave? All being well, I will try and implement something
this weekend.
Cheers,
Jason
--
Jason Wood
Homepage : http://www.uchian.pwp.blueyonder.co.uk

Hi Jason,
Here they are the full results:
locate konquerorrc
/usr/share/debian-edu/common/share/config/konquerorrc
locate spacer.png
/usr/share/apps/kdenlive/icons/hicolor/32x32/actions/spacer.png
/usr/src/kde/quanta-3.2.0/kommander/editor/pics/small/spacer.png
/usr/src/kdenlive-0.2.4/icons/hicolor/32x32/actions/spacer.png
/usr/src/kdenlive-cvs/kdenlive/icons/hicolor/32x32/actions/spacer.png
PS: Thanks a lot for your time and effort.
Regards,
Steven.
Jason Wood wrote:
>It still sounds like an install path issue. The toolbar and "edit" menu's are
>standard, and won't be affected by the install path of kdenlive.
>
>try the following as root :
>
>updatedb (to make sure your locate database is up to date)
>
>locate konquerorrc
>
>On my machine, one of the returned lines is :
>
>/usr/share/config/konquerorrc
>
>Now, everything from /share onwards is a kde-specific path, so kdenlive stuff
>should end up in /usr somewhere. (in my case)
>
>Now try this :
>locate spacer.png
>
>I get this :
>/usr/share/apps/kdenlive/icons/hicolor/32x32/actions/spacer.png
>
>As you see, in my install, the bit before /share is the same as for konqueror.
>
>(/usr in both cases)
>
>Can you do the same test on your system (the same two locate lines) and let me
>know the results?
>
>Cheers,
>Jason
>
>
>

On Friday 02 July 2004 15:13, Riviere Informatique SARL wrote:
> My menus are:
> File Edit View Settings Help
> There's no 'Project, Timeline or Render' menu.
>
> I've done a make clean and a configure as you described (I check the value
> of prefix which is /usr) Then make, make install, checked that the
> executable was properly installed and even did a 'type kdenlive' to see if
> I would actually execute the /usr/bin/kdenlive - but still no luck. There
> are 2 menus that DO pop up, now I've tried clicking just about everywhere:
> The 'Toolbar menu' when right-clicking on an empty part of the toolbar and
> a standard 'edit' menu when I rightclick in the right-hand window of the
> 'Debug' tab.
>
> I deleted the rc file too, as you suggested.
>
> All my other KDE apps work fine.
It still sounds like an install path issue. The toolbar and "edit" menu's are
standard, and won't be affected by the install path of kdenlive.
try the following as root :
updatedb (to make sure your locate database is up to date)
locate konquerorrc
On my machine, one of the returned lines is :
/usr/share/config/konquerorrc
Now, everything from /share onwards is a kde-specific path, so kdenlive stuff
should end up in /usr somewhere. (in my case)
Now try this :
locate spacer.png
I get this :
/usr/share/apps/kdenlive/icons/hicolor/32x32/actions/spacer.png
As you see, in my install, the bit before /share is the same as for konqueror.
(/usr in both cases)
Can you do the same test on your system (the same two locate lines) and let me
know the results?
Cheers,
Jason
--
Jason Wood
Homepage : http://www.uchian.pwp.blueyonder.co.uk

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
My menus are:<br>
File Edit View Settings Help<br>
There's no 'Project, Timeline or Render' menu.<br>
<br>
I've done a make clean and a configure as you described (I check the
value of prefix which is /usr)<br>
Then make, make install, checked that the executable was properly
installed and even did a 'type kdenlive' to see if I would actually
execute the /usr/bin/kdenlive - but still no luck.<br>
There are 2 menus that DO pop up, now I've tried clicking just about
everywhere: The 'Toolbar menu' when right-clicking on an empty part of
the toolbar and a standard 'edit' menu when I rightclick in the
right-hand window of the 'Debug' tab.<br>
<br>
I deleted the rc file too, as you suggested.<br>
<br>
All my other KDE apps work fine.<br>
<br>
I'm puzzled...<br>
<br>
Regards,<br>
Steven.<br>
<br>
Jason Wood wrote:
<blockquote cite="mid200406301857.47722.jasonwood@..."
type="cite">
<pre wrap="">On Tuesday 29 June 2004 21:18, Riviere Informatique SARL wrote:
</pre>
<blockquote type="cite">
<pre wrap="">That doesn't make a difference - still no context menu. I can change the
shortcuts to add a clip
</pre>
</blockquote>
<pre wrap=""><!---->
Do you get a full set of menus across the top of Kdenlive? (including Project,
Timeline, Render...)
If not, then you either have not installed Kdenlive, or have installed it to
an incorrect path.
To install a KDE app, run
./configure --prefix=`kde-config --prefix`
(watch out for those back-quote thingies around kde-config --prefix!)
then make, make install.
Afterwards, you might needs to remove the kdenliverc file out of
your .kde/shader/config directory as well.
Let me know if that helps.
Cheers,
Jason
</pre>
</blockquote>
</body>
</html>