Zynewave's Forum Page
Forum Replies Created
-
ZynewaveKeymasterAbout the new default track options:
They are intended as a quick way to set up a conventional mixer layout, where you have a set of bus sends and effect slots for each audio track. On the audio tracks you then assign VST instruments or place sound events.
The bus send tracks are by default minimized, so you’ll have to show the bus send track strip in the mixer (press H) to show the send dial. The next thing I’m going to work on is extending the headers of the mixer strip so that they show bus send dials and selection of the assigned plugin mapping.
Thinking further ahead, I plan to extend the zPEQ editor so that it will show a miniature EQ graph on the mixer header. A feature also seen in other hosts that have a built-in EQ on each track.
ZynewaveKeymaster- Default track options when creating new arrangement.
- Mixer bug fix.
ZynewaveKeymasterI get that too. When I created the Freebies project I had a single core machine. After I got a dual core machine I found that the LALLAPALLOOZA plugin crashes when used with multiprocessing. Disable the multiprocessing option in the preferences dialog, if you want to work with this plugin.
ZynewaveKeymasterI’ve received reply from Blue Cat. It seems that the next Parametr’EQ release will fix this problem.
ZynewaveKeymasterI think I’ll eventually remove this “relative path” option for plugins. It’s causing too much confusion. Plugin filenames can be configured as relative to a root VST folder (the VST folder you specify at project creation). The idea was that if you moved your entire plugin collection to a different drive or a different folder, you would only need to change the VST root folder in Podium, and the plugins in your projects would then load correctly from the new path. If the plugins are configured with absolute paths, you would need to use the “search” command if you move the plugins.
If the “Relative path” option is grayed out, it means that the plugin file is located outside the VST folder you’ve specified, and thus the filename cannot be relative to this folder.
ZynewaveKeymasterI’ve detected what the problem is, and I have sent an email to Blue Cat.
ZynewaveKeymasterHrmpf, I found a bug in the new mixer code 🙁 . Podium will crash if you delete all tracks in the arrangement. I’ll release a bug fix version in a few days. Let me know quickly if you find other problems.
ZynewaveKeymastera) Add a second relative path option to the Device mapping properties area?
I don’t want to complicate the mapping configuration more than needed.
Regarding the distinction between VST effect and instrument plugins: Some hosts (older Cubase version comes to mind) require that a plugin is classified as an effect, or else it will not be available in some of the UI menus. That’s why you see some instrument plugins come as two .dll versions, one compiled as an instrument and the other as an effect. There is none such UI restriction in Podium.
ZynewaveKeymasterHi,
You add tempo and time signature changes by inserting events on the lane above the tracks timeline:
http://www.zynewave.com/wiki/doku.php?id=guide:arrangement#time_signature_tempo
ZynewaveKeymasterWhen you use the “Import file” command, Podium will log the last folder you browse to, and use that the next time you use the import command. The path is stored in the setup file.
As for the two VST paths; I may add this later on. However I do think it’s less important for Podium than for other hosts, because of the way that you can import plugins from user specified folders. Setting up two paths for VST plugins also poses a problem with the “relative path” option for the plugin filename in the mapping properties. Podium would not know which of the two VST folders it should use to search for the plugins.
ZynewaveKeymasterOpen the list panel with the “List” button at the top right corner (or open a List window with Ctrl+L). Resize the panel so you reveal the file list. From this you can browse for your wave files and then drag them onto the tracks.
ZynewaveKeymaster@Jaegerteam wrote:
The VST-plugin should process MIDI only, not audio.
It should be one of those which “read and write” MIDI data.Ok, this is on the plan. Currently you cannot use MIDI-only VST plugins.
ZynewaveKeymaster- Dockable master chain and bus returns in the mixer.
- Menu for MIDI parameter creation in the inspector parameter panel.
April 17, 2007 at 21:04 in reply to: Restricted to Podium license ownersZynewaveKeymasterThis content is restricted to Podium license owners.ZynewaveKeymasterI don’t understand. Could you describe what you want to do in more detail?