question about the update Release 2024-09-30 Windows

[Drugo]

Hi
can i ask a question about the new update 2024-09-30 for windows ?

about

CD Ripper rips to .tmp instead of ._ by default (then renames after ripping album)

does the dbpoweramp rip tracks to ram or disk?
just because i have always thought it does rip and keep on ram and after write on disk
might you please make it more clear?
thanks
best regards

[Spoon]

It writes to disk

[Drugo]

It writes to disk

hi
sorry i guess it should be moved to cd ripper

CD Ripper rips to .tmp instead of ._ by default (then renames after ripping album)

do you mean the update does write directly to the disk and after it just performs a rename?
just because seems cd ripper does use temp folder
thanks Spoon

[Spoon]

For a long time CD Ripper wrote the album to ._ files, then renamed the whole album after ripping. Now it writes to .tmp and renames, nothing has really changed, just some programs would pickup on ._ when they should not, .tmp is better.

[Drugo]

For a long time CD Ripper wrote the album to ._ files, then renamed the whole album after ripping. Now it writes to .tmp and renames, nothing has really changed, just some programs would pickup on ._ when they should not, .tmp is better.

Hi
i got it , it does rip in ram ,encode and write tracks or the entrire album on disk in .tmp directly and after it does rename it ,right?
might you please move this topic to the ripper sub forum
thanks

[Spoon]

Correct, the idea is any player would not see the tracks until the whole album is ripped, especially if using ReplayGain which writes an album gain after all tracks are written.

[Drugo]

Correct, the idea is any player would not see the tracks until the whole album is ripped, especially if using ReplayGain which writes an album gain after all tracks are written.

hi
i would like to rip to ram without any temp files /folder

[GBrown]

i would like to rip to ram without any temp files /folder

You are really going to keep beating that drum despite the multiple replies in other threads from the developer.

With the current storage write speeds that far exceed the ripping speed capability of any optical drives, what additional benefit do you expect from keeping the temporary rip files exclusively in RAM? I'm trying to wrap my head around the benefits that would warrant this additional development time.

The dependability of the current temp methods when ripping entire discs ensures no player or library manager starts to index these tracks until the entire ripping process is completed. And only then does dbpa move it to the final destination and change the file type to the actual extension. At this point your music management software of choice can take over.

[Drugo]

You are really going to keep beating that drum despite the multiple replies in other threads from the developer.

With the current storage write speeds that far exceed the ripping speed capability of any optical drives, what additional benefit do you expect from keeping the temporary rip files exclusively in RAM? I'm trying to wrap my head around the benefits that would warrant this additional development time.

The dependability of the current temp methods when ripping entire discs ensures no player or library manager starts to index these tracks until the entire ripping process is completed. And only then does dbpa move it to the final destination and change the file type to the actual extension. At this point your music management software of choice can take over.

hi
some antivirus don't like temp files ,mostly when they are located or stored in the windows temp folder
that's why