swindus's Forum Page

Profile  |  Topics  |  Replies  |  Favorites

Forum Replies Created

Viewing 15 posts - 46 through 60 (of 187 total)
  • in reply to: Sluggish sliding/scrolling of arrangement #15659
    swindus
    Participant

    No images are used.

    in reply to: Preview 2.19: Optimizations and bug fixes #15597
    swindus
    Participant

    @LiquidProj3ct wrote:

    The problem is with my PCR300 modulation wheel. It sends CC10 to PoiZone or Toxic Biohazard, and their modulation wheel works nice. But in the moment I tweak the mod wheel, the panning of the synth changes!! If CC10 = 1 then I only hear by left channel (or right? I cannot remember) and if CC10=127 then I only hear by right channel (or left?). However the pan fader of the mixer is always centered.

    CC10 is the ‘default’ for pan like CC07 is the ‘default’ for volume. CC01 is normally used for the modulation wheel. I did a test here with Poizone in Podium and Reaper and it pans on CC10. So it looks like a plugin issue. But I think you can reassign the CCs of the plugins.

    in reply to: Preview 2.19: Optimizations and bug fixes #15595
    swindus
    Participant

    @Zynewave wrote:

    • Added “enable recording of VST plugin MIDI output” option to the preferences. This option is by default off.

    Works great here. I have tested it with Drumazon and Nepheton from D16. They support MIDI out since the latest version. Any chance for implementing this?
    http://www.zynewave.com/forum/viewtopic.php?t=1874
    Because the new versions can also sends pattern and instrument names to the host.

    in reply to: 2.18 #15579
    swindus
    Participant

    @Zynewave wrote:

    If you hold the control key when you drop an object, it will be added as a child object of the object you drop on. This works for all object types and not just folder objects.

    Thanks!

    in reply to: 2.18 #15577
    swindus
    Participant

    It is not possible to add a device via drag and drop to an empty folder in the device list on the project page. It is possible if the folder holds at least one item. This makes the reorganization of loaded plugins/devices more complicated as it could be.

    Is there a reason for this? Or is it a bug?

    in reply to: Preview 2.18: New compiler and x64 test version #15486
    swindus
    Participant

    @Zynewave wrote:

    @swindus wrote:

    Its working now, thanks!

    I have a request. The key ‘H’ is used for minimizing and maximizing tracks. Would it be possible to add the command ‘Ctrl’ + ‘H’ for minimizing all tracks and maximizing the selected one?

    Ctrl+H is already used for toggling the “hide track lane” option.

    When you say maximize, do you mean that the selected track should zoom out vertically to fill the entire tracks region?

    No, just to the ‘last’ not minimized state like using H on one track.

    in reply to: Preview 2.18: New compiler and x64 test version #15483
    swindus
    Participant

    Found another graphic quirk. The peaks of audio sequences are not drawn at the beginning in the arrangement. Its the same on imported or bounced audio. As you can see in the sound editor the audio event is complete.

    Just cut a sequence with Ctrl + T and you can see what I mean. The area without peaks at the beginning becomes greater and greater depending on the position of the event on the timeline.

    in reply to: Preview 2.18: New compiler and x64 test version #15482
    swindus
    Participant

    Its working now, thanks!

    I have a request. The key ‘H’ is used for minimizing and maximizing tracks. Would it be possible to add the command ‘Ctrl’ + ‘H’ for minimizing all tracks and maximizing the selected one?

    in reply to: Preview 2.18: New compiler and x64 test version #15480
    swindus
    Participant

    On the way ….

    in reply to: Preview 2.18: New compiler and x64 test version #15476
    swindus
    Participant

    Got some graphic problems with 2.18. Some stripes in the backround in the arrangement and on the project page too. I’m on Vista 32.

    in reply to: Is Midi vst effects support far away? #15402
    swindus
    Participant

    For me MIDI plugs are also more important than time stretching.

    in reply to: 2.16 #15218
    swindus
    Participant

    @Mike G wrote:

    One very minor suggestion, when you click outside the zoom range, I feel the default should be to keep the same vertical position as previously, not to set the top of the zoom range to where you clicked.
    If you did want to scroll the vertical zoom it feels like you should scroll down after clicking.

    Same here.

    in reply to: unable to edit lops or midi #15125
    swindus
    Participant

    @auxlen wrote:

    Hi…totally new to Podium.

    I have the demo and when i drag a wav loop to the track and then double click on the loop it brings up a blank box. previously i could mess with the loop. i also cannot see the piano roll to manually paint in midi. i could when i first played with the app. I obviously have messed something up. 😳

    is there a ‘factory reset’ option or does anyone know what i did?

    There is some kind of ‘factory reset’. Choose ‘Load Default Setup’ from the Setup menu.

    in reply to: 2.15 #15123
    swindus
    Participant

    Great update! 😀

    in reply to: Preview 2.15: New automation system #15114
    swindus
    Participant

    @aMUSEd wrote:

    @swindus wrote:

    MIDI control change != VST automation

    You can record midi controller messages like VST automation. Have a look here:
    http://www.zynewave.com/forum/viewtopic.php?p=12407#12407
    You need to create the cc message first then it works. Would be better if Podium creates a parameter track on incoming cc messages in record mode automatically.

    And there is no mapping between controller messages and VST automation. So a knob controlled by cc messages does not create a VST automation sequence. I think that is what aMUSEd is talking about.

    Oh right – I don’t really understand why if I move it with a mouse it’s VST automation but if I move it with hardware it’s treated so differently. Ideally I’d prefer to use hardware to tweak knobs where possible (many plugins do have built in midi learn on knobs)

    Because MIDI is MIDI and VST automation is VST automation. They are simply two different things. You don’t need a MIDI cable for VST automation and VST automation works without any MIDI devices/setups.

    What is missing here is a mapping between MIDI and VST automation or in other words a MIDI learn function for VST parameters. This has nothing to do with a MIDI learn on a cutoff fader of a VST instrument for example.

Viewing 15 posts - 46 through 60 (of 187 total)
© 2021 Zynewave