Search found 155 matches
- Tue May 26, 2015 7:59 am
- Forum: Help and Support
- Topic: File could not be parsed
- Replies: 6
- Views: 15470
[Solved] File could not be parsed
Good - enjoy!
- Sun May 24, 2015 4:47 pm
- Forum: Help and Support
- Topic: ffmpeg has a return code of 139
- Replies: 23
- Views: 37530
Building: ffmpeg
Played around more with the long option list from https://evermeet.cx/ffmpeg/ - had to convert to "with"… Got it built but without three options: --with-libvpx --with-avisynth --with-gpl Still building 15.8 MB. build command: brew install ffmpeg --with-fdk-aac --with-ffplay --with-freetype...
- Sat May 23, 2015 11:20 pm
- Forum: Help and Support
- Topic: ffmpeg has a return code of 139
- Replies: 23
- Views: 37530
Re: ffmpeg has a return code of 139
OK - sounds good - latest is what they look for, Xcode 4.6.3 was for 10.7.5 but the "Note" may apply for any version. Attached are my build notes edited after completion. There were a few iterations trying to resolve some of the errors. Not sure exactly which operation fixed each. You code...
- Sat May 23, 2015 2:05 pm
- Forum: Help and Support
- Topic: ffmpeg has a return code of 139
- Replies: 23
- Views: 37530
Re: ffmpeg has a return code of 139
yes - cleaning up my notes during the build. Could you beta test it for me since your system is virgin and I don't want to reinstall this one! if yes - what is your system configuration(s)? if 10.7 or 10.8, install or update to: Xcode 4.6.3 ( https://developer.apple.com/downloads # search: "xco...
- Sat May 23, 2015 1:27 am
- Forum: Feature Suggestions
- Topic: Also don't show the word "the" on "Ignore the word 'the' while sorting"
- Replies: 3
- Views: 6840
Re: Also don't show the word "the" on "Ignore the word 'the' while sorting"
Understood. Then these are two different issues.
The option you want enhanced is for video titles (and others), maybe there should be (yet) another option to cover your issue. This makes sense.
Note: I only use UMS now for videos.
The option you want enhanced is for video titles (and others), maybe there should be (yet) another option to cover your issue. This makes sense.
Note: I only use UMS now for videos.
- Sat May 23, 2015 1:17 am
- Forum: Help and Support
- Topic: ffmpeg has a return code of 139
- Replies: 23
- Views: 37530
local build ffmpeg with libass
Summary: The 139 error was a Segmentation Violation corrected in the latest 2.6.2 version. This led to another error: DEBUG [ffmpeg-1-2] [AVFilterGraph @ 0x7faa42d01360] No such filter: 'ass' DEBUG [ffmpeg-1-2] Error opening filters! I decided to build it locally. Their directions were lacking impor...
- Sat May 23, 2015 12:52 am
- Forum: Feature Suggestions
- Topic: Also don't show the word "the" on "Ignore the word 'the' while sorting"
- Replies: 3
- Views: 6840
Please don't do it - it will get ugly fast!
On this I will respectfully disagree - strongly. The titles are registered and recorded as the studio intended. To delete "The" makes it confusing when searching and looking online and here. The titles are what they are. Ignoring "The" looking at a sorted listing is easier than t...
- Fri May 22, 2015 2:50 pm
- Forum: Help and Support
- Topic: Subtitle & Transcoding Information
- Replies: 5
- Views: 7081
Re: Subtitle & Transcoding Information
Play with this: - Transcoding setings / FFmpeg / FontConfig Embedded Fonts No such option. Tried: "Defer to MEncoder" - no effect - Transcoding setings / MEncoder / FontConfig Embedded Fonts + Use SSA/ASS Subtitle Styli Both were checked, tried unchecking - no effect - Transcoding setings...
- Fri May 22, 2015 2:02 pm
- Forum: Help and Support
- Topic: Subtitle & Transcoding Information
- Replies: 5
- Views: 7081
Re: Subtitle & Transcoding Information
Progress: it was not easy but I succeeded in building a static ffmpeg binary and no 'ass' errors: DEBUG 22:02:30.797 [ffmpeg-1] Starting /Users/umsmkv/UMS_J8/ums_OSX-Java8_x2/target/ums-5.1.2_x2-distribution/Universal Media Server.app/Contents/Resources/osx/ffmpeg -y -f lavfi -i nullsrc=s=720x480:d=...
- Fri May 22, 2015 1:32 am
- Forum: Help and Support
- Topic: File could not be parsed
- Replies: 6
- Views: 15470
Re: File could not be parsed
one of the non-parsed file was : "01 - Intro.flac" I just renamed the file to "01_Intro.flac" (with no space) Oh yes - missed that point. In the "parse()' routine it does a bunch of tests which, if they fail, all report "parse error". Very misleading. The bandwidt...