Topic: Need help please with GUI / graphics issues…thanks…

Viewing 8 posts - 16 through 23 (of 23 total)
  • #13678
    Zynewave
    Keymaster

    @Conquistador wrote:

    However…I could not access Affinity settings for any audio hosts I have…Project 5, Sonar..CD Architecht e.t.c

    Can’t you open the dialog, or are the CPU check boxes just grayed out?

    Maybe it has something to do with the audio/MIDI driver that you use in your hosts. Does it change anything if you disable all MIDI/audio drivers in Podium and then restart Podium?

    #13679
    Conquistador
    Participant

    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…

    #13682
    Conquistador
    Participant

    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.

    #13684
    Zynewave
    Keymaster

    @Conquistador wrote:

    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.

    I was expecting that. I was thinking more about the problems you have with plugin editors, when I suggested limiting the cores to 1. Let me know if this has changed anything.

    #13686
    Conquistador
    Participant

    Made the changes and loaded a project…the shifting appears on one CPU and on four.

    If you use the freebie Spitfish you can see this behaviour quite easily (hopefully anyway). Simply holding down a knob and moving it around for a few sconds will cause Podiums screen to shift. Of course if one was to automate another plug for instance (cut offf on a synth) you would be holding that parameter knob much longer than a few seconds.

    It is less frequent with plugs like RMX but Spitfish shows it up quite quickly.

    Podiums CPU meter was around 70. Latency 512. One core.

    I reproduced the same shifting on four cores with a latency setting of 256.

    #13689
    Zynewave
    Keymaster

    @Conquistador wrote:

    If you use the freebie Spitfish you can see this behaviour quite easily (hopefully anyway). Simply holding down a knob and moving it around for a few sconds will cause Podiums screen to shift. Of course if one was to automate another plug for instance (cut offf on a synth) you would be holding that parameter knob much longer than a few seconds.

    I downloaded Spitfish. This plugin unfortunately does not implement the proper method for keeping the host UI alive when you click and hold one of its controls. This means that e.g. the Podium play cursor stops moving as long as you hold the control. But I do not get the “not responding” message. I can click and hold the Spitfish control forever without seeing this message. I am puzzled why you get this not responding message.

    #13693
    Conquistador
    Participant

    @Zynewave wrote:

    I downloaded Spitfish. This plugin unfortunately does not implement the proper method for keeping the host UI alive when you click and hold one of its controls. This means that e.g. the Podium play cursor stops moving as long as you hold the control.

    Yes. That is why I suggested using it. I think you said this before about fish Fillets plugs so I wanted a worst case scenario plug to show you the problem…but it did not really help reproduce the problem for you sadly.

    But I do not get the “not responding” message. I can click and hold the Spitfish control forever without seeing this message. I am puzzled why you get this not responding message

    .

    I will have to Google this extensively and see what comes up. Vista might be somehow causing the clash but Podium is the only app that graphically shifts so…(scratches head) no idea here.

    Two longshots…I am running a quad and even though it should help mask such an issue it might be exposing it.

    Secondly…we may be using different graphics cards Nvidia here ATi for you? (should make zero difference but worth asking).

    The not responding message might be an OS issue but it is still only Podium that seems to show it.

    Any how I’ll Google diffrent search terms and see what comes up.

    Thanks for your time on this so far!

    #13726
    ZChris
    Participant

    Hi, I managed to reproduce a similar problem in a different way, opening an arrangement with NI Battery loaded on a track. I’m pretty sure it was becaues the Battery sample browser was pointed at a massive directory of thousands of wavs. Podium would do a similar thing with the not responding message but after about 10 secs or so it recovered. Hope that helps diagnose it.

    Edit: I should add this is Vista x64 on a pretty fast music/gaming PC with a Q6600 CPU.

Viewing 8 posts - 16 through 23 (of 23 total)
  • You must be logged in to reply to this topic.
© 2021 Zynewave