Previous Page | Next Page

by Lunar at 6:47 AM EST on January 16, 2010
man this delix plugin in xmplay doesn't play all the formats deliplayer does. :( or doesn't SEEM to. i was hoping i wouldn't have to reinstall deli. i hate it.
by Knurek at 7:36 AM EST on January 16, 2010
Lunar: It should play everything except for DigiBooster Pro IIRC. What format are you referring to? Some require adding replayers to the xmp-delix.dat archive.
by DrO at 8:14 AM EST on January 25, 2010
Seriously, it seems that the Winamp installer screws up the existing dlls somehow. So copy the fresh ones over the existing ones.
will have a look into it over the next few days as i'm wondering if the optimiser (is meant to re-base the official dlls for a loading time improvement) is messing with something but need to check it out properly.

and unfortunately 5.57x was a messed up release but 5.572 seems to have been better in general (unfortunately not for emu related areas it seems).

-daz

edited 10:53 AM EST January 25, 2010

edited 10:53 AM EST January 25, 2010
by hcs at 11:55 AM EST on January 25, 2010
Yeah, it looks like it's rebasing our dlls as well. I don't know enough about Windows linking to know why this would cause it to fail loading vgmstream, but that seems to be the issue. Is it just running on every dll in the Winamp dir?
by Hotcakes at 3:29 PM EST on January 25, 2010
Pretty sure it's not in_vgmstream.dll (or at least, not only vgmstream) - I replaced that but not the ogg/mpg dlls and still nothing loaded.

in_psf still works so maybe you can compare against it somehow, if he gives access to the source?

I do wish they'd leave shit alone if it's going to break stuff.
by hcs at 3:57 PM EST on January 25, 2010
Hotcakes, it doesn't seem like it touches in_vgmstream.dll at all, or libvorbis.dll from what I've heard, just the libmpg123-0.dll. And Dr0 is going to look into it when he gets the chance. In the meantime there's an easy workaround.
by DrO at 3:58 PM EST on January 25, 2010
hcs: that's the feeling i've got maybe happening but i need to get my hands on some more of the build system to be able to check that.

Hotcakes: it's never done intentionally to cause breakages, etc but unfortunately it can and does happen in particular with plug-ins that are still designed in the 2.x style instead of being better designed really for a 5.5+ style (so all unicode & newer api compatible).

in most cases it's generally issues in the external plug-ins (not helped that documentation is dire for large parts of plug-in integration) which are shown up by the changes in the client itself (like the change in compile has caused for some plug-ins).

and it's not helped that i've not been active around here for sometime to keep up-to-date with issues (like the v5.51 spectrum vis incompatibility crash which was caught from this forum/irc) as often an issue posted over here will be something many more are experiencing but aren't properly reporting.

either way i'll post back once i've had a chance to check things out and see what the issue is and see if a resolution can be done for the future.

-daz
by hcs at 4:30 PM EST on January 25, 2010
Hm, in the future should I direct people to the official forums, on the chance that it will get more attention there?
by Franpa at 11:45 PM EST on January 25, 2010
There forum is reasonably active
by DrO at 5:45 AM EST on January 26, 2010
hcs: if i'm not around then yes that'd be the best way if there is a major issue.

franpa: i'd have hoped so ;)

-daz

Previous Page | Next Page
Go to Page 0 1 2 3 4 5 6 7 8

Search this thread

Show all threads

Reply to this thread:

User Name Tags:

bold: [b]bold[/b]
italics: [i]italics[/i]
emphasis: [em]emphasis[/em]
underline: [u]underline[/u]
small: [small]small[/small]
Link: [url=http://www.google.com]Link[/url]

[img=https://www.hcs64.com/images/mm1.png]
Password
Subject
Message

HCS Forum Index
Halley's Comet Software
forum source