peelnpuff wrote:yo,
ok Just to make it clear i m not on the MPC DAW team =)
.. but you should be brother because you nailed it.
100% + for all your notes and suggestions!
now my 2 cents regarding to the
"pluginscanner" component. and a rebuild of some codelines..
because i am no native i will try to keep it with an "example" so you guys can get me right...
Waves plugins ! although it is possible to use Waves plugins in MPC Software, we all know it´s a pain in the ass. Since last Waveshell updates in 9.7 it´s even not possible anymore to downgrade software to 1.6 , 1.5, 1.3.1 scan plugins and update MPC Software to latest again..
So the only way to get them working again for now is wrapping up the shell to single vsts to get them recognized. not cool !
But i don´t want to hate here and also no need to wag the finger at AKAI because it´s the same pain for Adobe Audition, Cantabile Performer or other Software.
So here maybe a hint for the developers that may help to find the problem and finally fix this!-The pluginscanner Versions in 1.2 and 1.3.1 DO properly recognize newest Waveshells and in 1.2 and 1.3.1 you can use Waves plugins without any issue
-BUT it´s not possible to upgarde older versions anymore and keep that plugs because they get lost! (the "why" you can see below)
Maybe you guys that coded it now already got the point now but i try to place a hint in my shi++y english..
it has to do something with the "additional" plugin information that are gathered since software version 1.4+
-Manufacturer and plugin type
because Waves plugins information for all Plugins are stored in that one Waveshell "maybe" waves does not propperly tag all information for each single plug and this crashes your pluginscanner routine because scanner can´t gather/place the information
OR
-your pluginscanner has an "timeout" option implanted since 1.5+ that has to be raised up... (because of the scanning time for the Waveshell)
OR
- it is because of the fact that Waves plugins comprise of 2 components now.. WaveShell-VST 9.6 AND WaveShell-VST 9.7 and your pluginscanner is not able to integrate further information to an already exiting plugin information tree that is stored in scanner cache
+possible that information of scanned 9.6 has to keep stored in cache for scanning 9.7 and that´s the issue there
cheers
also .. i already tried to hand out this (and technically more deeper) information via official support forum 2 times . i didn´t even got a proper response. it was totally clear that the guys that answered my posts has never touched any MPC Software. and i doubt the information was pushed to right directions. and that´s not the way support can work!
AKAI has to implent a routine that mails are directed to the proper place and then get´s answered.
hopefully Mpc-Tutor is able to push this information in the right directions because it seems that i am not
aarmSiggar