ACID Pro 10 hiccups

Tonic wrote on 11/22/2020, 5:23 AM

I've updated from fully working version 7 to this...thing. Reason for my update was only to have the 64-bit support. However, I have found out that this version is so buggy. Almost every time I open ACID it gives me error or errors. One is this:
 

Version 10.0.4 (Build 29) 64-bit

Exception 0xC0000005 (access violation) READ:0x0000000000000000 IP:0x0000000008AA3C1D

In Module 'sfvstwrap.dll' at Address 0x00000000088A0000 + 0x0000000000203C1D

Thread: GUI ID=0x16BC Stack=

 

or it can be this:

 

ACID Pro

Version 10.0.4 (Build 29) 64-bit

Exception 0xC0000005 (access violation) READ:0x0000000000000000 IP:0x0000000008A93C1D

In Module 'sfvstwrap.dll' at Address 0x0000000008890000 + 0x0000000000203C1D

Thread: GUI ID=0x1F1C Stack= 

 

Then VST scanning seems to have problems working, since it sends me errors almost every time I

open ACID. I have to keep opening and close ACID until it shuts up (read= works normally).
I find this very odd. My VST's are all legit and good to go, so what's the problem?

Then, lastly, since I've updated from version 7 to 10, I have not been able to render a stereo file

from 5.1 project. That makes no sense either. In version 7 everything worked fine.
So, since my update, I had to stop making 5.1 projects, since it won't render them to mp3, wave..etc.
Pretty useless. I would go back to version 7 in an isntant, if there was 64-bit support.

Can anyone help me with some of my problems with this program, please?
My PC is stacked with i5 7600k with 16gb ram, so it can handle the program.

 

Comments

Matthew-Thomas wrote on 11/22/2020, 9:20 AM

Yeah, there’s been a bunch of issues. One tip is to not just double click on the program icon and don’t launch it by opening your most recent project. Right click and run Acid as an administrator. That seems to make it crash less upon startup. Whole damn program is glitchy tho.

AmanSingh wrote on 11/22/2020, 10:27 AM

Yeah, there’s been a bunch of issues. One tip is to not just double click on the program icon and don’t launch it by opening your most recent project. Right click and run Acid as an administrator. That seems to make it crash less upon startup. Whole damn program is glitchy tho.

Agreed with matthew, I have faded the Ctrl+S keys on my keyboard as when it will crash, you never know. Sad thing is, Acid Pro's workflow, paint tool, explorer window, loop handling, the speed, its unmatched. No other DAW has been able to accomplish this. I have always come back to it for these reasons but you are right, its great when it works but is still very glitchy, crashy, clunky especially in MIDI realm. But I am sticking with it as this is the DAW I know like I know my own smell!

To possibly help the OP, in the error, you notice it says something about sfvstwrap, I am almost 100% certain that it has something to do with VST scan or a plugin that isn't agreeing with AcidPro. Might want to remove all 3rd party plugins from it's plugin explorer and see if the problem persists.

AmanSingh wrote on 11/22/2020, 10:29 AM

Here is a post from another user with similar problems, I had suggested the samething there as well. Try it: "..............Thanks so much for your help. I was able to trouble-shoot some of the plugins. And ultimately, I needed to Scan/Force rebuild the plugins, via the plugin manager. Now, Acid Pro seems to launch without error. I really appreciate your time!!!"

jocker-boy wrote on 11/24/2020, 10:39 AM

None of the options help to solve this problem.I have tried various ways, cleaning the registry with Ccleaner, disabling UAC, compatibility modes, DPI ... etc.With administrator mode also doesn't work properly, run from taskbar.Specialists have to work on this, otherwise nothing will help without a patch that will solve these problems.As I wrote earlier, Acid is unnecessarily cluttered with additional features like Morph Pads, Stem Marker , Melodyne plugin or many weak vst or vsti fx core plugins...The first thing programmers should do is to create a very stable and well written program kernel.Then focus on improving its basic functions.And all the vst, vsti, morph pad, stem maker etc it should be made available as an additional option and not "hot" integrated with the program.First the basics, stability, quality ... speed ... and then the cherries for the cake.The steel principle of success.

AmanSingh wrote on 11/24/2020, 5:00 PM

None of the options help to solve this problem.I have tried various ways, cleaning the registry with Ccleaner, disabling UAC, compatibility modes, DPI ... etc.With administrator mode also doesn't work properly, run from taskbar.Specialists have to work on this, otherwise nothing will help without a patch that will solve these problems.As I wrote earlier, Acid is unnecessarily cluttered with additional features like Morph Pads, Stem Marker , Melodyne plugin or many weak vst or vsti fx core plugins...The first thing programmers should do is to create a very stable and well written program kernel.Then focus on improving its basic functions.And all the vst, vsti, morph pad, stem maker etc it should be made available as an additional option and not "hot" integrated with the program.First the basics, stability, quality ... speed ... and then the cherries for the cake.The steel principle of success.

300% agreed with your comment! Yes, it is unnecessarily cluttered with useless features. I said the same exact thing when version 8 had come out. They should have just worked on version 7, fixed what was wrong. I knew it off of the bat when I saw the darkened GUI. It was as if the CEO handed the program to a non-musician intern and told him to do something "new" with it. Not realizing that it is a very serious DAW that needs "fixing", not a do-over. Anyway, about the bugs, i just read in another post that employees are under lock-down and may not be working on Acid as they should. So I am just dealing with the issues as I have completely switched back to Acid Pro so cannot really go back. The old me is back on it and it wouldn't make sense to switch all projects back to ableton.

Trensharo wrote on 11/25/2020, 3:02 AM

None of the options help to solve this problem.I have tried various ways, cleaning the registry with Ccleaner, disabling UAC, compatibility modes, DPI ... etc.With administrator mode also doesn't work properly, run from taskbar.Specialists have to work on this, otherwise nothing will help without a patch that will solve these problems.As I wrote earlier, Acid is unnecessarily cluttered with additional features like Morph Pads, Stem Marker , Melodyne plugin or many weak vst or vsti fx core plugins...The first thing programmers should do is to create a very stable and well written program kernel.Then focus on improving its basic functions.And all the vst, vsti, morph pad, stem maker etc it should be made available as an additional option and not "hot" integrated with the program.First the basics, stability, quality ... speed ... and then the cherries for the cake.The steel principle of success.

300% agreed with your comment! Yes, it is unnecessarily cluttered with useless features. I said the same exact thing when version 8 had come out. They should have just worked on version 7, fixed what was wrong. I knew it off of the bat when I saw the darkened GUI. It was as if the CEO handed the program to a non-musician intern and told him to do something "new" with it. Not realizing that it is a very serious DAW that needs "fixing", not a do-over. Anyway, about the bugs, i just read in another post that employees are under lock-down and may not be working on Acid as they should. So I am just dealing with the issues as I have completely switched back to Acid Pro so cannot really go back. The old me is back on it and it wouldn't make sense to switch all projects back to ableton.

Version 8 was that. Version 7 with 64 bit support. VST3 came very late and the scanner was garbage. Acid isn’t really filled with unnecessary features, though. It’s one of the more focused DAWs on the market. It just isn’t robust software.

AmanSingh wrote on 11/25/2020, 3:18 AM

None of the options help to solve this problem.I have tried various ways, cleaning the registry with Ccleaner, disabling UAC, compatibility modes, DPI ... etc.With administrator mode also doesn't work properly, run from taskbar.Specialists have to work on this, otherwise nothing will help without a patch that will solve these problems.As I wrote earlier, Acid is unnecessarily cluttered with additional features like Morph Pads, Stem Marker , Melodyne plugin or many weak vst or vsti fx core plugins...The first thing programmers should do is to create a very stable and well written program kernel.Then focus on improving its basic functions.And all the vst, vsti, morph pad, stem maker etc it should be made available as an additional option and not "hot" integrated with the program.First the basics, stability, quality ... speed ... and then the cherries for the cake.The steel principle of success.

300% agreed with your comment! Yes, it is unnecessarily cluttered with useless features. I said the same exact thing when version 8 had come out. They should have just worked on version 7, fixed what was wrong. I knew it off of the bat when I saw the darkened GUI. It was as if the CEO handed the program to a non-musician intern and told him to do something "new" with it. Not realizing that it is a very serious DAW that needs "fixing", not a do-over. Anyway, about the bugs, i just read in another post that employees are under lock-down and may not be working on Acid as they should. So I am just dealing with the issues as I have completely switched back to Acid Pro so cannot really go back. The old me is back on it and it wouldn't make sense to switch all projects back to ableton.

Version 8 was that. Version 7 with 64 bit support. VST3 came very late and the scanner was garbage. Acid isn’t really filled with unnecessary features, though. It’s one of the more focused DAWs on the market. It just isn’t robust software.

The weird thing is, version 7 was way more stable being 32bit on my system than 8. I couldn't complete a single song on it without it crashing plus the GUI was way too hard to work with, I could've dealt with crashes, but the dark screen killed it for me. I gave up, waited until 9 came, still various issues but I am back on 10 due to the light skin and at least able to stick with it. However, the morph pads, no, I dare not touch those as Acid crashes mid-segment. Melodyne hasn't worked to-date for me as its grayed out. I bought the Studio version and use it stand alone. Stem maker, the quality is so poor on the outcome that I am embarrased to remix a track. The GUI starts jittering when zoomed in to edit audio. So far, in my eyes, the only step-forward thing that has really changed from version 7, is the 32 to 64 bit format. That is about it. The rest, i think made Acid even more unstable. I believe that majority out there uses Acid as a quick writing pad. Most everyone uses a secondary DAW to create their music/loops and than compile them in Acid as the loop handling/pencil (paint) tool and quick explorer on the bottom is the key which no other DAW has. That is how I always did. So, trying to add VSTs and additional features isn't necessary as they really bring the house down, just fix the bugs for now. Oh well.

So, on to waiting for the next update. But I read in another post that Acid may not even be worked on at the moment due to Covid. I do my own troubleshooting and make it work & do my best to help others so they don't drive off to the competitor, I want Acid to stay this time for the companies to pick it up and "fix" it instead of giving it up like Sony did. I can't see myself working on another DAW as fast as I can on this. But I am glad that I am not the only one who is frustrated and continue to pay for this once great application.

Edit: PC specs: Win10, 32g Ram, 1tb SSD, 1660s nvidia graphics card and i7 10th gen CPU

jocker-boy wrote on 11/25/2020, 9:19 AM

A więc zrobić czekania na następną aktualizację. Ale przeczytałem w innym poście, że Acid może nawet nie być w tej chwili pracowany z powodu Covid. Sam rozwiązuję problemy i sprawiam, że wszystko działa i staram się innym pomóc, aby nie odjechali do konkurencji. Chcę, aby firma Acid została tym razem, aby rozpocząć grę do odebrania i „reklam” zamiast dawać tak jak Sony. Nie widzę siebie pracującego nad innym DAW tak szybko, jak to możliwe. Ale cieszę się, że nie tylko ja jestem sfrustrowany i nadal płacę za tę niegdyś świetną aplikację.

Edycja: specyfikacja komputera: Win10, 32g Ram, 1 TB SSD, karta graficzna nvidia 1660s i procesor i7 10.generacji

 

You're right mate.Once again, I would like to remind you that the basis for the work on Acid by Magix should be stable 64 bit kernel,communication with 64 bit applications, vst, vsti editors ... etc. GUI refining , focusing on the quality of the audio engine & audio rendering. At the same time, monitoring the quality when working with changing the tempo and key of audio files or pitchshifting with accurate beatgrid analysis and matching of longer time audio files.Here, ensuring the compliance and quality of Zplane Elastique Pro Better performance and stability to prevent the program from clogging unnecessarily.Retreat to 32 bits, because that's history.These are the basics.They need to work on a better form of sidechain better automation of sends and returns and envelopes not merged directly into the file graphic on the audio track, just a slide-out panel and more controls to handle that can be added as fx, etc.As of now, I'm not doing any updates above if all of this doesn't improve.

 

AmanSingh wrote on 11/25/2020, 10:10 AM

A więc zrobić czekania na następną aktualizację. Ale przeczytałem w innym poście, że Acid może nawet nie być w tej chwili pracowany z powodu Covid. Sam rozwiązuję problemy i sprawiam, że wszystko działa i staram się innym pomóc, aby nie odjechali do konkurencji. Chcę, aby firma Acid została tym razem, aby rozpocząć grę do odebrania i „reklam” zamiast dawać tak jak Sony. Nie widzę siebie pracującego nad innym DAW tak szybko, jak to możliwe. Ale cieszę się, że nie tylko ja jestem sfrustrowany i nadal płacę za tę niegdyś świetną aplikację.

Edycja: specyfikacja komputera: Win10, 32g Ram, 1 TB SSD, karta graficzna nvidia 1660s i procesor i7 10.generacji

 

You're right mate.Once again, I would like to remind you that the basis for the work on Acid by Magix should be stable 64 bit kernel,communication with 64 bit applications, vst, vsti editors ... etc. GUI refining , focusing on the quality of the audio engine & audio rendering. At the same time, monitoring the quality when working with changing the tempo and key of audio files or pitchshifting with accurate beatgrid analysis and matching of longer time audio files.Here, ensuring the compliance and quality of Zplane Elastique Pro Better performance and stability to prevent the program from clogging unnecessarily.Retreat to 32 bits, because that's history.These are the basics.They need to work on a better form of sidechain better automation of sends and returns and envelopes not merged directly into the file graphic on the audio track, just a slide-out panel and more controls to handle that can be added as fx, etc.As of now, I'm not doing any updates above if all of this doesn't improve.

 

Same here, brother. I am holding off from any further upgrades at this point. This is my DAW, my choice of weapon but it is clunky. I will wait until I know for sure that the next upgrade is stable before I pay another dime. I could have done without MIDI, VST instruments and other garbage, just solidify version 7. Go back to it and fix it. Don't try to make the GUI dark or inverted or whatever they did. Only thing they could have added was sidechaining like you mentioned.

Someone in here said it was version 8, well no, version 8 was nothing but a complete mess! I paid for 8 and used 7 because version 8 was clunkier and that dark GUI, it was like shaving in the dark with a piece of glass without a mirror. I have used it since 1998, I will never find the same workflow anywhere, period. Anyway, I could go on all day on this topic. I can't go back to any other DAW at this point, too tired to switch, I am on AcidPro 100%, unstable or not. Dealing with it. I have been pretty active in the forums to help the best I can so people don't drop this DAW once again. I have no idea if Magix ever gets in here and reads our frustration.

LooneyBinJim wrote on 11/25/2020, 1:46 PM

A więc zrobić czekania na następną aktualizację. Ale przeczytałem w innym poście, że Acid może nawet nie być w tej chwili pracowany z powodu Covid. Sam rozwiązuję problemy i sprawiam, że wszystko działa i staram się innym pomóc, aby nie odjechali do konkurencji. Chcę, aby firma Acid została tym razem, aby rozpocząć grę do odebrania i „reklam” zamiast dawać tak jak Sony. Nie widzę siebie pracującego nad innym DAW tak szybko, jak to możliwe. Ale cieszę się, że nie tylko ja jestem sfrustrowany i nadal płacę za tę niegdyś świetną aplikację.

Edycja: specyfikacja komputera: Win10, 32g Ram, 1 TB SSD, karta graficzna nvidia 1660s i procesor i7 10.generacji

 

You're right mate.Once again, I would like to remind you that the basis for the work on Acid by Magix should be stable 64 bit kernel,communication with 64 bit applications, vst, vsti editors ... etc. GUI refining , focusing on the quality of the audio engine & audio rendering. At the same time, monitoring the quality when working with changing the tempo and key of audio files or pitchshifting with accurate beatgrid analysis and matching of longer time audio files.Here, ensuring the compliance and quality of Zplane Elastique Pro Better performance and stability to prevent the program from clogging unnecessarily.Retreat to 32 bits, because that's history.These are the basics.They need to work on a better form of sidechain better automation of sends and returns and envelopes not merged directly into the file graphic on the audio track, just a slide-out panel and more controls to handle that can be added as fx, etc.As of now, I'm not doing any updates above if all of this doesn't improve.

 

Same here, brother. I am holding off from any further upgrades at this point. This is my DAW, my choice of weapon but it is clunky. I will wait until I know for sure that the next upgrade is stable before I pay another dime. I could have done without MIDI, VST instruments and other garbage, just solidify version 7. Go back to it and fix it. Don't try to make the GUI dark or inverted or whatever they did. Only thing they could have added was sidechaining like you mentioned.

Someone in here said it was version 8, well no, version 8 was nothing but a complete mess! I paid for 8 and used 7 because version 8 was clunkier and that dark GUI, it was like shaving in the dark with a piece of glass without a mirror. I have used it since 1998, I will never find the same workflow anywhere, period. Anyway, I could go on all day on this topic. I can't go back to any other DAW at this point, too tired to switch, I am on AcidPro 100%, unstable or not. Dealing with it. I have been pretty active in the forums to help the best I can so people don't drop this DAW once again. I have no idea if Magix ever gets in here and reads our frustration.

I agree with everything you guys are saying .I moved to 8 when released.OmG i was so happy that my Favourite Daw was back and being supported .Hmm i havent made a single tune since..

Well now im on 10 .03..24 i moved onto 10.04.and that was it crash crash same error ...After downgrading im plagued with upgrade at start buvt thats it.I only start as admin,I have noticed using any lets say Plugins i shouldnt have ie waves gold pack (deleted it dont call the FEDS)

I dont know if it will help ,i have 10.03.24 if you need it let me know.

If you open the preferences with shift held down it opens a new tag called internal,Its has with allsorts of magic some im sure will screw the program more but got to be worth a look.?I have moved the lower editing explorer panel to the top above tracks ... Also the boxes now have thicker outines thanks to the new menu ...

Might be a help? you can default if u get stuck...

AmanSingh wrote on 11/25/2020, 5:22 PM

A więc zrobić czekania na następną aktualizację. Ale przeczytałem w innym poście, że Acid może nawet nie być w tej chwili pracowany z powodu Covid. Sam rozwiązuję problemy i sprawiam, że wszystko działa i staram się innym pomóc, aby nie odjechali do konkurencji. Chcę, aby firma Acid została tym razem, aby rozpocząć grę do odebrania i „reklam” zamiast dawać tak jak Sony. Nie widzę siebie pracującego nad innym DAW tak szybko, jak to możliwe. Ale cieszę się, że nie tylko ja jestem sfrustrowany i nadal płacę za tę niegdyś świetną aplikację.

Edycja: specyfikacja komputera: Win10, 32g Ram, 1 TB SSD, karta graficzna nvidia 1660s i procesor i7 10.generacji

 

You're right mate.Once again, I would like to remind you that the basis for the work on Acid by Magix should be stable 64 bit kernel,communication with 64 bit applications, vst, vsti editors ... etc. GUI refining , focusing on the quality of the audio engine & audio rendering. At the same time, monitoring the quality when working with changing the tempo and key of audio files or pitchshifting with accurate beatgrid analysis and matching of longer time audio files.Here, ensuring the compliance and quality of Zplane Elastique Pro Better performance and stability to prevent the program from clogging unnecessarily.Retreat to 32 bits, because that's history.These are the basics.They need to work on a better form of sidechain better automation of sends and returns and envelopes not merged directly into the file graphic on the audio track, just a slide-out panel and more controls to handle that can be added as fx, etc.As of now, I'm not doing any updates above if all of this doesn't improve.

 

Same here, brother. I am holding off from any further upgrades at this point. This is my DAW, my choice of weapon but it is clunky. I will wait until I know for sure that the next upgrade is stable before I pay another dime. I could have done without MIDI, VST instruments and other garbage, just solidify version 7. Go back to it and fix it. Don't try to make the GUI dark or inverted or whatever they did. Only thing they could have added was sidechaining like you mentioned.

Someone in here said it was version 8, well no, version 8 was nothing but a complete mess! I paid for 8 and used 7 because version 8 was clunkier and that dark GUI, it was like shaving in the dark with a piece of glass without a mirror. I have used it since 1998, I will never find the same workflow anywhere, period. Anyway, I could go on all day on this topic. I can't go back to any other DAW at this point, too tired to switch, I am on AcidPro 100%, unstable or not. Dealing with it. I have been pretty active in the forums to help the best I can so people don't drop this DAW once again. I have no idea if Magix ever gets in here and reads our frustration.

I agree with everything you guys are saying .I moved to 8 when released.OmG i was so happy that my Favourite Daw was back and being supported .Hmm i havent made a single tune since..

Well now im on 10 .03..24 i moved onto 10.04.and that was it crash crash same error ...After downgrading im plagued with upgrade at start buvt thats it.I only start as admin,I have noticed using any lets say Plugins i shouldnt have ie waves gold pack (deleted it dont call the FEDS)

I dont know if it will help ,i have 10.03.24 if you need it let me know.

If you open the preferences with shift held down it opens a new tag called internal,Its has with allsorts of magic some im sure will screw the program more but got to be worth a look.?I have moved the lower editing explorer panel to the top above tracks ... Also the boxes now have thicker outines thanks to the new menu ...

Might be a help? you can default if u get stuck...

Holy! I am gonna take a look at that later myself. However, I love the explorer where it is (on the bottom) but maybe I can find something else in there that I can fix myself. I will hit you guys back if I am able to find a solution to some of the issues others are having. See, this is what I am talking about, there are about handful of users in here that stay active and actually try to help each other out. I have been noticing there are a few that go around in forums and try to aggrevate the already frustrated users as they sound offended or something. But I am glad us old-skool AcidPro users are still around.

Tonic wrote on 11/25/2020, 5:46 PM

I thank you all for sharing your thoughts on how to solve the problems with Acid 10 Pro.
Couple of things to update; I have learned, that when you work your project in Acid and are ready to leave the program, before you go, save your work and open a new project - once this is done, just leave Acid. Now, whenever you want to return, Acid recalls the last project (by default - I think?), which is now empty "new project".
For some reason, no VST scan or other crashing errors appear!
So, it is proven now, that there is a bug and this is the way to avoid Acid to crash or go bananas.

However, something else is troubling:
While listening the whole project, I can't edit a single track, cause Acid will freeze. Yes, freeze. Like it can't handle real-time editing. It's ridiculous really, but true.
Anyone know what's that about?

Why do I stick with Acid? I have used it since the version 4. I have learned what the word "long-suffering" means :P Also - my friend has always used Cubase and not without grey hair. He is now using the latest version of the Cubase Artist version and it is unbelievable what he reports to me; He can barely use 10 tracks with VST's on, without the program shutting down. It crackles and pops and freezes and so on. He can hardly believe when I show my project in Acid; as I tend to have from 100 to 400 tracks and active VST at least in 20 tracks - at least.
So, there you go. That is why I use Acid. Other DAW never came even close, which is laughable.

Tonic wrote on 11/25/2020, 5:49 PM

I thank you all for sharing your thoughts on how to solve the problems with Acid 10 Pro.
Couple of things to update; I have learned, that when you work your project in Acid and are ready to leave the program, before you go, save your work and open a new project - once this is done, just leave Acid. Now, whenever you want to return, Acid recalls the last project (by default - I think?), which is now empty "new project".
For some reason, no VST scan or other crashing errors appear!
So, it is proven now, that there is a bug and this is the way to avoid Acid to crash or go bananas.

However, something else is troubling:
While listening the whole project, I can't edit a single track, cause Acid will freeze. Yes, freeze. Like it can't handle real-time editing. It's ridiculous really, but true.
Anyone know what's that about?

Why do I stick with Acid? I have used it since the version 4. I have learned what the word "long-suffering" means :P Also - my friend has always used Cubase and not without grey hair. He is now using the latest version of the Cubase Artist version and it is unbelievable what he reports to me; He can barely use 10 tracks with VST's on, without the program shutting down. It crackles and pops and freezes and so on. He can hardly believe when I show my project in Acid; as I tend to have from 100 to 400 tracks and active VST at least in 20 tracks - at least.
So, there you go. That is why I use Acid. Other DAW never came even close, which is laughable.

Like to add, that I can edit any track, while I pause the project and solo out the track I want to edit. Or even partner the track with some other tracks. But if all the tracks are active Acid can't handle the editing with VST's.

AmanSingh wrote on 11/25/2020, 9:34 PM

I thank you all for sharing your thoughts on how to solve the problems with Acid 10 Pro.
Couple of things to update; I have learned, that when you work your project in Acid and are ready to leave the program, before you go, save your work and open a new project - once this is done, just leave Acid. Now, whenever you want to return, Acid recalls the last project (by default - I think?), which is now empty "new project".
For some reason, no VST scan or other crashing errors appear!
So, it is proven now, that there is a bug and this is the way to avoid Acid to crash or go bananas.

However, something else is troubling:
While listening the whole project, I can't edit a single track, cause Acid will freeze. Yes, freeze. Like it can't handle real-time editing. It's ridiculous really, but true.
Anyone know what's that about?

Why do I stick with Acid? I have used it since the version 4. I have learned what the word "long-suffering" means :P Also - my friend has always used Cubase and not without grey hair. He is now using the latest version of the Cubase Artist version and it is unbelievable what he reports to me; He can barely use 10 tracks with VST's on, without the program shutting down. It crackles and pops and freezes and so on. He can hardly believe when I show my project in Acid; as I tend to have from 100 to 400 tracks and active VST at least in 20 tracks - at least.
So, there you go. That is why I use Acid. Other DAW never came even close, which is laughable.

Like to add, that I can edit any track, while I pause the project and solo out the track I want to edit. Or even partner the track with some other tracks. But if all the tracks are active Acid can't handle the editing with VST's.

So when you pause the project and solo the track, the GUI doesn't freeze up? I will try that. Ya, the screen freezing on micro editing has been the issue since version 7.

AmanSingh wrote on 11/25/2020, 9:49 PM

A więc zrobić czekania na następną aktualizację. Ale przeczytałem w innym poście, że Acid może nawet nie być w tej chwili pracowany z powodu Covid. Sam rozwiązuję problemy i sprawiam, że wszystko działa i staram się innym pomóc, aby nie odjechali do konkurencji. Chcę, aby firma Acid została tym razem, aby rozpocząć grę do odebrania i „reklam” zamiast dawać tak jak Sony. Nie widzę siebie pracującego nad innym DAW tak szybko, jak to możliwe. Ale cieszę się, że nie tylko ja jestem sfrustrowany i nadal płacę za tę niegdyś świetną aplikację.

Edycja: specyfikacja komputera: Win10, 32g Ram, 1 TB SSD, karta graficzna nvidia 1660s i procesor i7 10.generacji

 

You're right mate.Once again, I would like to remind you that the basis for the work on Acid by Magix should be stable 64 bit kernel,communication with 64 bit applications, vst, vsti editors ... etc. GUI refining , focusing on the quality of the audio engine & audio rendering. At the same time, monitoring the quality when working with changing the tempo and key of audio files or pitchshifting with accurate beatgrid analysis and matching of longer time audio files.Here, ensuring the compliance and quality of Zplane Elastique Pro Better performance and stability to prevent the program from clogging unnecessarily.Retreat to 32 bits, because that's history.These are the basics.They need to work on a better form of sidechain better automation of sends and returns and envelopes not merged directly into the file graphic on the audio track, just a slide-out panel and more controls to handle that can be added as fx, etc.As of now, I'm not doing any updates above if all of this doesn't improve.

 

Same here, brother. I am holding off from any further upgrades at this point. This is my DAW, my choice of weapon but it is clunky. I will wait until I know for sure that the next upgrade is stable before I pay another dime. I could have done without MIDI, VST instruments and other garbage, just solidify version 7. Go back to it and fix it. Don't try to make the GUI dark or inverted or whatever they did. Only thing they could have added was sidechaining like you mentioned.

Someone in here said it was version 8, well no, version 8 was nothing but a complete mess! I paid for 8 and used 7 because version 8 was clunkier and that dark GUI, it was like shaving in the dark with a piece of glass without a mirror. I have used it since 1998, I will never find the same workflow anywhere, period. Anyway, I could go on all day on this topic. I can't go back to any other DAW at this point, too tired to switch, I am on AcidPro 100%, unstable or not. Dealing with it. I have been pretty active in the forums to help the best I can so people don't drop this DAW once again. I have no idea if Magix ever gets in here and reads our frustration.

I agree with everything you guys are saying .I moved to 8 when released.OmG i was so happy that my Favourite Daw was back and being supported .Hmm i havent made a single tune since..

Well now im on 10 .03..24 i moved onto 10.04.and that was it crash crash same error ...After downgrading im plagued with upgrade at start buvt thats it.I only start as admin,I have noticed using any lets say Plugins i shouldnt have ie waves gold pack (deleted it dont call the FEDS)

I dont know if it will help ,i have 10.03.24 if you need it let me know.

If you open the preferences with shift held down it opens a new tag called internal,Its has with allsorts of magic some im sure will screw the program more but got to be worth a look.?I have moved the lower editing explorer panel to the top above tracks ... Also the boxes now have thicker outines thanks to the new menu ...

Might be a help? you can default if u get stuck...

Hey Loonybin, how do I change a value in there? Like True to False? Thanks man.