23 May '13 - 20:36 *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
 
   Home   Help Search Login Register  
Pages: 1 ... 25 26 [27] 28 29 ... 34
  Reply  |  Print  
Author Topic: Suggestions for 3.7  (Read 86930 times)
amit
Posts: 718


« Reply #520 on: 11 May '12 - 19:56 »
Reply with quoteQuote

With files with sample rate higher than 96000 my sound card buffer experience buffer underruns. To avoid this I need to downsample the files permanently or to resample all files inside xmplay.
That sounds strange. What output system are you using, and does increasing the buffer length help? Is 96000 Hz (or lower) the soundcard's highest supported rate? If so, ASIO or exclusive mode WASAPI output would automatically be limited to that (anything higher would be resampled to that).

My super sound card  can handle 192khz files. Its driver though is not so super  Wink  It is ESI juli@... In ASIO and WASAPI (exculsive mode) It plays without resampling 192khz but even setting the drivers' highest buffer length isn't enough to eliminate all buffer underruns.

I wouldn't want to eliminate for everybody the possibility to listen at 192khz , thus I thought to add this as an option and using "save setting" seemed logical without much fuss.
Logged
kokocipher
Posts: 10


« Reply #521 on: 11 May '12 - 20:41 »
Reply with quoteQuote

I want VSTi FX support on individual midi channels.  It'd be especially nice for songs with Overdrive guitar channels so you can apply Wahs, dist, and flanger.
Logged
kobiyashi
Posts: 3


« Reply #522 on: 11 May '12 - 21:33 »
Reply with quoteQuote

Quote
Here's an update that shouldn't flash and steal focus when the "-tray" option is used...

Excellent! Thanks, Ian!  Smiley

kobiyashi
Logged
Knurek
Posts: 499


« Reply #523 on: 13 May '12 - 14:57 »
Reply with quoteQuote

Ian, any chance for an increase in the maximum amplification value?
The update above extends the auto-amp range to 20 dB. Let me know if it still isn't enough.

Some silent tracks hover around +20 dB (fluctuate between 19ish and 20.0), but overall I think it's loud enough already, thank you.
Logged
kokocipher
Posts: 10


« Reply #524 on: 14 May '12 - 20:56 »
Reply with quoteQuote

How about auto adjustment for EQ: if the song's Treble is too high, it'll lower treble, if the bass is too low, it'll raise the bass.  The module will keep adjusting the EQ sliders as the song progresses.

User can also customize the degree of the adjustment: slight, normal, extreme.

slight adjustment: increase/decrease up to 30%
normal adjustment: increase/decrease up to 60%
extreme adjustment: increase/decrease up to 100%

or user can just type _% in.
Logged
sneakernets
Posts: 4


« Reply #525 on: 14 May '12 - 22:59 »
Reply with quoteQuote

Skin support for "equalizer curve" like WA2.9's EQ curve, for aesthetic purposes.
Manual entry for frequency ranges.
Logged
Alexsource
Posts: 258


« Reply #526 on: 25 May '12 - 19:17 »
Reply with quoteQuote

Been a long time since I last posted over here! Cool Cool

Some of you will not like this suggestion, but here goes...  Wink

How about some kind of ... online tag metadata search for module files in the xmplay library? (.MOD, .MTM, .XM, .IT, ext.)
It could search for the file title OR the filename OR both in sites like modarchive, pouet, nectarine or others and pull it from there, then prompt the user, you get my drift. Grin

Yes, most of my mods are not tagged in the library, and yes I'm a bit lazy Tongue:P
Logged
saga
Posts: 1365


« Reply #527 on: 26 May '12 - 13:02 »
Reply with quoteQuote

I don't this would work too well:
- You can search by file hash at ModArchive (which is IMHO the only search method that would make sense), but there is not much metadata associated with the tunes (author is mostly missing)
- Pouet is only a database of demos, not modules
- Nectarine usually doesn't store the original mods, so you'd get a lot of false positive with duplicate titles and such.
- ModLand and AMP don't seem to support search by file hash.
Logged
Alexsource
Posts: 258


« Reply #528 on: 26 May '12 - 23:49 »
Reply with quoteQuote

Never thought of hash, that would be the perfect to search indeed Wink
Yeah, modarchive don't usually have that much info. Undecided

Mmm... I guess it could use nectarine, modland, amp or others, search by title / filename, and narrow the duplicates down by song lenght / file size?  Huh Wink
Logged
saga
Posts: 1365


« Reply #529 on: 27 May '12 - 12:27 »
Reply with quoteQuote

That's something you can do manually, yes, but necessarily by using a machine. The problem is that there might be two MOD files called "foo", they could even have a similar size, and you want to listen to one of them. Now who made the "foo" track you are listening to, author 1 or author 2? You can easily determine this by listening to the tune or reading the sample text - a machine can only guess which of the two is the correct author.
Logged
Tsorovan
Posts: 1244


« Reply #530 on: 27 May '12 - 22:31 »
Reply with quoteQuote

How about freetext search of the instrument/sample names inside of the mod files?
Logged
Jace
Posts: 773


« Reply #531 on: 28 May '12 - 15:10 »
Reply with quoteQuote

Saga: Much like the cddb plugin lets you pick from several alternatives if there's more than one match?
Logged
Ian @ un4seen
Administrator
Posts: 15270


« Reply #532 on: 28 May '12 - 16:11 »
Reply with quoteQuote

Fetching info on MOD files from an online database would be a nice thing. I'm not familiar with what databases are available. Are there any that can return formatted (eg. XML or something) results, or would it require parsing of a webpage to extract the information? The latter wouldn't be very reliable, as the webpage layout might change.
Logged
Alexsource
Posts: 258


« Reply #533 on: 29 May '12 - 02:48 »
Reply with quoteQuote

Saga: Much like the cddb plugin lets you pick from several alternatives if there's more than one match?
That was what I was getting at.  Wink Yet, saga's point is valid, there might be too many alternatives.

How about freetext search of the instrument/sample names inside of the mod files?
This could be enough in some cases, at least to narrow down the artist. BTW, several mods i have have the artist included in the title, e.g.:
Title Metropoli by JosSs
File jos-mtrp.xm
Path D:\Música\xmplay\jos-mtrp.xm.zip
Size 377701 bytes
Format FastTracker 2
Channels 6
Patterns 11
Instruments 31
Samples 27 (8 bit)
Length 1:32 - 12 orders - looped
Output 48000 hz - stereo - 24 bit
DS mix software


Fetching info on MOD files from an online database would be a nice thing. I'm not familiar with what databases are available. Are there any that can return formatted (eg. XML or something) results, or would it require parsing of a webpage to extract the information? The latter wouldn't be very reliable, as the webpage layout might change.

Mmm... I've just checked, and nectarine seems to have a XML interface for the songs pages:
http://www.scenemusic.net/demovibes/song/35845/
versus
http://www.scenemusic.net/demovibes/xml/song/35845/

and apparently, modarchive has an API : http://modarchive.org/index.php?xml-api
they seem to want to track the traffic or somewhat (did not read all the way, mind you)...

There might be others...
Logged
saga
Posts: 1365


« Reply #534 on: 29 May '12 - 09:57 »
Reply with quoteQuote

they seem to want to track the traffic or somewhat
Do we? That would be new to me...
Logged
Alexsource
Posts: 258


« Reply #535 on: 29 May '12 - 11:16 »
Reply with quoteQuote

they seem to want to track the traffic or somewhat
Do we? That would be new to me...

Quote
API Key

The Mod Archive does not have unlimited resources, therefore it is necessary to ensure that there is some limit on the access to the API, this is done via an API key. API keys are granted upon successful application review, and also allow API-load to be tracked on a per-application basis.

This is the bit of text i was refering too.

Logged
saga
Posts: 1365


« Reply #536 on: 29 May '12 - 12:40 »
Reply with quoteQuote

Load tracking != traffic or user tracking. This is just to prevent that a single application that is accessing the API leeches off all the resources.
Logged
Alexsource
Posts: 258


« Reply #537 on: 31 May '12 - 02:58 »
Reply with quoteQuote

Load tracking != traffic or user tracking. This is just to prevent that a single application that is accessing the API leeches off all the resources.
Yes, that's right.

Are there any other sites that could be used? the more the merrier Wink
Logged
Ian @ un4seen
Administrator
Posts: 15270


« Reply #538 on: 31 May '12 - 17:47 »
Reply with quoteQuote

I think ModArchive is looking like the best of the databases mentioned so far for searchability, but as saga mentioned it doesn't always provide any additional info (artist and genre info is available some of the time from my small sample of checks).

Is the artist the main thing that you're looking for? If so, that will usually be somewhere in the file's texts, so perhaps XMPlay can try to extract that, like it does the year. The artist is a bit trickier to detect than the year though. I did implement a basic artist detection system at the same time as the year detection, but it gave mixed results, so it was left out. I'd say it gave a decent result 50% of the time, nothing 45% of time, and rubbish 5% of the time Smiley ... I could try resurrecting that if there are no better options.
Logged
saga
Posts: 1365


« Reply #539 on: 31 May '12 - 23:13 »
Reply with quoteQuote

I think ModArchive is looking like the best of the databases mentioned so far for searchability, but as saga mentioned it doesn't always provide any additional info (artist and genre info is available some of the time from my small sample of checks).
Note that there's also "guessed" artist information (taken from ModLand) available if one is logged into the site, and this is also available when using the XML API - meaning that you'd get artist information for many more tunes than normally visible on the site as a guest.
Logged
Pages: 1 ... 25 26 [27] 28 29 ... 34
  Reply  |  Print  
 
Jump to:  

Powered by SMF 1.1.18 | SMF © 2013, Simple Machines