Not even two, just maybe half a cent... Wouldn't it be possible not to integrate the final product of blender/audacity editing into the timeline but a temporary preview (leaving the original file untouched), and storing the parameters? (Actually that's what I understood marquitux meant) So that only if you render the *final* output in cinelerra, first all blender 'segments' are rendered in blender (maybe creating .blend files on the fly, using the stored parameters, or just using python), saved and then used to render the output with cinelerra...
In general, this sounds similar to the HD proxy-editing thing, maybe it could use the same interface... Just some thoughts.... really looking forward to be able to construct a timeline in cinelerra and do the compositing in blender some day.. Jonas On Thu, 30 Aug 2007 17:26:15 +0800 Graham Evans <[EMAIL PROTECTED]> wrote: > > > > > the same happends with audio, Adobe Premiere Pro CALLS from the > > timeline an audio editor: Adobe audition, it´s so simple, but works > > and the users had more control over the timeline, and no render is > > needed, well the soft makes de render internally.Wouln´t be great > > to have this in cinelerra? just RIGTH CLICK in an audioclip and and > > a popup or menu saying: OPEN in AUDACITY, then cinelerra runs a > > fast audio render, and replaces i the timeline the audio with the > > fake lossless WAV. that´s profesional, not very complex to achieve, > > correct me if i´m wrong, because audacity, can RUN-and-load > > externally: audacity temporary-audio.wav then just use the FX from > > audacity, and close-save and the timeline automatically refresh > > that file, cinelerra actually does this. > > > Hi Marquitux > > I have no knowledge of Blender so I can't make too much comment on > those suggestions. With audio production I have more experience. I > suspect your Blender idea has similar unresolved conceptual issue as > with your Audacity suggestion: > > You're asking Cinelerra (or Audacity as a child process of Cinelerra) > to create project source files 'on the fly'. This is a radical > departure > >from the Cinelerra way of working as I see it. You can't just > >'refresh > the file' as you say because the timeline audio is a subset (and > superset) of source audio file(s). Also I think the source files > should, in general, not be touched by Cinelerra. Otherwise the > conceptual framework of cinelerra gets undermined. > > So you actually have to create new source material : the rendered > audio segment. You could, I guess, do this in /tmp folder which is > then accessed during the final render job. But if /tmp folder is > machine specific then your project is no longer portable. So instead > I guess you ask the user where they want the new sources created. Or > you could, like Ardour does, have a whole big folder per project, > with xml, sources and renders (including timeline renders) all mixed > up. > > But here is the cost of your new feature here: the simplicity of > concept which underlies Cinelerra is lost. > > Ardour gives you the option to make your project folder self > contained by copying all the audio source files into it - but somehow > I think with video footage this is not an option. Cinelerra does > need more options for making projects portable though. > > I'm not saying your idea is bad. Just that it has, at the moment, no > flesh on those bones. Also the idea needs to be good enough to > abandon a certain simplicity which underlies the complexity of > Cinelerra. I'm unsure really whether I would use the feature. I'm > happy at the moment with a workflow where I am controlling and > keeping track of the sources and accessing Audacity, Ardour etc. in > seperate processes. That's something a window manager does well. > > Also I can't see how a multimedia framework is going to resolve this > issue for cinelerra. We're still talking apples (project files, > final renders) and pears (source editing). > > Do you have any idea how your idea might fit in with the Cinelerra > way of working with files, projects and rendering at the end? > > Another idea you mentioned I really like : integrating GIMP driven > effects with Cinelerra's keyframe automation. I wonder if the GIMP > engine is capable of working well with all four Cinelerra processes: > timeline preview, Compositor, background render and final render > processes. I guess the real question is: with how much work... > > Graham E > > _______________________________________________ > Cinelerra mailing list > [email protected] > https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra _______________________________________________ Cinelerra mailing list [email protected] https://init.linpro.no/mailman/skolelinux.no/listinfo/cinelerra
