Dandruffalright. good to know that you could fix it!
Dandruffi’ve tried the 1.37 demo -> when dragging the polyiblit vsti (1.1.3) from the right panel to the arrangement it also caused podium to crash (“memory could not be read” or something was the error-message). 100% reproducable here. maybe that’s the same bug!?
Dandruff@Zynewave wrote:
a “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.
just add “rescan all”. should be easy to implement i think. that’s the way how it works in cubase.
@Zynewave wrote:
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.
really? in cubase for example that’s not possible. it needs user-interaction (rescan of all plugins).
Dandruff@Zynewave wrote:
I have modified the normal ‘scan & import’ function so that it only imports a plugin if it is not already imported.
but please don’t forget: a “rescan all” is needed for some plugins (when changing settings in them – such as different output-config or settings which causes more latency)!
Dandruff@Podianer wrote:
I wonder why nobody else seems to think this way.
🙄
read the forums and you’ll see, that you are wrong with saying “nobody …”
Dandruff@Zynewave wrote:
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.
please with 0 samples delay, if possible!
Dandruffyeah. a good bank/program-management is essential for a good host. many vsts without an own patch-management rely on this. cubase for example saves these settings in a xml-file for every vst. then when you load the vst again, all banks/programs for this vst are loaded automatically (or are available) to it …
the best would be, if podium could use a steinberg-compatible xml-format. so users could interchange banks/programs saved with cubase/nuendo and podium.
Dandruffyes you are right i think. rme have included these offset-values (for the ad/da-conversions) into their input- and ouput-latency-values. this setting is global, and that’s why i have to correct (90 samples) the adat-input-latency at my hdsp9632 manually …
see http://www.rme-audio.com/english/download/hdsp9632_e.pdf (page 79 – buffer size)
so it would be great if podium could provide such delay per input and track …
Dandruff@Zynewave wrote:
Is that option specified separately for each input in Cubase?
yes and no. the global option (under asio preferences) applies to all inputs (in samples).
for individual inputs (or better say tracks in this case) there’s a delay control for each track (in milliseconds). trackdelay would then be this value + value of the global setting.
for me a global-option (for all inputs) would be enough, as i’m only using two inputs for this purpose (loopback), but if it is possible for you, then an option for each input(pair) would be perfect i think. maybe with switchable samples- or milliseconds-input!?
one more question: do you make use of the asio-offset-function? some inputs on my rme-card (i think the analog) should be automatically delay-compensated by the host. matthias from rme said, that this is currently not possible for all inputs. so they decided to add these offset-values for the analog-stage instead the digital-stage. cubase sx for example reads/scans these values from the asio-driver and compensates the delay automatically …
Dandruff@Zynewave wrote:
Podium cannot compensate for this. If you want to record your synth1 exactly as it is playing ‘live’, you need to use bounce-recording.
can you implement a manual “record-offset/latency” option? -xxxxxx samples to + xxxxxx samples? cubase sx for example has this in the asio-preferences.
my rme hdsp9632 card for example needs -90 samples correction for digital internal loopback recording …
Dandruff@Joachim wrote:
But, how many insert mappings per track would be enough?
6 pre-fader/eq and 2 post-fader/eq. like in cubase. and what’s very important: the ability to move/reorder these inserts around (up and down) on the fly!
Dandruff@super_crunchy wrote:
Regarding plugin development (ie built in plugins for Podium): I think that would be a waste of Frits’ time and skills.
yes -> engine and other things first. but i would like to see some good build-effekts. the most advantage i think would be, that they could use the same ui-style (same look, knob-feel and so on – for better integration, workflow and usage). and zynewave also should know best, how to don’t crash the host with plugins. it only has advantages 🙂
Dandruffdidn’t tried podium yet, but will asap.
also voted for “engine” (optimizing for speed & multiprocessor-systems, high quality samplerate-converter, noise-shaped dither with autoblacking, offline-bounce, sidechaining …)
second would be “ui” (consistent and full customizable, optimizing for speed, helpful tooltips, dualhead-capable …)
and then maybe some high quality bread&butter “effects” (x-band-parametric-eq, compressor, limiter with intersample-peak-suppression, ms/encoder/decoder …)