Jump to content

msmcleod

Staff
  • Posts

    6,009
  • Joined

  • Last visited

  • Days Won

    26

Everything posted by msmcleod

  1. You could draw a section using the arranger, then press play on that section in the arranger inspector:
  2. msmcleod

    I need ASIO4ALL

    +1 to this. Look at Andrew Scheps - he does some mixes in a hotel room, with his headphones plugged into his macbook using it's onboard device. If you're just mixing, and not recording anything, there's absolutely no reason why you can't use an onboard Realtek device. If you just use VSTi's to make music then there's no reason why you can't use an onboard Realtek device. In theory, there's shouldn't be anything stopping you recording audio with a Realtek device either... it's just that most motherboard manufacturers have done absolutely nothing to shield the audio signal path from the input to the Realtek chip, meaning you get loads of interference. This is not Realtek's fault - it's the fault of the motherboard manufacturer.
  3. The ID3 data is populated at the time the dialog is opened, based on the current project, and current export criteria. If you do a track export for example, it will use the track name as the name, and takes the rest from the browser notes tab. It will show a different name for each and every track. If you check "Use same settings for all", then it will automatically populate each "name" field with the track name. For entire mix exports, it'll use the project name. Whatever is chosen within the dialog will be saved in the task. It does not get updated if you subsequently change the project name / track name / artist etc.
  4. Cakewalk already supports surround panning if the track is sent to a surround bus:
  5. You can use the Channel Tools plugin for this.
  6. I've got SONAR 8.5 installed on a 64 bit machine, alongside 64 bit versions of X1, X3, Platinum and CbB. I've not had any issues, but I would recommend installing them starting with the oldest SONAR version first to avoid potential issues with common components. You shouldn't see any issues with VST plugins, but you may well get issues with DX plugins. 32 bit DX plugins / DXi synths will not load in a 64 bit program. You'll need to replace these with their 64 bit counterparts manually.
  7. Can't you just set the filename to something other than {projectname} ? You can set the filename to anything you like. There's nothing forcing you use the tags, and actually with the workflow you've described, they won't help you ( unless of course, you're updating the browser notes, in which case you could use {notesname} instead). Also, you can use the "..." button next to the filename to specify both the filename an path at the same time. It will remember the path for the remainder of your session.
  8. msmcleod

    I need ASIO4ALL

    @Steven Lewis - if you really need to use ASIO4ALL, just hit No at the warning prompt and it'll use it and not bother you again. ASIO4ALL was being used by new users despite having a native ASIO driver installed. As ASIO4ALL is simply a wrapper for the WDM drivers, this was leading to sub-optimal performance. In most cases WASAPI will perform far better, or better still, use the native ASIO driver if there is one. If you've a very old audio interface, or you're using an advanced configuration for streaming, there might be a legitimate reason for using ASIO4ALL. In this case, just hit No at the warning prompt.
  9. Yes. The Title and Album are taken from the Name & Album fields from the Notes tab. If you're doing a tracks export, the Title field is replaced by the track name.
  10. If you specify MP3 as an output format, the MP3 Export Options dialog will appear either when clicking Export or clicking the "Add Task" button. When the MP3 Export Options dialog appears, make sure you check the "Encode ID3 info" checkbox:
  11. There could be various reasons for this: 1. A fault in your keyboard ( FWIW, I recently had to replace my Korg microKEY2 61 with exactly this problem on several keys) 2. The velocity curve configuration in your keyboard ( if it allows you to modify this ) 3. The VSTi instrument itself, e.g: - Some VSTi's have their own configuration for velocity curves. Check to see if you can change this. - Some sample based VSTi's have a limited number of samples, maybe as small as 4 samples per key. It may be that the VSTi just doesn't have a quieter sound for that velocity ( you can check this by editing the notes directly in the PRV to see if you can lower the velocity there) - Some VSTi's don't respond to velocity at all ( e.g. organs ). I would start by trying to do a factory reset of your keyboard. Most keyboards have some key combination you have to press when powering it up to reset it. Consult your keyboard's user guide, the manufacturer's website, and/or do a Google/YouTube search. Once you've done this, start recording some quiet MIDI notes in Cakewalk, and view them in the Events View and check the velocity of the notes recorded. Cakewalk doesn't modify velocity information as it comes in, so if it's stuck at a certain level, it's likely a hardware issue with your controller. If the lower velocities are showing up in the Events View, then the problem lies with the VSTi.
  12. @gmp - we've found and fixed the issue here. We'll get an update out ASAP.
  13. Spaces in your filename perhaps? You could try using quotes for the %I and %O, command line parameters e.g: lame -V4 --vbr-new -m j "%I" "%O"
  14. There are two differences: 1. CA2A is a VST that can be used in any DAW, whereas PC2A is pro-channel only 2. CA2A has a sidechain input, PC2A doesn't.
  15. @gmp - You could try this: 1. SHIFT + double click the clip to zoom the track to full screen 2. ALT + Z to return to the previous view In fact you can use ALT + Z to work your way back through the history of all your zoom steps, SHIFT + ALT + Z will go forward through your history of zoom steps.
  16. If the project hasn't been saved, %PROJECTFOLDER% defaults to the global audio folder.
  17. You can add text events using the Events View.
  18. I've not delved into this deeply, but I suspect if this is a groove clip, and you've set beat 1 to the first transient in the waveform then what it is doing is aligning beat 1's transient to the grid rather than the edge of the clip. Which makes sense if you think about it.
  19. You've copied the clips as linked clips. That's why they're outlined.
  20. Looks like you've got a snap offset set on the clip. You can tell by the small corner on the bottom left of the clip. Check the clip properties:
  21. Linked clips? Without seeing them, I can't really say.
  22. Have you looked at Touch OSC ? https://hexler.net/touchosc
  23. New audio files are created every time you change the audio on your track - e.g. split, re-record etc. These are created so that: 1. You can undo those operations during a session 2. If you use auto-save, the older versions of the track audio is still there for those older versions The safest way to get a "clean" version of your project with only the audio files you need is to use File->Save As , and save your project to a new folder. The new project will only have the files it needs for the project.
  24. @J. R. - you can change the names of your inputs by giving them friendly names in preferences, e.g: Use the | character to separate the odd / even channels.
  25. Whenever I've had distorted sound with focusrite drivers, it's been because Windows is using the focusrite at 48Khz and CbB is using it at 44.1Khz. If they're both set to the same, there's no issues. Mostly though, I try to have Windows use a different sound device instead, like my onboard device or my USB headset.
×
×
  • Create New...