21 May '13 - 18:47 *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
 
  Home Help Search Login Register  
  Show Posts
Pages: [1] 2 3 ... 36
1  Developments / XMPlay / Re: XMPlay Stuff Labs: Experimenting with Cover & Rating. on: 7 May '13 - 00:47
Ian , wouldn't it be better if skin designers could assign specific visualization to their main/mini panel design with the relevant svp file attached? Designers could then integrate the correct placement and size for the visualization whether it is cover art , spectrum or other , to their design.
ReplyReply Reply with quoteQuote
2  Developments / XMPlay / Re: Suggestions for 3.8 on: 30 Dec '12 - 17:42
A big playlist-style skin as an option could help a lot. Smiley

Maybe combine the functionality of the extended info widow with the main window?
ReplyReply Reply with quoteQuote
3  Developments / XMPlay / Re: Suggestions for 3.7 on: 24 Dec '12 - 21:55
Saga, mlp(dvda) and dsd(sacd) are digital formats like any other and are not binded to optical media exclusively.
ReplyReply Reply with quoteQuote
4  Developments / XMPlay / Re: Suggestions for 3.7 on: 21 Dec '12 - 23:00
Is there a particular reason that you're interested in Foobar plugin support, eg. is there a plugin for some file format that neither XMPlay or Winamp currently has?

Two input plugins: DVD-A and SACD formats.
ReplyReply Reply with quoteQuote
5  Developments / XMPlay / Re: Suggestions for 3.7 on: 20 Dec '12 - 23:13
In the old days winamp was the standard for software music players. Since those days (apart from xmplay) foobar2000 had replaced it and took the lead. Is it possible to allow using foobar input plugins in xmplay or at least build a wrapper for them?
ReplyReply Reply with quoteQuote
6  Developments / XMPlay / Re: bit depth resolusion of pre-amp and dsp culculations on: 11 Dec '12 - 17:52
Although logically I think the pre-amp should be separate from auto amp , I can understand it is more efficient and simple to leave them joint together. Some dsp plugins though are less effective this way.

ReplyReply Reply with quoteQuote
7  Developments / XMPlay / bit depth resolusion of pre-amp and dsp culculations on: 11 Dec '12 - 03:20
I was checking out the vst host for winamp and saw something different from what I previously thought happening in xmplay.
I saw that 16 bit and 24 bit files were entering the vst host (32bit enabled) in their original bitdepth even though they had already been replaygained. I thought all calculations were made at 32 floating point resolution.Thus after changing a track gain it would show more than 16 bit , ie 32bit.

Isn't pre-amp section applied before other dsp plugins?
Isn't pre-amp applied already in 32 bit floating point resolution?
ReplyReply Reply with quoteQuote
8  Developments / XMPlay / Re: Clarification for Output Resolution and Bitrate on: 17 Nov '12 - 09:50
As I understand it , all files are initially transformed into 32 bit and all calculations (pre-amp,dsp,volume) are done with the added accuracy. Then at the last stage the audio stream is truncated to the desired bit depth (after dithering or without it).

Sample rate is a different aspect of the audio stream that is not related to bit depth. I am guessing a change of it is done , if requested , just prior to the last bit depth change.
ReplyReply Reply with quoteQuote
9  Developments / XMPlay / Re: Suggestions for 3.7 on: 9 Sep '12 - 17:38
Many times I want to skip a group of files but currently it is not possible. I choose files of the same album , folder or genre but It is not possible to skip to the next track after those selected. Is a change of this possible? When going down the list (List nav - down) after a group of tracks was selected the cursor would go to the first track below the selection.
ReplyReply Reply with quoteQuote
10  Developments / XMPlay / Re: ASIOx as Kernel Streaming in xmplay (for XP users with low-end sound cards) on: 9 Sep '12 - 17:21
Such debates are pointless. Without any concrete evidence of the differences it is impossible to isolate the factors that differ the listening experience between users , whether these are physiological , technological or psychological.
ReplyReply Reply with quoteQuote
11  Developments / XMPlay / Re: Whitecap & G-Force dont work on: 5 Sep '12 - 05:38
G-force vis plugin
ReplyReply Reply with quoteQuote
12  Developments / XMPlay / Re: Suggestions for 3.7 on: 29 Aug '12 - 17:11
The target playlist entry should already be highlighted when hovering over it, the same as when not drag'n'dropping. If it isn't, please try another skin, in case the skin's colour scheme means that it's not very noticeable.

I thought that instead of highlighting the tracks entries themselves xmplay can highlight the space between them. Thus when you hover (while dragging files) the upper half of a track row , a line above will be drawn and the files will be inserted there; if you hover the lower half a track row , a line will be drawn below it and the dragged tracks will be inserted beneath it.

Regarding the 2nd idea, that seems like it would break the ability to easily drop files to the end of the list. Currently, if files are dropped outside of the playlist but in the playlist panel, the files will be added to the end of the list. Wouldn't your suggestion prevent that?

One solution would be to accelerate the scrolling speed as you move away from the lower or upper edges of the list. After a distance the scrolling speed can be as high as getting to the end (or beginning) of the list instantly.
Another option can be to drop the files at the end of the list when you add right click to the constant hold of the left button(while drag and dropping files).
ReplyReply Reply with quoteQuote
13  Developments / XMPlay / Re: Suggestions for 3.7 on: 20 Aug '12 - 12:48
Hello ,

A couple of suggestions regarding drag and dropping files into lists:

1. When the DragN'Drop cursor is hovering the list a line between track lines will indicate the target destination of the inserted files.

2.While in DragN'Drop mode crossing the down or up edges of the list will scroll the list up or down slowly. Going further from those edges will increase the speed of the scroll.
ReplyReply Reply with quoteQuote
14  Developments / XMPlay / Re: Suggestions for 3.7 on: 18 Aug '12 - 03:23
Wouldn't it be easier to add in the xmplay.ini an option to set custom folders for skins,plugins,library,playlists? Then all instances of xmplay can share part of the core data.
ReplyReply Reply with quoteQuote
15  Developments / XMPlay / Re: Suggestions for 3.7 on: 9 Aug '12 - 04:10
In addition to replaygain options "album" and "track" can you add also "auto" mode?

In auto mode if a track before or after the current track are of the same album then album replaygain would be selected , otherwise - track replaygain data would be selected.

This functionality is impossible when in Random mode, since the following track will not be known. Also, such a thing would heavily depend on metadata information, which may be inconsistent or not present.

The best solution would be to have the user set up the playlist and RG mode the way they want it. Even with playing random tracks, I often use Album Gain data.

In random mode , there is no point in using album replaygain data because no continuity of volume level needed to be maintained.

The absence of some data is not restricting here as xmplay can always fall back to track replaygain data or no replaygain at all. Actually it is how xmplay is currently behaving when album replaygain option is chosen.

I asked for this option because I switch lists quite often and only part of them are sorted by albums , thus I need repeatedly to switch replaygain options. Other wise albums sound uneven (with track replaygain) or mixed tracks sound too quite/loud (with album replaygain). If there is a way to make xmplay be smarter - why not?
ReplyReply Reply with quoteQuote
16  Developments / XMPlay / Re: Suggestions for 3.7 on: 5 Aug '12 - 16:55
2. Add max playlist width setting. Sometimes when I listen to Japanese music and add single track playlist explodes to screen width D:

For your second request there is a solution: the function 'cut' in the titles format section.
%cut{vaiables|maximum length|text to put after cut string}
%cut{%2 - %3 - %5 - %1|30|...} => "artist - album - tracknumber -..."
ReplyReply Reply with quoteQuote
17  Developments / XMPlay / Re: Suggestions for 3.7 on: 17 Jul '12 - 15:47
Here's one more:  Wink

When selecting a track from the "recent tracks" list , the list will jump and highlight the track but won't start playing it. Many times I only want to locate recent track and play the next on the playlist.
ReplyReply Reply with quoteQuote
18  Developments / XMPlay / Re: Suggestions for 3.7 on: 16 Jul '12 - 00:28
In addition to replaygain options "album" and "track" can you add also "auto" mode?

In auto mode if a track before or after the current track are of the same album then album replaygain would be selected , otherwise - track replaygain data would be selected.
ReplyReply Reply with quoteQuote
19  Developments / XMPlay / Re: Suggestions for 3.7 on: 4 Jul '12 - 20:26
I was thinking a little more about multiple playlists implementation. For me a button for "new playlist" can replace the current "save list" button. Left clicking  this button would start a new playlist after auto saving the previous. Right clicking the button would show previously auto-saved playlists (stored in the xmplay app-data folder). In addition to that list there should be a few management commands for current playlist . Commands like "Save as" that would act as the current save button, "Rename" and "Remove" to delete playlist from the hard drive and list.
ReplyReply Reply with quoteQuote
20  Developments / XMPlay / Re: 3.6 reports, queries and bugs on: 18 May '12 - 22:55
Hello ,  I am using 3.6.0.61 (stuff) version. Monitoring library folders seems not to be working (also did not work on previous 60 version).
ReplyReply Reply with quoteQuote
Pages: [1] 2 3 ... 36
Powered by SMF 1.1.18 | SMF © 2013, Simple Machines