Jump to content

Wei Liang Yap

  • Content Count

  • Joined

  • Last visited

Community Reputation

11 Good

Recent Profile Visitors

677 profile views
  1. Thanks @Hatstand. Most of the material is speech. None of the people have a clue about what decibel is, and they will have done well if they even managed to send the video across. So it will be for me to try to make it such that it is loud enough, and not too loud. (The aim is so that the listener doesn't have to reach for the volume control many times) For uncomplicated clips it has been fastest to use Audacity for loudness normalisation to a target. (Can make it a macro, with limiter as second step). For the complex clips I use cakewalk plus any combination of envelopes, compression, limiting, erase, etc. I was hoping however that Cakewalk had a simple loudness normalisation tool like audacity. Hence this feature request. Wei Liang
  2. Hi - this is probably much more than I would ever need (in terms of I/O and routing), but I am wondering if anyone has experience of using this as a USB audio interface with Cakewalk. Any issues with its ASIO drivers?
  3. Thank you all for the suggestions. I'll look at the MLoudnessAnalyzer and 4U meter as well.
  4. Vocal Rider might be what I need. Thanks for the suggestion. Wei Liang
  5. Hi, I mean that this would be an automated process to: 1. Analyse/measure the integrated (average) perceived loudness as measured/defined with LUFS (aka LKFS). Example: it measures -6 dB LUFS. 2. Automatically increase or decrease the clip loudness to the desired level. Example: it reduces that clip by 8 dB so that it now measures -14 dB LUFS. 3. Optionally limit the peaks that exceed 0dB (or other user-defined threshold) The use case scenario: you are given a video compilation of various speeches and music clips and asked to fix the sound. Because some content is too soft and some content too loud, all within that video. Therefore I split the 60 minute audio into the different sections that need fixing and adjust those volumes then put it back into the video. I don't think a compressor is the right tool for this but others with more experience might educate me. Thanks PS this (loudness normalisation) can be done in audacity. But I would prefer to use my favourite software (cakewalk) 🙂
  6. Hello - it would be nice to have Proccess --> Apply Effect --> Loudness Normalize which can be applied to a clip, to normalise the loudness to a prefered LUFS target, which can also give the user the option to allow/disallow if the result will have peaks above 0dB, and also give the user the option to apply their preferred limiter plugin if so. Thanks, Wei Liang
  7. Hi - so I have been trying out the Spitfire BBC orchestra, and it seems to be a one-synth-per-voice, and the voice is set from the synth (i.e. not from the Channel/Bank/Program. For an orchestral mock-up it therefore means multiple synths of very similar sounding names. I notice that by double clicking at the space int the bottom left (see picture) it brings up the related SoftSynth instance (which is a good thing). I am wondering if there is any way of achieving the same thing from the track view (see second arrow with question mark)? Thanks, Wei Liang
  8. Hi, don't know if grantobrien (http://forum.cakewalk.com/Instrument-definition-for-Roland-RD2000-m3788479.aspx) or anyone else is interested, but here is an instrument definition file for the RD-2000 https://github.com/yapweiliang/RD-2000.INS
  9. Although there are various places to annotate, it would be nice to have an Index or TOC page that could summarise and hyperlink to the respective clip or folder or track marker or etc etc that has text. Sorry i appreciate this is a bit different to what the OP is asking. (DOI: i have no current need for this facility but i think it would be nice to have a means to keep track of multiple small things which could get buried. E.g. Effects on a single small clip.) Wei Liang
  10. OK thanks I'll stop here for now. Having a different midi device as the first device then changes the order of the rest of my MIDI devices which is inconvenient when re-opening previous projects. However having a loopback device permanantly installed and 'looped' to the Control Surface will work, but it shifts the problem to the loopback device to remember to re-connect to the Control Surface. Hopefully at some stage there will be a way for CbB to 'remember' disconnected USB MIDI devices Thanks for your time Mark. Wei Liang
  11. Hello, I've been tinkering, and it does seem no matter what I do, that when the control surface (Zoom R16) is unplugged, that CbB goes for the first rather than the last device. Any other suggestions? Below is the equivalent snippet from my TTSSEQ.INI. I also deleted and re-created the TTSSEQ (the [MIDI In Device Map] /[MIDI Out Device Map] does not seem relevant.) [MIDI Input Devices] 0=Port 1 on Micro 1=Port 2 on Micro 2=Port 3 on Micro 3=Port 4 on Micro 4=ZOOM R16_R24 Audio Interface MaxInPort=4 [MIDI Output Devices] 0=Port 3 on Micro 1=Port 6 on Micro 2=Port 5 on Micro 3=Port 2 on Micro 4=Port 4 on Micro 5=ZOOM R16_R24 Audio Interface MaxOutPort=5 Thanks in advance, Wei Liang
  12. I think most audio interfaces are set up as Stereo Pairs. So Zoom Channel 1 = 1 Left Zoom Channel 2 = 1 Right 3 = 2 Left 4 = 2 Right 5 = 3 Left etc. On CbB track if you make a mono track, you can assign either left or right input (e.g. Zoom 1 Left). But that is just the name of the input channel, and on the mixing console the mono track would normally be Pan in the Centre by default. What you can also do is rename the Input Drivers. At the bottom of your first picture, you can tick Use Friendly Names to Represent Audio Drivers. Then you can rename "Zoom R16... 1" (sorry your picture is out of focus I cannot read exactly) into "Zoom Ch 1/2" and the next one into "Zoom Ch 3/4" etc to help you to remember. You should probably also try the ASIO mode (Audio > Playback and Recording > Driver Mode) to see if it works better for you. Hope this helps Wei Liang
  13. Thank you for your thoughts. In my situation, when the control surface device (the Zoom) is unplugged, the control surface thingmy on CbB defaults to the first rather than the last device. (And when it is plugged in, it is already set as the last device). Your post has also prompted me to try the following, unfortunately didn't work 1 - with Zoom unplugged, set the output device to a 'spare' device (i.e. not my digital piano) 2 - save settings 3 - quit CbB 4 - plug in Zoom 5 - start CbB 6 - set output device to Zoom 7 - save settings 8 - quit CbB 9 - unplug Zoom 10 - start CbB ..... unfortunately same problem as initially described. (I was hoping it would remember a 'plan b' setup) I notice that my TTSSEQ.INI also has a [MIDI Out Device Map] heading which may or may not be in your TTSSEQ.INI. I'm not sure what this headings are for (MIDI In Device Map, and MIDI Out Device Map) these headings do not include my Zoom; however the [MIDI Output Devices] and [MIDI Input Devices] do include the Zoom. I'm going off on holiday soon, so probably will do the tinkering when I return, and try to learn what the Device Map is for. If you have any further thoughts it will be appreciated. Thanks, Wei Liang
  • Create New...