bpa wrote:
> The things about AIFF is that it is PCM - uncompressed just different
> byte order to WAV. So swap the bytes and then pass straight to DAC. So
> in theory there is no processing difference between files or even
> between passages in a file. That is why theories about metadata were
drmatt wrote:
> I think I was meaning the past tense. Yes, I got that gist.
>
> Presumably its a super special extra hard to decode aiff. Or that
> particular sequence of ones and zeros is more prone to noise related
> errors than any other.]
The things about AIFF is that it is PCM -
bpa wrote:
> Late to the party. We went through lots of stuff and never figured out
> why this one AIFF file behaved differently to the rest.I think I was meaning
> the past tense. Yes, I got that gist.
Presumably its a super special extra hard to decode aiff. Or that
particular sequence of
Mnyb wrote:
> Yes I have a new router , however the old Squeezebox Touch OP is using
> is only compatible with older wifi standards and thus not as fast as one
> would like , besides squeezebox wifi have never been on top off things
> .
>
> So the 2003 aproach still has merit when using old
sgmlaw wrote:
> These WAV bandwidth and storage arguments are so 2003. Anyone having an
> issue moving a WAV stream around wirelessly in 2019 needs to get a new
> router.
>
> Most of these audio file formats and their resulting streams are a
> trickle compared to even a 1080i file video
sgmlaw wrote:
> These WAV bandwidth and storage arguments are so 2003. Anyone having an
> issue moving a WAV stream around wirelessly in 2019 needs to get a new
> router.
>
>
You're looking at the problem from the wrong end.
The router is not the issue.
The WiFi card in the Touch is. It is
drmatt wrote:
> We're getting pretty desperate here...!
>
>
> -Transcoded from Matt's brain by Tapatalk-
Late to the party. We went through lots of stuff and never figured out
why this one AIFF file behaved differently to the rest.
bpa wrote:
> I think the OP should at least check it out thge possibility by enabling
> logging player.source to INFO and see if LMS does something strange to
> the file.
>
> However - why would affect just one file amongst other similarly encoded
> files ?We're getting pretty desperate
sgmlaw wrote:
> These WAV bandwidth and storage arguments are so 2003. Anyone having an
> issue moving a WAV stream around wirelessly in 2019 needs to get a new
> router.
>
> Most of these audio file formats and their resulting streams are a
> trickle compared to even a 1080i file video
These WAV bandwidth and storage arguments are so 2003. Anyone having an
issue moving a WAV stream around wirelessly in 2019 needs to get a new
router.
Most of these audio file formats and their resulting streams are a
trickle compared to even a 1080i file video stream, let alone a 4k one.
Any
garym wrote:
> File seems normal. No odd tags. Embedded art is small (normal) size. I
> havent had chance to play via touch yet.
File plays fine, but it turns out I can't truly do a test on my end. My
players are all wired via ethernet. And even if I converted one to WIFI,
I don't use EDO on
sherington wrote:
> Same with me too - mind you, the AIFF file is over 9000kbps - even
> 'normal' high-res files at around 2000kbps often have an issue over
> wi-fi.
>
> I resampled it to 44kz with dBPoweramp to FLAC at level 5, it came down
> to 358kpbs so was easy to play over wi-fi.
>
>
Stratmangler wrote:
> I'm not sure about unnecessary rubbish being added - it's often dictated
> by the resolution something was recorded at digitally in the first
> place.
> If you're set up to record at 24/192, then your initial resolution is
> 24/192.
> Usually stuff gets very much reduced
sherington wrote:
> Same with me too - mind you, the AIFF file is over 9000kbps - even
> 'normal' high-res files at around 2000kbps often have an issue over
> wi-fi.
>
> I resampled it to 44kz with dBPoweramp to FLAC at level 5, it came down
> to 358kpbs so was easy to play over wi-fi.
>
>
Stratmangler wrote:
> The file plays fine when my Touch is wired.
> It buffers repeatedly when I switch to Wi-Fi.
Same with me too - mind you, the AIFF file is over 9000kbps - even
'normal' high-res files at around 2000kbps often have an issue over
wi-fi.
I resampled it to 44kz with
The file plays fine when my Touch is wired.
It buffers repeatedly when I switch to Wi-Fi.
Chris :)
Stratmangler's Profile: http://forums.slimdevices.com/member.php?userid=20387
View this thread:
File seems normal. No odd tags. Embedded art is small (normal) size. I
havent had chance to play via touch yet.
*Home:* VBA 4TB (2.4)>LMS 7.9.1>Transporter, Touch, Boom, Radio
(ethernet)
*Cottage:* VBA 3TB (2.4)>LMS 7.9.1>Touch>Benchmark DAC I, Boom, Radio
w/Battery (Radio WIFI)
*Office:*
Stratmangler wrote:
> I see that the file has embedded artwork.
> Have the rest of the files got the same embedded image?
The OP said he tried with a version of the file without artwork. Perhaps
it is worth checking the file again.
DBart wrote:
> I think this link should take you to my public Dropbox where the second
> movement is posted:
>
> https://www.dropbox.com/s/x1xvr4oc6j0vwnm/02%20Andante%20Moderato.aiff?dl=0
I see that the file has embedded artwork.
Have the rest of the files got the same embedded image?
DBart wrote:
> I think this link should take you to my public Dropbox where the second
> movement is posted:
>
Got it. I'll take a look next week when I return home.
*Home:* VBA 4TB (2.4)>LMS 7.9.1>Transporter, Touch, Boom, Radio
(ethernet)
*Cottage:* VBA 3TB (2.4)>LMS
I think this link should take you to my public Dropbox where the second
movement is posted:
https://www.dropbox.com/s/x1xvr4oc6j0vwnm/02%20Andante%20Moderato.aiff?dl=0
DBart's Profile:
garym wrote:
> Its a real mystery. Im very curious. Can the OP post the track
> somewhere so that others can test it on a different system. Dropbox,
> etc.
> p.s. I hope this is an enjoyable track, as much of a headache as its
> been.
Well, through some redecorating post-Christmas my
Stratmangler wrote:
> AIFF can be thought of as being WAV with knobs on.
> WAV capable of carrying metadata, something that WAV itself has
> difficulty with.
> So the files are bigger from the off.
> They're both PCM, and both have bandwidth hogging issues, which if not
> met causes
AIFF can be thought of as being WAV with knobs on.
WAV capable of carrying metadata, something that WAV itself has
difficulty with.
So the files are bigger from the off.
They're both PCM, and both have bandwidth hogging issues, which if not
met causes rebuffering.
The reason why FLAC was
drmatt wrote:
> Is the file being transcoded by lms? Delays during transcoding will also
> manifest as client buffering, iirc.
I think the OP should at least check it out thge possibility by enabling
logging player.source to INFO and see if LMS does something strange to
the file.
However -
Is the file being transcoded by lms? Delays during transcoding will also
manifest as client buffering, iirc.
-Transcoded from Matt's brain by Tapatalk-
--
Hardware: 3x Touch, 1x Radio, 2x Receivers, 1 HP Microserver NAS with
Debian+LMS 7.9.0
Music: ~1300 CDs, as 450 GB of 16/44k FLACs. No
JohnB wrote:
> Silly question: has the OP decoded the file and re-ncoded it with FLAC,
> compression level 0. If not I think that would be useful.
Yes and remove metadata and encoded into AIFF - every time the file
doesn't play - rebuffering
Silly question: has the OP decoded the file and re-ncoded it with FLAC,
compression level 0. If not I think that would be useful.
Touch, Meridian G92, Bryston B4 SST2, PMC OB1i speakers, HP Proliant
Microserver/Ubuntu, PC/Windows 7, iPad 4, iPeng, Squeezepad.
:rolleyes: I recall he may have tested with 24/96 and it worked fine.
p.s. if I have a choice on downloads I always buy 16/44.1. If not Ill
always choose 24/96 if I have a choice. Works with mt transporter and
touch. And its the *mastering* that matters anyhow.
drmatt wrote:
> Also. You
Also. You could always just downsample it to 16/44 and be done with
it.. :)
-Transcoded from Matt's brain by Tapatalk-
--
Hardware: 3x Touch, 1x Radio, 2x Receivers, 1 HP Microserver NAS with
Debian+LMS 7.9.0
Music: ~1300 CDs, as 450 GB of 16/44k FLACs. No less than 3x 24/44k
albums..
Its a real mystery. Im very curious. Can the OP post the track
somewhere so that others can test it on a different system. Dropbox,
etc.
p.s. I hope this is an enjoyable track, as much of a headache as its
been.
*Home:* VBA 4TB (2.4)>LMS 7.9.1>Transporter, Touch, Boom, Radio
(ethernet)
Yes I'm aware of aiff. It was the default audio file format on my SGI O2
... The implication of what's being discussed is that there is a *data*
dependency for this file. Something, very odd, about the audio data
itself is causing the Touch to require buffering whether it's played as
aiff (i.e.
DBart wrote:
> Yes - just bizarre it's with one file (well, 5 from the same recording)
> :-)
>
> Would there be a way that a studio, in this case ChannelClassics, would
> encode a file that would cause this to happen? All other 192 files were
> purchased from HDTracks and none of those exhibit
drmatt wrote:
> Flac encoders have changed over the years (though the files themselves
> are supposed to be the same format). Presumably the file plays fine if
> you decode it to wav/aiff and then re- encode to flac using a known
> encoder?
>
> In general no differences in compression
Flac encoders have changed over the years (though the files themselves
are supposed to be the same format). Presumably the file plays fine if
you decode it to wav/aiff and then re- encode to flac using a known
encoder?
In general no differences in compression methodology should result in a
flac
bpa wrote:
> While this may be a problem - it would not give rise to a "rebuffering"
> message from LMS
Yes - just bizarre it's with one file (well, 5 from the same recording)
:-)
Would there be a way that a studio, in this case ChannelClassics, would
encode a file that would cause this to
sgmlaw wrote:
> I assume you are running an outboard DAC off the Touch if this is a true
> 192 khz stream.
>
> What type of digital connection are you running? Toslink is more
> problematic and more prone to lose sync above 96 khz.
>
> If you can, use a 1.5 meter or longer coaxial connection
sgmlaw wrote:
> I assume you are running an outboard DAC off the Touch if this is a true
> 192 khz stream.
>
> What type of digital connection are you running? Toslink is more
> problematic and more prone to lose sync above 96 khz.
>
> If you can, use a 1.5 meter or longer coaxial connection
DBart wrote:
> Thanks - I'll give it a try. becoming a little project here :-)
I assume you are running an outboard DAC off the Touch if this is a true
192 khz stream.
What type of digital connection are you running? Toslink is more
problematic and more prone to lose sync above 96 khz.
If
bpa wrote:
> Touch 24/96 Flac files should play OK if wireless connection is good
> (i.e. strong signal, littler interference fom toehr networks and traffic
> levels moderate) but some suppliers use a high-ish compression level on
> Flac which can cause problems for Touch - to check you could
DBart wrote:
> Well, after changing the ID3 to 2.3 it still rebuffers. Even tried to
> play the original FLAC fields over the touch, and they do the same
> thing. May contact ChannelClassics if I'm so motivated. This just seems
> like an odd issue, but again, the 24/96 files stream fine, and
Yes, I agree. Again, thanks for all of your guidance in this project.
DBart's Profile: http://forums.slimdevices.com/member.php?userid=63836
View this thread: http://forums.slimdevices.com/showthread.php?t=109917
DBart wrote:
> Well, after changing the ID3 to 2.3 it still rebuffers. Even tried to
> play the original FLAC fields over the touch, and they do the same
> thing. May contact ChannelClassics if I'm so motivated. This just seems
> like an odd issue, but again, the 24/96 files stream fine, and the
Well, after changing the ID3 to 2.3 it still rebuffers. Even tried to
play the original FLAC fields over the touch, and they do the same
thing. May contact ChannelClassics if I'm so motivated. This just seems
like an odd issue, but again, the 24/96 files stream fine, and the files
play perfectly
DBart wrote:
> I'll look into some options and see what works.
>
> Again, thank you very much for talking me through this process. I really
> do appreciate it!
Happy to help.
*Home:* VBA 4TB (2.4)>LMS 7.9.1>Transporter, Touch, Boom, Radio
(ethernet)
*Cottage:* VBA 3TB (2.4)>LMS
garym wrote:
> Yes that file now has ID3v2.3 tag instead of the 2.4 tag you previously
> reported.
>
> Itunes wont play flac files. There are other players that will run on a
> Mac that will, but if you prefer iTunes you cant use flac. But yes,
> for squeezeboxes and LMS I find that flac
Yes that file now has ID3v2.3 tag instead of the 2.4 tag you previously
reported.
Itunes wont play flac files. There are other players that will run on a
Mac that will, but if you prefer iTunes you cant use flac. But yes,
for squeezeboxes and LMS I find that flac files are best for lossless
garym wrote:
> This is correct. So now Id do the AIFF conversions then see what tag
> type shows for them.
>
> ps. Remind me of why you want AIFF files instead of FLAC. Squeezeboxes
> handle FLAC files so much easier and better for network bandwidth,
> particularly for these hi-res files. Is
DBart wrote:
> Opened up an .m4a file and this is what it now says:
>
> 26375
This is correct. So now Id do the AIFF conversions then see what tag
type shows for them.
ps. Remind me of why you want AIFF files instead of FLAC. Squeezeboxes
handle FLAC files so much easier and better for
garym wrote:
> What you are seeing now is exactly correct. These are flac files and
> mp3tag is reporting correctly that there is a single metadata tag in
> each file (flac type tag) and mp3tag is reading that flac tag to report
> the tag fields (artist, album, etc). So all looks good so far.
DBart wrote:
> Ok - re copied and saved. it didn't show any extra spaces, but maybe
> something was there in the copy/paste. Boxes are goner, but still no
> other info.
>
> 26374
What you are seeing now is exactly correct. These are flac files and
mp3tag is reporting correctly that there is a
garym wrote:
> You probably copied in an extra space. Go back in to the value and
> delete any spaces at the end then save.
Ok - re copied and saved. it didn't show any extra spaces, but maybe
something was there in the copy/paste. Boxes are goner, but still no
other info.
26374
DBart wrote:
> Yes, all files are FLAC. I re-downloaded the files from the
> ChannelClassics website and am working on them in their original state.
> Will concert to AIFF if/when I get this thing going.
>
> I copied your Vale field exactly as you typed it. Did I moss something?
>
> Thanks
garym wrote:
> Correct but you may have some extra spaces after the contents of the
> column value entry. This is why you are getting the [] [] showing up.
> Also, are the files you have open in mo3tag all FLAC files?
Yes, all files are FLAC. I re-downloaded the files from the
ChannelClassics
Correct but you may have some extra spaces after the contents of the
column value entry. This is why you are getting the [] [] showing up.
Also, are the files you have open in mo3tag all FLAC files?
*Home:* VBA 4TB (2.4)>LMS 7.9.1>Transporter, Touch, Boom, Radio
(ethernet)
*Cottage:* VBA 3TB
garym wrote:
> 1. in mp3tag, right click on column heading area, then select CUSTOMIZE,
> then NEW to create a new column
> 2. in the popup box, give the new column heading the following info:
> Name: Tag Type
> Value: %_tag_read%[ (%_tag%)]
> leave field and sort by blank and do NOT tick
1. in mp3tag, right click on column heading area, then select CUSTOMIZE,
then NEW to create a new column
2. in the popup box, give the new column heading the following info:
Name: Tag Type
Value: %_tag_read%[ (%_tag%)]
leave field and sort by blank and do NOT tick "numeric"
3. in left side of
reinholdk wrote:
> For mp3 files you would chose settings like this:
>
> 26368
>
> then select the files, remove all tags and rewrite the v2 tags (X in
> menu bar, then undo). Undo would write only the v2 tags then. You can
> check the tag column in the main panel.
@reinholdk:
I believe I
For mp3 files you would chose settings like this:
26368
then select the files, remove all tags and rewrite the v2 tags (X in
menu bar, then undo). Undo would write only the v2 tags then. You can
check the tag column in the main panel.
slartibartfast wrote:
> Pretty sure mp3tag can do it. First remove the current tags and then
> write the correct version. The tag version is chosen in the settings.
>
> Sent from my SM-G900F using Tapatalk
@slartibartfast
Thanks for the info - downloaded mp3tag. Running it on a Mac, and the
DBart wrote:
> I checked out Tag, Max, Tag Editor, and XLD. I can't seem to find
> anything about changing the Tag Version. I'm probably missing something,
> but there doesn't seem to be a way to do it?
>
> The only way I seem to have of even identifying the Tag Version is by
> looking at the
garym wrote:
> There must be an option or setting in xld or max to use ID3v2.3 tags. Or
> maybe iTunes changed it. Look at all these until you can get it created
> as ID3v2.3 vs 2.4.
I checked out Tag, Max, Tag Editor, and XLD. I can't seem to find
anything about changing the Tag Version. I'm
DBart wrote:
> Downloaded as a FLAC file - used XLD and Max to convert to AIFF. Same
> result.
>
> Any tweaking of metadata was done through iTunes 12.9.2.5 - which was
> minimal, only adjusting the album title.
There must be an option or setting in xld or max to use ID3v2.3 tags. Or
maybe
garym wrote:
> Im away from computer. But what program did you use for converting this
> file to AIFF. What program do you normally use for tag editing.
Downloaded as a FLAC file - used XLD and Max to convert to AIFF. Same
result.
Any tweaking of metadata was done through iTunes 12.9.2.5 -
DBart wrote:
> Ok, cool - how might I go about doing that?
Im away from computer. But what program did you use for converting this
file to AIFF. What program do you normally use for tag editing.
*Home:* VBA 4TB (2.4)>LMS 7.9.1>Transporter, Touch, Boom, Radio
(ethernet)
*Cottage:* VBA 3TB
garym wrote:
> The bad file has a ID3 ver 2.4 tag while the good file has a ID3 ver 2.3
> tag. Convert the 2.4 tag to 2.3 and see if that works. Not sure, but
> mp3tag may handle AIFF files and can convert tag versions.
Ok, cool - how might I go about doing that?
DBart wrote:
> Checked out the "bad" file (Mahler 2) and a "good" file (Mahler 9).
> Here's what is says:
>
> 2635726358
The bad file has a ID3 ver 2.4 tag while the good file has a ID3 ver 2.3
tag. Convert the 2.4 tag to 2.3 and see if that works. Not sure, but
mp3tag may handle AIFF files
bpa wrote:
> Can you just check what LMS thinks the format of the bad file compared
> to a good file (i.e. drill down on WegGUI to track leve linfo) - File
> format, bit rate, sample rate etc. just in case LMS is doing something
> special for the "bad" file
Checked out the "bad" file (Mahler
DBart wrote:
> Yes, I tried a wired connection (it's above somewhere in the thread).
> That worked without a hitch. However, due to location it is not a
> permanent option.
>
> Again, not a serious problem by any means as my 24/96 version of the
> file player just fine. Just curious how one
bpa wrote:
> Have you tried the original advice - a wired connection ?
>
> AIFF is uncompressed so encoding cannot vary between files. It looks
> like a network issue but could be a combination of things.
>
> Native ALAC support in Touch was dodgy/incomplete and so by default was
> disabled
DBart wrote:
> Thanks to all for your replies to this question. Removed the artwork,
> still no go. Replaced it with an image that was very small, still no
> improvement. Not sure what else to do with the metadata. It's an AIFF
> file, like all of my other 192 files. It's the only one i
Try FLAC ?
My experience with Touch is that , your lucky if 24/96 works on wifi
without some dropouts now and then . Innthe end i wired the Touch ( and
the server is ofcourse wired )
Main hifi: Touch + CIA PS +MeridianG68J
Thanks to all for your replies to this question. Removed the artwork,
still no go. Replaced it with an image that was very small, still no
improvement. Not sure what else to do with the metadata. It's an AIFF
file, like all of my other 192 files. It's the only one i downloaded
from the
Just a side comment: I understand that your other 24/192 files play
correctly, but keep in mind that you're playing 192000*3*2*8 =
9.2Mbits/s on a medium whose theoritical raw max speed is 54Mbps, and a
real max speed with 1500bytes MTU of 31.4Mbits/s
DBart wrote:
> Thank you both for your replies. Ran a length of Ethernet cable to the
> Touch and the file in question plays without hiccup. Now my question is:
> why would one 192 file not play when all others are fine by wireless?
> Its just puzzling is all. Connecting the Touch by Ethernet
Is there embedded artwork? I recall a situation long ago that turned out
to be a gigantic size embedded art.
*Home:* VBA 4TB (2.4)>LMS 7.9.1>Transporter, Touch, Boom, Radio
(ethernet)
*Cottage:* VBA 3TB (2.4)>LMS 7.9.1>Touch>Benchmark DAC I, Boom, Radio
w/Battery (Radio WIFI)
*Office:*
Thank you both for your replies. Ran a length of Ethernet cable to the
Touch and the file in question plays without hiccup. Now my question is:
why would one 192 file not play when all others are fine by wireless?
Its just puzzling is all. Connecting the Touch by Ethernet is not.
Permanent
@DBart
Also try;
Playing the file in another player
reconverting the file in question
and check the tagging
ronnie
Man in a van's Profile: http://forums.slimdevices.com/member.php?userid=43627
View this thread:
Run it on ethernet.
Chris :)
Stratmangler's Profile: http://forums.slimdevices.com/member.php?userid=20387
View this thread: http://forums.slimdevices.com/showthread.php?t=109917
Hello,
Squeezebox Touch streaming wirelessly to iMac running Mojave. Using the
Enhanced Digital applet for 192 playback. I have one 24/192 file that
simply will not playback without constant rebuffing. All other 24/192
files playback without issue. I have re-downloaded the file several
times
80 matches
Mail list logo
