Sorry to say again, but I'm having more crashes.
Load up the default view. Add in a basic bass line wav. Push Q to loop. Play with spacebar then again to pause. Held down arrow key to move to a spot, push M to add marker. Push spacebar again and the program is gone. Happened to me twice in a row.
I've recently performed a DISM repair and a scannow so it can't be that.
Windows 10 PC latest update.
In the internal preferences I tried changing the engine and mixer sample rate to 48kHz and 24 bit, to match my samples and the specs my audio interface is running. This time I got four markers down before it crashed.
Tried using my Onyx 8 instead, but no. It won't let me use markers.
I tried disabling my antivirus but that didn't help.
Wondering if my samples are corrupted. I recently batch processed them. Here's an example of them.
So I tried it with a backup of my old samples, but no it still crashes with those too.
@ItsMeTho What audio device driver is selected in the program preferences?
You can check the Windows Reliability Monitor for crash descriptions. You can press the Windows key and R on your keyboard to open the Run window. Type perfmon /rel and press Enter to start it.
Click on a red X to show a crash and double click on the crash to open a detailed description. If the program crashes in ntdll then it's likely a driver problem. Could be any driver, also the graphics card.
@ItsMeTho What audio device driver is selected in the program preferences?
You can check the Windows Reliability Monitor for crash descriptions. You can press the Windows key and R on your keyboard to open the Run window. Type perfmon /rel and press Enter to start it.
Click on a red X to show a crash and double click on the crash to open a detailed description. If the program crashes in ntdll then it's likely a driver problem. Could be any driver, also the graphics card.
"Roland Rubix". Works fine in every other place. Tried my Onyx 8 interface to see if that's the problem but it crashed too.
The windows reliability isn't showing any events.
Resetting all SF settings to default didn't help.
I reset the 'Force Single Instance' to false that didn't help.
Tried the mixer and engine bit rate at 32 (32 bit float?). That didn't help.
I thought maybe Directory Opus auto-hiding those .sfk files could have been it, but no.
I checked and gave more write permissions to the user, from the parent file. Nope.
Removed 'read only - inherited' but that does nothing and just reverses, apparently.
I just realized looking at my ASIO advanced tab, that it's showing me 18ms latency with my default buffer. It's usually 10ms. In all my wisdom I had reformatted all my samples to 48kHz 24 bit, to match up the audio interface so that there is no resampling. Well I just screwed my MIDI controller latency on my whole library. That's a big yikes. If I shorten the buffer I just increased the processing; the opposite of what I tried to do. Dammit.
And I can't get basic 1d3v2 tags on my samples either, and there's no reason at all for them not to write. Nothing is working for me.
@ItsMeTho In case sfk files get modified during file editing, you might lose the waveform graphics, but maybe this also makes the program unstable, but that's just a guess from me.
Makes no sense that the Reliability Monitor isn't showing any crashes. You find crashes either there or in the Windows Event Viewer (which is more cumbersome to navigate). This would mean that Sound Forge isn't crashing. Do you get a crash report window from Sound Forge itself?
Maybe try a simple audio device driver like Microsoft Sound Mapper and see if this helps.
@ItsMeTho In case sfk files get modified during file editing, you might lose the waveform graphics, but maybe this also makes the program unstable, but that's just a guess from me.
Makes no sense that the Reliability Monitor isn't showing any crashes. You find crashes either there or in the Windows Event Viewer (which is more cumbersome to navigate). This would mean that Sound Forge isn't crashing. Do you get a crash report window from Sound Forge itself?
Maybe try a simple audio device driver like Microsoft Sound Mapper and see if this helps.
The Windows Event Viewer did show me some warnings and errors, maybe relevant.
I did the same things to crash SF on purpose to see if a new event popped but nothing appeared. There are some things from yesterday. A denied CSLID thing. Don't know what the SF app ID is, and I couldn't find it, to see if it's SF involved.
Don't know why it needs an always-on updater, using 30MB of my RAM, for a program that gets updated once every two years.
I have a .net framework warning. Tried to see about reinstalling it but it will be a hassle. I won't unless I know that's what it is. There is a tutorial on how to allow user permissions for .net framework for an app ID, on the windows registry. I didn't do it because I can't prove it's SF involved in the warnings.
Oh and a "metadata staging failed". Lots of entries for that.
So I was checking out other file things elsewhere and that prompted me to check on my windows sound settings.
My audio interface was set to run at 44.1kHz for some reason (even though I set it to 48kHz a while back). Then I checked the Roland website and the Rubix "automatically sets its sampling rate to the host".
Hmm... That's interesting because I set SF18 to 48 but Windows is telling it 44.1. Hmm... So in the windows settings after changing it back to 48 I haven't had a crash in SF18 yet.
Oh no. 😅 All that work and it was just that stupid little mistake.
@ItsMeTho Interesting. Usually there should be an error message that the sample rate couldn't be set instead of a crash. But good to know that you found the solution
Thanks for all the helps. 😊
Ya. I think it's strange behavior in general because this audio interface is kind of unique, in auto-setting its sample rate. You should see the buffer settings. Ever seen something so bizarre?
It's an excellent interface though.
Now that I've tested everything out I think SF18 Studio is going to be a buy. This program is more than a little cherry 👌🍒. I'm actually surprised I've never heard of it until recently. How many other things in life do people know but aren't telling me? How rude. 😠
Now I think that I have the task of purging my 120k sample library, restoring from back up, batch processing, sorting, tagging and renaming them all. Ugh.
The only thing I'm still unsure of is the tempo and key with wav files. I embedded that data into some flac files and FL Studio STILL didn't detect that tempo info was embedded (you got to be kidding me with that).
The marker and regions embedded from SF18 seem to be working fine, even in wav files. But key and tempo is still a thorn in my side. Every analyzer software has a different opinion; they all say different things about the same sample (Excuse me but I didn't know the math laws are arbitrary. Didn't know the frequency number of C5 was a matter of opinion.). It's pretty bad when that info is even written right on the file name and the program still gets it wrong.
NI Traktor Pro 4 half-times the results. Imagine coding music software for a living, and when having samples in a folder named "EDM", you actually programmed your software, that when presented with the choice, it chooses 64 bpm instead of 128.
I've been working on this problem for a week now and it's driving me bonkers. Why can't I just get basic metadata in my samples. Things that were invented back in like windows 95.
@ItsMeTho Since you have Sononym, you can use either it's renaming feature or it's project feature, to rename files.
This writes the found properties into the filename, following your settings. Of course, if you want to use it for the first step likely depends on how accurate it can detect everything to your liking
Then, in Sound Forge you should technically be able to write a script to read out the filenames and populate the metadata of the files via SfSummaryInfo and SfFileACIDInfo. How well this data can be read out from other applications like FL Studio I don't know. Usually, support for acidized audio files were somewhat common the early 2000s but I don't know if this is still the case.