Topic: Podium has set Punch Out marker to infinity in one project

Viewing 8 posts - 1 through 8 (of 8 total)
  • July 3, 2005 at 09:32 #576
    super_crunchy
    Participant

    Hi Frits

    I am having a problem with the Punch Out in one of my projects.

    When I open the arrangement in my project, Podium freezes when I try to play the arrangement.

    I noticed that Punch Out has been set to infinity somehow, and I’m sure this is causing the crash. No matter how far I zoom out, I cannot find the red Punch out marker…

    I’ve emailed the project to info [at] zynewave [dot] com

    Specs:

    Win XP home
    Podium 1.32, and 1.34 I’ve tested this bug in (crashes in both with this project)
    48Khz sample rate
    Only this project is affected, and I’m not sure why only it is. How can I fix it up?

    Thanks

    July 3, 2005 at 09:47 #5016
    super_crunchy
    Participant

    Edit: I’ve tried “Load default setup” and I’ve also deleted Podium.ini

    But the problem with this one project remains… also, the project in question was probably made in Podium 1.31 or maybe earlier. However none of my other older projects (of which I have many) have had this bug with the Punch Out set to infinity

    July 3, 2005 at 10:09 #5017
    Zynewave
    Keymaster

    Hi,

    Punch out location is not set to infinity, but the bar stretches towards infinity because punch out is disabled. The punch out locator in your project is set to 578 (same as punch in), which is displayed in the field next to the punch in/out buttons. Enable punch out to be able to drag the punch out locator. Also you can right click in the timeline and use the ‘set punch out here’.

    Why your project freezes, I don’t know. I tried playing it, and the cursor moves ok, but I don’t have the plugins your project is using. Does it freeze if you just enable monitoring of the arrangement?

    July 3, 2005 at 23:29 #5018
    super_crunchy
    Participant

    Hi Frits

    You must not be seeing what I am seeing. I’ve emailed some example images to show you what I am seeing (note, I mocked the images up in PhotoShop because I’m not on my music machine right now… don’t tell my boss!!) 😉

    Thanks

    July 4, 2005 at 00:51 #5019
    Zynewave
    Keymaster

    The images are as I expected, and I’d like to stick to my previous explanation 😉 :
    Select the ‘punch out’ button, and you will get the handle.

    July 4, 2005 at 09:02 #5020
    super_crunchy
    Participant

    Sorry Frits, I didn’t read through your original explanation clearly enough 😳 Tried the Punch Out button, works just like you say 😉

    Looks like a plugin is causing the problem, as you’d thought, I’m currently taking each out (one session at a time) and enabling the arrangement. I think I’ll be here a while before I find the culprit, but it’s the only way to find out for sure…

    Thanks for your help, helpful and straight to the point as always, Cheers

    July 4, 2005 at 23:24 #5021
    super_crunchy
    Participant

    hey frits

    is there any chance you could build in a plugin tester which checks for offending plugins in projects if you ask it to, and disables the plugin without crashing Podium? i wasn’t sure if that would be possible to build within VST architecture. Just a thought. I have another project now which is also crashing when I enable monitoring, and I’m not sure if it’s the same plugin or a different one

    July 5, 2005 at 01:36 #5022
    Zynewave
    Keymaster

    is there any chance you could build in a plugin tester which checks for offending plugins in projects if you ask it to, and disables the plugin without crashing Podium?

    Podium has protection against plugin crashes during plugin load and in the audio processing thread. Even with this protection it is still possible for the plugin to overwrite memory belonging to the host, and thus possibly causing a crash in the host.

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