alex's Forum Page

Profile  |  Topics  |  Replies  |  Favorites

Forum Replies Created

Viewing 15 posts - 16 through 30 (of 131 total)
  • in reply to: FRITS, WE NEED YOUR INPUT! #22838
    alex
    Participant

    O.K. I knew some of these questions would be asked 🙂

    Automatic scanning for new plugis is not a problem – that’s what everybody’s doing manually now and I’m convinced that should be solved.

    The other part is trickier:

    @druid wrote:

    Automatic plugin scanning at the start is trickier than it sounds, too, in my opinion. How does Podium know whether a plugin has been updated or not, whether it exists or not, and so on? .

    It knows whether it exists or not because it’s in the VST folder or not :mrgreen:

    But, as The Telenator has already mentioned, Podium will not know If some plugin is the updated version of the old one, sometimes. On the other hand, that’s already the problem, ain’t it? If you want to use a new version of your favorite plugin you’re gonna do it, don’t matter what, aye?

    @druid wrote:

    One problem I have with automatic removal of plugins and so on is in cases where older songs are loaded, and the VST has since been deleted. I have had this occur.

    Why would you delete the plugin that you use (have used) in projects unless you have the newer version?

    What’s possible, for sure, is that if you load the old plugins back, Podium will put them right where they were before, with all your settings, of coarse (I know that works in other software). The other thing I’ve noticed (accidentally) is that if you have two .dll files in your folder(s) that represent the same plugin (that was the same version in my case), Podium will load both of them (maybe it should stay that way(?)). I remember that I’ve read somewhere that the x software, while scanning (when building plugin database for the first time) will, if you have two versions of the same plugin, load the first one and skip the other don’t matter if it’s the newer or the older one (that means it recognizes it’s the same plugin, but doesn’t care).

    I would like that Podium lists only what’s in the VST folder (what kingtubby described), but I am aware of the problems. On the other hand, some of them already exist. Finally, I have to say that I know absolutely nothing about programming, so I can only talk about things I’ve seen in other apps.

    Maybe, Frits has the solution.

    P.S. Another thing that should (and can) be solved – new plugins should be usable in all old projects as soon as they’re loaded.

    Cheers, Alex

    in reply to: With which other DAWs can/should compete Podium? #22821
    alex
    Participant

    Yes, Reaper needs a good amount of tweaking (and knowledge) to be really usable and “comfortable”, if you want to put it that way (and that’s what some people like about it and some don’t), but once you’ve done it, you have the weapon in your hands.

    Now, I’m really sorry to have to say this, but the real question is: can Podium compete any of those DAWs? I know nothing about DAWs listed in OP – I only mix on Reaper (at home), Pro Tools, Cubase and Nuendo in other studios, and I gotta say that if Reaper didn’t exist I would have to buy PT. Can’t say much about MIDI – I only use it because I have to (to make tunes for one of the sellyourmusiconline.com websites). But that’s just a side job. Audio is my thing and that’s what I do. Anyways, I’ve clicked on one of the links and checked the feature list – most (if not all) of the features we discussed repeatedly are there. If Podium had the basic features it still misses, I’m sure none of those DAWs could touch it, but…..

    in reply to: With which other DAWs can/should compete Podium? #22819
    alex
    Participant
    in reply to: Two Problems in Return Section #22814
    alex
    Participant

    @Levendis wrote:

    May I suggest you use a reverb that has ‘stereo width’ control?!

    That’s the best workaround if you want to pan mono reverb under or opposite of the source. Of coarse, you can’t use reverbs that don’t have “width” control.

    The easiest way would be to use mono return and pan that, and the only real workaround for that, if you want to use some of your favorite mono verbs, is to make a copy of the track with all fx, insert that verb and pan that, but there’s that stupid cpu (BTW, I haven’t tried to do that – hopefully the pan knob won’t disappear :lol:).

    But, it’s not so important as long as there’s a workaround(s) – I just wanted to know if it was something about Podium or if it was me, doing something wrong.

    @Levendis wrote:

    Curse you, alex, for burning calories in my brain :clown:

    😆 😆 😆

    in reply to: FRITS, WE NEED YOUR INPUT! #22813
    alex
    Participant

    @Levendis wrote:

    @alex wrote:

    Plugin scan – adding new and removing deleted plugins (from the list) at every launch.

    Preferably, this would be optional behaviour, as the Telenator suggests. I like that Podium loads fast.

    O.K. I didn’t bother to explain this, because I was sure Frits knew what I was talking about.

    No worries, Levendis 🙂 It goes like this:

    Podium should actually only scan for what has changed, meaning, it would only need as much time to load the new plugins as you would need to do it manually, and at the same time it should also remove the deleted plugins from the list (so, that you don’t have to rescan for that). So, unless you change something in your VST folder(s), nothing happens. 😉

    Cheers, Alex

    in reply to: Two Problems in Return Section #22807
    alex
    Participant

    Thanks for explaining this =D> It was driving me nuts :frustrated:

    in reply to: YOUR FEATURE REQUEST LISTS #22804
    alex
    Participant

    @Impulslogik wrote:

    Here are some suggestions which would improve my (and others?) workflow.

    1. drag/drop audio from Browser into plugins which support drag/drop too. Like in ShortCircuit for faster mapping or Imageline Edison and Granite from New Sonic Arts for faster/easier workflow.

    2. Easier export for related audioparts with one click. To clarify my problem here is an example:

    I have a big sample database with drums, hats, snares, loops. I browse with podiums file browser through the files and drag the samples which i like into my arrangement. When i save my projekt podium doesn’t save all the samples in one directory in my project folder. I have to export all the files one by one via the editor – see workflow 😀

    All in all podium is a real powerfull daw but the WORKFLOW could be improved…

    Regards, Impulslogik…

    in reply to: Bottom Line #22803
    alex
    Participant

    @ Impulslogik

    Hi, and welcome to the Forum. Since this thread (basically) is the unannounced bastard child of The Telenator’s YOUR FEATURE REQUESTS LISTS thread, and this is your first post, I’ll move the second part of it there, because I think that’s where it belongs (hope you don’t mind).

    All in all, there’s very few responses, so, this thread failed to show what I thought it would.

    I’ll expand on this later, when I have more time.

    Cheers, Alex

    in reply to: Two Problems in Return Section #22801
    alex
    Participant

    @MLS wrote:

    You’re right, the pan knob is gone! It’s hidden (not grayed out).
    The strange thing is that if I delete and recreate Return manually and insert the plugin (mono), the pan knob is perfectly visible and working.

    That.

    in reply to: Two Problems in Return Section #22799
    alex
    Participant

    Yes, that’s it. Every mono plugin acts that way. I can’t really get what that’s all about. 😕

    in reply to: Two Problems in Return Section #22797
    alex
    Participant

    Tnx for your answer!

    It’s very simple – just create a return for a mono track and choose any mono to mono plugin (it should be reverb, but every mono to mono plugin acts the same way) for return channel.

    That way I get the meter in return channel showing single bar (not both channels) and the pan knob is grayed out.

    in reply to: Two Problems in Return Section #22794
    alex
    Participant

    Hi evb, again! 😆

    Can somebody, please, choose a mono to mono reverb in return channel and tell me if pan is enabled. It only takes a minute.

    Thanks!

    in reply to: Audio editing Problems #22790
    alex
    Participant

    O.K. got it. But, in REAPER you can also use qwerty keyboard if you want to and you will see the keys depressed in real time (which won’t happen in Reason, for example). That’s why I asked.

    in reply to: "CharBooster" Anyone? AXP Is at It Again #22786
    alex
    Participant

    I new you was gonna post about this one (found out about it yesterday) 😀

    Didn’t have much time to play with it, but I like it very much, so far.

    Cheers, Alex

    in reply to: Audio editing Problems #22785
    alex
    Participant

    @The Telenator wrote:

    I’m still a proponent for this feature. A Virtual Keyboard (no, let’s not go the QWERTY keys way — we need some real keys).

    Ain’t it the same thing? You only get to choose whether you want to play it with a mouse or qwerty keyboard.

Viewing 15 posts - 16 through 30 (of 131 total)
© 2021 Zynewave