LiquidProj3ct's Forum Page

Profile  |  Topics  |  Replies  |  Favorites

Forum Replies Created

Viewing 15 posts - 691 through 705 (of 748 total)
  • in reply to: Preview 2.09: Piano roll editor updates #14027
    LiquidProj3ct
    Participant

    @Pigini wrote:

    @LiquidProj3ct wrote:

    Hi Frits, I’ve trying multiple resizing but, honestly, it’s a little weird.

    1. The minimun note lenght should be the piano roll snap if it’s enabled, and no zero. Usually people don’t use “clicks” sounds! Another related problem: imagine that you have a chord in the start of a clip and it’s reduced to zero, you cannot select it

    But as long as you have not deselected it, you can still change it, the notes still seem to “know” their initial values.
    I noticed with snap enabled, it depends which note you grab and drag.
    Grab the shortest one and it cant get shorter than the snap value.

    @LiquidProj3ct wrote:

    2. Podium forces notes to snap when resizing. This is a BIG problem. If you have some 1/8 notes, and a 1/8 dotted note, if you get longer all them and the snap is in 1/8, the 1/8 notes would be 1/4 notes, and the 1/8 dotted would be 1/4 notes also!!! (when its lenght should be a 1/4+1/16). This also is a problem when you have the notes with a starting quantization, you would lose the quantization!

    Yes, the behaviour with snap enabled works a bit like the absolute option in some other hosts. If you dont want that, you would only have to deselect snap, the visual grid is a good guide to see where you are. The way Frits implemented it makes good use of the snap option when resizing and an additional option for absolute changes is not needed.

    Hey man, instead of dragging multiple notes simultaneously, I can drag them individually also in order to change their lenghts. But that’s not the idea. I think that the idea of interface is make it easy & functional, and those are my suggestions for do it easy and ‘workflowable’.

    Best regards 🙂

    in reply to: 2.08 #14012
    LiquidProj3ct
    Participant

    Frits, it’s me again… i’m the bug-man 😳

    Now I was using Gladiator 2 in Podium. I did two patches for it and I saved the song. Later when I load again the project I discovered that Gladiator 2 didn’t saved it changes!!!!! Then I deleted them.

    I did a new project only with a Gladiator 2, and I discovered that Podium don’t save the “CATEGORY” of gladiator (category = internal preset folder), but this only happens with 2 categories: Vocoder and Pad.

    It’s soooooooooooo weird. I tried to reproduce the bug in FL Studio 8.02 but I couldn’t do it, FL Studio save the project without problems.

    Best regards

    in reply to: Preview 2.09: Piano roll editor updates #14010
    LiquidProj3ct
    Participant

    Hi Frits, I’ve trying multiple resizing but, honestly, it’s a little weird.

    1. The minimun note lenght should be the piano roll snap if it’s enabled, and no zero. Usually people don’t use “clicks” sounds! Another related problem: imagine that you have a chord in the start of a clip and it’s reduced to zero, you cannot select it

    2. Podium forces notes to snap when resizing. This is a BIG problem. If you have some 1/8 notes, and a 1/8 dotted note, if you get longer all them and the snap is in 1/8, the 1/8 notes would be 1/4 notes, and the 1/8 dotted would be 1/4 notes also!!! (when its lenght should be a 1/4+1/16). This also is a problem when you have the notes with a starting quantization, you would lose the quantization!

    Best regards 😉

    in reply to: Preview 2.09: Piano roll editor updates #14000
    LiquidProj3ct
    Participant

    The minimal lenth of notes should be the snap value, if snap if off then leave the note as a simple click sound.

    By example, snap on at 1/16. If you have two notes selected, 1/8 and 1/16 and you get short them, the next step would be 1/16 and 1/16. Now if you want do them longer both notes would be 1/8 and 1/8.

    This is how work in the most host I’ve tried before found Podium.

    in reply to: 2.08 #13994
    LiquidProj3ct
    Participant

    Frits, I’ve tested this bug in Podium 2.08 and 2.09b4. I also downloaded another host, Reaper, in order to check that this wasn’t a Sylenth1 bug.

    I’ve problems with Sylenth1. Just make some chords with a pad sound, loop them, then do (with volume release as example) that Sylenth reach its maximun voices polyphony, and then, mute and unmute the Sylenth track in Podium mixer.

    When you unmute Sylenth1’s track it doesn’t reproduce any sound. If you pause and play the song again, there isn’t any sound either (you can see in Sylenth preview keyboard how MIDI reach Sylenth1). The only way for restore the sound of Sylenth is setting the polyphony to 0 and set again to the desired value.

    I think it’s a Podium bug because I hadn’t any problem in Reaper (muting the Reaper mixer track, and disabling and bypassing Sylenth1 in Reaper).

    Here you’re a .pod Press play and mute/unmute the Sylenth1 mixer track:

    http://www.megaupload.com/es/?d=XF9M5MT2

    Thanks you!

    LiquidProj3ct
    Participant

    Sorry, but I don’t think that we could see the year 3000 😛 . You could simplify a little erasing the two/three first numbers.

    Podium 9.1 instead Podium 2009.1
    Podium 12.4 instead Podium 2012.4

    in reply to: Adjusting default automation value #13937
    LiquidProj3ct
    Participant

    Ok, thanks you! 🙂

    in reply to: Restricted to Podium license owners
    LiquidProj3ct
    Participant
    This content is restricted to Podium license owners.
    in reply to: Restricted to Podium license owners
    LiquidProj3ct
    Participant
    This content is restricted to Podium license owners.
    in reply to: Restricted to Podium license owners
    LiquidProj3ct
    Participant
    This content is restricted to Podium license owners.
    in reply to: Restricted to Podium license owners
    LiquidProj3ct
    Participant
    This content is restricted to Podium license owners.
    in reply to: Restricted to Podium license owners
    LiquidProj3ct
    Participant
    This content is restricted to Podium license owners.
    in reply to: Two problems using Poise (H-man, please read this) #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!

    in reply to: Effect’s on/off switch automation #13833
    LiquidProj3ct
    Participant

    Ok, thx for answer 🙂

    in reply to: Two problems using Poise (H-man, please read this) #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.

Viewing 15 posts - 691 through 705 (of 748 total)
© 2021 Zynewave