Jump to content

kokobeware

Member
  • Posts

    117
  • Joined

  • Last visited

kokobeware's Achievements

  1. I was hoping for something that would scan the folder and only convert the 32 bit files and leave the 24 and 16 bit untouched. This will convert and replace all files to 24 bit, which might not be a bad thing if I can't find another app to do it. Cheers
  2. I have a folder that contains sub-folders and thousands of samples of 16, 24 and 32 bit files. I want to convert the 32 bit to 24 bit and replace the original file with the same filename. Any suggestions of apps that will allow this as a one step batch process?
  3. Just tried some tests of the sidechain compensation with Logic Compressor, FabFilter Pro C-2, FabFilter Pro-MB, DMG Multiplicity. Logic Compressor and Pro-C2 are compensated perfectly. The two multibands are not. Not sure if that's a multiband problem? I was sending the kick on Audio 1 to the sidechain and auditioning the sidechain. Then removing output of Audio 1 and bouncing to line up audio. Also got different results for Pro-MB depending on if it was on an audio track or an instrument track. Weird. Instrument track Pro-MB 888 samples Multiplicity 1981 samples Audio track Pro-MB 213 samples (early so chopping off beginning of bounce) Multiplicity 1981 samples
  4. I posted the 2 bugs below in the 10.5 thread and Apple Feedback and happy to report that they've both been fixed in 10.5.1 "If I unlock/lock a screenset, the screenset goes blank and when I click the number at the top it say No Project Open but if I change to a different screenset the project is still open. Did some testing and the Link is causing this issue. On 10.4.8 my template Link is set to Content and solo region performs properly. 10.5.0 with Link set to Content, solo region shoots you to the deepest folder level. Can get solo region to work properly if I set Link to Off."
  5. That worked thanks! And it seems if you do it once, it's fixed if I now want to unlock/lock any other screensets. Looks like a bug I'll report. Found out if you have a screenset with a floating window like an Event Float or floating Environment window locked in the screenset, then you try to unlock/lock, this bug will appear.
  6. Did some testing and the Link is causing this issue. On 10.4.8 my template Link is set to Content and solo region performs properly. 10.5.0 with Link set to Content, solo region shoots you to the deepest folder level. Can get solo region to work properly if I set Link to Off. Tried it on fresh session, without my template and it behaves like that. Can someone please confirm?
  7. That worked thanks! And it seems if you do it once, it's fixed if I now want to unlock/lock any other screensets. Looks like a bug I'll report.
  8. Anyone notice anything weird opening an older template? If I unlock/lock a screenset, the screenset goes blank and when I click the number at the top it say No Project Open but if I change to a different screenset the project is still open. Soloing a region brings me to the inner most folder I have hidden with groove templates. Can't figure that one out. I think I"m going to build my template from scratch in 10.5 just to be sure.
  9. I was worried that was the case. I've already sent feedback, hopefully they'll add back. I've used the below commands for ages. When I'm in the arrange I'm using keys near transport control for fast stop, start, rec. When I'm editing audio I always want right hand on mouse and left hand to navigate. - Global Commands Go to Selection Start + (numeric keypad) Go to Selection End - (numeric keypad) - Audio File Editor Go to Selection Start Q Go to Selection End W
  10. Can someone please confirm that they've actually removed the following key commands: "Go to Selection Start/End" from the Audio File Editor section and are forcing you to use the "Go to Selection Start/End" from the Global Section? I've used different commands for both sections for 25 years, that would be a kick to the nuts.
  11. Thanks for that. Anyway to disable this behaviour?
  12. Update. I figured out the problem started by selecting a small area, maybe a quarter of a bar with the marquee tool across 12-15 tracks. Then somehow Auto Drop was enabled and that's why recording was happening on all those tracks. Auto Drop was not in the toolbar to begin with, but then appeared there when the problem started. I checked the key commands and no key command was assigned to Auto Drop. So I understand why all the tracks were getting recorded on, but don't understand why Auto Drop was getting initiated.
  13. I'll have to wait for it to happen again and they contact me and I'll have them grab screenshots. I had them quit Logic and reopen and it still acted that way. I think they only fixed it by restarting the Mac.
  14. I have two clients that I believe have pressed something and now when they record midi, it will record on all midi tracks and trigger all midi instruments. I can't reproduce it. I've had them test with the Musical Typing Keyboard with the same result so it's not their midi controller. Anyone have any idea what key command they could of pressed so I can disable them?
×
×
  • Create New...