SDL is not that optimized it’s basically a graphic API on top of Picaaso96, if Protracker was converted to P96 then speed will increase.

salass00 is also talking about FPS, this suggest to me that protracker graphics is copied whit 25 fps, when only the changes need to be refreshed inside the window.

And there might plenty of speed to be gained, in the SDL pixel plotting routines.

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

Actually, the problem with almost all SDL ports is that they busy-loop. They don't wait for events, but rather redraw-poll-redraw all the time. While that isn't a problem with a game, it's a problem with an application.

_________________
Seriously, if you want to contact me do not bother sending me a PM here. Write me a mail

Hi all

I just run it on my A4000 OS4.0 no problem.
But it SLOOOOOOW.

Best regards

v1.98e released.

Quote:

- Added a screen update scheduler so only modified parts of the screen   are now refreshed, this should speed up things quite a bit   as it looks like some implementations of SDL are borked. - Added an option to play instrument while editing.

so no midi ?

I wonder if there is interest in supporting lylehaze with os4.1.
I would do it but it would help my economy if we could split
the cost ;) That way he could enjoy os4.1 and maybe do midi support
for protrekkr. I dont know how much midi the pc version supports but
would be nice at least to try it out on amiga.

Lyle: I hope its ok for me to ask this

Kicko,
Thank You. It's a very nice offer.
My Amiga has been shut down and put into storage. I really don't have time to even try to look at that code.
Once I get everything back together, I'll be happy to give it a try, but I have no way of knowing how long that will be.

But don't hold your breath!! CAMD is REALLY EASY to work with. Since this program already has MIDI support, all that needs to be done is:

OpenLibrary()
GetInterface()
CreateMidi(), all you need is an app name
Request a destination cluster from the user.
AddMidiLink() to that cluster

PutMidi() for each message

and when you are done..
RemoveMidiLink()
DeleteMidi()
DropInterface()
CloseLibrary()

f you want to be lazy, you could even skip the cluster requester, and just hard-code it to out.0 or protrekkr.0. That would be less convenient, but the end user could use MIDIThru to connect it from there.

Example code to do all of this is already posted in CAMDTools.lha. Those are mostly REALLY SIMPLE examples, for just that reason.

If anyone has questions, I would be HAPPY to help by E-Mail. The developer to do this does NOT need MIDI equipment or a MIDI interface. there are CAMD tools to show you exactly what is coming out, either in text form or graphically.

LyleHaze
[edit] more detailed steps described

Last edited by lylehaze on 29-May-2009 at 06:26 AM.

_________________
question=(2b||!(2b))