Sign In:     

Forum: Wishes and new features

Topic: Skins - Wishes and new features - Page: 15
PhantomDeejay wrote :
Personally I use a "file catalog" system that pretty much prevents duplicates for the most part.
Don't get me wrong, I do have some, but not that many.
So, for me my main folder/filename structure is like this:

Drive/Music/2025-2029/Artist - Title (Remix).ext

If I download a few older songs today and try to put them on the '2000-2004' folder (as an example) then 2 things can happen.
Either the song exists allready (and therefore I can check if the newer version I have is better quality or not) or it doesn't so the new file gets in place anyway.

I choose this system because the year of a track release is pretty much a constant that can be determined very easily. It's not like "genre" where tracks can fall into two or three or even more genres and subgenres.
I use the tags of the files to set "genres" correctly, and then I rely on the tags to set up filter folders that give me the equivalent of what other dj's get when they use the "Genre" folder split format.

Finally I pay great attention to the source of my downloads. I know pretty much that the pools I use provide "real" high quality content, and I rarely (if ever) have come across a "fake" bitrate file.

Just some food for thought..


thanks for comment, this way you expose can be a solution andwill try to adopt it, but at this moment i need a fast way to select and discard songs. first thing to do it is quallity and second thing to consider will be how fine the grid is generated.
i´m amateur so my tracks come from all kind of sources...
i´m not worried if isn´t perfect way, if after clean duplicates i feel some track isn´t good sound can try to get it again...
so this comments are great and help me (hopeto other too) to continue learning things about this great hobbye who unites us.





groovindj wrote :
I can only give you my opinion and my method, but you may not like it!

I've already suggested not to rely totally on whether certain frequencies are present, because even in a good quality recording, they may not be there. I also would not depend on using software to make a decision for me. My ears and my brain are my tools.

If a track sounds bad, I will replace it - not just because it's 128k bit rate or because it doesn't have content above 15kHz, but more likely because the balance between frequencies is incorrect, or I don't hear things clearly enough.


it is exactly what i thought, that you did not have a solution to the question, i really appreciate your comments, but i immediately realized that the way you use it is very slow and tedious, that it has nothing to do with whether it is better or worse, but as you can imagine, what you do i already knew how to do it and it is precisely what i tried to avoid. thanks anyway, and sorry if i was a bit hard.
when say about age from audience make me smile a lot, because is a great thrut
 
Just to add to the above, I do the same as George (although all video) by 5 year folder and version. If I get a new better or upscaled version I just replace the original one then rescan and re-do the stems and cue point so it maintains it's place in playlists, history and keeps the play count.

I also agree with @GroovinDJ (for once) :) in that the bitrate isn't the sole determinator whether a file is "good" or not. I have some 128 files that sound and play fine. I use my ears and good quality headphones to decide rather than software.
 
user24401128 wrote :
you did not have a solution

I did - but it wasn't what you wanted to hear.

user24401128 wrote :
it has nothing to do with whether it is better or worse

It has everything to do with whether it's better or worse. I'm judging with my ears, not software, bitrate or high frequency content. I'm making my own decision, rather than leaving it to an algorithm.
 
groovindj wrote :
user24401128 wrote :
you did not have a solution

I did - but it wasn't what you wanted to hear.

user24401128 wrote :
it has nothing to do with whether it is better or worse

It has everything to do with whether it's better or worse. I'm judging with my ears, not software, bitrate or high frequency content. I'm making my own decision, rather than leaving it to an algorithm.



Ok. thanks for all. great comments and absolutely rights all things you wrote, awesone....

CONTINUA SEARCHING FOR METHOD TO SELECT AND DISCARD DUPLICATE FILES. IT HASNT BE PERFECT, LIKE MYFRIEND GROOVINDJ, NOT SEARCHING FOR PERFECTION, ONLY WOULD A TOOL FOR IT, DON´T WANNA HAVE TO HEAR EACH OF ABOUT 4K FILES DUPLICATES IN MY LIBRARY...

Some one knows about tools who ADION was refer?
 
we need to have more options to customize the browser, if you guys can't work why whe can't add some useful things to the browser like custom layouts or different instances of browsers, custom columns ( not only user 1 or 2 ) , different styles per columns
 
POI visibility

I wish a verb could allow to change visibility of POIs. In my specific case, I would like to be able to toggle First Beat and Load Point from Invisible to Marker Only to see them in the skin waveform. I guess it could be interesting to do similar things with MixPoints and Automix cues. Thanks.
 
Lowering the entry level, should "no overlay" choice of video skins "edit this skin" create a "hello video skin" xml, just so how to move/resize/new focus becomes easier to explain.
 
BEEP

I'd also love to have a beep verb. The first reason could be for debugging, as a way of tracing if a part of code is being used or not. The second reason would be to easily check if transposition is fine, or if the right key was detected. It could be done like this: deck XX beep 500ms 'A#m'. I suggest using the base note of the key since it would be directly compatible with get_key. Thanks!
 
"Having the option to change the custom buttons’ color would be very useful."
thx!!!
 
djsadim wrote :
"Having the option to change the custom buttons’ color would be very useful."
thx!!!


Skinwise "custom buttons" don't differ from any other buttons. So, It can be done already.
Unless you mean something else..
 
PhantomDeejay wrote :

Skinwise "custom buttons" don't differ from any other buttons. So, It can be done already.
Unless you mean something else..


George yes, I mean having a drop-down menu to select a color, like the one that already exists for the custom button’s name.