![]() ![]() Also is always better to group your audio channels to the main busses for the great tape sat and glue. In this case I recommend to use them for additional reverb stuff because they are not delay compensated and introduce some latency. Well, the 12 main Busses are enough for the most applications but in the case you will need more than that you can use the utility busses. I am also a Pro Tools user and I mix in mixbus 32C. I can only be responsible for what I say, not what you understand.(08-29-2016, 07:28 PM)Arionas Wrote: Welcome! How can it work in almost 7 other DAW but only failed in Mixbus. I always make sure every VST plugin I installed works on all DAW including (Machine/Komplete) that I use and so far everything works on every DAW, no blacklist in any DAW. It's basically the Harrison Mixbus DAW itself that has its own method of scanning the plugin. I think, for Harrison mixbus, it has nothing to do with the crack or other group release or merging releases. All DAW can accept VST/VST3 plugin doesn't care who k'd or legit except for this very DAW, the Mixbus. Only for Reason Rack which can still be considered as Extension, same goes to Pre-Sonus Add-ons and extensions. None of the R2R DAW release prohibited the user from using either legit, k'd by other group VST and VST3. ![]() "Contents can be installed to only R2R PreSonus release." - releases that been labeled like that are mostly the expansion or add-on. So far everything works great, I have most of the group releases plus older group like AiR, H2O etc still working fine and been working since their release. I understand that combining releases might cause problems but I think I've been here long enough to know which group release I'd like to use and merging groups release for a dev brand. exe or emulators + cert, And also explain with revisions what they did wrong and own it while others groups just don't care to explain or even communicate.ฤก. I only use R2R releases because they do not modify the windows structure with untrust worthy files, they modify release. R2R might need the original update wintrust.dll to function correctly in the first place and that may be also why some might be having problems with R2R release not working because they are not understanding the bottom line. But the same time when uninstalling forgetting to remove said wintrust.dll and replace it with the original. Now another thing is the issue with VR wanting you to switch the wintrust.dll for they Modified version. Another problem i have noticed is that many users keep bouncing back and forth between VR and R2R Releases and are not taking the required steps to fully uninstall the VR versions or these Releases correctly, Even if they removed all registry code allot of the VR installs leave behind locked files and that is when R2R installs say that it cant install because a dirty LIC on some of the programs. as an example = A witch says, Contents can be installed to only R2R PreSonus release. I might not of explained it correctly or my wording might throw you off. Hi Stevie Dude, what if it has to do with the releases that are installed on your system, say some of the plugins are from VR and work with other Daw's but since this is a R2R release that may as you might have read on other R2R releases that the plugin's can only work if your using R2R versions of the other Daw's. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |