ProTracker 2.3F

[Ywe, IT-Scenes]

I think the move to med-res was correct, and suits several channels later. You really should move to 4K in these days aswell.

[no9]

I would welcome a tracker with ability to modulate loop parameters. Either by pattern commands or envelopes. Kind of this [ Show youtube player ]

[Ywe, IT-Scenes]

Van Der Falk used lots of stuff like this: [ Show youtube player ]

[Ywe, IT-Scenes]

PS: [ Show youtube player ]

[no9]

Originally Posted by Ywe, IT-Scenes

Van Der Falk used lots of stuff like this: [ Show youtube player ]

Yeah, he was great. But unfornately no Protracker allowed us to do this, seemengly simple, thing.

[Ywe, IT-Scenes]

It was enthusiast scene oriented. You could have done that, connected external chorus, reverb, it would have sounded great, and 8-bit is tight on drums.

Some did even use c64 profesionally, with software like Supertracks etc. Name familiar yes, and probably was the forerunner to "tracking". Its author went on to Emagic that was bought by Apple, and they are doing Logic now.

Many think the plugin thing has become a mess though, and so there is a resurgence in tracking interest. I suggest Protracker 2m (second millennium) as said before.

And instead of now typical loudnesswar sound, 4 submix oriented, with just a few mastering things (eq, softclip, 2db limiting).

[Ywe, IT-Scenes]

Med-res as used in Octamed was more professional oriented.

https://www.youtube.com/channel/UCi7...4Y4UTuIigrG9GQ

Serenity.

[Jope]

Originally Posted by 8bitbubsy

But then I got reminded about how hard it would be to write UI code, especially for bitplanes. I thought about doing chunky-2-planar and write the UI in C, but that would require a rather fast Amiga.

Please make the attempt anyway to have it run on a slow Amiga.. So many tools are needlessly heavy because a light UI requires more effort.

[britelite]

Originally Posted by Jope

Please make the attempt anyway to have it run on a slow Amiga.. So many tools are needlessly heavy because a light UI requires more effort.

And considering the original FT2 runs in a bitplane mode anyway, there's no reason why an Amiga-version couldn't

[Ywe, IT-Scenes]

Trackers really started shining with the compact save/load module format. Where before ST-0x disks were used.

[ Show youtube player ]

One can still see 8chan ST-01 modules, but it didn´t take off, due to the enthusiast focus. Some effort to fix this may be the prosumer label. That seems to have faded aswell. And that is the big challenge, to get momentum going with a higher sometimes elitist goal. Which really was defining of the amiga culture.

[8bitbubsy]

Originally Posted by britelite

And considering the original FT2 runs in a bitplane mode anyway, there's no reason why an Amiga-version couldn't

It's a pain in the butt to work with, and a real motivation killer. It's better to have a slower version than having none at all, imo.
My motivation to create a new tracker from scratch for Amiga is already very low, and any way to make the process faster and simpler is golden.
Of course it wouldn't require 060 and RTG and stuff, that would make it a luxury program that only a few people could run (on real hardware).

Anyway, I have updated PT2.3F today with a >64kB bugfix in the parallel port sampling code (thanks to echolevel/Syphus for finding these bugs):
https://16-bits.org/PT23F.LHA
https://github.com/8bitbubsy/pt23f

[Jope]

Thanks for continuing to make PT2.3 better. <3

[8bitbubsy]

There seems to be some other bugs with parallel port sampling, the tracker might crash when editing the newly sampled sample. I'll look into it one day and report back.

[syphus]

Originally Posted by hairball

Hi, I tried the PT2.3F download but can't get it to work. Seems like there isn't any actual software in the file, just a bunch of readme files.

I have the 2.3F bootable disk by Syphus, is that the latest version?

Any help is appreciated, I'm a noob at this emulation stuff

Sorry this is a bit late hairball, but I hope you got it sorted.

As 8bitbubsy said, there's no affiliation between us or the two versions - I released my build (with some customised graphics and a few quality-of-life tweaks that suit my workflow) because some people spotted it and asked if they could try it. The bootPT project is simply an attempt to give newcomers to Amiga tracking an easy, bootable way to fire up a stable version of PT with all the latest fixes and features and dive straight into tracking (it's got some chip samples on the disk too).

As quickly as possible, whenever 8bitbubsy updates his version (which I refer to as the 'official' version of PT2.3F, insofar as any Protracker can be considered official ), I merge his fixes into my code and update bootPT. Or it'd be more accurate to say that I merge my customisations into a copy of his latest code, then assemble that, then test to make sure my changes haven't broken anything.

I hope it's not caused too much confusion - I try to be clear about things in all documentation and I provide links to 8bitbubsy's site so that people can get the canonical version. He's done an amazing job, which only seems more impressive if you spend any time looking at the nightmare of ASM he's tidied up, and he's been very accommodating of my suggestions, bug reports and the one fix I managed to figure out (despite my horrible ASM skills!)

Btw, one more thing I maintain in the bootPT project is an up to date and formatted copy of the Protracker Helpfile - originally written by Peter CRAYON Hanning in 1992, updated sporadically thereafter, and now including all of 8bitbubsy's fixes. Oh, and the 'secret' features he discovered while tidying up the code I tidied it up it for myself so I could easily ctrl+f on a single page in a phone/desktop browser to check a shortcut or some feature's behaviour. If it's useful to anyone else, that's a bonus.

PT HELPFILE

[saimon69]

What i miss is multithreading and the possibility to copy/paste patterns between different threads like in milkytracker
[EDIT] Forgot i asked this some time ago and got told is not going to happen, ok...

[8bitbubsy]

Ok I fixed the PT2.3F parallel port sampling bug, and also removed some other nonsense because I have now properly bug-fixed the quadrascope routine to never read past allocated memory (hopefully).

https://16-bits.org/PT23F.LHA
https://github.com/8bitbubsy/pt23f

TODO: There are some strange Disk Op. bugs, like entering ghost directories, and not always re-reading the directory when changing dir mode (module/song/sample).

[syphus]

Awesome, thanks! Tbh those Disk Op. bugs sound like things I've noticed in PT2.3D since forever, especially not always re-reading the dir. I've always had to click on the [1] / [2] gadget to force a re-read, and it's good for safety to avoid writing over something you didn't intend to, or accidentally loading a sample as a module if you forgot to switch mode. I'll look at PT2.3D to compare though.

[Akira]

Originally Posted by syphus

Awesome, thanks! Tbh those Disk Op. bugs sound like things I've noticed in PT2.3D since forever, especially not always re-reading the dir.

Some dirs, especially if longer filenames are involved, just don't work. It opens up an empty directory, then it requires two "parents" to go back, and it skips a level.

While talking about Disk Op, can we have, like in the clone, a warning about loading a module, if we have an unsaved module already open? This has always been the source of MANY nightmares in the past. Love that the clone asks you if you're sure you wanna load before fucking up your work.

Another most requested feature in our PT-1210 Discord:, many seem to want the extra "filters" option in the Sample window present in PT2 clone. Could that be implemented in 2.3F?

Thanks Bubsy for such amazing job !

[Ywe, IT-Scenes]

You should consider IT-X development, which is the continuation of this culture, on *nix, where it came from. (Irix, GL-Teapot, Tron etc.)

Where I am working on philosopical background as Islam, for Fair Pay, in these days.

https://www.youtube.com/playlist?lis...rQ9ooJ8XgpBtC5

[8bitbubsy]

Originally Posted by Akira

Some dirs, especially if longer filenames are involved, just don't work. It opens up an empty directory, then it requires two "parents" to go back, and it skips a level.

While talking about Disk Op, can we have, like in the clone, a warning about loading a module, if we have an unsaved module already open? This has always been the source of MANY nightmares in the past. Love that the clone asks you if you're sure you wanna load before fucking up your work.

Another most requested feature in our PT-1210 Discord:, many seem to want the extra "filters" option in the Sample window present in PT2 clone. Could that be implemented in 2.3F?

Thanks Bubsy for such amazing job !

Sorry, I'm already very tired of dealing with the PT asm code, and I want to be done with it forever, as soon as possible... Crucial bugs must be fixed though.