ZynewaveI can think of a number of ways to solve this. One of them is copy/paste of tracks (on the list). You would then highlight a track, press ctrl+c, and press ctrl+v for each duplicate you want.
Zynewavea “rescan all” is needed for some plugins (when changing settings in them – such as different output-config
This requires a little more development time, so for now only filename check is implemented.
or settings which causes more latency
This does not require a rescan. Podium will dynamically update latency compensation whenever a plugin reports a change in latency.
ZynewaveTo avoid having to exit/restart Podium, you can open the MIDI/Audio interfaces dialog and press OK, which will reinitialize the drivers.
ZynewaveGood idea. I have modified the normal ‘scan & import’ function so that it only imports a plugin if it is not already imported. Will be available in release 1.39.
ZynewaveThe ridiculous thing about it is, that this message disappears after a view starts of Podium.
I don’t understand. Do you mean the message does not appear, if you exit Podium and restart?
Do you use 48000 in your arrangements?
P.S. curious about the upcoming features in 1.39!!!
No major features. Just minor stuff and bug fixes.
ZynewaveNo it just said program not responding at the top of the screen.
Then there’s a good chance this is the bug that I have fixed recently. Try again when 1.39 is released.
P.S Do you just press quote and then after you insert the text press close tags.
Yes. I normally drag-highlight the text I want to quote from the topic review box, press Ctrl+C, set focus to the reply box, press the ‘Quote’ button, press Ctrl+V, and then press the ‘Quote’ button again (or ‘Close tags’). Then write the reply below the end quote tag.
ZynewaveHi Stu,
I replied to some of these issues in the other topic with the bugged project. I also asked some questions there which would help me pinpoint the problems.
ZynewaveThe limit for both program and bank library presets is 256 MB. If a plugin reports a preset size bigger than this, Podium will display an error message.
I notice that plugs like energyXT and DoppelMangler, which both need to save alot of data in presets, will crash when projects are reloaded.
Does the crash occur during the project load command, or when you activate monitoring of the loaded project? Maybe the crash occurs when the previous project is unloaded, so if you select ‘new project’ before reloading the project, when does the crash occur?
I briefly tried storing both program and bank library presets with eXT (1.4), and I could not provoke a crash when reloading the project. If you have a project file that crashes, please email it to me.
ZynewaveWhat I don’t get Frits is that I never had any problems with recording up until about version 1.35?
There has been no recent changes to the engine regarding latency compensation, so I’m afraid I don’t know why it appears to work differently for you with the latest versions.
Today Podium crashed when I was changeing the hierachy level of a track, I was just simply moving the track up a level.
A couple of days ago I found a bug in the multiprocessing code that could cause the engine to lock up, when a plugin was bypassed. This could explain your crash bug. Did a crash dialog appear, or did Podium just hang?
Karma synth still causes faults in the on exit save option
I’m aware of the remaining issues with the Karma synth.
Last but not least there have been alot more cpu spikes occuring, these had gone away for version 35 36 37 but have come back again.
What is the typical CPU percentage right before the spikes occur? If you are running on a hyperthreading processor, it could be issues with the multiprocessing. Try disabling the multiprocessing option in the audio page in the preferences dialog.
ZynewaveThere seems to be quite a few people interested in plug in development. A small collection of plugs developed by Frits is an interesting idea.
For a long time I have had an idea for a multi-fx plugin. It would solve both the problem of missing EQ and dynamics in the Podium mixer, as well as offer a solution for multiple effects on a single track. I’ll probably start experimenting with this soon, after I wrap up a few minor things.
ZynewaveDoes this proceedure have to be followed for every bank for every track for every project?
Not for every track. Once a fxp/fxb file is imported into the project, it will be available in the preset panel to all tracks that have the plugin assigned. If you’re just browsing the various bank files, you can reuse the one bank library preset you have created. Open the properties for the library preset, and import another bank file. I guess this could be streamlined by adding an ‘import file’ menu to the library preset context menu.
Zynewavedo you make use of the asio-offset-function?
After checking the ASIO documentation, I cannot find any reference to ‘offset’. Is this an RME specific addition to the ASIO spec?
Podium queries the ASIO driver for input and output latencies, but these values are global for the driver. The ASIO spec does not provide a means to specify individual latencies for each input/output. This is a problem with soundcards that have both analog and digital connections, because the AD/DA converters typically introduces additional latency.
ZynewaveRight-click on the track header where the impOSCar is assigned. Monitoring must be activated to see the preset menus. You can also click on the menu button in the header of the preset panel in the inspector.
Zynewavecan you implement a manual “record-offset/latency” option? -xxxxxx samples to + xxxxxx samples? cubase sx for example has this in the asio-preferences.
Is that option specified separately for each input in Cubase? Otherwise, setting a latency for a loopback input would also influence regular inputs.
ZynewaveYes the mapping is an audio input mapping named MIX IN LEFT+RIGHT
I’m guessing that this input is a loopback of the soundcard output. My Yamaha SW1K soundcard has a similar feature. The problem with this kind of input is that it will record everything that the soundcard is playing, so you’ll have to solo the synth1 track during recording. Another drawback is that depending on the soundcard driver, you will get at least one buffer delay from the soundcard output to the recorded input. Podium cannot compensate for this. If you want to record your synth1 exactly as it is playing ‘live’, you need to use bounce-recording.