I’ve started the trial, set up a Radeon RX Vega for the AI calculations, and the paths point to directories on a RAM disk. When I try to calculate something, I’m informed that there’s less than 200MB somewhere. This doesn’t help me much as I don’t know where to look or change settings to advice spectralayers to use the abundance of memory in the system.
There it goes, my testing time. Slowly but …
I would be grateful for suggestions on what I need to change so that I can start testing.
This refer to the Cache folder defined in Edit > Preferences > System, which by default is on the C: drive :
If the drive on which the Cache folder is set has less than 200MB free, this warning will be shown. You can change the Cache folder to a folder on another drive though.
Yes, that’s what I thought too. I checked before posting. It would be nice if the description also informs about the path.
There is plenty of space.
It could be due to OSFMount (RAMDisk) behavior in logical emulation mode. The drive letter is shown in Explorer, but not in Task Manager, Resource Manager, or Disk Management.
The various characters “\” or “/” in the path don’t seem to be a / causing the problem.
There may be a fallback path in the code for failing certain checks for a drive? But those checks may not be appropriate for OSFMount logical emulation mode path drives. ??
Two additional thoughts after a first look:
1:
As I’m used to WaveLabs user interaction behavior. A WaveLab mode for keyboard commands and knobs would therefore be helpful for users like me. For example, I am asked to add noisy parts to algorithms like DeClick or DeNoise. Finding them in the whole file seems to be a daunting, time-consuming and difficult task. Unfortunately, the marker file from WaveLab is ignored. Reading in these markers would help immensely.
2:
When the selection of an area becomes too small, no hand appears to move the selection anymore and you can’t move this small selection in the large file or can it be moved (by pressing a certain keyboard-key)?
To illustrate the situation described above, some images are shown. SpectralLayers 11.0.40 starts calculating, but from time to time it shows the user an error message, stops calculating and starts again after OK has been clicked to process the messages.
The above described handling / work around of this situation works only if one let stay Spectralayers in the foreground as the active application.
If I let SpectraLayers let do his DeNoise-Thing in the background and the bell rings for the info, “there would be less then 200 MB”, and I switch back to SpectraLayers to press OK to the error message, the application stalls and must be restart as shown in this picture:
May I provide the developers with something that would help to fix this in a short time frame? Let me know.
Another Thing I came across … How to update a preset? I have found only delete and create / add.
After the “DeNoise Thing” the result has higher levels as before. (above 0dB from before under -1dB).
Regarding your first concern :
Can you set the cache folder on a drive that is not managed by OSFMount ? For some reason it seems that SpectraLayers doesn’t interpret the free space on your I: drive properly.
You can also try to lower the warning limit to 10MB here, maybe it will trigger the warning less frequently:
Regarding 1: of the 3rd post: SpectraLayers can read markers from .wav files. Maybe there’s another way to save markers in wav files with WaveLab ?
Regarding 2 or your 3rd post: do you mean the display area ? You don’t need the hand icon to show up, just click anywhere in the rest of the overview to set the view there. You can even click anywhere and drag to move that view continuously.
Regarding updating the preset, just create a new preset with the same name, it will overwrite the previous one.
Regarding the DeNoise module issue, never saw that behavior before, does it do the same on other files ?
Thank you for the quick response! That is very pleasing.
I checked in both directions.
No solution there. I do not want loose speed and wear down my hardware (e.g. try to amass large SSD TBW values doe to large temporary files and trash my SSDs slowly but surely). If there is plenty of memory available, an application should use it. If not ( and there are many out there that use files for temp-variables instead of gulping in large amounts of memory and by doing so not loosing speed in additional file-processing internally), I try to alleviate this thread for my physical hardware with a RAM-Disk. For what to have enough memory if it is not used?
I hope, this could be fixed in SpectraLayers 11.0.50 or is there no intention in doing so because of whatever reason?
There are .mrk files as well. There should be the option to read them in if not doing it by default. Background-Discussion recently:
Regarding the level:
The file I used has this peak levels:
Have not checked it because I could not save the work … the application was frozen. Only saw the meters in read above 0 for whatever reason.
I started the test phase some days ago. …
What you can try is hack the registry to force the warning to 0MB (so that it never show up).
To do so, open regedit, and change the freespacelimit value in HKEY_CURRENT_USER\Software\Steinberg\SpectraLayers 11.0 to 0:
I, personally, would much rather update an existing preset “name” syntax than have to remember whatever syntax I previously used! That’s how the majority of other software I use works. 
The registry-fix does not help. The error-message still pops up. It also pops up when I try to export a file to this RAM-drive. Maybe is a check in some subclass-function not quiet right? Maybe one can create a RAM-Disk and debug?
After pressing OK to handle this error-message all works fine until this message again pops up and the calculation stops and waits for my interaction.
As for the greater then 0dB thing after denoise. After exporting and comparing, there is no above 0dB. The difference between the two files sounds like music for me. Not much noise in there. I may have to experiment … but the message pop up thing …
There may be a filter before playback? I encountered such thing in Steinbergs Postfilter. I enjoyed it for a while because it produced new spikes and levels for whatever reasons. However, I ask myself until today how that can happen? What does PostFilter do in the background? I used it for cutting out the “Trittschall” as advertised in a youtube-video. Only later, it dawned to me that the whole bass part had also lost audibility. So I do not use it anymore.
