Zynewave's Forum Page

Hi,

– instead of rotary control in mixer view you could use sliders

I will add this to the list.

– a button for bypassing plugins

Already on the list. But I will put a higher priority on it. Many have asked about this.

a transport bar in audio editor

There are two sound editor profiles in the default setup. If you open a sound from within an arrangement, there is no transport bar in the new window, as the sound is linked to the arrangement transport bar. If you enter a sound from the browser page, you will get a sound editor with a transport bar. If you desire a transport bar in the window opened from within the arrangement, you can insert it yourself by opening the Profile Properties dialog in the View menu. You should then insert a new toolbar region at the bottom of the list.

– objects in arrangement window can be reduced/enlarged by mouse on left/right (like in cubase)

There already is a minimize/restore button (the rightmost button in the track header) and you can zoom the height of an individual track by using the zoom tool and drag up/down on the track header. Did you have something else in mind?

– in piano roll view there’s no indication on what you’re editing : you could add an info box with position length note and velocity for example – and the keyboard is inactive

Already on the list. When you say keyboard I assume you mean the on screen piano roll in the editor. Clicking on this will select all events on that key. Note audition is on the plan.

– in piano roll too you could add the possibility to edit multiple notes (length,heigth,velocity) at a time by selecting the one you want

So if several events are selected then dragging the length of one of the events would change the length of the other events?

i wish i was clear enough

I think I understood you ok. 🙂

Frits

Import plugins is pretty smooth, however I would request an option to import an entire directory and its subdirectories, since all of my VSTi’s are organized into directories (so that they’ll be more organized in Steinberg products).

I have just added it to the future plan.

I’m not sure why I wouldn’t want to create a master track without bounce, all projects need to go to a mixdown wave sooner or later (I think?).

Some users may want to work with MIDI devices only.

Clicked Map. Chose Hypersonic 1+2. A red exclamation mark showed up. An error message about missing parent track mappings to handle audio which means nothing to me right now…

Ok, the problem is that your new track is on the same level as the master output. Use the ‘increase group level’ menu to make it feed into the master track. The master track should always be the topmost track. I just noticed there is a bug when clicking the ‘Insert new track’ menu in the area below the tracks. It does not insert the track at the bottom but rather before the currently selected track. Will fix this. I will also implement that the default group level for new tracks will be set so they are feeding to the master track.

Went back to Map and right-clicked Hypersonic to get the properties. Clicked Device is an instrument. Clicked Stereo from source and traget channels drop-downs.

It should not be necessary to go into the properties for the device mappings. These are for configuring the setup of the plugin/external device, and they should be set automatically by the import. If not set correctly, it’s likely to be a bug in Podium (with the exception of buggy plugins that supplies wrong info to Podium).

I hope that “user case scenario” helped you a bit

Great help! Thanks
Frits

I 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

Excellent, proof that Podium actually works 8)

Thanks guys

Thanks, 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

I 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.

Importing 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