JRiver 17 e versioni successive

[stealth82]

Molte novità importanti

17.0.95 (2/24/2012)

1. Changed: Updated LAV filters to .48 which fixes a crash with native DXVA2 on hardware that doesn't support decoding all formats.
2. Changed: IIR based DSP effects like low-pass, high-pass, Linkwitz, etc. better handle denormals (numbers very close to zero) so performance slowdowns don't arise from these numbers.
3. Changed: Tuned timing used when switching madVR between Display View and Theater View to (hopefully) fix black-screen hangs.
4. Changed: Updated the RSS feed for Theater View Yahoo! News to point to a new RSS feed that works (Yahoo! still offers the old feed, but it's full of broken links).
5. Fixed: Sometimes when deleting files, especially from Theater View, the remove empty folders prompt would not appear right away.
6. Fixed: Toggling the new DSP option 'Process independently of internal volume' could cause a burst of sound if the internal volume was low.
7. Fixed: Tempo & Pitch DSP did not flush fully, so on seek, etc. a little tail could be heard in some cases.
8. Changed: The text output in the Export Playlist tool creates standard CSV output (RFC 4180 compliant).
9. Fixed: Channel editing tool did not work for DVB-C/S and QAM tuner types.
10. Changed: Removed Output Format option for sources that have an incorrectly mastered subwoofer, use -10dB to the subwoofer in Parametric Equalizer instead if needed (discussed here: http://yabb.jriver.com/interact/index.php?topic=70303.0).
11. NEW: Add DLNA controller switch to ignore transport events (use polling mode) to the Player Zone.

17.0.94 (2/23/2012)

1. Fixed: WASAPI output mode could lose lip-sync when seeking in video.
2. Faster: Pruning of the Theater View background cache could cause exiting Theater View to be slow (pruning is now around 50x faster and only done once a week).
3. Fixed: LAV Source/Splitter filter would allow viewing configuration pages which is not valid for auto-configured Red October filters and in fact shows the config for a separately installed instance.
4. Changed: Theater View News works better when an article fails to load (like the current Yahoo! failures due to a Yahoo! server problem).
5. Fixed: Volume Protection could engage and turn the volume down on subsequent videos when playing videos back to back.
6. Faster: The HTML parser used by Theater View news is about 10x faster.
7. NEW: Each DSP effect can be set to be processed independently of internal volume (Options button at top right of DSP).
8. NEW: DSP effects can be set to process only when viewed, which is useful for visualization style items like Analyzer (Options button at top right of DSP).
9. Changed: Tuning to some wording in DSP Studio.
10. Changed: DSP Studio keeps 'Output Format' first and 'Volume Leveling' second. A message explaining this is shown if a user attempts to put other effects before these effects.
11. NEW: Added a second Parametric Equalizer to DSP Studio so it's possible to apply effects on either side of Room Correction, convolution, etc.
12. Changed: One-time reset of DSP effect ordering due to other changes.
13. Fixed: DLNA controller function was assuming it was in control whenever a zone was selected leading to badness if we were only viewing a zone someone else was controlling.
14. Changed: DLNA controller polls for playing state if it thinks it's playing but the position isn't updating from 0. This fixes trouble if an event is missed.
15. Turkey: Moved the search box to the lower-left of the Options dialog as discussed here: http://yabb.jriver.com/interact/index.php?topic=69921.0.

17.0.93 (2/21/2012)

1. Changed: Added support for reading the lens name from XMP.
2. Changed: Improved the HTML parsing engine used in Theater View > News to works better with BBC, possibly others.
3. Changed: Tweaked the list of reasons in the uninstall dialog.
4. NEW: Added The Verge to Theater View News.

17.0.92 (2/21/2012)

1. Changed: Updated German language file (thanks Bytestar).
2. Changed: MCWS functions that return a decimal will always use . as the decimal character (unless the value is designed to be displayed to a user like VolumeDisplay, etc.).
3. Changed: Revised how image playback creates hardware accelerated devices to fix stalls before drawing the image on some machines.
4. Fixed: Switching between 3d and regular Theater View lists could cause the number of thumbnails in a row to change.
5. Changed: Minor tuning to thumbnail sizing in Theater View to make a 1080p display more likely to show 3 rows for movies.
6. Fixed: VideoClock was not engaging in some cases so there could be frame repeats / frame drops.
7. Changed: VideoClock will allow up to a 1% clock drift to achieve a perfect 2.5 video to refresh rate multiplier (used for 24 Hz video on 60 Hz display).
8. Changed: Real Media video files (.rm,.rmvb,.rv,.smil) are now played through Red October rather than using the Real Media engine (which wasn't working anyhow).
9. Fixed: DVB-S channel scanning could get channels with wrong frequencies or multiple entries of the same channel with different frequencies.
10. NEW: Added a subtitle mode (Options > Video) that shows a sidecar when it's found, regardless of other settings. (mode: Show subtitles only if selected subtitle language is different from audio language, or if subtitles are in a sidecar file)
11. NEW: Added default field 'Lens'. Filled automatically from the EXIF tag with Canon cameras.
12. Fixed: Downloading from Library Server for transfer to a handheld might time out if conversion was custom MP3 and audio file was very large (~2 hours).

http://yabb.jriver.com/interact/index.php?topic=70371.0

[runner]

Lunedì proverò

[stealth82]

Nuova versione madVR

17.0.96 (2/28/2012)

1. Changed: Updated to madVR v0.81 with Red October HQ.
2. Changed: Gathering playback state and position information for a zone occurs in a background thread so a slow DLNA device or server can not cause user interface issues.
3. Faster: The threaded approach to display information updating allows running updates one tenth as much while providing smoother visual position incrementing.
4. Fixed: URL-based video playback was not working since build 94.
5. Changed: Kernel Streaming output no longer writes partial packets if there's a shortfall or at the end of a track but instead delivers a full packet with some silence (some drivers blue screen on partial packets).
6. Fixed: DVB-S channel scanning did not save modulation type value correctly.
7. Fixed: Theater View > Playing Now > Info could show the wrong track when first entering.
8. Changed: Video conversion for Gizmo / WebGizmo uses MP3 instead of AAC (works better with Android 4.0, maybe others).
9. NEW: Video conversion tool using Red October available on right-click menu (Library Tools/Convert Format). The UI is mostly finished, the transcode profiles are not fully defined and may not give expected results. More to come. WARNING -- Use with caution.
10. Fixed: After deleting files from Playing Now, the selection could unexpectedly revert to the playing track.
11. Changed: Renamed Options > Media Network > Client Options > to 'Automatically sync changes made on client back to server' to 'Auto sync with server'.
12. Fixed: DVB-T/S/C channel scanning could crash in some cases.
13. Changed: Theater View sheet list style adapts the image aspect ratio like other lists (instead of always using squares).
14. Fixed: A few bugs in the DLNA renderer.
15. Changed: Added Media_Duration to GetMediaInfo for the DLNA renderer.

http://yabb.jriver.com/interact/index.php?topic=70477.0

[GrandeBoma]

Se abilito l'accelerazione hardware con madvr ho problemi di scattosità qui e là mentre se disabilito l'accelerazione è tutto ok, ma i video a 60i non ce la fa, per quelli devo per forza abilitare l'accelerazione

[stealth82]

Evidentemente sei "corto" di scheda video.

[madman]

è ancora valida la scelta di una 6570 fanless per uso htpc con jriver e/o equivalenti (quindi LAV+madvr+DXVA2)?? o è consigliabile altro?

[stealth82]

Non conosco le ATI mentre mi pare di aver capito cosa devi cercare in un NVIDIA quando vuoi LA scheda video per queste cose "accelerate".

http://www.nvidia.com/object/graphic...s_buy_now.html

Più CUDA cores hai e meglio è; senza strafare ovviamente comprando una mega top di gamma.
Per dire, tra una 9500GT e una 450GTS c'è un bell'abisso di cores.

[stealth82]

17.0.99 (3/2/2012)

1. Changed: Improved the workaround for the blue-screen crashes in the Thesycon (and possibly other) audio drivers when resetting with Kernel Streaming.
2. Changed: Reworked how full packet Kernel Streaming delivery is handled to work better with video (full packets are required or some drivers stall playback).
3. Changed: If video hardware acceleration is enabled, and Media Center detects an Intel Atom processor, DXVA2 Native mode is preferred over CUVID mode for hardware acceleration.
4. Fixed: DLNA search didn't work properly with servers/renderers that used the same port for both.

17.0.98 (3/1/2012)

1. Fixed: The remote control plugin was not included in build 97, leading to problems.
2. Fixed: Filename truncation could still unnecessarily truncate long fields.

17.0.97 (2/29/2012)

1. Fixed: DVB-S channel scan could produce wrong polarization value ("Linear Horizontal" was set to "Not Defined").
2. Changed: Revised how filenames that are too long for the file system are truncated (previously truncation could be too aggressive).
3. Fixed: The program could crash when the remote control feature was disabled.
4. Fixed: DVB-T/S/C channel scanning could crash in some cases.
5. Fixed: Stopping image playback while audio playback was in progress could cause a crash in build 96.

http://yabb.jriver.com/interact/index.php?topic=70533.0

[GrandeBoma]

problemone: se abilito il refresh rate auto changer e uso madvr, quando entra in exclusive mode (l'unico che mi da la fluidità) se muovo il mouse per cambiare capitolo o mettere pausa, esce dall'exclusive mode... e l'uscita dall'exclusive mode determina il ritorno alla risoluzione di default. Quando poi riparte l'exclusive mode ovviamente la risoluzione rimane quella sbagliata. Come posso risolvere?

ho provato a usare il mode changer di madvr e disabilitare quello di jriver un opzione che funziona ma ha un grosso limite, che poichè i dvd non usano madvr con quelli non ho refresh rate changer e devo mettere manualmente 1080p24

[R!ck]

è ancora valida la scelta di una 6570 fanless per uso htpc con jriver e/o equivalenti (quindi LAV+madvr+DXVA2)?? o è consigliabile altro?

Ma Lav non è solo per schede NVIDIA?

http://forum.doom9.org/showthread.php?t=160290
http://forum.doom9.org/showthread.php?t=146228
http://yabb.jriver.com/interact/index.php?topic=65471.0
http://yabb.jriver.com/interact/index.php?topic=67835.0

[mrwinch]

Ma Lav non è solo per schede NVIDIA?

I codec LAV supportano perfettamente le ATI: non è ben chiaro se e come lo faccia madVR con JRiver...

[stealth82]

Non credo usare JRiver faccia alcuna differenza, il decoder è sempre quello. Se non ti sembra il caso bisogna verificare "contro" quale versione di JRiver lo testi: JRiver aggiorna periodicamente LAV con le sue releases.
Cmq, quando c'è qualcosa che non va le comunicazioni con lo sviluppatore sono immediate in quanto quest'ultimo è un attivo frequentatore del forum.

In verità molta gente interessante è attiva frequentatrice del forum JRiver: quelli di cui stiamo parlando sono nevcairiel per LAV e madshi per madVR.

[R!ck]

I codec LAV supportano perfettamente le ATI: non è ben chiaro se e come lo faccia madVR con JRiver...

E' una buona notizia rispetto a quando lo sviluppatore a caratteri cubitali a marzo 2011 scriveva:
"This is a decoder for NVIDIA GPUs, it does not work with ATI/AMD or Intel, and it never will!"

C'è ancora qualche problemino nelle prestazioni che non si risolverà senza lo sviluppo di un decoder DXVA2 nativo che edit:[...non...] è nei programmi dello sviluppatore.

DXVA2 "copy back"
In our series of hardware decoders, the new DXVA2 decoder now features hardware decoding also for AMD/ATI.
Its a "copy back" (or "renderless") decoder - that means all frames are copied back from the GPU to normal memory.

Sadly, however, AMD/ATI cards suffer from a serious performance penalty, which prevents them from showing their full potential. The decoder is fully Blu-ray compliant, and even goes beyond that, however playing 60fps movies will most likely not work fluidly.
H.264, VC-1 and MPEG-2 are fully supported (progressive and interlaced), as long as your hardware can keep up. Very old AMD/ATI cards, like 3000 series and below, might not be able to use this decoder. 4000 and up seem to be working ok.

I do have plans to work on a "native" DXVA2 decoder, which does not need to copy the frames back from the GPU, avoiding this performance bottleneck - however that goes with the loss of the flexibility of course. No post-processor, only EVR, etc.

For everyone else, i recommend to stick to your native decoders (CUVID/QuickSync), as they generally work better and faster then DXVA2.
Known Issues:
- Interlaced H.264 on Intel can show image corruption
- Some MPEG-2 streams show image corruption (all GPUs)

There is also the potential for crashing the GPU driver. It happened mostly on VC-1 interlaced, and all cases i encountered i also fixed, but if it happens, just let me know, and i'll look into it.

http://forum.doom9.org/showthread.ph...74#post1554374

[stealth82]

In realtà dice è nei piani dello sviluppatore.

[R!ck]

Grazie di avermelo fatto notare...mi è scappato un NON di troppo


PS
Ma non c'è il tag strike con questo forum?