kingtubbyZynewave wrote:
Could you try to set the VST root folder to a folder with alternative plugins, and see if the scan process can complete with this?
OK, after a bit of trial and error I moved the DR008.dll out of my plugins folder and did a rescan and it seemed to work normally. However after a while all my ram got eaten up…and it froze again – not Podiums fault there. 🙂
I did a scan of a sub-folder of the vst plugins directory and that worked fine.
Regarding the DR008.dll, I can import it using the ‘import plugin’ selection so I don’t know why it won’t work using the ‘import all’ option.
Mart
kingtubbyWhat Windows version are you running, and how much RAM do you have?
WinXP Home, 512mb ram.
What is your VST root folder set to?
It’s on a separate HD at E:vst plugins
Are there any other non-vstplugins dll files in your VST folders?
No.
Do I understand this correctly; Podium always imports the 2 first plugins successfully, but one of the following plugins will fail? What are your 3 first plugins?
I’ve just tried it again and watched it closely. The first plugin it loaded OK; VazPlus. Then while loading the second one; DR008, it froze – though it said ‘2 plugins loaded’.
Could you try to set the VST root folder to a folder with alternative plugins, and see if the scan process can complete with this?
I’ll try that and get back to you.
kingtubby@swayzak wrote:
Tried to start a simple project but can’t seem to set the audio properly to get a sound with a VSTi.
Also check out: http://www.zynewave.com/userfiles/ScamArtist/part1/page1.htm
Mart
kingtubbyThanks for putting in the new shortcut keys. I do a lot midi editing 🙂 and it’s made things a lot easier.
Mart
kingtubbyI’ve tried to recreate this bug, but using eXT 1.3.0 beta (feb 6th), with no success.
Mart
kingtubbyExcellent – Thanks Frits 😀
kingtubby@Zynewave wrote:
How about using the D and F keys to step back and forward between the tools that are available in the editor toolbar? Shift+D/F could then step the quantize value, and C could toggle quantize on/off.
Yeah, that’ll work fine for me. Though currently ‘alt’ toggles the segment tool, it would suit me better if it toggled the rearrange tool. Perhaps others would disagree 🙂
kingtubbyAnother vote for Era 🙂
kingtubbyI’d like to second that 🙂
kingtubbyI’m also trying to use Kubik in Podium. I get brief 100% cpu spikes when changing presets but is OK otherwise. The odd thing I’ve found is that I can’t get midi to trigger the Kubik built in sequencer. All the patches that utilise the Kubik sequencer just remain static, so to speak. Works fine in Energy XT. 😕
Mart
kingtubbyYou could use EnergyXT http://www.xt-hq.com and load it into Podium as a VSTi
It’s easy to layer synths and effects in XT and it does a whole lot more too 8)
kingtubbyI just tried the Imposcar demo in 1.16 and it works fine here – I guess that doesn’t help you much though 😕
Mart
kingtubby@duncanparsons wrote:
For myself, so long as the music is tight within the audio, I slide it until it sits properly.
Well yes, that’s what I do currently. I’d just like the option really.
Mart
kingtubbyI like to use Musiclab SlicyDrummer and FillinDrummer (I’m a bit lazy-haha :)) which are MFX I believe. I currently use them with DR008 which is fine as it is, but I guess I’d like to use them on their own too. I suppose I’m not really desperate for this though – it can wait a bit 😉
Regarding manual latency adjustment, I find that Podium tends to ever so slightly over-compensate when recording my external gear so that recorded parts are slightly ahead of time. Usually it’s not enough to be noticeable, only if it’s a particularly tight sequence or percussion part.
Mart
kingtubby@Zynewave wrote:
Since you are trying to create parameter objects manually, I assume that importing the Vaz did not automatically create a bunch of VST parameters? Maybe it’s because the Vaz does not support this, and relies on MIDI control
The nature of Vaz Mod means that there’s no fixed signal path and the user adds and links the modules, so I guess it makes sense that no parameter information would be sent.
Anyway, I followed your advice and set the parameter properties to ‘midi control change’, CC# to 70 – Actually I tried this before – where I went wrong was forgetting to set the maximum range to 127 – But it works now 🙂
Thanks Frits.
Mart