Content deleted Content added
→so rotten as to be unusable: new section |
|||
Line 6:
== so rotten as to be unusable ==
I'm sure the codec itself is fantastic, but i'm having trouble getting to a point where I can even make an objective assessment. Is anyone else finding the supplied user interface so buggy and mind-bendingly slow / bottlenecked as to be functionally broken? I've ended up at this page sort of as a sideline of going off to see if anyone else has used that SDK to make something a little quicker. IE something that doesn't typically take two or three minutes to switch between certain tabs, or entries in a source list, when I click between them on setting up an encode from one or more 250-mb-ish (15 minute) SVCD MPG2 sources. God only knows what it's doing. Perhaps re-reading and re-analysing each file in full every. single. time. or something. Also, having some kind of batch encode function would be nice... just figured out that if I hit Start now, everything on my source list would be lumped into the same file with the same name (or perhaps the last one on the list would overwrite everything that went before). It manages to do the clever thing of automatically naming it when you load in - and remembering the basic encode settings (eg bitrate) - but doesn't auto change the name or allow you to set "use same as input" or any kind of renaming rule (and forgets even the vaguely more advanced settings - like resolution).
Arrrrgh. Most freeware tools work better than this. Was it not use-tested before release? so, off we go, maybe there's some in the article maintext? [[Special:Contributions/193.63.174.10|193.63.174.10]] ([[User talk:193.63.174.10|talk]]) 17:02, 4 August 2009 (UTC)
| |||