druidI use Drumatic 3 and when I scan the folder where it is located, it works fine. Do you have many plugins in the same folder as Drumatic? You can also import a plugin (instead of a folder) and point it specifically to Drumatic. If you can’t see it listed there, then you don’t have the .dll plugin that is required, which would be why it can’t be used. If you can see it listed, then you tell Podium to import it and it doesn’t work, let us know.
druidTry this free plugin. I use it on my default template master track.
druid@UncleAge wrote:
I don’t think XT1/2 verifies plugins upon startup at all. My understanding is that it verifies them when you load them on a track. And I could be wrong but I’m pretty sure it is the only host that does this.
No it doesn’t, you’re right. What I was trying to get at was that it lists .dll files (I think that’s how it does it) when you actually load that submenu that lists them. So no loading at startup, AND no searching a massive folder with tons of plugins. Rather, just read files, then try to load that plugin when you actually use it in a project. I think that’s how it works.
I always liked it, personally. It was dynamic. I didn’t need to update a plugin list, either central or per project. Still a problem for people with lots of plugins in one folder, but then I’d say it would be hard to scroll through that many plugins in a menu anyway.
druidThe way I do it is to have a template “blank” project, that I use when I start a new project, that has all the plugins loaded into it. And I had issues importing a lot of plugins as well. It seems to me it depends how many you import at once. I have mine organised in folders, so what I ended up doing was to import just one folder at once, instead of the whole VST folder. That way, I was able to import them all.
Not ideal; my ideal is the way XT1 (and 2?) does it, which is to have a submenu and then list folders, then .dll files. When it opens that submenu of that folder, it loads that folder at the time. This is bad for people who don’t like having subfolders, or even if they use folders to organise their VSTs, have lots of plugins.
druidOn a similar topic, I used MIDI channels for a track so that within a VST (eneryXT) I could trigger other events with notes but not have them play back the synth inside. I found it useful, for instance, to switch between different filters for drum patterns (so, notes could tell it to switch between unfiltered, hipass or lopass filtering). By separating the channels, I could contain information in the one MIDI event that was meant to fit together, and not need automation just for switching an input between one or two others inside of energyXT.
I’m sure many people have more uses for MIDI channels than I did.
druiddruidFor future reference, ASIO4ALL uses standard Windows audio (probably DirectX / Direct Audio?) and creates a virtual ASIO driver. So, that’s why I can use my motherboard’s on-board audio solution in Podium, because I use ASIO4ALL, which Podium interacts with its ASIO driver, and then ASIO4ALL converts all that to normal Windows Audio drivers. Something like that.
I’m glad you fixed your problem. The wireless card was doing that? That’s quite strange, for it to only affect ASIO audio and not normal audio? Still, a solution is a solution!
druid.. I’m such a sucker. I went for the Harmless one as well.
I’ve now bought this one too. Thanks for the heads up!
druiddruidWorking fine for me, on 64-bit, except for my Tascam USB audio interface. If you use a semi-pro or pro audio interface, check the drivers, and do yourself a favour and check out Google to see if there is negative feedback for it. In Tascam’s case, their 64-bit drivers are shocking and it seems to me the majority of users have issues with it, but they refuse to even look at it, or acknowledge it with more than “you should go back to 32-bit”.
I’m using an i7 860, and yeah, it’s working great. I’m pretty happy with it.
druidThanks for fixing the bug I posted. Though I couldn’t test it, it was reported that 88200Hz has the issue too. Have you fixed it for this as well?
(I ask just in case; it’s quite possible the fix was a general one and doesn’t need to be tweaked for each sample rate. 😛 )
druidNow there’s an awesome solution! Sounds like everyone could win from it, too!
druidArgh, as I thought, Sony don’t have detailed a BIOS reference manual that I can find, nor can I find it on Google.
It’s a bit troublesome, but if you have a digital camera, you could take photos of the different parts and I could help you from there. I’m not sure what else to try, really, as I’m not familiar with all the different names.
I can say though, that you might end up unlucky. Many OEMs like Dell cut down the amount of control people have in the BIOS, and undoubtedly Sony does too.
Usually in BIOS, in motherboards that are purchased outside of OEM, there is a section called “Advanced BIOS” or “Advanced ~” something or other. In there is usually the Aperture Size. But yeah, it’s quite possible you don’t have it. I won’t know unless I can see the BIOS screen myself, since I am unfamiliar with your system.
druidOoh, nasty! 🙂
I asked because I wondered if ASIO4ALL was causing it. I felt stupid asking, because I’m pretty well-versed on computers, but there might have been something I didn’t know about.
Anyway, I’m glad to see you found the problem! I’m looking forward to having the bug fixed!
And I only found out because I was going to bounce an example of vocals so my girlfriend could listen to something I did with them! 😆
druidWhen you start the computer, you can press the delete key (or sometimes it needs F2 or another button) to enter the BIOS setup. Inside there, try not to change anything except the setting that you are looking for, which is often called “AGP Aperture Size”, or something like that. It usually has megabyte settings like 32, 64, 128, and even 256 in some cases. Depending on the BIOS, it might be in various submenus, but it’s in the one that deals with extra peripherals like PCI cards and so forth, and not the CPU.
If you can’t find that, post a response saying so and give me the model of your desktop, and I will see if I can look for a manual that details the BIOS online.
Good luck!