Software help archive

A read-only archive of old serato.com help threads.

serato wont let me change my files info! plz help me....

Product
Scratch Live
Version
1.9.2
Hardware
Rane SL3
Computer
PC
OS
Platform
-
twisted_jdm_b16 5:47 AM - 3 November, 2009
Product: scratchlive
Version: 1.9.2
Hardware: scratchlive-sl3
Computer: pc
OS Version: vistasp1
---

im currently running 1.9.2 and it wont let me edit the info from my traxx. I try to edit my BPM# from say 160 to what it actually is which is 80 then i click enter then i press play a different track then i go back to the one i edited and "WAM" it goes back to what it originally said "160". thats just an example of whats basically happening.

all this is happening while i have the hardware disconnected. Im using an external hard drive that i have already taken ownership for the files and have them as "full control" "write" "read", etc.....

what is my problem here? is it just 1.9.2 that is causing this?

plz help this is driving me crazy... :(
twisted_jdm_b16 6:52 AM - 3 November, 2009
ive tested it out with files that are on my internal HD and it edits them fine so its just within my external HD that it foesnt want to edit them and save.

what all would u guys/girls recommend i do to my external HD to make sure it lets serato do whatever id like it to do to my files within my external HD?

sorry ppl this is just driving me nuts and i dont know what to do!
Konix 3:37 PM - 3 November, 2009
Have you disabled UAC in Vista?

Also, try this...

1. Right-click the external drive's letter in Explorer (D:, E:, etc.) and select "Properties"
2. Click the Security tab
3. Click "Edit." You will be asked to elevate.
4. Select "Users" and check the Modify box
5. Click OK enough times to get back to where you were.
twisted_jdm_b16 4:48 PM - 3 November, 2009
So should i disable the UAC on vista? i havent yet.
Konix 6:02 PM - 3 November, 2009
Yes, I would try disabling UAC and see if that works. It has worked for others in the past.
twisted_jdm_b16 4:30 AM - 5 November, 2009
Yeah that worked! Although i dont remember having to do that on previous versions of SSL. Why is that?