Messages

1

SFML projects / Re: sfeMovie Project [v1.0 released] [looking for developers]

« on: November 20, 2014, 08:31:36 am »

Sorry about my conspicuous absence just as I started getting involved with things. I had hoped this semester would be as easy as my previous one and so I would have plenty of time to work on side projects. Unfortunately, this was not the case. I keep intending to get a little bit worked on here and there but life keeps getting in the way.

Depending on familial obligations I may or may not have time to get some work done over the holidays.

2

SFML projects / Re: sfeMovie Project [v1.0 released] [looking for developers]

« on: August 31, 2014, 07:47:51 pm »

You would open a command prompt and navigate to where msys.bat is. Then you would use:

Code: [Select]

PATH=d:\path\to\mingw\bin;%PATH%
msys.bat
You could also edit msys.bat to do this for you when you run it.

If you just run "make" then you don't need to select a specific target, so you can disregard ALL_BUILD. If you really want to know what ALL_BUILD is, it is just a target that cmake generates that ensures that every other target is built...but the default for "make" without any parameters is to build all targets.

I haven't worked much with Ceylo's build system before I started tweaking it on my own so I don't know why your bash shell would be switching to a cmd shell in the middle of "make install"

3

SFML projects / Re: sfeMovie Project [v1.0 released] [looking for developers]

« on: August 28, 2014, 09:21:13 pm »

Ok but the MinGW version shipped with QtCreator does not contain MSYS, can i download it separately, place it on the directory of my MinGW and use it on the branch?

Yes, i used mingw32-make inside the cmake directory. I use Qt Creator as my IDE.

MSYS can be set up to work with ANY mingw installation, as long as you add your mingw bin directory (the one with gcc.exe etc...) to your PATH environmental variable BEFORE starting your MSYS shell.  You could even use the same MSYS environment with several different compilers as long as you were careful about prefixes for any libraries you "install"

Using GNU make inside an MSYS environment should work fine, and is much more flexible than mingw32-make in many regards. FFmpeg uses a completely custom build system (it is NOT autotools no matter how much it may look like it) and mingw32-make was not designed with this in mind.

4

SFML projects / Re: sfeMovie Project [v1.0 released] [looking for developers]

« on: August 24, 2014, 04:53:58 pm »

For now they are the main competitors for the next web standard vs H.265 video and AAC audio.

The only major usage of either codec right now is via Youtube where newer submissions are being converted to these formats. Otherwise I know Mumble is transitioning its clients to use Opus as well, and there are several 4k TV manufacturers on-board to support VP9 (but probably H.265 as well).

5

SFML projects / Re: sfeMovie Project [v1.0 released] [looking for developers]

« on: August 24, 2014, 08:27:21 am »

Another set of free codecs you can add to your legal page list:
Opus audio
VP9 video (available through newer libvpx builds, still kinda early in its life but quite usable)

FFMpeg has no support for it yet that I've seen, but another one to watch for is Daala.

6

SFML projects / Re: sfeMovie Project [v1.0 released]

« on: September 27, 2012, 02:17:17 pm »

From what I know now, dirac is the only "free" codec you don't have listed in the faq.
http://diracvideo.org/

libschroedinger can be built into ffmpeg for dirac support, but it has a dependency on liborc, which has given me headaches trying to build in mingw before, so windows support would be difficult to achieve (unless mingw builds have been fixed in the last few months).

From a cursory search, I couldn't find any mention of patents on any kind of subtitle format, but I'll try to contact one of the developers of libass and see if there are any "gotchas".

Stream selection support and subtitle support would be great, but give me some time to break into the code before I start bombarding you with technical questions.

7

SFML projects / Re: sfeMovie Project [v1.0 released]

« on: September 27, 2012, 11:15:20 am »

Your FAQ doesn't list matroska, MKV or WebM in the list of supported "formats" (what I call containers), so I assumed it wasn't supported in the binary releases. Sorry for the misunderstanding!

I am very familiar with video containers and codecs, and was looking for a solution that would support everything I need without royalty encumbrance. I am settling in on matroska/webm, ogg, and wav for supported containers (there will be audio-only parts to the program as well), with VP8 and theora (perhaps dirac if they fix some of the portability issues with libschroedinger) options for video and vorbis, FLAC and PCM options for audio. If embedded subtitles can be supported, I'd also like to support ASS/SSA/SRT (need to do some more research on whether patents cover any of these).

Subtitles can be embedded in a matroska container, so if you wanted to add in support for them, that would be a good place to start. I'm not sure if WebM subset supports subtitles or not, but it is basically a subset of the Matroska container. After I've had some time to familiarize myself with sfe::Movie a bit, I may look into adding in subtitle support myself.

On a side note, how well does sfe::Movie support containers with multiple video or audio streams? It isn't important for my purposes, but you do have that possibility with mkv.

8

SFML projects / Re: sfeMovie Project [v1.0 released]

« on: September 27, 2012, 08:56:46 am »

Two things I would like to see, and I was wondering if they can be accomplished with a simple rebuild of ffmpeg:

Matroska format support (patent-unencumbered container format that is highly extensible).

Libass support for advanced subtitle rendering.

The first one is pretty important to me, while the second is something I would like to make available, but I understand if I need to implement it separately with the simple text drawing available in sfml. Libass can be a major CPU hog if you abuse its capabilities too much, but anything is a better option than hard-coding subtitles onto video (not only can you not turn them on or off, but they compress particularly poorly causing artifacts around text and bit starvation in other areas of the video).