A-ha!
I can now change Podiums Processor Affinity settings.
It turns out it was a Compatibility setting for Podium that kept blocking the Affinity access. Not compatibility with Vista (of course Podium supports that and has done for some time now) but a Priviledge Level setting on that same page.
I had that option ticked. Why? If you install a plugin on Vista and attempt to activate it, if the host is not running As an administrator you cannot register/ activate the plugin.
To save me having to do that each time I simply leave the option ticked when running my audio apps. It is totally harmless and might even help some plugs run properly.
In any case it is not essential beyond assisting with plugin activation and that clearly was the problem blocking Affinity access. I switched back to my Echo box drivers (just tried an Edirol UA-25 with Vista drivers) and it still allowed me to access the Affinity settings. So it was not drivers but it did look that way.
I have reduced the cores to one for Podium but if I click on the screen when Podium loads a project, the screen still shifts left, for a few seconds.
Still no access to it at all Frits. I followed your advice to the letter.
I can see the Set Affinity… command (not grayed out) but I do not even get to the processor screen I posted earlier.
I get this instead after the Set Affinity… command is clicked.
I have another audio interface and I am installing the Vista driver for it now. This is all happening on Vista x86/32. That should confirm or deny the driver theory you suggested. As it affects other audio hosts, it is something to do with audio in some way but lets see if the other interface I have makes any difference…
Really strange… I cannot change Affinity settings for Podium on Vista x86 either. Are you sure I should be able to do this without an additional step somewhere?
Excellent thanks. 🙂
Super fast Frits! Thanks!
@LiquidProj3ct wrote:
Honestly, thanks you! 🙂
Now I can leave my glasses in the car 😛
😛
Thanks for the additional info.
@Zynewave wrote:
Podium is hiding the window titlebar to save some valuable space that can be better used to show additional tracks etc. Other applications are doing something similar. I believe Tracktion also has done away with the standard window titlebar.
Yes I think Tracktion does indeed not use Windows title bar.
Something you could try:
When Podium is launched, open the task manager, right-click the Podium.exe on the processes page, select “set affinity” and reduce the number of enabled CPUs to only one. Let me know if you still experience problems even when only running on one CPU core
For some reason I am not getting access to this option. I can see it. I click on it…and I then get an error “Unable to Access or Set Process Affinity”
I thought it might be due to the OS. x64 here so maybe because Podium is not a native x64 app it will not let me change the Affinity settings.?!?!?
Reason Adapted had a similar problem (did a quick check) but some other apps (x86 versions on x64)) did not have this issue and I get access to their Affinity settings easily.
I will try again on x86 Vista.
Exactly its that “comfortable” size I’m looking for. 🙂 If there is a way to simplify midi editing even further then this FR is definitely one of them. 8)
Please I really need two or three levels more of vertical zoom in the piano roll, it’s difficult for me see the notes with big screen resolutions, I need see the notes more bigger
Thx!
I was thinking the exact same thing today! 🙂 Totally agree.
@Zynewave wrote:
I’ve seen the “not responding” message before, but that is only when there is a bug that causes Podium to freeze completely (an endless loop in the code, not a crash).
Hmmm could be something more serious then.
How many seconds does it take during Podium startup before the not responding message appears?
It depends. It is intermittent but if you click anywere on the screen as Podium loads a project, it can take about two seconds or so then it appears.
And does the screen return to normal when Podium is finally ready after startup?
Yes once a project has fully loaded the screen returns to normal.
It is the Windows OS that appends the “not responding” text in the title bar. The Podium maximized state hides all window borders and the window title bar (unlike other applications), so that is why the screen shifts when the Windows OS forces the window title to be visible.
Thanks for clarifying that…so there is a reason for this behaviour. This brings me to another question though… why is it that Podium is doing something (at least in this area) “unlike other applications”?
It seems to be something under Podiums hood (which is way over my head just guessing here) but if Podium is doing somehting it probably should not, then should this behaviour not be changed as Windows clearly is clashing with Podium in some way or another. It also explains why the other apps I have did not exhibit this graphical shift.
If you restore the Podium main window so that the window frame is visible, you won’t see the shift when the “not responding” message is appended to the title.
Yeah so far I have not seen it following your suggestion, but I would not use Podium that way.
Thanks for answering the q’s. I was beggining to wonder if my internet security package was causing the issue. The shifting seems to stop if
a. No internet usage is active or available.
b. No firewall or antivirus is active
c. If no Task manager is visible.
Problem is, somehow I cannot use Podium the way many here appear to, while accessing the internet.
I generally will shut everything down for serious work (as many here likely do) but even with that at times I have seen some shifting of the screen while working on a project.
What model is your CPU?
Processor Intel(R) Core(TM)2 Quad CPU @ 2.40GHz, 2403 Mhz,
4 Core(s)
4 Logical Processor(s)
If you need more info I can simply click on one of those tabs to get another screen shot up.
Its a nice little free app (if you do not already know of it) CPU -Z
Their home page.
There is even one for video cards called GPU-Z
@Zynewave wrote:
What action were you doing to cause the crash?
I think it was simply bypassing an effect or two. As the template I am setting up has some bypassed effects. It did not happen again after re starting Podium though.
Podium has some kind of warning pop up message should that not have popped up?
Thanks!
However I would suggest a more flexible process though that allows a user to choose the tracks they want to move to a new group. The suggestion you put forward works if all the tracks underneath the selected track are the tracks you want in the group. But it is not so good if any one of the tracks below a selected track are not supposed to be moved.
Being able to pre select more than one track then using a Move to Group track command for instance would be much better.
…just thought it was worth a mention. 8)
This was not of any real importance to me. I was just trying to help. Thought the info might be useful.
I was creating a template in Podium beyond that I am not sure what else you would like to know.
It might be a good idea to have a list of a few things you want to know if there is a crash in Podium or indeed any support related post.
OS
Podium version
Offline or online usage
e.t.c
Maybe even make it a sticky.
HTH
Does it happen when Podium is in full screen mode, too?
Yep.
Or do you, by any chance, remember around which Podium version it first appeared?
Pre 2.07 for sure.
Maybe Frits could send you a few older ones for testing.
Funnily enough I have many older builds but I simply don’t have the time for testing older builds frankly. I think the issue is best resolved looking at the current build.
Sorry I can’t be of much help… if anything, I’d say you could try out some newer and older drivers for your graphics card.
Whadddaya know Nvidia released a driver update today 08.01.09(8800GT here)…downloading now… Nvidia may be reading this thread >tee hee< :wink: I don’t think I will try an older driver…graphics driver support can be iffy but I prefer new drivers to old personally, although driver support is not that straightforward.
In any case I don’t think it’s a graphic driver issue as Podium is the only app that has the problem here. I’ll see what happens with the new driver.
It’d be great if you could try on a different PC, though.
Worth a try…
Cheers 🙂