![]() |
Quote:
|
External Codec Error
1 Attachment(s)
Hello, it's been ages since i had an error !!
This Came directly from Xtool documentation Xtool version used 6.2 this is my wav.ini [Stream1] Name=wav Codec=wavpack BigEndian=0 Signature=0x46464952 Structure=Signature(4),FileSize(4),FileType(4),Str eam StreamOffset=-12 CompressedSize=FileSize + 8 DecompressedSize=0 Condition1=FileType = 0x45564157 Condition2=FileSize >= 4096 this is my xtool.ini [wavpack] Encode=wavpack.exe -hh -x4 <filein>.wav <fileout>.wv Decode=wvunpack.exe <filein>.wv <fileout>.wav i have been unable to make this even detect the sample FLAC internal codec works and so any other NOTE: i use this as standalone and not in FA for testing purposes |
xtool.ini:
[wavpack] Encode=wavpack.exe -hh -x4 <filein> <fileout> Decode=wvunpack.exe <filein> <fileout> or [wavpack] Encode=wavpack.exe -hh -x4 - - <stdin> <stdout> Decode=wvunpack.exe - - <stdin> <stdout> |
Quote:
it's a bug confirmed, it's been fixed already |
Update available
Changes - added universal lz4f scanner - fixed issues with database feature - fixed issues with executable plugin support - updated lzo codecs |
Update available
Changes - fixed issues with lzo2a and lzo1c codecs |
XTool v 0.6.4
Code:
[0] Processed lzo2a stream at 00000000199339FB (6669 >> 32768 >> 6669) using v999 successfully |
Update available
Changes - updated oodle scanner - remove xdelta support from oodle and lzo codecs (crc mismatch often generates large diff files) Notes I've been getting reports of xtool taking a long time to process oodle streams (or getting stuck) so I reworked the scanner. I reverse engineered the code of oo2rec (I lost the source code) and rewrote parts of the code so xtool should produce better results while being faster. There is a parameter rework as well, some people may know of the "n#" parameter which when set increases the chances of xtool capturing a stream. The default value now is 32, can be increased to 64, 128... Up to you, there is no limit just keep in mind that increasing this value also means longer precompression times. Results on DOOM Eternal's "gameresources_4_1.streamdb" oo2reck Code:
Compressed 1 file, 1,353,405,353 => 2,584,084,262 bytes. Ratio 190.93%Rumour has it that it's still processing as we speak (stuck on 5.7%) :rolleyes: xtool 0.6.5 (-mkraken:l6:n128) Code:
Compressed 1 file, 1,353,405,353 => 2,589,860,614 bytes. Ratio 191.36% |
Quote:
it's fixed :P , adding one big file and all libraries inside along with all versions of xtool isnt a good idea |
confiused . .
xt 065 , ( same result with other version ) https://blogger.googleusercontent.co...147/frusta.png |
Hi guys!
I need a little help.... Something is wrong here. Tried to precomp a file with deduplication ,but XTool 0.6.5 doesnt make it. It looks like it ignores the corresponding parameter,even .bin file not created! V0.3.1 works fine! What am i do wrong? [External compressor:x065-dedup] header = 0 packcmd = xtool065\xtool.exe precomp -mzlib -c32mb -t100p --dbase --dedup=chor065.bin - - <stdin> <stdout> [External compressor:x065-nodedup] header = 0 packcmd = xtool065\xtool.exe precomp -mzlib -c32mb -t100p - - <stdin> <stdout> [External compressor:x031-dedup] header = 0 packcmd = xtool031\xtool.exe precomp -mzlib -c32mb -t100p --dbase --dedup=chor031.bin - - <stdin> <stdout> [External compressor:x031-nodedup] header = 0 packcmd = xtool031\xtool.exe precomp -mzlib -c32mb -t100p - - <stdin> <stdout> Results : Xtool 0.3.1 ,deduplicated : 40.2 GB Xtool 0.3.1 ,not deduplicated : 42.9 GB Xtool 0.6.5 ,deduplicated : 42.9 GB Xtool 0.6.5 ,not deduplicated : 42.9 GB All processes finished without error. V0.6.5 is the "pure" version ,directly from Zee's ZIP-file... Btw where to insert --verbose command? Only one place is accepted in my experiments ,but no verbose infos are displayed... |
Quote:
|
You can make a batch file near xtool.exe and drag&drop a file onto it. This way you don't use freearc for it.
Example Code:
@echo off |
Nobody ? :(
Found. Damn... Parameters were changed... |
Quick question, or I guess just asking for some clarification, in regards to "bms2xtl", can you only process a given file with your generated database, if the codec is one that xtool supports? So for example xtool wouldn't be able to process a COMTYPE if it isn't deflate, lz4(hc/x/f)... etc.? I guess what I'm asking in essence is am I correct in saying external, quickbms-native COMTYPEs aren't supported.
|
| All times are GMT -7. The time now is 04:10. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2026, vBulletin Solutions Inc.
FileForums @ https://fileforums.com