More > JRiver Media Center 30 for Windows

NEW: JRVR Video Enhancements in Media Center 30

<< < (2/31) > >>

Hendrik:

--- Quote from: tkolsto on August 25, 2022, 03:26:55 pm ---"Built-in deinterlacing independent of the GPU driver"

I read about deinterlacing. This is to get better perceived motion and reduce flicker. So this is going to done seperately away from the GPU and handled within JRiver? Did I understand this correctly? And I interpret this to be a better way of rendering video?

Looking forward to this greatly! Maybe my problems will be less troublesome. Also the presets is a welcomed feature :)

--- End quote ---

I'm not sure you quite understand what interlacing and deinterlacing is. Content can be interlaced, which is an inherent property of the video - typical for live TV content (prominently sports, concerts, and such events). Our displays are not interlaced, so we need to convert them - enter deinterlacing.

This planned change has no advantages beyond dealing with videos of such a nature.

Smack:
Hello Hendrik

I just saw that in the upcoming mc30 release the black bar detection might be implemented.

Just out of curiosity how does it work. Do I have eggheads (like the conheads) because the picture has to be streched? Or will there be left and right some of the picture cropped?

Hendrik:
It will not cut off any image (unless you want it to), nor stretch the image in unnatural ways.

People with an ordinary 16:9 screen won't really make use of this, its useful for wider screens and projectors.

HTPC Videophile:

--- Quote from: Hendrik on August 26, 2022, 12:00:10 am ---The same sidecar will be used, its not a "audio analysis sidecar" file, its generic. You can turn off sidecars and just use the MC library to store the data if you don't want it there.
The entire idea of the sidecar file is to have it next to the video, which means as long as the video file exists, its likely for the sidecar to go with it - if it were moved to a central location, that feature would be lost, and all you get is basically the MC Database, which already stores all this in a central location.

I personally turn the sidecars off as well, and just make sure my MC Database has regular backups as needed. Thats surely an option you can go for if you don't want the sidecar next to your file.

--- End quote ---
  thanks for the confirmation Hendrik regarding this. One adjunct query regarding the same: For the  case  of varying width of black bars within the same movie, will the video analysis take care of it(eagerly expected scenario for me !) or will it resolve to some nominal value that just removes/minimizes the black bars (Unwanted/Unacceptable scenario for me !). And if i don't mind stretching/distorting my videos to fill the screen , can i stretch the cropped videos(using video analysis info) to full screen(16:9) display like i do after MadVR automatic cropping.Will it give the same results as far as final image co-ordinates are concerned(compared to MadVR) . if my query is NOt clear i might post screen shots of video image with MadVr cropping/processing and  then MC  stretching .     Also please  clarify the query(1) in my above post .

Hendrik:
The first version will most likely not support varying aspect ratios. Its a niche feature used in only a very small minority of movies, and often also part of the artistic intent.

The entire idea is to not detect blackbars live during playback, because thats computationally rather expensive and complex, which is why madVR for example only allows it with CPU decoding and not when hardware accelerated decoding is used (and its slow).
Instead, the black bars will be detect beforehand, and the information only used during playback.

Navigation

[0] Message Index

[#] Next page

[*] Previous page