1 Oct 10:39
1 Oct 14:46
Re: Next Developer meeting reschedule
Christian Thaeter schrieb: > I just talked with joel who has some very busy time this week. > > Since we have some (very few) core issues in the list and we delayed > some things last time because joel had no time we now came up with a > new date proposal: > > Monday 6th Oct, as early as 18:00 UTC, probably later. > > Please confirm this and make suggestions about a concrete time. Hi Christian, basically I am glad the meeting is rescheduled, because I am very busy too and hadn't time to prepare the things I wanted to discuss > Monday 6th Oct, as early as 18:00 UTC, probably later. Monday is problematic for me, because I am at work at Baader until late at night. I could accommodate 21:00 UTC (which is 23:00 here) But why not just picking the next Thursday? Thursday seemed to work well for everybody. So my proposal is: Thursday 9th Oct, 18:00 UTC, or later if this helps. Cheers, Hermann
1 Oct 18:44
Re: Next Developer meeting reschedule
prg@... wrote: > Christian Thaeter schrieb: >> I just talked with joel who has some very busy time this week. >> >> Since we have some (very few) core issues in the list and we delayed >> some things last time because joel had no time we now came up with a >> new date proposal: >> >> Monday 6th Oct, as early as 18:00 UTC, probably later. >> >> Please confirm this and make suggestions about a concrete time. > > Hi Christian, > > basically I am glad the meeting is rescheduled, because I am very busy > too and hadn't time to prepare the things I wanted to discuss > >> Monday 6th Oct, as early as 18:00 UTC, probably later. > > Monday is problematic for me, because I am at work at Baader until late > at night. I could accommodate 21:00 UTC (which is 23:00 here) > > But why not just picking the next Thursday? Thursday seemed to work > well for everybody. So my proposal is: > > Thursday 9th Oct, 18:00 UTC, or later if this helps. Joel saied that Thursdays never work well for him. Joel: Tuesday, Wednesdy, Friday, Weekend?(Continue reading)
1 Oct 19:05
Re: Next Developer meeting reschedule
On 18:44 Wed 01 Oct , Christian Thaeter wrote: > prg@... wrote: > > Christian Thaeter schrieb: > >> I just talked with joel who has some very busy time this week. > >> > >> Since we have some (very few) core issues in the list and we delayed > >> some things last time because joel had no time we now came up with a > >> new date proposal: > >> > >> Monday 6th Oct, as early as 18:00 UTC, probably later. > >> > >> Please confirm this and make suggestions about a concrete time. > > > > Hi Christian, > > > > basically I am glad the meeting is rescheduled, because I am very busy > > too and hadn't time to prepare the things I wanted to discuss > > > >> Monday 6th Oct, as early as 18:00 UTC, probably later. > > > > Monday is problematic for me, because I am at work at Baader until late > > at night. I could accommodate 21:00 UTC (which is 23:00 here) > > > > But why not just picking the next Thursday? Thursday seemed to work > > well for everybody. So my proposal is: > > > > Thursday 9th Oct, 18:00 UTC, or later if this helps. > > Joel saied that Thursdays never work well for him. >(Continue reading)
1 Oct 19:18
Re: Next Developer meeting reschedule
Clay Barnes wrote: > On 18:44 Wed 01 Oct , Christian Thaeter wrote: >> prg@... wrote: >>> Christian Thaeter schrieb: >>>> I just talked with joel who has some very busy time this week. >>>> >>>> Since we have some (very few) core issues in the list and we delayed >>>> some things last time because joel had no time we now came up with a >>>> new date proposal: >>>> >>>> Monday 6th Oct, as early as 18:00 UTC, probably later. >>>> >>>> Please confirm this and make suggestions about a concrete time. >>> Hi Christian, >>> >>> basically I am glad the meeting is rescheduled, because I am very busy >>> too and hadn't time to prepare the things I wanted to discuss >>> >>>> Monday 6th Oct, as early as 18:00 UTC, probably later. >>> Monday is problematic for me, because I am at work at Baader until late >>> at night. I could accommodate 21:00 UTC (which is 23:00 here) >>> >>> But why not just picking the next Thursday? Thursday seemed to work >>> well for everybody. So my proposal is: >>> >>> Thursday 9th Oct, 18:00 UTC, or later if this helps. >> Joel saied that Thursdays never work well for him. >> >> Joel: Tuesday, Wednesdy, Friday, Weekend? >>(Continue reading)
1 Oct 18:57
Re: Next Developer meeting reschedule
Ciao! On Wed, 2008-10-01 at 14:46 +0200, prg@... wrote: > > Monday 6th Oct, as early as 18:00 UTC, probably later. > > Please confirm this and make suggestions about a concrete time. > So my proposal is: > Thursday 9th Oct, 18:00 UTC, or later if this helps. Both dates are good for me. I'm interested in the logo discussion, more in the decision process than in the logo itself. I'll be there! Ciao! raffa
1 Oct 19:45
Re: Next Developer meeting reschedule
On 19:18 Wed 01 Oct , Christian Thaeter wrote: > Clay Barnes wrote: > > On 18:44 Wed 01 Oct , Christian Thaeter wrote: > >> prg@... wrote: > >>> Christian Thaeter schrieb: > >>>> I just talked with joel who has some very busy time this week. > >>>> > >>>> Since we have some (very few) core issues in the list and we delayed > >>>> some things last time because joel had no time we now came up with a > >>>> new date proposal: > >>>> > >>>> Monday 6th Oct, as early as 18:00 UTC, probably later. > >>>> > >>>> Please confirm this and make suggestions about a concrete time. > >>> Hi Christian, > >>> > >>> basically I am glad the meeting is rescheduled, because I am very busy > >>> too and hadn't time to prepare the things I wanted to discuss > >>> > >>>> Monday 6th Oct, as early as 18:00 UTC, probably later. > >>> Monday is problematic for me, because I am at work at Baader until late > >>> at night. I could accommodate 21:00 UTC (which is 23:00 here) > >>> > >>> But why not just picking the next Thursday? Thursday seemed to work > >>> well for everybody. So my proposal is: > >>> > >>> Thursday 9th Oct, 18:00 UTC, or later if this helps. > >> Joel saied that Thursdays never work well for him. > >> > >> Joel: Tuesday, Wednesdy, Friday, Weekend?(Continue reading)
1 Oct 19:51
Re: Next Developer meeting reschedule
Clay Barnes schrieb: > I'll be sure to peruse the wiki first, though, in case I've missed > some UI decisions that affect them. > Hi Clay, as far as I am aware most GUI relevant discussions lately happend here on the mailinglist. I take it you are aware of nasa's proposal: http://pipapo.org/pipawiki/Lumiera/DesignProcess/DelectusShotEvaluator cheers, Hermann
1 Oct 19:58
Re: Next Developer meeting reschedule
> prg@... wrote: >> But why not just picking the next Thursday? Thursday seemed to work >> well for everybody. So my proposal is: >> >> Thursday 9th Oct, 18:00 UTC, or later if this helps. > Christian Thaeter schrieb: > Joel saied that Thursdays never work well for him. > > Joel: Tuesday, Wednesdy, Friday, Weekend? > > How about the others? (Plouj, nasa, simav,...?) for me: Thursday, Friday, Sunday work best, Mon-Wed is problematic
1 Oct 20:24
Automatic Audio Syncing / Fingerprinting
I just re-read this > http://pipapo.org/pipawiki/Lumiera/DesignProcess/DelectusShotEvaluator > and thought that this is interesting point: --- The application should be smart enough to fill in audio if the existing source is missing. For example, in a recent project I was working on a camera op accidently set the shotgun mike to test mode, ruining about 10% of the audio for the gig. I was running sound, and luckily I had a backup copy of the main audio being recorded. This application should, when told that these two are of the same event at the same time, seamlessly overlay the backup audio over the section of the old audio that has been marked bad and not even play the bad audio. This is just background noise, and streamlining the immense task of sorting through footage needs to be simplified as much as possible. --- Because still, at least in lower budget productions for flexibility reasons (no cables to the camera etc), external audio (Flash-Recorder / DAT) without TC sync is used. Even the more professional Prosumer cameras / Audio Equipment lack possibilities to sync for Freerun or other sync strategies. On the other hand, at least in video, often external Sound recorders and camera mic record the same sound from different perspectives. So, automatic syncing where possible by creating audio fingerprints could be nice. I dont know if this is what the part in the document referred to.
RSS Feed