Zynewave's Forum Page

@Cris17 wrote:

Hello everybody, my name is Cris and I am a little new to the DAW world and these forums.

Welcome to the forum, Cris.

1) I saw that many people would really like support for midi plugins. An arpeggiator (maybe something like energyxt?) would be highly appreciated. Or even support for one would be wonderful. Is this going to happen soon?

I just made a reply to a similar question:
http://www.zynewave.com/forum/viewtopic.php?t=2850

2) Is there any possibility to implement some basic staff view of the midi notes? I don’t think it would be too complicated. I often write in midi and would like to be able to see the music in notes.

I currently don’t have plans for a staff view. In the distant future I can see myself experimenting with this, but that is years away.

Frits

It’s not on the top of the todo-list, so I can’t say when it will arrive. Sorry about that. I’ve tried to give estimates on these larger features before, but the priorities on the todo-list is often in a state of flux. I work best when I don’t have to rush through a feature implementation road-map.

You select the automation parameter from either the right-click menu, or the parameter panel in the inspector.

In case you haven’t watched any yet, there are a few videos on the Zynewave youtube channel that shows how automation can be used:

http://www.youtube.com/ZynewaveDotCom

@michi_mak wrote:

so what happened to the list with 50+ request you had bookmarked?

I haven’t lost it, if that’s what you’re thinking.

It is not a problem running Podium on ARM processors. I already have Podium running on ARM with the experimental iOS port I did a while back.

What is more problematic is that Microsoft is rumored to only support Metro style apps and not desktop apps, with Windows 8 on ARM based tablets. The new Metro API is called WinRT, which replaces the old Win32 API. With WinRT, Microsoft has understandably chosen to cut out some of the older redundant technology. For example, the Win32 GDI graphics system that Podium uses, is replaced by Direct2D in WinRT. So, I’ll need to implement support for Direct2D in Podium. There are other problem areas, such as with the audio and MIDI support in WinRT, but I’ll just have to deal with them one at a time.

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.

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.

Not yet. I expect to have it fixed for the next release.