From: J K.Eason
Sent: Saturday, July 23, 2016 7:15 PM
Can't you use the --fatfilename or --hfsfilename Output Option switches
on GIP's command line? I assume it works the same under Linux as Windows.
--fatfilename Remove FAT forbidden characters in file and
directory nam
> *From:* RS
> *To:* get_iplayer@lists.infradead.org
> *Date:* Sat, 23 Jul 2016 14:14:33 +0100
>
> From: Chris Allison
> Sent: Friday, July 22, 2016 22:37
> To: RS
>
> >You could use the linux/freebsd utility detox, compiled under
> cygwin
> >to clean up file names.
>
> Many thanks for the sug
From: Chris Allison
Sent: Friday, July 22, 2016 22:37
To: RS
You could use the linux/freebsd utility detox, compiled under cygwin
to clean up file names.
Many thanks for the suggestion. I think it is probably easier to use Linux
directly rather than install and learn to use cygwin. detox l
From: Vangelis forthnet
Sent: Friday, July 22, 2016 01:25
You could also have asked me how I handle files with colons in the names.
In all honesty, how could I?
Sorry, my comment was not intended to cause offence. You asked me how I
coped with a limitation of a file system I was using. I
On Thu Jul 21 22:19:27 BST 2016, RS wrote:
If I need to download a file larger
than 4GByte from get_iplayer
(snip)
I'll have to do it to an internal NTFS drive.
I can then use ffmpeg to split it into FAT32
compatible files so I can use the satellite
receiver to play them.
Many thanks for
From: Vangelis forthnet
Sent: Tuesday, July 19, 2016 00:42
Both drives are formatted as FAT32.
How are you managing > 4GB video files with the above file system on those
drives?
The solution adopted in the satellite receiver is to break a recording up
into 500MByte segments (about 10min at
On Mon Jul 18 16:02:27 BST 2016, RS wrote:
Both drives are formatted as FAT32.
This is necessary for compatibility
with my satellite receiver,
but it is also necessary for safe hot removal.
Hello, Richard :-)
How are you managing > 4GB video files
with the above file system on those drive
From: RS
Sent: Monday, July 18, 2016 16:02
The performance of the two drives was much more similar. The Samsung drive
started at 79GByte/s. It then fell to 30GByte/s after about 500MByte and
remained at that level. The Maxtor drive started at 77GByte/s and also
fell to 30GByte/s after about
From: Nick
Sent: Sunday, July 17, 2016 14:19
There was a thing at some point with Windows where external drives
would not have write caching enabled. Perhaps the different OS versions
and/or different drives have ended up with different settings?
Drive caching being off means that external dr
On Sun, 17 Jul 2016 13:27:19 +0100
"RS" wrote:
>
> Why the Maxtor slows down the HLSHD download in Windows 10 and not
> Windows 7 or Vista and why the slow down is so severe and remarkably
> consistent remain a mystery, but at least I now know what the
> solution is.
There was a thing at some po
From: Nick Payne
Sent: Friday, July 15, 2016 09:46
I've never seen a USB3 slowdown on either operating system on any of our
PCs or laptops, nor had any USB3 connected devices suddenly drop from view.
I run my backups to external USB3 drives, and the Robocopy log from the
latest backup of my PC
On 15/07/2016 8:24 AM, RS wrote:
From what I have been reading it seems that Windows 10 and Windows 8.1
have problems with USB 3 drives. In some cases they stop being
recognised after a period of idle time. I have not had that, but
there is a really dramatic slowing down.
I've never seen a
From: Vangelis forthnet
Sent: Tuesday, July 12, 2016 03:08
so your assumption inside this thread that your
2.95-dev snapshot was using ffmpeg to fetch hlshd
is at fault; please read further down:
Hello Vangelis
Many thanks for the detailed clarification. I have a vague recollection
that when
On Mon Jul 11 17:52:25 BST 2016, RS wrote:
The timestamp of the dev version I am referring to
is 14 Feb 2016 at 2305.
Hello Richard
Is the timestamp you quote an attribute of the
downloaded 2.95-dev perl script file?
If, in fact, you did download at that place in time
the then most up-to-date
From: Alan Milewczyk
Sent: Monday, July 11, 2016 22:05
I'd second that, over the weekend I was downloading a fortnight's worth of
Wimbledon on my laptop using 2.95 Win 7 x64 and getting speeds typically of
20-30Mbps, although I noticed there were periods where it dropped to about
3Mbps. I'm on V
From: Colin Law
Sent: Monday, July 11, 2016 21:27
I cannot see that the release of v2.95 can have any impact if you are
not actually using that version. I would assume it is just
co-incidence.
Colin
I did think if there were now many more people using the HLS streams that
could slow thing
1:27, Colin Law wrote:
On 11 July 2016 at 14:25, RS wrote:
The release of v2.95 seems to have had quite an impact on hlshd download
speeds.
I cannot see that the release of v2.95 can have any impact if you are
not actually using that version. I would assume it is just
co-in
On 11 July 2016 at 14:25, RS wrote:
> The release of v2.95 seems to have had quite an impact on hlshd download
> speeds.
I cannot see that the release of v2.95 can have any impact if you are
not actually using that version. I would assume it is just
co-incidence.
From: tellyaddict
Sent: Monday, July 11, 2016 20:33
The Pure Perl HLS Downloader that is now built into 2.95 is much faster
than downloading with FFMpeg.
Thanks, I'll give it a try. I was just surprised at such a dramatic
reduction in speed for ffmpeg.
__
The Pure Perl HLS Downloader that is now built into 2.95 is much faster than
downloading with FFMpeg.
> Sent: Monday, July 11, 2016 at 4:59 PM
> From: RS
> To: get_iplayer@lists.infradead.org
> Subject: Re: hlshd download speeds
>
> -Original Message-
> From:
The timestamp of the dev version I am referring to is 14 Feb 2016 at 2305.
The Perl includes this
# require ffmpeg for HLS
if ( $mode =~ /^(hls|hvf)/ && (! main::exists_in_path('ffmpeg')) ) {
if ( $opt->{hlsffmpeg} ) {
main::logger "\nWARNING: --hls-ffmpeg specified and required
ffmpe
-Original Message-
From: James Scholes
Sent: Monday, July 11, 2016 15:35
This is probably caused by the switch to using a built-in HLS/DASH
downloader, rather than FFmpeg.
Sorry, when I said I hadn't changed anything I meant I hadn't changed
anything. I have not installed the relea
RS wrote:
> The release of v2.95 seems to have had quite an impact on hlshd download
> speeds.
This is probably caused by the switch to using a built-in HLS/DASH
downloader, rather than FFmpeg. I haven't looked at FFmpeg's download
code, but I would imagine it is multithrea
The release of v2.95 seems to have had quite an impact on hlshd download
speeds. I have been using a dev version of 2.95 for some time. I am not
sure which one, but I haven't changed anything so I am comparing like with
like. With Vista I was regularly getting hlshd download speeds of
24 matches
Mail list logo
