Bug: Loading sample on used pad replaces sound! *VIDEO

Is this a bug or is this by design now? Before when you loaded a sample on a used pad, the old sample just got deassign from the pad and the new sound would be on the pad. Now, loading a sample on a used pad completely removes the old sound from the project! However, the old sample still remains in the samples folder on the hard drive even though it's no longer in your project!


EDIT:

Here's a video of the issue. I'm browsing and loading from the hardware:

That doesn't seem like a good design if thats the case.

Have you tried to see if you can Undo the process once the sample is gone?
I was just going through some samples pretty quickly and noticed I had loaded a sample in place of one that was already on a pad. I hit undo and it looks like it put the sample back in. I didn't check to see if the sample had been deleted from the project previously but I'll see if it's happening or not.

May have something to do with the "Improved Delete Unused Samples" function.

Isn't the samples folder part of the project tho? Maybe this is where the unused sample resides until you use the delete unused function...

To be clear, If you load the new sample onto a pad, you cannot assign the old sample on a seprate layer as it's been removed from the project in the ram, but when you save project and check the hard disk, the old sample is saved like it was and should be in ram.. ?

DJ Hellfire wrote:Is this a bug or is this by design now? Before when you loaded a sample on a used pad, the old sample just got deassign from the pad and the new sound would be on the pad. Now, loading a sample on a used pad completely removes the old sound from the project! However, the old sample still remains in the samples folder on the hard drive even though it's no longer in your project!

Oh hell no, this could suck if it's what I think you're saying. I could deal with the old way as it was like hardware and you just had to go back into pad assignments and add the sound back as another layer.

Sounds like now I'd have to drop the new sound to some new pad, then go to pad assignment and move the sound over to where I wanted to layer it... (I have to really dig into 1.5 tonight since i couldn't last night)

I know beta testers can never catch everything but soe of the stuff we all use often shouldnt slip thru the cracks

dazastah wrote:To be clear, If you load the new sample onto a pad, you cannot assign the old sample on a seprate layer as it's been removed from the project in the ram, but when you save project and check the hard disk, the old sample is saved like it was and should be in ram.. ?

Correct!

MPCTNT wrote:

DJ Hellfire wrote:Is this a bug or is this by design now? Before when you loaded a sample on a used pad, the old sample just got deassign from the pad and the new sound would be on the pad. Now, loading a sample on a used pad completely removes the old sound from the project! However, the old sample still remains in the samples folder on the hard drive even though it's no longer in your project!

Oh hell no, this could suck if it's what I think you're saying. I could deal with the old way as it was like hardware and you just had to go back into pad assignments and add the sound back as another layer.

Sounds like now I'd have to drop the new sound to some new pad, then go to pad assignment and move the sound over to where I wanted to layer it... (I have to really dig into 1.5 tonight since i couldn't last night)

I know beta testers can never catch everything but soe of the stuff we all use often shouldnt slip thru the cracks

Well, you can also just load the sound without selecting a pad. You don't have to assign it to a pad on load. Just deselect the pad and press load. It will load into the program, just not on a pad!

DJ Hellfire wrote:Well, you can also just load the sound without selecting a pad. You don't have to assign it to a pad on load. Just deselect the pad and press load. It will load into the program, just not on a pad!

Right I do both at times... but for the times I take it straight to a pad, I prefer it not totally removing whats alrdy there from the project

MPCTNT wrote:

DJ Hellfire wrote:Well, you can also just load the sound without selecting a pad. You don't have to assign it to a pad on load. Just deselect the pad and press load. It will load into the program, just not on a pad!

Right I do both at times... but for the times I take it straight to a pad, I prefer it not totally removing whats alrdy there from the project

So have you verified this issue as well on your end?

Can someone post a video (without profanity ) with this issue? Please post your system spec as well.

I have been trying to produce this on my end but can't. I can load via browser or drag-n-drop a sample on a pad. It will replace this existing sample (unless I hold SHIFT and drop to a layer). But no sample is removed from Project Info window.

DJ Hellfire wrote:

MPCTNT wrote:

DJ Hellfire wrote:Well, you can also just load the sound without selecting a pad. You don't have to assign it to a pad on load. Just deselect the pad and press load. It will load into the program, just not on a pad!

Right I do both at times... but for the times I take it straight to a pad, I prefer it not totally removing whats alrdy there from the project

So have you verified this issue as well on your end?

I just tried this and it works as it did before... replaces sound on the sound on the pad but the replaced sound remains in the program as unassigned

I can't recreate this at my end

Works fine for me still.

The sample is sticking around for me as well.
Maybe it's related to the location of the original file. Is it an external or local drive?
What type of file is it? 24bit Wav, 16bit, aiff, mp3?

It still works as normal for me.

Windows 7
i7
16GB
Ren 1.5

Not sure what is happening on your end Bruh, but looks like most of us are not getting that.

Post up a short vid of it. Not that we can fix it but are curious to see what you are experiencing