Skip to main content

Topic: Tremor issues (Read 2810 times) previous topic - next topic

0 Members and 1 Guest are viewing this topic.
Tremor issues
Hi,

I was able to get vobis tremor checkout from the tree. I am running it on visual studio.
The compilation went properly.

I am running into an issue as the output seems to be not correct and is not playble.

As suggsted in the file initialization.html i did the changes to make the code take input from FILE.

I think i made the mistake somewhere as when i dumped the output it shows me only four three kinds of bytes
eith 80 , 7F , FF, 00  in the whole file. This is supposed to be the PCM output file.

The input is playable by other OGG players faithfully.

I am running the code on Visual studio 2005 .

The code has not been changed except to take FILE reading as binary as passed as input . I have used simple fopen.

I would appreciate if somebody can tell me where i am going wrong.

thanks,



Tremor issues
Reply #1
BTW i am using the code from main branch http://svn.xiph.org/trunk/Tremor/

  • saratoga
  • [*][*][*][*][*]
Tremor issues
Reply #2
Did you get it to work without your modifications?

Tremor issues
Reply #3
Well, i have only changed the code to take input from file which is working fine as the vorbis is able to read the file and extract what it needs faithfully but still the output is not correct.

  • john33
  • [*][*][*][*][*]
  • Developer
Tremor issues
Reply #4
Your easiest option would be to use the standard oggdec and make the changes necessary to compile against the Tremor libs. I did this about 8 years ago, but I don't think much has changed at least as far as the API is concerned.
John
----------------------------------------------------------------
My compiles and utilities are at http://www.rarewares.org/

  • saratoga
  • [*][*][*][*][*]
Tremor issues
Reply #5
Well, i have only changed the code to take input from file which is working fine as the vorbis is able to read the file and extract what it needs faithfully but still the output is not correct.


So you didn't test the original code to see if it was being compiled correctly?  I would start with that . . .