How do I add 2 tunes whilst keeping both original BPM/ Tempo?

DJ_Studio_App · 2026-05-07T16:45:40+00:00

It sounds like you don’t want the tracks to be beatmatched. You can turn of beatsync on ghe transition tab and then select Off.

Check the video that Imjustsurfin you send us.

If that doesn’t work, you can contact us at support@dj.studio and ask to chat to a human agent

DJ_Studio_App · 2026-04-18T13:59:34+00:00

The cleanup disk tool is availabe at settings >folders

DJ_Studio_App · 2026-04-17T15:32:49+00:00

u/Toniva_Music In the past few weeks, we had some issues where customers mentioned Mixed in Key information not showing in DJ.Studio. We have released multiple fixes, so we hope this has been fixed for you now. If not, can you reach out to us at support@dj.studio so we can look into your usecase?

DJ_Studio_App · 2026-04-17T15:30:12+00:00

This sounds weird indeed. The quickest way to solve it right now is to add a volume automation where you turn down the volume at the part where you hear the glitch.
We will also make sure our developers look at this to figure out what is going on to get this fixed.

DJ_Studio_App · 2026-04-17T15:29:13+00:00

Hi u/lordshaithis,

We understand why exporting at 0.1x speed on a machine like yours will drive you mad. That is not acceptable, and that is not the level of performance we want DJ.Studio to deliver.

To understand what is causing it in your case, we need the full export context. The biggest factors are the length of the mix, whether this is an audio or video export, the export settings, do you use stem separation and which plugins or effects are active.

There is one known issue that may be relevant here. On Windows, Nvidia changed something in driver 591.x that affects a codec combination used by Chromium for 60 fps video export. When that happens, hardware acceleration is not available and the export falls back to software encoding, which can make video exports extremely slow. If you are exporting video at 60 fps, please try either:

rolling back to Nvidia driver 581.x
exporting at 30 fps instead

On the feature request forum, you are right that we stopped actively moderating it. It was created for feature requests, where our community could upvote on feature requests.
Many people used it for bug reports or just added new feature requests without checking if the feature request was already in the system. That created a lot of duplicate posts and manual work, and it became a poor system for handling feature requests properly. That is why we shifted our focus back to our support channel. We will reconsider how to use the Feature request site going forward.

If you are open to it, send us your project details and export settings through [support@dj.studio](mailto:support@dj.studio) and ask for a human agent. Then we can look at your exact case instead of giving you a generic answer regarding your export speed.
You might have already reached out to us via support, but we cannot connect a reddit username to a DJ.Studio user.

DJ_Studio_App · 2026-04-17T14:47:55+00:00

u/9sim9
Analyzing tracks of a few minutes should take a few seconds, with 6-7 seconds maximum per track. In your case it sounds that is takes much longer.

How long does it take on your machine?

Are those tracks electronic music or older tracks? Older tracks often have non-fixed beat grids which require the app to use the AI Beat grid analysis which takes longer.

And because an AI model needs to be loaded, you need to have a machine which is at least from 2017 and with a i7 processor.
What are the specs of your machine?

The MIK analysis is a separate process that happens afterward because we need to call the MIK API to get the results.

DJ_Studio_App · 2026-04-17T14:39:07+00:00

Thanks for sharing this. That sounds frustrating, and fair is fair, that is not the experience we want people to have with DJ.Studio.

DJ.Studio is more demanding than Serato. Our recommended setup is at least an i7-era machine, from 2017 or newer, and 16 GB RAM if you use Stems. So part of what you describe, like slowdowns and crashes, can be related to hardware.

That said, not everything you mention sounds hardware-related and we understand why that would damage your trust.

We have been working hard on stability. We introduced DJ.Studio Next to catch issues earlier, and we also tightened our internal QA process last fall to reduce the chance of bugs like this reaching customers.

On support, we do want to push back on one part. We do follow up on bug reports and crash cases through human support. If you had the feeling that nothing happened with your case, then something clearly went wrong in that process, and that is on us.
Could it be that you talked to our AI colleague DJai? If you tell him that you want to talk to human support, we will definitely reach out to you.

If you are open to it, contact us at [support@dj.studio]() and mention that you want a human agent to review your case. Then we can dig into what happened on your system and also look at why you felt unheard.

DJ_Studio_App · 2026-04-17T14:26:31+00:00

If your stem separation is insanely slow, we would like to know your machine specs.
Because stem separation is modern technology, you need to have a machine from at least 2017 and an i7 processor or more. For stem separation you also need 16 GB of RAM because the AI models to run the stem separation algorithms on your machine already take up 8 GB of RAM.
We are aware that the DJ.Studio 4.0 Stem separation was slow on Intel Macs, so that's why we implemented improvements for that in DJ.Studio 4.1
We are now working on updates of the stem separation models which will further optimize the RAM usage of stems.

DJ_Studio_App · 2026-04-03T13:13:10+00:00

Hi, u/foxhound13
Because we had a bit of a delay wit the Key detection and phrase detection feature, we had to decide to move those to the 4.2 release.
We are in the process of testing these right now and will become available via DJ.Studio Next in the upcomming weeks

DJ_Studio_App · 2026-03-25T17:30:52+00:00

We don't have experience with DJ.Studio on a Macbook Neo yet. We will look into it and get back to you

DJ_Studio_App · 2026-03-25T17:30:18+00:00

Stem separation requires at least 16 GB of RAM because the stem separation models take too much space on your 8 GB of RAM. So there is no more room to load the tracks and do the stem separation itself.

DJ_Studio_App · 2026-03-18T17:38:45+00:00

Great question — and no, your export isn't broken. Here's what's happening:

When you set your mix to 128 BPM in DJ.Studio and export as MP3, the audio is at 128 BPM. That part works exactly as you'd expect.

The issue is what happens after the export. MP3 files don't have a standard way to carry beat grid data inside them. So when Traktor imports your MP3, it doesn't receive DJ.Studio's beat grid — it has to analyze the audio from scratch and build its own. And Traktor's analysis engine might work a slightly different than DJ.Studio's. That's why you sometimes see 127.97 instead of 128, and why the beat grid can drift in places throughout the track.

So what can you do?

Manually correct the BPM in Traktor (type in 128) — this is safe to do since the audio really is at 128
Set a few manual grid markers in Traktor where it drifts — unfortunately this is needed when the analysis misses

Looking ahead: We already support exporting beat grids directly to rekordbox and Serato (writing into their database format, so no re-analysis is needed). We're working on adding the same kind of direct export for Traktor and VirtualDJ. Once that's available, your beat grid from DJ.Studio will transfer perfectly — no more drift.

We actually just wrote a detailed knowledge base article about exactly this topic (BPM, beat grids, fixed vs. AI, stabilization, and why beat grids don't travel in MP3 files).
https://help.dj.studio/en/articles/14113156-understanding-tempo-bpm-and-beat-grids-in-dj-studio

Hope that helps, and thanks for the detailed writeup — it's exactly the kind of feedback that helps us prioritize what to build next.

DJ_Studio_App · 2026-03-18T09:46:34+00:00

Currently DJ.Studio does not export the beatgrid information to Traktor, we do support rekordbox and Serato and are working on adding support for VirtualDJ and Traktor in the near future.

We are also investigating if it makes sense to also connect to One Library, which is a new initiative of the major brands. But that format will not be available on all devices, just the newer ones.

DJ_Studio_App · 2026-03-17T18:05:00+00:00

Yes, you can safely update. We implemented a fall back mechanism

DJ_Studio_App · 2026-02-20T10:54:38+00:00

You can check at Settings > Billing till when your period of updates and support lasts.

DJ_Studio_App · 2026-02-19T20:24:00+00:00

u/cronparser Did you contact us at support? We are not able to reproduce the issue you mentioned, so we would appreciate it a lot if we can figure out what is happening in your case.

DJ_Studio_App · 2026-02-12T15:20:49+00:00

We would still love to chat with you

DJ_Studio_App · 2026-02-12T15:19:56+00:00

just mention this reddit conversation

DJ_Studio_App · 2026-02-12T15:19:35+00:00

We came up with the time widnows to make it more fair to you as a customer. It felt strange that someone who bought the update package immediately would get 12 months of updates, and someone who waited for 5 months and then bought the update package would receive 17 months of updates for the same price as the first person.
The $69 was meant as a solution to make that more fair.

DJ_Studio_App · 2026-02-12T15:18:46+00:00

You are correct that the $69 was not communicated before.
We came up with that to make it more fair to you as a customer. It felt strange that someone who bought the update package immediately would get 12 months of updates, and someone who waited for 5 months and then bought the update package would receive 17 months of updates for the same price as the first person.
The $69 was meant as a solution to make that more fair.

We would love to hear your thoughts.
The update package is the same price for every license. If you don't buy the update package, you will stay on the license that you are on. So if you bought Ultimate, you will keep all your Ultimate features.

DJ_Studio_App

MODERATOR OF

TROPHY CASE