@Varthall

Do you have any objection to making the work & notes you last did on Milky Tracker available?

I am a software programmer by profession. Theoretically, I can do the work. I am not versed in the available amiga library routines to help with any of the complaints. I do not care to be often reminded of bugs crying out to be repaired by someone (me) who has taken an interest.

From scratch I successfully ported a low-ish level, non trivial, c program from Solaris to Amiga 4.1.2 (I think it was), but I was very familiar with the Solaris version and no GUI was involved.

I naively thought I would be of service in porting tcl to AmigaOS4.1 so we could run the QA tests for sqlite 3.0. There, I found that low level tcl was not very straight forwardly ported. There were some technics that I had not enough understanding of Amiga OS System operation. I spent soooo many hours with so little to show.

But, if this is the only reasonable way to move programs of user interest, I am willing to consider it, but I don't want it to be THE only thing I do on my X1000.

George Wyche

@Varthall

I also would like to see a usable Milky Tracker again.

I used Milky Tracker in the past thanks to your port of some years ago. I showed the work to our Amiga Users' group.

I reached for hd-rec because of an outstanding, piano demo. But troubles with it (before becoming open source) and missing the absolutely necessary plug in for piano finally left me sour.

Milkly Tracker is cross platform and has you and possibly kask1e as knowlegable support. I find Milky Tracker very tedious to get anything other than a "march" down. The learning curve when it comes to short cuts is about the same for all other such programs.

All to say, I am willing to take Milky Tracker back rather than have nothing. So efforts you make on the program will certainly serve more than just one user.

Want a bounty for the work?

ggw

Until I got my X1000 and could use AmiCygnix's GIMP, ImageFX was THE image tool for my pictures and maintenance of my website.

I look over my shoulder and there in our bookcase are Image FX manuals that I rescued from a box of Amiga stuff that a guy was getting rid of. Finally, I could read about all the neat things it could do... long before gimp was a phenom.

I remember S. Woodall saying that ImageFX was intricately woven into 68K asm code and he wasn't interested in trying to convert it to C code for porting to other systems.

So, good luck to A-EON.

Yep.
"When its done!"

@LiveForIt and @Severin,

Thanks for the short, clear description of the "http: requestor" issue. I am guessing that the mplayer I was using was doing exactly the same thing, just internally.

I will look (again) at AmigaAmp. It and Tunenet are yet 2 more programs to learn well enough to know the work arounds for their quirks. MPlayer was, seemingly, a "one-program-solves-all", but "internet stations" keep messing around with their delivery schemes and stations become no longer accessible.

Inexplicably, the mplayer began, some months ago, to connect to the audio at too slow, too fast, sometimes just right speed. Only "just right speed" would play for more that 2 hours with perfection. So many times, I have to run an errand, leaving mplayer working, and return to find the X1000 hung, and a buzzing noise coming from the head phones. The buffering (for even delivery) was not settable and was not adequate.

All reasons to look into liveForIt-MPlayer as a replacement.

More, later.

==============
PS: I have to agree about the less than ideal GUI of Amigans.net. It has the screwest way of allowing me to finally login. The seemingly normal way, over there on the left, WON'T work. I'm serious: I have to purposefully enter a wrong password, get sent to that "intermediate screen" where I enter that proper password, and I'm in. Strange.

I am not at all clear about HTTP Handler. Besides, I don't want my setup to differ from "stock", i.e. no workarounds that I am quite likely to forget are in place.

My "work around" is to use the command line and suffer the 3 [Cancel] clicks AND starting another window just to do BREAK for a graceful exit.

About documentation: I am not too good at automatically substituting "Amiga (and supposed obvious translations)" for Linux specific info.

I was looking for a "what is different for the Amiga MPlayer vs Linux" or where ever this code is derived. Maybe just a compile switch listing? then I can at least see what to NOT to follow along in the Linux documentation. I have followed along with (for the most part) the discussion about the various flavors of mplayer that are currently being worked on for OS4.

I'm never, ever sure how much to continue to soak up before asking specific questions. MPlayer is a good example of that, because of what I did read about the mplayer linux documentation was/is voluminus with many options. I'll mention again that my principal interest is in the audio for internet radio.

Thanks for your suggestion, anyway. I did go do some reading about the http-handler, but the questions mounted up faster than the answers, affirming my decision to stick closer to "stock".

George Wyche
PS. I do make non-trivial donations for the software I use, so this conversation might be more than just to an enthusiast. Thanks.

@LiveForIt

This sequence keeps presenting me with a requestor.
10.Work2:liveforit-mplayer> mplayer-altivec -playlist http://media.kcrw.com/live/kcrwlive.pls

----- the requestor ------
AmigaDOS
Please insert volume
http:
in any drive
Process: 960 "mplayer-altivec"
-----------------------------

If I Cancel the requestor, it reappears. Upon the 2nd Cancel, another appears. But when the 3rd one appears, then a Cancel allows the program to play as I had hoped.

My 5 questions:
1) Should I put this at the bugs list?
2) Is there a "how to use LiveForIt-MPlayer" that covers an error on my part?
3) Did I not get all of the documentation? The 2 README files mention documention that is not in this directory.
4) Where should I be reading/asking about liveForIt-MPlayer?
and 5) I am used to typing Control+c to stop MPlayer, but now that hangs the program and window. Though I have discovered that opening a separate window and typing STATUS to find the <#>, then BREAK <#> ALL does cause a graceful exit, I have no way of knowing if this the accepted way or not? So. Is Control+c a feature request? Defect? or "Other"?

Thank you,
George Wyche

=========== The computer setup ===============
I am using X1000, most recent updates, downloaded liveforit-mplayer from OS4Depot last night. There is no installation so I put it directly into my Work2: an SFS-2 partition. My principle use of any mplayer is for internet audio streams.