[Kdenlive-devel] Does Kdenlive build? (preparing for a V0.1.1 tarball)
On Sunday 12 January 2003 05:26 pm, Chris Clayton wrote: > On Sunday 12 January 2003 4:12 pm, Rolf Dubitzky wrote: > > A) Chris, are you using KDE as desktop? > > Yes Rolf, I am running KDE 3.0.5a. > > > if yes, couls you try to start > > piave like this: > > artsdsp /usr/local/bin/piave -d > > That works fine, I get proper playback. Thanks (to both Rolf and Jason). I wonder what's going on there... I tried KDE at home and made sure aRts is running and I was able to play a video with mplayer, an mp3 wit xmms and still I had no trouble to get audio from piave... hmm... I guess we can live with artsdsp till someone implements MCOP to piave. However, haveing a KDE application that does not work under KDE but with Fvwm is a little bit embarassing, don't you think??;- Cheers, Rolf *** Rolf Dubitzky e-mail: Rolf.Dubitzky at Physik.TU-Dresden.de s-mail see http://hep.phy.tu-dresden.de/~dubitzky/ ***
[Kdenlive-devel] Does Kdenlive build? (preparing for a V0.1.1 tarball)
On Sunday 12 January 2003 04:55 pm, Chris Clayton wrote: > Jason, Rolf. > > I've maybe been partially wasting your time because I was not dragging the > clip onto the timeline. NP. > Yes, I see playback. These actions add the following to piave's xterm: ok. so far so good ;-) > > 4. Seek somewhere over the clip and press play - do you get playback? > > Maybe not a complete waste of your time, because I don't see playback here. > Immediatelt, as far as I can tell, the playback window just goes grey and > kdeonlive's green light goes off. The following is added to piave's > console: > server.cc:215 INFO: << sending message stop > ossstream.cc:138 WARNING: couldn't get right sampling rate > audio->frequency=32000 rate_request=32072 Hmm... te message says, that piave tries to get an oss stream rom the /dev/dsp with a sampling frequency of 32000, which is correct. But your system returns a stream with a sampling rate of 32072 Does anybody know what that means? Does your sound driver mayby not support 32000 bit samplings? If so, what should piave do in such a case, or is the 32000 bit channel only busy, and the next best channel is 32072??? I have two ideas: A) Chris, are you using KDE as desktop? if yes, couls you try to start piave like this: artsdsp /usr/local/bin/piave -d B) I go back home and try to find out how OSS works. Any help is appreciated. Cheers, Rolf *** Rolf Dubitzky e-mail: Rolf.Dubitzky at Physik.TU-Dresden.de s-mail see http://hep.phy.tu-dresden.de/~dubitzky/ ***
[Kdenlive-devel] Does Kdenlive build? (preparing for a V0.1.1 tarball)
On Sunday 12 January 2003 4:12 pm, Rolf Dubitzky wrote: > A) Chris, are you using KDE as desktop? Yes Rolf, I am running KDE 3.0.5a. > if yes, couls you try to start > piave like this: > artsdsp /usr/local/bin/piave -d > That works fine, I get proper playback. Thanks (to both Rolf and Jason). Chris
[Kdenlive-devel] Does Kdenlive build? (preparing for a V0.1.1 tarball)
On Sunday 12 January 2003 04:09 pm, Jason Wood wrote: > Erm, should be obvious, but please pass the filename back in the > getFileCapabilities command as you normally would, or I won't know which > file request I am recieving an answer to! yes, sure, and I would prefere: unknown format or Cheers, Rolf *** Rolf Dubitzky e-mail: Rolf.Dubitzky at Physik.TU-Dresden.de s-mail see http://hep.phy.tu-dresden.de/~dubitzky/ ***
[Kdenlive-devel] Does Kdenlive build? (preparing for a V0.1.1 tarball)
On Sunday 12 January 2003 04:01 pm, Jason Wood wrote: > And 4, dissallow the adding of clips to the project list which cannot be > used with the current project settings. right. > Incidentally, this reminds me of a bug in piave : if you try to get the > fileProperties of a non-dv clip (for example, a webpage of a .cpp file) > piave crashes. > > I'm not suggesting that piave should try to pass back relevant info about > such files ;-) but a simple > > > > or similar would probably make sense. Oooopsy! Yes, of course. I'll fix it right now. unfortunately I can't commit it, since sourceforge cvs seems to be down (again) Cheers, Rolf *** Rolf Dubitzky e-mail: Rolf.Dubitzky at Physik.TU-Dresden.de s-mail see http://hep.phy.tu-dresden.de/~dubitzky/ ***
[Kdenlive-devel] Does Kdenlive build? (preparing for a V0.1.1 tarball)
On Sunday 12 January 2003 03:55 pm, Jason Wood wrote: > On Sunday 12 Jan 2003 2:21 pm, Rolf Dubitzky wrote: > Hmm, I think I might have seen this bug manifest myself, but in my case > kdenlive always restarts piave again straight afterwards (you see the green > LED flash on,off,on), so I didn't pay it too much thought. > > Chris, could you run piave in a seperate console : I see the same here. > piave -d > > Then start kdenlive, and let me know if it still closes? At least for me, when running in a seperate window, everything is ok... Cheers, Rolf *** Rolf Dubitzky e-mail: Rolf.Dubitzky at Physik.TU-Dresden.de s-mail see http://hep.phy.tu-dresden.de/~dubitzky/ ***
no playback (was: [Kdenlive-devel] Does Kdenlive build? (preparing for a V0.1.1 tarball) )
On Sunday 12 January 2003 03:50 pm, Chris Clayton wrote: > Rolf, > > Thats changed things a bit but still no playback. Aww.. crap! ;-) Well, let's see... > and in the debug tab: > > piave_base.cc:129 INFO: Setting up project for PAL system > piave_base.cc:163 INFO: Setup preview mode > server.cc:151 INFO: initListenSocket > server.cc:184 INFO: Stopp listening for connections > server.cc:166 WARNING: Error initialising server > server.cc:140 WARNING: Error accepting connection > server.cc:74 WARNING: atexit handler: This is not used if you start piave in a seperate window, so we can ignor it... > frame.cc:833 INFO: allocating new DVFrame > avstream.cc:144 INFO: video: > avstream.cc:145 INFO: system : PAL > avstream.cc:146 INFO: format : 4:3 > avstream.cc:150 INFO: audio: > avstream.cc:151 INFO: frequency : 32000 > avstream.cc:152 INFO: num_channels : 2 > avstream.cc:153 INFO: quantization : 12 > avstream.cc:154 INFO: emphasis : off > avstream.cc:155 INFO: sampling : 2 > server.cc:213 INFO: << sending message start > server.cc:214 INFO: > filename="/home/chris/4x3-PAL.dv" duration="2.00"/> ok. great. > server.cc:215 INFO: << sending message stop > kdenserver.cc:97 INFO: waiting for dropQueue >notempty< > > If I try to start playback, I see nothing but the following gets added to > the xterm: > > server.cc:238 INFO: > receive message start > server.cc:239 INFO: > > Ok, here is the problem, the scenelist is empty. your clip was supposed to show up there. 1) have you actually inserted a clip to the timeline? Unlike in kino, you have first 'add' the clip to the filelist (upper left window) and then drag&drop it to the timeline. 2) If you have a clip in the timeline, before you hit play, try moving the slider (any of the two). If you see a picture, hit play. if you can playback now it may be possible, that you have an older version of kdenlive. Try to cvs update. 3) If you still didn't see any kind of picture... errr... h.. could you please send the output again? > setSceneList > type: standard queue > attributes: none > scenelist >type: standard queue >attributes: none > kdenserver.cc:661 INFO: new HEAD >>> >StoryMNode: start 0 length 0 > storybase.cc:536 INFO: setting HEAD with length=0 Hmm.. somehow your timeline seems to be empty strange... > Hope this is helpful, Cheers Yes, very, thanx a lot for your patience ;-) Cheers, Rolf *** Rolf Dubitzky e-mail: Rolf.Dubitzky at Physik.TU-Dresden.de s-mail see http://hep.phy.tu-dresden.de/~dubitzky/ ***
[Kdenlive-devel] Does Kdenlive build? (preparing for a V0.1.1 tarball)
Jason, Rolf. I've maybe been partially wasting your time because I was not dragging the clip onto the timeline. However, I've followed Jason's list and below is what I get (I've included everything written to piave's console at each stage, but the problem occurs right at the end, so you may want to look there first): > 1. Add the clip to the project list. > 2. Drag the clip from the project list to the timeline - you should get a > long pink box. Peanut:~$ /usr/local/bin/piave -d piave_base.cc:129 INFO: Setting up project for PAL system piave_base.cc:163 INFO: Setup preview mode server.cc:151 INFO: initListenSocket server.cc:178 INFO: Listening on port 6100 server.cc:118 INFO: Got connection on socket 4 server.cc:184 INFO: Stopp listening for connections kdenserver.cc:377 INFO: starting main server loop kdenserver.cc:328 INFO: starting process thread kdenserver.cc:97 INFO: waiting for dropQueue >notempty< server.cc:238 INFO: > receive message start server.cc:239 INFO: server.cc:240 INFO: > receive message stop kdenserver.cc:268 INFO: Recieved VEML command getCapabilites kdenserver.cc:272 WARNING: unknown command "getCapabilites" kdenserver.cc:268 INFO: Recieved VEML command createVideoXWindow outsdlstream.cc:64 INFO: Initializing SDL outsdlstream.cc:75 INFO: setting SDL video mode outsdlstream.cc:87 INFO: detected bpp=16 outsdlstream.cc:106 INFO: Got SDL overlay outsdlstream.cc:108 INFO: Got SDL hardware overlay outsdlstream.cc:109 INFO: _overlay->planes=1 outsdlstream.cc:110 INFO: _overlay->pitches[0]=1440 outsdlstream.cc:111 INFO: _overlay->w=720 _overlay->h=576 outsdlstream.cc:113 INFO: lock overlay ok outsdlstream.cc:135 INFO: Using SDL YUV overlay _SDL_init_OK=1 kdenserver.cc:425 WARNING: window not resizable server.cc:213 INFO: << sending message start server.cc:214 INFO: server.cc:215 INFO: << sending message stop kdenserver.cc:97 INFO: waiting for dropQueue >notempty< server.cc:238 INFO: > receive message start server.cc:239 INFO: server.cc:240 INFO: > receive message stop kdenserver.cc:268 INFO: Recieved VEML command getFileProperties avstream.cc:110 INFO: Init InRawDVStream avstream.cc:122 INFO: opened file "/home/chris/4x3-PAL.dv" with 50 frames. frame.cc:833 INFO: allocating new DVFrame avstream.cc:144 INFO: video: avstream.cc:145 INFO: system : PAL avstream.cc:146 INFO: format : 4:3 avstream.cc:150 INFO: audio: avstream.cc:151 INFO: frequency : 32000 avstream.cc:152 INFO: num_channels : 2 avstream.cc:153 INFO: quantization : 12 avstream.cc:154 INFO: emphasis : off avstream.cc:155 INFO: sampling : 2 server.cc:213 INFO: << sending message start server.cc:214 INFO: server.cc:215 INFO: << sending message stop kdenserver.cc:97 INFO: waiting for dropQueue >notempty< > 3. Seek around (drag the ruler marker around the project) - when you move > it over the clip, do you get playback? Yes, I see playback. These actions add the following to piave's xterm: server.cc:238 INFO: > receive message start server.cc:239 INFO: server.cc:240 INFO: > receive message stop kdenserver.cc:268 INFO: Recieved VEML command setSceneList VEML.cc:81 INFO: add daughter (*cmndListIter)->name()=scenelist VEML.cc:81 INFO: add daughter (*cmndListIter)->name()=scene VEML.cc:81 INFO: add daughter (*cmndListIter)->name()=stillcolor VEML.cc:81 INFO: add daughter (*cmndListIter)->name()=scene VEML.cc:81 INFO: add daughter (*cmndListIter)->name()=input kdenserver.cc:268 INFO: Recieved VEML command seek kdenserver.cc:608 INFO: setSceneList start setSceneList type: standard queue attributes: none scenelist type: standard queue attributes: none scene type: standard queue attributes: 1 Name: duration val: 0.6 stillcolor type: standard queue attributes: 1 Name: yuvcolor val: #00 scene type: standard queue attributes: 1 Name: duration val: 2 input type: standard queue attributes: 3 Name: file val: /home/chris/4x3-PAL.dv Name: inpoint val: 0 Name: outpoint val: 2 storybase.cc:441 INFO: length()=15 mediaelements.cc:57 INFO: construct AVChunk with length=50 name=/home/chris/4x3-PAL.dv kdenserver.cc:642 INFO: head->length()=15 avChunk->start()=15 storybase.cc:441 INFO: length()=65 kdenserver.cc:661 INFO: new HEAD >>> StoryMNode: start 0 length 65 Q25PIAVE10ColorStill start: 0 length: 15 Q25PIAVE7AVChunk start: 15 length: 50 storybase.cc:536 INFO: setting HEAD with length=65 kdenserver.cc:665 INFO: new HEAD <<< server.cc:213 INFO: << sending message start server.cc:214 INFO: server.cc:215 INFO: << sending message stop kdenserver.cc:472 INFO: seek frame=1
[Kdenlive-devel] Does Kdenlive build? (preparing for a V0.1.1 tarball)
On Sunday 12 January 2003 03:29 pm, Jason Wood wrote: > On Sunday 12 Jan 2003 2:03 pm, Rolf Dubitzky wrote: > > On Sunday 12 January 2003 02:47 pm, Jason Wood wrote: > > > On Sunday 12 Jan 2003 12:04 pm, Rolf Dubitzky wrote: > I can handle that, but it is the simple bit :-) > > To add things properly to kdenlive (i.e., not as a hack), I need to be able > to > > > 1. Determine which file formats piave can export to. Ok, I see, once I implement I will add that. > 2. Add a dialog to ask the user which of those formats he wishes to work > in. 3. Setup the timeline and project accordingly (this is quick and easy) > By the time stages 1 and 2 are done though, we are very close to having > specified input file formats as well, and it will be very easy to add e.g. > picture (png, jpg) support in kdenlive. This gives an idea as to the > general nature of the code that needs to be implemented - a quick hack for > NTSC isn't going to achieve much. hmm... > If piave can handle inacurate frame reading (e.g. being sent from the > timeline at 25 fps when piave is rendering at 30fps) then I think we should > leave it at that for now if we want to release a beta, or put off the beta > release until we have done things properly. I don't know. propperly might take a while, but I would like to have something that can be used by our friends overseas... but maybe you are right and it's for the second release... > In case you read me wrong, the file format you will be passing in > getFileCapabilities is what it should be passing, not a hack - but to > quickly add NTSC support properly would be a hack if we disregard the > handling of all other file formats. Yes, I agree. Cheers, Rolf *** Rolf Dubitzky e-mail: Rolf.Dubitzky at Physik.TU-Dresden.de s-mail see http://hep.phy.tu-dresden.de/~dubitzky/ ***
[Kdenlive-devel] Does Kdenlive build? (preparing for a V0.1.1 tarball)
On Sunday 12 Jan 2003 3:12 pm, Rolf Dubitzky wrote: > On Sunday 12 January 2003 04:09 pm, Jason Wood wrote: > > Erm, should be obvious, but please pass the filename back in the > > getFileCapabilities command as you normally would, or I won't know which > > file request I am recieving an answer to! > > yes, sure, and I would prefere: > > > unknown format > That's fine. Cheers, Jason -- Jason Wood Homepage : www.uchian.pwp.blueyonder.co.uk
[Kdenlive-devel] Does Kdenlive build? (preparing for a V0.1.1 tarball)
Hi Jason, could you look into that? I don't understand why that is happening: On Sunday 12 January 2003 03:08 pm, Chris Clayton wrote: > piave_base.cc:129 INFO: Setting up project for PAL system > piave_base.cc:163 INFO: Setup preview mode > server.cc:151 INFO: initListenSocket > server.cc:178 INFO: Listening on port 6100 > server.cc:118 INFO: Got connection on socket 14 > server.cc:184 INFO: Stopp listening for connections > kdenserver.cc:377 INFO: starting main server loop Up to here everything is ok, but then > server.cc:229 INFO: Connection closed by client piave receives a connection closed by kdenlive Any idea why? > server.cc:238 INFO: > receive message start > server.cc:239 INFO: > > server.cc:240 INFO: > receive message stop > kdenserver.cc:312 INFO: stop listen thread > kdenserver.cc:328 INFO: starting process thread > kdenserver.cc:364 INFO: stop process thread > server.cc:194 INFO: Close communication socket > server.cc Cheers, Rolf *** Rolf Dubitzky e-mail: Rolf.Dubitzky at Physik.TU-Dresden.de s-mail see http://hep.phy.tu-dresden.de/~dubitzky/ ***
[Kdenlive-devel] Does Kdenlive build? (preparing for a V0.1.1 tarball)
Hmm.. that means, that piave is sopping imediately doesn't get a single command. I'll look into it. In themeantime, could you try to start piave in a seperate xterm: /usr/local/bin/piave -d and then in the other xtern kdenlive? Cheers, Rolf On Sunday 12 January 2003 03:08 pm, Chris Clayton wrote: > Rolf, > > I've got your clip now, thamks for that. > > But I still get no playback. This is what I see: > > Filename: 4x3-PAL.dv > Type: n/a > Duration: unknown > Usage Count: 0 > Size: 6.9M > > and in the debug tab: > > piave_base.cc:129 INFO: Setting up project for PAL system > piave_base.cc:163 INFO: Setup preview mode > server.cc:151 INFO: initListenSocket > server.cc:178 INFO: Listening on port 6100 > server.cc:118 INFO: Got connection on socket 14 > server.cc:184 INFO: Stopp listening for connections > kdenserver.cc:377 INFO: starting main server loop > server.cc:229 INFO: Connection closed by client > server.cc:238 INFO: > receive message start > server.cc:239 INFO: > > server.cc:240 INFO: > receive message stop > kdenserver.cc:312 INFO: stop listen thread > kdenserver.cc:328 INFO: starting process thread > kdenserver.cc:364 INFO: stop process thread > server.cc:194 INFO: Close communication socket > server.cc > > 74 > WARNING: > atexit handler: > > > As before, feel free to ask for any other information. > > Cheers > > Chris > > > --- > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld ?omething 2 See! > http://www.vasoftware.com > ___ > Kdenlive-devel mailing list > Kdenlive-devel at lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/kdenlive-devel -- Cheers, Rolf *** Rolf Dubitzky e-mail: Rolf.Dubitzky at Physik.TU-Dresden.de s-mail see http://hep.phy.tu-dresden.de/~dubitzky/ ***
[Kdenlive-devel] Does Kdenlive build? (preparing for a V0.1.1 tarball)
On Sunday 12 Jan 2003 3:02 pm, Rolf Dubitzky wrote: > On Sunday 12 January 2003 04:01 pm, Jason Wood wrote: > > And 4, dissallow the adding of clips to the project list which cannot be > > used with the current project settings. > > right. > > > Incidentally, this reminds me of a bug in piave : if you try to get the > > fileProperties of a non-dv clip (for example, a webpage of a .cpp file) > > piave crashes. > > > > I'm not suggesting that piave should try to pass back relevant info about > > such files ;-) but a simple > > > > > > > > or similar would probably make sense. > > Oooopsy! Yes, of course. I'll fix it right now. unfortunately I can't > commit it, since sourceforge cvs seems to be down (again) Erm, should be obvious, but please pass the filename back in the getFileCapabilities command as you normally would, or I won't know which file request I am recieving an answer to! Cheers, Jason -- Jason Wood Homepage : www.uchian.pwp.blueyonder.co.uk
[Kdenlive-devel] Does Kdenlive build? (preparing for a V0.1.1 tarball)
On Sunday 12 Jan 2003 2:50 pm, Chris Clayton wrote: > Rolf, > > Thats changed things a bit but still no playback. > > > Hmm.. that means, that piave is sopping imediately doesn't get a single > > command. I'll look into it. In themeantime, could you try to start piave > > in a seperate xterm: > > > > /usr/local/bin/piave -d > > In kdenlive, I see: > > Filename: 4x3-PAL.dv > Type: n/a > Duration: 00:00:02:00 > Usage Count: 0 > Size: 6.9M > > and in the debug tab: > > piave base.cc:129 INFO: Setting up project for PAL system > piave base.cc:163 INFO: Setup preview mode > server.cc:151 INFO: initListenSocket > server.cc:184 INFO: Stopp listening for connections > server.cc:166 WARNING: Error initialising server > server.cc:140 WARNING: Error accepting connection > server.cc:74 WARNING: atexit handler: If you start piave in a console, the debug window in kdenlive will not show piaves output (the debug info will appear in the console). However, from what I can see, everything is indeed working correctly. Are you dragging the clip from the project list to the timeline before you play it? At the moment, the monitor window only shows you what is on the timeline - yes, this is all to do with the monitor needing proper functionality - I'm on the case, ok? ;-) So try this : With piave open in a console : 1. Add the clip to the project list. 2. Drag the clip from the project list to the timeline - you should get a long pink box. 3. Seek around (drag the ruler marker around the project) - when you move it over the clip, do you get playback? 4. Seek somewhere over the clip and press play - do you get playback? If yes, then everything is ok, otherwise send the debug info of the exepriment. If everything works with piave running ni a console, please try it again without running piave in the console - i.e. just start kdenlive. Do the same, above steps work? Cheers, Jason -- Jason Wood Homepage : www.uchian.pwp.blueyonder.co.uk
[Kdenlive-devel] Does Kdenlive build? (preparing for a V0.1.1 tarball)
On Sunday 12 January 2003 02:47 pm, Jason Wood wrote: > On Sunday 12 Jan 2003 12:04 pm, Rolf Dubitzky wrote: > All of the 25fps references have now vanished, and instead they ask the > document via framesPerSecond() to get the correct framerate. However, this > value is hardcoded to PAL (25 fps) at the moment, it is a bit of work to > fix this properly, because I need to be able to tell piave what framerate > to render to. Well, mixed projects are not an option for the near future. > Exactly how piave handles the conversion of NTSC to PAL and PAL to NTSC is > out of kdenlive's hands. Having pure PAL _or_ NTSC projects maybe not too difficult. conversion will take while. > However, if we want to prevent this from happening > (i.e. tell kdenlive not to allow clips of different frame rates) we need to > choose a paramter to the call in the area I > hinted at when we were talking about transitions. It would say something > like : > > > > > > > > Or to put it another way, handling NTSC, whilst it should not be difficult, > is quite a bit of work, which overlaps with the "file format support" quite > a lot. Yes, you are right. But let's try to make un-mixed projects work. I think that is possible, don't you? Actually it will take me a while to implement it propperly, because NTSC has an aspect ratio different from a typical screen. with PAL I don't have to worry about that, but NTSC must be scaled to look right on a computer screen. For YUV_overlay that's easy, but.. well, let's see... I'll commit a patch in a minute that will send for NTSC something like: and for a PAL clip: Cheers, Rolf *** Rolf Dubitzky e-mail: Rolf.Dubitzky at Physik.TU-Dresden.de s-mail see http://hep.phy.tu-dresden.de/~dubitzky/ ***
[Kdenlive-devel] Does Kdenlive build? (preparing for a V0.1.1 tarball)
On Sunday 12 Jan 2003 2:42 pm, Rolf Dubitzky wrote: > On Sunday 12 January 2003 03:29 pm, Jason Wood wrote: > > On Sunday 12 Jan 2003 2:03 pm, Rolf Dubitzky wrote: > > > On Sunday 12 January 2003 02:47 pm, Jason Wood wrote: > > > > On Sunday 12 Jan 2003 12:04 pm, Rolf Dubitzky wrote: > > > > I can handle that, but it is the simple bit :-) > > > > To add things properly to kdenlive (i.e., not as a hack), I need to be > > able to > > > > > > 1. Determine which file formats piave can export to. > > Ok, I see, once I implement I will add that. > > > 2. Add a dialog to ask the user which of those formats he wishes to work > > in. 3. Setup the timeline and project accordingly (this is quick and > > easy) And I just rememberd what number four is :-) And 4, dissallow the adding of clips to the project list which cannot be used with the current project settings. Incidentally, this reminds me of a bug in piave : if you try to get the fileProperties of a non-dv clip (for example, a webpage of a .cpp file) piave crashes. I'm not suggesting that piave should try to pass back relevant info about such files ;-) but a simple or similar would probably make sense. Cheers, Jason -- Jason Wood Homepage : www.uchian.pwp.blueyonder.co.uk
[Kdenlive-devel] Does Kdenlive build? (preparing for a V0.1.1 tarball)
On Sunday 12 Jan 2003 2:21 pm, Rolf Dubitzky wrote: > Hi Jason, > > could you look into that? I don't understand why that is happening: > > On Sunday 12 January 2003 03:08 pm, Chris Clayton wrote: > > piave_base.cc:129 INFO: Setting up project for PAL system > > piave_base.cc:163 INFO: Setup preview mode > > server.cc:151 INFO: initListenSocket > > server.cc:178 INFO: Listening on port 6100 > > server.cc:118 INFO: Got connection on socket 14 > > server.cc:184 INFO: Stopp listening for connections > > kdenserver.cc:377 INFO: starting main server loop > > Up to here everything is ok, but then > > > server.cc:229 INFO: Connection closed by client > > piave receives a connection closed by kdenlive Any idea why? Hmm, I think I might have seen this bug manifest myself, but in my case kdenlive always restarts piave again straight afterwards (you see the green LED flash on,off,on), so I didn't pay it too much thought. Chris, could you run piave in a seperate console : piave -d Then start kdenlive, and let me know if it still closes? Cheers, Jason -- Jason Wood Homepage : www.uchian.pwp.blueyonder.co.uk
[Kdenlive-devel] Does Kdenlive build? (preparing for a V0.1.1 tarball)
Rolf, Thats changed things a bit but still no playback. > Hmm.. that means, that piave is sopping imediately doesn't get a single > command. I'll look into it. In themeantime, could you try to start piave in > a seperate xterm: > > /usr/local/bin/piave -d > In kdenlive, I see: Filename: 4x3-PAL.dv Type: n/a Duration: 00:00:02:00 Usage Count: 0 Size: 6.9M and in the debug tab: piave_base.cc:129 INFO: Setting up project for PAL system piave_base.cc:163 INFO: Setup preview mode server.cc:151 INFO: initListenSocket server.cc:184 INFO: Stopp listening for connections server.cc:166 WARNING: Error initialising server server.cc:140 WARNING: Error accepting connection server.cc:74 WARNING: atexit handler: in the xterm from which piave started I see: Peanut:~$ /usr/local/bin/piave -d piave_base.cc:129 INFO: Setting up project for PAL system piave_base.cc:163 INFO: Setup preview mode server.cc:151 INFO: initListenSocket server.cc:178 INFO: Listening on port 6100 server.cc:118 INFO: Got connection on socket 4 server.cc:184 INFO: Stopp listening for connections kdenserver.cc:377 INFO: starting main server loop kdenserver.cc:328 INFO: starting process thread server.cc:238 INFO: > receive message start server.cc:239 INFO: server.cc:240 INFO: > receive message stop kdenserver.cc:268 INFO: Recieved VEML command getCapabilites kdenserver.cc:272 WARNING: unknown command "getCapabilites" kdenserver.cc:268 INFO: Recieved VEML command createVideoXWindow outsdlstream.cc:64 INFO: Initializing SDL outsdlstream.cc:75 INFO: setting SDL video mode outsdlstream.cc:87 INFO: detected bpp=16 outsdlstream.cc:106 INFO: Got SDL overlay outsdlstream.cc:108 INFO: Got SDL hardware overlay outsdlstream.cc:109 INFO: _overlay->planes=1 outsdlstream.cc:110 INFO: _overlay->pitches[0]=1440 outsdlstream.cc:111 INFO: _overlay->w=720 _overlay->h=576 outsdlstream.cc:113 INFO: lock overlay ok outsdlstream.cc:135 INFO: Using SDL YUV overlay _SDL_init_OK=1 kdenserver.cc:425 WARNING: window not resizable server.cc:213 INFO: << sending message start server.cc:214 INFO: server.cc:215 INFO: << sending message stop kdenserver.cc:97 INFO: waiting for dropQueue >notempty< server.cc:238 INFO: > receive message start server.cc:239 INFO: server.cc:240 INFO: > receive message stop kdenserver.cc:268 INFO: Recieved VEML command getFileProperties avstream.cc:110 INFO: Init InRawDVStream avstream.cc:122 INFO: opened file "/home/chris/4x3-PAL.dv" with 50 frames. frame.cc:833 INFO: allocating new DVFrame avstream.cc:144 INFO: video: avstream.cc:145 INFO: system : PAL avstream.cc:146 INFO: format : 4:3 avstream.cc:150 INFO: audio: avstream.cc:151 INFO: frequency : 32000 avstream.cc:152 INFO: num_channels : 2 avstream.cc:153 INFO: quantization : 12 avstream.cc:154 INFO: emphasis : off avstream.cc:155 INFO: sampling : 2 server.cc:213 INFO: << sending message start server.cc:214 INFO: server.cc:215 INFO: << sending message stop kdenserver.cc:97 INFO: waiting for dropQueue >notempty< If I try to start playback, I see nothing but the following gets added to the xterm: server.cc:238 INFO: > receive message start server.cc:239 INFO: server.cc:240 INFO: > receive message stop kdenserver.cc:268 INFO: Recieved VEML command setSceneList VEML.cc:81 INFO: add daughter (*cmndListIter)->name()=scenelist kdenserver.cc:268 INFO: Recieved VEML command play kdenserver.cc:608 INFO: setSceneList start setSceneList type: standard queue attributes: none scenelist type: standard queue attributes: none kdenserver.cc:661 INFO: new HEAD >>> StoryMNode: start 0 length 0 storybase.cc:536 INFO: setting HEAD with length=0 kdenserver.cc:665 INFO: new HEAD <<< server.cc:213 INFO: << sending message start server.cc:214 INFO: server.cc:215 INFO: << sending message stop server.cc:213 INFO: << sending message start server.cc:214 INFO: server.cc:215 INFO: << sending message stop server.cc:213 INFO: << sending message start server.cc:214 INFO: server.cc:215 INFO: << sending message stop frame.cc:224 INFO: Global::render_width=720 Global::render_height=576 frame.cc:228 INFO: (_pixbuf): got pixbuf withAlpha=0 server.cc:213 INFO: << sending message start server.cc:214 INFO: server.cc:215 INFO: << sending message stop server.cc:213 INFO: << sending message start server.cc:214 INFO: server.cc:215 INFO: << sending message stop server.cc:213 INFO: << sending message start server.cc:214 INFO: server.cc:215 INFO: << sending message stop server.cc:213 INFO: << sending message start server.cc:214 INFO: server.cc:215 INFO: << sending message stop server.cc:213 INFO: << sending message start server.cc:214 INFO: server.cc:215 INFO: << sending message stop server
[Kdenlive-devel] Does Kdenlive build? (preparing for a V0.1.1 tarball)
On Sunday 12 Jan 2003 2:03 pm, Rolf Dubitzky wrote: > On Sunday 12 January 2003 02:47 pm, Jason Wood wrote: > > On Sunday 12 Jan 2003 12:04 pm, Rolf Dubitzky wrote: > > > > All of the 25fps references have now vanished, and instead they ask the > > document via framesPerSecond() to get the correct framerate. However, > > this value is hardcoded to PAL (25 fps) at the moment, it is a bit of > > work to fix this properly, because I need to be able to tell piave what > > framerate to render to. > > Well, mixed projects are not an option for the near future. > > > Exactly how piave handles the conversion of NTSC to PAL and PAL to NTSC > > is out of kdenlive's hands. > > Having pure PAL _or_ NTSC projects maybe not too difficult. conversion will > take while. > > > However, if we want to prevent this from happening > > (i.e. tell kdenlive not to allow clips of different frame rates) we need > > to choose a paramter to the call in the > > area I hinted at when we were talking about transitions. It would say > > something like : > > > > > > > > > > > > > > > > Or to put it another way, handling NTSC, whilst it should not be > > difficult, is quite a bit of work, which overlaps with the "file format > > support" quite a lot. > > Yes, you are right. But let's try to make un-mixed projects work. I think > that is possible, don't you? Actually it will take me a while to implement > it propperly, because NTSC has an aspect ratio different from a typical > screen. with PAL I don't have to worry about that, but NTSC must be scaled > to look right on a computer screen. For YUV_overlay that's easy, but.. > well, let's see... > > I'll commit a patch in a minute that will send for NTSC something like: I can handle that, but it is the simple bit :-) To add things properly to kdenlive (i.e., not as a hack), I need to be able to : 1. Determine which file formats piave can export to. 2. Add a dialog to ask the user which of those formats he wishes to work in. 3. Setup the timeline and project accordingly (this is quick and easy) By the time stages 1 and 2 are done though, we are very close to having specified input file formats as well, and it will be very easy to add e.g. picture (png, jpg) support in kdenlive. This gives an idea as to the general nature of the code that needs to be implemented - a quick hack for NTSC isn't going to achieve much. If piave can handle inacurate frame reading (e.g. being sent from the timeline at 25 fps when piave is rendering at 30fps) then I think we should leave it at that for now if we want to release a beta, or put off the beta release until we have done things properly. In case you read me wrong, the file format you will be passing in getFileCapabilities is what it should be passing, not a hack - but to quickly add NTSC support properly would be a hack if we disregard the handling of all other file formats. Cheers, Jason -- Jason Wood Homepage : www.uchian.pwp.blueyonder.co.uk
[Kdenlive-devel] Does Kdenlive build? (preparing for a V0.1.1 tarball)
Rolf, I've got your clip now, thamks for that. But I still get no playback. This is what I see: Filename: 4x3-PAL.dv Type: n/a Duration: unknown Usage Count: 0 Size: 6.9M and in the debug tab: piave_base.cc:129 INFO: Setting up project for PAL system piave_base.cc:163 INFO: Setup preview mode server.cc:151 INFO: initListenSocket server.cc:178 INFO: Listening on port 6100 server.cc:118 INFO: Got connection on socket 14 server.cc:184 INFO: Stopp listening for connections kdenserver.cc:377 INFO: starting main server loop server.cc:229 INFO: Connection closed by client server.cc:238 INFO: > receive message start server.cc:239 INFO: server.cc:240 INFO: > receive message stop kdenserver.cc:312 INFO: stop listen thread kdenserver.cc:328 INFO: starting process thread kdenserver.cc:364 INFO: stop process thread server.cc:194 INFO: Close communication socket server.cc : 74 WARNING: atexit handler: As before, feel free to ask for any other information. Cheers Chris
[Kdenlive-devel] Does Kdenlive build? (preparing for a V0.1.1 tarball)
On Sunday 12 Jan 2003 1:47 pm, Jason Wood wrote: > Assuming that I get passed the frame rate in getFrameProperties, kdenlive > will be able to specify the correctly length for the NTSC clip. That should have said, getFileProperties Cheers, Jason -- Jason Wood Homepage : www.uchian.pwp.blueyonder.co.uk
[Kdenlive-devel] Does Kdenlive build? (preparing for a V0.1.1 tarball)
On Sunday 12 Jan 2003 12:04 pm, Rolf Dubitzky wrote: > On Sunday 12 January 2003 12:58 pm, Rolf Dubitzky wrote: > > On Sunday 12 January 2003 08:22 am, Chris Clayton wrote: > > the file you tried is NTSC. In principle supporting NTSC is not a big > > deal, > > Err, well, when I said that, I was thinking of piave only. I don't know how > many hardcoded 25fps are in kdenlive. Since piave does not even report back > the format of the clip, even if kdenlive could handle NTSC, it wouldn't > know about it. And also, as NTSC fps is not as easy to convert from > milliseconds to integer we might see more rounding errors. > > I guess NTSC is something we should really fix before beta 1. Assuming that I get passed the frame rate in getFrameProperties, kdenlive will be able to specify the correctly length for the NTSC clip. All of the 25fps references have now vanished, and instead they ask the document via framesPerSecond() to get the correct framerate. However, this value is hardcoded to PAL (25 fps) at the moment, it is a bit of work to fix this properly, because I need to be able to tell piave what framerate to render to. Exactly how piave handles the conversion of NTSC to PAL and PAL to NTSC is out of kdenlive's hands. However, if we want to prevent this from happening (i.e. tell kdenlive not to allow clips of different frame rates) we need to choose a paramter to the call in the area I hinted at when we were talking about transitions. It would say something like : Or to put it another way, handling NTSC, whilst it should not be difficult, is quite a bit of work, which overlaps with the "file format support" quite a lot. Cheers, Jason -- Jason Wood Homepage : www.uchian.pwp.blueyonder.co.uk
[Kdenlive-devel] Does Kdenlive build? (preparing for a V0.1.1 tarball)
On Sunday 12 January 2003 11:58 am, Rolf Dubitzky wrote: > the file you tried is NTSC. Ok, sorry about that. > you can download a PAL sample here: > > http://www.dubitzky.de/piave/4x3-PAL.dv I'll download that, give it a try and report back. Cheers, Chris
[Kdenlive-devel] Does Kdenlive build? (preparing for a V0.1.1 tarball)
On Sunday 12 January 2003 12:58 pm, Rolf Dubitzky wrote: > On Sunday 12 January 2003 08:22 am, Chris Clayton wrote: > the file you tried is NTSC. In principle supporting NTSC is not a big deal, Err, well, when I said that, I was thinking of piave only. I don't know how many hardcoded 25fps are in kdenlive. Since piave does not even report back the format of the clip, even if kdenlive could handle NTSC, it wouldn't know about it. And also, as NTSC fps is not as easy to convert from milliseconds to integer we might see more rounding errors. I guess NTSC is something we should really fix before beta 1. Cheers, Rolf *** Rolf Dubitzky e-mail: Rolf.Dubitzky at Physik.TU-Dresden.de s-mail see http://hep.phy.tu-dresden.de/~dubitzky/ ***
[Kdenlive-devel] Does Kdenlive build? (preparing for a V0.1.1 tarball)
On Sunday 12 January 2003 08:22 am, Chris Clayton wrote: > Jason, > > > To Reinhard, Chris and anyone else on the list who has tried, could you > > tell me if kdenlive from current CVS builds successfully on your system? > > I get a clean build of both piave and kdenlive but I am not getting > playback. > > I don't yet have any clips of my own - I am slowly building up the business > case for dv camera with my wife. The clip I am using is 4x3.dv from the > kino download page at sourceforge, so I am assuming I have the suitable dv > file. Hi Chris, the file you tried is NTSC. In principle supporting NTSC is not a big deal, but as I only have a PAL DV camera it's a little bit hard to test for me and you probably hit a bug. Just to check is everything else is working, you can download a PAL sample here: http://www.dubitzky.de/piave/4x3-PAL.dv I'll try and see what I can do for NTSC. The sample from kino is only three frames long, does anybody happen to have a longer NTSC sample? Cheers, Rolf *** Rolf Dubitzky e-mail: Rolf.Dubitzky at Physik.TU-Dresden.de s-mail see http://hep.phy.tu-dresden.de/~dubitzky/ ***
[Kdenlive-devel] Does Kdenlive build? (preparing for a V0.1.1 tarball)
Jason, > To Reinhard, Chris and anyone else on the list who has tried, could you > tell me if kdenlive from current CVS builds successfully on your system? I get a clean build of both piave and kdenlive but I am not getting playback. I don't yet have any clips of my own - I am slowly building up the business case for dv camera with my wife. The clip I am using is 4x3.dv from the kino download page at sourceforge, so I am assuming I have the suitable dv file. What I see is: Filename: 4x3.dv Type: n/a Duration: unknown Usage Count: 0 Size: 235Kb On the debug tab I see: piave_base.cc:129 INFO: Setting up project for PAL system piave_base.cc:163 INFO: Setup preview mode server.cc:151 INFO: initListenSocket server.cc:178 INFO: Listening on port 6100 server.cc:118 INFO: Got connection on socket 14 server.cc:184 INFO: Stopp listening for connections kdenserver.cc:377 INFO: starting main server loop server.cc:74 WARNING: atexit handler: server.cc:229 INFO: Connection closed by client server.cc:238 INFO: > receive message start server.cc:239 INFO: server.cc:240 INFO: > receive message stop kdenserver.cc:312 INFO: stop listen thread kdenserver.cc:328 INFO: starting process thread kdenserver.cc:364 INFO: stop process thread server.cc:194 INFO: Close communication socket Sorry guys! Please feel completely free to ask for additional information although, I have a few other things to do today, so answers may take a few hours. Chris
[Kdenlive-devel] Does Kdenlive build? (preparing for a V0.1.1 tarball)
Hi, piave and kdenlive builds trouble-free! Also play back works very good. greetings Reinhard Am Samstag 11 Januar 2003 08:51 nachmittags/abends schrieb Jason Wood: > Hi, > > To Reinhard, Chris and anyone else on the list who has tried, could you > tell me if kdenlive from current CVS builds successfully on your system? I > am preparing to upload a tarball to match the piave tarball that Rolf > recently announced. > > Like Rolf, I have started using sourceforge's bug trackers and feature > request systems, which can be found on the project page : > > http://www.sourceforge.net/projects/kdenlive > > As far as I am aware, there are no "showstoppers" (i.e. bugs which cause > kdenlive to crash, or which stop it from working adequately). However, > there are a number of usability issues left to be fixed, the more critical > of which I have listed as bugs (yes, very subjective as to when a user > interface problem is a bug or not, I know) > > Assuming that I don't hear about any problems, I will upload a kdenlive > tarball sometime tommorrow. > > Cheers, > Jason
[Kdenlive-devel] Does Kdenlive build? (preparing for a V0.1.1 tarball)
Hi, To Reinhard, Chris and anyone else on the list who has tried, could you tell me if kdenlive from current CVS builds successfully on your system? I am preparing to upload a tarball to match the piave tarball that Rolf recently announced. Like Rolf, I have started using sourceforge's bug trackers and feature request systems, which can be found on the project page : http://www.sourceforge.net/projects/kdenlive As far as I am aware, there are no "showstoppers" (i.e. bugs which cause kdenlive to crash, or which stop it from working adequately). However, there are a number of usability issues left to be fixed, the more critical of which I have listed as bugs (yes, very subjective as to when a user interface problem is a bug or not, I know) Assuming that I don't hear about any problems, I will upload a kdenlive tarball sometime tommorrow. Cheers, Jason -- Jason Wood Homepage : www.uchian.pwp.blueyonder.co.uk
