|Protracker Big Problem With Glitches||page 1 2 |
03 Mar 2018 08:43
|Hello after some friends on Facebook reporting that protracker is hard to use because of the glitches made when channels are playing in protracker i need to inform the team that also after core 2.7 the glitches are here and worse than core 2.5.|
A friend reported that the CPU is is on 99% when protracker is playing a module.
After using digibooster with a 32ch .XM 9mb module the cpu is on 50%-60% with AHI on 14bit stereo++ with no problems.
Please can you make a fix for protracker apps ?
This happens from protracker 1.8 to 3.15 and more.
03 Mar 2018 09:53
|Yes exact the same problem here !|
03 Mar 2018 10:29
|EXTERNAL LINK |
Stuart Blacklock wrote:
''OK I spotted something, I an Digibooster playing a 9MB XM file running 32CH at once at 27KHz 14 BIT Calibrated stereo ++ and the Vampire barely breaks a sweat, I ran Protracker 4CH and it maxed out the CPU yet when I went from protracker screen to workbench the CPU drops dramatically, I think the CPU is overtaxing for some reason''
Gunnar von Boehn
(Apollo Team Member)
03 Mar 2018 10:30
|Thanks for the report, we are looking into this.|
03 Mar 2018 10:44
|Thanks Gunnar. I know that the team works hard for everything. Also the glitch happens on lcd monitors too.|
03 Mar 2018 11:18
|There's no problem with protracker. You need a 060 friendly version.|
03 Mar 2018 11:56
|I use ProTracker 3.62|
03 Mar 2018 12:07
|Hello all, I have just downloaded 2.3E which was modded in 2017, that does in fact play and work flawlessly, I have also located a copy of 3.62 which works much better than 3.15 and 4 but it does still max the CPU out and does glitch, it does appear Protracker is the issue though I never had this issue on my A1200 PPC 060, so what do I do? I do like the 2.3E version though I want to use the later 3V,|
For those who are interested 2.3E is the only one I found to work 3.62 almost does, 1.0B, 1.0C, 1.1b, 1.2a, 1.2e, 1.3, 1.3b, 1.8se, 2.0a, 2.3a, 2.3d, 3.00b, 3.15, 3.1b, 3.53, 3.61, 4.0b and 4.0b2 do not
A working copy for the 68060 CPU can be found here
Sadly it seems no other Protracker was updated though I did find on Aminet the source code available for 4.0B2
Alas I have no programming skills what so ever so I wouldn't know how to make this work
03 Mar 2018 14:25
|yes you are right 2.3e runs pretty good ...|
(for me personally, i I would never have come up with the idea
that an older version runs better than a newer one) ...
but thank you for your research !
(Apollo Team Member)
03 Mar 2018 18:52
|It's a nice tracker. Here's couple older tests with it:|
04 Mar 2018 13:02
|It's better for this issue to be fixed because I never used 2.3 protraker in my life. I was and I still use 3.15 - 3.62 versions a lot and many others doth same.|
Please make a fix if you can. It's a serious problem as I use my Vamped A600 to make music a lot.
04 Mar 2018 22:59
|If you disable cpu chaches and boot in pal resolution I think that every version of protracker works correctly|
12 Mar 2018 20:02
|Just tried this, by holding down the two mice keys whilst booting and selecting "disable cache" on the bot option screen and booting into the PAL screen mode rather than the SAGA screen mode but I can confirm it does not fix the fault, I also checked an old video of my A1200 PPC 060 and it didn't glitch on that. 2.3e works great but I think that fix was mostly because of the missing notes and such, I think there may be an issue with the Vampire core and Protracker still as Protracker still maxes out the CPU during playing on every version except 2.3e|
19 Mar 2018 18:03
|This is not normal that the CPU maxes out with protracker thats not normal and its a glitch that evolves all protracker apps. |
I cant understand why this happens but its a big problem (at least for me) I use protracker apps a lot. Some newer versions help me to make some effects on samples that you cant make on 2.3e like the mod2samp on latest versions. I tested also on 2.7 core and did the same. I changed to core 2.8 and the same glitches happen.
No fun with protracker :(
04 Apr 2018 09:34
|Can you please share one of those problematic module to reproduce it ?|
05 Apr 2018 12:27
|Renaud Schweingruber wrote:|
Can you please share one of those problematic module to reproduce it ?
The one I notice almost instantly is "fresh House" off the CDPD CD, Looks like it’s on Aminet too but any module on protracker using all 4 tracks at the same time seems to make it glitch but if you run Tinymeter in the background on another display you can see when any version of Protracker is opened ( except 2.3e) the CPU max’s out, before it even starts playing
Aminet LHA download can be found here
05 Apr 2018 15:24
|Thanks for the link.|
I've just tried with current GOLD2.9 WIP core with such environnement :
* Vampire 600 v2
* Current GOLD2.9 WIP core (rev 5104)
* ProTracker 3.15
* Module your linked to
* PM tool to monitor CPU usage (http://aminet.net/package/util/moni/pm)
I have a constant average CPU load of <1% while playing
06 Apr 2018 19:56
|Perfect :-) Looking forward to trying it out when the core is ready, and will report back|
07 Apr 2018 23:19
|Hello, just installed 2.9 but I am afraid to say its exactly the same, using 3.15 the CPU maxes out and PT glitches during play. Currently I am in possession of two Vamp cards, one for myself, the other is for a friend, my A500+ is using my own install of 3.9, my friends is running Coffin R49, both have exactly the same issue|
have posted a pic on Vampire FB, whist pulling this image from a video the A500 crashed
Error: 8080 0006 Task: 08002320
10 Apr 2018 08:33
|The 2.3E 060 fix works perfect on vampire with no glitches at all.|
Can this code be imported on 3.62 or 3.61 from the 2.3E 060 fix ?
The highest cpu compatibility for 3.61 and 3.62 was for 030 and 000 only no 040/060 fix for those versions. Thats what I'm asking.
Maybe if someone can code the 3.62 or 3.61 with the same 060 fix for 2.3E it will eliminate the problem.