[Feedback] How do you like version 8.0.8.29 ?

Comments

Rednroll wrote on 3/19/2019, 10:51 AM

 

 

One thing I really wish is that the Plug-In manager showed more details like it does in SF12. In SF 12 the Plug-in manager displays if it's a VST2 or VST3 plugin as well as tells you if it's 32bit or 64bit plugin. AP8 seems to only tell you if it's a VST3 plugin or not which is better than Vegas Pro which doesn't seem to tell you anything in regards to the plugin properties and lets you know which version of the plugin you are using in your project.

the current build DOES show the architecture, if the VST is a different architecture from the version of Acid you're using. e.g. if you're using 64bit version, it will label the 32bit plugins accordingly. If the VST is the same architect as the version of Acid you're running it doesn't display it. Did you actually add in your 32bit Plugins?

Anyway to get AP8 and Vegas Pro 16 to display plugin details like SF12? There's a little thing of consistency across apps that I really like and it seems SF12 has the best implementation. When you enable "Details" in the AP8 plug-in manager view there is a column of "version" but nothing is displayed. I'm guessing that column should display VST version?

Yeah, you're right there. Looking at the properties info of a plugin does show the version, but it's not being populated in the details view.

 

 

One thing I really wish is that the Plug-In manager showed more details like it does in SF12. In SF 12 the Plug-in manager displays if it's a VST2 or VST3 plugin as well as tells you if it's 32bit or 64bit plugin. AP8 seems to only tell you if it's a VST3 plugin or not which is better than Vegas Pro which doesn't seem to tell you anything in regards to the plugin properties and lets you know which version of the plugin you are using in your project.

the current build DOES show the architecture, if the VST is a different architecture from the version of Acid you're using. e.g. if you're using 64bit version, it will label the 32bit plugins accordingly. If the VST is the same architect as the version of Acid you're running it doesn't display it. Did you actually add in your 32bit Plugins?

Anyway to get AP8 and Vegas Pro 16 to display plugin details like SF12? There's a little thing of consistency across apps that I really like and it seems SF12 has the best implementation. When you enable "Details" in the AP8 plug-in manager view there is a column of "version" but nothing is displayed. I'm guessing that column should display VST version?

Yeah, you're right there. Looking at the properties info of a plugin does show the version, but it's not being populated in the details view.


I'm pretty sure I have SF and Acid scanning the same folders and my 32bit plugins have been added. What's odd to me is that SF shows all my VST3 plugins as being 64bit but in Acid as you have shown they're labeled VST3 "32bit".

I'm really confused, so if there's no label next to the plugin name, and I'm using the 64bit version of Acid, then I should assume that it is a VST2 64bit plugin or a VST3 64bit plugin? It seems to be the latest Acid update is "VST2" according to what I'm seeing with my plugin names, yet they added VST3 support in the latest update.

If you could help me out here, because I'm really struggling to understand the methodology in Acid and it's definitely much clearer in SF.

These are my iZotope plugins. Starting from the top.

"Neutron 2"= ???/???

"Neutron 2 (VST3)"= VST3/64bit??

"Neutron 2 (VST3) (32 Bit)"= VST3/32bit

 

Now I go to my Waves folder

"Abbey Road Plates Mono"= ???/???

"Abbey Road Plates Mono (32bit)"= ???/32bit

 

What a mess to try and figure out.

Rednroll wrote on 3/19/2019, 11:28 AM

OK, I just confirmed my VST scanned folders between Sound Forge and Acid Pro

Sound Forge VST folders

*C:\Program Files\VSTplugins\
*C:\Program Files\Common Files\VST3\
*C:\Program Files (x86)\VstPlugins\

Acid Pro VST folders

*C:\Program Files\VSTPlugins\
*C:\Program Files\Common Files\VST3\
*C:\Program Files (x86)\VstPlugins\
C:\Program Files (x86)\Common Files\VST3\
C:\ProgramData\ACID\ACID Pro\8.0\MAGIX Plugins\
C:\ProgramData\ACID\ACID Pro\8.0\MxSynth\

 

So now the problem, in Acid I have no waves VST3 plugins showing up, but they are clearly showing up in SF12. In the Izotope plugin folder, it shows "(VST3) next to the plugin's name. So therefore that must mean that Acid must think it's a VST2/64bit program.

Djronrella wrote on 3/20/2019, 5:08 AM

Latest Version has light theme!

Click Options Preference and then Display!, Look for Icon to click light or dark background!

Rednroll wrote on 3/21/2019, 6:13 AM

 

the current build DOES show the architecture, if the VST is a different architecture from the version of Acid you're using. e.g. if you're using 64bit version, it will label the 32bit plugins accordingly. If the VST is the same architect as the version of Acid you're running it doesn't display it. Did you actually add in your 32bit Plugins?

I think I know where my confusion is with all this. Yes, Acid does show you if you're using the 64bit or 32bit version and the names of plugins makes sense from what you described. It shows "(32bit)" next to their names when I'm using the 64bit version of Acid. What it doesn't show you is if it's a VST3 or VST2 host. Acid added VST3 plugin support in the latest update. So based off of what you described and what I'm currently seeing with my plugin names is that the problem seems to be that although the latest update has VST3 host support, Acid still thinks it is a VST2 host since I it displays "(VST3)" labels next to my plugin names, thus causing confusion since Acid is not behaving consistently with its plugin naming convention to what you described.

 

So don't expect any type of consistency between Magix apps is the theme I'm starting to witness. Don't expect consistency for it's VST plugin support naming within an app and don't expect consistency between Magix apps from the same family of products such as Sound Forge Pro 12, Acid Pro 8, and Vegas Pro 16. Expect the unexpected. Good to know.

Gordon-Currie wrote on 3/21/2019, 11:46 PM

While I think it is cool that there is 32 bit VST support, I am not one who wanted this - yet I cannot even open the new version. I wish Magix had implemented this so we had a choice to use the 32 bit plugins.

Acid 7 Pro and Sound Forge 11 were the last 32 bit hosts I had. When A8 and SF12 came out as 64 bit, I looked forward to removing every 32 bit plugin from my system. Maybe if I had done that before updating, I wouldn't be dead in the water.

Gordon-Currie wrote on 3/23/2019, 6:06 PM

After trying the "delete XML files" tip (no change) and then uninstalling and reinstalling (no change), I uninstalled and reinstalled the last good version. Works and I can get things done now.

Maybe the fact I have Sony Acid 7 Pro also installed could be a problem? I made sure to leave unchecked the option to install the 32 bit version.

Also, I just discovered this - AP 8 can no longer read MP4 files. So if you use Acid to compose to video, you must use AVI (or some other legacy format).

Matt-Francis wrote on 3/24/2019, 10:40 AM

Latest Version has light theme!

Click Options Preference and then Display!, Look for Icon to click light or dark background!

how to upgrade or are you talking about MAGIX ACID Music Studio 11.0.7.18 x86 x64

Open AP8, go to Help at the top of the screen, click on Update program online.

Taurus_1911 wrote on 3/25/2019, 11:04 AM

Here's what I've been getting in the new build:

 

Input monitoring chooses to randomly stop functioning in the middle of projects. Anyone ever experience that? It's all fine for while and you can hear what you're playing as you're recording, then all of a sudden input monitoring ceases to function on RECORD only. It's bizzarre. And it's crippling.

 

Also, that problem seems to park itself in a project once it occurs, and it's universal to the project. Once it rears its head, all tracks have the input monitor disabled on RECORD only. The track records, but you can't hear what you're doing. You can eek by if you know you're really sticking your technique and it feels right, but honestly, that's lame. You can also hear a bit of your playing if your input device allows you to hear the signal direct, and you can pull down ACID's mix to balance, but again, that's lame.

SO, what is corrupting the project file? New ones function fine....for awhile. Some projects escape this fate, some do not. Of course it always seems to occur when you're really in the zone and chasing down something cool.

CidBil wrote on 3/27/2019, 5:13 AM

I'm finding it interesting that some folks don't seem to have the update program online option. Possibly a bug? Here's what mine looks like.

Tinus72 wrote on 3/27/2019, 7:57 AM

Hi, with the light theme back in the game, i finaly did the upgrade, had same issues, after uninstalling all, cleaning up al leftovers, registry, programdata, user profile data, i don't use 32 bit vst plugins anymore so here no problems.reinstalled acid 8, started, plugin scan oke, updated to 8.08.29 and started acid, all running, only issue sofar with some vst's having a different name now, so vst loading error in project, reassign vst, issue solved. running on waves soundgrid

CidBil wrote on 3/27/2019, 9:42 AM

@mikhail-e......I'm curious as to which version of AP8 you have installed. Comparing my screenshot to yours, I noticed that in addition to the Update Progamm Online option, you also have an option to go to Acid Planet.com. Considering that AcidPlanet.com no longer exists, and instead Producer Planet is in it's place in the menu, seems to me you're working with an outdated version. HTH

CidBil wrote on 3/27/2019, 2:37 PM

@mikhail-e......I'm curious as to which version of AP8 you have installed. Comparing my screenshot to yours, I noticed that in addition to the Update Progamm Online option, you also have an option to go to Acid Planet.com. Considering that AcidPlanet.com no longer exists, and instead Producer Planet is in it's place in the menu, seems to me you're working with an outdated version. HTH

I'm 15 years old with Acid.... and 8 version of pirate ))

 

CidBil wrote on 3/27/2019, 2:38 PM

LOL, well my young friend, there's your problem........if you're using a pirated version, I'm pretty sure you're going to have issues..........plus it's illegal.

CidBil wrote on 3/27/2019, 4:32 PM

Copyright Infringement. International Law.....and again, if you are using a pirated version, or keygen or crack of some sort, then you will continue to have problems, and I'm pretty sure you won't be able to upgrade. Just sayin'...

You might want to check out Music Studio 11.....at $60, it should fit your needs, and with the license in hand, you'll be able to upgrade to AP8 eventually...here's the link, there's a free trial available that will at least let you "test drive" it, to see if it's something you can use......HTH https://www.magix.com/us/music/acid/acid-music-studio/

lt20018 wrote on 3/28/2019, 7:09 PM

Ok CidBil i have that same issue where my Help Menu still shows Acidplanet and i purchased mine from Magix...Whats the deal? Also still inquiring about this so called patch? Asked the forum where to find about a week ago and nothing...I have slowed down on my gripes with Acid Pro 8 and other issues involving the DAW due to lack of support here in the states..Reno Support hours and also professionalism. I have started to search for a new DAW...from frequent crashing to all of these back end "fixes & patches" has totally slowed down my work production to the point I am reconsidering everything....

sheppo wrote on 4/2/2019, 8:07 AM

So don't expect any type of consistency between Magix apps is the theme I'm starting to witness. Don't expect consistency for it's VST plugin support naming within an app and don't expect consistency between Magix apps from the same family of products such as Sound Forge Pro 12, Acid Pro 8, and Vegas Pro 16. Expect the unexpected. Good to know.

@Rednroll - sorry dude, I didn't see your response. It's always best to @ someone when you're replying to them so they get a notification.

I think you've hit the nail on the head, but do not agree it was done by design. I have no proof, of course, just I think these types of inconsistencies happen easily. I'll raise this as a particular inconsistency that needs tidying up between Magix's products. Sadly that may mean if it gets 'fixed' some projects from this version will likely throw VST issues when loading in future versions..

@lt20018 - I would try uninstalling Acid, then downloaded and installing it again from your magix.com profile / my products section. The latest version was not previously published there (maybe it is now), but the version that was will prompt you to download the very latest version. Let me know how you get on an @ mention me so I get a notification.

LooneyBinJim wrote on 4/5/2019, 5:12 PM

I love Acid.....I Love/loved Acid pro..

I have had a very very good experience as a Magix customer the support have always helped always replied and kept me upto date with progress .Brilliant.

Even gave me a access to 8.08.10 beta because the problem was fixed however 8.08?? wasn't due till jan?????.

How ever today i feel Robbed .Loaded web to see Acid Pro 9.

YES Acid Pro 9 may release buy now get 9 upgrade on release....WTF I have spent the last year trying so hard to make music using Acid My favourite piece of kit since Acid Pro 1......I purchased 8 upgrade 25/4/18 before the price was set to rise,, what a idiot i am.So many of us have spent the last year running Acid reporting bug after bug .I have checked the small print i cant find it but im sure it says somewhere Ap8 users will pay for the Privilege of testing the software for future release of ACID PRO 9. Magix said i would get the old ACID experience but 64bit ...Well Magix i got sore head from all the hours spent loading restarting and shutting down whole sessions.

I HAD THE SAMARITANS SUICIDE LINE ON SPEED DIAL IT REALLY HAS BEEN I EXPERIENCE ...

aACID 9..... mAY RELEASE thanks Magix

lt20018 wrote on 4/6/2019, 3:31 PM

I love Acid.....I Love/loved Acid pro..

I have had a very very good experience as a Magix customer the support have always helped always replied and kept me upto date with progress .Brilliant.

Even gave me a access to 8.08.10 beta because the problem was fixed however 8.08?? wasn't due till jan?????.

How ever today i feel Robbed .Loaded web to see Acid Pro 9.

YES Acid Pro 9 may release buy now get 9 upgrade on release....WTF I have spent the last year trying so hard to make music using Acid My favourite piece of kit since Acid Pro 1......I purchased 8 upgrade 25/4/18 before the price was set to rise,, what a idiot i am.So many of us have spent the last year running Acid reporting bug after bug .I have checked the small print i cant find it but im sure it says somewhere Ap8 users will pay for the Privilege of testing the software for future release of ACID PRO 9. Magix said i would get the old ACID experience but 64bit ...Well Magix i got sore head from all the hours spent loading restarting and shutting down whole sessions.

I HAD THE SAMARITANS SUICIDE LINE ON SPEED DIAL IT REALLY HAS BEEN I EXPERIENCE ...

aACID 9..... mAY RELEASE thanks Magix

I feel that pain to the CORE! I will say for the ones that have went through the back and forth year troubles with AP8...AP9 should be way better and stable, at least the ones that stuck it out should get a discount...just saying...I will still hang in there to see what AP9 looks like.......to be cont...

lt20018 wrote on 4/6/2019, 4:52 PM

So don't expect any type of consistency between Magix apps is the theme I'm starting to witness. Don't expect consistency for it's VST plugin support naming within an app and don't expect consistency between Magix apps from the same family of products such as Sound Forge Pro 12, Acid Pro 8, and Vegas Pro 16. Expect the unexpected. Good to know.

@Rednroll - sorry dude, I didn't see your response. It's always best to @ someone when you're replying to them so they get a notification.

I think you've hit the nail on the head, but do not agree it was done by design. I have no proof, of course, just I think these types of inconsistencies happen easily. I'll raise this as a particular inconsistency that needs tidying up between Magix's products. Sadly that may mean if it gets 'fixed' some projects from this version will likely throw VST issues when loading in future versions..

@lt20018 - I would try uninstalling Acid, then downloaded and installing it again from your magix.com profile / my products section. The latest version was not previously published there (maybe it is now), but the version that was will prompt you to download the very latest version. Let me know how you get on an @ mention me so I get a notification.

Uninstalled...followed instructions...reinstalled. Now just stuck on "Scanning for Plug-In's & Scanning VST". I have repeated the process many times. Same result...

passionfly1 wrote on 4/7/2019, 10:39 AM

I can't get that far. New version freezing on start up while scanning for vst. I emptied vst folders to see if I could get started but no joy. Help !

 

@jon-l

I'm really sorry for the issues you have been experiencing with the latest patch release. It had a massive rebuild of the complete plug-in scanning system, so even after much, much testing, some problems we couldn't predict. If you are having trouble getting ACID to open because of the VST scanning, the following might help:

With ACID not running, 
locate the following directory on your machine:

C:\Users\User\AppData\Local\MAGIX\ACID Pro\8.0

Locate these files: 
acidpro.plugincache_x32.xml
acidpro.plugincache_x64.xml
​acidpro_bridgeaware_plugincache_x64.xml

and delete them. If you open the program again, ACID should reset its search directory for plugins. It will be necessary to add and scan again any additional VST folders.

If you are able to open ACID, a force rescan on the VST configuration tab should do the trick and show all the available plugins.

@Animal-Nation I would recommend you start the application as administrator, this helped another user!

Cheers!

Bea

HEY! This actually fixed my problem and rebuilt all the VST locations on my hard drive automatically. Even places I had no idea I had VST3 add-ins. You should work for Magix Tech Support. You accomplished more in one post then they can in a few days! BRILLIANT!

I don't understand why the update did not even do this simple procedure and prevent all the headaches of the update scanning the VST folders. My entire Acid Pro 8 app had a serious font resolution issues problem and had to be exited afterwards many times due to this erroneous VST folder scan. THIS FIXES IT!

passionfly1 wrote on 4/7/2019, 10:45 AM

I'm finding it interesting that some folks don't seem to have the update program online option. Possibly a bug? Here's what mine looks like.


FYI, Magix, here in the States we only spell the word "program" with ONE (1) "M" not TWO (2). Its "program" not "programm" or even "programme". I have actually seen it only spelled with an "E" only in Europe so I am assuming its a typo since its not even spelled with that useless "E". =P
Why add a second extra "M" when one will do? You don't say it any different, why add extra useless letters?
Its just a very silly language thing =P

johnebaker wrote on 4/7/2019, 12:19 PM

@passionfly1

It is a translation error - Programm is the German spelling of the word for Program.

John EB

Forum Moderator

Last changed by johnebaker on 4/7/2019, 1:04 PM, changed a total of 1 times.

VPX 15, Movie Studio 2024, 2023, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional 64bit on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB HDD (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 23H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

Musition wrote on 4/7/2019, 5:23 PM

I haven't had much time to check out all of the fixes, but I like the update so far. I'm glad to have a light theme to choose. One thing I did notice however... Next time there's an upgrade, make sure to save all user settings so they can be restored. What happened with me was that, after the update, I noticed all the track colors went back to their defaults. I think I'm one of the few people that customizes those colors. I'm not upset over it, just wanted to mention.

toddbooster wrote on 4/8/2019, 4:15 PM

I'm finding it interesting that some folks don't seem to have the update program online option. Possibly a bug? Here's what mine looks like.

Man, with all this work updating, I really wish they'd finally fix that spelling mistake!