[x264-devel] Re: [OSX] Re: x264 improvement

Firas Al-Tahan firearse at gmail.com
Tue Mar 14 14:48:35 CET 2006


Sounds to me like there's a great demand for Dual PPC with Altivec
optimization here...

:)

Thanks for the note Tim, I'll be sure to get that updated when I get homew
tonight. Meanwhile - I'll be looking on the Apple pages for help with
Altivec, from my initial research there seems to be a lot there.

H.264 on Quicktime is very slow - but I haven't compared it to x264 yet.
Anyone know how well the Intels are doing with regards to 1080p? Seems they
can do SD to at least 25FPS.

Thanks,

Firas
(Dual 2GHz G5)


On 3/14/06, Tim Greatrex <tim.greatrex at mac.com> wrote:
>
> I have had a quick go but no luck yet (as i said i am fairly new to
> all this!) Will try out davids tips later on. As for books, i just
> tend to look up stuff on tinternet. Apple pages seem fairly helpful
> as a start point.
>
> BTW there's XCode 2.2.1 now (see apple developer site).
>
> Tim
> (Dual G4 PM / G4 ibook)
>
>
> On 13 Mar 2006, at 23:06, Firas Al-Tahan wrote:
>
> > I'm certainly willing to try!
> >
> > Tim - have you been able to get the x264 code into XCode 2.1? I
> > haven't had much experience with XCode, and the book I bought  ("The
> > Mac XCode 2 Book" by Michael Cohen & Dennis Cohen) is a pile of crap.
> >
> > Having read the Apple pages, the Shark tool should help identify areas
> > needing optimization. Once I get XCode working with the x264 project,
> > il be happy.
> >
> > Now, just to finish off the coursework and the exams first....
> >
> > Firas
> >
> > On 3/13/06, Tim Greatrex <tim.greatrex at mac.com> wrote:
> >> I'm guessing the issue may be that he has worked on this in his spare
> >> time, while he works for a company that develops a different codec
> >> which it then sells (so x264 is classed as the competition). I
> >> doesn't sound like there are any legal issues with the code he's
> >> developed, but maybe moral issues for his position within his day-
> >> job.
> >>
> >> As a mac user (who is very new to c and at the moment can't make
> >> head-
> >> nor-tail of the x264 code (though it works great!), let alone altivec
> >> optimisations) it would be great if you could make it available,
> >> especially with some good annotations describing what does what if
> >> possible, so that myself and people like Firas can learn from you.
> >>
> >>
> >> Tim Greatrex
> >>
> >> On 13 Mar 2006, at 18:20, Firas Al-Tahan wrote:
> >>
> >>> Hey,
> >>>
> >>> if it means anything David, I think all PPC owners working with x264
> >>> would really appreicate your efforts.
> >>>
> >>> I don't claim to have a full knowledge of the GPL - but as Benjamin
> >>> Larsson said - I can't see where there'd be a problem -
> >>> especially if
> >>> it was coded on a home computer in your own free time.
> >>>
> >>> Thanks,
> >>>
> >>> Firas
> >>>
> >>> On 3/13/06, David Wolstencroft <lordrpi at gmail.com> wrote:
> >>>> I didn't look at the to field before sending, an incredibly bad
> >>>> mistake by me.
> >>>>
> >>>> This x264 build resides on my home computer only. I mainly fiddled
> >>>> around with the Altivec to get better with the technology and have
> >>>> been able to boost performance of the x264 builds on my home
> >>>> computer. Since then my duties have changed as I have become more
> >>>> involved with software engineering, so I'm afraid of it being
> >>>> looked
> >>>> at as competition.
> >>>>
> >>>> - David
> >>>>
> >>>>
> >>>> On Mar 13, 2006, at 5:03 AM, Benjamin Larsson wrote:
> >>>>
> >>>>> David Wolstencroft wrote:
> >>>>>
> >>>>>> Eric,
> >>>>>>
> >>>>>> I might have mentioned before that I have some faster altivec
> >>>>>> code
> >>>>>> for the G4/G5, yet I'm a bit nervous to incorporate it due to my
> >>>>>> employer. If you would like to add it "silently", that would be
> >>>>>> great.
> >>>>>>
> >>>>>> - David
> >>>>>
> >>>>> Well first if you were coding this under working hours then your
> >>>>> employer owns the code, which means that if this is added
> >>>>> silently the
> >>>>> code isn't really free just added without the knowledge of the
> >>>>> owner.
> >>>>> But then we have the GPL aspect, if the code is distributed to
> >>>>> someone,
> >>>>> they have a right to get the source under the GPL and they can
> >>>>> redistribute it as they see fit.  On the other hand if you did
> >>>>> this in
> >>>>> your freetime and just don't want you employer to know that you
> >>>>> contributed some code I guess it is up to the maintainer if your
> >>>>> contribution is accepted. I wouldn't object in such a case.
> >>>>>
> >>>>> MvH
> >>>>> Benjamin Larsson
> >>>>>
> >>>>> --
> >>>>> "incorrect information" is an oxymoron. Information is, by
> >>>>> definition, factual, correct.
> >>>>>
> >>>>> --
> >>>>> This is the x264-devel mailing-list
> >>>>> To unsubscribe, go to: http://developers.videolan.org/lists.html
> >>>>>
> >>>>
> >>>> --
> >>>> This is the x264-devel mailing-list
> >>>> To unsubscribe, go to: http://developers.videolan.org/lists.html
> >>>>
> >>>>
> >>>
> >>> --
> >>> This is the x264-devel mailing-list
> >>> To unsubscribe, go to: http://developers.videolan.org/lists.html
> >>>
> >>
> >> --
> >> This is the x264-devel mailing-list
> >> To unsubscribe, go to: http://developers.videolan.org/lists.html
> >>
> >>
> >
> > --
> > This is the x264-devel mailing-list
> > To unsubscribe, go to: http://developers.videolan.org/lists.html
> >
>
> --
> This is the x264-devel mailing-list
> To unsubscribe, go to: http://developers.videolan.org/lists.html
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.videolan.org/pipermail/x264-devel/attachments/20060314/84299eb7/attachment.htm 


More information about the x264-devel mailing list