|Thread title||Replies||Last modified|
|Do you enjoy Trad Jazz?||0||16:01, 18 May 2013|
|Levels of headings||6||15:29, 27 February 2013|
|Audio alignment||0||18:59, 22 February 2013|
|Lost video||4||12:01, 20 February 2013|
|upload new vers of file and the browser cache||1||11:10, 13 July 2012|
|embed Vimeo||3||22:50, 3 July 2012|
|Embed Video test bed||5||15:12, 3 July 2012|
|Translating the Manual||0||15:38, 11 July 2011|
In case you are wondering why there have been so many edits of heading levels on the Kdenlive pages, it's all about how the sections fit together in the online manual. If no allowance is made on the UserBase pages the online manual index would have what obviously should be subsections appearing as top level sections.
So we want the heading levels to start at level 4 ? - ie 4 equals signs around the heading ?
What ever is the recomendation I am happy to try and follow it. Just give me a guide as to what it should be!
No. Top level heading will always be 2. If it's possible to visualise your headings as the whole kdenlive tree, that will tell you where to put headings, but sometimes it's too complicated when you are writing a page. In that case continue to write as you are doing and yurchor or Claus_chr will adapt them as necessary. Getting the stuff written is the important thing. Our translators can fix up the heading markup if necessary. I just thought you would wonder what was going on
I had not actually noticed. But thanks for the heads up. And thanks for cleaning up after me.
While we are on the subject of headings though.
I don't like what the headings to on the table of contents page on
The headings go
5. Project and File management
1.The Project Tree 2.Project File Details 3. Settings
1. Editing 2. Grouping 3. Guides
But they should go
5. Project and File management
5.1 The Project Tree 5.2 Project File Details 5.3 Settings
6.1 Editing 6.2 Grouping 6.3 Guides
Is there anything that can be done about that ?
I don't like it either, but there is no easy answer. We could use bulleted lists, instead, which probably wouldn't look as bad. Other than that, my searching hasn't found any solution as yet.
Hi. Do you know anything about audio alignment in kdenlive? There is a discussion thread http://userbase.kde.org/Talk:Kdenlive/Manual/Timeline/Right_Click_Menu#Audio_alignment_2031
Could you please take a look at http://userbase.kde.org/Talk:Kdenlive/Manual/Introduction#Video_is_hidden_1974 ? Thanks.
I found another video intro to kdenlive on youtube. Dunno how it compares to the missing one.
If it bears a recent date it is certainly better than no video at all. Can you change the link to point to that, please?
I have a suggestion that we should add a note on the page where you upload a new version of a file.
This note should be something like.
"After uploading a new version of the file it is recommended that you force a refresh of the page in the browser. Otherwise the browser may display the old version in the file from within its cache. And you might think your new file version has not updated"
So the mediawiki-embedvideo extension is supposed to support vimeo videos too.
So this should display a video
But it errors.
This is probably an issue with the embedvideo extension. Which could be chased up at embedvideo bug tracker.
I would chase this up. But I don't know what version of the embedvideo was installed recently etc. So maybe some one else would be nice enough to chase this :-)
Actually i think it is a problem with the id. The sources tell me it should go to http://vimeo.com/moogaloop.swf?clip_id=$1&;server=vimeo.com&fullscreen=0&show_title=1&show_byline=1&show_portrait=0 where you can replace $1 with the id you gave. But going to that url directly it also states this video doesn't exist. Can you tell me the name of the video or something, where i can find it?
So I requested userbase install [EmbedVideo] extension.
Neverendingo 12:59, 28 June 201 Posts "Skadoosh, installed :)" which I take to mean that he did install it.
But that means
should embed a video.
But it does not.
Sorry, my mistake, it was set in the wrong config, which was only used by the other wikis. Now it works
Sweet. That is so awesome. I was envisioning some sort of policy road block