ZynewaveOpen the properties dialog for the library preset, and use the export button.
ZynewaveMouse clicking in the tracks area is used to select objects or (if not clicking on an object) starting a marquee selection of objects.
Click with the mouse on the timeline to move the play cursor.
ZynewaveArrow keys are used to navigate the focus/selection of events. Use the q/w keys to move between markers, and shift+q/w to move in 1 bar steps.
ZynewaveHi,
I don’t have an Audigy, but based on the names of the MIDI ports you listed, I’d say that the “SB Audigy MIDI IO” must be the external MIDI connection. I also recommend you don’t select the “Microsoft GS Wavetable SW Synth” as this may lock the audio output, causing conflicts with the ASIO driver.
Frits
Zynewave@jcleaver wrote:
Not to hijack this thread, but is there any plans to build the control support to have it be implemented by a definition file, so that it doesn’t necessarily have to be hard-coded in? That way if someone had a different controller one might be able to download a definition file, (or create one) and have support for their control.
My original thought was to expand the parameter object properties with an “action” setting. This would allow configuring any type of MIDI message to start/stop and adjust gain/pan etc. and would be sufficient for supporting e.g. the BCF in standard operating mode (not Mackie emu). However, the additions to the parameter object properties would become too complex in order to allow full support for all the Mackie control features (such as the LCD display).
Later on I may add the “action” setting to allow control surface setups using simpler MIDI controllers.
ZynewavePerhaps I should take some time and detail the BCF2000 equivalent key mappings?
No need. I found some charts in a pdf downloaded from Behringers site.
Zynewavewhy create a function you don’t feel will be used?
Folder objects are used extensively in the devices folder, automatically created by the project creation. When you look at the maps panel in the track inspector, then the “Audio Outputs”, “Busses” etc. are folder objects. The user has the possibility to modify these. Probably the first thing you would need to manually create folders for, would be to organize plugins into folders such as “Effects”/”Instruments” or more elaborate categories. An essential feature if you have a large collection of plugins.
Zynewave1. Will Podium be able to respond to mute/solo buttons?
Yes. Already done.
2. Will the transport bar be able to send cursor-position to the control surface (ie enable the led-display on the control surface to show current position).
Yes. Already done. Can be switched between bar/beat and clock time.
3. Will the jog-wheel function?
Yes, but this is not implemented yet.
are you gonna implement an option to auto-follow the cursor as it plays along the tracks? I heard that a scroll function would be implemented when you drag the cursor to end of window, but will there be auto-follow too?
There is already an “automatic scroll” option in the view menu.
ZynewaveNote that to do this you have to right-click the parent track and choose Hide Tracks in Group. Clicking the + / – on the parent (group) track tidies up the display however the BCF2000 still responds to the automation tracks.
Ctrl+clicking the +/- will do the same as the “Hide Tracks…” menu option.
First, I have noticed that you don’t have to enable record on an automation track to write events to it. Anyone can test this with a mouse or pitch-wheel. Movements on these tracks are written as events even during regular playback.
This is on purpose. You could say that moving faders is like drawing with the pencil in the curve editor. I dislike the Read/Write automation modes that many other hosts use.
I have also noticed that written events cannot be changed, once written, by using the faders. In other words, the fader will just tear out of your hand on its merry way to following the automation curve.
This is because the BCF does not have touch sensitive faders. The following is going into the guide later on:
Having a control surface with touch sensitive motorized faders is an advantage when you work with automation on parameter tracks. If touch sense is not supported, Podium has no way of knowing that the fader is grabbed, and so will send fader movements of any already recorded automation. This can result in motor resistance when you try to move the fader to edit the automation.
This problem could be solved by using the control surface channel record buttons as simulated touch. You would then just hold down the channel record button, which will stop the fader movements, grab the fader to edit the automation, and release the record button to simulate releasing the fader.
ZynewaveMost people will have no need for creating folders. You may want to organize plugins in category folders in the project start page device list. If you have a large number of arrangements and sounds you may also prefer to organize them into folders.
ZynewaveHi Klemperer,
Although there are no replies to Koolkeys post here, I know that a major part of my recent customers have been using the Podium CM version before buying the full version. So I’m probably doing that type of promotion again, although nothing is planned at the moment.
About the steep learning curve: A lot of things have improved since 1.77. I’m on a constant quest to try to simplify the UI workflow without sacrificing the flexibility of the hiearchic track design.
Frits
ZynewaveI’ve started a new chapter in the guide, explaining the Mackie control in detail:
http://www.zynewave.com/wiki/doku.php?id=guide:mackie_control
The “arrangement selection mode” explains why the BCF will not be active before arrangement monitoring is activated. There is a downloadable utility for BCF that simulates the Mackie LCD display, which may be a help when using BCF with Podium.
ZynewaveTo help with the testing, I’ve created a new “Control Surfaces” chapter in the guide:
http://www.zynewave.com/wiki/doku.php?id=guide:control_surfaces
This must be the first time a feature is described in the guide, before it is available in a release 😮
ZynewaveZynewave