Try the following and see if this helps. And this is due to Acid Pro still being very unstable at the moment. After doing the following, it stopped the crashes in my case and rendering problems are gone.

Remove any Magix effects/Instruments (midi). Do not use Side-Chaining (this should resolve the rendering problem). If you must, use 3rd party plugins which are 64 bit only.

If you are using Melodyne within Acid, export your tuned track and import and turn off melodyne.

Nice, thank you! I saved the project to a new file, and turned off all plug-ins. No crashing, and I was able to render a complete output file. Honestly, I didn't think the culprit would be the plugins that came with the software. 😑That's super disappointing.

Thanks again!

Ya man, I found these solutions out after a lot of trial and error especially the side-chaining one. I found out the hard way and almost lost a client. Long frustrating story. But everything is OK now. I just mix the stems in either S1 or Protools so side-chaining and other things can be done. But because Magix was nice enough to reply to me and a major update is on it's way, I am happy and waiting. I need Acid Pro

If an export crashes, can you try to set the AUDIO DEVICE to "Microsoft SoundMapper" instead of ASIO?

If you want to help us to fix this export crash issue, please try if that workaround helps you and report your results here or directly to me.

We are kind of able to reproduce the export crashes by using many eFX plugins, but there seems to be a race condition - sometimes the export works, sometimes not. But they seem not to happen or at least much less often when using SoundMapper.

Any reports from you are welcome.

Hey Frank, was that for Peter or myself?

Hey Frank, was that for Peter or myself?

For both of you and anyone reading here, so for everyone who has crashes or issues with rendering his project to MP3 (or other formats, of course).

Sim cara, eu descobri essas soluções depois de muitas dos erros, especialmente o side-chaining. Descobri da maneira mais difícil e quase perdi um cliente. História longa e frustrante. Mas está tudo bem agora. Acabei de misturar conforme se apressa em S1 ou Protools para que o encadeamento lateral e outras coisas possam ser feitas. Mas porque Magix foi bom o suficiente para responder e uma grande atualização está um caminho, estou feliz e esperando. Eu preciso de ácido pro

The Side chain works in real time render bro.

If an export crashes, can you try to set the AUDIO DEVICE to "Microsoft SoundMapper" instead of ASIO?

If you want to help us to fix this export crash issue, please try if that workaround helps you and report your results here or directly to me.

We are kind of able to reproduce the export crashes by using many eFX plugins, but there seems to be a race condition - sometimes the export works, sometimes not. But they seem not to happen or at least much less often when using SoundMapper.

Any reports from you are welcome.

 

Stripping out the Magix plugins from the entire track did the trick. I've been slowly using them again one by one to figure out if it's a single culprit, or if it's a combination of them that are causing problems. I completed the first project, where I initially encountered this issue, and another after that without any other issues. I haven't had to try changing the Audio Device yet, I might horse around with that later.

I tested with all MAGIX fx plugins, and I found that the eFX_VocalStrip is very likely to crash quite soon. All other plugins work fine on my side for now. (I did only basic tests with the side chaining yet, but will investigate further in that area).

Hey Frank, was that for Peter or myself?

For both of you and anyone reading here, so for everyone who has crashes or issues with rendering his project to MP3 (or other formats, of course).

Frank, I appreciate you are allowing us to send you errors for further development. I have been pretty active here in the forums trying my best to help out others. All I want is the bug fixes, GUI jitters and MP3 support but it doesn't seem like its coming. Since you have been nice enough to message here, will you be able to tell us if there is light at the end of tunnel? Is there really an update coming anytime soon?

I tested with all MAGIX fx plugins, and I found that the eFX_VocalStrip is very likely to crash quite soon. All other plugins work fine on my side for now. (I did only basic tests with the side chaining yet, but will investigate further in that area).

Noted! And thanks for the active trouble-shooting. I opted to passively troubleshoot the issue, carefully choosing which Acid plug-ins to use as I went through my projects, so I would have gotten there eventually, but I'm super grateful you took the time to figure it out!

Frank, I appreciate you are allowing us to send you errors for further development. I have been pretty active here in the forums trying my best to help out there but I am personally losing motivation to continue with acid pro. All I wanted was the bug fixes, GUI jitters and MP3 support but it doesn't seem like its coming. Since you have been nice enough to message here, will you be able to tell us if there is light at the end of tunnel? Is there really an update coming anytime soon?

You and me both, Aman. I am getting back to making music after a 10+ year hiatus. I chose Acid because that's the DAW I used last time (version 4? 5?), and I wanted to flatten the learning curve as much as possible. This time it only took me 1 project to learn the bulk of the software, instead of 10. 😉

But I've been really disappointed by the instability of the software. Between the Crash-a-palooza you helped me with last week, and some really weird issues today (like my loops being corrupted into loud static, and my MIDI voices being reassigned between opening and closing the software - it sometimes takes hours to audition the right sound, just to have to do it again????) I'm starting to come down with a case of buyer's regret.

Hey Peter, I have been with that regret since version 8. Just a drop of faith and hope that if there will be an update, hopefully it will have something to offer. In the meantime, I just paid for Ableton 11 upgrade-coming next week. I have projects that need finishing. My workflow isn't the same anywhere else but what else can we do? Acid won't work.

Yeah, Ableton seems to be what all the grown-up music folk are using. I'm definitely gonna have to save my pennies for that. Good on ya, and I'd love to hear some of your tunes sometime!

Of course we want to improve the ACID stability, but we struggle to get reliable reproductions of any crashes - so I am afraid that it will take longer to fix the issues.

Especially, if you have found a way to make ACID crash each time when doing a certain thing, please let us know.

(But it seems there are some race conditions in the ACID engine, which are hard to nail down.)

Of course we want to improve the ACID stability, but we struggle to get reliable reproductions of any crashes - so I am afraid that it will take longer to fix the issues.

Especially, if you have found a way to make ACID crash each time when doing a certain thing, please let us know.

(But it seems there are some race conditions in the ACID engine, which are hard to nail down.)

But Frank, how would I send an error if there is no error to generate. I have already sent Mp3 problem error since 2018. I have had this issue since version 8. For some reason, it only happens on tower computers and not in laptops.

The GUI lag is not an error, it just start to get jittery and comes to a halt when zoomed in to do surgical editing. Try this with about 20-30 tracks in a 3 minute song, maybe you can re-create the same problem.

Thank you for joining the forums among us.

Ditch Acid Pro 10.429 go back to Acid Pro 10.2 or 10.3.? Roll back this fixes the mp3 problem and stability problem

Hey Looney, that won't work. I actually have the older versions. The weird thing is, I have been having MP3 problem since version 8 had come out. I had posted about that multiple times since then but stopped acid pro altogether for a year as I couldn't deal with that problem. Most of the vocalists that would send me their stems were Mp3s and I needed to work fast so I moved to Ableton. But I am back on Acid pro as I do better. My music sounds worse as I don't have the same workflow in ableton or S1.

I think a good course of action in this case is having a policy in place and letting the vocalists know that the only format you accept for Audio Material is WAV or AIFF. Nothing else. No MP3, OGG, AAC, WMA, whatever.

I probably wouldn't use a vocalist again if they sent me MP3 files. That is such a clueless thing to do.

There are multiple problems with MP3:

1. It uses Lossy Compression
2. It wastes CPU to use compressed audio files in your project.
3. DAWs may react differently to MP3 files that come from different Encoders. An MP3 that works fine in Cubase may cause issues in ACID Pro. An MP3 that works fine in ACID Pro may cause issues in Studio one. We see this with Compressed Video Files in NLEs, as well.

This is why people are told, routinely, to stop using Delivery CODECs for Acquisition.

If a vocalist is recording their own audio and sending you MP3 files, you should reject it and demand WAV or AIFF files. It is extremely unprofessional, and in some cases the audio quality is audiobly worse.

MP3 is something I'd take only when I'm using source material that cannot be gotten in any other format - the way News Channels will take an MP4 from someone's smartphone because no one else was there to get the footage...

But I'd still convert it to WAV before importing into my DAW, for the reasons stated above.

Many DAWs will offer to convert compressed Audio to WAV before import, or at least have a setting to do this. I feel like MAGIX should add such an option to ACID Pro.

@Former user Hear Hear ! 👍

I think a good course of action in this case is having a policy in place and letting the vocalists know that the only format you accept for Audio Material is WAV or AIFF. Nothing else. No MP3, OGG, AAC, WMA, whatever.

I probably wouldn't use a vocalist again if they sent me MP3 files. That is such a clueless thing to do.

There are multiple problems with MP3:

1. It uses Lossy Compression
2. It wastes CPU to use compressed audio files in your project.
3. DAWs may react differently to MP3 files that come from different Encoders. An MP3 that works fine in Cubase may cause issues in ACID Pro. An MP3 that works fine in ACID Pro may cause issues in Studio one. We see this with Compressed Video Files in NLEs, as well.

This is why people are told, routinely, to stop using Delivery CODECs for Acquisition.

If a vocalist is recording their own audio and sending you MP3 files, you should reject it and demand WAV or AIFF files. It is extremely unprofessional, and in some cases the audio quality is audiobly worse.

MP3 is something I'd take only when I'm using source material that cannot be gotten in any other format - the way News Channels will take an MP4 from someone's smartphone because no one else was there to get the footage...

But I'd still convert it to WAV before importing into my DAW, for the reasons stated above.

Many DAWs will offer to convert compressed Audio to WAV before import, or at least have a setting to do this. I feel like MAGIX should add such an option to ACID Pro.

Dude, have you ever worked with anyone? recorded anyone? Who asked what an MP3 does? seems like you just come in here to preach to the choir. Kind of getting sick of your stuff. My problem is that MP3 codec doesn't work in my copy of Acid. Anyway, You been here for months and I have noticed you tend to aggrevate users. do you actually ever have a proper solution to provide? just a bunch of redundant information on almost every post you have. Everything you wrote up there, its a widely known information. There is already a lack of people who come in here to provide useful information. Magix appears to careless. Then there are people like yourself who come in and post information which has been already discussed about and doesn't actually help the real issue. You sent me a long drawn out direct message explaining I should switch DAWs and to which I wrote back nicely. You have been warned by moderators, too. Unless you have a solution worked out, post here, or just keep it quiet. (I have blocked your content as I have not seen any usefulness from you to myself or to others).

@Former user Take a breath....from your past posts we understand you have a 'problem' with 'Trensharo' BUT everything he wrote in his last post was the absolute truth. MP3 is not a professional recording format and yes I have a studio where I record artists of all different styles of music. MP3 is for emailing a rough mix to a client and nothing more. If you want quality, record in wave (windows) or aiff (mac), render to wave or aiff. (your client may want a quality copy 😉) then you can convert a copy to mp3 later. All the backing tracks I do for clients are recorded and rendered at 48000, 24 bit , wave. Oh, and thanks for all the time you spend trying to help people here on this forum.

All the best, Cheers

? @Maxthechu, The problem here is that MP3 codec is broken in some users' case. What you and him are writing is unnecessary and doesn't help the issue. Unless you know how to fix this problem, please stop trolling. I come here looking for help just like anyone and when there are users who are just vomiting redundant preaching, doesn't help at all. AGAIN, the issue here is how to fix broken MP3 codec link in AP. No one asked the difference between an MP3 or Wave. Now, unless you have a solution to the MAIN problem, please stop trolling. Thats the issue I have with that other user. I had to shut him off due to his negativity. Never actually had a solution for anyone but rather antagonizing users with this comments. Seems like we have another one here. Please, reply only if you actually have a solution for me. Writing non-sense un-asked for information is wasting both of our time.