Hi dumi,
I just checked the 1.29 demo, and it is not expired on my system. Things you should check:
1/ Check the system time on your PC (double click the clock in the Windows start bar). If it is set to later than May 2005, the Podium demo will think it has expired.
2/ Check that the 1.29 version number is shown in the popup over the Podium icon on the desktop or in the Zynewave program group in the start menu. The previous 1.25 demo version have expired on April 1.
Frits
just a nicety really!
I’ll get to those, when all the necessities has been implemented 😉
Since you’re developing the plugs yourself, would it not be easy just to compile an alternative version without the hasEditor flag?
Note to self: Implement offline bounce for Duncan 😉
The items on the future map is not necessarily listed in order of priority.
It’s a big feature to implement though, so it won’t be here for some months.
Have you considered a Wiki web for documentation and guides?
I have not considered this, but it is a good suggestion. I went to the renoise.com site but could not find links to Wiki documentation. Maybe it’s for registered users only?
I think I still have to write up the basic documentation myself, but a Wiki system could be useful for additional tutorials or whatever.
@Zynewave wrote:
@Zynewave wrote:
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.
The scan will load plugins and immediately unload them. Maybe DR008 doesn’t like to be discarded so quickly 🙂
Actually, ignore that remark. This is what happens when you import the plugin manually as well. I’ll install my old DR008 1.1 demo and check it out.
That was a no go. I’ve had the demo installed a long time ago, so the new installation just pops up with a dialog saying it has expired. I’m afraid I won’t be able to check the DR008 scanning problem for now.
I’ll carry on then. 🙂
On the page referenced, tobybear points out something about the number of programs – could this be what is making Podium hang?
It was. I did not guard against plugins returning a negative number of presets. VST in a nutshell. Fix will be in 1.30. Thanks for notifying me.
So if I want to record sysex stuff live into Podium AND hear it’s effects on the plg cards at the same time, then I have to route the output of the standalone editor to both the plg and Podium simultaneously ?
Yes. If that is a problem, I’ll have to add a ‘SysEx thru’ option, either in the Podium preferences, or in the device mapping properties.
@swayzak wrote:
@Zynewave wrote:
Incidently, I’ve noticed that scrolling in the browser of the project window (on left side) is sometimes a bit erratic – the scroll flickers / oscillates and the list flicks back to the top.
Could you describe how you provoke this behaviour. Are you dragging the slider, clicking the arrow buttons, pressing arrow keys or using mousewheel?
Dragging the slider – it seems as though the slider “wants” to spring back. Weird….
The only way I managed to provoke this, is if I use cursor navigation keys while dragging the slider. Moving the list caret with the keys will scroll the list if the caret is outside the visible area. Could this be what you observed?
PS The “cheque is in the post”… 😉
Got it, thanks 🙂 You’re now a VIP.