Topic: problem with TotalMix

good evening everyone,

i use a HDSPe Madiface (PCIe) with a Sonnet PCIe / thunderbolt adapter to a MacBook pro (late13) with sierra 10.12.4.
Used to work fine, but recently, not sure when, TotalMix started to show 44.1KHZ in the top bar of its window, while the HDSPe settings are correctly set to 48Khz, also the audio midi set up utility shows 48Khz correctly.

the card ID is 22849427 on hardware sticker, 22849033 on HDSPe settings window. (weird??)
Driver is 4.09 and firmware 23.
i have tried totalmix FX 1.40 and 1.42, i have tried uninstall and reinstall the software, remove plist files, no good.

1)is that important?
2)can be fixed?

thanks

aris

Re: problem with TotalMix

Is the Clock Source set to "internal"?

UFX+, FireFace 802 FS, Digiface USB
12 Mic, M1610 pro, Micstasy
MacBookPro M1
Logic Pro X

Re: problem with TotalMix

the choices i have is master or auto sync.
it's on master.

Re: problem with TotalMix

Any MADI devices connected?
Are these set as slave?

UFX+, FireFace 802 FS, Digiface USB
12 Mic, M1610 pro, Micstasy
MacBookPro M1
Logic Pro X

Re: problem with TotalMix

No, these tests are done without madi signal presence.
just the card and the laptop.
you think maybe this is the problem?
i will try that and be back.
thank you very much.

Re: problem with TotalMix

i tried with madi signal from a digital desk, same thing, sync locked in 48k in HDSPe settings, in audio midi set up utility 48k, in cubase 48k, in digital desk 48k, everywhere except totalmix window that still indicates 44.1k in the upper bar.
i tried to upload a photo.

[img]/Users/aris/Desktop/IMG_1446.jpg[/img]

Re: problem with TotalMix

photo

https://ibb.co/gGc8y5

Re: problem with TotalMix

i used madiface to feed a digico console.
card set to master, desk set to receive clock from madi signal. it locks correctly in 48k.
so the interface seems to work.
problem is just on totalmix window indication. for some reason, keeps 44.1.

9

Re: problem with TotalMix

aris koudouris wrote:

1)is that important?

Not at all. This is just a (wrong) info message, not something related to processing.

aris koudouris wrote:

2)can be fixed?

Yes, it will be fixed.

Regards
Matthias Carstens
RME