![]() ![]() But, those that only support byte-based positioning regardless of if UMS had done all it should correctly, ultimately cannot seek when transcoding. UMS doesn't handle all of these details properly, so there are probably some renderers where it could work had UMS done it correctly where it's not available. That said, it's not quite that simple, as there are multiple details I left out, that can impact what the renderer supports and not. This means that renderers that use time-based positioning does support seeking while transcoding, but those that only accepts byte-based positioning doesn't. The duration in time is known since it is the same as the duration of the source file. When transcoding, the duration in bytes in undefined, there's no way to know that until you have transcoded the whole file (aka played through it). The fundamental problem is that some use byte-based positioning (by number x from the start of the file) and some use time-based positioning. In short, seeking while transcoding works on some renderers but not on others. That said, the duration (in bytes, not seconds) would still be unknown so I don't quite see how it would solve anything.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |