|
| Author |
Message |
Iluvatar
Joined: 29 Feb 2008
Posts: 335
|
 Posted: Tue Nov 15, 2011 11:11 pm Post subject: |
 |
|
Well assuming you had changed your ffmpeg path settings to point to the correct file I would have to say that maybe some of the ASM abilities that FFmpeg is compiled with is different between your processor (i7?) and mine (Core2Duo). I seem to remember that the MacPorts build that I used started enabling ASM during compile for FFmpeg sometime after my first build, which you said worked for you.
Give me some time to disable that and upload a new build for you to test. Time is a bit short with a new addition to my family so I would say by the end of the week I can do something.
Good to hear the feedback. I wouldn't have thought of the issue if not for it. |
|
| Back to top |
|
 |
cweb
Joined: 19 Sep 2011
Posts: 17
|
| Posted: Wed Nov 16, 2011 7:22 pm Post subject: |
|
|
Congrats on the new family. No rush on my part.
Ooooh! If you have time can you describe how you apply the 'non-monotone timestamp'. Thanks. |
|
| Back to top |
|
|
Iluvatar
Joined: 29 Feb 2008
Posts: 335
|
| Posted: Sun Dec 04, 2011 5:45 pm Post subject: |
|
|
| cweb wrote: | Congrats on the new family. No rush on my part.
Ooooh! If you have time can you describe how you apply the 'non-monotone timestamp'. Thanks. |
Thanks.
I have attached to the first post a 64bit version only. Please try this to see if it fixes your issue. I have a couple build options to play with to see what the issue was but I wanted to start by disabling the Universal build. Next on the list if this doesn't work is the YASM support for ASM optimizations.
Please run this in the Terminal.app and post the output if you run into errors. That really is the only way I can see what the possible issue is.
---
The non-monotone timestamp issue is when certain MKV files containing h264 video fails to remux into a MP4. I mostly run into this with BBC content. The output that FFmpeg displays is an 'non-monotone timestamp' error. The patch that I am using can be applied to the FFmpeg source files before compilation. This has stopped all circumstances of the 'non-montone' error that I have run across.
You can apply this patch by using the terminal to 'cd' into your FFmpeg source folder. Then use the command:
| Code: |
patch -p0 < ../patch-non-monotone.diff
|
Where '../patch-non-monotone.diff' is the location of your diff file.
You should see the following if successful:
| Code: |
patching file libavformat/utils.c
Hunk #1 succeeded at 3099 (offset -6 lines).
|
Last edited by Iluvatar on Tue Dec 20, 2011 3:31 am; edited 1 time in total |
|
| Back to top |
|
|
cweb
Joined: 19 Sep 2011
Posts: 17
|
| Posted: Wed Dec 07, 2011 6:34 pm Post subject: |
|
|
| Installed your new version and now it seems to work on my machine with snow leopard. |
|
| Back to top |
|
|
Iluvatar
Joined: 29 Feb 2008
Posts: 335
|
| Posted: Wed Dec 07, 2011 7:02 pm Post subject: |
|
|
hmm ok it looks like I will discontinue the Universal package. The problem may lie with the MacPorts app which I use to compile. Instead of supporting the dwindling 32 bit Intel processor crowd I may just drop it and maintain a 64 bit build only. I can't imagine there are that many CoreDuo users out there anyways.
_________________
My pyTivo fork - Read link for changes
FFmpeg for OS X |
|
| Back to top |
|
|
quietlyconfident
Joined: 02 Jan 2012
Posts: 2
|
| Posted: Mon Jan 02, 2012 3:29 am Post subject: Re: FFmpeg Builds for Mac OS X |
|
|
| Iluvatar wrote: | ==Updated 12/19/11==
As other available FFmpeg builds for OS X have become out of date I have compiled a recent static build that I can distribute. |
I downloaded pyTivo and configured it per the instructions, along with your ffmpeg, and it did not work. It seemed to run fine, and the Tivo could see it and the list of videos in the video directory, but on selecting one of those videos, the expected option to transfer was not present.
I attempted to run ffmpeg for a test, which failed:
| Code: |
MyComputer:pyTivo myhomedir$ /Applications/pyTivo/ffmpeg
dyld: Library not loaded: /opt/local/lib/libmp3lame.0.dylib
Referenced from: /Applications/pyTivo/ffmpeg
Reason: image not found
Trace/BPT trap: 5
|
I turned on debug mode for pyTivo and the same thing happened in the logs. I believe that the above ffmpeg error indicates that it was not statically linked, as suggested in the original post. (or, I am doing it wrong). Is anyone else encountering the same difficulty? Currently, I'm building with macports, will see if that works. |
|
| Back to top |
|
|
Iluvatar
Joined: 29 Feb 2008
Posts: 335
|
| Posted: Mon Jan 02, 2012 3:53 am Post subject: |
|
|
| Crap. I must have messed up the build. Tested fine too. I'll have a new build up in a day or two. Please provide an update then to let me know if it worked. |
|
| Back to top |
|
|
quietlyconfident
Joined: 02 Jan 2012
Posts: 2
|
| Posted: Mon Jan 02, 2012 7:47 pm Post subject: |
|
|
| Iluvatar wrote: | Crap. I must have messed up the build. Tested fine too. I'll have a new build up in a day or two. Please provide an update then to let me know if it worked. |
Will do. FWIW, I was able to build with MacPorts (almost point and click) and it seems to work now, after a few reboots all around. Thanks. |
|
| Back to top |
|
|
Iluvatar
Joined: 29 Feb 2008
Posts: 335
|
| Posted: Tue Jan 03, 2012 2:15 pm Post subject: |
|
|
| quietlyconfident wrote: | | Iluvatar wrote: | Crap. I must have messed up the build. Tested fine too. I'll have a new build up in a day or two. Please provide an update then to let me know if it worked. |
Will do. FWIW, I was able to build with MacPorts (almost point and click) and it seems to work now, after a few reboots all around. Thanks. |
I have uploaded a build that should fix the issues. I use MacPorts to build these as well (just modified for a better pyTivo build) and I believe what happened was that I updated Lame without modifying the portfile to a static build first. It broke FFmpeg the next time I created a new build, but since I had Lame installed already I didn't notice the fault. |
|
| Back to top |
|
|
cweb
Joined: 19 Sep 2011
Posts: 17
|
| Posted: Wed Jan 18, 2012 9:52 pm Post subject: |
|
|
| Do you use the same "patch-non-monotone.diff" file, regardless of the version of the ffmpeg source code? |
|
| Back to top |
|
|
Iluvatar
Joined: 29 Feb 2008
Posts: 335
|
| Posted: Wed Jan 18, 2012 10:44 pm Post subject: |
|
|
| cweb wrote: | Do you use the same "patch-non-monotone.diff" file, regardless of the version of the ffmpeg source code? |
Yes I have. Although the patch may need updating for line changes depending on FFmpeg developments.
I have not tested it on 0.9 series however as it is fundamentally incompatible with pyTivo as it is right now, so I am unaware of it's necessity or not.
_________________
My pyTivo fork - Read link for changes
FFmpeg for OS X |
|
| Back to top |
|
|
Iluvatar
Joined: 29 Feb 2008
Posts: 335
|
| Posted: Fri Jan 27, 2012 5:27 pm Post subject: |
|
|
I have uploaded a new version - 0.8.10, see OP.
FFmpeg 0.9 and 0.10 have already been released but are incompatible with pyTivo currently. Read note in original post for more info.
_________________
My pyTivo fork - Read link for changes
FFmpeg for OS X |
|
| Back to top |
|
|
cweb
Joined: 19 Sep 2011
Posts: 17
|
| Posted: Sat Jan 28, 2012 6:20 pm Post subject: |
|
|
Thank you for the continued great work keeping us up-to-date with your timely builds.
Question: What features won't work in pytivo if one uses ffmpeg v0.91? I did one of my play around compiles of v0.9.1 and it appears to work just fine with it. I'm using it with pytivo, vidmgr, stream baby and haven't seen any problems. Although I haven't done any extensive feature testing, I've been able to play a variety formats.
Not sure what I'm doing right or wrong. |
|
| Back to top |
|
|
Iluvatar
Joined: 29 Feb 2008
Posts: 335
|
| Posted: Sat Jan 28, 2012 6:30 pm Post subject: |
|
|
| cweb wrote: | Thank you for the continued great work keeping us up-to-date with your timely builds.
Question: What features won't work in pytivo if one uses ffmpeg v0.91? I did one of my play around compiles of v0.9.1 and it appears to work just fine with it. I'm using it with pytivo, vidmgr, stream baby and haven't seen any problems. Although I haven't done any extensive feature testing, I've been able to play a variety formats.
Not sure what I'm doing right or wrong. |
Interesting. What pyTivo branch are you using? I tested 0.9.0 with the lucasnz branch and it didn't work at all. I don't remember the exact error but it was pretty much a complete FFmpeg failure. It's possible that there are different usage cases that I didn't test.
My statements were based on the new API changes introduced with 0.9+ that change the command line arguments that pyTivo uses. I documented them here While there are currently some deprecated commands that have an alias link to the new functionality there are others that have been completely removed already such as stream mapping.
I can probably upload a test build of 0.10 for people to work with who want to.
_________________
My pyTivo fork - Read link for changes
FFmpeg for OS X |
|
| Back to top |
|
|
cweb
Joined: 19 Sep 2011
Posts: 17
|
| Posted: Sun Jan 29, 2012 2:47 am Post subject: |
|
|
| I'm using Wmcbrine's branch and ffmpeg 0.9.1. Streaming works fine. Let me know if any other info would be helpful. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
