Jump to content

msmcleod

Staff
  • Posts

    7,042
  • Joined

  • Last visited

  • Days Won

    38

Everything posted by msmcleod

  1. @Jordi - thanks for the report. I've found the cause of the crash and it'll be fixed for the next drop.
  2. Yep, more or less the same here in Argyll & Bute. It's been averaging 10-12C during the day and no colder than 3C during the night (which isn't that much different than it was in August, give or take 5C). No sign of snow apart from on the mountains. Considering I'm around 250 miles North of Edmonton, it amazes me how different the climate is across the pond.
  3. It's just a JSON format file. You should be able to do a search/replace on the note values.
  4. I'm not seeing that issue here, either with the VST3 or VST2 version of Kontakt 6. I guess it could be related to a specific Kontakt library ( i.e. if a particular Kontakt library crashes when releasing, it could stop the others from being released) , or just that if you've got a large number of libraries loaded it takes a while for them to be released?
  5. It all comes down to the number of writes you can make. SSD's have a limited number of erase/writes to each "spot". If any of those four bits in the QVO changes, it has to rewrite all four bits, whereas the Pro would only need to write the one. So it's not gonna last as long if you use it for your OS drive, but if you're using it mainly for reading (e.g. for samples), then it should be fine.
  6. Inserting a time signature at a measure changes it at that measure not just for that measure. In other words, when you insert a time signature at a measure, it stays at that time signature until it reaches another time signature change. So if you've only got one time signature entry, the whole song will be in that time signature.
  7. You didn't mention what type of bagpipes you wanted, but I suspect you meant traditional Scottish great highland bag pipes. Uillean pipes have a far more mellow sound, tend not to have the drone, and may not be quite what you're after. You could try out these ones: https://www.universal-piper.com/en/the-virtual-bagpipe-lab/ https://www.bigfishaudio.com/Celtic-Instruments both which have a range of different bag pipes. This one is free and synthetic, but doesn't too sound bad - I suspect it would sound convincing enough in a mix: http://flowstoners.com/quilcom
  8. Yes - just click the add ruler button, and you can have both M:B:T and H:M:S:F
  9. @Fred's Gratis Scores / @Noel Borthwick - I can reproduce this with track templates containing Kontakt, but not with other VSTi's. Observations: Closing and reopening the project, without closing Cakewalk itself, reclaims the memory After exporting the template, if I then delete the Kontakt instance from the synth rack, then undo, this also reclaims the memory Exporting the template multiple times, doesn't significantly increase the memory used So I suspect this is a Kontakt issue, specifically that Kontakt doesn't free up the memory it's claimed until all instances have been released from memory. As all of the memory is freed up once Kontakt has gone, I don't think this is a leak as such - it's just that Kontakt has reserved that memory and will use it as needed if you start adding additional libraries.
  10. If you hold down CTRL + SHIFT while dragging the clips on to the track, they'll be put on the same track one after another.
  11. I wasn't giving guidance, I was answering a specific question. I'd have thought that after buying a piece of equipment you'd at least read the user guide that came with it. And if you'd bothered to read the Cakewalk user guide, you'd have found the answer I posted as well.
  12. I can confirm that. It uses heaps of CPU in every DAW I've tried it in. Scheps OmniChannel is pretty light in comparison, as is the Waves SSL Channel / SSL G Channel.
  13. @Pitarch - this is most likely something specific to your project. We'd need to try to reproduce the issue using your project file. Can you zip up the folder your project is in, and send it to @Jonathan Sasor along with details of exactly what you're copying / pasting?
  14. I've not come across this function, but they way I'd envisage it would work would be: 1. Take a list of all the notes that are still on at the time CC64 is switched to > 0 2. Now add all the notes are are on before the time CC64 is switched back to 0 3. Extend the duration of all of the notes above so that it matches the time that CC64 is switched back to 0, but only if their duration ended before that time. 4. Remove the CC64's. Obviously it'll need to cope with multiple CC64's throughout the track. I can't see this being a huge advantage for cutting down MIDI data as CC64 messages are only 2 bytes long. Assuming you're only ever transmitting on a single MIDI channel I guess it could interrupt the state of running status, requiring a re-transmission of the first byte of a Note On event immediately after the CC64, but even then that's just an extra byte. If you're transmitting on more than one MIDI channel for that port, it'll likely not affect running status at all. Also, it'll likely make your notes look like a complete mess in the PRV.
  15. They should already have received that info from Mackie when they got the SDK from them. The button layout is as follows ( taken from https://www.loudtechnologies.eu/shop/data/articles/images/zoom/m_3375.jpg?version=Z24we9Yi - Loud Technologies is the Mackie subsidiary that wrote the control surface firmware )
  16. On the nanoKONTROL 2, you can use the Cycle button as a shift button: Hold down Cycle then press Track " > " to switch to buses Hold down Cycle then press Track " < " to switch back to tracks FYI - all of the shortcuts are as follows:
  17. When Mackie first brought out the MCU, they asked all the major DAW companies at the time to provide button mappings. Cakewalk provided Mackie with mappings for SONAR, and Mackie shipped overlays for all the DAW's with the MCU. The basic transport controls, faders and v-pots are standard across all the DAWs, but all of the other buttons vary between DAWs. When other control surface manufacturers provided emulation for Mackie, they had different modes for each DAW in order to match each DAW's button layout. So unless they specifically mention they support Cakewalk/SONAR, they won't have the correct button mappings. Furthermore, it's not just a matter of re-mapping within Cakewalk - the control surfaces themselves assume a particular state when a button is pressed ( this is due to these surfaces having far fewer buttons / controls than the original MCU ). I'm unsure why some manufacturers have decided not to include Cakewalk/SONAR mappings, but they've obviously made a conscious decision not to include them. I suggest contacting StudioLogic and ask why they don't have Cakewalk/SONAR mappings, and if they could add them.
  18. They're stored in %APPDATA%\Cakewalk\Cakewalk Core\master.ins
  19. I've rarely had to do this, but when I have, I've just: Inserted a new slower tempo 4 measures after the end of the project recorded what I needed to there moved the clip back to where I wanted it deleted the tempo entry at the end Either that, or just recorded it in separate project and copied/pasted it back. The tempo map itself cannot be bypassed, as literally all timing calculation within the engine depends on it.
  20. @Jeremy Murray-Wakefield - what MIDI interface are you using? Another user was reporting stuck notes in normal playing through Cakewalk. As it turned out, it was the MIDI interface drivers. I could reproduce using this interface, but was fine using another :
  21. Native Instruments are going through the process of releasing VST3 versions of all their plugins, which is why there have been so many updates recently. They seem to be releasing a new batch every week or two.
  22. @dogufo - I can confirm the issue is with the MIDISport driver. How I came to this conclusion: The stuck notes also happen in SONAR Platinum, and they certainly never used to The MIDISport refuses to even appear as device within MixCraft or Reaper, and the device freezes on exit and needs unplugged/plugged back in Replacing the MIDISport with a MidiTech Midiface 8x8 solved the issue, with no stuck notes The MIDISport driver is now 8 years old, so it's not really surprising. Most manufacturers needed to update their drivers for Windows 10 2004 / Windows 10 20H1. For example, the Korg USB drivers stopped working when this update came out, and it took a month or two for them to issue a replacement. I've not had the chance to try it yet, but I suspect if I try the MIDISport in Windows 7 it'll be fine.
  23. @dogufo - ok, I set up a similar rig as follows: Fatar MIDI Out -> MIDISport Ch 1 In SY77 MIDI Out -> MIDISport Ch 2 In SY77 MIDI In -> MIDISport Ch 2 Out SY77 L&R -> spare input channels on my audio interface In CbB, the MIDI inputs & outputs were enabled to match the three above - i.e. MIDISport In 1&2, and MIDISport 2 Out. On the SY77 I turned local off - this is important, as otherwise you'll get MIDI feedback. For the most part, everything worked as expected and I could record/playback in CbB. However, I did manage to reproduce the sticking notes. At this point, I'm not sure whether it's CbB, or it's the MIDISport drivers. There hasn't been any recent changes in CbB's MIDI behaviour, and the MIDISport drivers haven't been updated in a long time. That being said, Windows updates have been coming along regularly, and it's not uncommon for them to break stuff with MIDI - it's happened before a few times. I'll do a bit more investigation and get back to you. Thanks for reporting this.
  24. IMO the Korg nanoKONTROL Studio is one of the best of the lower price hardware control surfaces. I use it daily in my office. The nanoKONTROL 2 is also very good. For motorized faders, Mackie MCU, Presonus FaderPort 8 or 16 and Behringer X-Touch are all good. The Icon series are good too, but you need to be careful to select a model that actually supports Cakewalk/SONAR.
  25. FWIW - I almost exclusively use Crucial MX500's nowadays. They're the only SSD's that have never let me down.
×
×
  • Create New...