Jeremy Oakes

2 hours ago, marled said:

I did this upgrade a long time ago. Although they say it can detect polyphonic material please just be prepared that for many stuff it doesn't work! Nevertheless I can remember a positive case when a keyboarder reached 2 keys instead of one and I could remove the faulty one. My impression is that polyphonic material only works for very clean material like piano (that was the positive case above), picked accoustic guitar and such stuff, forget about synthesizer, vocals and the like! 😖

It works for vocals - getting things in tune for example. you can easily ( sic ) work out which blobs refer to the voice. and modify them.

i also use it for bass - to tame things down. But recently i’ve been converting it to midi, then i use a soft synth - a good way to get rid of finger “clicks” or transients.

YMMV,

Jerry

3 hours ago, Blogospherianman said:

My Computer had updated to 1903 and my first session after (using the Liquid Saffire 56 with a TI Chipset firewire card) was hiccuping and actually recorded glitching in the audio where the hiccups occurred.  This prompted me to roll back and read more on Focusrite’s website where I found the info about it not being compatible.  Luckily RX7 helped me fix the glitches. 😄 The LS 56 has always been a stable and solid beast for me till now though.  Glad for those who are still running perfectly though.  Hiccups don’t inspire confidence with customers. 

Roll back to what ?

Jerry

On 11/27/2019 at 6:39 AM, bvideo said:

Uh oh, Some of those Saffires are DICE-based. Drivers were always dicey. Any word about any other DICE-based interfaces going belly up in 1903?

Nope. My LS 56 is still purring along. Dice controller, FW card with TI chip, standard W10 drivers. Wonderful piece of kit. On W10 1903.

Jerry

On 11/15/2019 at 6:12 PM, Robert Bone said:

My best advice is to try to leave all things USB plugged into the very first port you ever plugged them into, so that these issues don't even crop up.  It is one GIANT pain in the rear to have to go through all of that in the first place, so leaving things plugged into the same ports is the easiest path to avoiding the issues.

I literally took a picture of the back of my computer, and then edited it to add text labels with arrows, pointing to each USB port and named each device so if I ever had to unplug and reconnect the USB devices, I could hopefully get them back into the same ports.

Bob Bone

Yes, this is almost what i do - i make a sketch. 

J

On 11/12/2019 at 7:53 PM, Robert Bone said:

I had an issue with a midi controller, where it worked like a champ outside of Cakewalk, and had worked fine IN Cakewalk, but it began looking inert one morning, and I thought maybe its midi port had been moved, but since I had it plugged into my computer's front panel, I could see that it had not moved.

Turned out that a friend of mine had unplugged my audio interface, and had plugged it back into a different port, and moving THAT device somehow resulted in a reshuffling of ports and devices in Windows, and that confused Cakewalk.

The fix for me, was to remove the midi controller as a midi input device in Preferences, then click Apply, then save the project, open it again, and then add the midi controller back in as a midi input device, and THEN it started working.  I had to go through this for every project I opened.  QUITE the pain.

So - maybe worth a quick try - so recapping:

1) Open a project where your controller isn't working

2) Go into CbB preferences and remove your midi controller from an input midi device, and I suppose midi output device as well

3) Click apply

4) Save the project and exit

5) Open the project again

6) Add the midi controller again, in Preferences, as a valid midi input and midi output device.

7) Click Apply and save project - see if that worked.  

Anyways, the above steps fixed my issues, which seem similar - controller quitting working in CbB but working fine elsewhere in other apps.

Bob Bone

 

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

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

7 minutes ago, Promidi said:

As a test, If you create a single MIDI track.  Set the M-Audio keyboard as it's input. set to OMNI. Do you see the MIDI meter activity for that track when you press keys?

Thanks for the test, but nope, nothing ! 
J
 

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

5 hours ago, Colin Nicholls said:

Yeah, I did that. I'm offered the download for Focusrite Control 3.4.4. I'm sure that if I installed it, it would install the actual driver with the updated version number.

Sorry for the confusion. In my case, at least, I'm getting very good performance with the older driver and no incentive to update it, although I probably will at some point.

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

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 minutes ago, Bajan Blue said:

I've spent way more on divorce attorneys.

 

Ha ha, brilliant - and a great way to look at the true costs of even the most expensive software -!!!

Nigel

Me too, but it still hurts when you see their upgrade price.

At least i didn’t have to upgrade  the lawyers fees, they were fixed.

Jerry

 

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

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

I finallyheard from Focusrite who admitted there is a problem and they are investigating. They recommend sticking with v 2.4.5.

cheers,

J

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

@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

On 8/25/2019 at 12:31 AM, Ben Staton said:

We ran into this recently too, and logged it with Focusrite. I believe they're looking into it.

I suggest maybe rolling back to the previous driver version and/or sticking with ASIO mode.

It also wouldn't do any harm to log it with Focusrite directly.

Ahhhhh, so I wasn’t dreaming .

already logged and awaiting a reply

J

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 

12 hours ago, studiodude1 said:

Focusrite is only showing version 3.2.1 as available now. No new driver available.

That is the “new” software/driver package

Jerry

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

9 hours ago, Chuck E Baby said:

That stinks man, sorry to hear this.

Im not sure I can add anything to help here except maybe trying deleting AUD.INI and let Cakewalk Rebuild a new one.

I don't know im reaching here. Maybe a corrupt AUD.INI.

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

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

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

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

Goldwave is a great audio editor

J