>
> Many portable players have limited fast forward
>and skipping capabilities so it makes it easier to skip to a file part way
>through to resume listening.
>
Hi
I only split the files because my mp3 player won't play m4a files with duration
greater than 30 minutes.
But yes, I agree, even if
From: batguano999
Sent: Friday, January 27, 2017 09:38
So you could probably download a m4a radio show that is not longer than
1800 seconds...
get_iplayer --force --mode=dashhigh --raw --type=radio url=
Then de-mux it...
ffmpeg -i foo.m4a -c copy foo.aac
Then re-mux it...
mp4creator
Hi Vangelis
On 26/01/17 23:46, Vangelis forthnet wrote:
On Thu Jan 26 18:45:27 GMT 2017, Budge wrote:
How do I add "hafbest" to my prefs. Tried the obvious prefs-add
radiomode=hafbest but that gave me a search option!!! Grateful for
some guidance please.
get_iplayer --radiomode=hafbest
>The resultant file with a duration of 1800s
>(30min) did play on the AGPtEK player, but durations of 1900s and more did
>not play. That is an improvement on 14min
>
So you could probably download a m4a radio show that is not longer than 1800
seconds...
get_iplayer --force --mode=dashhigh
From: batguano999
Sent: Wednesday, January 25, 2017 15:50
The next question is how to convert AVC3 to AVC1 or AAC. I have already
tried using ffmpeg and its aac codec. It was very slow and I still
couldn't
play the file. I have also tried the Nero encoder
This is pointless.
If you're
On Thu Jan 26 18:45:27 GMT 2017, Budge wrote:
How do I add "hafbest" to my prefs.
Tried the obvious prefs-add radiomode=hafbest
but that gave me a search option!!!
Grateful for some guidance please.
get_iplayer --radiomode=hafbest --prefs-add
should do it...
On 26/01/17 17:11, iz wrote:
Sent: Thursday, January 26, 2017 at 4:36 PM
From: Budge
profile" error with this file. I am using ffmpeg v3.2-6.5 but I do not
think it is an ffmpeg fault. There was an update on my system on 17
ffmpeg 3.2 may be the culprit. That particular version caused a
> Sent: Thursday, January 26, 2017 at 4:36 PM
> From: Budge
>
> profile" error with this file. I am using ffmpeg v3.2-6.5 but I do not
> think it is an ffmpeg fault. There was an update on my system on 17
ffmpeg 3.2 may be the culprit. That particular version caused a problem with
remuxing
On 26/01/17 15:47, RS wrote:
From: Budge Sent: Thursday, January 26, 2017 11:01
I have not seen the Unknown profile message.
Try AtomicParsley -T 1
I have not seen that message. It may be that the files I have looked at
have been older than 17 Jan. To make sure I had something up to
From: Budge Sent: Thursday, January 26, 2017 11:01
I have not seen the Unknown profile message.
Try AtomicParsley -T 1
I have not seen that message. It may be that the files I have looked at
have been older than 17 Jan. To make sure I had something up to date I
tried it with today's
On 23/01/17 11:45, Budge wrote:
[snip]
... when I
chased Linn this is relevant part of the reply:-
"The issue is heavily influenced by but not directly related to track
duration. (Possibly too much technical detail - it's caused by the
number of entries in the 'stsz' table. Problem files have
On 25/01/17 00:21, RS wrote:
From: Budge Sent: Tuesday, January 24, 2017 10:38
I have not seen the Unknown profile message.
Try AtomicParsley -T 1
___
get_iplayer mailing list
get_iplayer@lists.infradead.org
>
>The next question is how to convert AVC3 to AVC1 or AAC. I have already
>tried using ffmpeg and its aac codec. It was very slow and I still couldn't
>play the file. I have also tried the Nero encoder
>
>
This is pointless.
If you're converting from lossy to lossy aac you might as well
> Sent: Wednesday, January 25, 2017 at 11:46 AM
> From: RS
>
> It seems that DASH is not simply AAC. The adaptive bit rate may be what is
> causing Linn to complain about the size of the stsz table.
"Adaptive bit rate" isn't an inherent property of a stream or the resulting
file. That phrase
From: Budge Sent: Tuesday, January 24, 2017 10:38
Have you looked at your files with AtomicParsley to see if you get the
message I get "MPEG-4 Unknown profile" on your problem files? It would be
good to learn if we have the same problem. This is no longer a long file
problem.
Thanks for
On 23/01/17 23:41, RS wrote:
From: batguano999
Sent: Monday, January 23, 2017 17:51
To check whether your version of FFmpeg creates m4a files that play
nice with the Linn...
Create some test files with different durations... 15 minutes, 30
minutes, 60 minutes etc. up to 3 hours.
If they all
>
>What does it mean if the shorter M4A/AAC files play but longer ones don't,
>because that is the situation I have? I can get the files to play if I run
>mp4box, which introduces 500ms interleaving, but only for files up to about
>14min.
>
>Do you have any suggestions for multiplexers which
From: batguano999
Sent: Monday, January 23, 2017 17:51
To check whether your version of FFmpeg creates m4a files that play nice
with the Linn...
Create some test files with different durations... 15 minutes, 30 minutes,
60 minutes etc. up to 3 hours.
If they all play OK then you can
On 23/01/17 19:21, batguano999 wrote:
To emulate the BBC files the command would be like this...
ffmpeg -f lavfi -i sine=d=900 -y -c:a aac -b:a 320k -ac 2 -ar 48000
320k_900_FFmpeg.m4a
Thanks. I have run 900 second and 3600 seconds. Not a hint of any
problem:-
AtomicParsley version:
>
>
>I would point out however that these files are mono at about 70 kbp/s
>
To emulate the BBC files the command would be like this...
ffmpeg -f lavfi -i sine=d=900 -y -c:a aac -b:a 320k -ac 2 -ar 48000
320k_900_FFmpeg.m4a
___
get_iplayer
On 23/01/17 17:51, batguano999 wrote:
Trouble is, if this is due to ffmpeg update, I have no idea when change
took place but certainly within the last week or so. (Or on reflection
was it when I upgraded from openSUSE 42.1 to 42.2??? Groan) How can I
find that info on my system? That would at
>
>Trouble is, if this is due to ffmpeg update, I have no idea when change
>took place but certainly within the last week or so. (Or on reflection
>was it when I upgraded from openSUSE 42.1 to 42.2??? Groan) How can I
>find that info on my system? That would at least enable me to test and
On 23/01/17 17:24, RS wrote:
From: Budge
Sent: Monday, January 23, 2017 11:45
You will have to ask somebody who knows about these things but when I
chased Linn this is relevant part of the reply:-
"The issue is heavily influenced by but not directly related to track
duration. (Possibly
From: Budge
Sent: Monday, January 23, 2017 11:45
You will have to ask somebody who knows about these things but when I
chased Linn this is relevant part of the reply:-
"The issue is heavily influenced by but not directly related to track
duration. (Possibly too much technical detail -
On 23/01/17 15:36, batguano999 wrote:
Hi
I think that your problems are caused because the aac files muxed by FFmpeg
into m4a when using get_iplayer are not compatible with your Linn DS devices.
This is also the case with some other hardware players. I know from personal
experience.
Linn
Hi
I think that your problems are caused because the aac files muxed by FFmpeg
into m4a when using get_iplayer are not compatible with your Linn DS devices.
This is also the case with some other hardware players. I know from personal
experience.
Linn have told you "...the problems are caused
[snip]
What I haven't yet understood, both from the problem you have and the
problem I have, is why it is more difficult for a player to play a long
piece in AAC than in other formats. I thought this was something
segmentation and fragmentation was supposed to deal with, to facilitate
Can't solve your problem, but if you have some Linn stuff you don't want
I might make you an offer. OT for this list I know.
M
On 01/18/2017 12:50 PM, RS wrote:
From: Budge
Sent: Sunday, January 15, 2017 13:11
The issue could be that Linn's player doesn't have enough memory to
read the
Thank you for the suggestion Richard, one of several I have received.
Of course I could re code these files and I am sure I would not be able
to hear any differences between file formats. These types of argument
have been well explained here
From: Budge
Sent: Sunday, January 15, 2017 13:11
The issue could be that Linn's player doesn't have enough memory to read
the sample tables from the file's MP4 container, so it refuses to play
the file. If >>so, splitting the file or transcoding to FLAC are probably
the best options.
Hi Richard,
On 14/01/17 15:20, iz wrote:
Sent: Saturday, January 14, 2017 at 12:05 PM
From: RS
always suspicious of people who refer to "chunks" when there is a recognised
I suspect they are using "chunk" from MP4 parlance, though a chunk contains multiple
audio blocks ("samples" in MP4).
> Sent: Saturday, January 14, 2017 at 12:05 PM
> From: RS
>
> always suspicious of people who refer to "chunks" when there is a recognised
I suspect they are using "chunk" from MP4 parlance, though a chunk contains
multiple audio blocks ("samples" in MP4).
> Does the Linn play all the files
From: iz
Sent: Friday, January 13, 2017 20:19
In this case, you only need arithmetic. AAC uses a fixed number of samples
per frame (the "1024 spf" you see in the frame rate in MediaInfo output),
so the >total number of frames is basically a function of sample rate and
programme duration.
> Sent: Thursday, January 12, 2017 at 3:30 PM
>
> My question is with what does one look at a file to find out this info.
> I tried mediainfo and am none the wiser. What tool gives me the detail
> to which Linn referred?
In this case, you only need arithmetic. AAC uses a fixed number of
On 13/01/17 00:24, RS wrote:
From: Budge Sent: Thursday, January 12, 2017 18:26
Many thanks. Yes I agree ffmpeg was my first thought but I am spoiled
for choice of command options. ffprobe output didn't tell me what I
was looking for although that may be due to me not understanding what
I
From: Budge Sent: Thursday, January 12, 2017 18:26
Many thanks. Yes I agree ffmpeg was my first thought but I am spoiled for
choice of command options. ffprobe output didn't tell me what I was
looking for although that may be due to me not understanding what I was
looking at. However I
On 12/01/17 16:14, Jim web wrote:
In article <37968d10-ab7a-f131-e07d-00b58cc2a...@errichel.co.uk>, Budge
wrote:
On 10/01/17 22:48, Budge wrote: [snip] Linn advised thus.
As a workaround for now, you could convert the file to a different
format. I've checked that it
In article <37968d10-ab7a-f131-e07d-00b58cc2a...@errichel.co.uk>, Budge
wrote:
> On 10/01/17 22:48, Budge wrote: [snip] Linn advised thus.
> >>> As a workaround for now, you could convert the file to a different
> >>> format. I've checked that it plays after converting to
On 10/01/17 22:48, Budge wrote:
[snip]
Linn advised thus.
As a workaround for now, you could convert the file to a different
format.
I've checked that it plays after converting to either FLAC or ALAC using
dbpoweramp.
You might even find that just re-writing it as AAC fixes things - the
Hi and many thanks for the info. I shall play around with Handbrake and
ffmpeg and see which gives the best result.
I find it significant that this is only a problem with larger files. I
wonder what the size threshold is and why.
Will report back. Also need to see how to automate the
On 2017-01-10 14:24, artisticforge . wrote:
While researching the cause it became apparent that the files were
thousands of small chunks.
I have found that running them through Handbrake "fixes" them.
i do not see anything that get_iplayer may do to alleviate the
problem. this is a BBC issue.
hello
I have noticed this also. iTunes would not import audio & video files
into the iTunes Library.
While researching the cause it became apparent that the files were
thousands of small chunks.
I have found that running them through Handbrake "fixes" them.
i do not see anything that get_iplayer
I have recently had trouble playing radio 3 operas on my Linn devices.
These files used to play although there were problems. They play well
on my RPi3 with IQaudIO DAC+ amd upmpdcli gapless player software.
(Totally brilliant setup which enables me to use excellent power
amplifiers which
43 matches
Mail list logo