From: Jason W. <jas...@bl...> - 2003-11-30 03:41:55
|
It works, but is not yet feature-complete. In particular, you cannot delete a marker once you have placed it (although you can Ctrl-Z to undo placement of the marker). Basically, you can : 1. Select the "marker" tool 2. click on a clip to place a marker. 3. After going back to the move tool, dragging clips around will snap to the markers as well as to the edges of clips, etc. Most importantly, markers will snap to other markers. What still needs to be done : 1. being able to delete markers (I am thinking Ctrl-clicking on them with the marker tool, and a "clear all markers" option in the menu somewhere. 2. Accurate positioning of markers - I think that a new action in the menu is needed to place a marker at the current seek position. 3. Markers on the timeline itself, and markers in the clip monitor. I think that setting markers via the clip monitor would be an intuitive way to set them (perhaps making obsolete the marker tool that I have semi-implemented?) Is there anything else you can think of? Please have a play around with what is there and let me know what you think, how else it could be better, etc. Oh yes, I have added a context menu to the timeline. Now all I need is suggestions as to which actions should be on the timeline context menu - at the moment, it is almost straight copy of the timeline menu, but that can be easily changed. Cheers, Jason -- Jason Wood Homepage : www.uchian.pwp.blueyonder.co.uk |
From: Jason W. <jas...@bl...> - 2003-11-30 15:40:36
|
On Sunday 30 Nov 2003 8:50 am, booker wrote: > Am Sonntag, 30. November 2003 04:41 schrieb Jason Wood: > > It works, but is not yet feature-complete. In particular, you cannot > > delete a marker once you have placed it (although you can Ctrl-Z to undo > > placement of the marker). > > > > Basically, you can : > > > > 1. Select the "marker" tool > > 2. click on a clip to place a marker. > > 3. After going back to the move tool, dragging clips around will snap to > > the markers as well as to the edges of clips, etc. Most importantly, > > markers will snap to other markers. > > > > What still needs to be done : > > > > 1. being able to delete markers (I am thinking Ctrl-clicking on them with > > the marker tool, and a "clear all markers" option in the menu somewhere. > > > > 2. Accurate positioning of markers - I think that a new action in the > > menu is needed to place a marker at the current seek position. > > > > 3. Markers on the timeline itself, and markers in the clip monitor. I > > think that setting markers via the clip monitor would be an intuitive way > > to set them (perhaps making obsolete the marker tool that I have > > semi-implemented?) > > > > Is there anything else you can think of? Please have a play around with > > what is there and let me know what you think, how else it could be > > better, etc. > > Cool, I will checkout, but right now piave failed to start up ... please > see the attached log file. > > greetings > Reinhard Erm, before I reply, did I just accept this message with a 450K log to be posted to everybody on the list? If I did, sorry. The log does not say much except that piave cannot listen on it's port. This normally means that an instance of piave from a previous run of kdenlive is still running, or that an instance of piave has recently crashed (in which case it takes a minute or so for the port to free itself). try doing : kill -9 piave wait a minute or two, and then restart kdenlive. In the meantime, I will persist the "ignore messages" setting in the debug window when exiting kdenlive so that we can get meaningful logs if something really is going wrong with piave on first connection. Cheers, Jason -- Jason Wood Homepage : www.uchian.pwp.blueyonder.co.uk |
From: <r....@t-...> - 2003-11-30 17:35:36
|
Am Sonntag, 30. November 2003 16:17 schrieben Sie: > The log does not say much except that piave cannot listen on it's port. > This normally means that an instance of piave from a previous run of > kdenlive is still running, or that an instance of piave has recently > crashed (in which case it takes a minute or so for the port to free > itself). > > try doing : > > kill -9 piave seems not to work, because I got "no such pid" message. > wait a minute or two, > > and then restart kdenlive. btw - Is it normal that there are 10 (ten) instances of piave running when kdenlive is started? greetings Reinhard |
From: Jason W. <jas...@bl...> - 2003-11-30 17:50:48
|
On Sunday 30 Nov 2003 5:39 pm, booker wrote: > Am Sonntag, 30. November 2003 16:17 schrieben Sie: > > The log does not say much except that piave cannot listen on it's port. > > This normally means that an instance of piave from a previous run of > > kdenlive is still running, or that an instance of piave has recently > > crashed (in which case it takes a minute or so for the port to free > > itself). > > > > try doing : > > > > kill -9 piave > > seems not to work, because I got "no such pid" message. oops, that should have read : killall -9 piave However I have just taken an update of piave, and seem to have some issues as well. See the bottom of the file for the relevant part of the log. It is somewhere within creating the video - the "document" instance of piave works fine - it happily finds the lengths of files. Like I mentioned, I have now made the "ignore messages" option on the debug window persist so that you can still get a log when just starting Kdenlive (as I did here). I am committing now. Remember that if the log is filling up with messages, you will experience slow performance from Kdenlive! So remember to turn it off when you've finished with it. > > wait a minute or two, > > > > and then restart kdenlive. > > btw - Is it normal that there are 10 (ten) instances of piave running when > kdenlive is started? Kdenlive (at the moment) will start 4 instances of piave, although by the time of the next release that should come back down to 3. However, piave makes use of several threads, which will each show up as a seperate entry in top, so 10 is probably about right. piave log for clip monitor follows : ---------------------------------------------------- Launching Process /usr/local/bin/piave as server on port 6103 Process launching successfully, pid = 3441 Connecting to server on port 6103 Sending Command <getCapabilities/> Connected on port 33297 to host on port 6103 Sending Command <createVideoXWindow format="xv" show="false" /> pluginmgr.cc:75 WARNING: failed to open dll: /usr/local/lib/piave/plugins/effects/libsamplerateplugin.so with errors: /usr/local/lib/piave/plugins/effects/libsamplerateplugin.so: undefined symbol: _ZN5PIAVE6Global5quietE pluginmgr.cc:78 INFO: opened dll: /usr/local/lib/piave/plugins/effects/libinvert.so pluginmgr.cc:90 INFO: Register plugin pluginName=InvertFilterPlugin pluginmgr.cc:78 INFO: opened dll: /usr/local/lib/piave/plugins/effects/libalphablend.so pluginmgr.cc:90 INFO: Register plugin pluginName=AlphaBlendPlugin pluginmgr.cc:78 INFO: opened dll: /usr/local/lib/piave/plugins/effects/libtextmaster.so pluginmgr.cc:90 INFO: Register plugin pluginName=TextMasterPlugin pluginmgr.cc:78 INFO: opened dll: /usr/local/lib/piave/plugins/effects/libimage.so pluginmgr.cc:90 INFO: Register plugin pluginName=ColorStillPlugin pluginmgr.cc:78 INFO: opened dll: /usr/local/lib/piave/plugins/iostream/librawdvstream.so pluginmgr.cc:90 INFO: Register plugin pluginName=LibDVDecoderPlugin pluginmgr.cc:90 INFO: Register plugin pluginName=LibDVEncoderPlugin pluginmgr.cc:90 INFO: Register plugin pluginName=InRawDVStreamPlugin pluginmgr.cc:90 INFO: Register plugin pluginName=OutRawDVStreamPlugin pluginmgr.cc:78 IN FO: opened dll: /usr/local/lib/piave/plugins/iostream/libsdlstream.so pluginmgr.cc:90 INFO: Register plugin pluginName=SDLStreamPlugin pluginmgr.cc:78 INFO: opened dll: /usr/local/lib/piave/plugins/iostream/libossstream.so pluginmgr.cc:90 INFO: Register plugin pluginName=OssPlugin pluginmgr.cc:78 INFO: opened dll: /usr/local/lib/piave/plugins/iostream/libavistream.so pluginmgr.cc:90 INFO: Register plugin pluginName=InAviDVStreamPlugin pluginmgr.cc:90 INFO: Register plugin pluginName=OutAviDVStreamPlugin pluginmgr.cc:78 INFO: opened dll: /usr/local/lib/piave/plugins/iostream/libartsstream.so pluginmgr.cc:90 INFO: Register plugin pluginName=ArtsPlugin pluginmgr.cc:78 INFO: opened dll: /usr/local/lib/piave/plugins/iostream/libvorbisfilestream.so pluginmgr.cc:90 INFO: Register plugin pluginName=VorbisfilePlugin pluginmgr.cc:78 INFO: opened dll: /usr/local/lib/piave/plugins/iostream/libsndfilestream.so pluginmgr.cc:90 INFO: Register plugin pluginName=SndfilePlugin pluginmgr.cc:78 INFO: opened dll: /usr/local/lib/piave/plugins/iostream/libalsastream.so pluginmgr.cc:90 INFO: Register plugin pluginName=AlsaPlugin server.cc:153 INFO: initListenSocket server.cc:180 INFO: Listening on port 6103 server.cc:120 INFO: Got connection on socket 7 server.cc:186 INFO: Stopp listening for connections kdenserver.cc:514 INFO: starting main server loop piave_base.cc:226 WARNING: PIAVE caught a segmentation violation 0 --- backtrace ------ start ---- /usr/local/lib/libpiave.so.0(_ZN5PIAVE6Global14printBackTraceEv+0x27) [0x40047a85] /usr/local/lib/libpiave.so.0(_ZN5PIAVE6Global18fatalSignalHandlerEi+0xd3) [0x40047c5b] /lib/i686/libpthread.so.0 [0x400aa4ec] /lib/i686/libc.so.6 [0x40637ca8] /usr/local/lib/libpiave.so.0(_ZN5PIAVE14KdenLiveServer23veml_createVideoXWindowEPKNS_8VEMLCmndE+0xdf9) [0x40066959] /usr/local/lib/libpiave.so.0(_ZN5PIAVE14KdenLiveServer15processCommandsEv+0x166) [0x400658d4] /usr/local/lib/libpiave.so.0(_ZN5PIAVE14KdenLiveServer17_process_commandsEPv+0x1e) [0x40064c88] /lib/i686/libpthread.so.0 [0x400a5600] /lib/i686/libc.so.6(__clone+0x57) [0x406e9a37] --- backtrace ------ stop ----- server.cc:76 WARNING: atexit handler: Cheers, Jason -- Jason Wood Homepage : www.uchian.pwp.blueyonder.co.uk |
From: <r....@t-...> - 2003-11-30 22:05:02
Attachments:
errormessages30nov2003_2
|
Am Sonntag, 30. November 2003 18:50 schrieb Jason Wood: > On Sunday 30 Nov 2003 5:39 pm, booker wrote: > > Am Sonntag, 30. November 2003 16:17 schrieben Sie: > > > The log does not say much except that piave cannot listen on it's port. > > > This normally means that an instance of piave from a previous run of > > > kdenlive is still running, or that an instance of piave has recently > > > crashed (in which case it takes a minute or so for the port to free > > > itself). > > > > > > try doing : > > > > > > kill -9 piave > > > > seems not to work, because I got "no such pid" message. > > oops, that should have read : > > killall -9 piave ok, so it seems that there is no remaining piave instance to be killed, right? [booker@linux kdenlive]$ killall -9 piave piave: no process killed > However I have just taken an update of piave, and seem to have some issues > as well. See the bottom of the file for the relevant part of the log. It is > somewhere within creating the video - the "document" instance of piave > works fine - it happily finds the lengths of files. > > Like I mentioned, I have now made the "ignore messages" option on the debug > window persist so that you can still get a log when just starting Kdenlive > (as I did here). I am committing now. I've attached the new log file, but i think the important part is directly at the beginning of it: "Connection Refused" greetings Reinhard btw - I still use mandrake 9.1 |
From: <je...@li...> - 2003-11-30 23:06:22
|
Hiya Jason, I haven't had a chance to try all of this out, but just some remarks that spring to mind. > 1. being able to delete markers (I am thinking Ctrl-clicking on them with > the marker tool, and a "clear all markers" option in the menu somewhere. Haven't you just found your own answer here? Wrt what should be in the context sensitive menu on the timeline? ;-) Basically, if I understand you correctly, you can set these markers on a clip somewhere, then dragging the clip around will make it snap on those markers. Either to other markers (from different clips) or their edges, right? If so, then I think you should be able to set the markers on the timeline (with the context sensitive menu). I would argue that 'what should go in the timeline' and 'what should go in the clip monitor' depends on what it does. And if the function of something spans multiple clips, then it should be done on the timeline... If the meaning of whatever you do only applies to one clip, then it should be done in the clip monitor. That ofcourse is just my humble idea, and it doesn't mean you couldn't do 'both'. But I would expect to set markers via the context sensitive menu on the timeline, and use that as well to remove them. Just my two pennies worth ;-) /Cheers, Jelte |
From: Jason W. <jas...@bl...> - 2003-12-01 00:39:45
|
On Sunday 30 Nov 2003 10:04 pm, je...@li... wrote: > Hiya Jason, > > I haven't had a chance to try all of this out, but just some remarks that > spring to mind. > > > 1. being able to delete markers (I am thinking Ctrl-clicking on them with > > the marker tool, and a "clear all markers" option in the menu somewhere. > > Haven't you just found your own answer here? Wrt what should be in the > context sensitive menu on the timeline? ;-) Well in this case, possibly :-) But my question about context menus was a little more all-encompassing. For instance - should the tools be in the context menu for easy access, or do they just clutter it up? > Basically, if I understand you correctly, you can set these markers on a > clip somewhere, then dragging the clip around will make it snap on those > markers. Either to other markers (from different clips) or their edges, > right? That is correct. > If so, then I think you should be able to set the markers on the > timeline (with the context sensitive menu). This is ok, but there is an issue of which clip gets the marker - should it be "all selected clips", or should it be "the clip that you right-clicked on"? Which feels "correct" to you? I think that it is necessary that the context-sensitive version should place the marker on the clip at the current seek time, the current "marker" tool I have implemented is actually useless because you cannot use it to accurately place markers (although I think it might still be useful for deleting them). > I would argue that 'what should go in the timeline' and 'what should go in > the clip monitor' depends on what it does. And if the function of something > spans multiple clips, then it should be done on the timeline... If the > meaning of whatever you do only applies to one clip, then it should be done > in the clip monitor. You can look at markers in two senses. The first is that the whole idea of snap markers is to be able to snap clips to each other. From this point of view, we want a representation of them on the timeline. The other way of looking at it is that you want to be able to place a snap marker with complete accuracy. From this point of view, a representation of markers within the clip monitor also makes sense. To be honest, I think that is the answer - there needs to be a representation of snap markers in both the clip monitor and on the timeline. There is a further extension to this then : when adding markers onto the timeline itself, we can again have markers on the timeline, and markers in the workspace monitor. > That ofcourse is just my humble idea, and it doesn't mean you couldn't do > 'both'. But I would expect to set markers via the context sensitive menu on > the timeline, and use that as well to remove them. That is possible, the solution via the clip monitor would be to have a button saying "add marker". I think that for the moment, I will add this as well as the one on the timeline, and see how it feels. Keep feeding me your thoughts though :-) Cheers, Jason -- Jason Wood Homepage : www.uchian.pwp.blueyonder.co.uk |