Hmmm that´s new to me.... I have done that many times without rating any post... I´ll do a test!

Just changed this thread of mine.... what do you see when you open it?

https://audiosex.pro/threads/solved-sound-devices-mixpre-3-experience.45027/

 

that's about driver, audio mode and operating system consistency indeed;
for ex. right now my RME HDSPe AIO on MacOS CoreAudio latencies are (as shown by Reaper):

at 44.1KHz:
3.4/4.2ms at 128 samples
6.3/7.1ms at 256 samples
12/12ms at 512 samples
23/24ms at 1024 samples

at 96kHz:
1.8/2.1ms at 128 samples
3.1/3.5ms at 256 samples
5.8/6.1ms at 512 samples
11/11ms at 1024 samples

 

Yours is not [solved]. It doesn't stick out with the greenish background. Maybe you used the wrong (solved) brackets

 

Got you now No Avenger..... problem is (as I see it) you dont have this marked as such in the overview at AZ, and that´s what I refer to. When you add the "[solved]" yourself it´s there for all to see.

 

come on dude

BTW since when are members allowed to change thread title....its not possible...and they had a reason..same as for best answer/solved feature...

BTW what is like/dislike/disagree/funny/winner....lot of rating

 

Last edited: Jul 26, 2019

sure i agree must test with same buffer size...i dont kno why i didnt realize that on my own,but maybe cause its over 40°...
but

is simply wrong...i do it a long time ..with windows 7...and i kno what a lite or just normal win7 sp1 un-updated with shut down all the services mentioned in win7 thread is running like.... like a rocket...and i install all the latest software...win10 is hell..

lol..surely not heh heh...
EDIT i got my own,pirate lite and others which i didnt made but check out some day but also these ones got not strip down by random, come on..
check
https://audiosex.pro/threads/the-windows-7-thread.42310/page-6#post-369555
these dudes did well

 

Last edited: Jul 26, 2019

you couldnt a long time..i remember reading a comment of oly why they did remove that option but now its able again..ok

yeah seriously that was the point bro...
it was @ploopy - a lot of rating going on here , isnt it

BTW PLOOPY i marked it as solved (and this was also in thread context cognizable) cause most didnt read proper , but its still to hot outside for going into the forum it seems heh heh..

i could rename the thread to asio4all vs magix asio driver but i dont think this is wanted by staff...

 

Last edited: Jul 26, 2019

he edited the title bo'

 

I changed title but now it should be in other section

 

Oh boy, would you look at that, the thread title changed.

 

This thread is crazy AF. Im out.

 

i was astounded for a couple of million milliseconds when i thought about the values given as acceptable in the guitarrist section (because of standind a few feet fron a rig).
until i realized that after introducing x ms of latency from your pc/vsts you still stand the same distance from your gear, so it will accumulate. in other words, with a bunch of vsts running, you have to get real close to the speakers.

i could be slightly off with some of the numbers since i read this in the 80s, just starting out:
delay of effects:
3-6 ms phasing
6-12 ms flanger
15-25 ms reverb
25 ms and up echo

 

crazy AF? Im in. What is it al about?

 

This is by far the dumbest thread I've read in a long time... oh my... ok, kid's here we go:

1) Magix' Asio Driver just is Asio4All, they licensed that. Use a hex editor and compare...

2) Asio4All or any other 'generic' asiodriver is ONLY necessary if you want to use your onboard realtek chip for music production with
decent latencies. With a Steinberg interface you use the Steinberg Asio driver and with the Edirol Interface you use the Edirol Asio driver.
Those drivers were programmed for exactly that hardware, so they perform best (as long as the product itself isn't total crap)

3) You can have as many asio drivers installed as you like, no asio driver would ever interfere with any other asio driver.
BUT: You can fuck up using them: Your fancy RME card will perform badly when you use asio4all to wrapp the wrapped mme windows
driver of your rme card back to asio...

4) Any NON generic (realtek/wasapi/mme/dx) ASIO driver will only ever work with exactly that one hardware it was programmed for.
Imagine someone saying "since from today I use a brother printer driver as driver for my logitech webcam."
The cause why RME asio drivers perform so well is because RMEs chips are "asio printed to hardware".

 

the rest of youre post was aware to everybody in this thread...
but i dont begin again to point out the thread , again and again..

 

Last edited: Jul 27, 2019

I was suspecting that, see gui design...
However it's not clear the reason why I can use Magix asio at 64 samples buffer without issues, while with a4a at 128 begins to stutter, all other settings being the same.

OR if the manufacturer itself does NOT provide any asio driver, like Terratec for Aureon (Ploytec then saved the issue). Actually, it worked also with a4a, though it SEEMED to me a bit less proficiently.

Yes, I had a4a, magix, generic low latency asio, ploytec and all ignored each other.

The reason why some daw provides asio driver like magix is because they include the most common laptop internal sound board, like realtek, conexant, etc.