Mod Archive Forums
Music Production => MilkyTracker => Tracking => MilkyTracker Community => Topic started by: unloopy on December 04, 2007, 01:39:24
-
Is anyone running (or does anyone know of someone running) milky on a gp2x f200?
-
Is that the new touch-screen one?
Milky ran fine on the original gp2x (using the d-pad to emulate the mouse) so I see no reason why it won't run on the f200. Also, if the SDL library supports the touch-screen, then you should be able to use that also.
-
A touch-screen gp2x? Now, THAT sounds interesting.
-
Thanks for the repky I just returned a fault ipaq so im thinking of getting one.
All the Ft like fun of milky and all the lsdj like fun of little gptracker AND it can run a version of pure data... who could say no? :)
-
My f200 just arrived today.
Cant seem to get milky to run though. I found a page on the file archive (for the gp2x) which suggested making a text file of the script bit of the readme file but it doesnt seem to work.. no file the 2x recognises as anything it can run.
Anyone able to help?
-
We want to get Milky running on that thing, so pop on #MilkyTracker on EsperNet (you can use the CHAT page on the website (http://www.milkytracker.net/?CHAT)) and we'll get things rolling. Mind the Chrimbo though.
-
Thanks :)
Ill try to pop on there later if im in. Havent had a chance this afternoon so far.
Ive got it to run but it wont quit without crashing (i think more fiddling will sort this out from what i read).
Im not sure if its running ok or not. I couldnt get any sound out of it (but i was rushed and between other jobs so thats prob me). And of course as i have it running its only really reacting to the joypad as it would to a gp2x joystick. Using the touchscreen it reacts but menus leap up and it doesnt really work as it did on the ipaq i tried. Again.. ill play more and try and note down the issues before i come back.
-
Ok i cant use any javascript on this pc so just whilst i remember....
I could only get sound by restarting after checking the force 2^n box in config and restarting. Not sure what this option is though....
I cant seem to quit the prog without it just going to a black screen and staying there.
I guess these are both general gp2x issues. If the first isnt ideal then id like to work out how to change it sincei plan to use milky quite a lot this year. As for the 2nd it seems some people dont have the same issue so itd be nice to be able to close and open the prog more freely as the gp2x firmware takes an age to boot. Advice welcomed.
Then theres the touch screen. It reacts but it acts a little like a touchpad on a laptop (if that makes sense) the cursor jumps around a bit when i try the stylus too and keeps bringing up the edit menu. Im not very techy so i dotn really know if im basicly missing something i should be doing to use touchscreen with it. If i can be of any use despite this in testing ill be around tomorrow and will pop onto the chat.
I know this platform is hardly likely to be important but if a good compromise between the f200 touch screen and buttons could be found it could work even better than it does on windows mobile. :)
-
I could only get sound by restarting after checking the force 2^n box in config and restarting. Not sure what this option is though....
This is related to audio buffers and it's a sort of compatibility switch for picky audio devices/drivers that only work with powers of two buffer sizes. The box is likely to disappear in the following MilkyTracker versions as the mixer code (along with other stuff) has been refactored beyond the need for it.
I cant seem to quit the prog without it just going to a black screen and staying there.
This is a general gp2x issue and AFAIR it has been solved by gp2x owners. I remember reading about it in some gp2x software download site, in MilkyTracker's comments.
The unexpectedness of the touch screen is to be expected. No work whatsoever has gone into F-200 compatibility yet so it's only natural it isn't working perfectly. Hopefully this situation will improve in the near future. Once a team member gets an F-200 at the latest.
I know this platform is hardly likely to be important but if a good compromise between the f200 touch screen and buttons could be found it could work even better than it does on windows mobile. :)
Yeah, I know! :)
Ok i cant use any javascript on this pc so just whilst i remember....
(The chat is Java but) There are other alternatives. There are tons of IRC clients available for different systems you can download and use to connect to the chat. And multi protocol IM apps like Miranda, Pidgin or Kopete work just as well. Then you just need to connect to a server on EsperNet (cosmos.esper.net for example, more at http://www.esper.net/servers.html ) and join the channel #MilkyTracker .
-
It seems like some people have got it quitting happily with the little script poted on the wiki and the file archive. Ive tried copying it into a text file and calling it milkytracker.gpe and calling the milkytrackergp2xlinuxarm file milkytracker but it seems not to find anything to run unless i affix .gpe to that and then it hangs when it quits. Maybe this is due to my near total ignorance of scripts though.. i wouldnt be surprised if i need someone on their forums to put this script in a different format or somesuch....
Yes i totaly wasnt expecting the touchscreen to work with a version set up for a joystick. The joystick version even sped up is really awkward on the f200 dpad though so i cant really use milky unless the touch screen works like it does on a pocket pc.. and i would love to be able to do that for live stuff or just starting projects to pick up later on my desktop in renoise.
Id love to get a few more people to use it with an f200. Im trying to think about how the d-pad, trigger buttons and shoulder buttons could be used together with the touchscreen. I think the dpad should work like the arrow keys on a desktop version. Right shoulder button could work like a shift key with them. The other buttons could be commands, or triggers for quick drum programming along with the d pad or perhaps there are better uses for them.
Perhaps one button could switch between treating the joystick/dpad as a mouse or as arrow keys. I think that would be more usable for f100 users too.
sorry if im droning on a bit... having tried it on windows mobile im quite excited by how well it could work on here .. i really think it would be hugely popular on the platform with a few tweaks.
Ill look into the irc thing. Ive never really used it. ta for informing me :)
-
Regarding the hanging on exit, that is due to a fault in your script file. Milkytracker should be named 'milkytracker' and the script file 'milkytracker.gpu' I think.
I don't think there is anything that we can do to fix the problems you are experiencing with the touchscreen. Milkytracker's input is handled by the SDL libraries, therefore any problems are due to SDL not interpreting the touchscreen correctly. I asked around a few times in #gp2xdev but couldn't find anyone had an f200 and was willing to help, perhaps you might get better luck on their forums. Are there any other SDL apps on the g2px that you could try?
-
I tried naming the script .gpu (also .gpe) and the other file milkytracker.
My gp2x just doesnt find a file it can execute in that case. I tried a script someone posted to the file archive also in case id got it wrong but that didnt work either. Perhaps this is due to the f200 having different firmware. Only renameing the main file milkytracker.gpe seems to work.
Is there a mouse arrow in the windows mobile version? my memory is hazy.
Ill give their forums a go and see if i can send anyone who knows their gp2x stuff your way.
Id be happy to test anything out too.
-
No, there is no mouse arrow in the windows mobile version. The mouse arrow is drawn to enable navigation via the d-pad, although I imagine it could be annoying when using the touch-screen.
-
Is anyone running (or does anyone know of someone running) milky on a gp2x f200?
Would just like to add that I got a GP2X F200 for xmas and got milkytracker to work immediately with no probs.... and i'm a n00b...
-
Does the touch screen work?
-
If you touch anywhere on the pattern it brings a menu (mute chan etc) up rather than moving the cursor to that point. The mouse arrow move close to where you touch. If you touch one of the buttons on the lower half or on other screens the gui works and depresses the button but it doesnt have any effect. When you push the a button there is also no effect .. if you use the joypad again the arrow moves from where it was before you used the touch screen and a only works when you get back to the button in that way.
I think that covers it. Ive struggled to explain it correctly so sorry if the above makes no sense.
-
If it brings up a context menu it basically means the tap is recognized as right mouse button click instead of a left click.
-
Interesting. So if this could be reversed (perhaps in the gp2x itself..ill ask on their forums and report back) and if the mouse arrow could be ditched or turned on and off in options the f200 should feel the same as the win mobile version? :)
Have you heard about their soon to be out pandora machine?
-
You need to understand that it is the underlying SDL implementation which needs to support the stylus tap and report it as a mouse button click. SDL is a system library that comes shipped with your GP2X. MilkyTracker relies on that library, so you should ask around if SDL on the GP2X correctly supports the stylus as an input device, if there are known problems and maybe have a look if games using the SDL have same similiar problems.
One more thought:
It can't be much of a problem to fix SDL to support the touch screen correctly if that's the problem at all. It can only mean a few lines of code and/or some tweaks, maybe, instead of asking around at a forum full of regular users you should find some developers willing to look at your problem. I bet it's just a matter of a few minutes.
-
Ill give that a go. Seems so tantalisingly close and id really like it running.
-
Loopy - I did pop into #gp2x-dev and asked around for some help, but it seems most devs don't own an F200 nor do they have any intentions of getting one. Also, no-one seemed to know anything regarding SDL and the touchscreen.
The Pandora looks very interesting.
-
There was a thead a while ago where some claimed they would develop for the touchscreen despite the pandora coming out. That was before anyone knew what itd look like or what the spec would be so that could have changed.
The keyboard is pretty interesting from a tracker pov but i wonder how usable it ll be for that in practice. Apparantly it ll be about 550MHz , big touchscreen, decent amount of ram and with two joysticks, a d pad and all thouse buttons it could be a bit of a killer for music software if the right people dev for it. Fingers crossed.
-
Ok I googled around a bit and found this:
http://www.gp2x.de/cgi-bin/cfiles.cgi?0,0,0,0,46,2358
It reads out the touch screen directly from device file. Seems that SDL either doesn't support the touch screen or it didn't at the time when this example was made.
Now you should convince Deltafire to hack that stuff in ;)
Edit:
Seems that SDL does not in fact support the touch screen, at this moment in time:
http://www.gp32x.com/board/index.php?showtopic=39053
-
Ok, so it seems that the SDL library that's supplied with the F200 is broken (as regards to touchscreen support). I spoke to some guys in #gp2xdev and they suggested that you try the Open2X SDL instead.
Let us know if it works :)
Update: You need to install Paeryn's SDL, which is probably the same as is included in the Open2X package.
-
Im going to do some investigating as i know very little about running this stuff and dont want to leave myself with a 100 quid paperweight due to my own stupidity ;D
-
A linux shared library is basically what a DLL is on windows. There's nothing more to know about it, replacing the SDL library with a modified one is a matter of a few minutes.
http://paeryn.myby.co.uk/
The website even says:
Updated with basic support for the F-200's touchscreen. Currently it appears as a mouse as long as no USB mouse is present. All mouse movement events appear with the left mouse button down.
I'm pretty sure this will solve all your problems.
If you don't know how to install it:
http://wiki.gp2x.org/wiki/Paeryn's_SDL
http://www.gp32x.com/board/index.php?showtopic=23819
-
Thanks for the time and the links :)
The only guides i can find on how to install it seem to assume a .gpu file to run which isnt in there. Ill keep looking for something very step by step but this is a bit beyond me to do quickly. Will come back when ive read up and understand what im doing.
-
Has Anyone gotten the touchscreen to work properly by replacing the SDL?
Furthermore, can someone please tell me the step by step process? I can't make heads or tails of how its meant to be done. :)
Thanks Guys.
-
As it seems you can't replace the existing SDL. You need to link milkytracker against the newer SDL library, which means you have to build milkytracker yourself.
-
ok. How to I build Milkytracker myself? :P I'll have an ask around some GP2X forums.
Is there a release of the Milkytracker GP2X Source Code somewhere, the version Deltafire built?
I left a message with Deltafire asking him if it was possible to build a version with the new SDL. No response yet.
Thanks for your help pailes,
-
ok. How to I build Milkytracker myself? :P I'll have an ask around some GP2X forums.
If you have never built anything for the GP2X yourself I'm sorry I can't help you, because neither did I. You need to set up a cross compilation environment on linux and work from there. I think there are a lot of tutorials out there which will help you getting started.
Is there a release of the Milkytracker GP2X Source Code somewhere, the version Deltafire built?
There is no GP2X MilkyTracker source code. Everything is in the regular source code tree, if you build MilkyTracker with the SDL frontend and the __LOWRES__ switch it will compile a version of MilkyTracker running in 320x240. That's it.
I left a message with Deltafire asking him if it was possible to build a version with the new SDL. No response yet.
Must be busy then, usually he's rather helpful.