yes that would be cool, or a feature to change individual tracks back to white would help

I would like it if the tracks only turned green (and went into the review crate) after a certain amount of time (30 seconds maybe?). I think this has been brought up in the "review section" discussion, but I think it's relevant here as well.

OR... if you load a track to the first deck, and then add another, only have the last track loaded to that deck turn green. In 1.5, you can view the log and see what song was loaded to which deck. I can tell what I REALLY played by ignoring the duplicate tracks on Deck 1 for example.

In this case, a track can turn green once it is unloaded after a track has been loaded to the other side. A) and B) will represent each deck in this example:

Deck A) Load song1 - song1 does not turn green
Deck B) Load song2 - song2 does not turn green
Deck A) Load song3 - song1 turns green
Deck A) Load song4 - song1 stays green, song3 does not turn green
Deck B) Load song5 - song2 turns green
Deck A) Load song6 - song4 turns green

Make sense?

Damn that was a good idea....

To late :-D To be fair... its not my idea, either.

All ideas would help me :-) .

Yes. It`s great that you have thought about song3 loaded in Deck A which didn`t turn green because song4 was also loaded in Deck A right after it BUT still before Deck B was changed.

This would also work with the "next" and "previous" buttons.

Hey SSL Team, please make it work.

Damn it!!! Oh well... not sure who it was, but props to them. Thanks nik.

Oh a side note, I thought about other instances... like when a track is ejected or if ScratchLive is closed while tracks are playing. In either scenario I think those tracks should be logged as well. I'm sure there's enough logic to it they could make it work.

Why not put an additional button next to each deck which you can press if you are actually going to play the track? You can have an option in setup to use the extra button click of leave it as it currently is.

-Niche

Sounds like too much work. The idea from Deez is much better IMHO.

very stupid question I know but it turns green when I load it play it for a sec or whatever but what does it really mean when its green????????

it means you played it. it's a way of letting you know what you've played. AND it goes to the "Revies" section (just hit the button) and it shows you what you played in chronological order.

the problem is, if you just preview a track without playing it, the song will turn green and go into the list.

i believe all this should be in the manual. it's a good read if you haven't read the whole thing yet.

thanks deeznuts

My current workaround is by using itunes to preview, but that means i have to search for songs in itunes then i have to find it again in ssl

yeah, it`s a good idea - but it could be easier with DeezNotes` suggestion

I like the idea that it turns green after a certain amount of time... It would kick ass if we can manually set that time.

I think DeezNotes is the best and most intelligent solution because automatically only the last loaded song in the not loud playing deck will turn green when the loud playing deck gets unloaded or replaced by a new track.

If you would manually set a time it would be probably too hard for SSL to understand the time if you put the needle back and forth to go to certain parts of a track while prelistening.

That's what I was thinking. If you load a track and you're getting ready to play it or you go get a drink (longer than the time threshold), then someone asks you to play something else, you'd want the actual song you played to get logged... not the one you loaded a few min. ago but never played.

This would help when there's more than one DJ. We still have to ask each other "did you play this?" because all tracks turn green... even ones we preview.

Give us this, please!

dont wanna start a new thread for this but i'd like to see an option for sorting the tracks by colour.. so u got all the white ones on top of the listing for example

Perhaps a simple solution for a revision to this review list feature is needed. Make the DJ mark "track played" manually. We do it all the time, manually, by tilting our records in the case or moving them to the back. What about a keystroke or UI element that could be activated/clicked. Its kinda like building a crate manually (drag and dropping) as you go along adding only those tracks you played.

It seems to me that the solutions provided so far appear to rely on one DJs playing style or the other; or make an assumption that doesn't work for a good set of situations. They're all good ideas and brainstorming can bring up some great solutions. As I was reading these, I had some concerns.

A fixed time counter is doomed. I'm certain there is no single magic number of seconds that could indicate that a track should be considered played for the DJs and music styles around the world.

A time counter that can be configured is a step better. But then you run into the problem of needing to adjust it when playing different music styles, samples, etc. And if you change styles/elements during a set, you're spending too much time in the setup screen twiddling a setting.

The alternating "if I'm playing a track on #2 and the DJ just loaded a new track on #1, then log the track on #2 as being played" is innovative, but relys on a DJ alternating 1, 2, 1, 2. There is also the boundary condition (they are usually the problem ones) of the last track. How does the system log the last track in your set. Do you have to cue up one on the other table just to log the one you previously played? Does the system always log the last track that has an active control single before you close the app? What if there is a DJ playing after you? These three all sound like a hack. I don't like any of my crackpot ideas to solve the last track problem.

I guess I'll always be a program manager thinking how to describe the feature so it meets a customer's need and is clear enough for the dev and testers. I do hope that these forums provide useful information to Serato

That's what I stated in one of my posts (I think).

Your first idea would be much easier if they made no modification to the current config. I've done this by going to the review section and dragging all songs to a crate. After closing SSL, you can open that crate file in a text editor. I had to do some hard Find+Replace plus some manual editing to get it somewhat cleaned up. I think there was still an issue with *some* songs not being logged if played in a certain order. Still easier to do it this way than manually tagging IMO.

I also thought about if a user was DJing only on one side (with Auto turned on or something). I suppose if a song reaches the end and another song is loaded on the same side it would log these songs, but your point is still valid. It gets tricky.

The log included in 1.5 was nice, but that had to be removed so... ?

But who cares if they're green?

or how about a way to UNDO the green line by line????

Because you can tell what songs you or another DJ has played during the course of the night.

If I just pre-listened to songs I could forget to play them during a set because they are marked as played already.

^^ sometimes when sampling thru a bunch of tunes trying to find a new direction to take the crowd I quickly sample 10-15 tunes. That gived me 15 'green' songs which is incorrect! not to mention annoying. I'd like to think SSL could determine if I sampled or played them. Give me some way to clear individuals not a whole crate.

Except of ...



... DeezNotes found out a superb solution already. It just needs to be added in SSL :-) .

not turning green for so many seconds would be nice

I thought so too (at first), but it won't be efficient if you're mixing very quickly or...

thought about that but i didnt want to just type "bump"

bump

I hate when people just type "bump"
Oh wait that was me a month ago....

Has it been a month yet?
No?
Oh well

bump

FIX this please!
at least make ctrl-z work correctly!

pump

pumps in the bumps

biddump.

lol - you can stop bumping this now :)
You've got my attention already
(and yes, I've seen the other thread [www.scratchlive.net] on this too)

and inside info on how you are going to squash this issue?

Still have to properly read through you guys feedback and have a good think about what will work best :) but it's a bit down on my list of things to do at the moment (and its a loooong list)
Still at least you guys know that this issue is on the radar so you don't need to keep bumping desperately.

If you do have any new ideas and thoughts on this issue please post them here or on the other thread and we will take them into consideration

Okay, so just to make sure this doesnt get lost...

I suggested this same theory a VERY long time ago.....

I was quickly shot down, by those dj's that let a long track play or run a loop on deck 1 - and drop snippets of other tracks on deck 2. These overlays tracks wouldn't make the 'played' list. The above only works for traditional mixing of back and forth on 2 decks. I really think this gets ulta confusing, suppose I'd be happy with setting a minimum time limit of a track being played in order for it to be added to the 'played' list. [must play track for 1:30 before being added to played list]

It sounds like it uses something like "if track x is still on deck a and stopped while track y is playing on deck b, add track x to played list." And vice versa for the b tracks.

I think KaGeN's idea is easier to implement though... SSL probably uses something like an "onload" handlers for each deck... so when you load a track onto the respective deck, reset the current timer for the track after each load then if the time is longer than the users preference, add to played list. simple and effective imo.

That was some what similar to what djkevinz said in reply to my post:

"I think I figured it out - How about it only turns green if you change the OTHER deck while you're playing it. That way only songs you mix out of turn green. I think that's the only way for SERATO to know that you really played the track."

Seems pretty straightforward and relatively simple to implement.

mike

I like it, but I do think that sometimes what we think is easy and straightforward for us could be nightmarish and difficult for a programmer. Who knows.

Still, this is a pretty important feature in my list. So I say BUMPEETEEBUMP!

What???

Come on fix this ASAP

To me, this is where the confusion for the programmers come into play. They have to make *everyone* happy. When there's more than one option, I begin to think that we may need an optional setting. As it stands now, we have 3 options: 1) the current review method; 2) time based threshold; 3) track load logic.

I don't know how they're gonna do it, but I'm glad to see they're working on it.

Options make nik39 happy.

imho, I like the the time-based method myself... that would let at least let the user specify, depending on their preferences. For anyone who does quick in/outs (or say throw in a bit of scratching here and there), I'd want those tracks to be included as well, listed as "teases" in the mix. Others might not want to do that.

Having a slimmer list of tunes is better than the BLOAT you get if you just plop the track on for a few seconds to listen to it and determine if it's what you're gonna play next. I think you should be able to enable a "traditional" mode 1/2/1/2/1/2 - based on the above theory, and also have a timer feature that works in conjunction or seperatly.

Well, the issue here is just the tracks turning green and I suppose being added to the review section. As far as a track listing of played songs, that would relate to the "playedsongs.log" file feature request. I remember reading somewhere that this would come back as a new "feature?"

Maybe we could use them both in a way to narrow down what was played at the end of the night, but I guess we should leave the option open to each individual DJ as to how their tracks get marked as played/green during a set?

Backspin: !PMUBEETEEPMUB

Echo: B B U U M M P P E E E E T T E E E E B B U U M M P P ! !

Word.

all Pene - we did all the hard work for you... start coding. -lol

I'm with this - I just want a simple button to click on or next to the deck that marks the track green (played). And then turn off the auto green.

While this would be neat, the less keystrokes the better - I'd much rather be messing with my records and not have to worry whether the track got marked as played (by whatever system is implemented). I think an automated system would be optimal with a manual option if possible.

Not fixed yet !

We need "right-click" with a *reset* option for the track maybe. The time limit suggestion that somebody made for "preview" listening is another great suggestion!

personally, id be happy with the log telling me which deck i loaded the track onto and for how long it was loaded on there. i could establish my set list from that... but i suppose that isnt really the issue.

the options i see are thus...

1. delay 30 seconds before a track goes green. i from time to time play little samples of songs, just to scratch over the top, and ill come back to it. this might mean that i will load two tracks onto deck a within two minutes. i dont necessarily want that track to go green, i put it in the prepare list. in another instance, i will sometimes play the break, the sample source, but this might be for less than 30 seconds... id really like to know that i did drop the break before the tune, for example, the calcuttas before one thing. however, i dont need that tune to go green.

2. a manual process - a keystroke to make the track get logged. its not gonna work for me, im too busy thinking about tunes.

i really think that DeezNotes idea will work for the track marking... but i definately want to have my tracks logged, what track it is, its id3 tag and its filename, which deck it was loaded to, and what time it was loaded - that would just be schweet.

sorry for joining in late - not meaning to flog a dead horse.

No problem. I think we can rest assured that they'll get this feature added along with the track logging feature. That's another one I wanted to have back from one of the beta versions. It works very well for track logging and troubleshooting. Sam also promised that feature was coming back as well.

One really simple solution would be to make ctrl-z ( UNLOAD LAST TRACK ) mark the track as not played, as it's supposed to do.

Instead it just unloads the track but leaves it marked as played.

I don't think they fixed this in 1.6.3, but I'll check later and report.

the idea that tracks turn green is that it could help djs who play the traditional way not to repeate a track. people who scratch can use the same sample/song to scratch several times without the need to know if they've been using it earlier ..

.. allthough we all want to know in what context we used the tracks/samples. time information on how long a track was loaded and on which deck in the review could do the trick .. especially if exported to external text file (not possible now i suppose) ..

maybe a button to just turn one track at a time back white.... or you could right click and do it on a track (for those who use muti buton pads/mice... for the macbook guys.. just hold don control while clicking right clicks for you)

i thought i was traditional, how many times with vinyl i used to change my mind & go digging for something else

How about the prepare section. Don't you hate when you load a few tracks in there and as you start previewing them they dissapear!!! Then you hit Ctrl-L to find them and nothing!!! ARRRRGGGGGGG!!!! it pisses me off!!!

that's the reason I build sets as a crate instead, that preview section is worthless.

is not worthless, I like it for quick requests and things like that. If I think of something I throw it in there. I guess I just figured out that you can very easily hit REVIEW and pick the track again. It will be the first one shown so I guess thats the solution to my problem... :)

But still there should be something done about that.

Good tip, im gonna try that tomorow

CTRL+Z (COMMAND+Z on Macintosh) still doesn't change track status to not played on 1.6.3

Is it so hard to fix?

DeezNotes´ suggestion is still my fav (see his first post above).

CTRL+Z would be fine, too.

bump for 1.8

this would be nice as i tend to completely overlook the green tracks

Me too. And its really getting on my nerves now. I try to remember to drop a track in the prepare window if I listen to it and it turns green but I don't play at that moment. Many times I will want to play it but later and the green really throws me off, so the prepare window helps.

Right now this is one of my first request for improvement.

Keep up the great work, Rane.

Yes! As I have added new tracks (far faster than I used to with vinyl, $$$) I need to pre-listen A LOT. Also the names aren't yet familiar so it's hard to remember what I actually played when I look it over. Seriously BUMP.

I like the if it plays for 45 seconds then it should turn green idea.

or better yet, start off with 45 to a minute as default and then offer that parameter user configurability as an option

More like a preview mode for the track to be played. With this feature if added to the new version in the set up mode we can set a time period we want the track to be previewed before the track itself turns green I think this should be helpful because many times I load track preview it say to myself no not this one let me try another track and I would go back to the track at a later time and wonder if I did played that track or not. I can’t tell if I did or didn’t because that tracks played and previewed are all green.

At least, if ctrl-z would work, we would have a manual option to unmark the tracks... I can't understand why this takes so long!
I'm a unhappy with this; my library keeps growing and I haven't the right tools to manage it.
Why bother with video when you have a half working browser ?
I guess I should start considering other options less focused on scratch djs.

Defenitely allow for SINGLE TRACK "Green Removal". I NEED IT. Even if the review time feature is implemented, allow us to reset one single track as needed.

please. :)

DJ BIS, check this thread:
scratchlive.net

thanks.

I think if you play the whole track it should turn green and if you only play part of a track it should turn red. Then you can manualy unmark single tracks tracks.

interesting. One thing is for sure, there are several colors that could be used to indicate different track status...

Nah, dont make it too complicated.


There is maybe one song in a night which I play completely from the beginning to the end. So I dont think this is a good solution.

^^ i agree. Keep It Simple. User-defined # of seconds to turn white, or the other-deck-load-while-playing, with an option to un-mark a single song.

By the way- I hardly ever have a deck unloaded, so the time option would have to only count while the needle was down.

why not going like this:

load track 1 in a deck and using "eject button" - track 1 will stay white!

load track 1 and "overwrite" with the next new track 3 (while 2 was played on the other deck) will turn the first track 1 into green....

does it make sense to you?

I don't think I understand. It seems like my suggestion at the top will do this already?

DeezNotes´ suggestion is still my favourite because it all will work automatically.

loaded track turns green, only when a second drack is loaded.

you can load as many tracks as you want, trying as many as you want out, but they will stay white. the only way they will turn green is if another song is loaded into the other deck

right Deez?

sounds like it would be easy to implement (but I havnt a clue)

its a buffer set at 1.

like a list, each new item you can pencil in
erase and repencil
but as soon as you start on the next item the preceding one turns to ink for you



a single ungreen, would you really use it?

Wow. I tried to explain in hundreds of words, and you come up with a few words and everything is clear, AKIEM. :-/ I feel retarded.

lol

I should have laid down one of my long ass rants for you then

Nah, I gotcha, but I think the way you speak is simply not compatible with certain other individuals. ;)

oh, thats my accent

it`s a nice accent :-)

why stank you :)

As usual... AKIEM got it right (a lot simpler too). From the looks of it, it's on their "to do" list.

I second Akiem (bump)

Third that. Why would it count as a played track if it didn't make it to the mains? If "they" didn't hear it it dosen't count, nice thought. Only turns green if you load the next deck, it's so simple it's stupid.

posted by me in 2005:


sounds the same as DeezNotes's suggestion.
Hope it comes soon.

Yes I think several of us independently had the same idea at one point or another. This would work for me better than the X seconds rule.

It would be good to have.

Bump

Since I was busy in march, this is my March bumb, or have i been to busy to notice we already have this feature......

yeh i would like to see something like this. I would rather use review for playlist instead of having to retype.

there is an Un-Greening Feature in 1.7.2... check out the beta

Cool I just read this in the notes of 1.7.2 beta

Fixed undo track load (ctrl-z) behaviour to remove track from end of review list and revert played state to what it was before the track load (green/white). Additionally, pressing ctrl-z twice will reload the track.

This seems to be languishing a bit - this is my #1 request for future adds. Pleeeeaase!!

I mean the X seconds rule or the not-turn-green-if-the-other-deck-isn't-unloaded.

Thanks for the Ctrl-Z fix at least though!

Hey Guys,

I think the Ctrl-Z feature is fina and probably the best solution. The problem with the "turn green on other decks loads" suggestion is that auto play songs will never be loaded. Keep in mind that I truly beleive at some point in the very near future Serato will add smoe sort of mixing/cross fading to the auto play feature. This will be useful for the down times (beginning of the night) or just using Serato for a your own personal party at your house where reall DJing isn't needed. Whatever the need situation may be, the suggestion would not account for any Autoplay features what so ever. Let's face it, you have to remove the song from the playing deck anyway. Ctrl-Z takes the track out of the playing deck, turns it back to white, and removes it from the review window. It's actually a powerful little short cut. I think we just need to get in the habit of using it.

sorry for the misspellings above.

DeezNotes´ suggestions should still be a near SSL feature.

Ctrl-Z is only working for the last imported track. If I change my mind for upcoming songs twice or more then Ctrl-Z doesn`t work for more than one prelistened track.

BTW, I don`t really care if it might effect autoplay then.

cool idea

man you guys are trying to complicate the shit out of this. there just needs to be a 'history' crate. and the ONLY rule for this crate is that if you load a track and it plays for 30 seconds or more then it is automatically added to this crate.

as an added bonus a sub subcrates are made with a time/date name so your history is organized.

and of course the option to export this crate into html, csv (text/excel) or m3u must be available.

as far as tracks turning green, i think they should only turn green if you add them to 'prepare' and play the track for longer than 30 seconds.

I don't think this is the ultimate solution. Read what AKIEM wrote...

what about things like hot cuing? say i have an instrumental playing on deck a. i load an acapella with a cue point set in deck b and let a verse play. now i load a second acapella in deck b and let a verse play. finally i'm ready to switch up the track on deck a. according to AKIEM, only the second track i loaded in deck b will turn green.

I like AKIEM's idea but its seems to complicated for something as simple as 'pull the record up, play it, put the record back down in the crate'.

pretty much the same problem if you were to try out several records, they get put in the crate. oh yes 30 seconds, but say you pop on an acapella for less then 30, pop on just a scratch for a couple of seconds it wont get put in the crate

to me the crate is a whole other function

for me, tracks turn green to let me know what Ive played already (especially since its just text)

so yeah if you keep dropping short segments on the same deck it wont turn green, thats a trade off. But really, when you are doing that kind of work you have some better planning. When you are freestyling trying out various records to blend it sucks when they turn green if you hadnt actually played it yet

the tracks turn green so you dont load a record you already played, its not really about a list of what you played that session, different issue

I'm with you AKIEM. If I only play a few seconds of a song I still wouldn't want it to turn green... cause I really didn't "play" it.

ok well let's stay on the green issue.

maybe the threshold (30 seconds) can be adjustable?

What if I prelisten to a song more than 30 seconds or what so ever and then I decide not to play it?! I still don`t want the track turn green. So DeezNotes´suggestion from last year still makes the best sense to me, Akiem etc. .

I think it was originally Stuart's idea. At this point, I think it's safe to say we have 2 "new" suggestions of how tracks can turn green:

- Time-based threshold (possibly user-definable)

- The difficult (smart) way [the idea originally introduced by Stuart]

I think Stu's way is not difficult at all - if explained properly. Many have failed... (including me) but AKIEM once explained it in veeery simple words.

I also agree that it's not difficult, but some seem to think so...

I just wanted to narrow things down so we wouldn't keep going back and forth like these two: Watchwww.youtube.com

I'm happy with the current play it (green) ctrl-Z (clear's green) mechanism. I will occasionally forget to ctrl-Z unload but I'm happy with the current implementation.

I continue to believe the timer method could be troublesome. See my post above at www.scratchlive.net

I would rather have a right click function and/or a button on the gui to ungreen the individual tracks then a timer myself

I disagree with the status quo - sometimes I'll preview 10-20 songs in rapid sucession before actually queing it up. I can do this with one hand easily. Having to hit Ctrl-Z after each one slows me down by a factor of 4 or 5. At least give us an adjustable timer, that can be disabled for those who don't want it. I still think the load-the-other-deck logic is really elegant.

Yes!

Until playing Deck A isn`t unloaded I can prelisten to tracks in Deck B as many and as long as I want. Once Deck A is unloaded only the last prelisened and now playing track from Deck B turns green.

After that I can prelisten to tracks in Deck A as many and as long as I want. Once the playing track from Deck B gets unloaded or replaced only the last prelistened track from Deck A will turn green because this one is playing now. All other prelistend tracks I decided not to play remain white.

This would be a hand free feature without the need for pressing Ctrl-Z anymore.

this talk is all fine on dandy. will it (any method) get implemented? april 3, 2006 was a long time ago...

If Serato implement this, it has to be user-definable. Why code an arbitrary value into the program when it takes just a little more code on the front end to actually ask the user what he needs but no more code for the actual implementation.

I dont think even user defined is a good idea

I dont want even one second used waiting, or hurrying because of some timed control

"oh let me hurry and load something else before it turns green"

no sense to me

the load-the-other-deck logic gets my vote

the only issue with that is it you have Auto on (like in the beggingin of the night b4 peeps get there... or aty the end while the staff is cleaning up) that wont work... but they can also make it a rule inthat case that if the song plays ALL the way through even without the other deck being loaded... it turns green. ir it auto is on.. then the track turns green on any load.

Exaaaaaaactly.

disturbed you got the exact soultion right here, that should be the way serato handle this feature.
can you code? can you apply to work with the serato folks ... starting tomorrow?

no.. i cant code... not yet at least... plan on going back to collage and learning though once my wife is done.

i was hoping to see this in 1.8...

makes no sense for track to turn green immediately upon loading it...

we need to be able to set a time to when the track turns green (played for 20 seconds, etc)

Serato, will we see this soon? ever?

still hoping for dj disturbed's solution to be added in a futur version

tracks should neither turn green when prelistening while the interface is disconnected

I disagree. It is useful for me.

Daim, how do you "prelisten" to a track while DJing with Serato with a disconnected interface? If you mean the internal player in 1.8 before you start DJing and you wanna choose your first track then it would make sence that these prelistened tracks shouln`t turn green.

DeezNotes, I still vote for suggestion but why is it useful for you? If your suggestions gets added in an upcoming version you could still use your "load to the other deck" suggestion in the internal player - and then the tracks you have worked on or prelistened to will turn green (and remain green after connecting the interface).

DeezNotes, maybe I was wrong. I don`t have 1.8 installed right now. I am not really sure if there is Deck A & B in the internal player for an "load the other deck" option.

Wow, you dont even have 1.8 installed, dont know how it works but give an opinion ... about something you dont know.

You should try and know what youre talking in 1.8 about before commenting.

Typical nik39 again. "Right now" doesn`t mean I haven`t tried 1.8.

I just got a new hard drive and I haven`t installed everything yet.

It doesnt matter... "right now" or not.

Point is you are commenting on something which you havent tried out properly. That is the only explanation why you dont know whether we have deck a and B in the offline player. So... you talk about something you have no clue about.

whatever

when u prelisten while the interface is disconnected ur crowd won't hear the track.. and propably never will

As Deez said, I dont see a problem. It is quite helpful cause you know which tracks you have already "touched"/listened to during that session.

I don't understand the problem anyway... just press on review->clear to reset the list if you want to reset them before you play out. Whats the big deal?

I think Daim ment prelisening to tracks during a break when another DJ is spinning and then he doesn`t want to press review/clear because it`s still the same night and he doesn`t want to repeat a track from his first session. If prelistened tracks during his break with a disconnected interface turn green it wouldn`t really help im in his second session. There could be also added a feature to clear just the prelistened tracks from the internal player.

Yup

Tell you what... I'll give you a clear explanation:

Once 1.8 came out, I'd be on the train to work (30-60 min. ride) setting cue points. I'd pick a certain crate and do all the songs in that crate... on my way to work and on my way home. It was very helpful for me to see where I left off on the way home. That way, I didn't have to "guess" which songs in that crate I already set cue points for.

Last night I was hitting CTRL-Z to undo a song I had loaded (keep in mind I was using 1.7.1) but the track would still remain green!

I even went into the review pane to delete it, and even when you remove it from there, the song still remains week. I have to check on 1.7.4 and 1.8BETA, but I hope this was addressed!

If the track was previously played it can't be reset to white by undoing a later load.

But for the first time track load, they fixed (or gave us?) the ctrl-z-turns-back-to-white in 1.7.3 I think.

Yes.

we could just have a on/off

'load if only next deck' should solve it too, offline

Cool, that's what I thought.

I like the idea of the user-definable time limit... but the wait-until-other-deck-stops solution is definitely elegant, as someone said.

Also, though, I'd _really_ like a manual 'green' or 'un-green' key. Just like an email program (i.e. Outlook) where you can mark a message as 'read' or 'un-read' at any time. This really shouldn't be that hard to implement.

greater than 30 seconds

I think the scrobbling for Last.fm uses a proportion of the track time, which I think is 50%, rather than a set time, to determine if a song has been listened to. That might have some advantages over a set time in seconds...

I'd suggest a hybrid of GREEN if other deck is loaded while a tune plays OR user defined percentage is reached.

does anyone really want to be counting seconds while they spin?

i think the BEST solution is to just to have a button to hit to ungreen tracks individualy (other thenthe cmd-z combo... b/c sometimes you want to un-green a track that was NOT just loaded into a deck). This way if you want to ungreen a track to play later while listening to it in your phones you can.. but leave a track green that you DONT wanto to play later to remind yourself NOT to play it

same as counting seconds, I wouldnt be messing around with ungreening tracks while Im trying to play.

True.

unless you're playing in a dancehall sound, in which case there are probably at least two of you. That feature would be very useful in my genre.

I think what's being suggested here is an automated solution along with a manual solution. That makes sense.

I'd rather not RE-discuss time vs. percentages vs. deck loading theories. It's getting a little bit old.

just green the track played as soon as another one is on the other deck.

May be to turn the track back to ungreen if you EJECT the track ! Eject that track means that you don't want that track ...

good idea ;-)

well there are other uses for eject though, such as when you want to play real vinyl...

pretty good idea, but i personally don't EJECT a track,
i LOAD ANOTHER over it
i'm sure many people do this as well.

so, as is stated in my other/same thread, it would be best to choose a specific time elapsed on playing a track before it turns green, 0-30 seconds.

SIMPLE AS THAT...Everyone would be happy, as setting it to "0" would make it behave as it does now, turn green instantly upon loading...

not to compare programs as they're all different and serve different purposes,,, but PCDJ FX, does this, and it comes in VERY handy, as you can imagine.

I still think the timed solution will be annoying.
waiting or hurrying to cause or prevent an action.

99.98% of sets Ive ever seen, went from 1 to 2.
the 00.02% of sets Ive seen where a track played on 1, tracks switched on 2, where highly practiced routines. meaning who cares if they turn green?

AKIEM,

i don't think you understand, or perhaps i don't understand you

the whole point of this "track turning green" is to know what track(s) you've played throughout the night

and the whole point of the tracks turning green after a pre-set time is so that you know which tracks were played, NOT AUDITIONED.

no, I understand

let me ask you this, what time setting would you use for example?

i would use 15 to 20 seconds, probably 15

because that's plenty of time to audition a track(s) without having it turn green.

if i let it play for more than 15 seconds chances are that the song is going "live", and therefore i want it "marked"

the reason that the timed method keeps being mentioned is that it's simple an easy to implement.

alot of the other ideas are ingenious, but complicated.

without thinking about the other deck: if you load a track and it plays continuously for 15 seconds. then it should turn green because the assumption is after 15 seconds the track was not queued but actually played. if it was played for 13 seconds, or was stopped, or unloaded or another track was loaded it should not turn green.

this method can be implemented very easily with a few lines code and is tried and proven.

I guess the latter.



The auto method is not complicated.

Exactly, you say "chances are".

You might cue over 15 seconds then change your mind. No one ever comes to talk to you while you play? No malfunctions to attend, longer indecision moments, females, drinks, etc that cause you to leave the track you are cueing for more then 15 seconds? It happens to me all the time. I flip to another track at the last moment all the time. Or if your not on yet, you got two tracks cued, but then you change the second track you are going to play. All types of scenarios. And to make it worse, you know there is that little 15 second clock ticking while you are trying to cue. Me, I would be bothered by that enough to not even use it.

The point of the buffer method is that its not a mater of "usually I would want it to" or "chances are I would want" it to behave this way. The buffer method would behave the way you want it to all the time -literally.

As far as complication, I dont think it would be all that complicated, probably even less complicated. It is simply a buffer that pays attention to which deck the track was loaded on. Just a list where the second to the last turns green instead of the last(like now). Tracks only turn green when they are at the second to the last position and from the other deck. Just two points of logic. We already have a list, the review window. That sounds like allot less code to me.


Patronize me for a moment-
Go to the REVIEW window. Load up some tracks. Imagine that each track you add gets stamped with an 'R' or an 'L' depending on which deck you load it to. Now the very newest track you load will not turn green unless the track above it has the opposite R or L stamp. simple.

So you could load a whole string of tracks to the Right deck for example, but none of them turn green because each is marked R, and the track above it is marked R. But as soon as you load a track to the Left deck the track above it will turn green.

It would be a mater of marking tracks R or L, they dont have to actually show in the review panel, but that might actually be useful information to have too. There is some mechanism to tell the program what deck to load to, right or left, it seams like that would be easy to have it write to the tracks in the review list. From there it is simple, basic logic.

Or it wouldnt even have to attach to the track in the review window. Check the logic

R g (track turned green cuz the next is on the Left while this is on the Right)
L g
R g
L (track did not turn green cuz next is on the Left while this is Left)
L
L
L
L g
R
R g
L
L
R g



I dont know much about programing but, as easy as it sounds to add a variable count down timer, I bet this would be even more easy to implement. It actually wouldnt even have to attach L or R to the track in the review window just pay attention to a track being loaded to the opposite deck. It could just sit there with a variable L or R, depending on which deck the last track was loaded to. And remember what deck the last track was loaded to. If they are not equal, then turn green.

Let x=(L or R) of second to last track loaded (the one playing)
Let y=(L or R) of last track loaded (the one cueing)
If x≠y then turn second to last track green

there I did it in three lines of code :)

See what I mean by it does not actually have to write L,R to the track? It just has to keep track of when it flips between L and R. Theres a couple other very simple logic solutions that would work the same. For example it could say:
-If you load a track into the same deck that you did last time, do nothing.
-If you load a track into the other deck then turn the track of the already playing deck green.
Whatever would work best with the architecture.





I think the reason that the timed clock suggestion keeps coming up is that it is the first and natural solution anyone comes up with. It was my first thought. And the buffer solution is harder to understand. But sometimes harder to understand solutions are actually less complicated. Sometimes they just have to be distilled down to the essence.



So, the only situation that this does not solve the problem for is if, for example, you play a beat on one deck and go through loading several scratches on the other deck. But only a few DJs actually play this way. And of those few I bet that they are playing a well practiced set, not freestyling. And if you are freestyling, or putting together a set you will still have the review list to see what you played. Also if you are playing this style I bet that you would still have problems with the clock timed solution, just like everyone else, somehow, someway.

The way I see it, the Buffer Method would work all the time for 99.8% of DJs
While 100% of DJs would fall victim to the clock eventually if not often.

+100000000000...

As a new Serato user, I'm surprised that this painfully annoying glitch in Serato is "low" on Serato's priority list for fixes, as you mentioned by Pene the Moderation. It's the ONE thing about Serato that affects me EVERYTIME I play and ruins a basic efficiency of the program.

I really hope a simple key command to "un-green" a prelistened track is implemented in 1.8, at the very least.

Eventually, a user definable 0-30second threshold would satisfy 99.9% of users, I believe.

nop, I second akiem's and many others idea of the "buffer method"

Currently, you can press CTRL-Z to undo the last track you loaded which turns it back to white.

I'm sure they're aware we want this. It's only a matter of time. AKIEM is the shit.

i like the un-green button method... that way if you ant to ungreen a track you select it..hit the one button and just ungreen that one track... no need to argue over how long the timer needs to be before the track turns green (b/c we all have diff opinions on that)... you dont want that track to be green... hit the buton... and boom.. that track is no longer green even if you DID play it already earlier in the night. B/c maybe you are trying to find a certain remix of a song in your lib. but you have several named that same (you know stupid shit like that alwasy seems to heppenwhenyou are looking for something) you listen to 3 other version of that song for 5 seconds a piece and they are not it.... but the 4th one if right... well in that case I would want the other version to stay green to let me know that they already were not the right ones... but a little while later im looking for a next songto play.. i listen to a few and i find one that i want to play later to then I just hit the ungreen button to keep it un-marked as played.

but that only works on a track that is currently loaded into a deck.... if you want to un-green a track that is not loaded into the deck you have to ungreen all the tracks right now.. and most of thetime I'm not messing with my keyboard at all (i use an external mouse to do all music searching and will be adding a midi controller once i get the funds to get a trigger finger.. but i use an external controller to trigger cue points and loops now)

Deez Notes suggestion would ungreen all prelistended (even more than 1) tracks automatically without the need for pressing any keys at all.

I meant prelistened tracks don`t turn even green at all :-) .

yes.... but what would would a "pre-listened" track be defined as? each one of us has out own pref on what should be the rule for the track turning green or not.. thats why i say just add a button so that we can tell the program to ungreen any track at any time. they can add the times way of telling or when a track is loaded into the other deck way..... but they also need to have a way to turn that off for those of us who dont want to use it. one thing i used to hate about TDJS2 (with fs2) was it checked every song loaded as played, but in TDJS3 they added an un-check button that allowed you to un-check individual songs (too bad i HATE the TDJS3 GUI). but that was one thing I was glad they added. (we use TDJS at the strip club b/c you realy dont do any real mixing there... you use your voice to mix)

193 posts later...tracks still turn green if you pre-listen.

:-)

lol 194

here's another idea to confuse the issue further... dunno if anyone else will agree but i'd find it useful to be able to set how long tracks stay green once you've played them.

i use green-ness to indicate something i might be likely to play... if i've not played a track for (say) two months it'd be more helpful to me for the track to revert back to being white; this kinda works both ways around, for helping ignore tracks that are slipping out of rotation, or indeed to help you avoid playing tracks to death: once it's gone white again you know you've given the track a rest and won't bore your audience with it if you play it again ;)

I've heard of another suggestion somewhere that was along the lines of a "Last Played" column. That might be more useful than just colors.

this annoys me too.
what about a button (where the itunes and colour option is) in the column.
you press the (preview) button just to the left of the track name.
the track would occupy the non playing deck (without waveform for speed) and give you options to then fully load the track, send to prepare or dump and preview another.
i'd like that

ha,
hey I was just thinking out your suggestion

See, I dont use itunes to preview. I load them into A or B and skip around on the vinyl. This is just my way. So yeah, I get the green bleed. I agree, a simple key command to change a green track to white would be totally expected and can avoid a lot of stress picking the next track.

How about this...once you delete the track from the review section SSL automatically turns the track white!

This still requires un-doing the green. The desire is to not have tracks turn green in the first place unless they have 1) been played for a certain time OR 2) other deck was loaded while playing.

bumping this!

Best option is an "undo selection" shortcut!

tracks should turn a different color then green thats pre listened to.( maybe red or blue ) whatever it is would be a good change.there alot of tracks we pre listen to ( edit make cue points ).i feel this would help better then not having a track change color at all.


anyone with me?

whats wrong with green?

Yea! This would be the $hit

because green is for previously played tracks.

Keep in mind red is for tracks that can't be found.

ah, you mean blue for auditioned tracks and green for played. that could work.

+ help illustrate, track turns blue on load, green when cut is loaded on the other deck

that would also help in the situation where you want to track cuts played on the same deck (they would at least be blue)

yes i agree !!

blue or something other then green.i know this would help me.and i hope it would help everyone.

also having info on how many times a track was played. ( with a reset button )
i feel both of these new suggestions would be huge if installed on further programs.

there alot of times i made cue points or edited a track with the box not plugged in and the track turned green ( and then during a gig im like i did not play that or did i ) lol!! ** too many shots **
but i do feel this would help ( even without drinking ) lol!!

211 - maybe some yellow, pink and strawberry blue. too? :-)

this discussion is about non-coloring pre-listened tracks

ok. menace lol!

why not have them turn blue?
you will know right away if it was pre listened to.i would like to know if i listened to it or edited before i listen to it.

whats wrong with pink or strawberry blue now. lol ;)

because pre-listened tracks should remain white

... and if you like to know if you have edited a song already you could use one of the 18 color icons for each edited track.

ok menace your way is the best way.im glad we came to a conclusion. lol!

eggshell

blue an cream

LOL

BIG BIG Bump for this!

Here's a repost of what I said in another thread:

I do not want to jump through hoops to avoid getting inaccurate information about what I've played. If Serato aren't going to make the tracking intelligent, at least give us a way to PERMANENTLY turn the damn thing off.

Ideally, what we really want is a system that gives us choices:

1. The current system.
2. Turn the system off completely.
3. Turn tracks green only after we've played the track for more than 30 seconds or so.
4. Turn the tracks green only when we change the track in the other player.

There's no reason why they can't have multiple systems and allow us to choose the one that's most appropriate for our style. Suffice to say, the current system doesn't work for me, or (judging by the content of this thread), a significant number of other DJs.

Oh, and for the record, I'm personally in favour of the 'mark the track in deck X as played only when I change the track in deck Y or I close the software' approach. That would work perfectly for me, but I appreciate that it's not a 'one size fits all' solution.

ditto ^ pleeeze

As an aside, the ONLY system that's potentially difficult/complex to implement is the timer based system. My preferred approach should be trivial to implement, so I really can't understand why it's taking so long for Serato to implement it. There's obviously demand for it.

This makes the most sense and seems to be easy enough. After all this time and this many people requesting this, why is there still no support. Seriously guys, give something. Start with this feature and see how it goes. This is a very much needed feature. I dont get the lack of support. Sure talk and say, but just do already...

My last post was in December. I really thought Id see some progress by now.

i agree.

load-the-other-deck logic is still my vote

Agreed!!

load-the-other-deck logic is also my vote

That's mine too, + last track played.

It is now May 2008 and I still want to see this feature implemented. Thanks. DJ Kase has spoken.

-If you load a track into the same deck that you did last time, do nothing.
-If you load a track into the other deck then turn the track of the already playing deck green.

Umm, it's actually June ;-)

DJ Kase is not perfect, especially in the middle of the night on an empty stomach lol

srsly guys please! FOR THE LOVE OF ALL THINGS HOLY PLEASE MAKE THIS HAPPEN! :-)

and yes I actually meant to SHOUT!

can someone from serato tell us whether they will ever implement this very popular, basic and much needed feature?

the way it works now does not make sense as everything you load turns green.

this seems to be one of THE MOST requested features

Agreed. For the love of [insert deity here] - please sort this out. It's driving some of us insane.

i think it's driving MOST of us nuts, not some of us...

Akiem has gone insane.

I have a massively awesome idea.

Use more than just green and not-green. Add red, yellow, blue, orange, etc etc.

The longer the song has been played for, the redder the color gets.

If you have loaded a song to a deck = blue
If you have played that song for 10 seconds or more = green
If you have played it for 30 seconds or more = yellow
If you played it for 1 minutes = orange
If you played it for 2 minutes or more = red.

Sounds massively complicated, plus you end up with an evil rainbow lollipop in your crates aka tracks turning red, blue, orange, yellow etc.

I am not a huge fan of this.

IMO... In the order of importance:

1) Bugs which affect the stability of the program
2) Bugs which affect the functionality of the program
3) Features which eliminate repetitive tasks
4) Features which extend functionality
5) Features that make you feel all gooey inside

This falls under category 4 to me. I'd rather they fix the 1.8.1 scroll crash first. I'd also want a better library management system integrated into the software a little more than how tracks turn green, but I think some of us use "the green" in different ways. I have found a solution where this doesn't bother me as much as it did before.

Well said Deez.
I'd be happy to have a better algorithm for the review list. But having a rock-solid Serato os far more important.
And while many suggestions in this section are individually interesting, if everything was implemented, we'd need 24" HD to fit them all ^^

Whats your solution Deez?

For me, there is little and possibly contradictory information gained from a green track. I believe it is meant to say "this track has been played". But instead it says, "this track was played, or was tried but didnt fit come back to it, or it was tried but will never fit tonight dont bother". What gets lost and becomes a memory game is trying to remember which song to come back to. I will never develop the 'ungreen' method, because it is counter intuitive and, takes too much time.

Deez, I agree with your hierarchy. But I think that you can weight tasks like that, but you can work on more then one item at a time. Otherwise you could always be stuck in just the higher level. Also I think you can give different wieght to task depending on, was it said to be in the works, vs never going to happen? Is there lots of requests for it vs none? Is it easy to implement vs impossible. Will it benefit many vs a few? etc.

I'd argue that this could be be category 3 - if you don't want a track to change colour when you load it, you have to manually unload it, hence a repetitive task.

If you're prepared to stretch the definition of a bug to include defects in the design, as well as the implementation, you could even argue that this should be category two. I'd not go quite that far, but as AKIEM just said, this is a feature that gives us contradictory information, and is therefore considered by many of us to be fundamentally broken.

I've said it before and I'll say it again. If I had a way to turn the bloody thing off altogether, I'd have done it by now. I'd rather have no information about what I've played than incorrect information.

I agree. I just didn't want to go there.


My solution won't work for everyone. It's not a full-proof solution to the issue either. Last but not least, to properly define a solution you must properly identify your problem. Multiple people have multiple "problems" with tracks turning green.

I think the most common is that if a song is auditioned, but not played they don't want it to appear green. The CTRL-Z method is a work-around, but not a final solution. Some people keep their tracks green (forever) to identify what they have played.

For me, I deal with what I have identified as the common issue. I also like to review what I have played for later (I save almost every set to a new crate... the good ones at least). The review list/green tracks have tracks which I did not play.

In the long run what works for me is a combination of CTRL-Z, the prepare crate (for tracks I didn't play but want to) and are already green, and setting colors to tracks after they have been reviewed. Today, A LOT of my common tracks have colors associated with them which is a huge change from my first post in this thread. This identify common (or stale) tracks I play all the time (fixing the "keep it green" issue). As for the primary issue, it in no way resolves the problem. It is merely a way I unconsciously work around it with the tools provided.

It would still be nice to UN-green particular tracks (possibly by deleting from the review list) as well as add logic to the greening process as stated above.


I see your point, but this can be argued in many different ways. As an additional example, adjusting my columns for all my crates is probably the most repetitive task I perform using this software.

thanks for illustrating

another voice says yes to this suggestion : )

Maybe just use yellow orange red.

Yellow if it has been loaded at all.
Orange if it has been played for 30 seconds or more.
Red if it has been played for a minute or more.

interesting
although Im not sure I would care about how long a track was played, and I dont think I would like so many colors.

what if:
on load - turns yellow, or light green.
if played - turns dark green
(of course played means it is loaded while another track is auditioned)

Multiple colours really wouldn't work for me. I'm not so much interested in what I've loaded, or even what I've played so much as what I've NOT played.

DJ MouseAT, Im trying to fallow your point, but Im not sure what you are saying. Isnt knowing what you have not loaded + knowing what you loaded but have not played exactly the same as knowing what you have NOT played?

There are only three states (unless you get into flagging and other mess) that a track can be classified as:

-unplayed
-auditioned
-played

If you know what the true state of any two of these are, you also know the third state. The problem we have now is that there is no difference between 'played' and 'auditioned', they both turn green. The only remedy being cntl+z to ungreen a track manually, which is a great hassle for people to consistently remember to do or for people who dont touch the keyboard.

At first I didnt like the idea of more then one color, but thinking about it some more, I like white + two colors. I think a light green (auditioned) and a dark green (played) would be perfect. It wouldnt be too crazy of a rainbow effect, but still give you a difference between auditioned and played.

See, that's the thing that would annoy me. A good implementation of what we had now would have the played tunes turn green, and the unplayed remain white. That's nice and simple, if I've not played it yet, it's white and I can easily ignore any tunes that aren't white.

Once you start having multiple colours, it's suddenly not as simple. You're having to look at both white and (whatever colour auditioned tracks are) and disregarding the green ones. Yes, it's possible, but I think it'll harm the readability of the list a bit. It's no longer that simple two colour split that makes things so clear in the first place.

Multiple colours may work for some people, but I doubt it'll work for me.

but i dont want the tracks that i audition to turn green instantaneously

cuz then i dont know if i've auditioned them or actually played them (live)

hence, a turn green after x seconds

plain and simple

Pardon?

all these posts and this shit still isn't implemented. give me the source, i can do it in less than 10 minutes.

I say Serato hire DJ Nyce imemdiately so we can have this "Nice" feature....

nik39,

which word didn't you understand?
plain? or simple?

i79.photobucket.com

-Load a track in A it turns light green.
-Load another track in A it light green.
-Load a track in B it turns green, and the track in A turns dark green.

This means, If you are cuing a record it will turn light green, but if you play in it will turn dark green. This give you all the information you need. Have you played a track, only cued it, or never loaded it. I think those are the only three conditions a track can be in when it comes to leading (unless you get into play count)

or green and blue, or whatever colors

I'm all for the 'UNLOAD LAST TRACK' suggestion turning the track black again.

or

Deleting track from review section turning it black again... both very simple solutions...

int the first one already the way it works?

nether one of those solutions address the problems I have. I hardly use the keyboard, and I load tracks then switch and play something else ALL the time. There is no way I could be bothered with remembering to unload every single track I choose not to play.

What do you mean?

akiem, that wont work...what differentiated whether you play or cue, audition it?
you need to have a set time, for this, loading to one player, loading to another, etc, tells you nothing about if the track was played live,

Sure it will, you should read the whole thread. It will work most of the time. Fallow the logic.

-your action - SSL action


-you have no tracks loaded - all white

-load a track in deck A - track turns light green

-load a track in deck A - second track turns light green
(so far normal)

-load a track in deck B - track in deck B turns light green, track in deck A turns dark green
(this assumes that you are playing A, and cuing B)

-load a track in deck A - track in deck A turns light green, track in deck B turns dark green
(this assumes that you are playing B, and cuing A)

-and so on


yes, it is true that SSL can not track your x-fader, and even if it could wouldnt know which track you are playing. But this is the assumption: If you load a track in one deck, you are playing the track in the other deck.

no, it will not work 100% of the time. If you do things like load the acapella then the vocal on the same deck, or run a routine with the same track on one deck. But I would estimate that 97.92% of DJs dont perform such routines. DJs who do such routines probably have well practiced routines (meaning tracking play isnt so important), and these DJs also play less practiced routines where this method would be practical. So this should work for most DJs all the time, and a lot of the time for the other small percentage. When it doesnt work, its probably not important in the first place for these DJs.

On the other hand the 'x seconds' will fail approx. 97.21% DJs at some point per set. Even when you have set the X to your optimal time, invariably you will encounter situations where it does not work.

Deciding to change tracks at the last second will have them marked wrong. Or playing a simple several bar quick transition (which incidentally will probably catch the same DJs who quick play tracks on the same deck anyway)

I think it would drive some DJs crazy knowing there is a timed action that start counting down each and every time they load a track.

Lastly, I would assume that writing the code for the 'x seconds method' would be a whole lot harder to do then the 'second deck method' which is really a very simple piece of logic.

Akiem,

no offense but this is ASSUMING you're playing the track,

i alternate many times between A&B, as i'm sure many SSL users do.

just because i load A, load A, then load B, DOES NOT mean my A is playing,

i may be auditioning with both SSL decks, as i do say if i'm spinning off CD's, or off my second computer...

so turn green after "45 seconds" is "almost" guaranteed that you're playing the track live...

no offense taken,


but, the timed method is also an assumption. In fact it is an assumption 100% of the time. It assumes the X is the correct amount of time. On the other hand the A/B method is a CORRECT assumption most of the time.

so you have to compare assumptions, which is going to be correct for more DJs most of the time? Which is more likely to be wrong all the time?



Yes it absolutely does unless nothing is playing, or a third deck.

If you are loading on B, then A must be playing. A will get marked.

If you do a sequence of loading and playing on deck B, then A is still playing. The only thing that wont get marked is all but the last track on B.



right, I dont see how or why SSL should take into account what you do outside the system. But mostly, wouldnt that further increase the inaccuracy of the x time? If you are playing from another source then it would be sure to have reached the threshold marking both tracks as 'played' even though they are both only being cued. So in both cases you are likely to have the same problem, unplayed tracks being marked as played.

ether way, if you are using a third deck, that third deck is not getting counted in the playlist.



So if you set it to "50 seconds" would you be more or less "almost" guaranteed to be playing it?

You realize that if you set it for "45 seconds" you are locked into unloading that track before 45 seconds or it gets marked wrong. If you played 25 seconds of you CD, then 25 seconds of deck A, you cant change deck B without having it marked wrong. But the exact same scenario would play out fine as long as you play in the right order.

ether way, there is no way for SSL to know what you are actually playing. It is an assumption in both cases.

the question is, what will work most often for most DJs?

All DJs will potentially have wrongly marked tracks with X Time, while many if not most will have 100% accuracy with the A/B Method.

There is a great larger margin for error with the X Time Method, there is the potential for every single track loaded to be marked incorrectly no matter the sequence. While the potential for error is 0, if the A/B sequence is maintained, which is the way probably 90% plus of DJs play 99% of the time.

And even you dont always play A/B, because you play a third deck, you are guaranteed to not be marking every track you play, so thats an issue that you are already dealing with and cant be solved.

And if you are doing quick switching on a single deck it is highly likely that you are working from a set routine and dont really need to go back and see what you played, you know. If you dont, its not that hard to figure it out bassed on how it would be marked.

And [whatever deity] help you if you are doing both a third deck, and quick switching on the same deck, the X Time will really screw you.

In the end, Im 99.87% sure that the A/B method will work perfectly for most DJs, and even be less of a problem when it is a problem for some DJs.

Add that to how simple it would be to write.


Also, there would be a solution for going from a third deck into A or B. Im assuming that you want to have the option of deck A or B next. In this case, load your two potential next tracks in A then B. But if you want to play B instead of A then just ctrl+/ to reverse the decks, SSL could take this into account and mark correctly. All you would have to do is remember to start on deck A. And again for this situation you would 100% correctness.

And for quick switching on one deck you could do the same hit ctrl+/ twice, or we could add a 'mark played' button, if you really need to track those (which I suspect you wouldnt)

pwnd.

AKIEM, your logic is infallible. You are my hero.

Can I quote you on that? I need some more shit to say in discussion with my girlfriend.

arguments (discussions) don't matter. either method isn't implemented and absolutely no indication that is even being looked into.

I havnt noticed them saying too much about any suggestion recently. But I think that they do actually read every single post in this section. maybe contacting them directly would get the info that you want. Ive gotten information asking directly. otherwise, I just assume they see it and will get to it when they can, if they can or want to.

but yes, I would like to hear something on this. from my pov this could be one of the simplest but most worthwhile functions added. cost/ben looks good to me

then again, for all I know
this would require a complete rewrite and the general user giveth a kuf not

AKIEM, I follow your A/B logic
+1 on that one.

However, I think adding another color will clutter the display, and take my focus away from those white tracks... I can see why you'd want to see which tracks has been auditioned, but for me however, I'd like to keep it as simple as possible:

-you have no tracks loaded - all white

-load a track in deck A - track stays white
(..if not played earlier, and therefore already green.. )

-load a track in deck A - second track in deck A stays white
(so far normal)

-load a track in deck B - track in deck B stays white, track in deck A turns green
(this assumes that you are playing A, and cuing B)

-load a track in deck A - track in deck A stays white, track in deck B turns green
(this assumes that you are playing B, and cuing A)


If ever implemented they could make a switch for "advanced review" in setup>playback settings, so people can stick to the old method if they prefer it.

how about this idea,

i think it would be IDIOT proof

have an extra column, which you can quickly hide/show anytime,

where evertime you launch SSL, all tracks are set to 0:00

now load a track and play, it will track length of consective play, but will record longest played time,

so i start , play for 10 sec, then stop, then start play for 1 minute, it will record track as 1 minute played,

now i just goto my "length played" column and it tells me all tracks i've played, and the duration of the play,

NO ASSUMPTIONS HERE.... you know exactly what you played/cued.

I think this is too complicated and not necessary.

Plus... how would you know the order in which those tracks were played? Sort by playlength?

Nah, not a good idea at all.

sort by whatever column you want, so all cued, columns would be on top, or in alphabetical order, or artist order

i think it's quite simple to implement

i personally don't need to know the order i played them because every party is different,

and i would not want to play songs in same order as that way to predictable as a DJ, i like to mix it up on the fly as i feel fit.

i just need to know WHAT i played and what i cued (auditioned)

you could have a "order played" column if you wish

Not sure what that has to do with my question.



-1 on your whole idea.

Not MUSICLEE proof at all.

i just like the x consecutive seconds, turn green

other like A/B method

i just know that MANY want Serato to do something about this,
whichever method they see best fit,
maybe a "combo" of both methods put together ???

A/B method and only if "other" plays for at least 30 sec.

No.

I could be wrong, but I think we have 1 awesome solution and a 2nd not-as-awesome solution. It's good to express the want for said feature. That should get their attention. It's not a good idea to suggest things which would not work for all users and creates confusion within the thread.

For the fifty-leventh time... my vote is A/B logic with the ability to manually remove greens by deleting from the Review list.

at this point i don't care what method, just implement something, soon...

ORLY.

nik, you're funny, but looks aren't everything...

Exactly. That's why AKIEM's suggestion is the way to go, not some funky threshold multi color, multi column solution.

what do you mean "no assumptions"?

you still wouldnt know the difference between a track being played or cued

This is actually DeezNotes idea, I just reasoned it out to prove it was best, and make the thread long. With a long thread it cant be ignored/forgotten.

Right now Im doing a ritualistic incantation that will call spirits into being who will travel down to NZ and wisper into the ears of the developers "Tracks shouldnt turn green instead of just pre-listening"

If you guys are wondering about whats going on down there. It will stop when this feature reaches beta.


But yeah, at first I thought timed until I realized A/B was possible. A/B is something Serato would develop, X Time is something Stanton would develop. And Im sorry to say, this new Musiclee idea is something Microsoft would develop.

yes, I agree optional

but I still think that it may not be as bothersome as it sounds to give 'cue' a different shade from 'played'. absolutely a personal pref. but take a look at the sketch i79.photobucket.com

I find it very easy to focus on 'unloaded, loaded or played'. Especially with the logic of the cued being lighter and the played being darker.

I just think I would like that option and would get allot out of knowing the difference between loaded, unloaded and played. There is no other state that could be automatically determined.

Actually it was my idea.

I snatched it off from a different board ;))

j/k. Whoever. Whatever. It is the best+easiest way.

What really upsets/bothers me is the last time a Serato support staff posted here was Nov. 27, 2006. YES, 2006. This has been the biggest request in the past year. WHERE ARE THEY? Seriously, not a "working on it guys", or "it's coming soon fellas". Nothing. GET TO IT ALREADY SERATO PROPLE!!!

Their resources are probably tied up with that bullshit ITCH program.

Fuck ITCH.

and tied up with Video as Remix NY is here...

i guess we gots to wait

Don't worry guys, we are still here.... and this is on my personal list of improvements i'm campaigning for. Deciding exactly how we implement this is the challenge. Hold tight :)

+1 on the tracks not turning green if u don't play it
like only green after 30s seems ok to me

Yeah I had a look at your sketch, we agree more or less. However, I audtion a LOT of tracks when I play (I often change my mind in the last few seconds befor mixing in) so I would end up with a green rainbow there. Se example sketch farm4.static.flickr.com
I guess its just a matter of personal preference, so yes, optional would be good :D

well how about we use a piñada instead of a real horse for this one?

really lets just keep this thread growing

DJ Tom B. (Booty Shakers), what if you go over 30 seconds then decide not to play the record thats being cued? I do it all the time. Sure set it longer the 30, but what about if you only play four bars of a record? It wont be marked at all. Then you would want to set it to 5?

79.63% of DJs vary cuing times often enough per set to cause the X Time function to mark at least several files inaccurately every single set. Another 13.48% of DJ have very predictable cuing routines (these are mostly House DJs who play the same set all the time). That leaves 6.87% who this might work ok for because they play every song to the end and always fallow their playlist exactly. But even these guys can be persuaded by a fellatious chic to switch on some bullshit at the last second. (in the interest of PC, go ahead and change that last 'chic' to 'stud', it really is germane to the point and I guess stupid ether way) The point which is, that leaves only 0.02% of DJs who the X Time method will always work for. By no coincident at all, that 0.02% are the subject of a 'You DJ So Bad...' joke that goes thus:

You DJ So Bad that you dint even know that you are supposed to use both decks.

The point is that the X Time method will usually function incorrectly for lots of DJs, and will not always work well for the rest.


Presenting the A/B Method:
If you load a file, there is the presumption that you are only cuing, and it does not turn green. But the file in the opposite deck does turn green because it is presumed that the track in the other deck is in fact playing.

This method will work 100% of the time for a about 92.76% of DJs. When it does not work there are some simple methods for dealing with it, or adjusting procedures slightly so that it would work.

I'm too lazy to read the whole thread again ,) so I don't know if my idea is new.

A simple solution could be to make a distinction between tracks played on the left deck and tracks played on the right deck (color, L/R icon...).

What's your opinion?

my opinion = read the thread

Good, and we're too lazy to read your whole post.

check you guys all complaining over some trivial shit like this

spare a thought for this guy

www.blogger.co.kr

he can't see colour at all, has no idea which ones are green or whatever...

lol... now that you mention it, it does seem kind of trivial. I mean, my records NEVER turned green and I only played them each once per night. ;-)

+1

There ya go. It also needs a way to turn back to white, too, without doing ALL songs. If you queue 5 pitbull songs and only play 3 cause they match better, you might need the other 2 if the next Dj doesn't show! 2 hours = 60 hip hop songs for the A.D.D. generation. I don't like it either, but oh well :)

was that a dig at Sarah Palin?

This has been up here for so long that I've given up. I an getting used to pressing ctrl-Z when previewing but that's pretty tedious and not really useful for the way I play.

great.. 2,5 years.. 300 posts.. nothing happened

Is the general consensus the a/b method would work better than a timer method?
When I play, I sometimes cue songs up for more than a minute, but then change my mind at the last minute. Other times I might only play 40 seconds of a song...
I dont think the timer method would work great for me, but the a/b method definitely would.

+ 1 on the a/b method, works for me.
now, if there was a texfile export option from the review list ...

+1 on A/B method, sounds more practical than the timer method.

Yes.

+1 A/B

...and it needs to still work with the 'instant doubles - one table method'

The option to select this feature would also be a plus, instead of not giving us the choice to turn it off and on.

a/b for the win

A/B would be my favourite method, too - because I can`t tell in advance if I change my mind before or after a certain time or even seconds before the playing song ends and I also don`t wanna have a certain time limit in my head until I have to decide what I really play next.

So A/B rules.

A/B would work perfectly for me. If it's an optional feature with a way to turn it off, that should keep most people happy.

great. still talking about it...

wow... can't believe this thread started back in 2006 and it STILL hasn't been implemented into the software... gives me hope for other requests.

...patience grass hoppaz...

I think waiting since 2006 IS patience...

I honestly expected a big, new and improved version for Christmas. Still cant believe this. We even found the way for this to happen.

True... I didn't even realize its been that long. I'm getting old... lol

Nick M wrote:

An eject from deck button is my preferred method especially if serato goes to more than two decks (4deck mixing). Other than that if we are stuck with 2 decks for the rest of next year i'd prefer to see the deck A deck B example Akiem mentioed earlier in the thread, it's a greatidea.

The time method has too many variables imo

Nerds rejoice. This feature is finally here in the 1.9 beta
8)

how does the feature exactly work now in 1.9?
I just don't want to install a beta *g*

yes...

Watch this... Watchwww.youtube.com

thank you

HALLELUJAH or however it is spelled.

just when I was getting used to pressing ctrl z every time I had load a new track...


btw KONIX you are the MAN

that would reaallly help!

its soo annoyin just prelistening tracks and then turning green.

Yay! It was implemented, nice!!! Nice to see Serato is listening to it's users, kudos to Serato support :D