What i want to know is how do get i the automatic overlap mode working in Mairlist. When i import the mp3’s in the database via the import module you see the question disable autoque or not . When i dashed this on and have import all my files , nothing hapens a smoorh overlap sound just a pause of 2 sec. This is strange you should get a smooth overlap…
Auto Cue must be enabled. So do not check the “disable Auto Cue” box!
After you imported a file with Auto Cue enabled, you should see a Fade Out point set in the properties/PFL dialog. This will be used for the smooth overlap.
If no Fade Out point is defined, neither through Auto Cue nor manually, the file will be played until its very end.
Yes, you’ll need to open the Config Utility and set some values. I use these values, and they work well. YMMV…
Cue In = -50 (dB) b[/b]
Fade = -17 (dB) b[/b]
Cue Out = -50 (dB) b[/b]
You made need to adjust the fade a little to your satisfaction.
Also, I would suggest that you read through the new manual. It will answer your questions and also teach you some things that even advanced users probably aren’t aware of.
[quote=“alecm33, post:3, topic:7272”]Cue In = 50
Fade = 17
Cue Out = 50
You made need to adjust the fade a little to your satisfaction. [/quote] >COUGH<
Cue In = -50 (dB)
Fade = -17 (dB)
Cue Out = -50 (dB)
FTFY.*
Personally, I use:
Cue In = -90 (dB)
Fade = -12 (dB)
Cue Out = -90 (dB)
… but I do also use ripping software (dBPowerAmp) which removes ‘silence’ from both ends of all CD tracks.
Thanks, Alec. That was my plan.
Document thoroughly once, record that accurately and consistently, then cross-reference thoroughly.
Organise into sensible chunks (sections/chapters), and never be afraid to re-organise even major parts later (and as you go) if they would make more sense to the user if you instead do it ‘that’ way around.
If you ever read something back later and think, ‘would I need to know anything else to understand this when reading it for the first time?’ then add it right there where it needs to be.
Always describe everything using language and terms the user will know and understand immediately, but where something has an ‘Official Name,’ use that Name but also explain it to the user in their terms. (“The Cartwall works like ‘single-shot’ or ‘instant’ players, or hardware cart players.”)
That’s how you produce reliable, trustworthy documentation where everything is 100% accurate and easy to find. Which is the only sort worth the name of user documentation. (Yes, I’ve taken courses on this stuff. Which were both enormously enjoyable and useful. :))