Zooming In slows everything down. This bug is still there!

Former user wrote on 4/22/2020, 6:34 AM

As soon as the project gets a little complex, for example about 20 tracks, I zoom in for some close editing, everything slows down to a snail's pace. It can take few seconds just to cut an paste a single piece of audio in close zoom mode. And there are absolutely no Midi/instruments running. All Audio and ZERO effects running except for the default EQ that opens with every new track.

I have had this issue since version 7, anyone else having this problem out there? Is Magix aware of this?

My specs on a new "gaming" machine, even though I don't do any gaming:


 

Comments

Former user wrote on 4/28/2020, 4:39 PM

As soon as the project gets a little complex, for example about 20 tracks, I zoom in for some close editing, everything slows down to a snail's pace. It can take few seconds just to cut an paste a single piece of audio in close zoom mode. And there are absolutely no Midi/instruments running. All Audio and ZERO effects running except for the default EQ that opens with every new track.

I have had this issue since version 7, anyone else having this problem out there? Is Magix aware of this?

My specs on a new "gaming" machine, even though I don't do any gaming:


 

Anyone? Am the only one with this issue?

DannyNYC wrote on 6/5/2020, 2:33 PM

All I can suggest is saving. OFTEN. Like after every single change. It's horribly tedious ... but the one time you forget to save after a change, BLINK. There goes your project. And for some reason it's usually after you did something BRILLANT or just made the track come together and the changes get lost. I can't count as high as the number of times it's happened to me.

It's always, like you said, when things start to get a little involved (as any will). For me, it's using undo -- especially if I don't stop the thing from playing frst. All of a sudden a project that was almost finished slows to a crawl to accommodate all the saving. I don't believe -- if they are aware of the problem -- that it's anything they can fix. It's probably an issue of taxing the system resources. If you're using MIDI, freeze the tracks as soon as you can -- that seems to help A LOT. If you are using Windows, check your system paging file. Make sure you have set the reccommended amount of scratch memory and that you set it -- don't let Windows manage it. After you do that, restart to make sure the memory is allocated properly. Also often overlooked is disk defragging --- run it at least weekly. Best of luck ...

 

sheppo wrote on 6/6/2020, 11:15 AM

I think this issue is related to the "Quick fade edit edges of audio events" setting on the audio tab of preferences.. set the quick fade time to 1 ms, and it should be resolved. You might get some clicks in your audio as a result, so remember to set it back when renedering.

I reported this issue a long time ago on the beta forum, and can confirm, it's been in the software as long as I can remember. It becomes even more of a problem if your project has tempo transitions in it. It seems to make Acid run PAINFULLY.. (as in seconds per frame, rather than frames per second).. slow when moving around the timeline.

Former user wrote on 6/7/2020, 12:28 AM

All I can suggest is saving. OFTEN. Like after every single change. It's horribly tedious ... but the one time you forget to save after a change, BLINK. There goes your project. And for some reason it's usually after you did something BRILLANT or just made the track come together and the changes get lost. I can't count as high as the number of times it's happened to me.

It's always, like you said, when things start to get a little involved (as any will). For me, it's using undo -- especially if I don't stop the thing from playing frst. All of a sudden a project that was almost finished slows to a crawl to accommodate all the saving. I don't believe -- if they are aware of the problem -- that it's anything they can fix. It's probably an issue of taxing the system resources. If you're using MIDI, freeze the tracks as soon as you can -- that seems to help A LOT. If you are using Windows, check your system paging file. Make sure you have set the reccommended amount of scratch memory and that you set it -- don't let Windows manage it. After you do that, restart to make sure the memory is allocated properly. Also often overlooked is disk defragging --- run it at least weekly. Best of luck ...

 

Hey Danny, thanks for finally answering this post. It was sitting there for a while. Plus I gave up on it. and you have no idea how frustrated I have gotten at so many levels trying to give Acid changes but I have given up completely. I just come here to see if I can help anyone else who still wants to give it a try. But to me, its a dead DAW. Just not cutting it. About you saying save a lot, man, Ctrl and S keys having fading colors by now, as I just don't trust Acid anymore about when it will take a dump mid-project. I gave up on Acid Pro in 2008 when I made the mistake of recording audio on it with a high paying customer who simply couldn't sing but wanted to. She finally got a line right after about the 100th take and the damn arrangement window froze!!! I had no excuse to explain to her that this time, it was my fault (or Acid's poor recording handling). That was when I learned a valuable lesson that Acid is finished. That was version 6 or 7 I think. I switched completely to cubase for everything. No DAW has Acid's pick and paint ability and the way the explorer works, but Magix even ruined that. Well, not gonna go into that detail.

If I was Magix, I would have kept version 8, and just worked on that. Changing GUI colors, adding senseless features was unnecessary to start off as other DAWs are years ahead in that game. Oh well, my DAW of choice now is FL, as that kinda comes close as far as "painting" goes but its tedious to work in. I almost own all famous DAWs in their full version, because I kept looking for that same workflow as Acid pro but nothing matches. I just wish Acid Pro was in the hands of musicians who actually used this DAW well. The way the updates and upgrades are being done, I am sorry to say, there is no way that the developers are former Acid Pro users.

Well, don't work on major projects and risk them like I did.