If you enable the “show latency information” option in the mixer, you can verify what your latency is in samples and milliseconds. An ASIO buffer size of 2048 will give a fairly noticeable delay when monitoring direct. It’s also possible that some plugins (typically compressors) add additional latency. If your PC can’t handle lower buffer sizes with ASIO4ALL, then you may get better performance with a dedicated soundcard that has a native ASIO driver.
You could also split the sound event where you want to boost, set up a crossfade by resizing the events so they overlap, and then raise the gain of the new sound event.
I have no intention of letting Podium die. I realize it’s been a while since the last release, but I’ve been busy with another job. I have to do other work to make a living.
I’ve also spent some time with the Windows 8 developer preview, to examine what is needed to make Podium run on that platform. The world is moving fast towards touch-based input on tablet-size form factors, and I want to ensure that Podium will run on those systems as well. That will require a series of updates that I’m preparing, such as an updated project file storage method, and updates to the graphics and audio layer I’m using in Podium. Those updates will take some time and unfortunately does not provide new features, but I find it important that Podium will be able to support all Windows 8 platforms (Intel/Arm) from the day Windows 8 launches.
As far as I can remember, ReWire cannot handle offline (faster than realtime) bounce. Try using realtime bounce recording.
Not yet. I expect to have it fixed for the next release.
You can email your .pod project file to me (info at zynewave.com), and I’ll see if your setup is ok.
Both meters are moving on the tracks and the master
From your description, I take it that your recorded audio files actually contain wave data in both channels (i.e. are there two channels displayed in the waveform display).
If so, then it likely is a problem with the audio output mapping selected on the master track. On project creation, Podium will create both stereo and mono mappings for all the channels you’ve enabled on your audio interface. Open the properties for the main output mapping, and check that the “mixer output” combobox is showing “stereo”.
Only the values of the actual point events are saved in MIDI files. If you use line or spline point automation, you’ll need to convert those to bar points. You can use the “transform to grid aligned points” command (uses the editor grid value), and then “convert to bar points”.
@VanGogh wrote:
One Question I have, on one single Track I can “load” only 1 Midi channel of 16 at once?
Yes.
@VanGogh wrote:
Hi,
so far I’m trying the demo. Is there a possibelity to labeling the event
entries? Appropiate Keys ( enharmonic) flat and sharp is probably difficult to implement?BTW: Cool Software…soon I will buy a licence
VanGogh
Hi,
Your screenshot shows that you’ve found that you can enter labels for the keys on the keyboard through the “Customize Note Map” menu. If you hover the mouse over an event, the label on the keyboard will be highlighted. You can also color code specific key lanes, so that it is easy to associate note events placed on special purpose keys (e.g. keyswitches in samplers). Another option is to select a scale in a tempo event, which will cause the lanes for notes in the scale to be highlighted.
The actual events can’t be labeled. I think it will be too messy to write text on all events.
Hang on, I think I know what you refer to. If it is the drum editor you are working with, then please check the popup help for the “wide event mode” tool button in the drum map editor.
I’m not 100% sure what you mean with “shadow areas”. If your sequence event starts beyond bar 1, then the range before that cannot be edited in the note sequence. You’ll need to add a new sequence event on the track.
I’d also love to have a zComp plugin, but it is not a trivial job to implement one that should rival commercial alternatives. I’d say I need a month to code one I would find acceptable. I spent about two months coding zReverb, for comparison. Currently I’ve put development of additional zPlugins on hold, because I think there are quite a few missing Podium features that are more important.
@The Telenator wrote:
In addition and like I said before, Podium is most likely going to remain my No.1 system from here on out. IF SO, editing and maintaining a guide might not be a that big a deal for me. The stuff you hate is the stuff I’ve done for years — I actually enjoy editing, and it used to be my daytime survival gig between bands and sessions. To do a tech manual well, one really ought to know the product inside and out. Editing out outdated features is one of the easier tasks. If you want a full edit and future updating, maybe I might be willing to trade you for a lifetime of upgrades and a nifty on-screen keyboard? Perhaps something to consider for now.
That sounds like a good deal. No rush though. I think you’ll need a few months with Podium before you can decide whether revising the Podium guide would be worthwhile.
Notice that the installed Podium pdf guide is actually just an export/print of the wiki guide.