I haven't downloaded PAL as yet, sorry. I have played with mhwaveedit though.Lobster wrote: After trying the mhwaveedit recorder in Puppy PAL (Puppy 4 Alpha 1) and normalising. I got something but too much interference to use. I tried Wreckedleg and it produced an MP3 but did not seem to contain any sound? Is Lame required and not available in PAL?
Any updates?
Lame is required in the versions of wreckedleg so far published. However, it is not actually essential to use lame to produce the mp3s; If your system has the appropriate mp3 libraries (I forget their name) rec (of sox fame) can produce mp3's directly itself (albeit with less flexibility in terms of abr or cbr or vbr). I wrote something about that in the earlier rec2lamegui thread, I think, when talking about how to add mp3 support to Soxgui. Obviously you need sox and the aforementioned libraries though.
As for updates to wreckedleg... The promised major update IS coming, eventually... I am working on it, but it is tricky and taking ages, so will be a while yet. (In fact, it is taking much longer than I thought, but that is because I am building a more sophisticated overall system than I originally planned, whilst keeping the user interface pretty much as simple as before).
However, it is fair to say that the level of difficulty involved in implementing my new "concept" has at times threatened to frazzle my tiny mind, and slowed me to a snails pace. I've also been distracted now and then (sought refuge you might say) with too many forum "discussions" and debates about other things... I'm trying to focus though!
Everything I'm currently writing at the moment centres around a completely general-purpose client-server driven communication subsystem (being written in C), which I will be using in several planned applications (including wreckedleg) to simplify the processing of gtkdialog3 events. I call it "wiak"; a name I'll explain some day...
I'm also separating the UI from the event processing in the new wreckedleg in such a way that it will be easy to re-write the frontend for other linuxes, using for example Murga-Lua (for say, DSL) and even curses or plain dialog for a commandline only linux. "wiak", itself, as I mentioned above, is written in C and can itself be driven from the commandline...
Most of my wiak-ideas have now been implemented and tested in working bits and pieces, but I don't know when I'll manage to fill the remaining few holes and get all the pieces harmoniously joined and working together; in practice, you could say I'm purposively not hurrying. Being a general-purpose subsystem I have to design wiak's application interface very carefully because it can be difficult to add functionality later to such a subsystem without breaking everything else that might be using it.
It's all coming along though. It probably sounds much more complicated than the end product actually will be (what an effort for next to nothing really!) I may well become quiet for a while, but something will later suddenly appear!