Weird Protracker issue.

Amiga1992 · 06 February 2012, 20:39

I am having issues with Protracker 2.3d, some tunes lock up the machine.
I don't understand which tunes are or why they lock up. What happens is this.

- Tune starts to play.
- Soon after, scrren lockup. Mouse is locked, spectrum display locked, VU bars locked, but the currently shown pattern keeps scrolling
- Some samples soundcorrupted, either noisy or at a too high pitch rate (alvin chipmunk material right there :P)

I tried this both with my Amiga and WinUAE and the same happens. Find attached a MOD that has such problem

Anybody has any clue?

s2325 · 06 February 2012, 21:48

I have same problem with very fast tunes, but only in WinUAE.

Amiga1992 · 07 February 2012, 00:20

Happens in my 030 Amiga, so maybe it is the Protracker version? Weird, because it seems to be the most popular of the 2.X batch.
I tried changing the clock from CIA to VBLANK and the same issue happens.
I don't think it has to do with speed because I have played some VERY fast tunes in it without problems. I think it MIGHT have to do with certain sample data.

StingRay · 07 February 2012, 07:56

Quote:

Originally Posted by Akira

I think it MIGHT have to do with certain sample data.

That's correct. Check if there are samples with a replen <2 in the module as PT2.3 won't handle these correctly (min replen needs to be 2).

Amiga1992 · 07 February 2012, 10:19

Thanks for that.
And what version do you think supports this? I just wonder what thesetunes were made with. Perhaps I should be using that version instead

daxb · 07 February 2012, 11:52

Same behaviour with PT2.3d on A1200 040. HippoPlayer and PT3.62 play the mod correct (I guess). So use other PT version should avoid the problem.

Amiga1992 · 07 February 2012, 20:24

Which version of the 2.X branch is the most recommended? I thought .3d was , but it seems it isn't

I'm not using 3.X, ever.

StingRay · 07 February 2012, 20:37

Quote:

Originally Posted by Akira

Which version of the 2.X branch is the most recommended? I thought .3d was , but it seems it isn't

I'm not using 3.X, ever.

PT 2.xx is perfectly fine. As far as I remember it was a bug in one of the older Noise-/Protracker versions which allowed samples with replen 0 to be saved. If memory serves me right it would be enough to save the module with PT2.x and the replen will be fixed.

Quote:

Originally Posted by Akira

Thanks for that.
And what version do you think supports this? I just wonder what thesetunes were made with. Perhaps I should be using that version instead

See above, 2.xx is fine.

Amiga1992 · 07 February 2012, 20:40

Thank you Stingray, I will try this fix. They are not my MODs anyway, I was playing some random stuff.
But now that I remember, I did have one that I had made with FastTracker and when passed onto PT2.3d locked up in a similar way. I did something to the samples and it worked fine. Probably I did what you say, only that I was just trying out stuff and was pure dumb luck.

Thanks again.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Weird A-Max / A1000 issue	desiv	support.Hardware	0	06 November 2011 06:35
Weird MaxTransfer issue	Retroplay	support.Hardware	2	11 May 2011 22:38
Jesus on E's weird issue... I must be doing something wrong here.	Claw22000	support.Demos	5	02 May 2011 10:17
Weird WinUAE issue?!	h0ffman	Coders. General	4	07 December 2010 13:42
Weird Screen Issue * HELP!!!	W4r3DeV1L	support.Hardware	9	06 October 2009 13:21

06 February 2012, 21:48	#2
s2325 Zone Friend Join Date: Jun 2006 Location: Gargore Age: 43 Posts: 17,789	I have same problem with very fast tunes, but only in WinUAE.

07 February 2012, 00:20	#3
Amiga1992 Registered User Join Date: May 2001 Location: ? Posts: 19,646	Happens in my 030 Amiga, so maybe it is the Protracker version? Weird, because it seems to be the most popular of the 2.X batch. I tried changing the clock from CIA to VBLANK and the same issue happens. I don't think it has to do with speed because I have played some VERY fast tunes in it without problems. I think it MIGHT have to do with certain sample data.

07 February 2012, 10:19	#5
Amiga1992 Registered User Join Date: May 2001 Location: ? Posts: 19,646	Thanks for that. And what version do you think supports this? I just wonder what thesetunes were made with. Perhaps I should be using that version instead

07 February 2012, 11:52	#6
daxb Registered User Join Date: Oct 2009 Location: Germany Posts: 3,304	Same behaviour with PT2.3d on A1200 040. HippoPlayer and PT3.62 play the mod correct (I guess). So use other PT version should avoid the problem.

07 February 2012, 20:24	#7
Amiga1992 Registered User Join Date: May 2001 Location: ? Posts: 19,646	Which version of the 2.X branch is the most recommended? I thought .3d was , but it seems it isn't I'm not using 3.X, ever.

07 February 2012, 20:40	#9
Amiga1992 Registered User Join Date: May 2001 Location: ? Posts: 19,646	Thank you Stingray, I will try this fix. They are not my MODs anyway, I was playing some random stuff. But now that I remember, I did have one that I had made with FastTracker and when passed onto PT2.3d locked up in a similar way. I did something to the samples and it worked fine. Probably I did what you say, only that I was just trying out stuff and was pure dumb luck. Thanks again.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)