Jump to content

Michal Ochedowski

Members
  • Posts

    59
  • Joined

  • Last visited

Everything posted by Michal Ochedowski

  1. Craig, thank you for your answer. You have confirmed that it's a proper way of sample preview and frequent sample rate conversion is a normal thing. To clarify, I'm using dedicated ASIO driver for my external soundcard. It's set to 48 kHz, my projects are always in 48 kHz. My settings in Reaper are exactly the same. That's why I compared sample browsing in both DAWs. My biggest issue with how Cakewalk handles sample preview is frequent sample rate conversion and multiple files being written to hard drive. I didn't mean overwriting original samples. I meant newly created files in "Audio Data" folder for each sample I click in the Media browser. Sometimes when I click the same sample three or four times, this file is overwritten in the same place - "Audio Data" folder. After each click it gets a new number in brackets right after sample's name. Bare in mind I'm still referring to new project without any saved data. Just sample browsing. I forgot to mention earlier that my main drive is SSD. All data involved with Cakewalk is handled by that drive. Repeated writing to SSD isn't exactly something good. That was main reason why I wanted to get someone else's opinion. I guess one of the workarounds will be changing "Audio Data" folder to directory on external hdd (regular magnetic type).
  2. I searched for answers online including this forum. It looks like no one asked this question before. Is it normal that while previewing samples in Cakewalk, every single file has to be converted to project's sample rate just to be played within the browser ? I mean situation where I don't import any data to tracks. I'm only listening to sounds clicking in the browser. Since I came here after using Reaper, I'm confused. In Reaper I never had to deal with multiple sample rate conversions while browsing sounds. Browsing samples didn't even involve creating peak files. I'm wondering if this is the only way Cakewalk can deal with samples having eg. 44.1 kHz rate when my project is in 48 kHz. It wouldn't bother me as much if it was single sample rate conversion for each file. It is not. I can click on three samples in a row and then click them again in the same or different order and every time they are converted to project's sample rate. Applied conversion is always indicated by message displayed for a second instead of "Current Now Time" at the top. Of course each time this happens, new file is being written to hard drive in main "Audio Data" folder. One more thing - when I close Cakewalk after multiple sample preview without saving a project, "Sample rate conversion" appears multiple times for a few seconds in the window mentioned above. Is this normal ? I'm aware that in Reaper sample rate conversion also may be taking place, behind the scenes. However it never involves constant writing and overwriting files on the hard drive. I'd appreciate some feedback on the subject.
  3. Thank you. Having this knowledge about what happens and why helps a ton! I didn't expect such generous response. I also received an email from Mike regarding my bug report. Great customer service!
  4. Noel, do you mean that in Clip Automation -> Gain view when envelope nodes are selected, Bounce to Clip(s) is disallowed but when in the same view clip or it's portion is selected, Bounce to Clip(s) is still going to be allowed ?
  5. Noel, thank you for checking it and letting us know. How I discovered this bug in the first place: I wanted to change Gain envelope for a copied portion of a clip and then bounce result to new clip. I wasn't looking for anything obscure, but it was there Disallowing bounce option in this scenario is a good idea. I just tried it again out of curiosity. This time newly bounced clip was twice the original length. For no reason Just to clarify - the changes you made today are going to be available for us after next Cakewalk update, correct ?
  6. I've sent a message to support with short info and link to this topic.
  7. Thank you for quick answer. This screen capture is brilliant! I also checked another scenario. Point 5 in my guide can also be changed to: Lower Gain envelope or draw some Gain automation in clip on Track 2. Then use Bounce to clip(s) action. Result is the same. Mono file.
  8. Hello. I would like to verify something. I wrote a step by step guide to recreate what for me is really unusual Bounce to Clip(s) behaviour. Everything below was performed with Smart Tool (F5). 1. Open empty project with single audio track - Track 1. 2. Drag a stereo sample to Track 1. 3. Mark any portion of the sample and copy it to Track 2. 4. On Track 2 in Edit Filter (underneath track name) choose Clip Automation - > Gain. 5. Right-click and drag over upper half of the sample on Track 2. I mean the part of the sample where red Gain line is displayed. 6. From Clips menu choose Bounce to Clip(s) action or use a custom keyboard shortcut. 7. Here is the strange part. As a result on Track 2 you should get a mono sample in place of the stereo sample. This mono sample will appear in Cakewalk's Audio folder. Also it's Clip name field will be blank. 8. In Edit Filter on Track 2 go back to Clips view. 9. Click and drag newly created mono sample to the right. 10. Now stereo sample should appear in the same place where this mono sample previously was. 11. As a result on Track 2 you now should have stereo sample in the same state as it was right after being copied from Track 1 + mono sample placed to the right of the stereo sample. I checked it. I do not have any shortcut assigned to Convert to Mono action. I did not change any of the clip's envelopes (pan, gain) prior to bouncing. I can't find any explanation to this behaviour. Why mono sample is created over a stereo sample ? Perhaps someone can recreate this and confirm, or simply explain.
×
×
  • Create New...