|
Post by FriendlyBaron on Aug 27, 2016 21:32:34 GMT
How to make @giordanop never race my tracks again
|
|
zjoao
Member
Posts: 9
Registered on: August 2016
|
Post by zjoao on Aug 29, 2016 2:29:13 GMT
Sign me up pls
|
|
Hertz
Member
Winner of Chiliad-Sandy Triathlon
Posts: 580
Registered on: December 2015
|
Post by Hertz on Aug 29, 2016 4:07:48 GMT
You just have to be on teamspeak playlist waiting room at 1AM UTC (9PM EST/8PM CST/6PM PST.)
|
|
|
Post by the619soldier on Aug 29, 2016 6:06:20 GMT
I'm confused about this "Note that it's technically the next day at 1AM UTC, but it's still "the night of Tuesday" when you haven't gone to bed and it becomes 1AM UTC".
So does that mean the times are technically the next day from when they're listed? So "the night of Tuesday" would be early Wednesday morning, the night of Friday is really Saturday morning, etc?
|
|
|
Post by Sarah on Aug 29, 2016 9:48:25 GMT
Monday night playlist is 1 AM UTC tuesday, tuesday night playlist is 1 AM UTC wednesday and so forth. the619soldier
|
|
|
Post by FriendlyBaron on Aug 29, 2016 17:16:29 GMT
I'm confused about this "Note that it's technically the next day at 1AM UTC, but it's still "the night of Tuesday" when you haven't gone to bed and it becomes 1AM UTC". So does that mean the times are technically the next day from when they're listed? So "the night of Tuesday" would be early Wednesday morning, the night of Friday is really Saturday morning, etc? I see you are in New Zeland? I believe that means you are 12 hours ahead of UTC, so the playlist would be at 1pm Tuesday through Saturday for you.
|
|
nrainier
Member
Posts: 159
Registered on: March 2015
PSN ID: NRanier
Social Club: NRainier
Discord: NRainier #9046
|
Post by nrainier on Aug 30, 2016 20:44:59 GMT
Tuesday HYPE! No? No one? Ok R.I.P.
|
|
|
Post by FriendlyBaron on Aug 30, 2016 20:54:05 GMT
|
|
The_Bad_Loser
Member
Recent Status?
Posts: 1,044
Registered on: July 2014
|
Post by The_Bad_Loser on Aug 30, 2016 21:10:49 GMT
Not enough bbq.
|
|
|
Post by misssnuggles on Aug 31, 2016 5:37:25 GMT
Oh wow I won something. I'd just like to thank my PC for not stuttering and my puppies for all their support, except when they sit on the cords for my headset and controller.
|
|
|
Post by Skirakzalus on Aug 31, 2016 5:43:27 GMT
Is there a way to avoid the playlist bug that swaps the last track with the second to last one? I keep having trouble getting the lmao to stick to the end of the playlist.
|
|
|
Post by FriendlyBaron on Aug 31, 2016 5:51:40 GMT
Is there a way to avoid the playlist bug that swaps the last track with the second to last one? I keep having trouble getting the lmao to stick to the end of the playlist. I think I was saving the playlist first with default order, then go to edit it again and change orders to avoid that bug.
|
|
Prutoog
Member
If you no longer go for a gap that doesn't exist. You're no longer a nodo playlist driver!
Posts: 570
Registered on: June 2015
|
Post by Prutoog on Aug 31, 2016 6:04:58 GMT
As far as I can tell the bug is caused by adding tracks from different folders i.e. your jobs folder and bookmarked folder. I dont have the bug when I do it as follows: First I add my own tracks (in the order they should end up in pl). Then all the bookmarked jobs in alphabetical order (cause I can never go back to the first page unless I switch session or start a job in between). Then I move the bookmarked jobs around my own.
|
|
|
Post by Skirakzalus on Aug 31, 2016 7:14:55 GMT
FriendlyBaron Prutoog Tried both ways and several others, it always switches after saving it in the final order. And after several tries I came to the conclusion that it is either witchcraft or the playlist for some reason has something against that one track being the last one as soon as it has 10 jobs.
|
|
Prutoog
Member
If you no longer go for a gap that doesn't exist. You're no longer a nodo playlist driver!
Posts: 570
Registered on: June 2015
|
Post by Prutoog on Aug 31, 2016 7:23:57 GMT
yeah, its not an exact science. Some jobs may bring the bug with them or something. Try figuring out which jobs exactly causes it. If its one of yours. Try republishing it. Also did you keep trying from the same pl? Or did you delete the bugged pl and start from scratch?
|
|