ConquistadorConquistadorConquistadorNice work Malcolm. =D>
ConquistadorYeah that was it Frits the VST plugin path was blank. I did load the default set up (after saving my own) it must have wiped my settings out (as it should). I then loaded a colour set up only, instead of my complete set up, so the VST path remained blank. Good call thanks. 8)
ConquistadorHmmmm…. this is still a problem in the mixer. If you can fence of FX dragging there for 2.22 it would be great.
Tracks in the arranger of course do not have this probelm anymore (thanks) but the mixer does. It can get messy with duplicates easily created. :-k
Conquistador@Zynewave wrote:
@Conquistador wrote:
I think the “Search for missing plugins” command does not work. For some reason nothing happens when I use this command.
Looks broken. Please verify… :-k
Check your VST plugin paths in the preferences. If you have run the beta exe from a folder that has a VSTPlugins subfolder, then that folder may have replaced your normal VSTplugins folder in your Podium.ini.
Ah…ok I’ll double check that thanks.
Conquistador@druid wrote:
Are you sure it’s nothing to do with 64-bit or Windows version? Just checking.
Nah…Podium is flawless on vista x64, it turned out I needed to simply re install Podium. Not had to do that more than twice in 4 or so years. But the last Podium beta or two messed something up on my system I think.
While it may not affect other users PC’s I think it will be safer for me to use another PC when having a look at future Podium Betas. Anyway back a to a bullet proof Podium. Cheers guys. 🙂
Conquistador@Zynewave wrote:
I fixed a critical bug, so I have just released 2.21 a little sooner than planned. The track toolbar didn’t make it into this release.
I really hope it makes it into 2.22. Your initial description of this feature sounds promising. Too early to draw any real conclusion as we have not seen it yet. But if it can simplify track management a bit more in some way or the other it should be a useful addtion to Podium.
This does sound very promising indeed now that I have just read it again… 🙂
“…track toolbar. In the default setup it will sit right below the navigator. I’m considering several new toolbar elements, such as: New track, Marker lane toggle, Tempo lane toggle, global bounce/solo/mute/record buttons, and a new “track filter bar” which will behave similar to the 2.20 editor profile bar.”
The whole Editor Bar style presentation is sooooo efffective.
ConquistadorThanks for the feedback guys. 🙂 At least that confirms the problem is not with the plugins.
I have used these plugs before in Podium and they worked perfectly well that is why I am a bit puzzled as to why they are not working properly now.
It might have something to do with me running the Podium betas on the same machine recently. I think I will uninstall Podium and reinstall. There cannot be anything wrong with the plugins as they are just dll files to copy…so no install necessary.
Hopefully a Podium reinstall will fix the problems. :-k
ConquistadorCheers Frits. A nice UI focused release. 🙂
I think the “Search for missing plugins” command does not work. For some reason nothing happens when I use this command.
Looks broken. Please verify… :-k
Conquistador@Zynewave wrote:
Beta2:
• Added a title bar at the top of the project window. This holds the menu buttons that previously were placed between the inspector and project page tabs.
THANK YOU! 🙂
I always felt the previous UI placement for those menu buttons overlapped other buttons. They look perfectly placed now. 🙂 The auto hide is so subtle but very clever.
• Moved the browser page tab next to the inspector tab. Selecting either the inspector or the browser will automatically hide the other.
Brilliant. Right next to each other and now far more accessible. It may be an idea though to allow for the browser to be moved to the left or right of the Podium UI should a user wish to move it. Samplitude 11’s browser can be dragged to the left edge, top, bottom or right edge of the UI.
I am more than happy where it is in Beta 2 and 3. I think it really simplifies the UI Navigation and highlights the browser much more. But for Liquid project and others who might want to see the browser and the Inspector at the same time an option for them would I am sure be welcomed.
But I love the current placement. 🙂
Podium has such a modern look now. I just wish that setting up drum plugs and using kits was much easier….its so far behind the rest of the UI now. Too far I would say. The drum midi editor needs more UI additions badly. 🙁
Personally I’d love to see the inspector evolve to something like the mixerstrip of the currently selected track (like in logic or ext) and have all the other functionality move to the browser. I feel that studio 1 handled this very nicely. But that’s food for another topic.
Interesting point. Maybe plugins in the browser and the Inspector Group panel for pure track controls including a large meter. I would not mind that!
Conquistador2.20 has been pretty solid here so far. A really nice Podium release. I have probably spent too much time with the Editor bar just sliding the buttons left and right 😛
Great addition thanks! 🙂
Conquistador@Mike G wrote:
Hi,
Quick question.
I’m planning on installing windows 7 64 bit. (soonish)
I checked and my audio device has 64 bit driver support.
Is there any disadvantage to 64 bit that anyone knows of? (Will some plug-ins not work etc.)
Thanks,
Mike G
I have used Vista x64 for well over a year. The biggest problem you would likely have faced is x64 drivers for your audio device. Since you have that already IMO that is pretty much it.
I have installed all my x86 /32bit apps and plugins and they all work on x64 Vista with Podium. Spectrasonics, NI, freebies e.t.c.
Of course YMMV but the audio driver support is the biggie IMO. All 32bit software will run in a sandbox of sorts…a WoW64 layer. Don’t think this will slow your apps to a crawl…far from it here, Podium zips along quite superbly on Vista x64. Totally rock solid and uber responsive.
I would certainly check your plugins for x64 versions in future when Podium goes x64. Devs like Voxengo for instance already have a huge roster of x64 plugs.
You will find that your x86 apps will by default be directed to a “Programs (x86)” folder instead of the normal “Programs”. Thats Windows way of making sure your x86 an x64 apps do not get mixed up. I welcome that frankly. You can still direct any install anywhere you want though. No problem there. Windows 7 may do things differently though but IMO that is unlikely.
@Zynewave wrote:
When Windows 7 is released (est. end of 2009) I’ll probably treat myself to a new PC with Win7 64 bit preinstalled. At that point I’ll start working on a 64 bit version of Podium. Until then I think my time is better spent on working on Podium features.
I pre orderedW7a few weeks ago (its out on the 22nd of OCT.) and found out that the full Retail version of Windows 7 has the x86 and the x64 version on the same disc. Not sure if the upgrade version of W7 from Vista does. :-k
ConquistadorLoving the focus on more UI changes thanks! 🙂
Love the new look buttons. That brings a lovely UI consistency to Podium.
I’m now going to start on the main 2.21 feature, which will be a new track toolbar. In the default setup it will sit right below the navigator. I’m considering several new toolbar elements, such as: New track, Marker lane toggle, Tempo lane toggle, global bounce/solo/mute/record buttons, and a new “track filter bar” which will behave similar to the 2.20 editor profile bar. More about that later
.
Even more goodies on the way 🙂
That “track filter bar” sounds very interesting indeed. Might be the solution to some of the track issues I have had with the hierarchy recently. Guess I need to see it first but its sounds like it could work very well in theory.
If it behaves like the Editor bar then I am really looking forward to it. That was a superb addition to Podium. The toggling of lanes and global buttons for BSMR will be very welcome indeed! 🙂
ConquistadorI understand it now. Thanks for the illustrations aMUSEd 🙂
I think I will highlight these two quotes of yours that I agree with as well.
Maybe it would make more sense to just have (as I suggested long ago) the making a Project something that is done at the start as a “container” for a number of Arrangements (based on that Project template) and that any “save as” refers to Arrangements, not Projects. That would hopefully resolve this long standing confusion.
It might require a lot of work (hopefully not) but either way it sure would be a huge step to simplifying this aspect of Podium.
imho a “save arrangement as” command should place a new Arrangement into the existing Project folder but a “save as” for Projects should create a whole new Project folder along with assigning the Project a name etc. There should ideally also be a dialogue for collecting or duplicating associated media (Reaper has something like that in its save dialogues)
Looking at your images I have to agree with this as well. :-k