> > My latest code test can be found here: > > > > http://aug.ment.org/tmp/encode.c > > > > I've updated it so that it writes audio and video data at half second > > intervals. > > > > For testing, I am only using "twos" as the audio format. > > > > Whenever I set up gmerlin_plugincfg to use quicktime encoding and mov > > container format....ALL seems to go great. I can encode all audio > > and video formats. > > Just curious: Did you also try e_ffmpeg with the fixes I checked in?
with FFMPEG AVI/AC3/MPEG4 - video is just grey AVI/AC3/DIVx - video is just grey AVI/AC3/MJPEG - still cannot start the encoder due to colorspace mpeg1, wmv etc say they are not supported by AVI > > However, if I use the quicktime API, but encode with AVI > > containers....the audio is messed up! Do you get the same thing? > > I would, If I used TOWS with AVI.... > > > Am I missing something while encoding? > > TWOS (big endian PCM) is quicktime only. You should get a warning about > that. > > Try SOWT. It's little endian and supported in both mov and avi. Is there a reason why these options show up in cases that they are not allowed? This seems like a user interface or structure issue; if the options are illegal, they should not be there, I think. Any way to guard against this? > Difficult to decide what to do for these cases. In e_ffmpeg I simply > reject unsupported combinations of codecs and containers (with the > disadvantage that I sometimes also rejected valid ones like AC3 in AVI). Couldn't this just be a tree structure in the registry? > In libquicktime I have compatibility flags for the codecs (which should > trigger the warnings). But these flags are defined according to what the > "official" software plays. But there are some very interesting codecs > (like ffv1, the best and fastest lossless codec I know), which would be > rejected in all cases :) ok, I see. But, still, if gmerlin can make it and play it...it should be ok. If gmerlin cannot make that combination of codecs into a playable stream, it should not be an option. Maybe I have not understood something. > Maybe an option "Reject unsupported/incompatible codecs" would be an idea. I think that should be default, if possible. ------------------------------------------------------------------------------ The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com _______________________________________________ Gmerlin-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/gmerlin-general
