Re: [CinCV] Is it possible to get my own repo?
Hi. I have uploaded all done so far to git repo einar. I created README describing status of this branch. Einar ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCV] Is it possible to get my own repo?
On Wed, Mar 3, 2010 at 4:09 PM, p...@ichthyostega.de wrote: > Thus, I think the foremost question is: is your intention just to fix the > existing code base at places, or do you intend to re-work it for real > improvement, thus moving away from the way "upstream" handles things? > I think it is impossible get real improvement and keep at the same time codebase close to upstream. I think that I am already too far away with the locking patch. My first goal is to stabilize Cinelerra (no crashes, no hangups), speed things up a bit, improve bit GUI (there are glitches, alogics). Some internals may need rewrite. Cleanup of sources. Afterwards IT is possible to look at features and decide what to do with them. For example: must a NLE editor support various intput devices? Of course it will then be possible to add new features. Einar ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCV] Is it possible to get my own repo?
Hi ct, Einar asap you decided i'm ready to test... the cin vesion i normally use is the last from community git and it uses to be the more stable, comparating with packaging people have in their machines and comparating with las heroinewarrior (which i use as well) Thx bugs hunters and mergers, as usual for (tons of) works (and patience)... baci vale Einar Rünkaru wrote: Hi. I think that I have managed to fix Cinelerra-2.1CV locking problem. It seems fix for bugzilla bugs 278, 383, 406, 414, 493, 519 - may be some more, some may be irrelevant. Fix is huge and tested on couple laptops with 32bit distributions. Obviously it needs more testing on different hardware/distibutions. During debugging I found and fixed addittional bugs: - subtitle decoding in libmpeg3 - added defaults into libmpeg3 for subtitle color - index generation in libmpeg3 - edit_font_color initialization of S.U.V - more info in assert info window - removed BC_Windowevents (now 7 threads less) - fix of bug 524 - fixed copiler warnings of some plugins - fixed timebar cursor updating of viewer and compositor - trace subsystem was rewritten to static buffers, added backtrace dump on crash - lots of cleanups Important change behaviour: composer and viewer always display the frame starting at the time shown on clock. Frame displayed does not depend on forward/backward direction. There was inconsistency when direction was accounted when not (mask). I intend to continue bug-hunting. Work done so far may be useful for somebody. Great work :) My question is: Is it possible to get my own repo? Of course, visit us on IRC, send your ssh-pubkey. You can also (meanwhile) use the Mob repository which is public pushable through git:// protocoll, just create your own branch there. Christian Einar Rünkaru ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra This message was sent using IMP, the Internet Messaging Program. ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCV] Is it possible to get my own repo?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 p...@ichthyostega.de wrote: > Einar Rünkaru schrieb: >> Important change behaviour: composer and viewer always display the frame >> starting at the time shown on clock. Frame displayed does not depend on >> forward/backward direction. There was inconsistency when direction was >> accounted when not (mask). >> >> I intend to continue bug-hunting. Work done so far may be useful for >> somebody. > > Hellor Einar, > > welcome in the club of cinelerra bug hunters ;-) > > The issue described above is one of the most annoying "strange design > decisions" in Cinelerra. Probably a lot of people (including myself) would > welcome just to phase it out. This is true and may solve a basical problem of cin's usability > Some years ago I worked on a larger patch to remove the greatest obstacles > and strangenesses on the bezier automation curve handlings. This patch is > not accepted into Cin-CV until today. One of the reasons is that I too tried > to partially rectify these and some similar problems with dragging nodes in > the > trackcanvas (GUI). > Would be great to merge your work (for 64 bit) with Einar's one; after doing that cinelerra cv would get a big step forward in usability for extended production > > Meanwhile the situation might be different, inasmuch develompment on the > community version of Cinelerra is mostly stalled, I don't think this is still true by now, as long as I've been teaching for 2 years cinelerra cv (2.1), and I think that most people on this ml still consider that version of cinelerra as the stable version. > > And how to we all (Cinelerra community) judge the situation? Do we still > intend to merge in what upstream provides, or would we be willing to stick > to the Cin-2.1 codebase and in turn accept more disruptive changes? > I consider the second option as the more usefull by now, in order to keep the value of the community work; and I agree that the bezier patch sould be merged with the whole 2.1 codebase as long as the Einar's changes after a short testing on other supported architectures. In order to test Einar's code I'd like him to put it into a pubblic repo. My 2 cents jilt -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkuPjRcACgkQNom9shKmKsoGNwCeOpkpqVWiluaRFLxzRm7d880Y BtcAoIokzOKe72lHaM7oV4wauGoReBxM =HNyQ -END PGP SIGNATURE- ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCV] Is it possible to get my own repo?
Einar Rünkaru schrieb: > Important change behaviour: composer and viewer always display the frame > starting at the time shown on clock. Frame displayed does not depend on > forward/backward direction. There was inconsistency when direction was > accounted when not (mask). > > I intend to continue bug-hunting. Work done so far may be useful for > somebody. Hellor Einar, welcome in the club of cinelerra bug hunters ;-) The issue described above is one of the most annoying "strange design decisions" in Cinelerra. Probably a lot of people (including myself) would welcome just to phase it out. Anyway, the greatest problem with this seems to be "mergeability" with upstream. The whole source base is littered with these "if (play_forward) ... else ..."-constructs and the off by one offset is handled manually at dozens of locations. Some years ago I worked on a larger patch to remove the greatest obstacles and strangenesses on the bezier automation curve handlings. This patch is not accepted into Cin-CV until today. One of the reasons is that I too tried to partially rectify these and some similar problems with dragging nodes in the trackcanvas (GUI). At that time, the folks involved into cinelerra development since a long time pointed out, that, as "upstream" can't be counted upon when it comes to accepting changes, any change has to be done such as not to hinder merging in new source versions from upstream. Meanwhile the situation might be different, inasmuch develompment on the community version of Cinelerra is mostly stalled, due to lack of developers. Cinelerra 4 is out since a long time and we didn't even manage to perform the merge into CV. Thus, I think the foremost question is: is your intention just to fix the existing code base at places, or do you intend to re-work it for real improvement, thus moving away from the way "upstream" handles things? And how to we all (Cinelerra community) judge the situation? Do we still intend to merge in what upstream provides, or would we be willing to stick to the Cin-2.1 codebase and in turn accept more disruptive changes? Cheers Hermannn Voßeler (aka "Ichthyo") ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCV] Is it possible to get my own repo?
Einar Rünkaru wrote: > Hi. > > I think that I have managed to fix Cinelerra-2.1CV locking problem. > It seems fix for bugzilla bugs 278, 383, 406, 414, 493, 519 - may be > some more, some may be irrelevant. > > Fix is huge and tested on couple laptops with 32bit distributions. > Obviously it needs more testing on different hardware/distibutions. > > During debugging I found and fixed addittional bugs: > - subtitle decoding in libmpeg3 > - added defaults into libmpeg3 for subtitle color > - index generation in libmpeg3 > - edit_font_color initialization of S.U.V > - more info in assert info window > - removed BC_Windowevents (now 7 threads less) > - fix of bug 524 > - fixed copiler warnings of some plugins > - fixed timebar cursor updating of viewer and compositor > - trace subsystem was rewritten to static buffers, added backtrace > dump on crash > - lots of cleanups > > Important change behaviour: composer and viewer always display the frame > starting at the time shown on clock. Frame displayed does not depend on > forward/backward direction. There was inconsistency when direction was > accounted when not (mask). > > I intend to continue bug-hunting. Work done so far may be useful for somebody. Great work :) > > My question is: Is it possible to get my own repo? Of course, visit us on IRC, send your ssh-pubkey. You can also (meanwhile) use the Mob repository which is public pushable through git:// protocoll, just create your own branch there. Christian > > Einar Rünkaru > > ___ > Cinelerra mailing list > Cinelerra@skolelinux.no > https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra