issues w/Cross / cdj 2000

[zacki1]

Hy there,
I'm experiencing a number of issues with my current version 3.2.1 of Cross.
My setup is
CDJ 2000 x 2 --> USB connected to MacBook 4.1 (core 2 duo 2.4 ghz, 4gb ram, 256 gb SSD)
DJM 900nxs

First issues:
My collection is as large as about 2500 tracks (most tracks bought from beatport, djshop, etc.)
Recently I am experiencing a complete freeze of Cross when I load certain tracks into the player. Cross then can only be forcefully quit and restarted, which is horrible if you are in a live set. I haven't changed/modified my music folders (structure is Alltracks/DATEOFPURCHASE/TRACK) since the beginnings, everything stayed the same, these tracks are also not missing or something else, they simply cause a complete overload (cpu 100%).
I've just tried this again and used the sample "put your hands up", if I delete and reimport everything works just fine, but I can't live with the fear that during my gigs certain tracks just crash my software.

Issue two:
To me this is the even bigger issue, bc. I am experiencing "lag" problems after a while. E.g. I am playing track A and want to load in a second track. Music stops playing for a short time and continues or stops continues and stops again, like you experience buffer issues in youtube or so . I have always cache audio in memory enabled, lead in lead out 21 seconds, read track gain at load enabled. This "lag" issues appears to happen more often when I have tracks that start at an in-track point, which I would be happy if someone could tell me how to generally disable this function (since I always want tracks to start right from the beginning).

I think the general question for me is if I should think about investing money into a new macbook, that would solve all these issues and enable me new features such as video etc..

Okay thats it for now, thanks to everyone who firstly reads and secondly is able and willing to help me!


Let me know if you need more information

florian.rtf

[RoJeC]

Someone recently mentioned similar behavior for the 850, whereas others have no issue at all.
Not likely your specs are causing it. Your collection is small.
Not sure if the devteam has figured all out yet as they do not seem to be able to duplicate it. The remark that when Cue is at start behaves different might be of interest.

Cross by design puts the Cue at the first beat of a beat cycle to fit smooth running and mixing. Other parameters to detect Cue point have been removed over time as they have other issues. (like beginning of sound, beginning of sound in first x seconds, sound above y dbA in first x seconds). Setting Cue to t=0 often is not the solution.

Are you running in HID mode?

[zacki1]

Hy Roland,

thx for your support,
Yes I am running HID advanced Mode, I've just tested standard mode, but Cross does not work in this mode at all.

I've now switched off Quantize on both CDJ's and changed MIDI Channels to 1 in both players.

Is there anything else I can do?

Btw. this issue seems to appear after a while running the software, not immediately when I start it.

[jwlanky]

I had a lag/pause/stop issue on my 850s, its been cured by doubling my ram from 4gb to 8gb.
Hope that helps.

[zacki1]

okay, thank you,

I wonder how this can affect Cross, since I allowed Cross to use maximum audio cache.
Since I am watching this issue very closely now, I found that only tracks that start at a random cue point (seems like Cross sometimes saved cue points where I stoped the song when last played) it appears.
Is there a possiblity to disable this function, I don't see any use in this function ?

[RoJeC]

Adding memory above 3.5gb is only useful when running 64bit OS. It might have worked, but then the adding is still more likely to have done something else than contributing to Cross solely.

Cross does not have a function to save last played position as Cue. There are 2 ways of setting Cue. One is the analyze, which does it once. The other is setting a manual Cue. To do this:
- stop track and press Cue (gui or MIDI), C-key.
- while play: SHIFT-C.

There are ways to MIDI map so the result will be as you mentioned. Please let's know if you're not using the functions as described and tell what you touch to stop when it happens (and maybe other circumstances) as I guess you use HID.

[zacki1]

@RoJeC, yes I believe a memory update does not help either, besides I don't understand the issues have to do with memory or cpu, ssd, since everything fulfills the requirements.
I indeed might set cues unintentionally and unwillingly.
By looking at it more in detail I found the following.
If you take a look at the attached picture you can see my two decks are loaded with tracks. In this case deck A plays from the beginning (it is a typical track running from the beginning to the end), but when I loaded in deck b with the MÖWE remix it starts at the very end. I remember setting a loop in my last performance as I played this track and then selected a new track by scrolling and pushing on my cdj.
The problem now is that while Cross is loading the track (orange line deck b) the music simply cuts off (1/2 second) and comes back again.
Even worse if I press cue on deck b's CDJ 2000 I increase the number of cut offs until the track eventually finishes loading the new track.


I have HID advanced enabled on my cdjs.

Is there a way to completely disable this feature and let every track start at the beginning, since I use hot keys with my cdj in order to jump to certain cues.

20140807_150817.jpg

[gullum]

Cross does indeed save where you last set cue and loads the song/track with the playhead at that position. So if you load a songs scroll into it (after 8 - 16 beats for better mixing or what ever reason) then press cue button, Cross will set a cue point/memorie point not an hot cue. and saves it in the data base. I happen to love that future so I can have 3 - 4 hot cues not related to where I want to start my songs.

But I do not notice any glitch maybe because I always load songs fully before playing them.

This is what happened to you second track last time you played (loaded it) you set a loop and pressed the cue button probable to hear how it mixed. therefore it loaded at that point

[RoJeC]

Audio glitch means the buffer of the soundcard cannot be filled in time. Every few ms the cpu fills it with the next few ms. Loading a track takes time . especially when files tske time to be released by hardware and high priority programs like anti virus. The orange bar is not so much loading as it is caching. The later the cue the more of the file needs to be processed. Which still points to a latency issue.

If you want to use locators or loops then do you use the Cross function for this. You can save upto 8 per track.

I don't think a no cue function will make into Cross. Not even as an option. Without a cue decent mixing will be hard. I find it pretty rare to have tracks starting at a usuable position that is exactly 0. Though these do exist..

[zacki1]

okay thanks everyone,

so I guess the only chance I have is to buy a new macbook since I otherwise need to reset cues during my mix. I am afraid that I forget to do this in front of a crowd and next time risk audio glitch.
It's just a little annoying since I updated memory and ssd only bc. of Cross.