Jump to content

Jeremy Oakes

Members
  • Content Count

    168
  • Joined

  • Last visited

Everything posted by Jeremy Oakes

  1. Well this worked for me - many thanks for the tip Bob. I also deleted some of the ghosted USB ports mentioning devices no longer in use. Whether that also helped is a moot point. So like you Bob, i’ll do that now for each project ......’.. Best, J
  2. Many thanks for your suggestions, tried and tested but no luck. one thing i am getting now is an error box when opening a Dim Pro stand alone : Box is called “ midilnOpen[] ” with a message “error opening midi device”, I then select Oxygen 61 and it plays fine Thanks, J
  3. Hello, I have this M-Audio keyboard that used to work fine in Sonar and in Cakewalk. I play it through a soft synth. After not using it for a a month or so I fired it up in a project and I can't get any sound through Dimension Pro. Here's what I've done to trouble shoot : * Updates : both W10 Pro and Cakewalk are fully updated. The unit has the latest firmware - there are no drivers for it - its class compliant * Opened up the stand-alone version of Dim Pro (and also Rapture ) and lo and behold I can get sound, so the keyboard is sending a signal. I also checked with Midi Ox. * Checked the I/O routing : Midi track input (Oxygen Omni, I, 2, etc I've tried them all) sending via the Dim Pro Stereo output. Audio track has the Primary Stereo out of Dim Pro selected as in , output going to master (I've tried different sound device outputs, to no avail. Input Echo is on. * Tried using other soft synths (eg : Lounge Lizzard - stand alone works fine, VST in Cakewalk does not. * Moved all the sliders, nobs, pads etc one by one, no luck. * Searched on the old Sonar website and this one for inspiration, no luck. Any ideas what I'm doing wrong ? Its certainly user error, as the thing plays in stand alone's, so what am I missing ? All the best, J
  4. The driver is included in the software .exe file. In other words you install the control and the driver gets installed. shame they don’t make the driver available separately......... on my system i stll get BSOD’s with the new drivers, i had to roll back. L’ve had a ticket open with them for a few months, but they seem to be ignoring it. One of the Bakers chimed in on a previous post saying they also had reported a problem. i guess we live in hope .... Jerry
  5. I do this for our group. I split the long recordings into manageable length projects then work on each one. To keep the same sound levels can be problematic due to things like guitarists fiddling with volume pots between quiet and loud moments, your ears will tell you what levels to use. Personally i would not use one long track, its much easier nce everything’s been split up to work on individual tracks. Others may see otherwise, but this is my workflow. Jerry
  6. They’ve updated the USB driver in the 3.4.0 package, but don’t bother, it still gives a bad pool header and BSOD, at least on my system. In WhoCrashed, the Focusrite USB driver is still the culprit. Maybe one day...................... cheers, J
  7. As usual from Magix the upgrade path is horrendously expensive. 149€ from SFpro 12 ..... https://www.magix.com/gb/music/sound-forge/sound-forge-pro/ Jerry
  8. I finallyheard from Focusrite who admitted there is a problem and they are investigating. They recommend sticking with v 2.4.5. cheers, J
  9. No, its not the same as for the 18i20 second gen https://customer.focusrite.com/support/downloads?brand=Focusrite&product_by_range=552&download_type=software cheers, J
  10. @filo : is this driver part of the newly released 3.2.1 package from Focusrite ? If so, there’s another fred where Ben Statton from Cakewalk confirms my op. i still haven’t heard anything positive back from Focusrite. J
  11. Ahhhhh, so I wasn’t dreaming . already logged and awaiting a reply J
  12. I don’t know, i was on v2. something so for me it was a new package and when installed it showed the new fly out tab they talked about in their mail was available Whatever, i advise not installing it as it BSOD’d each time i opened a project in CbB. WhoCrashed reported it was the focusrite usb driver each time. so i rolled back and am still waiting to hear from them. Jerry
  13. That is the “new” software/driver package Jerry
  14. I had a bad experience, see my post upstairs. Once i rolled back to the previous installation, all went well. Beware. i’ve got a ticket in with them, but so far no reply. Jerry
  15. Hi Chuck, thanks for the input. i rolled back to the previous drivers and .... without deleting the aud.ini file, no crashes using the same projects. Hopefully Focusrite will get back to me soonish. Jerry
  16. I got an e-mail from Focusrite this am and updated my 18i20 second gen as per instructions. Wow, 3 BSOD so far, “Bad Pool Caller” x 1 and “Kernal Heap “ something x 2 Nothing in my config changed since the up grade. I currently have a ticket in with them, It happens when i open a CbB project then start the song. I am up to date with everything (video, drivers etc), WhoCrashed indicates its focusriteusbaudio.sys that is the culprit. Anybody else have such an issue ? I’ll be rolling back to the previous software/drivers asap. Jerry
  17. I never use the metronome - i use the hi hat as a count in on the first bar. Melodyne i always use on small clips only. Its long, its a pain but it works superbly Jerry
  18. Have you tried bouncing them as clips before recording ? i always do that and have not come across this. You can always undo if the bounce is no good. J
  19. Heh, heh, as you said. There is a way ! I got the same deal from Audio Deluxe, invoiced in USD which when translated to Euros, is a really great price !!! jerry
  20. I hate it when people “boast” about their download speed 🤪. If you live in the country, at the distant of an ADSL link its more like 2 to 3 hours ..... yep i’m officially jealous !!:. J
×
×
  • Create New...