[PROJECT] ProTracker v2.3D clone for modern platforms

[no9]

You are right actually. I use old Adobe Audition 3 for quick sample edits and apparently it opens it incorrectly. Never occured to me before and this is why I didn't try to open it in another program. Sorry for not doing it before posting here. Now I did check it in Foobar and Audacity and they read and play the same file fine. So possibly it is AA3 issue.

[8bitbubsy]

That might actually suggest that the output .wav is quirky (f.ex. odd amount of samples in the data with no padding sample, or nonsense chunk lengths). Some programs are written to handle quirky .wavs, and others aren't.
I'll look at the .wav writer closer some day.

[8bitbubsy]

This has now been fixed in v1.03. It was indeed related to a wrong chunk length when writing the .wav file.

https://16-bits.org/pt2.php

[Tigerskunk]

Just want to say thank you for this amazing software, 8bitbubsy!

[no9]

I missed that post and update. Thanks 8bitbubsy!

[no9]

Now I found this. High pitch warning!

[ Show youtube player ]

[8bitbubsy]

Not a bug if you understand how ProTracker really works.
Non-looping samples are in fact looping after they have been played (!), the first two sample points in the data are the loop points. This is why non-looping samples have a "Replen" of 2.

[no9]

I see. But this can't be reproduced in Protracker 2.3B and Melontracker on Amiga (emulated). The ones I checked. PT doesn't allow those bits to have any values.

[8bitbubsy]

Those trackers don't have the ability to hand-edit the sample data. I am in fact making sure that the first two bytes are always cleared on non-looping samples when doing other sample editing tasks. This has been thought about.

[no9]

Those trackers don't have the ability to hand-edit the sample data.

I managed to check this by using CUT command on prepared sound sample in sample editor.

So those two bits are cleared on module save in PT clone. Ok, I didn't know that. Thanks.

[Tigerskunk]

Maybe a stupid question, but, it it possible to have the channels pan 100% like it would be on a real Amiga on the Mac OS version?

I have a bit of a problem with my music sounding so different on the real machine.

[saimon69]

Milkytracker does the hard panning if that can help

[no9]

Originally Posted by 8bitbubsy

Those trackers don't have the ability to hand-edit the sample data. I am in fact making sure that the first two bytes are always cleared on non-looping samples when doing other sample editing tasks. This has been thought about.

On second thought - wouldn't it be better if those two bits was disabled from drawing in the first place?

[spoUP]

Will you ever add the possibility to sample directly in PT?

[8bitbubsy]

Originally Posted by spoUP

Will you ever add the possibility to sample directly in PT?

This was implemented some days ago.

[no9]

I found this module loads incorrectly in version 1.20

Dragon's Lair by Thunder
https://amp.dascene.net/downmod.php?index=72796

[8bitbubsy]

Originally Posted by no9

I found this module loads incorrectly in version 1.20

Dragon's Lair by Thunder
https://amp.dascene.net/downmod.php?index=72796

This song has a sample that is longer than 64kB, and it triggers a bug in the module loader. I'm fixing it now, but it will only load 65534 bytes max per sample!

[no9]

Oh, I got another feature suggestion. Because I again overwrote protracker.ini file while copying files into program folder from ZIP archive. Fortunately I made this mistake in the past and now I have backup of protracker.ini in protracker.ini-backup file.

This could be solved like Wordpress does. You could store default configuration in protracker-default.ini and read it when no protracker.ini file is present. Then create protracker.ini at first start of the program.

[no9]

Originally Posted by 8bitbubsy

This song has a sample that is longer than 64kB, and it triggers a bug in the module loader. I'm fixing it now, but it will only load 65534 bytes max per sample!

Ok, but there is a catch. By design Protracker didn't load samples longer than 64kB but there was a way to fool it to do so by packing samples with PowerPacker and eventually load and use them. There is not many such modules because the trick wasn't popular and probably wasn't compatible with some of the players but Protracker and Hippoplayer had no issue with that, as far I remember.

Btw. I also have much older version of your PT clone and it also loads it fine.

[8bitbubsy]

Problem fixed: https://16-bits.org/pt2.php
As said, the .MOD will still not play correctly, as sample 9 is now truncated to 65534 bytes. It fixes the rest of the samples being broken, though.

Originally Posted by no9

Oh, I got another feature suggestion. Because I again overwrote protracker.ini file while copying files into program folder from ZIP archive. Fortunately I made this mistake in the past and now I have backup of protracker.ini in protracker.ini-backup file.

This could be solved like Wordpress does. You could store default configuration in protracker-default.ini and read it when no protracker.ini file is present. Then create protracker.ini at first start of the program.

Sorry, I don't like this idea. I tend to add new features to protracker.ini, and I want most people to see them and use them. Most people are probably not changing too much in protracker.ini anyway. Just copy over the EXE and DLL if you only want to overwrite the program.