Recommended Posts

Anyone know how to get MP4 files playing on the PS3? I have a DVD copy of a particular football game and it was never released on HD besides the cable broadcast. I've since downloaded the HD version only to find it in the odd .mp4 format. The PS3 shows it as an unsupported file type when I transfer it over. I'm trying to use PS3video9 to convert it and we'll see in two hours how it works out.

Is there a faster way to make these compatible like the mkv files? Its pretty frustrating that the PS3 supports .mp4 files but is picky in which it will play [from what I've read, Sony has very strict requirements on what file types it will play].

Yeah I've had it where some MP4 work and some don't, it's a real pain :(

Thanks for the guide though Audioboxer, I'm going to give it a try soon because I've got tons of MKV's that I need to get working on the PS3.

It's just too much of a hassle connecting my laptop to my TV every time ;) haha

use GotSent to convert mkv files

it splits the mkv h264 video and audio and rejoins it into a ps3.xbox mp4 file

If you're going to manually convert the file make sure the h264 is level 4.1 compliant

^

MKV2VOB is better optimised for the PS3, and should be used over GOTSent.

The 360 can't do muxing and 5.1 dolby digital.

It can only do muxing and 2.0 stereo, or transcoding video and 5.1 dolby digital.

Figured it out. The file I have is x264 AVC (not supported). Needs to be h.264. C'mon Sony, expand support.

Erm x264 IS h.264 which is also known as AVC, H.264 is the standard and x264 is one set of developers take on that standard.

Your file probably doesnt work because it has been encoded using settings incompatible with the PS3 like P4x4 or too many reference frames.

Not all videos work, all programs like MKV2VOB do is demux the h.264 video file and audio file, patch the videostream to make it Level 4.1 instead of 5.1, re-encode the audio and remux it into a PS3 compatible container, if the video you are putting into it has incompatible settings then unless you transcode it reducing the quality what you put in you get out with is an incompatible file.

V2.2.4 2/June/2008

Fixed bug where subtitle SRT filename that contained a comma would result in no subtitles in resulting conversion.

Disabled return code checking (this caused mencoder error for some people), instead its only treated as a warning of possible failure.

Improved "Repairing AC3" step, should keep all channels from the original ac3, this is a work-around to a tsmuxer bug, tsmuxer author please fix it!

Last fix may help you guys that complained about the vocals track going missing?

Do you know why some 1080p MKVs need to be transcoded while others do not? It isn't a big deal for me since I set it overnight, but it is interesting.

Some 1080p films (mostly new ones) are ripped in video profile 4.1, which allows muxing.

I don't think it has any difference on the movie at all, but the issue is a lot of early stuff was ripped in 5.1 with programs, and if you rip it in 5.1 it's not possible to change to 4.1 and make the file work on a PS3 without transcoding.

4.1/5.1 has nothing to do with sound, it's just some sort of profile attached to the movie.

720p stuff can be changed from 5.1 > 4.1, it's just 1080p that has issues with it.

This is a first. 1080p file failed to play on the PS3. Its picking up the total time, sound (dolby digital 5.1 / 48khz), and video codec, but no playback whatsoever. It just sits @ 00:00:00.

Did it transcode or mux?

I wasn't watching it but I thought it did both from what my buddy said. It transcoded overnight and into the next day. When we were watching First Blood Pt 2 I asked what it was doing and he said it was muxing.

For some reason, the rip pops up a dolby digital logo on my screen for a few moments. None of the other rips have done that.

Also, would you recommend getting a 500GB 5400rpm drive or smaller 7200rpm drive for the PS3? It seems zippy enough currently but I will need a new drive. Also, instead of backing up and swapping drives, could I just buy an external drive and hook it up USB or would that not work?

  • 2 weeks later...
This is a first. 1080p file failed to play on the PS3. Its picking up the total time, sound (dolby digital 5.1 / 48khz), and video codec, but no playback whatsoever. It just sits @ 00:00:00.

I have a similar issue - the video didn't require transcoding but mkv2vob did have to change the audio from DTS to AVC 1/2(?).

I'm getting really peeved with the issue of getting HD-content to work on my PS3. It seems like you have to download a hundred programs which don't all work 100% of the time :(

I have a similar issue - the video didn't require transcoding but mkv2vob did have to change the audio from DTS to AVC 1/2(?).

I'm getting really peeved with the issue of getting HD-content to work on my PS3. It seems like you have to download a hundred programs which don't all work 100% of the time :(

There are no easy ways of getting mkv files to play on any console, best way is to use a PC based media centre.

There are no easy ways of getting mkv files to play on any console, best way is to use a PC based media centre.

I stream all my movies to my PS3 already.

Tools to convert mkv to PS3-playable formats aren't reliable enough (especially when you consider the time it takes for conversion etc) and it's even more annoying that some perfectly good xvid files won't play when streamed but will play if put on a usb stick and played through the PS3 that way.

I stream all my movies to my PS3 already.

Tools to convert mkv to PS3-playable formats aren't reliable enough (especially when you consider the time it takes for conversion etc) and it's even more annoying that some perfectly good xvid files won't play when streamed but will play if put on a usb stick and played through the PS3 that way.

95% of the 720p content I have just muxes and plays fine :/

I don't mess around with 1080p stuff and transcoding, but I guess that end of things will be more frustrating.

As for the streaming issue, TVersity are releasing a new update this month (big GUI change amongst other stuff), and I'm sure they'll make the app work even better with a PS3.

95% of the 720p content I have just muxes and plays fine :/

I don't mess around with 1080p stuff and transcoding, but I guess that end of things will be more frustrating.

As for the streaming issue, TVersity are releasing a new update this month (big GUI change amongst other stuff), and I'm sure they'll make the app work even better with a PS3.

TVersity just doesn't work for me - the service fails to start and I could never get it to work.

I managed to convert all my mkv's with GOTSent and they all worked without a problem.

Curious.

Are you muxing to vob with GOTSent though?

If not, it'll be converting audio to 2 Channel I believe... Ok if you don't care about 5.1!

This topic is now closed to further replies.
  • Posts

    • 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.
    • Remeber this decade, when the free internet died... tell your grand kids about this, record there reaction and post it on InstaTwitBook.com
    • UK nudity blockers are a looming privacy disaster, we must be able to see the source code by Paul Hill Image via Pexels The UK government, just like many state governments in the US and national governments around the world, has begun going on a bit of a power trip when it comes to digital safety. The major step taken so far is the introduction of the Online Safety Act, which requires users to prove their age to access adult websites (it includes more than this, too). Now, UK PM Keir Starmer is calling on Apple and Google, and presumably other mobile OS makers, to scan phones for explicit images to protect children. This potentially mandatory on-device scanning by vendor-controlled software will create unacceptable harms to individual freedoms and transparency, and introduce massive surveillance risks. In a statement on June 8, the Prime Minister stated that big tech companies, such as Apple and Google, must add features to their platforms, such as iOS and Android, that will detect and block sexually explicit or nude images involving under-18s on phones or tablets. Adults who want to take or send nudes would be required to hand over some form of identification to stop their phone from blocking these pictures, creating unnecessary privacy risks. According to the government, it wants to see these measures implemented within three months; otherwise, the government will introduce legislation to force them to introduce such technology. The legislation will include fines for companies and maybe even criminal liability for tech bosses who do not comply with the measures. In its announcement, the government said that stopping users from taking, sending, or receiving nudes without verifying their age is technically feasible, and pointed to a British firm called SafeToNet, which has made proprietary, closed-source, uninstallable software called HarmBlock and is actively selling a device with it enabled and is working with other OEMs. The fact that this software is closed source is a huge problem because it’s a black box; you do not know what it is doing on your device. The fact that it is unremovable is also a problem because you lose control of a phone that you own. Laughably, the government, just before highlighting SafeToNet, says that companies must introduce such measures “without threatening privacy or collecting any data.” It then says over-18s will still be able to view adult content by providing proof of age… Which sounds to me like data collection. SafeToNet makes some debatable claims about HarmBlock The government’s example software, HarmBlock, is a hugely alarming choice to espouse the virtues of this type of software. SafeToNet claims that HarmBlock is “ethically developed,” but this is the opposite of the truth. This black box software puts digital handcuffs on you if it’s installed in your device, taking away your freedom to control what software runs on your device, as it cannot be removed. It is not even free software, so we cannot inspect the source code to see what it is doing. For all we know, it could be acting maliciously. While that’s unlikely, we can’t verify that it’s not doing that. When Google and Apple do inevitably integrate these features on devices in the UK, they are very likely to be closed-source binaries, which will also be non-auditable. They will also have identity services built into them, which will require at least temporary collection of sensitive identity documents to verify your age. One saving grace for Android users is that this nudity blocker will very likely be implemented within the Google Play infrastructure that’s deeply tied into commercial Android devices. However, anyone with enough determination to throw out Google apps from their phone by flashing a custom ROM could find they regain control over their phone again without these digital handcuffs. Obviously, this is only how I expect Google to implement the feature; if it bakes it into the open-source Android somehow, that would be bad news for anyone looking to escape it. Outside of stripping mobile phone users of their freedom and sovereignty over their devices, these proprietary on-device machine learning or hash-matching solutions cannot be independently audited. This means that hackers could potentially exploit them because security researchers can’t investigate the code, and they could overstep their intended use case and collect even more user data without anybody knowing. We also wouldn’t know if the code is prone to detecting false positives or biased classification, because we can’t see the code. In the government’s announcement, contributing comments from the Internet Watch Foundation keep talking about “on-device protections” as if to say that users don’t need to worry about server-side processing; however, this is misleading, as data could flow from devices for the purpose of updates, remote model changes, telemetry, or server-side matching. We’ve also seen with the Online Safety Act that the government is never content with the laws it introduces; it always wants to expand the controls. If this scanning functionality arrives on devices, it might only block nudes initially, but later governments could pressure vendors for expanded access or use mandated features for other surveillance aims. The introduction of on-device scanners opens the door to massive risks in the future. Once nude blocking becomes normalized, regulators like Ofcom or politicians themselves could push for more controls over people’s devices. Very possible candidates for blocking include hate speech, misinformation, or undesirable political content. Also, there is a chance that once Apple and Google have developed this software, they might attempt to reuse the infrastructure for commercial or foreign requests, putting customers in greater danger. Just the UK's demand for this sets a precedent. What if a dictatorship decides to spy on activists by demanding that Google or Apple implement similar controls? Another concern with this scanning is that it adds compliance costs for businesses looking to get into the mobile operating system space. While Google and Apple dominate the space right now, there are lots of smaller companies creating mobile operating systems too, including community projects with very shallow pockets. How are these smaller competitors supposed to implement sophisticated nudity detectors? Simply put, they can’t. Then the government goes after them, causes them to shut down, and Google and Apple have less competition. Image via Aurora Store For us users who value sovereignty over our technology, this development will force us to seek freedom-respecting alternatives. The simplest path forward will likely be to install a custom ROM on an Android device; however, kicking Google off the phone with its black box nudity blocker could also make it harder to access apps such as banking apps, which tend to need you to pass Google's integrity checks. Thankfully, Google Play Store apps can still be obtained by storefronts such as the Aurora Store, but it just adds to the friction. To be fair to those pushing this measure to protect children, I think it will be reasonably effective, but people will still try to find ways around it, just as they’ve done with age gates on adult websites introduced under the Online Safety Act. In the effort to find circumvention methods, it could lead users to join riskier platforms that introduce new dangers. This effort also diverts resources from proven interventions such as law enforcement cooperation, targeted investigations, education, and support services to broad technical controls that have uncertain effectiveness (due to their newness). If the government is set on introducing such tools, then there ought to be safeguards in place. Any mandated code should be released as free software so that it can be audited, and the binaries should be reproducible builds so that the public knows nothing has been tampered with in the code used to create the binaries shipped out. Ideally, these tools should also be voluntary, opt-in, and even community-run. This would also allow people to have full control over their hardware while allowing parents to flip a switch to turn on these protections for children, with the knowledge that the code being run is doing exactly what it says on the tin, and nothing nefarious, like a black box solution could be doing. The government should also have a narrow legal scope where this technology stays with blocking nudes and not spreading to blocking political opinions, hate speech, and so on. Ideally, any implementation should avoid identity-linked age verification to keep user data safe, and matching should be done locally with no server telemetry to ensure it is truly on-device. While I do understand that stakeholders such as parents want to keep children safe, the potential for abuse with this type of software is colossal. It would entrench black-box surveillance and take away our freedom to use our devices as we want. There is also the acute risk that the government will demand this surveillance be expanded to block other activities, which could be particularly dangerous. If you are in the UK and don’t wish to see these measures implemented, it is still possible to write to your MP, which could lead to some better safeguards being introduced before it’s too late. Once we get more technical information about how this will be implemented, then we will be able to see if de-Googling Android devices will bypass this measure. For anyone with an iPhone, there is zero chance that you’ll be able to take off these handcuffs because Apple doesn’t let you mess with your software.
    • I'm reading the reports as EU rejecting Apple's proposal because Trusted System Agent would be an intermediary offered to third party AI's (this article is also worded as such) but Siri AI itself would not pass this intermediary. This would cause a situation where Siri AI would have more direct system access and offer it an unfair advantage. (speaking from EU regulator perspective here) Apple is citing security issues with doing what EU asked for, and I think this also supports this theory, because truly direct system access like Siri AI would make it impossible to control third party AI's running on the devices and e.g. reign them in via adjustments to Trusted System Agent. So, I _think_ this is the sticking point right now: EU saying they need to be on equal footing as Siri AI, Apple saying they can't be because Apple only trusts their own AI. Apple could of course be leaning a bit extra hard towards this because they're biased in terms of excluding competitors. One method to find an agreement would be to have Siri AI also run through Trusted System Agent and treat it as untrusted. This kind of defensive architecture design (especially when involving an AI) would honestly not be a very bad idea from a sheer engineering standpoint. But then Apple would need to swallow their pride and adapt worldwide due to EU, and make perhaps major updates delaying Siri AI once more.
  • 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!