Foobar doesn't use this extended playlist format, because it can only record time, artist and title in ambiguous fashion, and not other metadata fields.
I'm trying to use epsil's spotgen to convert Foobar playlists I have into Spotify playlists and the .m3u playlists are formatted differently than what it needs.
This is from the web demo--
"One can also import M3U playlists (with the file extension .m3u or .m3u8), provided they contain EXTM3U metadata. That is, the playlist should be on the form":
#EXTINF:404,Desire Lines - Deerhunter
Deerhunter/Halcyon Digest/06 Desire Lines.mp3
#EXTINF:230,Saved By Old Times - Deerhunter
Deerhunter/Microcastle/10 Saved By Old Times.mp3
#EXTINF:202,Agoraphobia - Deerhunter
When I create .m3u playlists and then open them up in notepad to copy them, they look like this:
E:\Dj Music\10 Farewell Track.mp3
E:\Dj Music\07 Clark - Snowbird.mp3
E:\Dj Music\4-22 Bad Dream.mp3
E:\Dj Music\6-07 Moving Glowstream (Amon Tobin R.mp3
E:\Dj Music\05 Northern Plastics.mp3
E:\Dj Music\05 Boc Maxima.mp3
E:\Dj Music\09 Niagra.mp3
E:\Dj Music\1-09 Bocuma.mp3
E:\Dj Music\1-13 Olson.mp3
E:\Dj Music\08 Sherbet Head.mp3
I have all of the track/album/artist info in Foobar before I export. How does that get tacked onto the .m3u info, along with the omission of the file location?
Edit: Here's the app, which I don't understand how to use!
Well, you are free to speculate about stuff that doesn't matter much if any, but for me, it's the stuff that does matter, as in #1:
OK, you misunderstand me a bit. I'm not speculating, I'm curious. I'm starting from the assumption that they DID solve this problem of driver linearity and I'd like to understand it a little bit, just like we do regular drivers. And I'd gently point out that perhaps the reason you don't have to worry about it is that conventional driver technology is fairly mature. I think you have to go pretty far down the scale nowadays to find a truly badly misdesigned driver product--do you agree?
Are your speaker designs not conventional ported? I have AR and have for years...
these are my coponents
Core (2018-07-24 10:54:48 UTC)
foobar2000 core 1.4
foo_albumlist.dll (2018-07-24 10:54:02 UTC)
Album List 4.6
foo_cdda.dll (2018-07-24 10:54:04 UTC)
CD Audio Decoder 3.0
foo_chacon.dll (2016-12-26 05:13:12 UTC)
foo_comserver2.dll (2006-07-31 19:13:20 UTC)
COM Automation server 0.7 alpha 6
foo_converter.dll (2018-07-24 10:54:04 UTC)
foo_discogs.dll (2018-09-20 04:43:43 UTC)
Discogs Tagger 2.14
foo_dop.dll (2011-06-28 17:25:35 UTC)
iPod manager 0.6.9.7
foo_dsp_bs2b.dll (2009-06-08 16:30:06 UTC)
foo_dsp_eq.dll (2018-07-24 10:53:56 UTC)
foo_dsp_soundtouch.dll (2018-02-02 08:01:53 UTC)
SoundTouch DSP 0.1 (SSE)
foo_dsp_std.dll (2018-07-24 10:53:58 UTC)
Standard DSP Array 1.3.1
foo_facets.dll (2011-08-19 00:06:16 UTC)
foo_fileops.dll (2018-07-24 10:54:00 UTC)
File Operations 2.3
foo_freedb2.dll (2018-07-24 10:54:14 UTC)
Online Tagger 0.7
foo_input_dts.dll (2017-09-24 01:12:30 UTC)
DTS decoder 0.5.3
foo_input_monkey.dll (2016-06-30 04:04:42 UTC)
Monkey's Audio Decoder 2.1.7
foo_input_sacd.dll (2016-08-01 03:43:48 UTC)
Super Audio CD Decoder 0.8.4
foo_input_std.dll (2018-07-24 10:54:34 UTC)
FFmpeg Decoders 3.2.4
Standard Input Array 1.0
foo_input_tak.dll (2016-08-22 12:09:51 UTC)
TAK Decoder 0.4.7
foo_rgscan.dll (2018-07-24 10:54:10 UTC)
ReplayGain Scanner 2.3
foo_run.dll (2016-06-30 04:27:14 UTC)
Run services 0.3.7
foo_textdisplay.dll (2016-06-30 00:04:14 UTC)
Text Display UI Element 1.1 beta 1
foo_ui_std.dll (2018-07-24 10:54:14 UTC)
Default User Interface 0.9.5
foo_uie_albumlist.dll (2017-01-13 19:18:38 UTC)
Album list panel 0.3.7
foo_uie_biography.dll (2010-12-11 13:47:22 UTC)
Biography View 0.4.2.4
foo_uie_graphical_browser.dll (2017-01-17 21:51:43 UTC)
Graphical Browser rev015
foo_uie_panel_splitter.dll (2009-12-09 20:16:12 UTC)
Panel Stack Splitter 0.3.8.3(alpha)
foo_unpack.dll (2018-07-24 10:54:08 UTC)
ZIP/GZIP/RAR Reader 1.8
Foobar version 1.4
process monitor log....I don't know how to make a log that will not be 200meg
Only £1,555 for pleasure of no pops and clicksThe price probably isn't out-of-line, if you need such a thing... It's expensive to design, manufacturer, market, and distribute in small quantities. Plus, you don't want to sell it too cheap! Audiophiles don't like cheap stuff... The more it costs the more they want it! (And, I assume this is for audiophiles.)
I'd probably pay that if we didn't have digital! I spent a lot of money replacing my records with CDs for the same reason... So I didn't have to listen to record noise.
Thanks for the read. I agree with the conclusions, especially #3, which is relevant here.Well, you are free to speculate about stuff that doesn't matter much if any, but for me, it's the stuff that does matter, as in #1:
The design of the big pumpkin on the MBLs uses aluminum strips, flexed and then "filled" with rubbery pieces glued in. You've never seen an aluminum spring, have you? There's a reason! Every conventional speaker has a spring force that returns the cone (or equivalent) to the center position. It's only on midrange and lower drivers that you can demonstrate this with your fingers, but on the MBLs, the big pumpkin goes down to about 100 Hz. I'm wondering what the spring force is and if it is linear.
1. The perception of loudspeaker sound quality is dominated by linear distortions, which can be accurately quantified and predicted using a set of comprehensive anechoic frequency response measurements (see my previous posting here)The data we have shows a rather uniform polar is expected.
That's actually remarkably uniform. Passive speaker too, a touch of DSP eq would make things even smoother. I think that's rather impressive engineering, not much else out there that can generate such a uniform field.
I've also done the Harman training (coupled with 40 yrs of speaker building, Klippel training, etc), so I'm not too shabby at detecting resonances. The MBLs do ok. Whatever your concern is about theoretical "aluminum springs" etc, I don't share them, as I'm only concerned with what matters most audibly. Again, the MBLs are certainly "audiophile" priced, but in a rarity, there is actually some clever engineering going on. Yes they are going to be sold by folks who sell a lot of unadulterated nonsense also.
I found the midbass consistently unpleasant and boomy, however. This was a demo in a listening room, so I would have expected them to be at their best, but I'm probably wrong about that too!Yes, that would be my only quibble, I find the bass quality to be sub-par to terrible, but that is true for about 95% of speakers (which are also ported boxes in rooms), for my tastes.
Unfortunately 30k cables won't solve that, but I'm sure he sells "traps" too.
Unfortunately, I'm bound by the current design of the panel API. All of the data for a panel is managed by its parent panel, and I can't see trying to augment that data in Columns UI working.
That's a shame... I should harass @Peter about it next