ZynewaveI just changed the ASIO enumeration at Podium startup. This will be available in v0.92 friday/saturday. Maybe this will help with the 44.1 stream error messages as well.
What Windows version are you using? The podium.ini file you sent me seems fine to me. No black screen on my system. Saving the setup file, as you tried with the menu, does not crash either. My best guess is that something with the driver initialization on your system is going wrong. Perhaps the new startup detection wil cure this.
Is there any Quick Start guides or anything? I’m having a hard time figuring this all out, coming from Cubase SX.
I know it’s not much help to you now, but I am currently creating some video tutorials, which I hope will be available in a week.
Just let me know what is confusing. It will help me in learning what areas I need to improve. If you need a quick guide on how to set up an arrangement with plugins, there is this topic.
Frits
ZynewaveHi suges,
Then I went to Settings or whatever it’s called to Save All Settings just for good measure. Then the program crashed.
Did it crash before the ‘Save Complete Setup’ finished? i.e. was pressing ‘Save’ in the file dialog the last thing you did?
I’d like to know what it is that is completely black. Is it the entire main browser window, everyting but the window frame? If you open an Object List window (press Ctrl+L) is this black also? If this is the case, then it’s because the color settings in the setup file somehow have been set to all blacks. Probably due to the crash.
To delete the corrupted setup look here: (if using W2K/XP):
C:Documents and Settings[user]Application DataZynewavePodium
Make a copy of the Podium.ini file and email it to me. There’s a chance I may detect why Podium crashed. Then just delete the Podium.ini file to start up with default settings again.
It should not be necessary to reinstall Podium. Reinstalling Podium will not delete the setup file either.
Podium seems to keep loading the DirectX ASIO driver for my Tascam when it first loads (I can tell because I get the “This is the first time using ASIO Full-Duplex…” message every time)
When Podium starts, it enumerates all available drivers on the system. This is implemented by the ASIO system by loading/unloading each driver to query its capabilities. Many have found this problematic, so I think I have to skip this method and just do a search of the registry for any available drivers. This will unfortunately only tell the name of the driver. Showing how many inputs/outputs, sample rates, etc. that each driver supports will not be possible until you activate a driver.
Don’t hesitate to ask if you run into further problems, I’m up and awake now 😉
Frits
ZynewaveExcellent, proof that Podium actually works 8)
Thanks guys
ZynewaveRegarding the constant overload bug mentioned in the 0.90 release topic:
Thanks to the helpful people at my local music-retailer, I was able to borrow a 828mkII unit. After installation on my Inspiron 8200 I had detected and fixed the bug within 5 minutes. Had I not had the device it could have taken several releases of Podium before I had figured out the cause.
And now a note to any host developers experiencing problems with MOTU ASIO drivers:
If you use the sample rate supplied by the driver in the TimeInfo structure for each ASIO buffer, don’t trust the sample rate is valid even though the flag in the structure indicates that it is valid 😕
The MOTU driver (v3.3) always sets the sample rate to 0.
I was able to set the latency to the lowest setting of 92 samples, but on my 1.7G P4, it was very sensitive at >25% cpu usage and would easily overload. At 256 samples it was ok.
I will release v0.92 on friday/saturday with this fix. Hopefully this will fix the problems reported with Creamware cards as well.
ZynewaveThanks, proffessor. This kind of feedback is helpful for me to know what I should focus on in the development.
It is the smallest zip among all sequencers i have tried.
Thanks for noticing, I’ve spent years on making it this compact :). Seriously; one reason is that I’m currently not including any system dll files in the installer. Typically these are included in installers, just in case they are not present on an endusers customized Windows installation.
What i did not manage to find was the
controllers (parameters). Podium showed to me only 2
controllers while there are more than 100 in battery.
Podium currently only supports MIDI parameters. Support of native VST parameters is on the schedule.
In piano roll view the name of the note (like C1,D1) is not
displayed at all. So you don’t know which octave you are on.
It’s on the list, but I will put a higher priority on it.
1) scripting events.
Another description of this could be ‘meta-parameters’. It’s a good idea, but also of a somewhat complex nature. I have a lot of simpler stuff that I need to implement first, but I will keep this in mind.
3) custom editing rolls
It will be hard to allow the user to freely configure the kind of editor they desire, but with time I may add a further variety of editors, like the guitar or score notation.
Thanks for your input,
Frits
ZynewaveIs it worth making it a sticky?
It sure is, when there is more than one topic in the forum 😛
ZynewaveI do need to put up some sort of indication that something is going on. That should be visible both when loading plugins and getting/setting large presets to plugins. These things could be handled in a background thread, but the main UI thread would still need to be blocked, since plugin and preset management are critical for any further actions.
ZynewaveI did plan on adding this at some point. I think there should be a little more activity here before it is worth creating a separate Music forum. Could you start by creating a topic in the Off Topic forum? When there are more people posting their links, I can move the topics to a new Music forum.
ZynewaveImporting a multioutput plugin in Podium will correctly create mappings for all the available output configurations. With the current VST 2.3 spec there unfortunately is no way to determine if a plugin supports multitimbrality, so Podium does not create separate mappings for the individual MIDI channels. On the future plan is an addition to the Project Wizard plugin panel, where the user can specify whether the imported plugin is multitimbral. If this option is selected then Podium would create the extra MIDI mappings automatically, but it is a dumb thing to implement just because of a flaw in the VST spec.
In the meantime, here’s what you have to do manually:
After importing the plugin, browse to the folder containing the plugin output mappings. Here you should create 16 new mappings set to the 16 MIDI output channels, all referring to the same global plugin instance as the audio mappings but with audio input/output disabled. When you place these on tracks they will not route audio, but only control MIDI on the individual channels. Elsewhere in the arrangement you then place the plugin audio mappings you intend to use. To see an example of how the separate use of audio and MIDI mappings can be used, look at the Drumatic plugin in the freebees example project.
And it’s almost the last thing on my list to figure out
😯 I’m sure we can find something that you need an explanation for 😉
Frits
Zynewaveis there a particular reason for the size limit?
Nah, just a precaution. Loading huge samples (maybe by mistake) can cause long lockups with some plugins, making it appear as if Podium has frozen. I think I will raise it to 128 MB, and hold my breath until someone complains this is not enough 🙂
ZynewaveInstalling a new version of Podium will automatically remove the previous installation.
ZynewaveIf it is a synth plugin, you can use the mute button. If you mean bypass an effect to let audio from sub tracks pass straight thru, then currently there is no way to bypass a mapping. A true track bypass button is on the plan along with a wet/dry setting.
If it is because you want to temporarily listen to the audio without the effect, you can use the ‘Unselect map’ in the track menu, and then use undo/redo. Not a perfect solution though, as the plugin will be unloaded and loaded in memory, which can take some time.
ZynewaveSend them to info@zynewave.com
ZynewaveI will try to implement Cubase script import for 0.92.
Alpha-search is not implemented, but I have just added it to the future plan.
See, that’s the problem with getting this stuff all in the right forums. What starts as a support question often becomes a feature request only after we find it is not already implemented
Discussing things here to see if there are ways to solve a wish/problem is fine by me. When the topic has been understood, and if it’s a complex feature request, it’s extra helpful to me if a user writes a summary in the future forum, like you did with the layered curves topic.
ZynewaveSorry, I was just being lazy. I guess what I wanted to know is what formats you prefer, and do you have your own customized patch files in a specific format?
I found the ‘Script documentation.txt’ file in my Cubase SX demo. I could not find a format description for the cakewalk .ins files, and from what I read on the net, there is no official docs from Cakewalk on this. There were some unofficial hints though.
The Cubase format is the cleanest and easiest to implement, but it does not support definitions for parameters. Cakewalk does this, but it would be a little tougher to implement import of .ins files. Would support for the Cubase format be sufficient for you?