Nope , AOL made a mistake.
I tried Foobar , BSplayer , VLC , others.
I found my "good ol' friend"- Winamp was the only media center I could
coax to do everything.
This thread will cover all 4 and what you need to do to get to this
level (below).
I have searched the world for plugins , many are still in development.
This architecture makes the main software's end of development irrelevant.
I was able to augment and expand it's capabilities way beyond the others.
Winamp is to media players what Windows 7 is to OS's - perfected. Same
"maturity" .
PS - all that on 2% processor. 😀😀
OS
I tried Foobar , BSplayer , VLC , others.
I found my "good ol' friend"- Winamp was the only media center I could
coax to do everything.
This thread will cover all 4 and what you need to do to get to this
level (below).
I have searched the world for plugins , many are still in development.
This architecture makes the main software's end of development irrelevant.
I was able to augment and expand it's capabilities way beyond the others.
Winamp is to media players what Windows 7 is to OS's - perfected. Same
"maturity" .
PS - all that on 2% processor. 😀😀
OS
Attachments
Last edited:
Ok -
Software -
-Winamp V5.666 ... most of the included plugins are bugfree.
Winamp 5.666 Released (Build 3516) - Winamp & SHOUTcast Forums
Respected source for it ....
-ASIOforAll driver - to replace the sound card's ASIO driver.
ASIO4ALL - Universal ASIO Driver
-Otachan's ASI😵ut.dll for winamp
WINAMP5? ASIO??????? (dll version) - ??????MIDI/Audio???
-Adionsoft WASAPI output plugin
adionSoft Winamp WASAPI Output Plugin - Freeware
These 3 output plugins (plus the native directsound_out ) will allow
you to interface with ALL soundcards. I have 6 systems , I can get all
to do ASIO .... some better than others. None crash.
-"Eye candy"-Classic spectrum analyzer ...
Classic Spectrum Analyzer - Winamp
- Paths.ini editor ...
Winamp & SHOUTcast Forums - View Single Post - Multi-user profile support in Winamp 5.11+ (inc Paths.ini Editor)
I will explain a better .ini setup and XML edit for winamp. We want
to compact and remove the library from "APPS". This help to keep
the library data unfragmented by browser caches and other dynamic
data. By being able to choose local and web paths , we can streamline
operation.
Next , I will go through the Winamp 5.666 setup. AOL added some B$ ,
but .... no malware.
OS
Software -
-Winamp V5.666 ... most of the included plugins are bugfree.
Winamp 5.666 Released (Build 3516) - Winamp & SHOUTcast Forums
Respected source for it ....
-ASIOforAll driver - to replace the sound card's ASIO driver.
ASIO4ALL - Universal ASIO Driver
-Otachan's ASI😵ut.dll for winamp
WINAMP5? ASIO??????? (dll version) - ??????MIDI/Audio???
-Adionsoft WASAPI output plugin
adionSoft Winamp WASAPI Output Plugin - Freeware
These 3 output plugins (plus the native directsound_out ) will allow
you to interface with ALL soundcards. I have 6 systems , I can get all
to do ASIO .... some better than others. None crash.
-"Eye candy"-Classic spectrum analyzer ...
Classic Spectrum Analyzer - Winamp
- Paths.ini editor ...
Winamp & SHOUTcast Forums - View Single Post - Multi-user profile support in Winamp 5.11+ (inc Paths.ini Editor)
I will explain a better .ini setup and XML edit for winamp. We want
to compact and remove the library from "APPS". This help to keep
the library data unfragmented by browser caches and other dynamic
data. By being able to choose local and web paths , we can streamline
operation.
Next , I will go through the Winamp 5.666 setup. AOL added some B$ ,
but .... no malware.
OS
Why not Foobar ??
I went with the "columns UI" for foobar.
(below attachment 1)
-no clickable art to play
-columns UI defaults to a playlist type operation.
Now Foobar is good , many of the ASIO output plugins for
winamp have Foobar equivalents .. often by the same plugin
authors.
I can even port DX-FFX-4 -
DX Rack series.
(at the bottom -freeware).
to foobar OR winamp. Any DX DSP can now run between the FLAC/MP3
decoder and the ASIO output. These DSP's run hidden by default (cool),
just click the FFX4 rack for any particular DSP.
This gives major DSP capability, (below 2).
All these have been run/tested for 3-10 years !! I started uing the oldest
"Sonitus DSP's" in 2004. Cakewalk and Steinburg bought it out in 2010
because it is so good ! Older V2 sonitus is still available online. V3 (like mine)
is 32 bit perfection - far exceeds the Foo or Winamp EQ.
PS - I added this same setup to foobar = >10% CPU vs. winamp 3%.
Foobar is just nowhere as mature as Winamp (15 years development).
OS
I went with the "columns UI" for foobar.
(below attachment 1)
-no clickable art to play
-columns UI defaults to a playlist type operation.
Now Foobar is good , many of the ASIO output plugins for
winamp have Foobar equivalents .. often by the same plugin
authors.
I can even port DX-FFX-4 -
DX Rack series.
(at the bottom -freeware).
to foobar OR winamp. Any DX DSP can now run between the FLAC/MP3
decoder and the ASIO output. These DSP's run hidden by default (cool),
just click the FFX4 rack for any particular DSP.
This gives major DSP capability, (below 2).
All these have been run/tested for 3-10 years !! I started uing the oldest
"Sonitus DSP's" in 2004. Cakewalk and Steinburg bought it out in 2010
because it is so good ! Older V2 sonitus is still available online. V3 (like mine)
is 32 bit perfection - far exceeds the Foo or Winamp EQ.
PS - I added this same setup to foobar = >10% CPU vs. winamp 3%.
Foobar is just nowhere as mature as Winamp (15 years development).
OS
Attachments
Last edited:
Setup ... (winamp)
Yes , AOL "bloated" the newer 5.xxx installation.
I use the " winamp5666_full_en-us_redux " only 9.6MB !
When you get to the components list (below).
-NO- (uncheck)
-NO !! "agent" (bloated chatty junk).
- sonic ripping burning /signal processor/or audio encoders.
- In output , to keep it lean .... no wave writer/waveout (just default directsound).
- (core media library) all the "core library" but uncheck the rest.
- user interface - No extended jump to file , tray control optional.
- Lastly , NO included visualizations.
Install , winamp will be a 21MB installation in program files/winamp folder.
It will ask what skin - (Big Bento) keeps the library/playlist all in one
compact window. Default is close to what is pictured in post #1.
It will try to communicate , abort.
(it's elevator.exe can not make a firewall exception).
And , the main winamp.com is gone ... as well.
"send data" entries in "error reporting" and "general preferences"
options -->preferences) uncheck any comm. boxes.
OS
Yes , AOL "bloated" the newer 5.xxx installation.
I use the " winamp5666_full_en-us_redux " only 9.6MB !
When you get to the components list (below).
-NO- (uncheck)
-NO !! "agent" (bloated chatty junk).
- sonic ripping burning /signal processor/or audio encoders.
- In output , to keep it lean .... no wave writer/waveout (just default directsound).
- (core media library) all the "core library" but uncheck the rest.
- user interface - No extended jump to file , tray control optional.
- Lastly , NO included visualizations.
Install , winamp will be a 21MB installation in program files/winamp folder.
It will ask what skin - (Big Bento) keeps the library/playlist all in one
compact window. Default is close to what is pictured in post #1.
It will try to communicate , abort.
(it's elevator.exe can not make a firewall exception).
And , the main winamp.com is gone ... as well.
"send data" entries in "error reporting" and "general preferences"
options -->preferences) uncheck any comm. boxes.
OS
Attachments
Next - fine tuning .....
Winamp went the "APP" way with its playlist/data folders.
It puts it in -
your other 3'rd party stuff (FF and chrome).
Once you compile your media libraries ... nothing much changes.
Why not have everything in one place ?
Program files/Winamp is a good place , take all the file/folders
out of the default "app" folder .... edit "paths.ini" (below 1)
example :
paste the "app" files/ folders there.
Attachment shows my finished setup.
You now have all things Winamp in one easy to access folder ...
(the main winamp folder). Winamp will no longer use "appdata" as a cache.
Before you establish your album database , you will still be <25MB
total.
Edit - Winamp is now "portable". The only registry entries deal with install/
uninstall. working paths and operation is NOT registry dependent.
OS
Winamp went the "APP" way with its playlist/data folders.
It puts it in -
Along with the browser Cache. Same dumping ground as all%AppData% Under Vista:
c:\users\<username>\AppData\Roaming\Winamp
your other 3'rd party stuff (FF and chrome).
Once you compile your media libraries ... nothing much changes.
Why not have everything in one place ?
Program files/Winamp is a good place , take all the file/folders
out of the default "app" folder .... edit "paths.ini" (below 1)
example :
-create a "data" folder (within the winamp folder) ,[Winamp]
cwd=%ProgramFiles%\Winamp
inidir=C:\Program Files (x86)\Winamp\data
m3udir=%ProgramFiles%\Winamp\data
paste the "app" files/ folders there.
Attachment shows my finished setup.
You now have all things Winamp in one easy to access folder ...
(the main winamp folder). Winamp will no longer use "appdata" as a cache.
Before you establish your album database , you will still be <25MB
total.
Edit - Winamp is now "portable". The only registry entries deal with install/
uninstall. working paths and operation is NOT registry dependent.
OS
Attachments
Last edited:
Create a database ...
Album art is any folder.jpg , I have found a 500 X500 jpg. is good for
HUGE databases. "folder" goes in the albums root directory.
PS - find >800x800 covers , reduce to 500x500 .... better than most
default cover art.
(below 1 example).
Art is put in -
1000 albums of (art) will create a 50MB "art" folder.
FLAC or MP3 works the same .... "folder.jpg" 500x500 pixel in the root.
Then you will have all the genre/artist's in one pane , album art in
the other (below 2).
OS
Album art is any folder.jpg , I have found a 500 X500 jpg. is good for
HUGE databases. "folder" goes in the albums root directory.
PS - find >800x800 covers , reduce to 500x500 .... better than most
default cover art.
(below 1 example).
Art is put in -
(using the last post's example "data" folder).C:\Program Files (x86)\Winamp\data\Plugins\ml\art
1000 albums of (art) will create a 50MB "art" folder.
FLAC or MP3 works the same .... "folder.jpg" 500x500 pixel in the root.
Then you will have all the genre/artist's in one pane , album art in
the other (below 2).
OS
Attachments
No offense meant ... but any "AIMP" search/or "AIMP spyware" that generates
472,000 hits is indeed dubious.
https://www.google.com/?gws_rd=ssl#q=aimp+spyware
Being created in the eastern bloc area is another red flag.
Many Russian links (infections) for this software !!!
- many infected plugins plus even a trojan " troj/agent -aimp"
Several antivirus companies have also flagged this software.
OS
Audiophile - ASIO
Found the right chain ... in_flac.dll --> otachan out_ASIO.dll -->ASIOforall .
(below 1)
This is a healthy chain . I can't break it. I can up/down sample while playing ,
(96>44 or 44>96) .. adjust the buffers , use hardware buffers - anything.
Main windows volume is active if you have the asioforall selected in the
otachan output plugin.
ASIOforall is just a windows install. the otachan out_ASIO.dll goes in the
"C:\Program Files (x86)\Winamp\Plugins" directory.
Some winamp plugins have installers , some you manually place.
In_Flac.dll is included with winamp.
This chain is quite efficient , CPU wise (below 2). Can't beat that !
The SQ is just phenomenal with either this chain or the adionsoft WASAPI
output. Both are under 5% , worst case (with visualization).
(below 2)
OS
Found the right chain ... in_flac.dll --> otachan out_ASIO.dll -->ASIOforall .
(below 1)
This is a healthy chain . I can't break it. I can up/down sample while playing ,
(96>44 or 44>96) .. adjust the buffers , use hardware buffers - anything.
Main windows volume is active if you have the asioforall selected in the
otachan output plugin.
ASIOforall is just a windows install. the otachan out_ASIO.dll goes in the
"C:\Program Files (x86)\Winamp\Plugins" directory.
Some winamp plugins have installers , some you manually place.
In_Flac.dll is included with winamp.
This chain is quite efficient , CPU wise (below 2). Can't beat that !
The SQ is just phenomenal with either this chain or the adionsoft WASAPI
output. Both are under 5% , worst case (with visualization).
(below 2)
OS
Attachments
Last edited:
Found it !
I have not seen anything like this !!
You install this update to the media library/skinning.
ClassicPro - Skin Consortium ClassicPro
Adds some
XML , updates ML.dll , and adds a few more folders. Don't let it
alter any path.ini / winamp.ini stuff (it asks you).
It comes with skins that have more or less "power".
Free Download - cPro - Insomnis v2 - Skin Consortium
"Insomnus" skin has 50 color variations and can search album and
title on the bottom art/info panel - kind of manual. Still , stable
and good looking. (below 1)
Free Download - cPro2 Dark Aluminum - Skin Consortium
The best of the best - this one will even ....
-pop up lyrics in it's browser , facebook pages , or wiki results for either
song or artist.
This can NOT happen , if you don't toggle the browser tab.
Fully tabbed search , folder/tree view , playlist , and album art -
just about everything. 50 colors. (below 2).
Strange to see a skin actually leverage more functionality out of
a program. There seems to be a lot of "unharnessed" features deep
within Winamp. Some of this is actually ported out to W7's existing
IE7-10 ... but Winamp itself gains scripted functionality.
Networking is next - I already have my 5 workstations going (easy and
flawless) ....
OS
I have not seen anything like this !!
You install this update to the media library/skinning.
ClassicPro - Skin Consortium ClassicPro
Adds some
XML , updates ML.dll , and adds a few more folders. Don't let it
alter any path.ini / winamp.ini stuff (it asks you).
It comes with skins that have more or less "power".
Free Download - cPro - Insomnis v2 - Skin Consortium
"Insomnus" skin has 50 color variations and can search album and
title on the bottom art/info panel - kind of manual. Still , stable
and good looking. (below 1)
Free Download - cPro2 Dark Aluminum - Skin Consortium
The best of the best - this one will even ....
-pop up lyrics in it's browser , facebook pages , or wiki results for either
song or artist.
This can NOT happen , if you don't toggle the browser tab.
Fully tabbed search , folder/tree view , playlist , and album art -
just about everything. 50 colors. (below 2).
Strange to see a skin actually leverage more functionality out of
a program. There seems to be a lot of "unharnessed" features deep
within Winamp. Some of this is actually ported out to W7's existing
IE7-10 ... but Winamp itself gains scripted functionality.
Networking is next - I already have my 5 workstations going (easy and
flawless) ....
OS
Attachments
Jriver - oops ....
Loaded 10K Flacs into Jriver = 10 minutes Winamp= 3:30 .
Edit - Jriver compresses album art even further to make it's database.
64bit Jriver ASIO crashes occasionally , 32bit can't take sample
changes like the Winamp otachan ASIO does. (will also crash)
I have ASUS 64bit/ASIO4all 32bit to port to.
Jriver is not as "abuse proof" as my winamp setup.
They have refined the GUI slightly over winamp. Treeview and
other file /art details are improved.
Jriver also uses less memory with a huge database (the more advanced
GUI).
But I could mis- set my ASIO4all
on winamp (no buffer) and not have a crash , 50$ .... Jriver should test
ASIO to buffer + latency for you (winamp ++) !!
Winamp actually "feels" much faster , but uses more memory.
Video is a joke on Jriver ... does not use a plugin type architecture
for codecs , you rely on Jriver.
I suppose the 50$ gets you support (and constant updates). Jriver
seems to really need it. 😀
PS- By testing WA/Jriver side-by-side , Jrivers core software is equal
to WA in 2008-9 (stability wise). If you used bad WA plugin's in the past ,
you might disagree. The recommendations in the first 9 posts of this
thread will get you a Winamp that is more stable/reliable and has nearly
the Jriver feature set. I can swap DS/WASAPI/ASIO "on the fly" with WA.
WA is also FREE !!
OS
Loaded 10K Flacs into Jriver = 10 minutes Winamp= 3:30 .
Edit - Jriver compresses album art even further to make it's database.
64bit Jriver ASIO crashes occasionally , 32bit can't take sample
changes like the Winamp otachan ASIO does. (will also crash)
I have ASUS 64bit/ASIO4all 32bit to port to.
Jriver is not as "abuse proof" as my winamp setup.
They have refined the GUI slightly over winamp. Treeview and
other file /art details are improved.
Jriver also uses less memory with a huge database (the more advanced
GUI).
But I could mis- set my ASIO4all
on winamp (no buffer) and not have a crash , 50$ .... Jriver should test
ASIO to buffer + latency for you (winamp ++) !!
Winamp actually "feels" much faster , but uses more memory.
Video is a joke on Jriver ... does not use a plugin type architecture
for codecs , you rely on Jriver.
I suppose the 50$ gets you support (and constant updates). Jriver
seems to really need it. 😀
PS- By testing WA/Jriver side-by-side , Jrivers core software is equal
to WA in 2008-9 (stability wise). If you used bad WA plugin's in the past ,
you might disagree. The recommendations in the first 9 posts of this
thread will get you a Winamp that is more stable/reliable and has nearly
the Jriver feature set. I can swap DS/WASAPI/ASIO "on the fly" with WA.
WA is also FREE !!
OS
I went with the "columns UI" for foobar.
Problem I had with foobar was, that, whatever I tried, I could not recreate the library view of Winamp. Especially the dual search-fields. I also use Winamp for music. Still the best, for me.
- Status
- Not open for further replies.
- Home
- Source & Line
- PC Based
- Windows + modified winamp media center