LiquidProj3ct's Forum Page

Profile  |  Topics  |  Replies  |  Favorites

Forum Replies Created

Viewing 15 posts - 421 through 435 (of 748 total)
  • in reply to: Preview 2.24: Embedded plugin editors in the rack #17068
    LiquidProj3ct
    Participant

    @Conquistador wrote:

    It seems to only appear when the inspector is dragged as far left as possible (as you both said) but also only when the scroll bar appears.

    That was my missing piece! I was scratching my head because I couldn’t replicate here in home.

    @Conquistador wrote:

    I instinctively clicked on the “No parameters are added to the rack editor” text expecting the Parameter list to show up.

    Me too.

    in reply to: Preview 2.24: Embedded plugin editors in the rack #17062
    LiquidProj3ct
    Participant

    You must reduce inspector width to the minimun. Anyway later I’ll try in my other PC, where I make music, and I’ll confirm. Because in this system is 100% replicable.

    in reply to: Preview 2.24: Embedded plugin editors in the rack #17060
    LiquidProj3ct
    Participant

    @Conquistador wrote:

    Ok (sorry I misunderstood you) 😳 a bug report it is then 😛 🙂

    Funny enough…FWIW I cannot replicate it. I am running a 1900 x 1200 screen here and a font as tiny as the one in your image would be practically indecipherable at 1900 x 1200, so I would definitely notice it if I was able to replicate it here. I just thought I would try the “import plugin” bug you mentioned and I cannot replicate that either. Beta 5.

    It doesn’t matter man 😉 Anyway Podium shouldn’t be in full screen mode. When Podium isn’t maximized is when you can replicate the bug.

    in reply to: Preview 2.24: Embedded plugin editors in the rack #17052
    LiquidProj3ct
    Participant

    If you drag a vst from windows explorer to Devices list, it isn’t imported, which is expected (?). But now you cannot import it with usual “Import plugin…” option from Devices menu until you restart Podium.

    in reply to: Preview 2.24: Embedded plugin editors in the rack #17051
    LiquidProj3ct
    Participant

    No Conquistador, that was a bug report not a feature request. I don’t want those mini fonts! Try to replicate it 🙂

    in reply to: Preview 2.24: Embedded plugin editors in the rack #17049
    LiquidProj3ct
    Participant

    edit: *this is a possible bug, it isnt’ a mockup or FR*

    I don’t know if you’re aware of this mini-font:

    To replicate add a mda DX10 (maybe any plugin), add all parameters and do the inspector the thinnest you can.

    Best regards

    in reply to: Preview 2.24: Embedded plugin editors in the rack #17048
    LiquidProj3ct
    Participant

    @thcilnnahoj wrote:

    The fader wouldn’t have to move over alone, though.

    A tad too extreme? 😛

    Nah! I love fat meters and thin girls! 😆

    edit: btw, are you done with Inspector changes? I’d like to suggest a last thing to Track panel. I find thorny look for a clip in track panel because they’re repeated lots of times, maybe you could avoid this repetition.

    in reply to: Preview 2.24: Embedded plugin editors in the rack #17047
    LiquidProj3ct
    Participant

    @Zynewave wrote:

    There’s a new “Editor” option button in the inspector parameter panel. Selecting this option will show checkboxes in the parameter list, for adding/removing parameters to the rack and mixer embedded editors.

    Glad you finally had done it! Thanks you! Now F4 get sense for me 😛

    @Zynewave wrote:

    That’s exactly the way the EQ looked before 2.24 – you really never used it? 🙂
    I think the new curve display makes more sense, but I’m fine with either.

    No 😳 I only had played a little with it, because I had other VSTs (not free) before met Podium. Now I’m looking for alternatives, I’m getting rid from my old vst collection, and zPEQ is perfect (well except colours for me, but I’ll try to adapt to them).

    in reply to: Preview 2.24: Embedded plugin editors in the rack #17034
    LiquidProj3ct
    Participant

    Before this update I never used zPEQ, now that it’s my default EQ I found something very confusing: the colours. When you mix diferent filters (parametric, LP, BP…) the colours doesn’t help at all: They difficult my vision. If you think this is ok, please consider this small change:

    in reply to: Preview 2.24: Embedded plugin editors in the rack #17027
    LiquidProj3ct
    Participant

    Ok, thx for explanation! I suggest ideas but i ignore all the complexy involved. Do them if ypu consider they’re good and posible 🙂

    in reply to: Preview 2.24: Embedded plugin editors in the rack #17015
    LiquidProj3ct
    Participant

    Good morning. It’s nice the mixer zoom 🙂 I’d like that meters were scaled too, and volume faders keep at the left of each strip when zooming. I consider it more classy.

    in reply to: Preview 2.24: Embedded plugin editors in the rack #17002
    LiquidProj3ct
    Participant

    @thcilnnahoj wrote:

    The embedded parameter lists start out completely blank now…? That’s sure to confuse most people.

    I second that, I spend around five minutes wondering how to use the blank list – maybe I should sleep more 😛

    @thcilnnahoj wrote:

    Plus, as always, going through a list and “ticking” the ones you want is much, much less annoying than opening the same menus again and again for one parameter at a time!

    I was aware about it, that’s the reason of my first mockup in this thread.

    After playing with new beta this evening I couldn’t figure what’s the utility of “automated parameters” in inspector. Why is it show in inspector if you cannot do nothing with it? (and you only can see one simultaneously). This isn’t critical, but I’d rather to see in that place a list of favorites parameter per track, because although we have a list per plugin every track is different and you need tweak different knobs each time.

    Another thing that you could add would be an assignable XY pad, where you can put your two more frecuently parameters per track. It’s something incredibly creative. If you don’t believe it, try to do some sweeps and recordings with zPEQ, and try to do the same with knobs below it. Compare. Now imagine you can do the same with two custom parameters.

    What would be a better solution? Shorten the texts to “” and “[m]”?

    I think that’s ok.

    I hope all this helps 🙂

    in reply to: 2.23 #16997
    LiquidProj3ct
    Participant

    @thcilnnahoj wrote:

    Liquid: If you don’t need the surround mappings, you can disable scanning for them on the new project creation page. You probably already had this option set off before!

    Yes, I just was doing a new template with zPEQ and I saw this. I was thinking that the could be different versions of the same plugin, or maybe surround… didn’t know, then I searched in help and later I asked here.

    Before this las beta release I wasn’t using zPEQ, but now that can be attached to inspector and mixer it’s my default EQ.

    in reply to: 2.23 #16994
    LiquidProj3ct
    Participant

    thx H-man, i was figuring that, but in the zPEQ and zPitch help I couldn’t find anything 🙂

    edit: english mistake, added to

    in reply to: 2.23 #16992
    LiquidProj3ct
    Participant

    Question, what does mean 5.0, 5.1 and 7.1 tags? I see them in zPEQ and zPitch

Viewing 15 posts - 421 through 435 (of 748 total)
© 2021 Zynewave