theshadowrunner
Well-Known Member
- Joined
- Mar 11, 2008
- Messages
- 335
- Likes
- 0
shure it is.
where is the log file located ?
In C:\My Documents on XP.
shure it is.
where is the log file located ?
In C:\My Documents on XP.
No.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
Maybe. I have to look into it.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.
KS? Hell, no!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
No idea.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?
Should work fine the way it is now.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.
No. With Wasapi (excl.) there can only be one. Hence the name "exclusive".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?
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.Maybe. I have to look into it.
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.KS? Hell, no!
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.Should work fine the way it is now.
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.No. With Wasapi (excl.) there can only be one. Hence the name "exclusive".
after deinstalling and manually deleting the ReClock registry key and a new install of 1.8.8.2 everything is now working.
thanks again.
As always... so many things to do, so little time...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.
I don't see the point, as ReClock's WASAPI thread already runs with realtime priority. It won't get any better than this.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
So the problem is, that ReClock detects a 60Hz refresh rate and refuses to sync 24/48fps material.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.
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.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.
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 1.8.8.2: 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.
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;allI don't see the point, as ReClock's WASAPI thread already runs with realtime priority. It won't get any better than this.
I think the MMCS regedit is another fundamental component of the playback platform
Roland and Cakewalk are not idiots to apply this MMCSS function and provide a default value AVRT_PRIORITY_CRITICAL (2) inside their preference
1. apply AvSetMmThreadPriority() functions to all the audio playback related threads and let us to customize the parameter values in the foobar2000 preferences, whatever in decoding threads or output threads (if output in push mode), whatever in foobar2000 itself or foobar2000 output plugins, just like the MMCSSThreadPriority parameter with value options from -2 to 2 in AUD.ini of Cakewalk Sonar.
2. Let foobar2000 change its own process priority itself and let us to define the priority level from normal to realtime in foobar2000 preference, and also let us to define the priority level of the ASIOhost32.exe, ASIOhost64.exe, WASAPIhost32.exe and WASAPIhost64.exe from normal to realtime too.
3. If possible, change the full file buffering behavior to the same as AWE of cPlay which would never be paged up to paging space in hard disk by the OS, or add an AWE playback function separately, if possible.
4. add support up to SSE4.x in all the possibly using processor instructions operations like decoding or DSP, if the foobar2000 installed machine provided.
The background priority. The range of values is 1-8.
The way MMCSS works is it gives you really-really-high-priority
Calls the AvSetMmThreadCharacteristics function to request that MMCSS increase the priority of the thread in which PlayExclusiveStream executes.
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.So the problem is, that ReClock detects a 60Hz refresh rate and refuses to sync 24/48fps material.
Yes, I realize that but anyway no big dealDS is shared, so ReClock won't complain. It doesn't even know that it can't use audio, Windows does the audio device allocation.
Tests of MMCSS during Vista development showed that, even with thread-priority boosting, heavy network traffic can cause enough long-running DPCs to prevent playback threads from keeping up with their media streaming requirements, resulting in glitching. MMCSS’ glitch-resistant mechanisms were therefore extended to include throttling of network activity.
To provide a better playback experience, Windows Vista introduces MMCSS to manage the CPU priorities of multimedia threads.
..
The various task keys specify how much preference threads associated with different multimedia types get for CPU and graphics processor resources
..
While Windows has always supported prioritization of CPU usage, it hasn't included the concept of I/O priority.
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
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
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..and a small usability tweak request if possible: a new Hotkey (Shortcut Key) to toggle "Enable sound compressor" ON/OFF.