Serious flaw in program

art2work4 wrote on 10/7/2020, 2:36 AM

I discovered a serious issue with SF Audio Cleaning lab. When opening audio files in the program, it will create a HM0 file. In these small files the peaklevel and audio waveform data is saved for the audio file that was opened.

So far so good, HOWEVER the program will always save the HM0 file in the original location of the audio file that was opened. And that creates issues !!!!!!!!!!!!!!!!!!!!

For instance I have loads of FLAC files on a NAS. For security reasons the folders are all "read-only". However SF ACL tries to save the HM0 files all the time in the originating folder, which is read-only, so the result is that I can't use the program to edit audio files.

PLEASE implement something so the user can determine in which file location the HM0 should be stored. Since there always is a Project file, there is no need to always save them in the original audio file location. After all the Project file can point to the location of the HM0 files

Comments

emmrecs wrote on 10/7/2020, 4:19 AM

@art2work4

Please remember these are user to user forums, not a contact for any Magix employee so I doubt that your pleas will be read by anyone in a position to make any change of this nature!

I have to say, speaking personally, I don't find the behaviour you are commenting on as a "flaw"! Every audio editing program I have stores any associated data files directly with the original audio file. This is to ensure that the program can easily "find" them again and so not have to recreate them if/when the audio file is re-opened.

At least one program I use does allow the user to specifically NOT save the associated data file; I don't think SFACL has that option.

Two questions:

  1. Which version of SFACL are you running, 1 or 2?
  2. I assume you are "editing" your FLAC files. Is that correct? If so, since they are in folders which are "read-only", how can any audio editing app save them back to their original location? I assume you must be putting them through some kind of intermediate process in order to save them on the NAS. If so, what?

Jeff

Win 10 Pro 64 bit, Intel i7 Quad Core 6700K @ 4GHz, 32 GB RAM, AMD Radeon R7 360 and Intel HD530 Graphics, MOTU 8-Pre f/w audio interface, VPX, MEP, Music Maker, Photo Story Deluxe, Photo Manager Deluxe, Xara 3D Maker 7, Reaper, Adobe Audition CS6 and CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D

johnebaker wrote on 10/7/2020, 4:29 AM

@art2work4

Hi

. . . . a serious issue . . . . . For security reasons the folders are all "read-only" . . . .

There are a lot of programs that create supplementary and temporary files in the same folder as the file being read so I would not call this a serious issue, more of an permissions issue

A common practice is to make the folder permissions Read/Write only for Authenticated user, Users or a User security group, with inheritance disabled and the files within them Read only.

John EB

Lateral thinking can get things done!

VPX 12, MEP Premium 2021, and earlier versions 2015 and 2016, Music Maker Premium 2021.

Running Windows 10 Professional 20H2 64bit on Intel i7-8700K 3.2 GHz, 16GB RAM, 3 x 2Tb internal HDD + 60GB internal SSD, + 6 ext backup HDDs, Sony FDR-AX53 Video camera, Contour HD 1080 and Sony HDR-AS30V Sports cams.

rraud wrote on 10/7/2020, 11:01 AM

I am not familiar with Sound Forge Audio Cleaning Lab but SF Pro creates a similar <.sfk> waveform file for fast opening. SF Pro has an option to "Hide new temporary files" so they are not visible. They can also be deleted without issue to the main audio file. I do not know if the ACL has the 'hide' option .. I do not know if the .hmo file is a project file or a waveform file. Waveform files can be deleted (or hidden) if they are an annoyance.

In any case, I do not consider it a "flaw" either.