3.7.1 gone from bad to worse

[Alpaca]

Will be fixed in next version.

Looking at the time it took to release 3.7.1 we‘ll be talking about April/May for the next version?

[amet]

Will be fixed in next version.

Looking at the time it took to release 3.7.1 we‘ll be talking about April/May for the next version?

That’s just rude and uncalled for, I am sure you are very proud of yourself

[Dave_O]

Yep. Noticed an issue with low-bitrate, 2-channels, AC3.
Will be fixed in next version.

Thanks. Here's Mediainfo from another fie that has the issue, hope it's useful:

General
Unique ID : 245090661966559087611830722016198891720 (0xB862BE975CCD6377AEFE58AE25AD98C8)
Complete name :
Format : Matroska
Format version : Version 4
File size : 7.65 GiB
Duration : 1h 43mn
Overall bit rate : 10.5 Mbps
Encoded date : UTC 2015-09-22 02:47:14
Writing application : mkvmerge v8.3.0 ('Over the Horizon') 64bit
Writing library : libebml v1.3.1 + libmatroska v1.4.2

Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : [email protected]
Format settings : CABAC / 5 Ref Frames
Format settings, CABAC : Yes
Format settings, ReFrames : 5 frames
Codec ID : V_MPEG4/ISO/AVC
Duration : 1h 43mn
Bit rate : 9 782 Kbps
Width : 1 920 pixels
Height : 808 pixels
Display aspect ratio : 2.40:1
Frame rate mode : Constant
Frame rate : 24.000 fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.263
Stream size : 7.09 GiB (93%)
Writing library : x264 core 148 r2597 e86f3a1
Encoding settings : cabac=1 / ref=5 / deblock=1:0:0 / analyse=0x3:0x133 / me=umh / subme=7 / psy=1 / psy_rd=1.00:0.00 / mixed_ref=1 / me_range=16 / chroma_me=1 / trellis=1 / 8x8dct=1 / cqm=0 / deadzone=21,11 / fast_pskip=0 / chroma_qp_offset=-2 / threads=25 / lookahead_threads=4 / sliced_threads=0 / nr=0 / decimate=1 / interlaced=0 / bluray_compat=0 / constrained_intra=0 / bframes=3 / b_pyramid=2 / b_adapt=1 / b_bias=0 / direct=1 / weightb=1 / open_gop=0 / weightp=2 / keyint=250 / keyint_min=23 / scenecut=40 / intra_refresh=0 / rc_lookahead=40 / rc=2pass / mbtree=1 / bitrate=9782 / ratetol=1.0 / qcomp=0.60 / qpmin=0 / qpmax=69 / qpstep=4 / cplxblur=20.0 / qblur=0.5 / ip_ratio=1.40 / aq=1:1.00
Language : English
Default : Yes
Forced : No

Audio
ID : 2
Format : DTS
Format/Info : Digital Theater Systems
Codec ID : A_DTS
Duration : 1h 43mn
Bit rate mode : Constant
Bit rate : 768 Kbps
Channel(s) : 6 channels
Channel layout : C L R Ls Rs LFE
Sampling rate : 48.0 KHz
Frame rate : 93.750 fps (512 SPF)
Bit depth : 24 bits
Compression mode : Lossy
Stream size : 570 MiB (7%)
Language : English
Default : Yes
Forced : No

[Alpaca]

Will be fixed in next version.

Looking at the time it took to release 3.7.1 we‘ll be talking about April/May for the next version?

That’s just rude and uncalled for, I am sure you are very proud of yourself

How is that rude? It‘s a simple question which btw remains unanswered together with an extrapolation based on recent facts. You could have answered that the team is working hard on the next release and the release is scheduled for end of February. But you didn’t. Instead you chose to post a meaningless answer and be offensive on top.

[timstephens24]

They're obviously working on the next release, and it was a little rude since you're implying that you'll have to wait 3 months for a fix. There's been a few releases that take awhile, but it's because there's a lot behind the scenes that are changed/updated. There's a lot of different setups out there, and what works for me could break for you, so it needs to be tested. It takes time and there's no exact timeline to release.

[Alpaca]

I admit that my question might have been fueled by a certain disappointment as I haven't been able to use MrMC since last September when the audio problems startet with version 3.7.0! That actually makes it almost 5 months without a working fix. You need quite a bit of patience and capacity for suffering to endure this as a paying customer.

[timstephens24]

Best bet is to try and get in the testing process to help identify them in the future. I don't have any files similar to what you're having issues with, so sometimes it takes someone that normally has a certain issue to be in testing. I know the devs want to get fixes out as fast as possible, but if they push stuff up without testing other issues pop up and more people are affected. It's a hard spot for them to be in.

[davilla]

rock and a hard place

[sirmcftv]

I'm seeing the same issue on the FireTV Stick 4K, video and audio are out of sync. I installed Kodi 18 and it seems to work well, so it is possible. Plex client also works, so not sure it's the new stick.

I initially bought MrMC (a few times on different accounts) to solve problems I used to have with Kodi, which it did. But now the situation seems to be reversed, it feels like the Android (Fire TV?) version of MrMC is not getting the attention it used to. I asked a few questions here in the forums about a problem I have with a local Plex server not being discovered, and no answers. Developers used to be more engaged in the past Perhaps the focus is on other platforms these days?

[davilla]

I'm seeing the same issue on the FireTV Stick 4K, video and audio are out of sync. I installed Kodi 18 and it seems to work well, so it is possible. Plex client also works, so not sure it's the new stick.

I initially bought MrMC (a few times on different accounts) to solve problems I used to have with Kodi, which it did. But now the situation seems to be reversed, it feels like the Android (Fire TV?) version of MrMC is not getting the attention it used to. I asked a few questions here in the forums about a problem I have with a local Plex server not being discovered, and no answers. Developers used to be more engaged in the past Perhaps the focus is on other platforms these days?

more like you are not looking in the right area