Discussion in 'ReClock' started by James, Jan 18, 2014.
In C:\My Documents on XP.
thanks found it.
Hi James, TYVM for the new build and I was hoping we could discuss a few points if you don't mind:
1) Were you able to reproduce this problem by any chance? http://forum.slysoft.com/showpost.php?p=362430&postcount=60
It's no big deal but it would appear to be very real.
2) Would you consider allowing Reclock to exchange informations with madVR? Many people are currently using Videoclock in JRiver because it does exchange infos with madVR, such as the fps rate which is mandatory when you want to process IVTC in madVR for instance. It's also relying on madVR for the refresh rate detection FWIR.
3) I very recently made the big jump to W7SP1(yay ) and what sounds the best for me with a UAC1 compliant async DAC in foobar is forcing its MMCSS priority from "'Playback" to "Pro Audio" and using KS instead of native ASIO or WASAPI event/push. Would you consider forcing "Pro Audio" for Reclock if that's not already the case? Here's a link on that matter: http://msdn.microsoft.com/en-us/library/windows/desktop/ms684247(v=vs.85).aspx
4) I've tried the "Novista" registry key but I can't get any KS audio output, be it 16/24/24@32 or 32int. My DAC relies on the windows built-in drivers, does this registry key work for anyone?
5) Regarding the media adaptation speeds, would you consider adding "48fps" please? This would come in handy should you process inverse PALSpeedup on deinterlaced PAL material. I've got a bunch of R2 DVD's here and I need to watch them in 50@48fps.
6) I sometimes play music in foobar and play movies without sound simultaneously, Reclock in WASAPI keeps showing a "The audio device is in use by another application" even though sound is muted in my video player, would that be possible to disable it?
Hope you can help, thanks in advance!
Maybe. I have to look into it.
KS? Hell, no!
Should work fine the way it is now.
No. With Wasapi (excl.) there can only be one. Hence the name "exclusive".
Hi James, thanks a lot for the replies.
OK fantastic news, you can find madshi's email address at http://madshi.net/about.htm , he will be more than willing to help and madVR is by far the currently leading VR so it would be really great if Reclock & madVR could exchange vital informations as IVTC is currently impossible for instance.
Sorry, I misexplained myself.....I was asking if you could please force the "Pro Audio" MMCS priority as this seems to improve the SQ in many ppl's experience(including mine). Apparently several Pro Audio device drivers developers also use this trick in order to force Windows to give the highest priority to the audio rendering thread.
This will equally help any kind of audio rendering and this might very well be a "free lunch" addition to Reclock
Well, there's no 48fps speed adaptation option in Reclock atm and my LCD TV doesn't support 48Hz, so I have to run it in 60Hz and enable mVR's frame blending so the 48fps adaptation can't be done automatically and I can't use any refresh rate multiple option in Reclock either.
My point was that if audio is muted in the video player, maybe Reclock could stop trying to allocate the audio device? Or possibly not complain that it didn't work at least. If I set Reclock to use DS while playing ASIO in foobar, Reclock is unable to lock the audio device and yet doesn't complain either.
after deinstalling and manually deleting the ReClock registry key and a new install of 18.104.22.168 everything is now working.
This is very weird, and a little scary... Glad, that it is working, but I still can't understand what happened.
There is one design flaw with the new "force frame rate feature" in 22.214.171.124: If you manually set a frame rate, and then set the framerate to "unknown", the DS estimator will not be called again, only the in-built estimator. This is because the DS estimator will only be called once, when the file is opened. This could probably have caused the problem you've seen, but stopping/starting playback should resolve this, as well as restarting the player.
As always... so many things to do, so little time...
I don't see the point, as ReClock's WASAPI thread already runs with realtime priority. It won't get any better than this.
So the problem is, that ReClock detects a 60Hz refresh rate and refuses to sync 24/48fps material.
DS is shared, so ReClock won't complain. It doesn't even know that it can't use audio, Windows does the audio device allocation.
I forgot to mention, that I'll try to improve that with the next version.
I fully agree and I'll save from this kind of audiophool link discussing MMCS priorities : http://www.phasure.com/index.php?topic=1398.0;all
A bit less audiophool here: http://www.hydrogenaudio.org/forums/index.php?showtopic=101368&mode=linear
Apparently Cakewalk Sonar runs MMCS at the highest priority and some device drivers from Roland also do, they know what they're doing.
His guidelines regarding foobar make quite a lot sense and would very much apply to Reclock as well I think:
I realize that Reclock already runs its WASAPI thread in realtime priority and I run a ramdisk pagefile so 2 & 3 are covered, the only MIA is 1, it would be really cool if you could please make it happen :rock:
It would appear that forcing "Pro Audio" does a lot more than what forcing "realtime" priority does: http://msdn.microsoft.com/en-us/library/ms684247.aspx
It basically ensures that all the rest runs in low priority and subjectively speaking this seems to improve SQ(and I didn't pronounce the J..... word ), at least many ppl say so, I would agree.
More discussions on MMCS can be found at:
This sounds full of win 8)
Well, adding a "48fps" entry in the adaptation speeds list would save the day for interlaced PAL content in 60Hz as mVR's frame blending works quite well and many displays out there don't accept 48Hz.
Yes, I realize that but anyway no big deal
You see, it will even throttle the network speed in order to provide multimedia apps with more CPU cycles: http://blogs.technet.com/b/markrussinovich/archive/2007/08/27/1833290.aspx
madVR already forces 0.5ms NT resolution, so this would only help further to get A/V as realtime as Windows could handle
Yes, all true, but ReClock won't work any better.
Fair enough, I guess it takes a very good reason for you to go through the trouble of diving into Ogo's messy code and even if forcing a high MMCS priority might very well improve SQ, Reclock must leave enough juice for the video rendering duh...so it would need to run in "Playback" priority and not quite "Pro Audio". I'll just fire up my usual startup process.exe batch that puts all non-vital background processes in low priority on single cores
Maybe you don't understand. ReClock is an audio renderer, it runs (mostly) in the thread context of the caller (e.g., a player application). The only internal threading is done, so the resampler can use multiple cores (pure luxury), and the wasapi output. (And some stuff not worth mentioning). Both is not really time critical (as long as it is called "soon enough", which is pretty much guaranteed).
Nothing blah blah pro audio oh my god is it a cool name will make it work better, if the caller (the player software) sucks. If it doesn't suck, ReClock won't suck, too.
Seven years later I was searching for this and read your request. Alas, it's never been implemented. Closer I could get, through EventGhost, is having remote buttons for Compression on and off. You need to set values in the registry, that correspond to what Reclock does when you activate the function through its control panel.
Separate names with a comma.