On Sat, 2 Jul 2016 13:30:16 +0100, Stroller wrote:
> The question may boil down to the Google Drive audio / video player,
> and its (in)ability to play AAC audio. But that would be surprising,
> don't you think?
Possibly, but easy to test. Download the file from drive to local
storage then try to
>
> Just top be clear: I'm pretty sure that's not _extracting_ the audio, but
> _transcoding_ it.
>
> The midentify output in my original post shows the audio to be AAC.
Extraction is;
ffmpeg -i "input file.mp4" -acodec copy "output file.aac"
Man page;
" Stream copy
Stream copy is a mod
Hello,
On Sat, 02 Jul 2016, Stroller wrote:
>Well, I tried that.
>
> youtube-dl -x --audio-format best http://www.bbc.co.uk/programmes/b07fl5bh
>
>This gives an .m4a file which also does not play on the device.
Have you tried mkv? E.g. download to m4a as above and then do a quick
mkvmerge
There is a VLC port in the Play Store. You can check F-Droid as well.
Also consider Termux although it has out of date repos.
Stroller wrote:
> I've only recently started using my Android device for playing audio.
>
> About once a week I listen to a podcast, which is usually an MP3 I've
> downloaded from NPR.org.
>
> On my laptop I copy these to Google Drive (big shout to
> net-misc/drive) and then I can access then v
And people look at you funny when you request a physical copy of the GPG key...
:|
> On 5 Jul 2016, at 12:57, Marvin Gülker wrote:
>
> Are the amd64 images all
> corrupt, and thus should not be used for installation? If so, they
> should not be linked to on the main download site.
This doesn't address the wider implications of this dodgy checksums, but I
think most people on
> On 4 Jul 2016, at 22:56, Willie M wrote:
>
> I also tried to download it and play it using best but it would not
> play. You best bet is to just extract the audio as mp3 using the command
> I showed you.
Just top be clear: I'm pretty sure that's not _extracting_ the audio, but
_transcoding_
Am Tue, 5 Jul 2016 13:26:50 +0300
schrieb Andrew Savchenko :
> Checksums are indeed wrong, whirlpool one too. Thanks for noticing,
> I opened a bug for this:
> https://bugs.gentoo.org/show_bug.cgi?id=588062
Okay, thank you. This has been now marked as a duplicate of another
bug[1], which in turn
Hi,
On Tue, 5 Jul 2016 09:57:02 +0200 Marvin Gülker wrote:
> Hi everyone,
>
> I was wanting to give Gentoo a try today, but failed to verify the
> current minimal installation medium for amd64[1]. The .iso file does
> not match the SHA512 checksum provided in the .DIGESTS.ASC file[2]. The
> wrong
Hi everyone,
I was wanting to give Gentoo a try today, but failed to verify the
current minimal installation medium for amd64[1]. The .iso file does
not match the SHA512 checksum provided in the .DIGESTS.ASC file[2]. The
wrong checksum was confirmed by a user in the #gentoo IRC channel on
freenode
11 matches
Mail list logo
