Recommended Posts

I guess Gavin is stumped then :(

If it only happens with the one file, then it's something to do with the way that specific file is encoded.

Check if any others work for me, then ill see if I can pinpoint what is wrong with that one file.

Hi Folks

I have been using MKV2VOB for a while now however recentley when i play the vob files using TVersity to stream they will always cut off about one hour in the the movie. Does anyone know why this is or how i can fix this ?

Matthew

Hmm... my 1080p copy of Transformers looks awful after transcoding... I couldn't get screenshots of the same frames, but you can still see how weird the encoded copy is:

The unencoded x264 version: http://www.troist.com/normal.png (This pic is not 56k friendly)

The mkv2vob encoded version: http://www.troist.com/encoded.jpg

Is this just a problem with the current 1080p playback? I used the x264 transcoding option. The outputted file was about a tenth of the size of the original copy.

Hmm... my 1080p copy of Transformers looks awful after transcoding... I couldn't get screenshots of the same frames, but you can still see how weird the encoded copy is:

The unencoded x264 version: http://www.troist.com/normal.png (This pic is not 56k friendly)

The mkv2vob encoded version: http://www.troist.com/encoded.jpg

Is this just a problem with the current 1080p playback? I used the x264 transcoding option. The outputted file was about a tenth of the size of the original copy.

It's not worked then. Sounds like you selected Divx :/

If you transcode with the x264 option the output file should be around the same size give or take.

What codec pack have you installed on your PC? I recommend you clean out your PC and install CCCP I linked to in the 1st post.

I believe others in this topic have done 1080 Transformers before?

My muxing is constantly failing, this is beginning to drive me crazy.

I'm using the settings listed in the opening post, and I've installed CCCP.

With more than 1 file?

If so you must not have space for the mux, or something else on your PC is interfering.

With the program at the build it's at, it's either the way the file is encoded or something not set up right.

There really isn't any more bugs left in it, and hundreds if not thousands of people use it :p

With more than 1 file?

If so you must not have space for the mux, or something else on your PC is interfering.

With the program at the build it's at, it's either the way the file is encoded or something not set up right.

There really isn't any more bugs left in it, and hundreds if not thousands of people use it :p

It's the same file over and over, it's the only file I actually want to use.

It can't be a size issue, there's 80GB free on the drive.

It's the same file over and over, it's the only file I actually want to use.

It can't be a size issue, there's 80GB free on the drive.

If it's one file, it must be a problem with the way it's encoded!

Can you get another rip of the movie?

Also one last thing you can try, http://www.smlabs.net/tsMuxer/tsMuxeR_1.4.6(b).zip

Put the newest tsmuxer in your mkv2vob tools folder and overwrite the previous - Longshot as the change from 1.3.6 (which MKV2VOB uses) to 1.4.6 doesn't really have anything that would help us in mkv muxing.

Try it anyway if all else fails.

I have another thing you can try if the above doesn't work, get back to me.

By the way is it 720p or 1080p?

The cutting off is happening with every movie that i stream and they are fine when i play them on the PC. I also have 100gb free on my drive so i cant see that being the issue.

It's either TVersity setting or your connection.

You doing wireless streaming?

Hmm... my 1080p copy of Transformers looks awful after transcoding... I couldn't get screenshots of the same frames, but you can still see how weird the encoded copy is:

The unencoded x264 version: http://www.troist.com/normal.png (This pic is not 56k friendly)

The mkv2vob encoded version: http://www.troist.com/encoded.jpg

Is this just a problem with the current 1080p playback? I used the x264 transcoding option. The outputted file was about a tenth of the size of the original copy.

I had the same problem with my copy of transformers, the x264 option always seemed to produce a file a 10th the size of the original. I had a look at the bitrate of the converted x264 file and noticed that it was a 10th of the original bitrate found on the source file, it would seem as though mkv2vob is using a lower bit rate when transcoding using the x264 option. I have tried other 1080p files including; Bourne Ultimatum and Harry Potter OoTP, both produce the same results. However using the XviD option produces files that are of 1080 resolution and with a good bit-rate and quality but sometimes the filesizes can be almost double the original.

3r1c had stated on the Doom9 forums that this could occur if mkv2vob is unable to read the header of the x264 file or the appropriate information is not in the header file (eg. resolution, bit-rate etc.).

I have been trying to find the exact command line inputs that mkv2vob uses to transcode the source x264 file to the PS3 compliant x264 file with little luck, if anyone knows the exact input to use with the x264 encoder please post it, thanks.

It's either TVersity setting or your connection.

You doing wireless streaming?

Yes im streaming wireless however i have a popcorn media tank in another room and it streams perfectly, so i dont think it has anything to with the network. I think it could be something to do with TVersity.

I dont know what happend but now all my movies are skipping! dont know if its the update problem but everything i've been using keeps skipping anyone have this problem please let me know this is not good! doint wired not wireless so dont know whats up1

^

If you read what MKV2VOB recommends, it actually says MPG has the "best compatibility".

I now use MPG, all ive really found though is WMP now plays the file - Previously VOBS were hit or miss in WMP.

Not noticed anything on the PS3 side, but I'd say it's worth putting all your movies in the MPG container if 3r1c recommends so.

This topic is now closed to further replies.
  • Posts

    • Wonder what MPs have ties to these privacy/verification/data harvesting companies that are going to step in this time. Last time under the Tories half the cabinet had fingers in the pies, heck even the PM and his wife at the time was working for silicon valley, probably made a fortune.
    • Google Chrome is killing all uBlock Origin bypasses, Microsoft Edge, Opera to follow by Sayan Sen For a while now the transition away from Manifest V2 (MV2) to MV3 has been on-going and it looks like it is entering its final phase of deprecation, at least, in the case of Google Chrome. A recent discussion thread in the w3c WebExtensions Community Group GitHub repo has highlighted how the latest and upcoming versions of the most popular browser are expected to be its final releases with support for MV2 extensions. Chromium contributor Andrey Bershanskiy shared details about recent Chromium changes and according to comments from Google engineer Devlin Cronin, Chrome has now started removing the flags that previously controlled MV2 availability. kExtensionManifestV2Disabled, the Chromium feature flag that allowed controlled disabling of MV2 add-ons, is now completely removed, which means you will likely no longer find uBlock Origin in your browser extensions list. He wrote: "The kExtensionManifestV2Disabled feature has been default-enabled for over a year. Remove the feature and the effectively-dead code. ... Any tests that relied on being in the "warning" phase (i.e., with the kExtensionManifestV2Disabled) for their sole behavior testing are removed, since this stage is no longer reachable." Cronin further explained why MV2 extensions are no longer allowed in supported Chrome versions as maintaining the associated functionality indefinitely is no longer possible. He cited growing technical difficulties and implementation complexities as well as security concerns. He wrote: "MV2 extensions are no longer allowed in any supported version of Chrome, and we are removing support for them and the associated functionality. We won't be able to provide / maintain this functionality indefinitely due to the complexity and tech debt, as well as the security risks it entails (we've actually found a number of bugs that are specific to MV2 lately). Of course, other browsers can continue supporting these if they so desire. Unfortunately, we won't be putting code behind a compilation flag ... We won't be removing all the MV2 code wholesale right away, so many of these things will continue working for awhile (but they will go away eventually, and some may go away sooner than others)." What this essentially means is that the tricks and bypasses that were used to keep MV2 extensions like uBlock Origin and others alive will not work any more on Chrome, or at least not for very long. For example the Windows Registry mod that could extend MV2 availability will cease to function after Chromium version 151. Here is a rundown of the changes coming in the final such releases of Chromium releases: Chromium 150 lost ExtensionManifestV2Disabled option Chromium 151 will loose ExtensionManifestV2Unsupported option Chromium 151 will loose ExtensionManifestV2Availability option Chromium 151 will likely loose AllowLegacyMV2Extensions option Other Chromium-based browsers like Opera and Microsoft Edge could soon follow suit too. Although it is not specified, Edge began disabling uBlock Origin back in February, and Opera could also stop the functioning of MV2 add-ons, even though it had committed to support MV2 for longer in October 2024. uBlock Origin developer Raymond Hill (gorhill) apparently stated the following: "For Opera I did submit 1.70.0 rather late, but this was weeks ago. A while ago I received an email from Opera that they plan to abandon MV2-based extension so maybe they are no longer allocating resources for reviewing such extensions." The email which developers like Gorhill mentions was received from Opera last year. Here is what it seemingly said: Hence for now the only Chromium browser that seems to be on-board fully with MV2 support is Brave, and perhaps Vivaldi as well. Meanwhile if you want to ditch Chromium browsers entirely then Mozilla Firefox is an excellent alternative as MV3 and MV2 are both supported. Of course the easiest solution is to switch to uBlock Origin Lite if you want to remain on Chrome, as it is MV3-based, but from our experience, uBO Lite does not seem to be as good as the original non-Lite version. Source: w3C (GitHub repo) As an online publication, Neowin too relies on ads for operating costs and, if you use an ad blocker, we'd appreciate being whitelisted. In addition, we have an ad-free subscription for $28 a year, which is another way to show support!
    • Write to your MP 😄 Like believing in Santa. Total surveillance IS the goal. Wake up.
    • This whole dumb age verification thing needs to die and be replaced by giving parents tools to control devices. Why am I required to plaster my ID all over the internet to prove I'm old enough when parents should be the ones dictating what their kids are doing on their phones. Apple released great set of tools for iPhones coming to iOS 27 that do just that. Why are governments not mandating that kind of control to phone makers to built them into phones. This whole thing is so absolutely idiotic it's wild.
  • Recent Achievements

    • Very Popular
      Captain_Eric earned a badge
      Very Popular
    • One Month Later
      amusc earned a badge
      One Month Later
    • One Month Later
      DJC50PLUS earned a badge
      One Month Later
    • Week One Done
      DJC50PLUS earned a badge
      Week One Done
    • Proficient
      Eric Biran went up a rank
      Proficient
  • Popular Contributors

    1. 1
      +primortal
      511
    2. 2
      PsYcHoKiLLa
      220
    3. 3
      ATLien_0
      92
    4. 4
      +Edouard
      90
    5. 5
      Steven P.
      83
  • Tell a friend

    Love Neowin? Tell a friend!