GoatTracker slow on OS X
category: general [glöplog]
Anyone have any idea why the new versions of GoatTracker on OS X are so slow?
I've built the latest one from source, and it's very slow.
It's using very little CPU, but it's only refreshing the main screen a couple of times per second.
This makes doing anything, even scrolling, horrible!
The old 1.4 version for Mac by Andreas Varga (of SIDPlay fame) is quite fast and usable.
I've built the latest one from source, and it's very slow.
It's using very little CPU, but it's only refreshing the main screen a couple of times per second.
This makes doing anything, even scrolling, horrible!
The old 1.4 version for Mac by Andreas Varga (of SIDPlay fame) is quite fast and usable.
Spent an hour getting it to compile, and then it was terribly slow, then spent an hour getting it to generate profile data, which didn't include any timing data due to multi-threading and short-sighted kernel developers, then spent an hour trying to wrap the code in a program to overwrite the thread-creation code to auto-include the timer from above, then just said fuck it.
I wanted to make a song, but I wasted the whole afternoon trying to get the tools to work.
I wanted to make a song, but I wasted the whole afternoon trying to get the tools to work.
I have a problem.
Couldn't fix it.
Thanks for that.
very nice apple :)
isnt this the same problem hitchhikr had with protrekkr? (my memory is hazy considering this but it was some updaterect-style overload?)
ah no i mean grafx2:
Quote:
Ok, here's the deal: under macosx SDL_UpdateRect() automatically waits for vblank so calling it for each pixels drawn isn't a good idea at all. What i did is to remove all those updates calls for macosx and just use one in Get_Input().
It was either that or having a huge array to gather all dirty rects and updating them all in one go. I made some tests and it seems to work perfectly now in both window & fullscreen modes, so maybe it would be good idea to modify that update code for other platforms as well ?
calling anything for each pixel drawn isn't a good idea :)
Quote:
[...] so calling it for each pixels drawn isn't a good idea at all.
Aha!
I've gone through the code, and sure enough, that was the problem.
I have now fixed it.
Is anyone interested in a copy of it?
Should I submit a fix back to Covert Bit Ops?
At last I have a PPC build of the latest version...
I've gone through the code, and sure enough, that was the problem.
I have now fixed it.
Is anyone interested in a copy of it?
Should I submit a fix back to Covert Bit Ops?
At last I have a PPC build of the latest version...
By the way, thank you guys!
No time for such stuff lately, but one day I'm sure to want to learn it so definitely either put it up on the net somewhere or pass the fix back to them :)
Submit it back to them, sure
the oldfashioned act of contacting the autor of the software in question just doesn't do it anymore these days -____ä
Ah it's nice to see some lovely banter and people helping each other and resolving stuff here. <3
i'm almost glad my crappy code for grafx2 actually helped someone fix something else :p
well... back on fixing other bugs now :)
well... back on fixing other bugs now :)
Your code ? Where ?
I added all these updaterects() to grafx2, it was working fine without them under msdos... anyway, next time i'll use double buffering :)
We're talking about the bug i fixed with the delayed sdl_updaterect() which made the tool to crawl like a snake under macosx.
yes, thanks for fixing it :)
I should not have created that bug in the first place...
I should not have created that bug in the first place...
please share your fixed version of goattracker
For what it's worth, Andreas's latest version for OS X is really great!
http://www.sidmusic.org/goattracker/mac/
It includes the latest version of GoatTracker, is nice and fast again, and now supports MIDI input!
http://www.sidmusic.org/goattracker/mac/
It includes the latest version of GoatTracker, is nice and fast again, and now supports MIDI input!
I'm trying to find a way to insert a row in the pattern editor. The help clearly says INS and no other key can do that. WTF...
INS works fine under Windows and Linux at least.
well the essence of the joke is that it's the osx version and macs don't have ins keys, especially laptops :) i know i can plug in a usb keyboard, but it's not interesting.