Freezing multiple tracks don't work

[Netchicks]

Trying to freeze multiple tracks at once gives error (see attached image). This worked with previous versions of Reaper. No changes to config have been done in the meantime.

[Fabian]

I just tried selecting two tracks and freezing them, and it worked fine here.

The issue you have seem to be unavailability of something along the path where Reaper tries to write the rendered files. Is the disk full?

Or maybe it is a problem with the Norwegian ö in the path and/or file name? There were some fixes for non-ASCII filenames on Windows, maybe those broke something...

[Netchicks]

Originally Posted by Fabian

I just tried selecting two tracks and freezing them, and it worked fine here.

The issue you have seem to be unavailability of something along the path where Reaper tries to write the rendered files. Is the disk full?

Or maybe it is a problem with the Norwegian ö in the path and/or file name? There were some fixes for non-ASCII filenames on Windows, maybe those broke something...

Thanks for the reply.
Disk isn't full. The Ø might complicate things, but then it should also be an issue when I freeze a single track too? Currently this only happens when I try to freeze multiple tracks. Where do I send in a bug report, or does this post count as a report?

[Fabian]

Fiddling a bit I managed to replicate it!

Two unnamed tracks. Freeze both, you get two files named ProjectName_freeze-001.wav, and ProjectName_freeze-002.wav.

Now, try to freeze again, the error shown in your image appears.

It seems that Reaper when incrementing the file counter, sets the same count for both files: ProjectName_freeze-003.wav, and of course then it locks itself trying to create two files with the same name in the same folder.

This seems like a bug, yes. And this is then a bug report.

Workaround for now: Name your tracks.

[Coachz]

What kind of animal doesn't name his tracks ? :-)

[Netchicks]

Originally Posted by Fabian

Fiddling a bit I managed to replicate it!

Two unnamed tracks. Freeze both, you get two files named ProjectName_freeze-001.wav, and ProjectName_freeze-002.wav.

Now, try to freeze again, the error shown in your image appears.

It seems that Reaper when incrementing the file counter, sets the same count for both files: ProjectName_freeze-003.wav, and of course then it locks itself trying to create two files with the same name in the same folder.

This seems like a bug, yes. And this is then a bug report.

Workaround for now: Name your tracks.

Thanks for this! Works on my end too

[Netchicks]

Originally Posted by Coachz

What kind of animal doesn't name his tracks ? :-)

Too many tracks, too little time to name them all :=)

[Fabian]

Originally Posted by Coachz

What kind of animal doesn't name his tracks ? :-)

Yeah, good point

But I think the same issue would arise if you had two tracks named the same, and tried to freeze those twice.

So I really think this is a bug, Reaper should be aware of its own renaming while freezing.

[Coachz]

Originally Posted by Fabian

Yeah, good point

But I think the same issue would arise if you had two tracks named the same, and tried to freeze those twice.

So I really think this is a bug, Reaper should be aware of its own renaming while freezing.

Very true. I live by freezing tracks so they absolutely have to work in my world of Reaper. I hope they get it sussed out.

[gkurtenbach]

Same bug happens to me when freezing two tracks with the same name, btw.

[fakemaxwell]

Confirming this has happened to me constantly on 6.11. Not sure if earlier versions did the same thing.

[Fabian]

This issue is apparently being fixed now:
https://forum.cockos.com/showthread.php?t=237124&page=2

[Fabian]

I just now tested v6.12, and indeed this issue is fixed. Nice!

EDIT: So maybe changing the title to include "[Fixed]" would be good, is what I mean