@UncleAge wrote:
The idea that users would pay for additional functionality could keep customers around and not looking over the fence so much. It could also appeal to the “less is more” crowd, as this group would have the option of running things on the lean side with no add-ons, and still knowing that its there if they need to add it in the future. Heck it would take the idea of Projects and Devices to another level.
I don’t know what’s available a this point with Podium and what the future holds. But when I look at Reaktor and the massive library available that goes well beyond the idea of a “soundbank” I’m just left wondering why that approach has not hit the DAW developers. Or has it?
Any thoughts?
If I understand you correctly I think offering a host in parts Midi, Audio or notation that can be plugged in so to speak is a very good idea. I really expected the Ableton Cycling 74 partnership do deliver that sort of approach. Perhaps they will in future.
I think most devs are not sure if the market really wants it (if they have even thought of it yet) but I am certain the market is there.
There are many audio focused producers, midi and a combination of both so I think the plugin feature approach within reason and delivered carefully (with user feedback) could definitely work…even Microsoft appear to be looking at this very same model for Windows 7.
So it is not really far fetched at all.
@Podianer wrote:
Hi there,
I always hated Reaper for its ugliness. But when using themes, it can look very polished. So I bought it a few weeks ago. Reaper is really rich of features, but one thing I like especially is the plugins pack that comes with it.
The good news is, some of them can be downloaded and uses freely. This is a huge addition when combined with Podium. So those people, who do not have the money to buy these “bread and butter” fx, can load them into Podium. I like the quality of these plugins. Especially the ReaXComp is nice. A multiband compressor, which can be very useful when mixing. What do you guys think?
Here is the link:
http://www.cockos.com/reaper/reaplugs/Max
They are a nice set of plugs although I do not really have space for them as I have my ‘go to’ set already. They are certainly one of the best free plugin suites around though. I think Justin surprisingly even keeps the free plugin pack updated as well.
@koolkeys wrote:
In the plugin browser on the left side, I have lots of plugin folders. When I scroll down to folders near the end of the list and expand them(hitting the plus sign), the folder opens but the contents are now below the bottom of the view and I have to scroll to see them.
It can be a bit of a hassle. I would certainly be happier with some sort of smart scroll that could in some way make things easier.
I think Plugin handling in general is way overdue for an overhaul personally. Mappings / plugin management should be far more user friendly.
@Piltdown Man wrote:
Hi,
I’d also love to see an option for MIDI loop-recording to create a new clip on subsequent passes.
I would like to see this in Podium as well.
@Mike G wrote:
Hi,
Couple of suggestions for midi files.
1 –
A “preview midi file” feature for a particular track might be nice when working from within the list pane. (Not drag, play, delete, drag, reset to start, drag, play, etc.)
Nice idea that would be very useful indeed.
Hi Frits,
I am having some stability and reliability issues with 1.98…
A. Crash when using the “Move Effect Track” command.
Steps…
1.Insert at least three FX on any track, even Zynewave FX
2. Use the move command a few times at least but during playback.
On my system here (with a project using about 50% – 60% CPU) it would consistently crash Podium. The whole screen would lock up and even getting the task manager to come up which thankfully is far more aggressive on Vista than on XP, at times would struggle to start up. Once it did I could end Podiums process.
B. Deleting tracks and strange behavior.
If you have an instrument mapping on track it appears you cannot delete the track. Certainly I cannot use the Delete Track command it just does not work but the Eraser tool works.
Also every so often a parameter track gets created randomly when trying to delete a track. Strange. Cannot delete those either unless with the Erase tool.
C. Dragging mappings within a track panel will create a copy. Unless I missed the implementation of drag and drop support within a track panel (in compact mode), I will have to assume this behavior is not as intended?
Track Layout Mode used to replicate all three issues: Compact
OS: Vista SP1 (had the same issues before using SP1)
Can you repro these issues Frits?
Cheers.
@Zynewave wrote:
Even if your final verdict of Nucleum will be that it is better placed in the recycle bin, I do think that the time I’ve spent learning SynthMaker can be valuable for me in the future.
Heh heh, I would not say “recycle bin” 😛 But more of a delivery of Nucleum and other new Zplugs in future through your own Zynewave code.
I can use SM as a prototyping tool for the development of future zPlugins. It’s fast and relatively easy to construct algorithms in SM, and it offers various components that can be used to analyze the audio in realtime. If I some day start development of e.g. a zComp plugin, I would start out in SynthMaker and get the parameters and sound as I want it to be. When done, it would be a simple job to port the algorithm to a natively coded zPlugin
This seems like a much better idea. Synthmaker used as a prototyping tool seems like a better approach especially if as you suggested, you do port the algo to a natively coded plug.
That seems a much better way forward for future plugs.
As a side note…some of the best software available today took a very long time to code…Podium interestingly is a superb example of this. Years in the making before it ever became commercially available but as a result it is an extremely stable host. Every Podium release maintains this very high level of stability.
Sometimes it really is better to give a project more time for a really good or best possible result.
Plugin / Device management problems (as discussed in detail elsewhere) definitely need to be addressed but the stability of Podium remains superb, these are separate things IMO.
Thanks for your comments rinxai 🙂
I certainly did not want my post to be taken the wrong way. I have been a supporter of Podium for years in various ways. Frits surely knows that.
Nucleum is indeed a valid response and a great idea it’s just it’s priority level IMO over mapping issues that for me is wrong. Especially as it too will be subject to problems with automapping.
Indeed it cannot be easy for Frits, with user requests here and there (many of mine in the past) but I think there are times when an issue really should be addressed if it is so obstructive to using a product. Even if a major dev effort is needed over a long time.
But it’s Frits decision at the end of the day, not mine. I will still support Podium here on this forum whatever he decides but cannot recommend it with that problem.
Hi Mike,
@Mike G wrote:
Hi,
I was trying to use track templates accross all projects.
E.g. I want to setup/maintain a vocals template track with certain EQ and Reverb or other plug-ins etc, and use this in all my projects.
Is this possible?
In your current project yes, but IIRC not in any or every project. Frits may know some workaround for this but unless I am mistaken it is not yet possible. Frits will hopefully confirm or deny this if I have got it wrong.
This then beings me to the next part of this post… Ever since I first started using Podium I thought plug-ins being “per project” was a strange (bad) idea.
For example if I move a plug in to a new folder or decide to re-arrange my plug-ins folder, existing projects break.
Another example would be if I add a new plug-in to a global list of plug-ins in Podium, what’s the harm in existing projects seeing that new plug in without me having to tell podium to “Import plug-ins from folder” again?In the very least I would like to have a choice of “Global” and “Per project” plug-in/devices mappings. What do you think?
This is my biggest and maybe only issue with Podium right now. The higher the number of projects you create in Podium the bigger the problem you create if you make changes to your VST folder…OR hardware down the line.
I think the plugin / mapping issue is way over due for a solid solution. I suggested many different ways to address the issue but Frits said he would look at it “post 2.0” which I think is a very bad idea frankly as it could be months from now….or longer.
I started this automapping thread 12 months ago! There are many suggestions to solve the issue there.
If I was reading that thread now as a potential buyer I would not even buy Podium until it was addressed. Outside of that I would buy it in a split second. My usage of Podium is very limited as a result of this issue.
While I appreciate he has development priorities (what dev does not) I cannot see how Nucleum is more important than solving this issue.
It is another plugin so it too will suffer from automapping issues so surely mapping issues should be sorted out first.
Podium is the only host I know with this glaring weakness. Although it only shows up after using it for some time which makes it an extremely frustrating problem to encounter.
Also another minor related point is that using track templates was only available on certain context menus, i.e. When you right-click an existing track, not from the tracks regsion menu or from right-clicking in the area below the tracks. Is there a reason for this?
Not sure about this…perhaps Frits can clarify.
HTH
@ Frits
Sorry Frits I know you have your plans and projections for features but really mapping issues are puzzling me at this point. Podium is so close to being all I would need for many of the projects I create. It is a major problem…12 months old now.
When it is addressed I can start recommending it to people who ask me about Podium but in this state (even with all the great new additions) I cannot honestly recommend it. That would seriously concern me as a dev in your shoes.
It might be tricky to solve (weeks or months of dev time) or easy but it is definitely essential IMO that this issue is resolved. Sorry to have to bring it up again and again but I did not start this thread and the problem keeps coming up again and again.
I can only conclude that for some reason you do not think it is that big a deal. I just don’t get it. Just trying to help make Podium better. >shrug< That is what we all want. 🙂
@kyran wrote:
Synthmaker has an assembler component, which means you can optimize you dsp algorithms at the lowest level.
Interesting. I was not aware of the assembler component or it’s functionality but…
Ofcourse the more you put into low level code the more time it takes to develop.
I guess Frits will have to make a judgement call on how much time he will have to put into it before the level of optimisation is comparable to non Synthmaker plugs.
but if you keep the gui closed I’m certain you can get a very good performance out of them.
Maybe, but I doubt Frits would want to find himself having to provide such a warning for new users to avoid optimization issues that should not be there in the first place.
The performance of a synth is for 80% in it’s dsp code (and the other 20 in stuff like gui’s), and synthmaker allows you to make just as many optimizations as any other way to develop software.
Ok…but it still boils IMO down to how much time Frits has to give to this, to optimize it to an acceptable level or comparable to good quality 3rd party plugs. Just my opinion but I don’t think that is the best use of his time.
Up to him of course. It might work out, it might not.
@Zynewave wrote:
One problem with Synthmaker plugins is that the plugins take a relatively long time to initialize when loaded.
Ok thanks for the detailed response Frits 🙂 but surely that will pose a problem with Synths as well in terms of optimization no?
Admittedly one would use probably 10 times less synths than FX in a project but the optimization issue with Synthmaker plugs is a concern.
FWIW I have a copy of Synthmaker (CM) and love the idea but having read your reply to me and Pigini’s posts I am not sure Nucleum is best offered via SynthMaker.
Some things are simply better if given more time:
Many of the best plugs took time (in some cases a very long time) to code. Having better quality plugs delivered over a longer stretch of time is IMO far better for Podiums perceived image than more plugs over a shorter time of lesser quality. Especially as many are aware of your TC background.
You are clearly capable enough:
The zReverb is an excellent example of your ability to try your hands at your own Zynewave code developed plugs. I rate it as easily as good TC’s Classic Reverb and in terms of tonality / sound /results somewhere between the TC’s Classic Reverb and their Mega Reverb having used all three and compared the plugs sometime ago myself. So you clearly have broad dev. skills.
zSynth:
Why not go for a zSynth at some point in future? Yes it might take 6 months but many high quality synths can take at least 12 months (or more)…but are remembered for years afterwards for their quality. I do not mind waiting over a year or more for a good quality fully optimised zSynth. Maybe spending 5 -10% of your dev time on it might work.
There are many other ways to draw in users *now* Frits, as discussed elsewhere.
So what happens to demo projects?
It would be great to address that issue now but I think Rewire, Automapping (which remains the biggest reason why I simply cannot use Podium as much as I would like to) and other core host features are more important.
I am 99.9 percent certain that while a new user would like to hit play and hear a demo project (as in other hosts), they are far more interested in what they can do with a host themselves with their own plugins for instance… the level of plugin support, VST scanning, playback, general usage, workflow e.t.c are far more important than a demo playing back…(for now at least IMO) when one looks at other areas that Podium can improve on.
Pigini’s points…
If bundling plugins with podium is so important why not cooperate with developers of the best freeware plugins and bundle them?
Like f.e. Claes’ shortcircuit is free now, but he could do with some extra PR for selling his Surge-Synth. http://www.vemberaudio.se
I agree with this as a short term solution or more likely a long term option if it will take so much time to code a very good quality plug. That crucial dev. time can be fed into more core host features. I cannot see how Nucleum is more important than solving Automapping or adding Rewire for instance.
Also some sort of Video support would finally address a long term weakness Podium still has compared to Tracktion, FL and Reaper for instance.
I believe your synthmakers plugins would be as good as synthmaker allows, but still, synthmaker plugins can’t beat the real ones, therefore can never be considered first rate. Even among the custom coded plugins the differences in terms of performance are huge. It really shows when throwing dense scores with lots of controller data at them.
If that is the case as Pigini said, then I seriously doubt Nucleum is best delivered through SynthMaker. Sorry Frits.
I know you mean well with your synthmaker schemes, but reviewers might hold it against you, degrading Podiums overall rating, quickly putting it into the hobbyist-corner because of the “made with synthmaker”-stigma the plugins bear.
Agreed.
Even if it may not be a certainty, as much as I personally really like the Synthmaker idea it is likely to get a not so favorable comparison with other hosts in that area. Interestingly CM Magazine are however very excited about FL’s Synthmaker version but I have no idea how well the SynthMaker optimisation works there. I still do not think it is worth the risk in Podium however IMO.
As I mentioned earlier, I can perfectly understand you need to do something different from time to time, and how interesting constructing plugins with synthmaker can be. Still, I fear it could do more damage than good for Podium.
It’s tough to have to say it especially as it is clearly so much fun for you Frits but I really do agree with Pigini here.
Going forward…
As Pigini suggested I am sure there are devs out there who would be very happy to give their free products some more exposure by bundling them with Podium for demo project playback ‘out of the box’.
@grymmjack wrote:
this host is a work of modern software engineering art.
it’s handling everything i’m throwing at it so far.
i have to ask; what is the catch? there has to be a catch right? no host is flawless. so how do i make the clock strike midnight and make podium take it’s make up off and show me the real female underneath – the one with some flaws but still lovable and beautiful for her flaws.
please help me find this side of podium. i’m in an evaluation period now, and so far i’m really clicking with it, but that scares me because i already have this experience with … well you can see in my sig.
Hi grymmjack,
Well Podium does not fry eggs just yet so you will have to make your own breakfast…sorry 😛
Koolkeys once described Podium as …”polished” I agree. Very well cooked. 🙂
@Zynewave wrote:
@Zynewave wrote:
The next Synthmaker project I’m considering is a drummachine based on sample playback.
Maybe I should rephrase that. I don’t intend to make a drummachine emulation with builtin sequencer. I imagine it to be a simplistic drumkit sampleplayer, that can replace the need for the Drumatic plugin in the current example project.
Even that level of functionality would be great. I would still give it at least one 😯 😛
It would be great to just use Zynewave plugs for Podium demos. Even simple VSTi’s would be a very good start.
I did not think you would go down that route frankly. I guess Synth Maker opens up some very nice options. FL studio 8 has a built in version of Synthmaker (you may already have heard of it) perhaps you might be interested in a Zynewave flavour of some of the 20+ creations here?
There are some really nice efforts on the Synthmaker site.
Would Synthmaker also simplify the development of zplugs for you?
@Zynewave wrote:
Sample import in an FM-synthesis synth?
He He…I was thinking of some of the Logic synths that have an input option (likely sidechain which is possible in Podium) but any how…
I prefer to keep the plugin concept simple. Implementing multiple synthesis techniques in one plugin would complicate the UI considerably. I would prefer to create individual plugins with focus on different synthesis techniques.
That’s fine, seems like a good approach.
The next Synthmaker project I’m considering is a drummachine based on sample playback
😯 😯 😯 ❗