Zynewave.
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.
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 …
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.
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 …
stuWhat I don’t get Frits is that I never had any problems with recording up until about version 1.35 ❓
stuWhile Im hear I’ll take the chance to report a few problems that have occured since installing version 1.38.
Today Podium crashed when I was changeing the hierachy level of a track, I was just simply moving the track up a level. I consider this very unusual because Podium has’nt crashed once since Ive had it.
During playback I could hear crackles when certain tracks started to play (as in my tune was playin along fine then when certain instruments came in I could hear noise that was’nt surposed to be there), I then solo’d the suspect tracks and the noise had gone, I then played them all together again and it had gone, I then closed the project reopend it and started playback the suspect tracks came in and so did the noise again, I did the solo thing again and the same thing happend, very strange what do you recon Frits.
Karma synth still causes faults in the on exit save option, theres no writing in the box’s and they are some what sqaushed. You still can’t save libary presets with it, the synth just returns to the starting patch. No doubt these problems are to do with that dll so don’t bother answering this if that is so.
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. These spikes have occurd in a project that was fine in version 1.37, they don’t always happen but they are more frequent and once they start I have to turn monitoring of and on again.
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.
stuDid a crash dialog appear, or did Podium just hang?
No it just said program not responding at the top of the screen.
What is the typical CPU percentage right before the spikes occur?
About 30%. I’ll just turn it of for now then.
P.S Do you just press quote and then after you insert the text press close tags.
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.