Zynewave's Forum Page

I noticed another thing with your project: There is no JamStix device definition object. That means all your JamStix mappings for individual input/output and MIDI channels are separate instances. The device definition is needed to tie together the mappings to one instance. If you are using more than one of these mappings on the tracks, then this can explain the erratic behaviour. I’ve managed to crash JamStix if I use more than one instance.

Try deleting the JamStix mappings folder and reimport the plugin. That should give you the required device definition. Let me know if this changes anything.

Edit: Actually the device definition object is in your project, but is not assigned to the JamStix mappings 😕 Did you create the JamStix mappings manually?

1. The installer will automatically uninstall an older version of Podium, no matter where it is installed. I’m using a simple installer tool with very few customizations to the standard behaviour. I’ve seen too many horror stories with installs/uninstalls that can corrupt a file system if they have been modified to do ‘intelligent’ stuff.

2. Where should this button be placed? Opening the interfaces dialog and pressing OK/enter will reinitialize the drivers.

3. This will probably be implemented at some point.

It is shown as a verification that the application is starting up. It may be a few seconds before the main window is shown. If the splash is not shown during this time, you may think that you didn’t double-click the Podium icon properly and then risk starting up Podium twice.

Another purpose of the splash screen is to show the version number. With the frequent updates, it is good to have confirmation that you are running the latest release.

Is there an option to disable the Startup-SplashScreen?

Is it really that ugly? 😮

Or is there another reason why you want this?

I’ve tried the JamStix demo, with ASIO4ALL. I could run it with a steady CPU reading of ~15%. At one point though, after frantically clicking on various buttons (I had no idea what I was doing), the CPU suddenly went to 100% and stayed in the red. Unloading and reloading the plugin seemed to fix it. I think it happened when I activated the JamStix metronome, but I cannot reproduce it.

Try to adjust some of the options in JamStix and see if the CPU usage is affected. Also try adjusting your ASIO buffer size and see if this affects it.

I’ll download the demo, and try it out in the weekend.

I need to stream the midi-output of Jamstix to a sampler plugin. When will this be available in Podium?

I don’t know when it will be available. It requires some careful planning. It involves additional coding on the engine, which is something I try not to do too often. The engine is by far the most complex part of the application.

It is on the plan, disguised as this item:
MIDI plugin support, either by supporting MFX or supporting the use of VST plugins with MIDI only.