I don't think anyone is working on that. But it should be fairly easy to do,
like you said. I think each media item has a edl variable built in, I think
it is used to check if we need to remove an edl file each time we delete an
item.
On Dec 27, 2007 7:59 PM, Evan Hisey <[EMAIL PROTECTED]> wrote:
Hey gang-
Was someone working on setting up encodings of the commercial free?
I was thinking a good place to stick teh option would be in the
reencoding server. It is already doing the reencodes so it should be
straight forward to add the extra field option. I was thinking
something like a basic
Jason Tackaberry wrote:
> On Thu, 2007-12-27 at 21:29 +0100, Dirk Meyer wrote:
>> > What is the behavior of pynotifier with simulate=True? From what I can
>> > see it just causes it to call select() on any fds we're monitoring, but
>> > doesn't do anything else (call timers or dispatchers) or even
On Thu, 2007-12-27 at 21:29 +0100, Dirk Meyer wrote:
> > What is the behavior of pynotifier with simulate=True? From what I can
> > see it just causes it to call select() on any fds we're monitoring, but
> > doesn't do anything else (call timers or dispatchers) or even invoke
> > callbacks for the
Jason Tackaberry wrote:
> On Thu, 2007-12-27 at 21:10 +0100, Dirk Meyer wrote:
>> It is the simulate parameter for nf_generic. We need it to run the
>> notifier loop in a thread for testing. This is a very kaa specific
>> patch crunchy does not like in pyNotifier.
>
> What is the behavior of pynoti
On Thu, 2007-12-27 at 21:10 +0100, Dirk Meyer wrote:
> It is the simulate parameter for nf_generic. We need it to run the
> notifier loop in a thread for testing. This is a very kaa specific
> patch crunchy does not like in pyNotifier.
What is the behavior of pynotifier with simulate=True? From w
Jason Tackaberry wrote:
> On Thu, 2007-12-27 at 20:29 +0100, Dirk Meyer wrote:
>> reason why kaa.notifier is in kaa.base. There is only one small patch
>> in our pynotifier that is not in the real pynotifier and that is for
>> running our mainloop in a different mainloop as thread. So if you have
>
On Thu, 2007-12-27 at 20:29 +0100, Dirk Meyer wrote:
> reason why kaa.notifier is in kaa.base. There is only one small patch
> in our pynotifier that is not in the real pynotifier and that is for
> running our mainloop in a different mainloop as thread. So if you have
> apps using pynotifier, you c
Robert Buchholz wrote:
> On Saturday 22 December 2007, Dirk Meyer wrote:
>> Now that Freevo 1.7.5 and Freevo 1.8.0rc1 are out you can also get a
>> new set of kaa modules you may want to use with these releases.
>>
>> kaa.base 0.2.0
> ...
>> * pyNotifier updates
>
> Is your pynotifier an actual for
On Saturday 22 December 2007, Dirk Meyer wrote:
> Now that Freevo 1.7.5 and Freevo 1.8.0rc1 are out you can also get a
> new set of kaa modules you may want to use with these releases.
>
> kaa.base 0.2.0
...
> * pyNotifier updates
Is your pynotifier an actual fork now that does not work with the
Duncan Webb wrote:
> Hoi Zäme,
>
> As promised the Freevo-1.7.5 and Freevo-1.8.0rc1 releases have been and
> can be downloaded from sourceforge
> https://sourceforge.net/project/showfiles.php?group_id=46652.
>
> Freevo-1.7.5 has been released about seven weeks after 1.7.4 this
> release has new sti
11 matches
Mail list logo
