Hello,
I notice a small problem that is related to subtitle rendering.
The system is MacBook with CoreDuo (32 bits) processor.
Installation of the OS is clean (HDD is erased during installation)
QuickTime 7 is not installed at all
Perian 1.1.2 is installed and updated to 1.1.4
So the problem appear in 2 places:
1. Preview icon is white square on movies (avi compressed with divx)
that have subtitles. If subtitle file is removed the icon is rendered
well.
2. In Front Row the preview is again white square for movies with
subtitles and when they are played the screen remain black and you may
heard only audio of the movie. If subtitle file is removed again
everything works great.
When open file with QuickTimeX it shows subtitled and video correct
(so the problem does not exist when use player alone). The problem
appear only in preview icon rendering and inside Front Row.
I hope this information is sufficient for reproduction of the problem
and debugging. If you need any additional information contact me.
> Hello,
> I notice a small problem that is related to subtitle rendering.
> The system is MacBook with CoreDuo (32 bits) processor.
> Installation of the OS is clean (HDD is erased during installation)
> QuickTime 7 is not installed at all
> Perian 1.1.2 is installed and updated to 1.1.4
> So the problem appear in 2 places:
> 1. Preview icon is white square on movies (avi compressed with divx)
> that have subtitles. If subtitle file is removed the icon is rendered
> well.
> 2. In Front Row the preview is again white square for movies with
> subtitles and when they are played the screen remain black and you may
> heard only audio of the movie. If subtitle file is removed again
> everything works great.
> When open file with QuickTimeX it shows subtitled and video correct
> (so the problem does not exist when use player alone). The problem
> appear only in preview icon rendering and inside Front Row.
> I hope this information is sufficient for reproduction of the problem
> and debugging. If you need any additional information contact me.
This is going to be embarrasing for Perian's Dev Team. Sorry. You guys
can also download and see what were missed. This proves that the
problem was actually Perian and not Apple.
I found a modified version of Perian, so first you have to uninstall
the current version of Perian. After installing it you don't have to
do anything on Preferences Panel just leave all the settings as it is.
> Hello,
> I notice a small problem that is related to subtitle rendering.
> The system is MacBook with CoreDuo (32 bits) processor.
> Installation of the OS is clean (HDD is erased during installation)
> QuickTime 7 is not installed at all
> Perian 1.1.2 is installed and updated to 1.1.4
> So the problem appear in 2 places:
> 1. Preview icon is white square on movies (avi compressed with divx)
> that have subtitles. If subtitle file is removed the icon is rendered
> well.
> 2. In Front Row the preview is again white square for movies with
> subtitles and when they are played the screen remain black and you may
> heard only audio of the movie. If subtitle file is removed again
> everything works great.
> When open file with QuickTimeX it shows subtitled and video correct
> (so the problem does not exist when use player alone). The problem
> appear only in preview icon rendering and inside Front Row.
> I hope this information is sufficient for reproduction of the problem
> and debugging. If you need any additional information contact me.
On Sep 4, 8:35 am, koblar <david.kob...@gmail.com> wrote:
> Hello!
> I and a lot off other people (I have read on forums) have the same
> problem. Did you maybe find any solution?
I've just downloaded code from perian svn and built it. Don't know if
there are other issues hidden somewhere, but at least the subtitles +
frontrow black screen issue has been solved.
> On Sep 4, 8:35 am, koblar <david.kob...@gmail.com> wrote:
> > Hello!
> > I and a lot off other people (I have read on forums) have the same
> > problem. Did you maybe find any solution?
> I've just downloaded code from perian svn and built it. Don't know if
> there are other issues hidden somewhere, but at least the subtitles +
> frontrow black screen issue has been solved.
> Can you please tell me what exactly have you done or if you can send
> me the file in which you biuld in perian svn...
> Best regards,
> David Koblar
> On Oct 1, 11:34 pm, dawe <daweonl...@gmail.com> wrote:
> > Hi
> > On Sep 4, 8:35 am, koblar <david.kob...@gmail.com> wrote:
> > > Hello!
> > > I and a lot off other people (I have read on forums) have the same
> > > problem. Did you maybe find any solution?
> > I've just downloaded code from perian svn and built it. Don't know if
> > there are other issues hidden somewhere, but at least the subtitles +
> > frontrow black screen issue has been solved.
You need to have 10.4 SDK (unless you want to modify build
configuration), just choose PerianPref in targets and build it (it
should build codecs as dependencies), as Deployment.
After that you will find a buid/deployment directory with the
preference pane
> You need to have 10.4 SDK (unless you want to modify build
> configuration), just choose PerianPref in targets and build it (it
> should build codecs as dependencies), as Deployment.
> After that you will find a buid/deployment directory with the
> preference pane
10.5 SDK now, actually.
(But it should still run on 10.4.)
I am sorry but I do not understand what do I have to do. Can you
please write step by step from begining til the end.
I managed to come to Perian.xcodeproj in trunk/perian where is a file
"project.pbxproj" and I do not know what to do with it. If I click it
it opens in safari and there is a lot of text.
Can you please tell me what is SDK?
Thanks
David
On Oct 2, 3:18 pm, dawe <daweonl...@gmail.com> wrote:
> You need to have 10.4 SDK (unless you want to modify build
> configuration), just choose PerianPref in targets and build it (it
> should build codecs as dependencies), as Deployment.
> After that you will find a buid/deployment directory with the
> preference pane
This mailing list is not for going to become a howto for how to use well
documented tools highly available on the internet. I understand wanting to
help each other, but you're starting to move away from the focus of this
list.
David please read the documentation on subversion and xcode, and if you
can't figure out the steps 1,2,3... that you were wanting here, then you
will need to wait until we put out the next version of Perian.
On Fri, Oct 2, 2009 at 11:27 AM, koblar <david.kob...@gmail.com> wrote:
> Hello again.
> I am sorry but I do not understand what do I have to do. Can you
> please write step by step from begining til the end.
> I managed to come to Perian.xcodeproj in trunk/perian where is a file
> "project.pbxproj" and I do not know what to do with it. If I click it
> it opens in safari and there is a lot of text.
> Can you please tell me what is SDK?
> Thanks
> David
> On Oct 2, 3:18 pm, dawe <daweonl...@gmail.com> wrote:
> > On Oct 2, 7:11 am, koblar <david.kob...@gmail.com> wrote:
> > > Hello!
> > > Can you please tell me what exactly have you done or if you can send
> > > me the file in which you biuld in perian svn...
> > You need to have 10.4 SDK (unless you want to modify build
> > configuration), just choose PerianPref in targets and build it (it
> > should build codecs as dependencies), as Deployment.
> > After that you will find a buid/deployment directory with the
> > preference pane
I do not know why is a problem for writing down a few steps. If you
would done a better job and released a new version of Perian this
would not be neccesary. So wat is the problem with releasing a new
version of Perian if you already figured out what is the problem for
not showing movie and have already solved it in svn. A lot of people
would apreciate it.
--
David
On Oct 3, 5:22 am, Christopher Forsythe <ch...@growl.info> wrote:
> This mailing list is not for going to become a howto for how to use well
> documented tools highly available on the internet. I understand wanting to
> help each other, but you're starting to move away from the focus of this
> list.
> David please read the documentation on subversion and xcode, and if you
> can't figure out the steps 1,2,3... that you were wanting here, then you
> will need to wait until we put out the next version of Perian.
> Chris
> On Fri, Oct 2, 2009 at 11:27 AM, koblar <david.kob...@gmail.com> wrote:
> > Hello again.
> > I am sorry but I do not understand what do I have to do. Can you
> > please write step by step from begining til the end.
> > I managed to come to Perian.xcodeproj in trunk/perian where is a file
> > "project.pbxproj" and I do not know what to do with it. If I click it
> > it opens in safari and there is a lot of text.
> > Can you please tell me what is SDK?
> > Thanks
> > David
> > On Oct 2, 3:18 pm, dawe <daweonl...@gmail.com> wrote:
> > > On Oct 2, 7:11 am, koblar <david.kob...@gmail.com> wrote:
> > > > Hello!
> > > > Can you please tell me what exactly have you done or if you can send
> > > > me the file in which you biuld in perian svn...
> > > You need to have 10.4 SDK (unless you want to modify build
> > > configuration), just choose PerianPref in targets and build it (it
> > > should build codecs as dependencies), as Deployment.
> > > After that you will find a buid/deployment directory with the
> > > preference pane
On Oct 2, 6:27 pm, koblar <david.kob...@gmail.com> wrote:
> Hello again.
> I am sorry but I do not understand what do I have to do. Can you
> please write step by step from begining til the end.
Make sure you have installed Xcode and the "Developers Tools" (they
are in your Snow Leopard DVD). During the install process you will be
asked to customize the installation and choose to include the 10.4
SDK.
Once done, open the terminal and issue
It will download latest source code for Perian. Open the folder and
look for the file "Perian.xcodeproj", open it (with Xcode). I guess
you are not familiar with it, but ini principle look at the tree on
the left of the window, look for "Targets", expand it and look for
"PerianPref" (or prefpane... can't recall right now), right click (or
ctrl click) on it and choose to build it. Go for a walk. When done you
will find in the same directory a directory "build" wich contains, in
the end, the preference pane...
HTH. BTW, if you have issues with Xcode try asking on Apple developers
lists.
Well, I'm no longer motivated to do any work on Perian this weekend. Perhaps I'll just relax this weekend instead. For those who can't understand how this could possibly be the case, here's how this email sounds to us:
On Oct 3, 2009, at 2:21 AM, koblar wrote:
> I do not know why is a problem for writing down a few steps.
I'm too lazy to search for how to do this myself even though the general steps for all OSS projects is well documented. In addition, I'm paying such little attention to this mailing list that I failed to notice the step-by-step instructions in the forums to which a link was included in an email sent to this list, in the same thread, just yesterday. I'm demanding that the developers or others contributors repeat the same process over and over and over just because I want it that way.
> If you > would done a better job and released a new version of Perian this > would not be neccesary.
I'm demanding better service from a free project done by generous people in their spare time. I should know better than to think that I'm deserving of anything more from people who have given so much and received so little, but apparently I don't.
> So wat is the problem with releasing a new > version of Perian if you already figured out what is the problem for > not showing movie and have already solved it in svn.
I have a better idea when a product should be released than the developers who are intimately familiar with all the details as well as its short-comings. I'm ignorant to the fact that the developers discussed changing this very code just yesterday in the IRC channel. I'm ignoring the fact that they have said a SL compatible release is being developed as well as the fact that this is not the only issue. I'm also ignoring the fact that incomplete releases result in far more outcry than a later release which is complete. I don't care that I'm uninformed; I'm going to present a demand anyway.
> A lot of people > would apreciate it.
I'm ignoring the fact that a lot more people are appreciative of what they already have, and are patient enough to wait for another release. Even though they outnumber the unappreciative by far, unfortunately the later are more vocal. Lastly, I wrote this email in such a rage that I failed to correct the numerous spelling mistakes that my browser would have been showing me.
I do not want to argue with you, because it is a waist of time. I will
write down just some explanations.
> Lastly, I wrote this email in
> such a rage that I failed to correct the numerous spelling mistakes
> that my browser would have been showing me.
Excuse me for my english. English is my second language and my browser
is not or was not showing me any spelling mistakes.
> I'm paying such little attention to this mailing list that I failed to
> notice the step-by-step instructions in the forums to which a link was
> included in an email sent to this list, in the same thread, just
> yesterday.
I have seen it and went by steps described in it. But in the middle it
produced an error "cannot find SDKs/MacOSX10.4u" which I did not know
how to find. And than later it was written that it should work with
10.5 also, but in my case does not. That is why I wrote back.
> I'm ignorant to the fact that the developers
> discussed changing this very code just yesterday in the IRC channel.
And from where should I know this?
> I'm ignoring the fact that a lot more people are appreciative of what
> they already have, and are patient enough to wait for another
> release.
I could be patient to if I would know for how long.
The first problem was written here on September 1. I have been waiting
patiently for over one month
Is that hard to predict and tell when the new release will come out?
Or at least release a beta version.
On Oct 3, 4:24 pm, Graham Booker <gboo...@cod3r.com> wrote:
> Well, I'm no longer motivated to do any work on Perian this weekend.
> Perhaps I'll just relax this weekend instead. For those who can't
> understand how this could possibly be the case, here's how this email
> sounds to us:
> On Oct 3, 2009, at 2:21 AM, koblar wrote:
> > I do not know why is a problem for writing down a few steps.
> I'm too lazy to search for how to do this myself even though the
> general steps for all OSS projects is well documented. In addition,
> I'm paying such little attention to this mailing list that I failed to
> notice the step-by-step instructions in the forums to which a link was
> included in an email sent to this list, in the same thread, just
> yesterday. I'm demanding that the developers or others contributors
> repeat the same process over and over and over just because I want it
> that way.
> > If you
> > would done a better job and released a new version of Perian this
> > would not be neccesary.
> I'm demanding better service from a free project done by generous
> people in their spare time. I should know better than to think that
> I'm deserving of anything more from people who have given so much and
> received so little, but apparently I don't.
> > So wat is the problem with releasing a new
> > version of Perian if you already figured out what is the problem for
> > not showing movie and have already solved it in svn.
> I have a better idea when a product should be released than the
> developers who are intimately familiar with all the details as well as
> its short-comings. I'm ignorant to the fact that the developers
> discussed changing this very code just yesterday in the IRC channel.
> I'm ignoring the fact that they have said a SL compatible release is
> being developed as well as the fact that this is not the only issue.
> I'm also ignoring the fact that incomplete releases result in far more
> outcry than a later release which is complete. I don't care that I'm
> uninformed; I'm going to present a demand anyway.
> > A lot of people
> > would apreciate it.
> I'm ignoring the fact that a lot more people are appreciative of what
> they already have, and are patient enough to wait for another
> release. Even though they outnumber the unappreciative by far,
> unfortunately the later are more vocal. Lastly, I wrote this email in
> such a rage that I failed to correct the numerous spelling mistakes
> that my browser would have been showing me.
I installed 10.4 SDK and developer tools from Leopard DVD and in
terminal copied svn to local disk. I double clicked on
"Perian.xcodeproj" as you said. In targets I can find only
"PerianPane" with cube logo and "CreatePrefPanePlist" with target
logo. I right clicked "PerianPane" and clicked Build.
As a result i get "Perian.prefPane" in folder "/Build/Development" and
in xcode in lower left corner message: "Build failed (1 error, 40
warnings)"
In build results it says:
Link/perian/build/Development/Peroan.component/Contents/MacOS/Perian
"_MIMIMT", referenced from:
_dcode_nals in bitstream_info.o
Symbol(s) not found
Collect2: Id returned 1 exit status
> On Oct 2, 6:27 pm, koblar <david.kob...@gmail.com> wrote:
> > Hello again.
> > I am sorry but I do not understand what do I have to do. Can you
> > please write step by step from begining til the end.
> Make sure you have installed Xcode and the "Developers Tools" (they
> are in your Snow Leopard DVD). During the install process you will be
> asked to customize the installation and choose to include the 10.4
> SDK.
> Once done, open the terminal and issue
> It will download latest source code for Perian. Open the folder and
> look for the file "Perian.xcodeproj", open it (with Xcode). I guess
> you are not familiar with it, but ini principle look at the tree on
> the left of the window, look for "Targets", expand it and look for
> "PerianPref" (or prefpane... can't recall right now), right click (or
> ctrl click) on it and choose to build it. Go for a walk. When done you
> will find in the same directory a directory "build" wich contains, in
> the end, the preference pane...
> HTH. BTW, if you have issues with Xcode try asking on Apple developers
> lists.
> I do not want to argue with you, because it is a waist of time. I will > write down just some explanations.
And yet, you still did.
>> Lastly, I wrote this email in >> such a rage that I failed to correct the numerous spelling mistakes >> that my browser would have been showing me.
> Excuse me for my english. English is my second language and my browser > is not or was not showing me any spelling mistakes.
I looked at the message headers and it said you were using Safari. Safari shows spelling mistakes. From this I assumed you were capable of correcting mistakes but chose not to out of haste (which is fairly common). Perhaps I assumed too much.
>> I'm paying such little attention to this mailing list that I failed >> to >> notice the step-by-step instructions in the forums to which a link >> was >> included in an email sent to this list, in the same thread, just >> yesterday.
> I have seen it and went by steps described in it. But in the middle it > produced an error "cannot find SDKs/MacOSX10.4u" which I did not know > how to find. And than later it was written that it should work with > 10.5 also, but in my case does not. That is why I wrote back.
That would have been extremely helpful to know, but alas, you never mentioned it. Regardless, this falls under topics Chris stated is outside the scope of this list.
>> I'm ignorant to the fact that the developers >> discussed changing this very code just yesterday in the IRC channel.
> And from where should I know this?
Thank you for making my point. I stated that you were ignorant of this fact, in other words, you didn't know it. From this it is easy to conclude you are not qualified to state when releases should be made.
>> I'm ignoring the fact that a lot more people are appreciative of what >> they already have, and are patient enough to wait for another >> release.
> I could be patient to if I would know for how long. > The first problem was written here on September 1. I have been waiting > patiently for over one month > Is that hard to predict and tell when the new release will come out? > Or at least release a beta version.
Releases will be made when they are made. This is not a company with full-time employees. As such, we do not have estimates. If things are going to slow for you, try fixing it yourself or hire someone to do it for you instead of trying to lay blame. We always welcome additional developers, but we are not going to be rushed into something we are unwilling to do (such as putting out incomplete releases).
At this point, I consider any further discussion with you to be as you put it "a [waste] of time." Since we are in agreement on that point, then you should not persist any further.
|
