Serato Software Feature Suggestions

Forum
 Serato Software Feature Suggestions
Suggestions for the next version
What features would you like to see in Serato software?

Suggestions for the next version

Knappyhead Lovebones 1:52 AM - 11 February, 2012
I have been using SSL for years and increasingly find myself frustrated with the application as the version increases... There are a couple 'no brainers' that i'd like to see incorporated in the app.

1. Corrupt files should not crash the program. PLEASE handle the error and give that file the "corrupt icon" instead of crashing. Basic error handling in software development... If the file can't be used, flag it and move on. :-)

2. Stop corrupting my files. It seems that every show results in new corrupted files (at least 2.3.X ). don't know why but seems way too common and has only started happening in recent versions.

3. Allow re-analyze to be paused and resumed (even after restarting). The crashes happen and then you have to start over if you are re-analyzing your library. Wouldn't be an issue if #1 & 2 were addressed.

4. If the database file CAN'T be updated for whatever reason, create a safety file and ALERT THE USER. This is more typical error handling that I feel is missing.

5. Read the initial key atom from mp4 files.


These don't seem like huge feature requests so please add these to the next cycle. :-)
MACA 6:51 AM - 11 February, 2012
+1
Serato
Glenn M 7:35 AM - 11 February, 2012
Quote:
1. Corrupt files should not crash the program. PLEASE handle the error and give that file the "corrupt icon" instead of crashing. Basic error handling in software development... If the file can't be used, flag it and move on. :-)

Corrupt files are marked so because their file structure does not conform to the specification of that file. There are many tools out there (such as tagging and audio apps) that break the spec. Also, sometimes when files download badly, big chunks end up missing off the end of the file.

The corruption indicator is just Serato's way of saying, 'hey, we've identified that this file doesn't conform to the specification.' Usually these files still play fine, but sometimes the decoders will fail.

There is no way to 'fail gracefully' from audio decoder like crashes without adding a lot of resource overhead. Event though we could prevent a malformed file from being played in the first place, most of the time spec violations don't affect the ability of the file to be played.

Quote:
2. Stop corrupting my files. It seems that every show results in new corrupted files (at least 2.3.X ). don't know why but seems way too common and has only started happening in recent versions.

As above. There is better corruption detection in 2.3.3 so you might actually get more files marked as corrupt.

I highly recommend using Scratch Live 2.3.3 and above and ITCH 2.1 and above.

Quote:
3. Allow re-analyze to be paused and resumed (even after restarting). The crashes happen and then you have to start over if you are re-analyzing your library. Wouldn't be an issue if #1 & 2 were addressed.

Analysis can be paused/cancelled by cmd/ctrl + clicking the 'analyse' button. Pressing it again will have analysis start from where it finished the last time it was used.

Quote:
4. If the database file CAN'T be updated for whatever reason, create a safety file and ALERT THE USER. This is more typical error handling that I feel is missing.

I'm not sure what could be happening here. You might want to mention this is the Help forum

Quote:
5. Read the initial key atom from mp4 files.
This will be available in 2.4.
Knappyhead Lovebones 6:20 AM - 18 February, 2012
Thanks for the response.
1. Are you thinking corruptions that crash are from audio issues? I get tagging issues. I've seen the challenges associated with certain apps and id3 versions. I was really referring to Serato crashing during analyze. I figure, I'm offline, scanning/analyzing my files and BAM. Crash. I agree with the overhead concerns when connected to my mixer and I appreciate the consideration to keep the overhead low. :-) I just get concerned with the crashing vs just saying "it's corrupt...check it out."

2. Got it. :) using 2.3.3 right now.

3. AWESOME! I learned something! Love it.

4. Will do.

5. YAYYYYYYYY!!!!! finally can put my metadata injection script I was dreaming up away. :-)


Thanks!