Topic: Two problems using Poise (H-man, please read this)

Viewing 11 posts - 1 through 11 (of 11 total)
  • #1779
    LiquidProj3ct
    Participant

    Hello,

    I’m using Podium 2.09b2 and Poise 1.0.9.3 and I’ve two problems.

    1. The first one, using multiple MIDI input and Audio outputs for Poise. Podium related, I think. Look at this picture:

    I want to divide the input clips for a same instance of Poise in two, then it’s more comfortable work with drums, because you don’t need do 34.256 different clips. I tried to create another preset in the Library and assign one preset to Track1 and other to Track2, but same result: the red “!”.

    What am I doing wrong? I attach also the pod file here: http://www.megaupload.com/es/?d=7U6FUWIX

    2. The second one, mainly poise related and no Podium (I think). I noticed that in this new version from yesterday (1.093) Poise don’t load the samples when you close and open again the project in Podium. It gives the error:

    Poise: There was an error while restoring chunk data. (Count not load Pad Data)

    I’m gonna ask about this last problem in the One Small Clue forum also.

    Best regards πŸ™‚

    #13788
    LiquidProj3ct
    Participant

    About the first problem, i don’t know if it’s possible do that in Podium (use two MIDI input for a same plugin).

    About the second problem I get the same error in Reaper (I just downloaded it for test this problem), then is a Poise’s bug.

    #13791
    H-man
    Participant

    Hey there,

    Just got home from work. I’ll have a look at this in a minute.

    Also I saw the post on the Poise support forum on KVR just now so I’ll run some tests and see what I come up with.

    Looks tricky. πŸ˜•

    #13792
    H-man
    Participant

    LP,

    I have been able to use multiple kits accross multiple instances of Poise (1093) by dragging the intstrument repeatedly onto the track lane.

    Note that Podium scans this pluging and creates 16 (midi input) versions however if you open the device settings these have no outputs (or inputs from the mixer).

    I don’t use these as I have grown acustomed to dragging the midi input between tracks.

    Maybe Frits can shed some ligjt on this. I bet it is covered serveral times in the forum somewhere.

    Note that copying and renaming the .dll seems to work as well but it’s not necessary IMO.

    @LiquidProj3ct wrote:

    2. The second one, mainly poise related and no Podium (I think). I noticed that in this new version from yesterday (1.093) Poise don’t load the samples when you close and open again the project in Podium. It gives the error:

    Poise: There was an error while restoring chunk data. (Count not load Pad Data)

    Okay, not getting that one. Regardless of whether I choose to embed the samples in the project file or not, they come back fine when I reload the Podium beta.

    I’ll keep stuffing around. Please post any interesting findings.

    Ben

    #13797
    LiquidProj3ct
    Participant

    @H-man wrote:

    LP,

    LowPass??? πŸ˜›

    @H-man wrote:

    Note that Podium scans this pluging and creates 16 (midi input) versions however if you open the device settings these have no outputs (or inputs from the mixer).

    I don’t use these as I have grown acustomed to dragging the midi input between tracks.

    Maybe Frits can shed some ligjt on this. I bet it is covered serveral times in the forum somewhere.

    Ok, thanks you, i’ll see if I can find something.

    cheers!

    #13826
    thcilnnahoj
    Participant

    I’m not entirely sure I understand what you’re describing :wink:, but here goes:

    With Poise, you can have up to 16 MIDI inputs and 16 stereo-pair audio outputs, no problem. πŸ™‚

    I downloaded your project file and noticed both of the midi tracks you programmed are played through Poise’s first stereo output (Poise (#1) Out 1+2).
    Since you have outputs 3+4 selected on track 4, I guess you wanted to split the outputs of your two MIDI channels – for this you need to assign the correct output channel to whichever drum pads you need to.

    In this picture, I assigned the two samples (hi-hat open & closed) triggered by the MIDI clip on track 2 to Poise’s output pair no. 2. You do this by dragging the ‘control’ I encircled red on Poise’s GUI up/down.

    Right, I hope this helps a little. I don’t know what you mean by “I tried to create another preset in the Library and assign one preset to Track1 and other to Track2“, however, the error you get in your screenshot is normal, since you tried to assign two presets to one plug-in at once!

    Another thing – you can, of course, also place MIDI clips on the tracks Poise outputs audio to.

    About your second problem, it’s probably best to ask Shannon (Poise developer) about that. πŸ˜•
    I can only say I had no such error when loading your project file and the samples you embedded played just fine…

    #13827
    LiquidProj3ct
    Participant

    Thx you thcilnnahoj, but that isn’t my problem.

    About the first problem is that I’d like use the Poise’s multiple inputs (and no outputs) with drums view for each input. In the example I uploaded I want use “the drums view” for both inputs, and no with the piano roll. That’s my problem.

    I’ve talked with Shannon already, and now I’ve a new version of Poise, where the bug is fixed.

    #13829
    Zynewave
    Keymaster

    @LiquidProj3ct wrote:

    About the first problem is that I’d like use the Poise’s multiple inputs (and no outputs) with drums view for each input. In the example I uploaded I want use “the drums view” for both inputs, and no with the piano roll. That’s my problem.

    The ! error appears because you have two tracks with a library preset assigned. That can lead to possible conflicts, since the plugin current settings then would be stored twice. You can solve it by creating a drum kit preset that is not a library preset. This requires some manual setup of the preset objects. You can see how this works with the “Kit Template” Drumatic preset in the Freebees example project. This setup is a bit complex, so it is not a solution that I can recommend.

    Another possibly simpler solution can be used if you don’t need to send the two drum tracks to separate Poise MIDI inputs: Select the Poise (#1)(01) track and activate “use as group track”. Now you can create any number of child tracks which all will use the drum editor, but they will all play into the (01) input.

    I’m not happy with the current method of setting up drum maps in Podium, so that is something I’m going to revise in a later update. I’m thinking about a solution where you don’t have to have the drum kit preset assigned to a track to activate the drum map editor on that track.

    I’ve talked with Shannon already, and now I’ve a new version of Poise, where the bug is fixed.

    Is that the bug where changes in the plugin is not saved when doing a save project in Podium?

    #13830
    swindus
    Participant

    @Zynewave wrote:

    I’m not happy with the current method of setting up drum maps in Podium, so that is something I’m going to revise in a later update. I’m thinking about a solution where you don’t have to have the drum kit preset assigned to a track to activate the drum map editor on that track.

    Looking forward to it. I also have problems using drum map presets on multi out instruments. For example: when I assign a drum map preset to the first output (#1) Out1 of a multi instrument the drum map is not used in the sequence editor on (#1) Out2 and so on, just the piano roll is used. And it is not possible to assign the same preset to the additional outs. So I assume the preset it assigned to tracks/sources and not to the plugin instance.

    #13834
    LiquidProj3ct
    Participant

    @Zynewave wrote:

    Another possibly simpler solution can be used if you don’t need to send the two drum tracks to separate Poise MIDI inputs: Select the Poise (#1)(01) track and activate “use as group track”. Now you can create any number of child tracks which all will use the drum editor, but they will all play into the (01) input.

    That’s right for me, thanks you a lot man πŸ™‚

    @Zynewave wrote:

    I’m not happy with the current method of setting up drum maps in Podium, so that is something I’m going to revise in a later update. I’m thinking about a solution where you don’t have to have the drum kit preset assigned to a track to activate the drum map editor on that track.

    I’d be more easy for newbie people as me… a simple right click in track and “Track as drumtrack” with the ability for add/remove/rename keys or whatever similar would be wonderful.

    @Zynewave wrote:

    Is that the bug where changes in the plugin is not saved when doing a save project in Podium?

    Yes, it was. Now I can load the samples in pads and I can save the plugin changes. Marvelous support!

    #13850
    H-man
    Participant

    @LiquidProj3ct wrote:

    @Zynewave wrote:

    Is that the bug where changes in the plugin is not saved when doing a save project in Podium?

    Yes, it was. Now I can load the samples in pads and I can save the plugin changes. Marvelous support!

    Well, there you go …happening here too now?!?

    Off to email Shannon.

Viewing 11 posts - 1 through 11 (of 11 total)
  • You must be logged in to reply to this topic.
Β© 2021 Zynewave