-
ACID Product Familyon 11/12/2019
ACID Pro 8 / 9 / Next - public beta versions October, 25
@Trensharo >> 3. MAGIX does have a refund policy. I've used it, several times. You have 14 days after a purchase to get a refund. You put in the support request, and they process it - no questions asked. The money is refunded to your account within 2 days of support getting your request. So that is totally your fault, not theirs. The refund policy, in my experience, is practically flawless. Within 14 days we were getting promises of fixes, and they have signally failed to deliver. That is totally not my fault. That I believed them is my fault.
-
ACID Product Familyon 11/10/2019
ACID Pro 8 / 9 / Next - public beta versions October, 25
@Trensharo >> Hobbyists need to take it more serious, if they want to get serious about problems. I have. I moved to REAPER and everything works straight out of the box. I'm only here because I paid for ACID and still have a current licence for it and don't have much time for paying for products that don't work. If Magix had a refund policy that worked then I'd take it and be out of here in a flash, leaving you to your weird theories. Also - @Greg-Elkins said: >> Is there some sort of trick to scanning 64 bit VST2 plugins? I can't get it to happen no matter what I do. Force rebuild doesn't do it. This is the same issue as I am facing. It's not some drivel about prehistoric architecture; it's about ACID not being able to scan directories and process the content. That is - as I said at the start of this thread - fundamental stuff. If they say they support something then they should support it, if not then they should say that too. It's not sticking to the advertising that is what bothers me the most. If Magix wants to refund me on v8 and v9 then I'll be delighted as nothing seems to work, unlike my cash which worked perfectly fine.
-
ACID Product Familyon 11/9/2019
ACID Pro 8 / 9 / Next - public beta versions October, 25
@Trensharo > Most of those plugins have 64-Bit versions, so just use those. Most but not all. Also, buying the 64 bit versions costs money. They work in REAPER, they don't work - or even scan - in ACID. Remind me which product is causing all the problems? > At some point, the onus is on the user to keep their plugins up to date. I also think there is at least some onus of the DAW manufacturer to provide a working product. ACID hasn't worked since v8 first came out. And anyway - if these 'don't work' then why are they supported at all? What a high-handed attitude to take! > Also, the standard installation directory for 32-Bit VST Plugins is C:\Program Files (x86)\Steinberg\VstPlugins. Try moving the data to there (or adding a Link in that folder) and see if the VST scanner reacts differently: It makes no difference. (It has also worked in that folder since v2 of ACID. Has something changed?)
-
ACID Product Familyon 11/6/2019
ACID Pro 8 / 9 / Next - public beta versions October, 25
Is there anything I can provide to assist with debugging? Thanks for your feedback and offer to help. Please tell us some examples for 32 Bit soft synths (manufacturer, name) which do not load (that means they are not scanned/recognized, or they fail when trying to use/instantiate them?) Please note that the Magix softsynth instruments which are coming with ACID only show up as 64 Bit by purpose, and when loading 32 Bit projects containing 32 Bit Magix Synth they are automatically replaced with their 64 Bit counter part. @Frank_Fader Attached is a folder list view of the 32 bit VST folder on my system. The folder is C:\Program Files (x86)\Vstplugins. That folder has been added to the VST Plugin Manager and 'force rescan' was selected. Not one of these plug-ins is available in the beta of Acid 9x64, and none are reported as having failed either. Edit: Not to throw in a grenade here, but the other DAW on my system picks all of these up fine.
-
ACID Product Familyon 10/29/2019
ACID Pro 8 / 9 / Next - public beta versions October, 25
Update - I went along to PROFILE\AppData\Local\MAGIX\ACID Pro\9.0 and deleted the XML files there and restarted the Acid 9x64 beta. This time it loaded all of the 32 bit VSTs (which is good) and none of the 32 bit soft synths, (which is bad). It loaded the 64 bits soft synths fine, though. Is there anything I can provide to assist with debugging?
-
ACID Product Familyon 10/28/2019
ACID Pro 8 / 9 / Next - public beta versions October, 25
I installed the new version and now none of my vst from vstplugins and stainberg/vstplugins show up only vst3s and acid vsts??? going back to older version. Yep, that's what I am getting too. I even tried it on another system - same result. ACID 9.0x beta doesn't pick up any 32 bit VSTs. Did your installation (weirdly) pick up the vendor names though>? Mine did.
-
ACID Product Familyon 10/25/2019
ACID Pro 8 / 9 / Next - public beta versions October, 25
Am I missing something here? I installed the beta of Acid PRO 9.0 x64 (9.03 b29) and pointed it at the three VST folders I have for x64, VST3 and x86 VSTs. Acid has picked up none of the 32 bits soft synths at all, but has picked up all the vendors names. (GForce, Arturia, etc....) Edit: it doesn't seem to have picked up any of the 32bits effects either. Edit #2: None reported as failed, none reported as ignored, and none reported as unavailable
-
ACID Product Familyon 10/6/2019
Thoughts from a ONCE loyal customer
@Christopher-Frank I cannot agree with you any more. Magix has destroyed the product completely. I'm well aware that support forums seldom have any nice job, well done posts anywhere on them as the people who come to it are seldom those who are having no problems at all. But here - have a look at the top posts on the forum; the problems are not just numerous - they are fundamental. I keep ACID 7/8/9 on my system because I have to - I have money invested in it and - more importantly - a whole load of musical projects which I may need to re-open some time. That they cannot always be re-opened without the usual round of unpredictable issues, ranging from dropping VSTs, losing effects, whole arrangements failing to be recognised by the very software that created them, and random white screens of death that presage another loss of work. I've switched to another DAW that seems to...well...work. (Ironically, I think it was put together by former Sony software engineers who worked on ACID back in the day) Sorry Magix - but ACID is dreadful. I am genuinely pissed off that I shelled out money for this, and even more pissed off that I shelled out money for v9 which was supposed to sort all the problems from before. As anyone who uses the product can tell you, v9 is substantially more unusable than the latest versions of v8. As has been said elsewhere, 'we are working on a fix' is no solution. At best I feel like an unpaid, unannounced pre-alpha tester; at worst I feel like I am the victim of some kind of fraud.
-
ACID Product Familyon 9/16/2019
Acid Pro 9.0.3.26 crashing
Is this a beta? I'm on 9.0.1 and can see no updates.
-
ACID Product Familyon 8/8/2019
ACID 9.0.1 and VSTs
@latxeroloko mellotronworker how do you do to work with kontakt in acid 9 ?? It's a 20 step process. A bit like this: Load Acid 9.0 Acid 9.0 crashes as it loads Reboot machine in hope for the best Load Acid 9.0 again It starts Look for Philharmonia VST and fail to find it Load inferior string samples in Kontakt 5.x instead thinking 'ah, this will do...I suppose' Record the MIDI piece into ACID Do some other stuff. Watch Acid crash slowly in the white screen of death as you do something innocuous like try to open a bus Load Acid 9.0 Acid 9.0 crashes as it loads Reboot machine in hope for the best Load Acid 9.0 again It starts Load track. Get a load of warnings about missing VSTs, including Kontakt which was loaded only a minute ago. Also notice a bunch of others missing without any reason. Play track. Experience the sound of a Stone Age MIDI piano playing my newly recorded string track. Scream. Go to https://www.reaper.fm/ and download the 60 day trial version which works flawlessly and without vast expense. Wonder why I was ever so stupid. No exaggerations.
-
ACID Product Familyon 7/30/2019
AP9 Beatmapper & Zoom issues
Beatmapping in AP9 appears to be utterly broken. I have tracks made with AP7 and AP8, neither of which will line up in AP9 at all. I am hoping that a fix is in the pipeline, but asking Magix support about this is like talking to an unresponsive brick wall.
-
ACID Product Familyon 7/27/2019
ACID 9.0.1 and VSTs
Then I have to assume that the next release will be v10 and I for one will not be wasting any more money on this. If they really want to restore faith in any of this then they have to have a proper beta test and roll out a version of v9 that reliably fixes everything. The latest thing I am finding now using v8 is that loading some perfectly straightforward VSTs (such as Kontakt!) does not display the VST's graphic at all, instead obscuring it behind a black box, usually precursor to the whole application crashing hard. I am also finding that loading VSTs in v8 isn't as reliable or consistent as I'd like, but is still way better than v9. None of my VST-3 instruments from Arturia load at all. (If anyone can shed any light on why a VST doesn't load when (a) it's there and (b) it loads perfectly fine into the likes of Cantabile, please let me know) With or without VST-3 support or 64 bit processing, Sony's version worked flawlessly all the time, every time. I am seriously considering going back to v7 and asking Magix for a refund.
-
ACID Product Familyon 7/26/2019
ACID 9.0.1 and VSTs
@Maxtheschu Sadly, this isn't a complete answer. No version of v8 (as far as I can tell) supports presets in VSTs, so they all get lost. What Magix need to do is update the last version of v8 to fix the presets issue and that issue only and then release it. Why they thought anything else was a good idea is beyond me.
-
ACID Product Familyon 7/15/2019
Are any of the new versions of ACID actually stable?
I think its just the Music Studio version which sucks. Not so. Acid 9.x has massive issues with plug-ins that have cost me way more than Acid ever did. Right now, it's hopeless garbage. Every time they add something something else falls to bits. In all candour, I'd avoid it right now.
-
ACID Product Familyon 7/12/2019
Are any of the new versions of ACID actually stable?
Interesting. So when is Magix sending out the apologies and refunds?
-
ACID Product Familyon 7/7/2019
Loops Collection Folder in Options
You think I haven't tried? I'm not the only person reporting radio silence from Tech Support.
-
ACID Product Familyon 7/7/2019
Loops Collection Folder in Options
Silence. It's bad enough this this is ridden with bugs, but being ignored by both forum and tech support is worse.
-
ACID Product Familyon 7/6/2019
ogg files
@Teije-Euverman Strange you should say that. I have a short 3 second OGG percussion loop I use sometimes, and used in previous versions of Acid Pro too. I dropped it into 9.0.1/64 and found that (a) it assumed it was a 35 second loop and (b) the sound was essentially some sped up and unrecognisable nonsense that lasted about a quarter of a second, following by 34 3/4 seconds of utter silence. What's going on?
-
ACID Product Familyon 6/30/2019
AP9 New Track problem (Simple)
Yes, I am getting this too. If it's a feature then I'd like it removed. I want to decide where the track goes, not someone at Magix.
-
ACID Product Familyon 6/30/2019
Just installed Version 9
When rendering in place, it keeps going back to the default folder, instead of last saved folder. Yes, I am getting this too. It's infuriating.
-
ACID Product Familyon 6/29/2019
Acid Pro 9 MP3 Support
They have also fixed the toolbar cropping...
-
ACID Product Familyon 6/20/2019
Acid Issue with Splash Sceen
I got around this by renaming my 32/64 VST folders, then starting up Acid 9.x, which obviously omitted all my VSTs. That let me get in and take out the splash screen setting. Unfortunately, that let me see all the VSTs that Acid 9.x is refusing to load which Acid 8.x loaded fine. Can someone offer me even the slightest explanation? I have so many projects invested in Acid that giving up on it seems like an extreme step, but frankly it's looking like it's going to have to happen if I am to get anything done.
-
ACID Product Familyon 6/20/2019
Acid Issue with Splash Sceen
@ralftaro > It's important that you made sure to include a space between the closing quotation mark and the beginning of the "/NOVSTGROVEL" command line argument. Sorry - didn't work. It still shows the VST scanning dialogue box, and it still locks. Who exactly is testing this stuff that we are paying money for?
-
ACID Product Familyon 6/19/2019
Acid Issue with Splash Sceen
Man, that’s annoying. Can you alt-tab to the window behind? @toddbooster alt-tab switches between processes. As this is within the same process, that does nothing. Is there actually a beta program for this software? I mean proper testers? Even some chimps would be nice. Or are the poor suckers who paid for it expected to fulfil that role for Magix? @ralftaro Here's an idea. Why not build in a 'safe mode' that allows Acid Pro to start up without loading any VSTs or any project files? At least that way we can get to the settings.
mellotronworker
Offline, Last login 8/12/2020, Member since 7/8/2018