Pascal port of the integer-only OGG vorbis decoder TREMOR

[Andru]

Great work! But is there any performance comparison of C and Pascal version of this library? Because ARM platform(where it will be useful) is very performance-sensetive, and it will be interesting to know how much this port can win/lose in performance.

[paul_nicholls]

Very very nice work Benjamin! Thanks for sharing, and your continuing great work as always

[BeRo]

Great work! But is there any performance comparison of C and Pascal version of this library? Because ARM platform(where it will be useful) is very performance-sensetive, and it will be interesting to know how much this port can win/lose in performance.

I did the port mainly for the ARM android target, because I'm working on a commerical android game (for currenr midrange and highend ARM-based smartphones and tablets) in the moment, where I've needed it, see the few ARM inline assembler source parts of it.

And i've uploaded a new version now, which fixes a small bug in the codebook decoder (which had decline some few but non-corrupted oggs falsely), and where I've optimized the memory allocation stuff a bit.

[Andru]

because I'm working on a commerical android game

Hmm, then why do not use a Tremolo? It's 15%-20% faster then Tremor.

[code_glitch]

Andru - in the context of the real world, why use windows over linux now we have wine 1.4?

Either way, this is indeed a very nice bit of news! Once again I am in awe at what you've managed to cram into such little space... I will definitely be checking this out later on

[Andru]

Andru - in the context of the real world, why use windows over linux now we have wine 1.4?

Because WINE is too buggy for support Windows software I just asked, maybe BeRo didn't know about Tremolo as better solution in performance. And I agree that his work is indeed great, and good that there is asm code inside this port, because I have a pity experience using PasJPEG and PasZlib. These solutions are too slow and better to use original versions.

[code_glitch]

Lol. I guess you do have a point, but now we have some .NET 3.5 goodness and most of office 2010 running smoothly, I can't really complain

As for speed, I find ports tend to be a tad slower than originals unless it has been 'over-viewed' by the person porting the code and improved upon. However, for things that are indeed very slow, I prefer to dump it into a separate thread, which on dual core system makes is appear as fast as it should be. I know the clock cycles are still going in, but from a user point of view, it can be quite the neat solution