PDA

View Full Version : 2.71 Thoughts


ReDVsion
14th December 2000, 17:39
B/c I won't dare reply to a damn 2.71 topic written by somebody (not "Somebody") who just wanted to write the first fucking post about 2.71, I'll write my comments here:

THANK YOU for bringing PP's DM MIDI back! I LOVE YOU JUSTIN! JUSTIN IS GOD!

AVS is trippy and fast. Nice work. And you got my pixel doubling back... very nice. The only problem I've seen is that when I activate the framerate counter I can't get rid of it w/o going out & back into fullscreen.

Gee.. It surprisingly looks like 2.7, 2.666... http://forums.winamp.com/ubb/biggrin.gif

One request: Please give us a winshade VU option! I'm not the only one requesting this.

Thanks for the new version, now take some time off for christmas vacation, dammit!

------------------
Bah! Humbug.

Reverend Ike
14th December 2000, 18:17
One note regarding the inclusion of PP's DirectMusic plugin in Winamp v2.71:

If you already had the DirectMusic plugin in_dm.dll installed, and you upgrade to Winamp v2.71, the DirectMusic plug-in v1.03 configuration window may pop-up each time you double-click on a shortcut that points to "...\Winamp.exe".

The solution, of course, is to close Winamp, go to your Plugins folder, and delete in_dm.dll.

(If I am wrong, hopefully PP will correct me).

[This message has been edited by Reverend Ike (edited December 14, 2000).]

Indyrod
14th December 2000, 23:02
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by Reverend Ike:
One note regarding the inclusion of PP's DirectMusic plugin in Winamp v2.71:

If you already had the DirectMusic plugin in_dm.dll installed, and you upgrade to Winamp v2.71, the DirectMusic plug-in v1.03 configuration window may pop-up each time you double-click on a shortcut that points to "...\Winamp.exe".

The solution, of course, is to close Winamp, go to your Plugins folder, and delete in_dm.dll.<HR></BLOCKQUOTE>


Ok, I'm lost..What does this new MIDI input plugin do for me? The HELP says there is a box to check for VIS, so Midi files will play through Winamp allowing Visual Plugins such as AVS. I don't see any such box in configuration. I understand it can write WAV files out, and why anybody would want to do that is confusing, but whatever. Any information would be appreciated.


------------------
"Let the past, be a learning experience for the future, but don't dwell on it"

Indyrod AVS Presets
Indyrod.deviantart.com (http://Indyrod.deviantart.com)

Wish
14th December 2000, 23:20
http://firehose.net/~deadbeef/in_mp3_271d.zip

Updated mp3 decoder 2.71d. Fixes a bug in the decoder. Saw this at Fileflash.

Reverend Ike
14th December 2000, 23:26
Indyrod -

Good question. This Nullsoft MIDI plugin doesn't have any Vis support I can find either, whereas PP's DM plugin does. So I just disabled the Nullsoft one and added the DM plugin back into my Plugins folder.

Maybe Justin or PP will enlighten us?

- - - - - - - - - - - - - - - - - - - -

Wish -

http://forums.winamp.com/ubb/Forum4/HTML/000923.html

[This message has been edited by Reverend Ike (edited December 14, 2000).]

Somebody
15th December 2000, 00:14
Bump

cuz of the updated mp3 decoder for people that use it :P

------------------
O.o

Thor
15th December 2000, 00:46
If there's allready an updated in_mp3 for 2.71, how come Justin didn't post it here ? or on his plan ? ...

This is weird ...

THOR

Reverend Ike
15th December 2000, 00:48
Thor -

He did. It was posted in the thread I referenced above (000923).

DJ Egg
15th December 2000, 02:56
Indyrod & Rev

Re : 2.71 MIDI Plugin config

For vis : checkmark "sample data from" (M$ Sound Mapper)
For DSP/FX : checkmark "send sample sound to output"

However, you can select the Device to M$ Music Synth instead of MIDIMapper
Vis should work with this regardless. Also gives option to enable "reverb".

Although it's all a bit too late if you've deleted the default in_mid.dll http://forums.winamp.com/ubb/eek.gif

However, I don't understand how PP's DM Plugin can be any different.
Surely the latest version must be the same as WA 2.71 default plugin ?
Yes/no/maybe ?

KenoDaddy_2000
15th December 2000, 14:09
Is it just me having a "dumbass" day or does the new mini vis plugin from Justin & crew do precisely nothing? The first thing it did was crashed Winamp - buton reloading I hit ctrl-shift-k and got a nice fullscreen blank screen! Any ideas (yes it is selected in the preferences settings).

Twilightseer
15th December 2000, 14:22
Keno,

The tiny vis works perfectly for me.
What happens if you change the plug-in's configuration ?

------------------
Twilightseer

Life isn't funny. Don't you know that ?

Thor
15th December 2000, 16:10
Thanks for pionting that out Reverend Ike

THOR

ReDVsion
15th December 2000, 18:36
Huh? Mini Vis? WTF?

------------------
Bah! Humbug.

Flynnz
15th December 2000, 19:13
I think I'll stick with my original plan.. and just wait a month or so for 2.8 - yummy.

peter
16th December 2000, 00:09
WHY THE HELL DO THEY HAVE TO SHUT DOWN THEIR SERVER WHILE I AM POSTING A REPLY ? I SPENT OVER 15 MINUTES ON TYPING AND IT HAS BEEN LOST. THIS SUCKS.



Ok. Now I'll try to re-create my old post:
1. Justin said that Winamp setup will delete old DMp versions. I've added an extra code to remove old config from Windows registry (new versions store config in winamp.ini). This causes old config window to appear on startup.
2. The version which is currently on my web site is a bit newer that the one bundled with Winamp v2.71. To determine exactly which DMp version are you running, see the about box. I wish Nullsoft had waited with v2.71 release one or two days more - I've just put my hands on Yamaha SW60XG and it enabled me to hunt tons of XG-specific bugs.
3. Looks like MIDI decompression support is NOT included with Winamp v2.71. You need read_file.dll which is included in DMp package on my web site. Blame Justin for that. I gave him two versions: with external read_file.dll (see 4.) and with decompression routines inside in_midi.dll (smaller). And he included the one that uses read_file.dll, but without read_file.dll itself. This really pisses me off.
4. Why the HELL there is still no compressed mod support ? Mod plug-in could use my read_file.dll to do this stuff. I emailed Jake about it a few weeks ago, but he doesn't seem to be going to implement it.
5. DMp docs are out of date. 'sample data from...' = 'sample for vis'.
6. Do not use 'send sampled data to output' option unless you really know what are you doing. It will send recorded sound back to your sound card (and mess everything up). Enable it only while diskwriting / SHOUTcasting / etc. For regular DSP, use M$ $ynth.
7. Q. What is the release date for Winamp 3?
A. We will serve no Winamp before its time. With that in mind it just might make a good Christmas present.(cough) Christmas '01 ?

[Edited by PP on 12-15-2000 at 05:32 PM]

Winsane
16th December 2000, 00:37
So you haven't gotten in the habit of selecting and copying each message before posting just in case? Heh.
Anyway, thanks for the info.

peter
16th December 2000, 00:49
I edited my old reply in notepad, then copied it to UBB and clicked 'submit reply'. Everything seemed OK so I closed notepad and lost it. Original version was a bit longer. It's 2:52 AM here, time to go to sleep...

Winsane
16th December 2000, 03:24
PP, I just noticed that the read_file.dll that comes with your in_midi.dll 2.34 is older than the one that came with 2.33a. Any particular reason? Which one should we use?

DJ Egg
16th December 2000, 04:11
So I almost got it right with my instructions above.
(Ooh . . . an underline facility . . . at last!)

PP
Cheers for the info re: when to use & when not to use "send sampled data to output"
Just one question, if ya get to see this thread again that is:
If I/we want to get your latest version of DMp with the read_file.dll included, do we install then rename/delete the default in_midi.dll, or do we rename your plugin to in_midi.dll ? :confused:

Hey, and yes, it pisses me off too that the in_mod.dll can't read compressed mods. I've got loads from traxinspace & they're virtually all still in zip format. If ModPlugPlayer can read zips & compressed formats, then surely Winamp should be able to as well. I tried the Unpack Plugin (c/o TSGH - where did all those plugins go) but it requires all compressed audio zips to have the MDZ ext, which I find very weird. MDZ is a compressed module format (ModuleZip), so how the hell can you convert/rename other formats such as mid/wav/mp*/etc with the mdz ext? Surely there must be a plugin that supports any audio file in zip format, like ModPlug does. I'm surely not going to convert/rename all my it/xm/mod modules to mdz. This'll mean resetting the ModPlug playlist all over again too . . . aargghh.

Looks like I'll still be using ModPlugPlayer for some time yet.
I'm dying to add all those modules to my winamp playlist, but I ain't gonna unzip any of them to do so.

If anyone can sort it out it's you PP.

(maybe I should post this in the wishlist?)

----------
DJ-Egg

Winsane
16th December 2000, 04:17
Originally posted by DJEgg
If I/we want to get your latest version of DMp with the read_file.dll included, do we install then rename/delete the default in_midi.dll, or do we rename your plugin to in_midi.dll ? :confused:
Huh?

Looks like I'll still be using ModPlugPlayer for some time yet.
I'm dying to add all those modules to my winamp playlist, but I ain't gonna unzip any of them to do so.

Ditto. There is PP's ModPlug engine plug-in for those, but it is a bit lacking in features.

DJ Egg
16th December 2000, 04:43
Seems pretty straight forward to me dude!
I'm using the default 2.71 in_midi.dll
We all know that this is PP's plugin, which is now included in the default install.
I've not got any of PP's "3rd party" plugins installed. I've always used the default mid & mod plugins.
So, what I wanted to know was, if I install PP's latest DMp to replace the default in_midi.dll . . . is PP's plugin also called in_midi.dll (in which case the default one will be overwritten), or is it called something else (eg. in_dm.dll)? If the latter, do we then delete/rename the default midi plugin to disable it, and do we then rename PP's plugin to in_midi.dll, or leave it as it is?

Not an easy one to explain, but is that any clearer?

I might try out PP's mod plugin. What features are lacking exactly?

Also, another thing that's pissing me off with the new forums is that the "show signature" box is checkmarked by default. There doesn't seem to be any way of disabling this in edit profile. Pfft again.

Winsane
16th December 2000, 04:51
Originally posted by DJEgg

is PP's plugin also called in_midi.dll (in which case the default one will be overwritten), or is it called something else (eg. in_dm.dll)?
The former.
I might try out PP's mod plugin. What features are lacking exactly?
Thought I answered this one for you before, but: Seeking, file info, and MDR support are the main things that are missing. It's been a while since I've played around with it (had to disable it to beta test Air's plug-in), so I don't remember if there's anything else worth mentioning about it.
Also, another thing that's pissing me off with the new forums is that the "show signature" box is checkmarked by default. There doesn't seem to be any way of disabling this in edit profile.
Hmm. For me, it's off by default. Maybe it automatically turns it on by default if you've got anything written in your signature box in your profile (mine's blank).

DJ Egg
16th December 2000, 06:00
Cheers for the help & info Winsane.
Hey, I always considered myself to be kinda superhuman, but how do you manage to reply in all the different forums all at once?
You must have plenty of windows open, yes? Hyper F5 refresh man.

Ya must be right about the sigs. Maybe I'll leave mine blank too.
It's kinda lame anyway, what d'ya think?

Winsane
16th December 2000, 06:51
Originally posted by DJEgg
Hey, I always considered myself to be kinda superhuman, but how do you manage to reply in all the different forums all at once?
You must have plenty of windows open, yes? Hyper F5 refresh man.
:confused: No, just one window at a time for the forums. Sometimes a second to browse slow-loading other sites.

As for the sig, how about turning your name into a link to your web site? Though I guess with the new forums, there'll be a link to your homepage anyway under each post, so that's not so necessary. I'd leave the "DJ Egg" part if you want people to address you that way instead of "DJEgg". This part:
^/^
`v
looks a little weird. Is it supposed to be a face? Anyway, I think the less vertical space a sig takes up, the better. But it's really up to you.

peter
16th December 2000, 09:59
Current version DMp is called in_midi.dll (hell, almost like in the pre-v0.4 age).
'Nullsoft MIDI plug-in v2.0' slightly modified version of 'DirectMusic plug-in v2.33a'. You can copy only read_file.dll (and it will work). If you have donwloaded some newer version (v2.34), it is recommended than you copy in_midi.dll too (it's less buggy).
About ModPlug plug-in - simply rename .mdr files to .mdz .
You can be 100% sure that you will be able to read all sorts of compressed (zip, rar, gzip, arj) files in Winamp3. I am afraid that decompression support dll (read_file.dll) will be available only on my web site - Nullsoft doesn't seem to be going to bundle this dll at all. It works very nice with Tempura (just copy my read_file.dll to tempura/plugins dir, compress some mp3, change zip file extension back to mp3 and open it); it works better than any known 'unzip' plug-in for WA2 because everything is done in memory, without intermediate temp files.

Thor
16th December 2000, 11:10
I've just been to your site PP...
And if I got it right the version op your DirectMuisc plugin that came with Winamp 2.71 was 'Nullsoft MIDI plug-in v2.0' slightly modified version of 'DirectMusic plug-in v2.33a' right ?
But that version is already outdated by 2 (!) new one's : 2.34 and 2.34a right ? ... Do you send these updates to Justin so he can bundle them with the next versions of Winamp ? ... They should be called 'Nullsoft MIDI plug-in v2.1' then ... :-) ... If anyone cares :-) ...

THOr

peter
16th December 2000, 11:43
Including DMp with Winamp setup finally forced everyone to test it and I got a few interesting bug reports; this is why there are two new versions; third one - v2.34b with final XG/GM fixes will be uploaded soon.
Of course, I will send an update to Justin (before the next WA release).

DJ Egg
16th December 2000, 13:03
PP
Cheers again.
I'll go d/l your latest DMp right away.
btw, I haven't got any MDR's, just loadsa IT & XM in ZIP format.

Winsane
I got rid of my sig. You're right, it was shite.

Anyone
Hey, what's the Views Column all about? [on each of the forums' main pages]
Aah, I take it that's how many people have actually viewed the thread
Far out!

Reverend Ike
16th December 2000, 13:10
Egg -

I believe it counts how many times the thread is looked at or "visited" by people regardless of whether they post in it. The LUFC forum has a counter like that also.

Thor
16th December 2000, 13:15
Thanks for the info PP !

THOR

DJ Egg
16th December 2000, 22:06
It's only been 2 days since 2.71 was officially released and already we've had an updated in_mp3.dll & in_midi.dll . . . the question is, how do we know if either of these are now included in the download?
I suppose we'll know if we get loads of posts from people with mp3 & mid plugin related problems.
Now there's a potential nightmare! Having to post endless links to the updated plugins . . .
I reckon a confirmation post from Justin wouldn't go amiss.

Winsane
17th December 2000, 00:03
Originally posted by Reverend Ike
LUFC
Whazzat?

By the way, PP, how exactly does that read_file.dll thing work? How would Winamp know to redirect files to it?

Indyrod
17th December 2000, 00:31
Quote Edit:
It's only been 2 days since 2.71 was officially released and already we've had an updated in_mp3.dll & in_midi.dll . . . the question is, how do we know if either of these are now
included in the download? I suppose we'll know if we get loads of posts from people with mp3 & mid plugin related
problems. Now there's a potential nightmare! Having to post endless links to the updated plugins . . .
I reckon a confirmation post from Justin wouldn't go amiss.
********************************************

I asked that identical question last night, as the first post in this new forum. The answer I got, was if Justin wants to do it, he will tell us. (or something like that) Since Justin did state, he was probably going to modify the 2.71 download, instead of doing another version, it would be nice to know what is going on.

I guess the fastest way to find out, is somebody download 2.71 now, and compare them. Justin also said, he was modifying AVS for 2.71 too, for the current download.

peter
17th December 2000, 00:44
(update: Justin says that my decompression support does bad things on Win2k; this is why it isn't bundled with WA setup. Whoever has Win2k installed, please test it and report, include your system specs.)
By the way, PP, how exactly does that read_file.dll thing work? How would Winamp know to redirect files to it?
Winamp3 will have new sort of plug-ins: readers (read_*.dll). Input plug-ins will not have to care about low-level file acces; they will just call Winamp's function to get a reader that supports given URL, then call reader's function to read data. For an example: URLs that begin with http:// will be opened by HTTP reader; this will enable all input plug-ins to automatically download files from the web. The 'original' read_file.dll from Tempura is a 'normal' file reader (reads 'local' URLs, like 'c:\music\x.mp3'). I've written a replacement DLL that does the same and automatically decompresses zip/rar/gzip/arj while reading; this simply causes all WA3 input plug-ins to read compressed files (Tempura's WAV plug-in doesn't seem to use readers for now, but who cares...).
I started DirectMusic plug-in v2.0 project several months ago. It was supposed to be Winamp3's default MIDI player. In some early beta I moved decompression routines to reader dll. I really didn't intend to port DMp2 back to WA2. In order to make testing easier (Tempura's stability is really bad), I wrote a simple Tempura input system emulator that runs under WA2 (simply translates WA2 calls to WA3 ones) and added code to use read_*.dll the same way Tempura does it (read_http.dll from Tempura doesn't seem to work, but I really don't care). (BTW, now I could port any WA3 input plug-in back to WA2 in 5 minutes, hehe). When Justin emailed me about including DMp with WA v2.7, DMp v2.0 beta was the most stable version available; there were tons of known bugs in v1.03 and I didn't feel like messing with old code. I've compiled two versions: one with read_file.dll (to allow other input plug-in authors to use it); one with decompression inside in_midi.dll (smaller total size).