It would be nice if you could explain why your earlier attempts failed, and what your recipe does to avoid those problems. That would allow to replicate this with different tools.

The difference between BINARY and MOTOROLA is just little versus big endian as you might guess. This answer is about addressing a bug in Brasero on your architecture.

The reason you need to do this is because […] PlayStation as far as I know, only supports BINARY as value for FILE — the PlayStation doesn’t support any values for FILE because it deals with physical discs, not cuesheet files.

And the whole cdemu to sound-juicer dance could have been replaced by a simple dd conv=swab…

After looking at the link, it looks to me like it is a big-endian vs. little-endian issue, and the Playstation only seems to support little-endian. So that's what the answer should start with. The rest just looks like a somewhat complicated way to achieve this with particular tools, I can think of at least two different ways out of my head to do differently with different tools (e.g. without any cue files).

@dirkt you're welcome to publish your toolchain

I don't have a playstation to test it... that's why it would be interesting to know what exactly has gone wrong, instead of "just do those particular steps with those tools". And now looking at it again, it might still be just an issue with the tools itself. I know 90% of Q&A on the internet today is just "Don't try to understand, just do those steps, turn off your brain", but it's not a particular good way to work with computers...

To keep beating the same drum, despite what is starting to come across as wilful ignorance: CD audio is defined to be little endian. It is part of the definition of CD audio. This has nothing whatsoever to do with the PlayStation, which came well after the fact. That you’ve found some broken user-antagonistic tools that are willing to screw up your CDs has nothing whatsoever to do with the PlayStation.

And it's not even certain that Brasero would burn an actual CD incorrectly; it's only known that it writes CD image files in big-endian, appropriately marked as MOTOROLA in the cue file, and some emulators refuse to read that.

This seems to be more related to your CDROM burning tools, than the PlayStation. This question is more like "How do I use Brasero and cdemu and sound-juicer to make an audio CDROM?"

@user253751: I don't agree, this question asks how to produce audio disc (images) which work both on PlayStations and emulators, preferably on GNU/Linux. The fact I've documented only a graphical pipeline doesn't imply I wouldn't be very happy to read the one-liner which makes the "SoundScope music player" an easy reality.

And again, the problem is not with using GUI vs CLI tools as such, but with you being apparently unable to explain what the problem is and how each of those tools is necessary to address it.

@user3840170: if with "unable to explain why you need to do so" you meant "atm unwilling to learn why duckstation only supports BINARY and why brasero only produces big-endian images" then I can agree with what you said.

If you don’t want to learn that, so be it, your loss; but then don’t go around writing Q&A pairs that teach people to follow steps they won’t have a chance to understand either.

@ScroogeMcDuck Our rules of engagement include the words “Be clear and constructive when giving feedback, and be open when receiving it.”. It goes both ways. If you don't want to hear constructive feedback, that's one thing, but please don't tell people off for giving it.

@wizzwizz4 editing writer's answer? constructive. derive unjustified, offensive implications on the writer out of nowhere? not constructive.

@wizzwizz4: user3840170 feedback has been readily integrated into the answer at every interaction. on the opposite, I can't see how bullying strangers for not wanting to fix bugs in random decades-old software projects (I even specified "now") could be considered good behaviour.

@wizzwizz4 as well as making strangers feeling guilty for not dedicating enough time to free (as in free beer) contributions to this website. luckly, since our contributions are also free as in freedom, he is very capable of fixing issues himself and not bothering others.

@ScroogeMcDuck Normally I'd agree – but those "offensive implications" are things you wrote about yourself. Editing your answer would be inappropriate, because fixing these issues would constitute rewriting the entire answer, which isn't allowed by Stack Exchange rules (except for community wiki posts); see the "clearly conflicts with author's intent" suggested edit rejection reason.

Have you considered starting a blog? Not every contribution is a good fit for this site; I've had plenty of closed and downvoted posts, myself, and I'm meant to know the rules!

@wizzwizz4 I trust willing readers in the next two decades to be able to understand how that user has been rude and assuming and how my answers were chill and calm.

@ScroogeMcDuck Your recent edit violates our self-promotion policy. I'd strongly recommend editing in a disclaimer about that tool's authorship; the system's pretty harsh on spammers.

thanks @Chenmunka