#AtomicAudio: Tools for CRI audio formats (ACB, AWB, ADX, HCA, etc.)
1065 messages ยท Page 2 of 2 (latest)
do yk why this would happen?
D:\git\AtomicAudio\src\AtomicAudioPy>python -u AtomicAudioTool.py add_simple_track --input-acb-path D:\Games\P5X\client\bin\Media\Windows\BGM_battle_random_07.acb --input-awb-path D:\Games\P5X\client\bin\Media\Windows\BGM_battle_random_07.awb --output-acb-path .\BGM_battle_random_07.acb --output-awb-path .\BGM_battle_random_07.awb --cue-id 0 --base-track-num 1 --new-audio-type HCA --new-audio-path C:\tools\KwasTools\BGM_battle_random_07.awb_0x403ffa00\00008.hca
Failed to read file!
0 b''```

oh its failing on the hca (?)
Apparently, but the next part looks like it should have read the HCA just fine....
Can you link the HCA?
Yeah, empty string printed after really means the assert shouldn't be failing....
oh wait even if the assert fails it still makes the file oops
...ah, could you also share the AWB? I don't know if that would affect anything, but it is one difference between out setups.
nevermind i was just extremely unlucky
actually yeah it seems very very heavily weighted towards playing the added tracks for some reason but i have no idea what would cause that
and sometimes is playing silence
Not sure why it'd be weighted toward the new ones. There is a probability that can be set somewhere, but I don't see it in here.
Hm, I don't see the loop start and end defined for the new HCA.
it does have ones, at least foobar says it does
Oh, I see what I was doing wrong. Also, looks like I don't enable loops for new sounds, oopsies....
Let me fix that....
ACE has some sort of weight option
and its editable
OK, I pushed a bunch of changes -- fixing loops in added cues/tracks, making RandomNoRepeat the default, fixing some padding issues, making sure track values (which may relate to weighting, to at least some degree) are actually updated.... Anyway, hopefully SOME part of this helps.
you can check the modified BP01 I've sent before
the new cues I've added have the modified weight values
if not i can send it later when I'm on the PC
Hm, yeah, I can't find it in here -- if you could send it later that'd be great ๐
it seems like they're stored in the Sequence "TrackValues" field
i.e the value for BGM_battle_random_07.acb seq 0 is 00640064006400640064006400640064 which is just 8 uint16s, all 100s
man and here i was like
"ok i have 6 tracks, so i have to give them all 100/6"
i cant believe using 100 on all just works
atlus PLEASE
๐คญ
Yeah, I just wasn't updating that before for added tracks. But I have weirdly yet to see anything but 100s in there in vanilla ACBs...
๐ฏ
This stuff re: TrackValues was in the pushed changes I mentioned above, so should all be good ๐
Lmk if you notice any improvement with the new version, aaron.
yeah it's working perfectly now. vanilla tracks and new tracks are playing about as often as eachother
Yessss
I'm glad!
Does this tool allow for grabbing/printing all the cue ids from an acb?
The print_info command will give you all details about each cue, yeah, although there's a lot in there beyond IDs.
oh yeah, i see what you mean ๐
i tried it on system.acb and it seems to dump the info... along with complaining about failing to read the file (i assume due to the encryption)
What was the complaint? ๐ค
Whyyy does it keep doing this ๐ญ I think I'm just gonna get rid of that assert, lmao.
๐ป
The string being empty literally means it shouldn't have an error 
But this has happened to multiple people now, so a bug is a bug....
Cool, let me know if there's another format for listing cue IDs that would be (more) helpful 
@junior bear Send over whichever ACB if you want me to grab + share the log for it with all the cue IDs later โ๏ธ