Sawndz 0.12 - RELEASED

[Jaklub]

sox.sourceforge.net -> Sourceforge's File Release System -> take the zipped win32 version

[vm19961126]

hmm? i have a question, what do you meen by support longer sounds, do you meen you can replace for example a 0.75 sec. sound with a 2.00 second sound?

[Jaklub]

yes

@donaldthescotishtwin: I saw your latest announcer call upload. Hex packets created by Sawndz should always work. I never had any problems with these and I got no reports they don't work. FYI, offsets the generated hex packets should be inserted to are in filenames.

[DTST]

Well my hex packets where created by just pressing convert and Insert then I sent them to ssbbtailsfan to test and he said the sound was too fast

[Jaklub]

Just tested your Roy call. First, the sample should have 1 channel. Because it has 2, the sound is slowed down. Second, the hex packet issue is caused by your sound being too long (0,2 second is a lot). If it wasn't, it would work fine and ROB's call wouldn't be interrupted.
After I inserted the generated hex packets, the only issue was ROB's sample being a bit cut at beginning.
You see, the sound hex packet is nothing more than copied spd file expanded to wave size - and that's the reason why it didn't work.

The sound was too fast probably because ssbbtailsfan got only the sound packet without packet with fix data.

I'll fix automatic hex packet creation in new version. It's an easy fix, so it will work.

[DTST]

You mean robs announcer call is interrupted when Inserting the hex packets? On my game it's fine but I didn't use sawndz 0.07 to make it also I sent ssbbtailsfan both the packet and the fix packet

[Jaklub]

What I mean is that the issue with Roy hex packets was not the speed, but the fact your sound is too long. Although it doesn't screw up the insertion in Sawndz, it does screw up the hex packet - and that will be fixed in next version. Thank you for that info, btw.

About too fast sound, it seems like ssbbtailsfan didn't insert the fix packet. I think one of you made a mistake, as the speed wasn't the issue with the packets.

[DTST]

NP does it sound accurate when inserted the way the text file says? Because I typed down exactly what I did before I inserted it

[Jaklub]

Yup, manual insertion of your sound works fine.

[vm19961126]

hmm okay then, but when I tried to insert a longer sound,the sound was just cut so it was the same length of the original...:S

[Jaklub]

Because it does not work that way.

Frequency Divide field is the key. I've tried to explain it once:

I'll try to explain it.
Let's say we have a sound effect that can be only one second long. We want to insert a sample that is two seconds long. To do this, we have to speed up our sample twice (so it fits into the limit) and save it in original sound frequency. In Frequency divide field we have to type 2 (because the sound we want to insert is twice as long as the original sound). Frequency of sound will be divided by this value (hence the name of the field). And so, we get 2 seconds long sound.

If that isn't clear enough, for now stick to using Generate sound.wav in newest Sawndz till I stop being lazy. That option was made to make lives easier.

[vm19961126]

hmmm... but that way, it isn't realy supporting longer sounds.. cuz the sounds are just as long as they has to be because of the limit... but I guess I just have to do it this way :P

[Jaklub]

Lower the frequency -> Have a longer sound -> PROFIT

For now, that's how it has to work.

[DTST]

to lower frequency change the numbers in frequency divide in insertion options

[Jaklub]

New version up.

- Generate sound.wav bugfixes.
- Now automatic hex packets work even if sound was originally too long.

http://www.mediafire.com/?to0plxtz80k9pib