You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed a strange behavior with the File Sink plugin on my machine, which runs Windows 11. My user account was created as C:\Users\firstname.lastname, so for instance my downloads folder is C:\Users\firstname.lastname\Downloads. Unfortunately, it looks like SDR Angel is splitting the file extension using the first instance of a . character instead of the last instance of a . character, so when I try to save a file to C:\Users\firstname.lastname\Downloads\testfile.sdriq, I get an error that SDR Angel is unable to open the file C:\Users\firstname.2023-08-04T23_27_22_906.sdriq, which is of course in a nonexistent directory.
I have gotten around this issue for now by recording everything directly to my C:\ drive, but it would be really nice if I was able to record files directly to folders associated with my user account!
The text was updated successfully, but these errors were encountered:
Version Info
SDR Angel 7.15.2
Windows 11 Pro Version 22H2
Problem Description
I noticed a strange behavior with the File Sink plugin on my machine, which runs Windows 11. My user account was created as
C:\Users\firstname.lastname
, so for instance my downloads folder isC:\Users\firstname.lastname\Downloads
. Unfortunately, it looks like SDR Angel is splitting the file extension using the first instance of a.
character instead of the last instance of a.
character, so when I try to save a file toC:\Users\firstname.lastname\Downloads\testfile.sdriq
, I get an error that SDR Angel is unable to open the fileC:\Users\firstname.2023-08-04T23_27_22_906.sdriq
, which is of course in a nonexistent directory.I have gotten around this issue for now by recording everything directly to my
C:\
drive, but it would be really nice if I was able to record files directly to folders associated with my user account!The text was updated successfully, but these errors were encountered: