@krille
There is indeed a misc setting in gui 2.0, but there is no option to set subs on auto.

Br.
Nasua

There seems to be a lot of misinformation on the 23.976 fps playback issue in this thread lately. Statements like claiming to have had 23.976 / 59.94 Hz output support since initial firmware, 23.976 fps playback at 50 Hz without stutter, speeding down audio to match 24 Hz output, stutter caused by display technology...

If you don't know what you're talking about, wouldn't it be better to just... not spread this misinformation?
Did anyone of you claiming to have perfect 23.976 fps playback actually confirm the vertical refresh rate your PlayonHD outputs, 23.976 Hz output without frame repeats and 59.94 Hz output with perfect cadence?

Hell Fire!!! Misinformation???

You want a quantum breakdown of the exact setting that people have used to elliminate what? Stutter? disinformation? Decimal points?

By "Cadence" I assume you are refering to 2:3 Pulldown (NTSC) or 2:2 Pulldown (PAL) which was mainly used to correct for different framerate standards and used with interlaced tv\video systems. With the exception of a HD tv transmissions (1080i) most units - DVD, Bluray etc. can output progressive signals to the tv. I actually thought cadence was related to voice.

Yeah, with the POHD there is microstutter. It can be severe and it can be minor and hardly noticeable, depending on some simple settings.

I have a Samsung TV, it's a european model which should respond nicely to a 50Hz (PAL system) input. With all other units outputting at 50Hz, it performs perfectly, but with the POHD it doesn't. Setting the output to 60HZ without 24p seems to work very well with the latest firmware. 60Hz with 24p in earlier firmware also worked. so I don't think it is the display technology at fault.

Most, if not all tv's these days will work with any standard and any voltage anywhere in the world. NTSC, PAL, SECAM, etc.. Regardless of whether it is Europe, USA, Japan, France. The only problem is the power outlets in the respective regions are different, that's all. So trying different POHD output settings should not be a problem.

It seems to most "experts"* on the interwebby that 24p is actually 23.976Hz. 24P looks neater and is easier to read than 23.976.

From what I have read in various forum posts it seems that the main problem with microstutter is with Realtek and the Realtek chips. This new firmware we are desperate for, based on the SDK v4, is supposed to fix this. Apparently it has for other Realtek based media players, or so say the rumourmills. So, maybe it's the 24p\23.976 output that isn't right with the current SDK.

*Definition of "Expert": Ex is something that has been and a spurt is a drip under pressure.

I have read through and fully understand the implications of what I have written. I also accept that what I have written may be interpreted as pure bullsh*t.

There 10 kinds of people. Those who understand binary and those who don't.

Hmmm.....

I need another whiskey.

A.V.

Using 24p output there should be no frame repeats for 23.976 fps playback. At 60 Hz (59.94) output 24p should be converted with 2:3 frame cadence (not referring to field cadence as with NTSC). In that way an ordinary video processor shouldn't have any problems restoring the original 23.976 fps.

The POHD (or PoS) plays 23.976 fps video content at 24 Hz (repeating frames) and at 60 Hz with an irregular frame cadence.

If transcoding 23.976 fps material to 24 fps (audio speedup), playback is fine without frame repeats. 25p material at 50 Hz also plays fine on the POHD.

I don't know why some people keeps claiming POHD 23.976 fps playback is not broken and keeps blaming whatever being the cause of the stutters. If it's misinformation or disinformation, you tell me...

You are funny

well for what my comments to this untill now concerns is simple,
i never had microstutter unless i changed some settings in my samsung tv as already posted.

a 23.976framerate as you can say is actually a 24Hz/1.001
so the outcome then is brought back to three decimals same goes for the 30/1.001 en the 60/1.001

plus i never claimed it is brought out as 24/1.001 (23.976Hz) as well ,
but on 24Hz material the tv says 1920x1080P @24Hz
if i play an mkv with 23.976 (24/1.001Hz) it does not give 1920x1080 @24Hz.
it just gives 1920x1080P that is all.

so if i follow the logic ,
if the tv does not see it as 24Hz it probably also is not put out has if it is 24Hz.

or am i wrong here??

if so teach me,
i am very eager to learn ,

Hi Dirk.

All of my .mkv collection on the POHD, according to media info, is 23.976 framerate.

If I set the output in video settings to 24p 'on' it overrides the 1080p 60Hz setting and my tv shows 1080p 24Hz.

This is irrespective of the movie playing.

As I mentioned earlier (and in other posts) I have managed to reduce the stutter to an acceptable level where it is either hardly noticeable or not there. However, I cannot use 24p with this latest firmware without getting the stutter.

I think the issue of 24p(Hz) and 23.976Hz is a tad confusing. The information out there on the web suggests 24p IS 23.976Hz. Other media streamer forums that are now using SDK 4.0 from Realtek are stating true 23.976 movie playback but I'll bet the setting in the unit is still 24p.

This would suggest there is a problem and it is Realtek who are at fault, correcting it with this new SDK 4.0.

It would also suggest that the ACRyan developers have little or no control over the hardware side of things, only the front end GUI. If this is the case then, surely, it must be possible to release a firmware using SDK 4.0 without a fancy new GUI.

I am particularly concerned about whether the DD chip in my machine can cope with a fancy GUI. Besides, like many others, I don't need a fancy GUI, Bit Torrent or Yamj\Thumbgen or whatever gadgety addons there are. We just want a media player and nas box that works properly.

The only way to test this is to get my hands on the new firmware just as everyone else wants. There has (have?) been a number of posts asking when the new firmware is likely to be ready but nobody is giving proper answers.

"Soon" doesn't cut it. We need a proper timeframe. The last response was "2 to 3 weeks" but from when?

Just some more of my ramblings.

Too early for a whiskey at the moment... Damn!

Cheers.

A.V.

i am afraid i can only nod as an reaction here

so yes it is a bit frustrating,

but if sdk 4.0 as you say solves it elsewhere i reccon it does it here as well ???

anyway i am just not allowed to give a timeframe even i would know it,
because i am no employee, and i find these kinds of info should come from them

i do find it strange however (still after almost a year)
that some do have the stutter problem and some don`t,
playing almost the same files.

so for me it is very difficult to pinpoint the exact reason for it,
only thing I did was what i explained in earlier posts.

maybe the difference is that i own one of the first
full HD lcd screens of samsung,
without a 100Hz screen or even higher as there are nowadays.

as i sincerely believe that is one of the course of the microstutter,
so if any picture enhance option s are switched off in the tv screen,
i really believe it should work.

but again i can`t test nor confirm this theory in any kind,
as i can`t fully test it.

I really wish i could solve this issue for everyone,
which i simply can`t , and this really bothers me a lot

but to go back in repeating

let see what the new sdk 4.0 brings to this issue,
and you need to try it to know the outcome.

besides what happens if you simply set the playonhd to 1080P @50Hz?
regardless if the 24P is on or off.

You're showing movies at 60 Hz refresh rate and believe the stutter is either hardly noticeable or not there. Did I get that right?

Yes, at the moment, with this firmware (r4824) movie playback is 1080p 60Hz, 24p off. But, as I have mentioned before, different firmware releases give different results.

My tv is European (UK) spec. so should be working at 50Hz (PAL system) and, with all my other units (Satellite, Bluray, DVD), it does with no issues whatsoever. With the pohd I have to set the output to 60Hz (NTSC output I suppose) to get the best result.

Cheers.

A.V.