have downloaded and installed it, but no way am I gonna test it out till others have done so ..... I have a sneaky suspicion that its gonna bugger up all my cues and beats .......
Post is closed for comments.
Sorry mate I should of said that's what I done with most of them. A lot of old tracks I wanted to clear out so had to search for them. Deleted around 25-30 last night using this method. Only in the collection though not in the playlists
Oh and thanks for the heads up on changing album info. I'll leave that for now and change in iTunes or something for now if needed.
Lol, thanks for the replies .... Guess I'll be sticking to 1.5.3 ;)
Strange how the first response was informing me how thus update had been 'in beta for some time and was very stable'
I don't know who's testing your beta releases, but you might want to hand the job over to some of the users on here who obviously have more of a clue than Pioneer.
Sorry mate I should of said that's what I done with most of them. A lot of old tracks I wanted to clear out so had to search for them. Deleted around 25-30 last night using this method. Only in the collection though not in the playlists
ok cool, so maybe its based on just fairly large libraries and specific characters, all I know is it happens on my 10.8 on 1.6.2 and never on 1.5.3
Ok.. I was a 1.5.4 victim.. installed 1.62 last night.. manually fixed all my beat grid issues that were left over.. improted/analyzed in batch for a few hours until I had confidence in new version - then sent rest of library to finish - only to wake up to "program quit unresponsive.." message over & over just like I had when I started with earlier version. I understand database is corrupted & I had a backup from a few mos ago to start from - but I've lost a days worth of work.. all the playlists & gig histories etc - What, my friends at pioneer, is the problem?
mine crashed too, I figured 1.6.2 seemed like a good fresh start after the beat fixes so i chose to re-analyzy my entire library, crashed 3 times before it finally finished, but at least it finished finally, If I was you I would just go back to 1.5.3 like most will do, 1.6 is buggy
Win7 32bit. I've just analysed 64000 tracks, had 3 crashes but this was possibly due to errors on some tracks. RB refuses to analyse 19 tracks which were analysed in 1.5.3. I deleted these without any problems. Tomorrow I'll be adding some new tracks to my collection so I'll find out then if the tags gets screwed up.
So I've imported about 500 new tracks without any problems. RB analysed them in what seemed a much quicker time than 1.5.3 and all the tags were in place. I updated the genre on the about 200 as a block without any issues. Another thing is that with 1.5.3 I had to unplug my drives before RB would start but with the new update it start with them plugged in in. Today I'm going to add my 2nd drives content which is about 40000 tracks so I'll see if it can handle a larger collection without presenting start up problems.
@ Gavin - Does no one ask questions regarding the performance of these beta testers when things are continuously missed as feedback suggests?
I had the same crashing issue last night in 1.6.2 on osx 10.7.4
I have under 2000 tracks in my collection, so can rule out large libraries being the cause. I upgraded to the leaked 1.6.1 and the delete bug was mentioned about it, so how did it make its way into 1.6.2 after being highlighted?
I love the hardware, but the software has a long way to go. We need to move on from the 1 step forward, 2 back with rekordbox. The least new releases should be are stable - Things need thoroughly tested before release. As in any walk of life, if people cant carry out the task assigned to them properly, surely its time to appoint other people who can... Surely pioneer need to protect their reputation?
Hey guys, 1.6.2 doesn't even launch for me, RekordBox logo loading comes up then instantly crashes. Never had a problem with 1.5.3 so i'm completely stumbled as to what could be causing this. When I first installed it, it worked perfectly, played for about 5hours no hitches. Trying again after that has been unsuccessful. Application log is relatively useless, doesn't seem to be any other events associated with it
@BeatLeSS > If you're having a problem with a crash, please follow this guide and read the instructions. If you still have problems, post a new thread with the info requested at the end. DO NOT POST CRASH OR ERROR LOGS UNLESS REQUESTED.
Given that we are now on 2.0.1, this thread is now closed. Please update as necessary and report any new issues to the rekordbox forum.