Amiga Music Preservation - Forum
Amiga Music Preservation => New features => Topic started by: Asle on May 15, 2011, 17:28:47
-
Ho,
OK, it's not a new feature, I know :). Still, only topic open about modinfo() is in the support conf.
Anyway, I've just added the support of OCT (Octalyser) format, from the Atari ST/Falcon world. Very few cases on AMP ... for now.
So, official list of supported formats are :
669, MTM, OKT, AHX/THX, SFX*, PTM, DIGI, DMF, STK, MOD, FST, OCT, S3M and BP*, IT, DBM
Remains to be done :
DBM (doubtful I manage this one) <- now done
EMOD (Quadra Composer)
IT (possible) <- incomplete
MED/OSS (very doubtful it'll be done)
ML (no doc)
XM (doubtful - or some1 give me a display idea)
Sylvain
-
bravo! :)
XM would be fab. Does the problem come from displaying the data?
-
XM and IT would be good.
Does Modinfo support FAR and ULT as well?
-
hum .. now that ULT is mentioned, I remember working on it ... however .. now, where is it ? weird. As for FAR, no, it's not. I guess it could also be supported. I'll have a look when motivation is up and spare time exists (or I'm surrounded with demands ;) )
Anyway, I can't say yet for IT as I'm not familiar enough with the format.
For XM, I have no problem with the format at all. It's how to display 128 instruments texts which can have, each, 16 samples texts. Any idea to display that would be welcome. Some thought:
instr1
sample1
sample2
...
instr2
sample
...
or the DP way
sample1 of instr1
sample2 of instr1
...
sample1 of instr2
...
instr1
instr2
instr3
etc.
inst
-
I quite like the way XMPlay displays the Instruments and Samples, pretty clear to read, no idea if that can be done that way.
-
Never used that ... how is it displayed ?
-
How practical it is to display like this, especially with the sheer number of instruments/samples, I don't know. This particular xm uses all of them because he included a text on the bottom line of the instrument list, so you have to scroll down to it.
-
Ok, so, the correspondence between inst and samp is lost. I know of a few XM that must keep these two together.
[self promotion]
my own XM.intricate love (http://amp.dascene.net/downmod.php?index=1321).
[/self promotion]
OK, in there, I would say in inst 09 "no Xtc player 0.95c"
and in the first samp of this inst : "mega ultraclick"
So, the FT2 way.
Out of context, the "message" is lost, as shown in XMplay/DP2.
Must think about it some more.
Sylvain
-
OK, in there, I would say in inst 09 "no Xtc player 0.95c"
and in the first samp of this inst : "mega ultraclick"
So, the FT2 way.
Out of context, the "message" is lost, as shown in XMplay/DP2.
As is in most cases looking at other replayers/trackers.
I was more interested in being able to click the Info button on AMP to see what information was stored in the actual XM file, as one would do with the formats that Modinfo already supports. I'm not to bothered how its presented to be honest. It's not like I load XM files into Fast-tracker anymore.
-
Never used that ... how is it displayed ?
WTF? Anyhow, what do you use to listen to modules on PC then? If you are using a PC, that is...
-
DP2 and milky :)
-
Same here. :)
-
Okay, you made me download Milky Tracker ;)
-
Yeah, it's really good.
Did you ever track btw? :)
-
Me? Nope, I was just a gamer in the 90's..
I once opened Dpaint (5 minutes for the fun) on the real machine but my various diskdealers never gave me a tracker, I was simply not aware of their existence (as for the demoscene) 4 years ago.
-
OK. interesting.
I played more with Dpaint than I ever did with Sound/Noise/Protracker. :)
-
OK, I've uploaded an early version of IT (all versions) support in ModInfo().
It sticks to samples (no instrument) as those are always present while instruments are not.
The size calculation is also probably wrong in a lot of cases as I don't know how to calculate the stored "compressed" sample sizes.
Anyway, I guess the next version will display the instruments like the comment. I'll draw a new box and fill those there.
Your thoughts ?
Sylvain
-
Some examples attached for you to peruse...
Although not attached, I Modinfo'd one .it module that changed the font in my text viewer which was weird, as it didn't happen to the others, but made it display slightly better than just text output! :D
Seems to much data displayed to be honest, especially the Unused patterns etc.
Displays garbage in samples text.
Only sticking to display sample texts will unfortunately not display anything for those that chose to write in the instruments. Some mods do contain info in the Instruments, but the majority in Samples section, or the Comments section.
Still like how XMPlay displays it.
-
ouch ... ok, I was referring, of course, to the online ModInfo() :).
I didn't touch the prog (DOS based) at all :).
And yes, instruments should, somehow, be part of the display.
I just wanted to show something that is quite accurate already.
Try the online version now :)
Sylvain
-
DBM (doubtful I manage this one)
Why? Is the format that bad to deal with? I'd love to see DBM modinfo handled.
Another nice feature on user end would be a single link allowing download of all mods by a given author, but I guess this would be an impossible or at least a loathsome task in php...
-
Why? Is the format that bad to deal with? I'd love to see DBM modinfo handled.
As far as I could see last time I checked, yes. I certainly can give it another go.
Another nice feature on user end would be a single link allowing download of all mods by a given author, but I guess this would be an impossible or at least a loathsome task in php...
The technical part was never the pb for that. we could add a button "get all displayed" that would generate a big zip on the fly. No the problem was more politic than anything else.
However, now that we have a new server and no fear of bandwidth, well, it can be done. All 4 AMP team members, however, must agree ;) that's the hard part I guess.
Sylvain
-
Why? Is the format that bad to deal with? I'd love to see DBM modinfo handled.
As far as I could see last time I checked, yes. I certainly can give it another go.
I did and, after 6 hours of work, it's done. So, DBM is now fully supported. What a strange format, really. It relies on chunks, however, the point of having INST _and_ SMPL is strange, as there can be only one sample per instrument. Also some DBM file have a DSPE chunk which is undocumented.
Anyway, if anyone encounters a pb, please tell me. Remember that I'm automatically tracking size problems only, so, I won't know of any other problem.
Thanks Ijon for motivating me to do this one.
Sylvain
-
About DBM you can ask krashan who develop it. Contact: http://www.amigafuture.de/profile.php?mode=viewprofile&u=1431
or via forum: http://www.amigafuture.de/viewforum.php?f=15
-
thanks for the links !
-
I did and, after 6 hours of work, it's done. So, DBM is now fully supported.
That's awesome, thanks!
I missed it a bit on HippoPlayer back then - Kari Pekka Koljonen should have spent a few more hours on coding. ;)
-
I missed it a bit on HippoPlayer back then - Kari Pekka Koljonen should have spent a few more hours on coding. ;)
Indeed! :)
-
the point of having INST _and_ SMPL is strange, as there can be only one sample per instrument. Also some DBM file have a DSPE chunk which is undocumented.
There can be only one sample per instrument, but several instruments per sample. :) So you load a sample into the project and then use it several times as different instruments with independent settings (loops, envelopes etc.). A very handy feature.
DSPE is probably DSP Echo, but this is only my guess.
-
Well, those were just while blog-ish remarks which won't affect the developed feature. I don't plan to go back there anymore ;) - unless of course something went amiss.
Still, thanks for helping clarify those.
Sylvain
-
Don't remember if I mentionned that earlier but is there any way to make search engines aware of the modinfo content ?
AFAICS big G isn't, at least with this syntax [site:amp.dascene.net] [word]
-
well, since the display of the content is done live, there's no searching the entire archive.
A solution could be to do as Buzz did on Exotica and store in a DB all the texts. Searching there would then be possible.
Don't know if this is where it'll go. I'll bring that up to the other (dormant) AMP staff members ;)
Sylvain
-
I've patched slightly AHX to support HVL musics now.
Just so you know :)
-
I've patched slightly AHX to support HVL musics now.
Just so you know :)
Any progress on adding Fasttracker modinfo yet?
-
afraid not. Maybe I can quickly hack something up, concentrating on instruments first.
I'll try something later today, if possible.
-
Would be nice for the 2nd most popular format after protracker ;)...
-
OK, well, first shot is not working as expected, so, not online.
I'm done for the day. I'm generating too many stupid PHP bugs, so, it's time to stop :)
I'll look at it tomorrow, with fresh eyes.
-
It's online for XM now. Instruments names are displayed and size calculation is also done. However, if the XM is missing some data, it could lead to wrong calculation.
Please, report problems, if any.
Sylvain
-
It's online for XM now. Instruments names are displayed and size calculation is also done. However, if the XM is missing some data, it could lead to wrong calculation.
Very nice and well done! 8)
But.... ;D
Please, report problems, if any.
It seems to show the Instrument text correctly, but it shows the Instrument details incorrectly, as it uses the sample column headings and no data. If that is the intention, then its no problem.
Must be pretty difficult to show all the Instrument/Sample texts/data etc. for all slots in XM files. Must be very problematic.
-
Instrument details are .. well, not what I wish. In XM, information like volume, size, rate (etc.) are stored at the sample level. As such, retrieving them up would make sense only if there was _one_ sample in a given instrument.
I chose, for the moment, to display nothing in there.
Maybe I could patch complete data if there's only one sample and tag the others as 'more than one sample'.
I still think displaying differently is necessary, for that kind of format. For now, it's the usual mask to display information.
Sylvain
-
Instrument details are .. well, not what I wish. In XM, information like volume, size, rate (etc.) are stored at the sample level. As such, retrieving them up would make sense only if there was _one_ sample in a given instrument.
I chose, for the moment, to display nothing in there.
Maybe I could patch complete data if there's only one sample and tag the others as 'more than one sample'.
I still think displaying differently is necessary, for that kind of format. For now, it's the usual mask to display information.
Sylvain
I see the problem. Do any other module format do anything similar internally?
Otherwise, you'd have to show everything for both sample and instruments, both could potentially be 128 rows deep or more? I've not really paid attention to how many rows .xm mods can contain info.
I was looking at how you do .it modules and wondered if splitting the data could be a possibility somehow?
-
IT and DBM have instruments as well. I don't remember, off hand, how it works for IT. DBM was no problem.
Regarding XM, I'm not sure I understand your comment. 128 rows could be a reference to pattern data ?
Nevertheless, there can be 128 instruments in a XM, and each instruments can store 16 samples. The concept is the following : for this instrument, which sample should be played when a given note is played. As such, you have a map of notes where you assign sample numbers (in the current instrument). Hence the specific information related to each sample. Instruments, here, are some kind of envelope only.
Now, yes, I believe the display mask must be changed. The more I think about it, the more I leaning toward something like that:
instrument 1 -
----sample 1 (sample data)
----sample 2 (sample data)
instrument 2 -
etc.
could take some time to write, though.
-
Regarding XM, I'm not sure I understand your comment. 128 rows could be a reference to pattern data ?
Sorry, I meant only how many slots/rows of data to show in the Info details when I click the Info button. 128 Instruments or 128 Samples slots/rows if the author filled all the details in the module. Obviously, when I clicked Info, I was expecting to see possibly up to 128 slots/rows displayed for Instruments and then 128 slots/rows for Samples.
When I started looking through a few xm's, I realised it was not practical to show instruments and samples or the page would need to be scrolled down considerably. Looking at Awesome' For a New World II.xm, it would have to display 128 instrument slots/rows and 328 sample slots/rows... I just didn't know that each instrument could store 16 samples...
-
All right, I misunderstood indeed !
Well, the display can be huge. That's for sure. The very max would be 128*16 lines for every sample and 128 more for instruments. That's a grand total of 2176 lines to display :).
Besides, the text in sample is rarely meaningful.
-
Besides, the text in sample is rarely meaningful.
Yeah, was just noticing that. At least its showing that text in the Instruments which is a damn sight better than nothing at all.. ;)
-
And there was a bug in the XM modinfo related to the 256 stored patterns possibility. Sorry.
-
Now, XM format version 0102 is handled ("standard" one is 0104).
thanks for an AMP fan for pointing a case via email :)
Shelter (http://amp.dascene.net/downmod.php?index=79468) by Zodiak.
-
And XM $0103 is also handled
Thanks to Xlat this time for pointing out a case !
Enhanced Intuition (http://amp.dascene.net/downmod.php?index=74998) by Vogue.
-
So, are zeroes in IT comments ever going to be fixed? ;)