Zynewave's Forum Page

1) Manually edit the names of your old output mappings and delete/duplicate new mappings to match the number of inputs/outputs on your new card. Adjust the starting channel number in any new mappings you create.

2) The editor profiles are stored in the Podium.ini file. You can reset this with the “Load default setup” menu command (available in the upper left corner of the project start page). Reinstalling Podium will not affect the Podium.ini file.

@wanyze wrote:

@Zynewave wrote:

You should be able to get the render to work if you temporarily swap the master mapping with the one that starts at channel 1.

Uhm, sorry again, but could you guide me please of how to do this step-by-step?

On the topmost master track, assign your “FW AP Analog Out 1/2 L+R” mapping instead of the S/PDIF. Do the render. Then assign the S/PDIF mapping back on the master.

Alternatively you can do realtime bounce recording, in which case you don’t have to swap your master mappings.

I have Image Line Plugins installed, but they work, no problems whatsoever.

Yes they work fine, but Podium crashes when it scans the Image Line plugins during import.

If I press CTRL+B the bounce track is active, but then “Render Bounce Track” is disabled, and I can’t bounce it off at all.

You just need to disable the bounce track (press B) and then the render command is available again.

Isn’t the purpose of activating the bounce track it’s muting all tracks underneath and listening to a rendered/bounced track?

Yes.

there is lonly the Audio track left playing by itself and I can hear it. Buy yet I still can’t bounce it off.

I can take a closer look if you email me the project file.

If you have punch-in/out enabled, the bounce will be limited to that range.

Hi,

I’m not aware of any plugin CPU consumption problems with Podium. I’ve also spent quite some time optimizing the engine, so as far as I know, there are no areas left that needs to be optimized.

Is your problem that the Podium CPU indicator reaches 100 sooner than it would in Cubase? Or does the audio start to crackle before reaching 100?

Some things to check:
Try increasing the ASIO buffer size a notch and see what this does to the CPU performance.
Check that the engine is running in 32-bit and not 64-bit mode.
Check that multiprocessing is enabled (if your AMD chip supports that).

The grid only reflects the time signature. It does not change according to the selected quantize value. But it’s a good suggestion, and something I may add later on as an option in the editor profile.