Zynewave's Forum Page

Profile  |  Topics  |  Replies  |  Favorites

Forum Replies Created

Viewing 15 posts - 3,151 through 3,165 (of 5,969 total)
  • in reply to: Won’t scan for plugins #11283
    Zynewave
    Keymaster

    Changing the “default vst plugin folder” in preferences does not cause a rescan. Use the “import plugins from folder…” menu command from the device panel on the start page. Select your root VST folder to do a complete scan. If you had plugins that crashed during scan at project creation, they will also crash when doing the import later on. Podium will log the last scanned plugin, and on restart it will notify you of the problematic plugin and put it on a quarantine list. Repeat the scanning until all crashing plugins have been put on the quarantine list.

    in reply to: Preview: Compact track layout #11273
    Zynewave
    Keymaster

    1.95 is released.

    I had a hard time writing the release note. I’m sure there are some new features I’ve forgot to mention. Maybe I just should have written “new and improved” instead of trying to list all the details 😉

    If you find bugs in 1.95, please report them in the release topic.

    in reply to: Podium Releases #11272
    Zynewave
    Keymaster
    • Compact track layout mode.

    Topic: 1.95

    in reply to: Preview: Compact track layout #11270
    Zynewave
    Keymaster

    @Conquistador wrote:

    Yes the warning icon is red but there is little I know of to solve the problem outside of using the “New insert mapping command” and bypassing your advice earlier which clearly would mean there is a problem here.

    If you want to use the plugins without the side chaining feature, then the insert mapping is the simplest solution. Only if you want to use side chaining you need to set up a separate track for the side chain input. Caco gave an example of how to set it up in a post on kvraudio:

    http://www.kvraudio.com/forum/viewtopic.php?p=2748273&#2748273

    in reply to: Preview: Compact track layout #11267
    Zynewave
    Keymaster

    @estwing wrote:

    in compact mode,to speed up selecting the input source would it be possible to have a couple of user definable slots (either audio or midi) under inputs.
    currently recording bass and guitar I am frequently assigning a particular audio input to various tracks, I have to right click,scroll input,scroll to audio,scroll to analog input 4, then left click to select.
    It would be good to make this a faster operation if the particular input could be listed in the first menu.
    thanks, mart.

    The “Input” submenu reflects the device object hierarchy. You can rearrange the inputs in the device list on the start page. If you combine all MIDI and audio inputs into one folder instead of two separate folders you’ll get rid of the input submenus. You can also move the inputs you use most frequently to the top of the folder.

    Also note that you can move an input from track to track by dragging the input object from the track headers.

    in reply to: Preview: Compact track layout #11265
    Zynewave
    Keymaster

    @Conquistador wrote:

    Hi Frits, any progress on the mappings issue I brought up a few posts earlier in this thread…?

    “I can definitely access a GEQ Overtone mapping and a Compressive Pro mapping (both free plugs to download and test) from my Instrument list in B17…”

    I get the same result in B18.

    Perhaps the fact that both plugs appear to need the “New insert Mapping” command (IMO Podium really needs an automatic process to do this like other hosts) to work properly in Podium, might have something to do with these mappings being accessible in the “Instrument” list. Just guessing.

    If they are sidechaining/global plugins, then there is no problem. The problem may be with the “Instrument” menu name. I’ve renamed it back to “Source” to hopefully avoid the confusion. One of the plugin mappings is the “return” from the plugin, so therefore it should be assigned as the bottom source in a track chain.

    in reply to: Preview: Compact track layout #11263
    Zynewave
    Keymaster

    @swindus wrote:

    One thing I have found/don’t understand:

    When I create a new track and check the option ‘Use as group track’ there is no way to add a track to this group track via drag and drop. First I need to create a child track from the track menu in the group track and after that it is possible to add tracks via drag and drop.

    Fixed in the new beta 18. Also fixed a couple of bugs related to the “move track” menu function.

    Tomorrow I’ll do further testing, and if I don’t find any new problems, I’ll probably release 1.95 this weekend.

    Those that are trying the beta, please check that there are no problems with loading and playing your old projects.

    in reply to: Restricted to Podium license owners
    Zynewave
    Keymaster
    This content is restricted to Podium license owners.
    in reply to: Restricted to Podium license owners
    Zynewave
    Keymaster
    This content is restricted to Podium license owners.
    in reply to: Preview: Compact track layout #11253
    Zynewave
    Keymaster

    @kingtubby wrote:

    @kingtubby wrote:

    When right-clicking in an empty space in the track-headers area and selecting ‘new track’, the new track always appears as a child to the track above it. It’s OK in expanded mode as you can change it’s position in the hierarchy, but in compact mode it doesn’t appear possible to move it around or delete it.

    As a supplementary to this, in beta17 all newly created tracks appear like this:

    As I said before, in compact mode it doesn’t appear possible to change the track level so that it feeds in to the master.

    Mart.

    This is because your master track is not defined to be a group track. I’m guessing you have used an old arrangement and converted it to compact mode. If you create a new arrangement Podium will add a “Master” group track to the audio output track. Having this separate master group track also makes it possible to add effects to the master chain.

    in reply to: In my opinion #11249
    Zynewave
    Keymaster

    http://www.zynewave.com/forum/viewtopic.php?t=1459

    It disables the audio mixing option on a track if you add an effect by dropping it on the left edge of the track header. You can either manually reenable audio mixing afterwards, or add an effect by creating a group track first, and then assign the effect mapping to the group track.

    in reply to: Preview: Compact track layout #11246
    Zynewave
    Keymaster

    @Igr0 wrote:

    Beta 16. Not Bug, but not right too:

    When i brows the track menu and get ” presets “, the presets menu window appears over all the next items on this track menu.So i was unable to see others lines of this track menu items.

    I’m not sure I understand you correctly. If you have preset subfolders, then these will unfold over the “load preset file…” etc. commands at the right edge of the main preset menu. You’ll still be able to access the commands though if you avoid resting the mouse over the submenu popups. If the problem is that the preset menu is so big that it won’t fit on the screen to the right of the tracks menu, then the submenu may unfold at the left edge. This is done by Windows and is not something I can control.

    in reply to: Preview: Compact track layout #11245
    Zynewave
    Keymaster

    @Conquistador wrote:

    B16
    1. Right click loss:
    In Expanded (Advanced) mode you cannot add an effect by right clicking. Is this an oversight or deliberate? I ask because it seems very odd to lose functionality going to Expanded mode from the simpler Compact mode. Expanded mode is of course supposed to provide more flexibility and more features exposed to a user, not less. One can of course add an effect to track by right clicking in Compact mode.

    So far “expanded” mode is more like “classic” mode, meaning it works like in previous releases. I’m still considering what to do with the expanded mode. Perhaps the new compact UI will be used in expanded mode as well, and expanded mode will thus be an extension of compact mode with less restrictions on track management.

    2. Strange plugin issues:
    Podium clearly knows the difference between an effect and an instrument mapping but…I can access my Effects (and instruments) from the “Instrument” command and my Instruments (and Effects) from the “Effects” command.

    Are you sure? The “Instruments” menu (previously named “Source”) contains all mappings that produce audio, meaning bus returns appear in this menu as well. The “Effects” menu contains mappings that take audio as input. Some instruments may accept audio input, and will thus appear in the effects menu as well.

    You can insert as many effect tracks as you like, this blank “lane” track or blank mapping holder will still be there. My question is….is it really necessary? Apologies in advance if I have totally misunderstood the obvious here. 🙂

    Apology accepted :P. The line you outlined is not an empty track. It’s the popup line for the lane track. The popup menu is the same as the right click menu on the lane track header. The line serves the dual purpose of displaying what is assigned to the lane track (i.e. instrument and input) as well as a left-click shortcut for displaying the popup menu you also get when right-clicking on the header.

    in reply to: Preview: Compact track layout #11244
    Zynewave
    Keymaster

    @H-man wrote:

    When dragging an effect onto a track (with existing instrument and effects), I noticed that the effect is always placed just above the instrument or at the bottom of the effects chain. I know it is possible to move it afterwards however would it be possible to choose the location in the effect chain when dragging?

    I’ll add drag/drop on the effects chain in a later release.

    in reply to: In my opinion #11241
    Zynewave
    Keymaster

    Sorry about this Sam.

    1.95 has turned out to be a mega update. I’ve stopped adding new features, and will now concentrate on testing and bug fixing.

    From an old email from you, I was under the impression that you had been using one of the 1.95 betas which had fixed the bug you refer to. Maybe I misunderstood you.

Viewing 15 posts - 3,151 through 3,165 (of 5,969 total)