Beatmapper Problem - Does not save edited data in all audio files.

jocker-boy wrote on 1/10/2022, 4:06 PM

Hi,

I have a problem with Beatmapper, specifically it doesn't save data for audio (wav) files after using it.It looks like I choose a given file - the audio track from the explorer starts after clicking on the Beatmapper file. I follow the procedure to edit the file in order, save it.However, when I click on the file that I edited in Beatmapper after a while, it restarts and I have to edit it again. After highlighting the file in the Acid explorer, there is no typical information there that the audio file has been processed in Beatmapper. In the directory on the disk there is an additional SFK file for the given file, but apparently without the edit data in Beatmapper.

This situation affects 99% of the files I try to set up in Beatmapper.I don't know what is the reason why it works badly.I tried various variants of using Beatmapper, unfortunately it doesn't help.Do you also have similar problems with it?

My OS is Windows 11 Pro, Intel i5 8200U, 16 GB Ram memory.Integrated audio card.

greetings

Mariusz

 

-----------------------------------------------------------------------

Edit

------------------------------------------------------------------------

I uninstalled the program, deleted all folders and files related to it,I cleaned the registry in Windows with CCleaner, deleted all SFK files from folders with audio files. I reinstalled the Acid Pro 10 x64.I set the audio driver in the DAW to Windows Classic Wave Driver instead of Asio4All

I started Beatmapper with one audio track, it went fine and saved the data, but the next audio file that I mapped unfortunately Beatmapper didn't save any data, in the next one the same.

I will try to install Windows 10 instead of Windows 11, maybe it will improve something?I have no more ideas.

 

Reinstalling Windows on Windows 10 didn't help.

Now I noticed that it saves data but not to all the audio files it edits in it? 😢So it works, but not every file is able to put data. The files I use are wav files with the same standard parameters. PCM 1411 kb / s 44100Hz 16 bit

 

 

Comments

sheppo wrote on 1/14/2022, 8:56 AM

well, that's not something I'd noticed before, typically because I don't use the same tracks over and over. However, this definitely did work at one point.

Anyway, to work around the issue, when in the clip properties, hit the blue floppy disk icon on the right hand side of the clip properties window. This saves the stretch info correctly for me. Even if you have custom stretch markers you'll still see the beat markers saying no, but will load correctly in to a new project correctly. Here's what I see.

ACID information
  ACID chunk: yes
  Stretch chunk: yes
  Stretch list: 1
  Stretch info2: yes
  Beat markers: no
  Detected beats: no

jocker-boy wrote on 1/14/2022, 1:22 PM

Hi Sheppo,

Thank you for your interest in the thread and for helping to solve this problem.As for the blue save icon, I always click on it after editing the audio file in Clip Proporties, but in the case of this and other clips it does not help, it does not help. When restarting the program, there is no trace of manually set tags or no information about the processing of the file in Beatmapper. :(.I ripped some files from the audio CDs and these Beatmapper edits and saves correctly the first time.After ripping, the files were processed in the same way in Platinum Notes and Mixed In Key 10,so these programs hardly ever harm them.I wonder if the DRM protection could be the reason here?

This can be seen in the screenshots below...hmmm..?