ZynewaveAre you trying to play a note sequence you have placed on the track? If so, does the MIDI indicator (at the right edge of the transport toolbar) light up during playback?
If you email me your project file, I can verify that you have set up your devices properly.
ZynewaveThat does not work
I need more details. Can’t you import the device definition or can’t you make it play when assigned to a track?
ZynewaveHi,
You need to import a device definition that is compatible with your synth. There’s some info here:
http://www.zynewave.com/wiki/doku.php?id=guide:project_start_page#importing_device_definitions
If you can’t find a device definition or cubase patch script file for your instrument, use the “generic multitimbral instrument” definition. This will give you mappings for each MIDI channel.
ZynewaveOpen 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.
When you split or resize the sound events on the tracks, this is done non-destructively. If your sound is used multiple places, you can use the “clone phantom sequence” command to make a unique instance. When it’s unique, you can use the “crop unique sequence” command to trim the sound to the contents shown in the event. When you select the event, you can do destructive waveform editing using the sound editor.
ZynewaveIt’s because the plugin supports multichannel use, so Podium imports it as a global plugin with separate mappings for each stereo input/output. If you want to use it in stereo-only mode, right-click the mapping in the device list, and use the “new insert mapping” command.
ZynewaveThis is indeed an area that could use some shortcuts. I’m going to improve on this as part of the ongoing mixer changes.
ZynewaveZynewaveI think you also mentioned some sort of peak indicator…have you now put aside that idea?
It will come later. Right now I’m working on streamlining the layout of the mixer.
ZynewaveHave you previously started Podium with success, before this error started appearing?
If you have used Podium previously, it could be either a selected MIDI or audio driver that is causing the problem. Try deleting the Podium.ini file:
C:Documents and Settings[user]Application DataZynewavePodium.ini
Zynewave@sam c wrote:
Do you mean 1.85?
Fixed typo. Thanks.
ZynewaveAbout 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.
ZynewaveZynewaveI 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.
ZynewaveI’ve received reply from Blue Cat. It seems that the next Parametr’EQ release will fix this problem.
ZynewaveI 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.