xma_parse09 correct syntax by event2020 at 9:09 AM EST on December 30, 2010
Hi.
Boy oh boy what a great site and thank you so much for creating such fantastic tools.
I am having some problems using xma_parse09 but the problems are caused by me not being sure of the correct syntax to use.
I have a file which I shall call file.fsb.xen.
I used XEN to extract the fsb from the Xen so now the file is called file.fsb.
I then used xmaextract which gave me 4 xma files: file_Channel_1.xma, file_Channel_2.xma, file_Channel_3.xma and file_Channel_4.xma - which I presume are the 4 channels which the .fsb file contained in a multichannel xma.
I understood that I then needed to use xma_parse09 to convert these files to a format that ToWav could then convert into wav files.
So I placed one of the 4 wma files into the same directory as xma_parse09. Opened a CMD box and used the syntax:
xma_test file_channel_1.xma -r channel1
As I am not that familier with working out offsets or blaock and data sizes I thought I'd leave theses switches blank so that xma_test used the defaults.
When I ran it I got the following report and error:
I believe this is an issue that I provide a fix for in xma_test 0.10. Get that and add the -I (uppercase i) option (to ignore packet skip) to your command line.
I believe that xmaextract parses out the individual streams but leaves the packet skips when it cats them together, so the resulting stream wants to skip around.
If this works, you will also need to attach a header to the resulting files so that toWav will recognize them. I believe this one will do the trick.
edited 9:30 AM EST December 30, 2010
Wow and thanks by event2020 at 11:39 AM EST on December 30, 2010
Hi hcs,
I cant beleive how fast you replied so thank you for that.
I will certainly give V0.10 a try but for those who dont know how (like me) to attach a header to the files, could you kindly give me a quick idiot proof run through.
I presume the files I have to attach it to are the ones that xmaextract extracts, in my example these are the ones called:
file_Channel_1.xma, file_Channel_2.xma, file_Channel_3.xma and file_Channel_4.xma.
I also assume that I will need to use a hex editor - I have Hex Workshop V6.
If I open file_Channel_1.xma in Hex Workshop I can obviously see all the hex code and I know that I also have to open the header you linked to and then >select all > copy
but then I have no clue what so ever about where to add the code from the header into the xma?
From what I have read on the various forums - The new header code is cut n pasted into the beginning of the xma but do I then have to delete any code to make way for the new?
Again in the forums I see people talking about after inserting the new header, you have to delete the second block and/or the third and its at that point my eyes glaze over and I start to gibber as Im afraid my newbie lack of knowledge kicks in.
Im sure you have more than enough to do with out people like me bothering you but as well as helping me, your reply may help others also.
In fact, as a thank you - I'd quite like to put together a step by step guide to replacing xma headers as I am sure many also dont have a clue like me.
Thanks again..
didnt work another parse error by event2020 at 2:20 PM EST on December 30, 2010
Hi
Thought I'd give it a go and I did exactly what I did before upto the point where I used xma_test010.
I placed one of the files that xmaextract created "filename.fsb_Channel_1.xma into the same directory as xma_test010.