The Telenator's Forum Page

Profile  |  Topics  |  Replies  |  Favorites

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 435 total)
  • in reply to: Restricted to Podium license owners
    The Telenator
    Participant
    This content is restricted to Podium license owners.
    in reply to: Restricted to Podium license owners
    The Telenator
    Participant
    This content is restricted to Podium license owners.
    in reply to: What about the future in Podium? #26594
    The Telenator
    Participant

    Greetings Frits,

    I didn’t mean to suggest that my edition of Podium had become un-workable since the license period had run its course. I was only saying that I like to keep current on any/all of my software licenses. At the moment, there is nothing in the most recent release that I cannot live without.

    For previous feature additions, let me just say that there were indeed some that were wonderful new items. That Mackie capability is a true blessing — among other things I can hit one bank button on my keyboard/control surface and jump up 8 tracks at a time to change their settings. I’ve also noted and appreciated several of the less noticeable upgrades in the last couple of years.

    I fully understand the time constraints you face when it comes to intensive changes that might be made to Podium. If it is any consolation, I am much more critical of certain DAW makers who boast large and skilled dev staffs — virtual armies of people or entire wings of buildings — yet seem almost totally incompetent when it comes to making the simplest of improvements. On a lark, and because they were practically giving the thing away, I bought Mixbus a few months ago. This Harrison Consoles ‘mixer page’ addition/add-on to the open-source Ardour DAW has proved to be a horror story I don’t even like to discuss. Similar, though, could be said of a few of the more established DAW companies, outfits that appear block-headed, obtuse or at least dreadfully slow in satisfying professional and casual users’ needs.

    Whatever the case at present, I have to insist that Podium is truly the most visually attractive DAW of all-time, a true beaut of a creation, and very good and solid at the things it is built to do. I think it still boasts the best-looking and most functional of all MIDI editors out there, also, and if nothing more I still drag files into it whenever I have major editing to do, and I work on them there.

    I hope I was clear about the routing issue(s). Naturally, I have been spoiled rotten through use of Reaper, but beyond that some devs have resolved track inflexibilities in their DAWs by ‘shimming’ in what is sometimes termed a ‘hybrid track’. I thought of this, short of some complete rewrite to much code. Cheers!

    in reply to: What about the future in Podium? #26591
    The Telenator
    Participant

    Greetings adimatis,

    Let me respond to your post and the Time Stretching mention first. I couldn’t agree more with you about the worthiness of this feature. However, it simply wasn’t one of my own requests for Podium — yet I did go along with it as part of our ‘list’ of features. It’s no easy add for any DAW dev, first of all. In fact, if you look at Reaper, you’ll see that they only do it by incorporating various of the elastique algorithms, which are products of zplane. I see other DAWs using same, and I have no idea what the contractual arrangements are, but it most certainly is not free. Those SDKs are all for licensed sale at zplane’s timestretch page.

    Now, I do use Time Stretching when necessary, but I’ve turned to doing it mainly using Melodyne Editor 2, although it works about as well to use Reaper’s elastique choices. This was just an added benefit of buying celemony’s wonderful editor.

    As for the rest, I’ll say I have had to throw my hands up and move on at this point. I’m a realist, and I have had to accept the realities of the situation. Much of this reminds me of my frustration some time ago with Cubase 4 and its horrible version 5 that came after. The very fact that they charged everyone there for version 5.5 — which was essentially only a hotfix for the mess they had created and called Cubase 5 — confirmed their arrogance toward customers to me and was part of what sent me running from that DAW platform. Conversely, what has kept me interested and dedicated to Podium for so long has been the better atmosphere here, including a distinct lack of snobbishness and the non-clique nature of Podium’s users. Also, I still believe in the great potential for Podium, if only it could be brought up to current DAW standards. Lack of a piddly little thing such as Metronome Count-In means I can’t cue musicians to a song start or any punch-ins. It’s like flying blind. Inflexibilities in routings and how instruments and FX can be run together is like being stuck in the last decade.

    in reply to: What about the future in Podium? #26485
    The Telenator
    Participant

    Greetings all,

    So, I’m in a bit of a spot here. My Podium license is up for renewal, don’t really need the Warmverb addition or any of the latest or upcoming changes, but probably would like to keep my license current and active.

    Thing is, we all came together over a year ago and considered just a handful of various features we truly wanted and/or needed. They were maybe 6 or 8 in total. These were both ridiculously small features, such as a Pre-Roll/Count-In added to the metronome, to larger things, such as some users’ request for full Time Stretching and others’ (including me) requesting significantly improved routing abilities.

    Insisting on a couple of measures of ‘click’ before the recording starts may seem like a silly thing, but it makes all the difference in the world between keeping Podium a modern up-to-date professional DAW or having it left in the past.

    And although I fully realise that the routing features (or limitations) are hard-coded deep within Podium’s structure (meaning a much harder thing to fix, certainly), the lack of being able to route MIDI, use MIDI FX, route audio easily from any input or source to any place, and similar, makes Podium unusable for me on at least half of my projects. I’m constantly being rewarded by some red warning notice that I can’t do this or that when I work. Even dropping a few MIDI clips, each in a separate track, below the group head track containing a drum VSTi gets me a red warning on each MIDI track. Yet the whole thing works just fine when I solo and audition each clip into the drum machine. What’s far worse, however, is the red warnings at too many turns when things are simply no-go. Podium is critically limited in track flexibility. If the coding is too hard to change, could a new ‘hybrid’ track be added in to fix this? A third kind of track that will accept anything inserted on it?

    Naturally, like others, I’ve tried numerous workarounds — almost always resulting in a total fail and using up far too much of my time and energy. I’ve gave up on those notions long ago. At present, I am nowadays using Podium solely for its editor screens, both MIDI and audio. They are quite good, so I sometimes work on clips from other DAW projects there before returning them.

    I have always loved Podium and would have liked to keep it as my go-to or only DAW, but the limitations and (for my needs) lack of just a very few modern features have made this impossible in the last year or so. I could easily pass on a request such as time stretching — it was not even a feature I asked for, but the few other things I find indispensable. Grouping and send/returns are a start but still too restrictive. Try running a Sequencer instrument into a VSTi — you can’t have two VSTi work together. You actually get a false statement about “this track processes audio but the other does not” — not actually the real case. Too much of this going on and not enough work being done has made me back off.

    in reply to: Some kinds words in the kvr website would be cool ;) #26289
    The Telenator
    Participant

    DITTO everything tempman said of KVR. The place simply rots, even if there are a total of six or seven regular members who actually KNOW what they are talking about. I’ll admit, I swing by there to get the latest news on upgrades, new releases, soundbanks, etc., but otherwise the place is a wasteland. If you know how to do and read Google Analytics stats, you’ll see that KVR IS a sort of closed club and that the mainstream of DAW and plugin users, both new and pro, largely avoid the place.

    Now, I did see that levendis took a few moments to post a recent good review of Podium. Quite nice. Otherwise, I have come to the opinion lately that you can scream the virtues of some chosen software all you want from the roof tops and, still, the greatest piece of soft gear will often go very ignored. I use a whole bunch of odd-yet-awesome plugins that are not ‘trendy’ enough or perhaps the right brand, and so they are passed up by the general market. They are excellent nonetheless, though … and so it goes. It is others’ loss that they can’t investigate what’s good and available. Podium is a prime example of ‘not hip enough clique-approved KVR software.’

    in reply to: Robert Rif (Slomo) – tragic news #25977
    The Telenator
    Participant

    Sad to hear about Slomo’s passing but thank you for informing us, shaun. I never met him either, but he used to be a regular on various forums and around here. I remember well the article and its excellent title in RedShark News that you mentioned.

    in reply to: Restricted to Podium license owners
    The Telenator
    Participant
    This content is restricted to Podium license owners.
    in reply to: Podium constantly crashing #25058
    The Telenator
    Participant

    Just happened to see your response in my mail as was leaving the net, so thought I should put in another word. Podium is one of those DAWs that does not like to find multiple .dll’s of any plugin. Now, I haven’t tried the renaming trick that will work in some hosts, but I’ll guess it wouldn’t be too keen. So, if you will, let that be a layman response to GetName/String and all that. Some hosts will ‘see’ multiple copies, other will only get the first it reads. Some you can ‘fool’ with naming and such.

    Let me just put it simply: Podium is a very ‘precise’ system. Bet you can feel it. It doesn’t like funny stuff or trick fixes. It’s like you can tell Frits thought through every possible iota of every aspect when putting it together. Operates very precisely and just how it is meant to. DAWs like Reaper will do all sorts of crazy things at times, will run with all manner of files missing or lost, post a complaint message, and then go on running! Podium doesn’t like BS. So, I certainly wouldn’t leave other files and copies belonging to ZASF floating around anywhere Podium might read them. Give it one good version with presets or whatever just where its support folder is supposed to be located, etc.

    Some details, of course, are in the Guide for smooth operation. The Preferences, Audio/MIDI settings are all rather sparse affairs without a lot of extra options/controls, but just make sure everything is set up correctly and the connections, especially, are right. Yes, Podium is one of those DAWs that will want to lock up on you if things aren’t 100%. I have a folder in x86 right near VSTPlugins that I drag plugins and things I don’t want hosts to see — extra copies, altered versions, etc. Hope this helps!

    Yes, it gets everything from its .INI and plugindatabase in Roaming, so, yes, I keep those proper and always make copies of them to store away. I tend to test potentially buggy plugins elsewhere first, too. Must say, once you get the ‘zen’ of Podium it won’t give any further trouble.

    Didn’t know ZASF was open source but did hear a user option to make a DSSI out of it, I guess for Linux use. That did make me wonder. So, hack away!

    in reply to: Podium constantly crashing #25041
    The Telenator
    Participant

    Out of interest in your endeavour and a great curiosity of why I have never at least tested ZASF at some point, I wanted to stop by and see how things are going. I did a quick search myself, and if my info is correct, you should not use any version of ZASF below v2.4.3, as earlier ones were indeed buggy in some hosts, notably trashing the attempts of those brave souls who insist on trying to do serious music on Linux systems and causing other fidgety DAWs such as Ableton to crash. (Not surprised in the slightest to see Live 8 listed among the victims after my year to trying this DAW and seeing numerous plugins crash it!) I’m not 100% confident on that version #, so you might want to look into that as well.
    I also wanted to offer that placing that ms runtime library within the VSTi’s folder should offer no real advantage to your machine over having a copy each in System32 and SysWOW64 (assuming you are on a 64-bit and you’ve given your PC a fresh boot so it can find all goodies such as those). I thought I should also mention that you really ought to have permission from any dev-owner of any software you plan to hack into. Now, don’t expect a hard knock on your door at 3 a.m. to find men in black suits to confront you about your tampering, but it is simply considered a common courtesy, and often devs are more than willing, even sometimes quite interested, to allow whatever project. I haven’t read the licenses, including Podium’s, but can assure it prohibits making changes. I recall in the case involving the day-glo bright red of charming synth Charlatan causing real eye strain that it was only after its owner’s written permission and our promise to then spec it as altered and ‘non-original’ that we opened up that .DLL and switched out the original .PNG files of its GUI. (One version of mine now sports a darker ruby metal flake skin today!)
    On to your other topics, I thought I’d offer that of all the various means outside of ASIO I’ve only made use of Windows Direct Sound and not MME (and WASABI locked up Podium the one time I tried it), and I only used it for a simple mic input a couple of times. If your TASCAM driver is giving you an issue, you could always try the free ASIO4ALL (important: v2.11, beta 1 is the most stable version for most users). Sometimes this ASIO will work considerably better than the native driver included with your hardware.
    As regards your question about the ‘rebuild plugin database’, it is merely one of the few options offered. Interestingly, the few times I have moved a plugin from one sub-folder within my VSTPlugins to another, Podium has caught the change every time, and it changes the file address automatically and will ask me if I wish to SAVE any project I have opened after making the change. [edit: should note that Podium is not like some DAWs that freak out over the slightest change in a plugin’s file address; it is a ‘ relative reader’] I’m explaining this part because your edition of Podium likewise should detect and change and ask to SAVE anytime you move an item. So, this part of your post above I did not understand. Perhaps you moved the plugin to a far different folder that you had not included in the important listing in your Preferences section? In any case, you can change the address yourself in the details box. Podium was built in a former time when users did not add, move or alter plugins nearly every day, unlike today when upgrades and new plugins are being released by the virtual hundreds constantly. I spend a fair portion of my time in this Host making sure my database is accurate and contains what I want to use in projects. I go through all current projects and use only ‘Load Database’ for each after updating plugindatabase.pod in my Roaming folder for Podium. It is the fastest and least painful way (and encourages me to be conservative about making lots of constant plugin changes as well)!
    I have probably missed something else you asked, but this seems a lot for now. Although I have settled on a simple ‘Two-DAW User’ approach to making music, no matter which other DAW I might use, Podium remains a mainstay and one of the two. And although I have always encouraged the addition of my ‘shortlist’ of features to future Podium editions, the simplicity and stability of Podium without a whole bevy of more and newer features is actually rather helpful and refreshing to me. The added features (and therefore the manual lengths) of every other DAW continue to grow by leaps and bounds with every new edition, and it is starting to be a bit too much, if you ask me. Like all DAWs, Podium ‘prefers’ some things set and/or done a certain way. Once these few idiosyncrasies are understood, Podium is a rock-solid and extremely efficient chunk of software. I have had no real issues or crashes in many months now. Best Wishes on your efforts and progress! -Tele

    in reply to: Podium constantly crashing #24988
    The Telenator
    Participant

    I’ve never bothered to search the registry for anything about Podium, but it would be easy, using Zynewave and then Podium in the FIND entry. I suspect there isn’t much in any case. The overall footprint elsewhere is pretty minimal — a folder in Roaming besides the regular file.

    I don’t know about at the moment, but ZASF used to be a very popular instrument, used to get mention quite a lot. Of course, lately, there’s just so much happening and loads of new things all the time. I just remember people having issues with it here and there.

    in reply to: Podium constantly crashing #24985
    The Telenator
    Participant

    Interesting trouble report here. I don’t know if I can solve it, but I can offer a couple of bits. First, if you are using the free version of Podium, you are restricted to using one core on your PC. That’s the main and just about only limitation of the free version. Second, accordingly, if you are attempting to do a substantial project, that limitation can get you into trouble quickly. Third, more important — you need to know that ZASF is a buggy plugin in several DAWs. It’s been a while since I dealt with it, but I think it’s one of the few that is simply a ‘no-go’ in Podium. I think maybe the same in Reaper, but you owe it to yourself to search engine this instrument and read up on it.

    I use Reaper and the licensed version of Podium roughly equally, as both have their many virtues. I would set aside the projects and wipe all trace of Podium files and then start over with a fresh download, just to be double certain the trouble didn’t begin with that. I’ve only had one corrupt dl of anything in my entire life, but it can happen. Podium is more bug and trouble-free than even most releases of Reaper, so it’s very unlikely a DAW issue. There are only a half dozen or so plugins that don’t work in Podium of the more than 200 I’ve tested, but I do think ZASF is one of them.

    Save a copy of your project files and maybe Frits can take a look at them. If it is some other buggy plugin, there is little you can do, whether in Podium or Reaper, besides testing each VST one at a time. But ultimately it is worth knowing. Good Luck with it! Cheers!

    in reply to: System crash #24943
    The Telenator
    Participant

    In case you are still searching for answers, I hadn’t been by the forum much until now and will offer my 2 cents on your problem, as I have experienced something like it long ago in Podium AND other DAWs. First, it must be emphasised that this is not a feature limited to Podium. Locked up drivers occur with all DAWs. Second, I also want to stress that it is almost never the DAW that is at fault — DAWs do not truly ‘lock on’ to ASIO drivers — the other way around might be a more acurate description. I have even seen the quite common result of the driver holding on so stubbornly that, if you open your Task Manage on your PC, you will see what is called a ‘ghost incidence’ of your DAW still supposedly up and running sometimes many minutes after you have closed the true version (or it has crashed). This is an example of what the best of these often dodgy drivers are capable of doing.

    There is more that could be said; however, since drivers, even today, still vary so much in quality and performance, that I must skip some comments. Might I suggest, if this issue continues, that you ‘pull the plug’ literally on your driver by removing the input cord that the driver is connected with, before then closing down the DAW? This is only one of several tricks, but in some cases we learn not to do a lott of ASIO settings changes as well while operating. Try to change things only when you must, and check to see that such changes ‘took’ and all is continuing to operate accordingly. As odd as this sounds, one almost has to treat the ASIO as a badly spoiled child and attempt to be firm with it, almost to the point of ‘training it’ to function as you require. The next step if continued troubles, of course, is to switch to one more reliable.

    Of more that could be discussed, I’ll just end by asking whether you have ever installed and run any audio software that could have damaged or corrupted your sound stack, such as the infamous NCH Software and its products such as SoundTap? If so, I can tell you that I have had to fix a little over a half dozen machines from stupid shims left behind after uninstalls and related corruption. These can seriously interfere with the proper operation of you ASIO and any DAWs you use. If NO, then dismiss the mention. Cheers and best wishes getting things sorted! -Tele

    in reply to: AXP SoftDrive GV – free Marshall Guv'nor VST model #24740
    The Telenator
    Participant

    Your latest creation looks rather interesting Alexander. I saw it somewhere yesterday. Yes, I may try to use it more for light saturation on tracks, because I haven’t been completely happy with some of the plugins made specifically for that purpose. I’ve found that even some of the more expensive ones don’t always sound very good, and a few of the cheapest ones have to be set nearly on full to get any effect at all.

    Glad to see you are still going strong with your very cool plugin line! Cheers! -Tele

    in reply to: Restricted to Podium license owners
    The Telenator
    Participant
    This content is restricted to Podium license owners.
Viewing 15 posts - 1 through 15 (of 435 total)
© 2021 Zynewave