Rejected speedy - "editing clicks"
So it's .5 sec too long (I removed every pause and read as fast as my human mouth could move (77 words))
They claim I mispronounced a name. Client's phonetics conflicted with the recording they provided which I matched - perfectly. Probably should have flagged the confusing conflicting directions.
Noted "editing clicks" of which I do not hear any. Any at all. Also, when does editing create "editing clicks" and how can this be prevented?? Helps if I'm not deaf I guess!! (joke)
Hear is that file:
https://www.dropbox.com/s/odwnzy0np9lubac/CODA%20-%20New%20York%202.wav?dl=0
Thanks for any help
Please sign in to leave a comment.
Hi JV,
-In terms of length, if it's a Spotify project it should be "less than 28 seconds". I see your recording is 29.781s long, so a bit longer than required.
-If you ever encounter any pronunciation issues, please feel free to raise a flag in order to contact our Production Management team who will be happy to provide assistance. You can learn how to raise a flag in our Knowledge Base article here: https://goo.gl/wX9KH4.
-In terms of clicks there's one at 4.200s in the word 'composer', at 19.076 in 'featuring' and a subtle one at 26.000 when you say July. The best way to avoid them is to apply crossfades in every edit point (or a fade out & fade in).
Hope that clears it up,
-Seb
Thanks for the quick reply post.
Yeah, maybe I should stay away from less than 28sec requirements with more than 70 words. Clearly my mouth can't move that fast!
I will flag next time for sure. Best not to assume anything no matter how obvious it may seem at the time.
One of those clicks you mentioned (4.200 sec) was in the midst of a segment that had not had edits. Perhaps the 'click' (that I STILL cannot hear) was caused by something else.
I can't hear any of the three clicks you mentioned. As far as I know I don't have a hearing problem. :) Is there a tool of some kind where I could detect these otherwise? When I do hear a click and I'm viewing the waveform in dB I can visually see the click so it's easy to spot (and hear.) With these I see and hear nothing. What am I missing here?
Thanks again!
Recording software with spectral view can make it easier to view these clicks, however it's best to listen carefully. I've attached a screenshot of the spectral view of your file, at 4.3s there is a click throughout the audible spectrum.
If clicks are not coming from editing they could be caused by a recording device with incorrect settings (like a small buffer size or a mismatch in sample rate) or even a slow hard drive that glitches when recording.
They are subtle but it's better not to have them.
Thanks Sebastian!
Using Audacity and did a dupe of the track and turned on the spectral view but it's not showing up quite like on your screenshot above (see mine below.) I'm using a Scarlett Solo to a rather long USB cord to my 2011 MBP (APPLE HDD HTS727575A9E362) Do you know of any tests that I might run to find the source of the issue?
Thanks again!
I agree that in Audacity it's not as clear (I used Audition). The issue could be the length of the usb cable or the buffer length in Audacity.
USB specs say that the max length is 16ft (or 5m). Longer runs could cause issues with sample dropouts causing these issues.
In terms of hard drive, if its 7200rpm it should be able to handle recording without a hitch.
I'd test a shorter usb cable (and if needed a longer mic cable instead).
Thanks Sebastian. I increased my buffer to 200ms as a precaution. I've had my current setup for quite awhile without issue so my thinking is that I either had several apps or notifications that may have bombarded my sound card during recording at that moment. Doubling the buffer should handle that and I'll also try to remember to turn notifications off as well! ;)
Cheers, J