Have a feature request or suggestion? Post your idea here!

Publicación

6 seguidores Seguir
2
Avatar

[CLOSED] updated to Rekordbox 3.2.0 - crashed within 5 minutes

Like some others I've been having constant crashing since updating to Yosemite.

When I saw there was a Rekordbox update I had hoped the troubles may be at an end... but still the same as before. Whilst playing tracks in the preview pane, it lasted about 5-6 minutes before crapping itself.

 

The important functions of the software are still working, the bugs are a real nuisance though.

 

Any suggestions?

crash log available if required.

 

o/s: Yosemite 10.10.2

processor: 2.7 GHz Intel Core i7.

memory: 8 GB 1333 MHz DDR3.

graphics: Intel HD Graphics 3000 512 MB

 

Mike Barty

La publicación no admite más comentarios.

50 comentarios

0
Avatar

I've had one crash but it's been much more stable than the previous release. I'm on Yosemite also. 

I would be interested to know if you get the white flash flickering across your waveform? This happened on the previous version also but at a faster rate. I'll see if I can attach a video below. 

Richie Barthez 0 votos
Acciones de comentarios Permalink
0
Avatar

I've had that flickering before in the previous version but only occasionally. I've just updated so not everything will be apparent yet.

To be fair, other than what I've described above I'm not really having much trouble. But for it to still be happening after an update is a concern.

 

Overall the previewing of tracks in the top pane is a lot more laggy than when I was using previous versions of the Mac operating system, but I have a pretty quick machine. Serious teething problems with Yosemite

Mike Barty 0 votos
Acciones de comentarios Permalink
0
Avatar

I'm having the same lag issues. Rekordbox 3 is great in terms of features, but it has lost all of the stability from the previous releases.

p0ly 0 votos
Acciones de comentarios Permalink
0
Avatar

I have had no problems with Rekordbox 3. Updatet to 3.2.0 yesterday and got no problems. Link works perfect with CDJ-2000NXS.

Have you try to uninstall rekordbox and re install it? If you still got problems i think you have to do a clean install of Yosemite. My girlfriend had problems with adobe photoshop after installing Yosemite, but i did a clean install of Yosemite on here mac and all problems were fix. If you google: Yosemite problems, you can read tons of people having all kinds off problems and 80% off the problems are fixed after a clean install of Yosemite.

I think that your problem is more Yosemite then Pioneer.

AnyID 0 votos
Acciones de comentarios Permalink
0
Avatar

I'm on a fresh install. There must be problems with certain hardware if some people have no trouble. I'm on a early 2011 machine

Mike Barty 0 votos
Acciones de comentarios Permalink
0
Avatar

As others have mentioned in other threads it's after 5-10 mins of working in Rekordbox that it just crashes and closes down. The same has just happened again tonight. I have been using Yosemite since launch and all my other apps are perfectly stable. I'm using a late 2011 Macbook pro with 8GB RAM. Would love to know of a possible fix that we could apply manually. 

Richie Barthez 0 votos
Acciones de comentarios Permalink
0
Avatar

this is so annoying. rekordbox 3.2 crashes for me too, after every 5 minutes. even if i don't use it but it is running, it crashes. I also use Yosemite. please help us. 

Juj D 0 votos
Acciones de comentarios Permalink
0
Avatar

I'll try that on sunday and see how I get on, but with so many people with the same issue, suggests the root of the problem must still be the software somewhere down the line...

Mike Barty 0 votos
Acciones de comentarios Permalink
0
Avatar

I agree with Mike. My database is enormous and its not a risk I'm willing to take if the crashing is caused by a conflict between the OS and the software, 

Richie Barthez 0 votos
Acciones de comentarios Permalink
0
Avatar

might actually re-install Snow Leopard on a seperate partition I'm getting a bit irritated by the whole thing

Mike Barty 0 votos
Acciones de comentarios Permalink
0
Avatar

@Richie > You don't need to delete the database - simply renaming it will allow the software to create a new blank database from which you can import just a few tracks to ascertain if the problem is your database itself.

Pulse 0 votos
Acciones de comentarios Permalink
0
Avatar

Just an FYI, I know this doesn't help you guys 100% but i have been using Yosemite and 3.2.0 with a database of 33k songs and i have no crashing issues whatsoever so i am not sure how much this is an OS based issue. I could obviously be wrong though, But wanted Pioneer to know it was all yosemite users

BriChi 0 votos
Acciones de comentarios Permalink
0
Avatar

I'm running it on two different Macs and haven't had any issues with over 35k tracks... but I also know my tracks are good. ;)

Pulse 0 votos
Acciones de comentarios Permalink
0
Avatar

@BriChi @Pulse I'm glad to hear your databases work fine but what does your CPU hit when you are scrolling through a waveform trying to set cue points on single player mode? Mine is at 90% on my i7...

p0ly 0 votos
Acciones de comentarios Permalink
0
Avatar

Even if users have "bad files" this shouldn't lead to horrible resource management and application crashes.

p0ly 0 votos
Acciones de comentarios Permalink
0
Avatar

I realize Rekordbox is free software, but when you spend $5000 on a Pioneer mixer and CDJs, its hardly free. We all have a certain expectation for performance. Especially due to the fact that a cracked version of Traktor functions flawlessly compared to this proprietary 5+ year old software from the "industry standard" corporation in DJing.

p0ly 0 votos
Acciones de comentarios Permalink
0
Avatar

@p0ly > I don't blame you for expecting it to perform flawlessly - no DJ wants to face the awkward situation of having their music stop mid-gig through no fault of their own. But even a performance race car requires the right fuel in order to operate at its best. If you have an MP3 with errors, different players will produce different results. Some will skip, some will crash, others will play right through it. Because of the nature of the CDJs, they tend to dislike bad audio files more than say your car stereo. As for the resource use, it could simply be an incompatibility or conflict with some other resource or service in your computer which is causing it to peak as high as it does. Unfortunately, even if we took two identical computers (hardware-wise), with different software being added at different times, results could vary with testing. The software title may be 5 years old, but v3 was released with massive changes and improvements over the previous incarnation of the software. Anyone who's used it since day 1 will tell you the same thing - it's night and day over the original builds. But that doesn't mean it's still going to be free of quirks and bugs either. While the engineers work their hardest to test the software and ensure its performance and operation, there will always be some specific set of variables that cause problems, errors, or crashes. We're here to provide the support to track down those instances and hopefully the engineers can look at the situation and say "Ah yes, I see why that's happening" and then address it. Sometimes they can find them quickly, other times it takes a lot of hunting and then figuring out how to solve it without breaking something else.

Pioneer is doing their best to ensure that their customers are satisfied with the products they make and with your help in troubleshooting we can try and achieve that satisfaction.

Pulse 0 votos
Acciones de comentarios Permalink
0
Avatar

I dont understand how some one got problems and some one dont.
I use itunes and have all my music stord on the internal hard drive. I let itunes sort my music and use itunes bridge on rekordbox. I have no problems, my mac lat 2012 have not been switch off in 8 days whit rekordbox on. I have set the mac on sleep many times, turnd link funktion in rekordbox on and off many times, imported music, analyzed, added cue points and loops but no problems have happend me.
You people that have problems, wher is your music stored? Internal or external hard drive? Could it be a hard drive problem? Have you tryed formating your mac (like a bew mac)? After many years of us the mac can be full of shi.. apps and bugs. Am not an expert, just asking.

AnyID 0 votos
Acciones de comentarios Permalink
0
Avatar

@AnyID I have used each version of Rekordbox since launch on a Mac and it's only the last two versions that have crashed persistently - which is why I think it's a bug between Yosemite and V31/2. All my mp3's are purchased through legit stores etc. All my music is stored on my external drive too. 

 

Richie Barthez 0 votos
Acciones de comentarios Permalink
0
Avatar

I'm on a slightly older macbook pro (early 2011). Is there anyone who can say they are having problems on a mac from 2012 and newer?

are there issues on tower based macs or only laptops?

I'm using a internal SSD. is everyone with problems using SSD?

 

in order to find the problem we also need to be asking the right questions as a process of elimination

Mike Barty 0 votos
Acciones de comentarios Permalink
0
Avatar

just messing around quick, searching, scrolling loading tracks, setting cues, my CPU never went above 56%

I am using an SSD, all music on internal drive

BriChi 0 votos
Acciones de comentarios Permalink
0
Avatar

@BriChi Same here. No problems here.
@ Richie Barthez I have used every versions to, but stil got no problems. I had some problems when i used external hdd, i found out that the problems was the external hdd, i think that there was some kind of drop out in the USB connection. When i switch to internal ssd i got no problems!

AnyID 0 votos
Acciones de comentarios Permalink
0
Avatar

@BriChi I've just spent a few hours editing and making fixes in my library without a crash. Would love to know what's causing these issues. 

Richie Barthez 0 votos
Acciones de comentarios Permalink
0
Avatar

I run my music library from an external FW drive and never have problems.

Pulse 0 votos
Acciones de comentarios Permalink
0
Avatar

hello, I'm having the same issues and also happen when I updated to Yoseemite.
it doesn't happen frequently but it does, one thing for sure I'm getting is a lot glitches on the waveforms while playing tracks. horrible!!

QUESTION!

let's say I'm working on tracks either fixing them or added hot cues and suddenly Rekordbox crashes. The information I was working on it gets deleted because of the crash or not? in other words if I was adding hot cues to one track in the system crashes once I open it again that file won't have hot cues and I have to insert them again?

JuanCarlos Sanchez 0 votos
Acciones de comentarios Permalink
0
Avatar

@JuanCarolosSanchez I think this is the issue here, it happens sometimes when you least expect it - not when you are pushing your processor. 

Richie Barthez 0 votos
Acciones de comentarios Permalink
0
Avatar

Hey guys, as per another thread where this is being discussed... please try the following: 

Because of the "smart quotes" function of Mac, when a user changes the text 0 to 1, the double quotation text is changed so that the value can be read as 0 instead of 1 even after changing the value. 

  1. From the “Go” menu in the Finder of Mac, select "Go to Folder...". 
  2. In the popup window, please type in “~/Library/Application Support/Pioneer/rekordbox” to open the folder and find “rekordbox3.settings”. 
  3. Control-click or right-click “rekordbox3.settings” then select “Open with” -> “Other...” and use TextEdit to open the file. 
  4. Find the following line in the settings file. 
    <VALUE name="DisableOpenGL" val="0"/> 

Screen_Shot_2015-02-15_at_8.52.27_PM.png

  1. Then, change the value from “0” to “1” as shown below. 
    <VALUE name="DisableOpenGL" val="1"/> 
    Please note: Be sure to copy the text "1" including the quotation mark " " in for example, 
     <VALUE name="nexusServerIsActivated" val="1"/> in the TextEdit and paste them instead of directly typing the value 1.

Close the file and restart rekordbox. 

Please try this process to solve the crash problem. 

Pulse 0 votos
Acciones de comentarios Permalink
0
Avatar

Just changed this value change this morning. I will be doing quite a bit of work on my library today so it should be the perfect test. 

Richie Barthez 0 votos
Acciones de comentarios Permalink