Hi Frits,
I’ve installed the new beta driver for the HDSP system, and according to RME, I suppose that it may give better performances within Podium :
http://www.rme-audio.com/download/hdsp_wdm_beta1.zip
“- Lower system load on start of data transmission (start of record/playback)
– Better performance on playback. We added a small safety buffer of 32
samples on the playback side. To give some numbers from a typical test
machine, crackling starts at:
Old driver 64 samples 60% 128 Samples 70% CPU load
New driver 64 samples 85% 128 Samples 90% CPU load
So even if you add the 32 samples to the 64 samples, the new driver
still does a better job than the old one at 128! And the 32 samples are
on the playback side only, so throughput monitoring is even more
attractive. Because of this tremendous improvement we removed the
highest buffer size and replaced it with a 32 sample setting as lowest
setting.
– Secure Record Technique. This driver includes a new scheme for
handling record data. It guarantess all record data to reach the
application even when the computer is blocked with 100% CPU load for a
short time. We think this is a real killer feature, as there is nothing
more important than reliability when doing recordings.”
I have not yet the time to really test it, but there is also a change in the output routing which is for me a real problem : the SPDIF outputs are now between the analog and ADAT, that is to say in position 9/10 instead of 17/18.
I know that you have already told me that you didn’t plan to add a custom selection of inputs and outputs in Podium π₯
But now when I work with 16 channels sound I will have to use 18 outputs, and add some plugin to shift the channels 9 to 16 in position 11 to 18.
It is not of course a big problem, but it would be VERY nice, some day, to be able to choose the outputs that are used, like in Steinberg, Motu or even EnergyXT, not only deactivate them…
Thanks.
You should actually contact RME about this…it is VERY unusual for a driver to change the order of the outputs. That kind of change would screw up a lot of people’s set ups, especially in Logic where you’d have to make some major changes not only to your Autoload, but to every song that had the old settings…actually now that I think about it, Podium too…works the same way, with the studio setup actually built into the project.
I notice you’re using a beta driver, so maybe this is a mistake/bug on RME’s part?
In any case, if they’re going to make a change like that, they should offer users–through the main driver or a peripheral mini-app–the option to configure the order of the outputs and present them to any sequencer as such. I remember my old MOTU could do that.
it is VERY unusual for a driver to change the order of the outputs
It is not a mistake and has been made because when the ADAT I/O is used at 96 kHz it has only four channels, so it it may seems more logical to have them “at the end”.
Of course, we need to change the routings for old projects π
they should offer users–through the main driver or a peripheral mini-app–the option to configure the order of the outputs and present them to any sequencer as such.
Yes, I hope that they will do it.
Podium too…works the same way, with the studio setup actually built into the project.
Not really. As I remember, Logic was like Steinberg’s, we can choose what channel bus goes to what output.
In Podium we can only activate or deactivate an output, but while it is “muted” it is always present in the bus.
For example if you have a 8 channels outputs mapping and you unselect the outputs 3 and 4, you will silmply have no sound on channels 3 and 4, the channels 5 to 10 are not “shifted” like they are in EnergyXT.
You can neither change theit order like it was possible in Logic or some others (if I remember well…).
So we can’t say that the studio setup is built in the project, it’s only the selection of the active outputs.
Having to add a plugin to change the order is not a problem, this is what I do when I use 24 channels, but it takes also some CPU resources, but I think that having the possibility to change it inside Podium will be helpfull when we change the position of connected devices or if someone go to another studio with a different interface.
Ohhh yeah I get what you’re saying now. Another feature to throw on the Future Development list I guess!
Another feature to throw on the Future Development list I guess!
Perhaps… When all the rest will be done ! π
@acousmod wrote:
Hi Frits,
I’ve installed the new beta driver for the HDSP system, and according to RME, I suppose that it may give better performances within Podium :
http://www.rme-audio.com/download/hdsp_wdm_beta1.zip
“- Lower system load on start of data transmission (start of record/playback)
– Better performance on playback. We added a small safety buffer of 32
samples on the playback side. To give some numbers from a typical test
machine, crackling starts at:
Old driver 64 samples 60% 128 Samples 70% CPU load
New driver 64 samples 85% 128 Samples 90% CPU load
So even if you add the 32 samples to the 64 samples, the new driver
still does a better job than the old one at 128! And the 32 samples are
on the playback side only, so throughput monitoring is even more
attractive. Because of this tremendous improvement we removed the
highest buffer size and replaced it with a 32 sample setting as lowest
setting.
– Secure Record Technique. This driver includes a new scheme for
handling record data. It guarantess all record data to reach the
application even when the computer is blocked with 100% CPU load for a
short time. We think this is a real killer feature, as there is nothing
more important than reliability when doing recordings.”I have not yet the time to really test it, but there is also a change in the output routing which is for me a real problem : the SPDIF outputs are now between the analog and ADAT, that is to say in position 9/10 instead of 17/18.
I know that you have already told me that you didn’t plan to add a custom selection of inputs and outputs in Podium π₯
But now when I work with 16 channels sound I will have to use 18 outputs, and add some plugin to shift the channels 9 to 16 in position 11 to 18.
It is not of course a big problem, but it would be VERY nice, some day, to be able to choose the outputs that are used, like in Steinberg, Motu or even EnergyXT, not only deactivate them…
Thanks.
This is a wdm driver isn’t it ?
As far as I understand it has no advantages for apps using ASIO drivers. Is this correct ?
Isn’t it aimed more at apps that perform better with wdm…eg. Sonar ?
swayzak
This is a wdm driver isn’t it ?
As far as I understand it has no advantages for apps using ASIO drivers. Is this correct ?
As it is said, this new version of the driver now supports the WDM, and has also some improvements which are available in ASIO too…