Zynewave's Forum Page

Profile  |  Topics  |  Replies  |  Favorites

Forum Replies Created

Viewing 15 posts - 1,651 through 1,665 (of 5,966 total)
  • in reply to: Hey Fritz…great job #16940
    Zynewave
    Keymaster

    @Podianer wrote:

    Hi Frits,

    Long time no see.. I hope you are doing well! As Sam I was absent from the forum for a while. Today I took a look at the new version of Podium and I must admit, you really really nailed it this time. The ui changes are beautiful! New releases are always interesting to look at, but gui changes are the most fun part to discover and explore.. 🙂 Podium really looks polished now.. This inspires me and now I want to record something in Podium… Again: Thank you Frits!!

    *off-grabbing-my-guitar* 8)

    Hi Podianer,

    Thanks, and good to hear from you again. I hope you stick around. There are still more UI improvements to come. 8)

    in reply to: Editing SysEx Parameters #16933
    Zynewave
    Keymaster

    @eclairon wrote:

    Once you have defined that parameter object, it will allow you to automate the parameter on a curve track, without worrying about the SysEx message format.

    I am not sure what you mean with the above quote so I will now go peruse the wiki 🙂

    Take a look at this chapter:
    http://www.zynewave.com/wiki/doku.php?id=guide:parameters#system_exclusive_messages

    If you have defined parameter objects for the SysEx part volume messages, then these SysEx messages are handled like any normal MIDI control change message. This means that when you record the SysEx messages, they are not recorded as stream events, but as curve suquences or parameter events with a value dial on them, depending on how you have set the “record as curve sequence…” option in the parameter properties. Then it’s just a matter of editing the curve or adjusting the parameter event dials to set your part levels. Podium will do the SysEx formatting during playback. You will need to do a bit of work to set up the parameter objects, but once done, it will make everything else easier.

    If the configuration of parameter objects seem too complex for your needs, then I can be persuaded to implement simple editing of short SysEx stream events.

    By the way, I could send a midi file if it would help to highlight what I am trying to achieve.

    Please do.

    in reply to: Applying an effect to a specific part of an audiofile #16932
    Zynewave
    Keymaster

    @MelodyMan wrote:

    I have another question. Is there a way to copy a track with just the effect rack and not the audio-events on it?

    Another method that does not involve track templates:

    Select the track you want to copy. Select “Track/Clipboard/Copy Track” (Ctrl+C). Select the destination track. Select “Track/Clipboard/Replace Effect Chain” (Ctrl+Shift+V).

    in reply to: Best way for multiple takes? #16927
    Zynewave
    Keymaster

    You should take a look at the “composite” track option. It’s designed for multi-take recording. Mike G wrote a section in the guide about it:

    http://www.zynewave.com/wiki/doku.php?id=guide:recording#loop-recording_and_composite_tracks

    in reply to: Editing SysEx Parameters #16926
    Zynewave
    Keymaster

    Hi Ron,

    When you record or import SysEx data from midi files, these SysEx messages are stored on the timeline in stream events. As you have discovered, there are currently no way you can edit the contents of the SysEx messages. What the other users are suggesting relate to parameter objects, which can be configured to encode value changes within SysEx messages.

    Can you describe what kind of SysEx messages you are trying to edit? If it is a short message for editing a parameter in your synth, then it may be worthwhile to create a SysEx parameter object. Once you have defined that parameter object, it will allow you to automate the parameter on a curve track, without worrying about the SysEx message format.

    Frits

    in reply to: Extend Podium’s track hierarchy concept #16916
    Zynewave
    Keymaster

    Sorry for not participating in this thread sooner. I have a hard time imagining how this would work. If it is to be a true reversal of the signal flow, then I see lots of conflicts. I guess there should be a group track option called perhaps “reverse signal flow” or “route output to child tracks”. What happens with the audio when it reaches the bottom of the hierarchy? Does it hyperspace up to the group track above the reversed flow track to continue its way up to the master? And what if you have a group track further up the chain which is also reversed?

    A simpler solution would be to have a group track option like “ghost play on child tracks”. This will not do any reversal of the flow, but instead automatically replicate the events placed on the group track on all the lanes of the child tracks. The events on the group track would then be muted of course. The events on the group track would be drawn semi-transparently on the child tracks.

    Zynewave
    Keymaster

    @Mike G wrote:

    -Either an option for bounced tracks to unload their plugins.

    If I understand you correctly, you just need to activate the “unload plugins when bounce” option in the bounce submenu. If your halion player tracks are bounced, then the plugin should never be loaded until you unbounce.

    in reply to: Preview 2.23: Redesigned group panel #16914
    Zynewave
    Keymaster

    @thcilnnahoj wrote:

    Just a tiny nitpick: The left side of the selection frame is overlapped by the line separating the “group level strips.” This can, with some color combinations, lead to an optical illusion that it is only 1 pixel wide on this side instead of two.

    That’s not a line, that’s a drop shadow from the elevated vertical group bar 😛

    About the automation recording issue: It really only works now if there’s no input assigned. Why did you decide against it working with bypassed inputs, like you suggested at first?

    I was unsure of the consequences, and so close to a release, I settled for the unassigned input. I may extend this to include bypassed inputs in a future release.

    in reply to: Podium Releases #16911
    Zynewave
    Keymaster
    • New track chain panel for managing effects, instruments, busses and inputs.
    • Extensive redesign of the track inspector, tracks region and mixer.

    Topic: 2.23

    in reply to: 2.23 #16910
    Zynewave
    Keymaster

    Sorry about the rather undetailed release notes. Podium 2.23 is a huge update of the UI, and somewhere along the way I gave up on keeping a detailed record of every single change. Let me know if I forgot to include something important in the release notes.

    Zynewave
    Keymaster

    Open the timeline ruler region dialog, and deselect the “left-click to slide timeline” option.

    in reply to: Preview 2.23: Redesigned group panel #16905
    Zynewave
    Keymaster

    @thcilnnahoj wrote:

    Also forgot to include this one in the summarized buglist:
    – Something goes wrong when you create a second master group – input/source selectors appear on the master tracks.
    You could assign these things before, even, but I don’t think that’s the point of multiple master groups, is it?

    When you add multiple master tracks, Podium skips the search for a master section, and the master tracks becomes like group tracks. That’s the technical explanation. I may in the future change this, so that each topmost output track is treated like a master track.

    Beta16 is up. This is hopefully the last beta. I’ll spend the rest of the evening testing it, and if nothing comes up, I’ll make a release later tonight.

    Record-enabled audio tracks are now playing, if there is no audio input assigned on the track. That allows for automation recording of effects on the audio track.

    in reply to: Hey Fritz…great job #16903
    Zynewave
    Keymaster

    Thanks.

    in reply to: Preview 2.23: Redesigned group panel #16900
    Zynewave
    Keymaster

    @thcilnnahoj wrote:

    Still in there, I’m afraid (beta 15 default setup):

    I forgot to mention you have to scroll with the mouse-wheel, which lets you scroll downwards infinitely (which is strange in itself, but I’ll save the discussion for another day. :lol:)

    Ok, thanks. I didn’t realize the track should be scrolled to the top.

    A new beta is coming later today. Late last night I found another bug in the mixer: The pan control gets stuck when you have moved it once #-o

    in reply to: Preview 2.23: Redesigned group panel #16893
    Zynewave
    Keymaster

    @LiquidProj3ct wrote:

    When I open a new project and new arragement I must follow these steps for a weird bug:





    This bug-report has finally reached the top of my todo pile. Can you please confirm that you still get the bug with the latest beta, and if so, please email me the project file.

Viewing 15 posts - 1,651 through 1,665 (of 5,966 total)
© 2021 Zynewave