|
|
Post by w3wilkes on Apr 19, 2021 17:27:45 GMT -5
A while back you fixed some stuff so I could get rid of BOM in ANSI ( link) files since the recommendation is to not use BOM for ANSI files. I have a profile for .m3u files that says ANSI and BOM is not checked. When I go to edit a *.m3u file now I get errors. My playlist generator creates playlists that are UTF8 with BOM and names them with the .m3u suffix. Now on open I get 2 warnings; Warning, current SOURCE is ANSI, file loaded was UTF8
Warning, Profile EOL is set to CRLF, file loaded was LFThen when I try to save after editing in SPFLite I expect the file to be saved as ANSI with no BOM like I have set in the profile for m3u file types. This used to work right after you implemented the change I requested. Now the save fails with these errors. File OPEN failed
File Abbey Road Medley not written
File not saved, was not modified
Multiple messages were triggered, press F1 (Help) to see themDid this get messed up sometime between then and now? Thanks, Wilkes Attachments:
|
|
|
|
Post by George on Apr 21, 2021 8:37:32 GMT -5
Wilkes: OK, I tried your scenario. I used a UTF8 file which HAD a BOM, and used LF as line delimiters.
The Profile had SOURCE UTF8, EOL CRLF, and BOM OFF.
File loaded fine, got only 1 message, the EOL mismatch one. You got 2 msgs, what SPFLite Version are you using?
Saved as a new file and correctly got a UTF8 file, no BOM, with CRLF line delimiters. No error messages.
George
|
|
|
|
Post by w3wilkes on Apr 21, 2021 9:38:08 GMT -5
George,
The difference is my profile for *.m3u files is SOURCE ANSI as that's how I want the file saved. All else including the original file type is as you said.
My version is 21104.
Wilkes
|
|
|
|
Post by George on Apr 21, 2021 9:50:51 GMT -5
OK, somehow missed that, I'll try again.
George
Tested. It writes a perfectly normal ANSI file with CRLF delimiters. I get no errors.
Send me your CFG file, I'll test with that.
George
|
|
|
|
Post by w3wilkes on Apr 21, 2021 10:38:49 GMT -5
Here's what you asked for and then some. Hopefully I found the .cfg file. I also attached the export and my original file I edited to get the error. Here's how I edit the file in SPFLite; X ALL F #EXT all DEL NX all RES C 'D:\MP3 Music\' '' all SAVE The intent is to get rid of the "playlist comments" and change it from explicit location to relative location so that my playlists work across all my devices / platforms. |
|
|
|
Post by George on Apr 21, 2021 12:08:33 GMT -5
OK, thanks for the test files. Sad to say, this is what I get  Got to be something local to your system, file access rules etc. George |
|
|
|
Post by w3wilkes on Apr 21, 2021 13:47:09 GMT -5
Really strange, tried SAVEAS and it fails regardless of where I try to save it. I can edit and save just fine with Notepad and Notepad++. I tried deleting the m3u profile and recreating and still no luck. At this point I'm kind of at a loss.
|
|
|
|
Post by George on Apr 21, 2021 14:52:54 GMT -5
Wilkes: Tried it all again, doing a SAVEAS rather than a simple SAVE. No difference.
I'm just as puzzled as you are.
You say the file was downloaded. Do a File Properties for the file, look at the General tab and see if at the bottom is says the file is 'Blocked' along with an offer to UnBlock it.
I'm grasping here.
George
[UPDATE]
I just checked the test file you sent. it IS blocked.
[\UPDATE]
|
|
|
|
Post by w3wilkes on Jun 1, 2021 15:19:01 GMT -5
Just an FYI update on this. I never figured out what the problem was. I could edit/save with Notepad and Notepad++, but always got the error with SPFLite. A couple of days ago Windows Update offered up the 21H1 release so I went ahead and installed it. Viola, SPFLite can once again edit/save/saveas for my playlists on my "D:\Music" folder. Nothing else changed. D: is a physically separate internal drive, not the system drive. Go figure! :-)
|
|
|
|
Post by George on Jun 5, 2021 12:17:27 GMT -5
I'm never surprised with what a Windows update will do. Recently, my Win10 system (which never goes to sleep itself) simply refused to put my screen to sleep, which it had been doing nicely for years. All power settings were checked and were still set correctly. This went on for about 3 weeks, and then magically 'self healed'.
Exactly - go figure!
|
|
