@Zynewave wrote:
- Fix: Minimizing/restoring the Podium application could reopen windows that were previously closed. This happened only on XP and was caused by a change in 2.13.
Curious! I experienced this with 2.13 and at least with 2.14 beta 3 too. I am, however, using Vista!
Ugh… I certainly did not think ahead as far as you did, Conquistador. 😆
However, I didn’t mean to say radically change both the browser and Inspector – just something along the lines of “Oh hey, all my devices are in here, too! But it looks a bit crowded… all those extra folders for parameters and presets… It’d be a waste to have this list and not be able to use it more easily.” – thus I suggested filters.
I guess I didn’t realize it wasn’t meant to be used for selecting VSTs but for project management instead.
I can see both your points, though, but don’t have much to contribute at the moment, so I’ll just give you two (semi-related) bits of information:
1- I prefer dragging my VSTs from the inspector, as the distance is shorter!
2- I actually drag all my audio files over from the Windows explorer. 😳
Well, you’ll know better than anyone if Podium did something different about updating plugin GUIs, maybe.
In any case, don’t worry about it… it’s no biggie. 😉
@Zynewave wrote:
Took me a whole day to trace this bug. One of those bugs that did not occur when running Podium in debugging mode. Please try the new beta3 and let me know if this fixes the problems you have experienced.
Fantastic! Everything crash-related is fine now. 8)
As for the delete key thingy… I’ll let you know, should it creep up again.
@Zynewave wrote:
@thcilnnahoj wrote:
– Filters for the Project browser to view only VST/VSTi + parameters; VST presets; Audio/MIDI sequences; Automation sequences. (If possible to seperate all these)
I can see the use for accessing sequences of different types, but why would you want VST filters when you have that directly in the inspector device panel?
Seen as all the devices are available from the browser anyway, I thought you might as well have the ability to access everything in one place, if you wanted.
– A button for ‘Going up one level’ in the file browser, maybe to the left of the folder icon in the address bar. Like in pre-Vista Windows Explorer.
The space left of the folder icon is used to show the pin icon when files are linked in the current project. But maybe I could implement clicking on a subfolder part in the address bar to go up to that folder. That allows for quickly going more than one step upwards. Sort of like the way the address bar in Vista file explorer behaves, but without the arrow buttons between each subfolder. Good idea?
Great, that’s even better.
Also, I’ve been repeatedly getting Visual C++ Runtime error crashes, likely related to the floating browser window. I’m not able to reproduce them exactly. 😕
When I simply close an arrangement and open another one, I get a crash.
Then, after starting Podium again, it happens with no browser visible, too.You did not get this bug in 2.13 and previous releases, right?
I haven’t experienced this bug myself. If you can reproduce it, please email me your Podium.ini file.
That’s strange… No, it doesn’t happen with 2.13.
It occurs 9/10 times when I switch from one arrangement to another, so not perfectly reproduceable – also with the default setup generated by both 2.13/14.
I see that I’ve got VC++ Redistributables from 2005 and 2008 installed – I don’t see any newer one on the Microsoft site.
So, no one else having this problem? 😕 Just try this please:
Start 2.14 – load default setup – open embedded or floating browser – open the Freebees project (through file menu or browser) – open Song A – open Song B – there’s the crash.
Furthermore, sometimes, when the browser window’s open I become unable to delete sequences in the arrangement by pressing my DEL key.
And you are sure that the arrangement editor has key focus? In other words, can you for example use the cursor keys to navigate in the arrangement editor?
Yes – insert and everything works, just not delete. Switching focus to another panel and back seemed to help.
Floating Inspector! 😯 – didn’t expect that.
Okay, here are some suggestions:
– Filters for the Project browser to view only VST/VSTi + parameters; VST presets; Audio/MIDI sequences; Automation sequences. (If possible to seperate all these)
– A button for ‘Going up one level’ in the file browser, maybe to the left of the folder icon in the address bar. Like in pre-Vista Windows Explorer.
– Double clicking a file during auditioning should stop, not restart from the beginning. Maybe also change the keyboard shortcut (Esc) to Enter/Return for both starting and stopping.
Also, I’ve been repeatedly getting Visual C++ Runtime error crashes, likely related to the floating browser window. I’m not able to reproduce them exactly. 😕
When I simply close an arrangement and open another one, I get a crash.
Then, after starting Podium again, it happens with no browser visible, too.
Furthermore, sometimes, when the browser window’s open I become unable to delete sequences in the arrangement by pressing my DEL key.
While I agree that it does look a bit similar to both Podium and Logic, I must say that I’m disappointed by the looks of this one.
And having seen Kristal too, I’d proclaim the dev not to be the best designer in town. 😕
(Track color bars to the left!? With huge flying shadows, too! 😯 Low contrast on the volume meters in the mixer. Start/Song/Project buttons completely out of place. And all the audio parts in that screenshot have one stray pixel in their bottom right corner!)
On top of that, the whole interface just seems ‘flat’ to me, and those gradients and glossy displays date it excactly to the late 2000’s, where everything has to look like a Mac…
Anyway, we’ll have to see what it’s really packing, feature-wise. Since if you’re willing to shell out what, €400-500? … well, you can get Cubase 5 for almost the same.
I do wish the developer good luck though, seeing that he’s a fellow Austrian. 🙂
[Edit: Just spotted, the pan faders have different colors for L&R – that’s a nice touch.]
You mean on the track header?
That’d be setting ‘Track header color opacity’ to 0% in the Track Region Properties.
Woah, you’re right! 😯
I don’t know if it’s got to do with a threshold, but I just tested and
it immediately crashed as I started playback (Vista 32-bit SP1 with M-Audio USB soundcard).
Don’t worry, I’m sure Frits’ll have it fixed in no time! 8)
No problems here with installer or seperate EXE on Vista Business 32-bit.
I can also run it in all compatibility modes – probably doesn’t say much, though.
I investigated a bit and it seems impossible to change presets only while Voyager’s GUI is visible.
Here’s a link: http://aodix.com/products.html for 1.1, though it still shows up as “Voyager 1.0” in Podium so it’s probably a neglicence of the late developer’s (:() behalf.
It’s all great so far… the only exception being scale highlighting. It gets awfully cluttered when used together with black key highlighting.
Unfortunately, I have no suggestions for improvement to offer right now, other than just don’t use both options at once. 😕