[CinCVS] fixing cinelerra, using standard C++ libs etc.
Finally I found some time to look at some cinelerra bugs. Cinelerra use quite some own things (which is natural since the cinelerra codebase predates the C++ standard). I believe the code complexity could be lowered by replacing some things with standard or defacto-standard libs rather fixing the problems in cinelerra's ad-hoc implementations. I give it a try and start using the C++ stdlib and few sane parts of boost. I'll just try the next few days to get something fixed and then we'll see how it turns out. But I would like to hear opinions from the other developers which parts of cinelerra should be improved this way. I am fully aware that this can lead to a big intrusive change. But making cinelerra easier to maintain and more stable is really worth the efforts imo. Some short list where I am working on: Remove the Garbage collector in favor of boost::shared_ptr, the GC has some nasty bugs, partially together with threads. By replacing ALL Asset* with boost::shared_ptr these should be fixed on expanse of some performance. Manage Assets in std::vector / std::list. When this works then refactor some uses of the shared_ptr to using references instead, this will regain most of the performance loss from above. When still not fscked up, then refactor the arrays/lists to hold normal pointers (or boost::ptr_vector/ptr_list) with clear ownership semantic. Maybe add some debugging allocator which tracks per-thread ownership of objects, aiding in finding complicated bugs. Maybe apply the above steps to other classes (File, EDL, etc...). Maybe add some pooled allocator which could improve performance even more. Christian ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] keyboard question
lol.. yes i agree.. but the thing is that most other editing systems have standared keyboard setting that i have more than memorized.. and with cinelerra i find myself having to re-learn the shortcuts. so what i wanted to do was find a way to import the avid standared into cinelerra... and trust i have trying to push cinelerra in madrid, and will now start offering a video workshop that uses cinelerra as its editng system.. butone of the things that makes people a bit weary of using the program is that the keyboard shortcuts arnt the same as the other programas editors are acstumed to work with. i think that if this problem gets resolved it would break the ice to get a lot of "profesionales" to make the switch. 2007/3/6, Marcin Kostur <[EMAIL PROTECTED]>: Learn defaults! My 3 cents: Few years ago i always was changing default to my custom key-setting on everything (emacs binding in firefox etc). It was really a hassle, at each new installation or at each foregin system i had to work i did a bunch of mistakes. With cinelerra - i did not like mouse button -setting and i changed them. Then It went 1.2->2.0, few version and i never knew what i set up. Now i alway (really always) learn "default" setting for any system (inc. cin. mouse). I have no problem using emacs kayboard, and few minutes later "windows copy/paste" in thunderbird. Usually defaults are not that bad and i am "upgrade" ready, what is bleeding edge era is quite important ;-) the best Marcin ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] keyboard question
Hey I suggested only my opinion to shortcuts problem in XXI. I think the cinelerra has little chances without working under windows. Unfortunately. The best Marcin ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCVS] Cinelerra sound system?
Hello. I was looking into writing support for the JACK sound system in CinelerraCVS. This is for me or for the whole community (if I'll ever get it working). I did find a message that said it's possible to use oss2jack, I havent't tried that, but off cause it would be nicer to have a native system. I couldn't quite figure out the sound architecture Cinelerra uses, the code isn't really documented that well! So I was hopeing some one could explain it to me. At a glance it seems that Cinelerra just creates desired audio class (ALSA, ESD etc.) (Where is this done?) and then probably writes in some buffer. This might cause problems with JACK though (callback architecture). But any way, hoping for some help. -Markku ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] keyboard question
On Wed, 7 Mar 2007, Marcin Kostur wrote: > I think the cinelerra has little chances without working under > windows. Unfortunately. It's doing pretty well already, for a package that doesn't work under Linux either... -- Matthew Skala [EMAIL PROTECTED]Embrace and defend. http://ansuz.sooke.bc.ca/ ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] fixing cinelerra, using standard C++ libs etc.
Am Mittwoch, den 07.03.2007, 10:20 +0100 schrieb Christian Thaeter: Finally I found some time to look at some cinelerra bugs. Cinelerra use > quite some own things.. > I believe the code complexity could be lowered by replacing some > things with standard or defacto-standard libs rather fixing the problems ... Hello Christian, I am much in favour of the cleanups you propose, indeed, many aspects of cinelerra source are hard to work with... but, as I see it, the main problem is: will such changes be accepted "upstream"?? If not, we will end up with a de-facto code fork. (I state this without intending any pun or hostility). /If/ we wanted a completely forked "Community-Cinelerra", we would need much more dev manpower Cheers, Hermann ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] fixing cinelerra, using standard C++ libs etc.
[EMAIL PROTECTED] wrote: > Am Mittwoch, den 07.03.2007, 10:20 +0100 schrieb Christian Thaeter: > Finally I found some time to look at some cinelerra bugs. Cinelerra use >> quite some own things.. > >> I believe the code complexity could be lowered by replacing some >> things with standard or defacto-standard libs rather fixing the problems > ... > > Hello Christian, > > I am much in favour of the cleanups you propose, indeed, many aspects > of cinelerra source are hard to work with... > > but, as I see it, the main problem is: > will such changes be accepted "upstream"?? Who knows :). Maybe Adam likes it and I hope when I/we get this good it has some chance to be accepted by him. Anyways this is Free Software and I use my free rights to fit it to my needs. This is still a personal experiment (first results later, looks promising so far). > If not, we will end up with a de-facto code fork. (I state this without > intending any pun or hostility). /If/ we wanted a completely forked > "Community-Cinelerra", we would need much more dev manpower CinlerraCV is already a de-facto fork, with friendly relations to upstream and kept to be somewhat mergeable (which is a hell of work). I try to keep my branch mergeable with CinelerraCV (Which is much easier to merge for sure). Future will tell how this works. Christian ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] fixing cinelerra, using standard C++ libs etc.
On Wed, 2007-03-07 at 15:26 +0100, [EMAIL PROTECTED] wrote: > Am Mittwoch, den 07.03.2007, 10:20 +0100 schrieb Christian Thaeter: > Finally I found some time to look at some cinelerra bugs. Cinelerra use > > quite some own things.. > > > I believe the code complexity could be lowered by replacing some > > things with standard or defacto-standard libs rather fixing the problems > ... > > Hello Christian, > > I am much in favour of the cleanups you propose, indeed, many aspects > of cinelerra source are hard to work with... > > but, as I see it, the main problem is: > will such changes be accepted "upstream"?? > > If not, we will end up with a de-facto code fork. (I state this without > intending any pun or hostility). /If/ we wanted a completely forked > "Community-Cinelerra", we would need much more dev manpower ...which we will never get unless the codebase gets cleaned up. I think Christians initiative deserves a "can do" attitude from the rest of us. :-) -- Herman Robak ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] SoC 2007
Il giorno mer, 07/03/2007 alle 01.36 +0100, Andraž Tori ha scritto: > On Wed, 2007-03-07 at 01:21 +0100, giskard wrote: > > hello, > > > > it's a long time i don't contribute to cinelerra,but i'm always > > interested in it. > > > > Yesterday i wondered why cinelerra cannot be part of SoC 2007 (SoC as > > in Summer of Code a project sponsored by google) > > Why not, we could... Kiberpipa can be mentoring organisation, and myself > and JohannJohanneses Sixt and maybe someone else as mentors... but the final > decision is on google... > > > I have some ideas, but for most of them i can't be the mentor (maybe for > > all). > > > > 1) write a GUI in gtk2 > > this is wy beyond SoC project > > > 2) re-write cinelerra-cv as a modular program > > I was thinking about smaller scale projects... > > > we have to decide if partecipate or not to SoC 2007. > > i am all for it ok! cool ! i will start reading SoC docs, Johannes (and * project guys) do you are ok? -- ciao, giskard signature.asc Description: Questa è una parte del messaggio firmata digitalmente
Re: [CinCVS] SoC 2007
Il giorno mer, 07/03/2007 alle 01.36 +0100, Andraž Tori ha scritto: > > On Wed, 2007-03-07 at 01:21 +0100, giskard wrote: > > > hello, > > > > > > it's a long time i don't contribute to cinelerra,but i'm always > > > interested in it. > > > > > > Yesterday i wondered why cinelerra cannot be part of SoC 2007 (SoC as > > > in Summer of Code a project sponsored by google) > > > > Why not, we could... Kiberpipa can be mentoring organisation, and myself > > and JohannJohanneses Sixt and maybe someone else as mentors... but the final > > decision is on google... > > > > > I have some ideas, but for most of them i can't be the mentor (maybe for > > > all). > > > > > > 1) write a GUI in gtk2 > > > > this is wy beyond SoC project > > > > > 2) re-write cinelerra-cv as a modular program > > > > I was thinking about smaller scale projects... > > > > > we have to decide if partecipate or not to SoC 2007. > > > > i am all for it > > Am Mittwoch, den 07.03.2007, 17:34 +0100 schrieb giskard: > ok! cool ! > i will start reading SoC docs, Johannes (and * project guys) do you are ok? > > > > Yesterday i wondered why cinelerra cannot be part of SoC 2007 (SoC as > > > in Summer of Code a project sponsored by google) > > > > Why not, we could... Kiberpipa can be mentoring organisation, and myself > > and JohannJohanneses Sixt and maybe someone else as mentors... but the final > > decision is on google... > > > > > I have some ideas, but for most of them i can't be the mentor (maybe for > > > all). Il giorno mer, 07/03/2007 alle 01.36 +0100, Andraž Tori ha scritto: > > I was thinking about smaller scale projects... > > hello Andraž, hello giskard, what's with handling interlaced internally? wouldn't this be a "smaller" project? Somthing along the following lines: - you have e.g. 50i material - you swith the project framerate up from 25fps to 50fps - any 50i clips now "emit" 50 frames per second while doing some clever interpolation - all the rest (all plugins, transistions, masks, keyframes, the whole video pipeline need not be modified) - you render your project immediately into a pipeline with 50fps and handle the re-assembling to the final delivery format externally Cheers, Hermann V. ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
[CinCVS] [DRAFT] SoC 07
hello *, this is the mail that i will send to google SoC administrator :) it needs more work, please modify it when it's necessary :) the deadline is mon 12/03! Q: What is your Organization's Name? A: Cinelerra CV Q: What is your Organization's Homepage? A: http://cv.cinelerra.org Q: Describe your organization. A: This is an unofficial SVN repository and community home page for Cinelerra, the non-linear video editor and compositor for Linux. Why 2 versions of cinelerra? Cinelerra is developed "upstream" by an entity (guy/girl/group) we'll call HV that is a sharing but not a community sort of entity. HV likes to work on its own copy of cinelerra on its own, releasing code on a periodical basis (every 6 months or so). Some developers decided that it would be nice to develop in a community fashion, (public svn access) but did not really want to fork (which is seen as being nasty). Basically we maintain a copy that is fairly similar to the official release, (i.e. we don't do code-tidying patches). But apply our bug fixes, compiler compliance fixes, and enhancements to the svn. We do try to send the patches upstream, (but it sucks having to apply a patch to two systems, but that's life!) Thus the CV has a number of features that the official version does not have. Q: Why is your organization applying to participate in GSoC 2007? What do you hope to gain by participating? A: 1) Interest in Cinelerra 2) More people involved in free video editor 3) improove cinelerra Yes, i need to phrase this in a better way. Q: What license does your project use? A: GPL (i'm wrong?) Q: URL for your ideas page A: i have to setup it, but i need to know if someone want ask (and can mentor) other features. Q: What is the main development mailing list for your organization? A: cinelerra@skolelinux.no Q: Where is the main IRC channel for your organization? A: #cinelerra on freenode Q: What criteria did you use to select these individuals as mentors? Please be as specific as possible. A: Developer of the project and? minmax jsixt could you please help me answer this question ;) thank you Q: Who will your mentors be? Please enter their Google Account address separated by commas. If your organization is accepted we will email each mentor to invite them to take part. (optional) A: mentors can please open an account on gmail. I know there will be a lot of problem with this request..please don't blame me :( Q: What is your plan for dealing with disappearing students? A: kill them all? ;) If the project is started we will try to continue it, if not..no problems. Q: What is your plan for dealing with disappearing mentors? A: This will be a problem, as mentors == main developers ;) Q: What steps will you take to encourage students to interact with your project's community before, during and after the program? A: dunno no idea yet Q: What will you do to ensure that your accepted students stick with the project after GSoC concludes? A: same..no idea yet. -- ciao, giskard signature.asc Description: Questa è una parte del messaggio firmata digitalmente
Re: [CinCVS] [DRAFT] SoC 07
i don't think CinelerraCV is considered an "organization" probably we willh ave to use something like Kiberpipa as cover organization (which we can) or some other formal organization bye andraz On Wed, 2007-03-07 at 18:56 +0100, giskard wrote: > hello *, > > this is the mail that i will send to google SoC administrator :) > > it needs more work, please modify it when it's necessary :) > > the deadline is mon 12/03! > > > Q: What is your Organization's Name? > A: Cinelerra CV > > Q: What is your Organization's Homepage? > A: http://cv.cinelerra.org > > Q: Describe your organization. > A: This is an unofficial SVN repository and community home page for > Cinelerra, the non-linear video editor and compositor for Linux. > Why 2 versions of cinelerra? > Cinelerra is developed "upstream" by an entity (guy/girl/group) we'll > call HV that is a sharing but not a community sort of entity. HV likes > to work on its own copy of cinelerra on its own, releasing code on a > periodical basis (every 6 months or so). > Some developers decided that it would be nice to develop in a community > fashion, (public svn access) but did not really want to fork (which is > seen as being nasty). > Basically we maintain a copy that is fairly similar to the official > release, (i.e. we don't do code-tidying patches). But apply our bug > fixes, compiler compliance fixes, and enhancements to the svn. We do try > to send the patches upstream, (but it sucks having to apply a patch to > two systems, but that's life!) Thus the CV has a number of features that > the official version does not have. > > Q: Why is your organization applying to participate in GSoC 2007? What > do you hope to gain by participating? > A: 1) Interest in Cinelerra >2) More people involved in free video editor >3) improove cinelerra > > Yes, i need to phrase this in a better way. > > Q: What license does your project use? > A: GPL (i'm wrong?) > > Q: URL for your ideas page > A: i have to setup it, but i need to know if someone want ask (and can > mentor) other features. > > Q: What is the main development mailing list for your organization? > A: cinelerra@skolelinux.no > > Q: Where is the main IRC channel for your organization? > A: #cinelerra on freenode > > Q: What criteria did you use to select these individuals as mentors? > Please be as specific as possible. > A: Developer of the project and? minmax jsixt could you please help me > answer this question ;) thank you > > Q: Who will your mentors be? Please enter their Google Account address > separated by commas. If your organization is accepted we will email each > mentor to invite them to take part. (optional) > A: mentors can please open an account on gmail. I know there will be a > lot of problem with this request..please don't blame me :( > > Q: What is your plan for dealing with disappearing students? > A: kill them all? ;) If the project is started we will try to continue > it, if not..no problems. > > Q: What is your plan for dealing with disappearing mentors? > A: This will be a problem, as mentors == main developers ;) > > Q: What steps will you take to encourage students to interact with your > project's community before, during and after the program? > A: dunno no idea yet > > Q: What will you do to ensure that your accepted students stick with the > project after GSoC concludes? > A: same..no idea yet. > > ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] fixing cinelerra, using standard C++ libs etc.
> Remove the Garbage collector in favor of boost::shared_ptr, the GC has > some nasty bugs, partially together with threads. By replacing ALL > Asset* with boost::shared_ptr these should be fixed on expanse of > some performance. > > Manage Assets in std::vector / > std::list. First things done: http://www.pipapo.org/gitweb?p=cinelerra/ct;a=shortlog;h=ct you might pull it with git git clone git://git.pipapo.org/git/cinelerra/ct or git clone git://repo.or.cz/cinelerra_cv/ct.git Valgrind so far was quite pleased with it, but I didn't do a in-depth check yet, some things still use the original Garbage collector and I want to remove them too. Note that I didn't yet hacked the configure.ac to check for boost. I also plan to add my debugging library http://www.pipapo.org/pipawiki/NoBug to make things a little more safe. Christian ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] Trying to record from MiniDV camera.
On Tue, 06 Mar 2007 17:38:46 -0500 Fred Williams <[EMAIL PROTECTED]> wrote: > Hey, if Kino is free S/W, why not just liberate the code and then > match styles and compile? Isn't that what free S/W is all about? I heard on #cinelerra (some time ago) about idea to just provide front-end in Cinelerra for dvgrab which does good job... Sincerely, Gour signature.asc Description: PGP signature
[CinCVS] MJPEG captures not loading correctly
Hello. I was wondering if anyone can use MJPEG captures from a Zoran based capture card with Cinelerra? That is, the files can be opened, but only one field of each frame is processed (and shrunk to the top of the frame) which leaves the bottom half of the frame green. This has been an issue with every version of Cinelerra I've tried. I've also tried both internal and external ffmpeg to see if that makes a difference. It doesn't. Any ideas? Thanks - Peter Bored stiff? Loosen up... Download and play hundreds of games for free on Yahoo! Games. http://games.yahoo.com/games/front ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] fixing cinelerra, using standard C++ libs etc.
Message: 6 From: [EMAIL PROTECTED] To: Subject: Re: [CinCVS] fixing cinelerra, using standard C++ libs etc. Date: Wed, 07 Mar 2007 15:26:19 +0100 Reply-To: cinelerra@skolelinux.no Am Mittwoch, den 07.03.2007, 10:20 +0100 schrieb Christian Thaeter: Finally I found some time to look at some cinelerra bugs. Cinelerra use > quite some own things.. > I believe the code complexity could be lowered by replacing some > things with standard or defacto-standard libs rather fixing the problems ... Hello Christian, I am much in favour of the cleanups you propose, indeed, many aspects of cinelerra source are hard to work with... but, as I see it, the main problem is: will such changes be accepted "upstream"?? If not, we will end up with a de-facto code fork. (I state this without intending any pun or hostility). /If/ we wanted a completely forked "Community-Cinelerra", we would need much more dev manpower Cheers, Hermann Hey all, First off, apologies if I am replying to this incorrectly - I usually read mailing lists, rarely post. I thought Hermann's comment about dev manpower was worth me coming out of my shell. I work as tech support at a film department in an University of fine art. I have been expounding the virtues of using an open source model in an educational and artistic setting for a few years now. It seems that ears are beginning to perk up. One main point of interest has become the Cinelerra project. We recognize Cinelerra as an amazingly powerful tool, but one which is not particularly usable for us as an institution in its present form. We have begun to piece together a two pronged approach for our film department with regards to open source software development - partnership with another local University and their computer sciences dept, and pursuing research grants. We have talked about some specific film related programs which currently don't exist, at least in the open source realm. We are also talking about Cinelerra. Here is where the community can really help out - and hopefully we can really help you guys too. I'm not a programmer by any stretch of the imagination, but I do have some idea of how big a project Cinelerra is. We've outlined a few things which we feel need to be "fixed up" before we can be serious about using Cinelerra as a core part of our program - reliability and ease of installation and use being two areas. Currently it seems there are functions which are not working properly - firewire import for one. Installation is also somewhat convoluted (though projects like Ubuntu Studio might help alleviate that problem). One large feature which is missing (or so it seems) for us is support for DVCPro HD in MXF wrappers (from the HVX200 camera). Any thoughts or advice you as the developer community can pass on would be great. In particular I would like to know more about how we could work with you guys to create the best possible software. Also, in the case of the grants (if and when) - are there any cinelerra/linux developers out there who would consider working with us on contract? I will remind everyone out there in cinelerraland that this is still in the very early stages of planning, but the idea does have the support of admin here at the school, so it is something that isn't just a pipe dream. Please email me directly with ideas and suggestions, be it with the program itself, or with regards to how we as an institution with specific goals (which conceivably could differ from the CV project) do not can work positively with the community. To sum up our basic goals for the project: 1. Have a feature rich, professional quality HD video editor which is usable as a teaching tool. 2. Stable codebase 3. Streamlined work flow. 4. Must not require a degree in computer science to install and set up to use. 5. Develop codecs to support our file type of choice - DVCPro HD in MXF wrapper. (Red camera may expand this requirement.) 6. Maintain GPL status of project, and provide community with all research and development progress. Thanks for taking the time to read all this. I hope I'm not clogging up the list with this mammoth email. Nathan Ryan (nryan~nscad.ca) replace ~ with @ ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] MJPEG captures not loading correctly
Peter Federighi wrote: Hello. I was wondering if anyone can use MJPEG captures from a Zoran based capture card with Cinelerra? That is, the files can be opened, but only one field of each frame is processed (and shrunk to the top of the frame) which leaves the bottom half of the frame green. This has been an issue with every version of Cinelerra I've tried. I've also tried both internal and external ffmpeg to see if that makes a difference. It doesn't. Any ideas? Thanks - Peter Peter, I use the zoran based DC10+ capture card and I can load the files perfectly. I use qt format and full resolution (768x576). I have seen the behaviour you describe and I believe that it is a driver thing. The kernel driver from 2.6.10 and up should be working (and earlier ones maybe also) If your in need for a test clip, please let me know as I can provide one for you to test if it is Cinelerra or your driver Harm Lubbers ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] SoC 2007
On Wednesday 07 March 2007 17:34, giskard wrote: > i will start reading SoC docs, Johannes (and * project guys) do you are > ok? I think I'm ok. I'm hoping that mentoring a project is not too time consuming. My favorite project is to make X11, X11-XV, and X11-GL drivers into a single driver which decides at runtime which accelerations are available and dynamically load GL libraries. That way it's not necessary to have separate builds for OpenGL and non-OpenGL support. And it's also possible to make ATI drivers work. -- Hannes ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] fixing cinelerra, using standard C++ libs etc.
Nathan Ryan wrote: > Hey all, First off, apologies if I am replying to this incorrectly - > I usually read mailing lists, rarely post. > > I thought Hermann's comment about dev manpower was worth me coming > out of my shell. > > I work as tech support at a film department in an University of fine > art. I have been expounding the virtues of using an open source > model in an educational and artistic setting for a few years now. It > seems that ears are beginning to perk up. One main point of interest > has become the Cinelerra project. We recognize Cinelerra as an > amazingly powerful tool, but one which is not particularly usable for > us as an institution in its present form. We have begun to piece > together a two pronged approach for our film department with regards > to open source software development - partnership with another local > University and their computer sciences dept, and pursuing research > grants. We have talked about some specific film related programs > which currently don't exist, at least in the open source realm. We > are also talking about Cinelerra. Here is where the community can > really help out - and hopefully we can really help you guys too. I'm > not a programmer by any stretch of the imagination, but I do have > some idea of how big a project Cinelerra is. We've outlined a http://www.dwheeler.com/sloccount/ Totals grouped by language (dominant language first): ansic: 310217 (53.96%) cpp: 247874 (43.12%) sh: 10580 (1.84%) asm: 5936 (1.03%) perl: 258 (0.04%) sed: 16 (0.00%) Total Physical Source Lines of Code (SLOC)= 574,881 Development Effort Estimate, Person-Years (Person-Months) = 157.97 (1,895.69) (Basic COCOMO model, Person-Months = 2.4 * (KSLOC**1.05)) Schedule Estimate, Years (Months) = 3.67 (44.00) (Basic COCOMO model, Months = 2.5 * (person-months**0.38)) Estimated Average Number of Developers (Effort/Schedule) = 43.08 Total Estimated Cost to Develop = $ 21,340,200 (average salary = $56,286/year, overhead = 2.40). YMMV about this results ;) > few things which we feel need to be "fixed up" before we can be > serious about using Cinelerra as a core part of our program - > reliability and ease of installation and use being two areas. > Currently it seems there are functions which are not working properly > - firewire import for one. I proposed some time ago to throw the FW import away and instead make a dvgrab frontend at that place. Thats probably the best and simplest way to fix it. Maybe without live preview. > Installation is also somewhat convoluted (though projects like Ubuntu > Studio might help alleviate that problem). One large feature which > is missing (or so it seems) for us is support for DVCPro HD in MXF > wrappers (from the HVX200 camera). Any thoughts or advice you as the > developer community can pass on would be great. In particular I > would like to know more about how we could work with you guys to > create the best possible software. Also, in the case of the grants > (if and when) - are there any cinelerra/linux developers out there > who would consider working with us on contract? I do, but I am quite new on board. I'd step back for anyone else who want's this job. How about HV? > I will remind everyone out there in cinelerraland that this is still > in the very early stages of planning, but the idea does have the > support of admin here at the school, so it is something that isn't > just a pipe dream. Please email me directly with ideas and > suggestions, be it with the program itself, or with regards to how we > as an institution with specific goals (which conceivably could differ > from the CV project) do not can work positively with the community. > > To sum up our basic goals for the project: > > 1. Have a feature rich, professional quality HD video editor which is > usable as a teaching tool. Mission already completed. > 2. Stable codebase Neverending work, but under way. > 3. Streamlined work flow. Cinelerra could be used in diffrent ways/workflows, some could be improved for sure but I'd rather dont want't to miss any existing ones. > 4. Must not require a degree in computer science to install and set > up to use. apt-get install cinelerra > 5. Develop codecs to support our file type of choice - DVCPro HD in > MXF wrapper. (Red camera may expand this requirement.) Sounds like much work. > 6. Maintain GPL status of project, and provide community with all > research and development progress. GPL can't be taken back Cheers Christian ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] fixing cinelerra, using standard C++ libs etc.
Christian Thaeter wrote: > you might pull it with git > git clone git://git.pipapo.org/git/cinelerra/ct correction: git clone git://git.pipapo.org/cinelerra/ct > or > git clone git://repo.or.cz/cinelerra_cv/ct.git not yet ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] fixing cinelerra, using standard C++ libs etc.
On Wednesday 07 March 2007 19:25, Christian Thaeter wrote: > > Remove the Garbage collector in favor of boost::shared_ptr, the GC has > > some nasty bugs, partially together with threads. By replacing ALL > > Asset* with boost::shared_ptr these should be fixed on expanse of > > some performance. Is boost::shared_ptr thread safe? If not, this replacement does not fix anything, in particular not the thread related bugs. > > Manage Assets in std::vector / > > std::list. > > First things done: > http://www.pipapo.org/gitweb?p=cinelerra/ct;a=shortlog;h=ct > you might pull it with git > git clone git://git.pipapo.org/git/cinelerra/ct > or > git clone git://repo.or.cz/cinelerra_cv/ct.git Replacing Asset* in parameter lists by Asset& is certainly not worth it. You gain absolutely nothing, but only introduce a lot of unnecessary code changes. Please don't do that. If you want to change something to use std:: classes, start by replacing strings (char*) by std::string. But don't do that in one big sweep, be very selective which strings you replace. Start with the text in the Titler plugin (that's a real bug). Work your way through topics, eg. path names (which are easily overflown), other strings that are user input. Finally, user interface strings like menu titles. (At least) for the latter use a typedef because these strings are likely to be promoted to Unicode strings to better support non-latin UI languages. -- Hannes ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] fixing cinelerra, using standard C++ libs etc.
Johannes Sixt wrote: > On Wednesday 07 March 2007 19:25, Christian Thaeter wrote: >>> Remove the Garbage collector in favor of boost::shared_ptr, the GC has >>> some nasty bugs, partially together with threads. By replacing ALL >>> Asset* with boost::shared_ptr these should be fixed on expanse of >>> some performance. > > Is boost::shared_ptr thread safe? If not, this replacement does not fix > anything, in particular not the thread related bugs. http://www.boost.org/libs/smart_ptr/shared_ptr.htm#ThreadSafety so its not fully, but it employs the locking which already exists. The only problem could be when the internal use-count drops to zero and the thread prepares to delete a object, if then a context switch occurs and another thread increments the use count to 1 we have a problem. But this case is avoided because ALL pointers are shared pointers now. This costs little performance but guards against that case. I have Cinelerra running under valgrind for hours here now, loading some hundred assets and valgrind didnt report a single error with asset handling, thats at least far better than before :). Even if there is some corner case left where thread safety play against us, it's now possible to replace the shared_ptr easily with something else. But as long I don't observe such glitches I concentrate on improving a debugging frameworks which aids in finding race conditions, deadlocks and unspecified ownership of objects. The shared_ptr transistion is only a prelimary step, somewhat better than a bandaid to fix some bugs, later to be optimized mostly out again. Christian ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] fixing cinelerra, using standard C++ libs etc.
En/na Nathan Ryan ha escrit: Any thoughts or advice you as the developer community can pass on would be great. In particular I would like to know more about how we could work with you guys to create the best possible software. Also, in the case of the grants (if and when) - are there any cinelerra/linux developers out there who would consider working with us on contract? these are really great news. i see just one big point here that andraz insist on remember us everytime someone asks for a new feature: money. contracting someone to code those improvements is one of the best ways to help cinelerra. please, give us some feedback about this project if goes forward. regards. -- ^ ^ O O (_ _) muzzol(a)gmail.com jabber id: muzzol(a)jabber.dk No atribueixis qualitats humanes als ordinadors. No els hi agrada. "El gobierno español sólo habla con terroristas, homosexuales y catalanes, a ver cuando se decide a hablar con gente normal" Jiménez Losantos bomb terrorism bush aznar teletubbies ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] Trying to record from MiniDV camera.
On Wed, 2007-07-03 at 19:19 +0100, Gour wrote: > On Tue, 06 Mar 2007 17:38:46 -0500 > Fred Williams <[EMAIL PROTECTED]> wrote: > > > Hey, if Kino is free S/W, why not just liberate the code and then > > match styles and compile? Isn't that what free S/W is all about? > > I heard on #cinelerra (some time ago) about idea to just provide > front-end in Cinelerra for dvgrab which does good job... That sounds workable. I decided on trying Kino first and it worked fine too. So I may not go further unless problems arise. -- Regards, Fred Williams ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
Re: [CinCVS] MJPEG captures not loading correctly
--- Harm Lubbers <[EMAIL PROTECTED]> wrote: > Peter, > I use the zoran based DC10+ capture card and I can load the files > perfectly. > I use qt format and full resolution (768x576). > I have seen the behaviour you describe and I believe that it is a > driver > thing. > The kernel driver from 2.6.10 and up should be working (and earlier > ones > maybe also) > > If your in need for a test clip, please let me know as I can provide > one > for you to test if it is Cinelerra or your driver > > Harm Lubbers Harm, Hmm... A driver thing, huh? If it does turn out to be a driver thing, is there anything that can be done in the Windows world? (I actually do most capturing in Windows because I can capture audio through the Zoran card (DC30plus) so that should any frames be dropped, the audio will still be synchronized.) It would be great to have a clip that is known to work. If you could email it to me that would be great. My email address is pfederighi at yahoo.com. FYI, Yahoo!Mail has a limit of 10MB for attachments. Thank you, - Peter Never miss an email again! Yahoo! Toolbar alerts you the instant new Mail arrives. http://tools.search.yahoo.com/toolbar/features/mail/ ___ Cinelerra mailing list Cinelerra@skolelinux.no https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
