#Mixbus quantizing update#
#Mixbus quantizing upgrade#
#Mixbus quantizing pro#
#Mixbus quantizing Pc#
#Mixbus quantizing plus#

is NOT claiming that these features are not available elsewhere.

will mark features available in Ardour.

unless I note that it’s new in Mixbus 6.

is about any features in Mixbus, not just Mixbus 6.

Here we go with another list! This article… More than half of these items are not discussed previously. I don’t like to replicate previous content, but some of the items here have been discussed previously. I hope that this is made clear enough that you can filter it out if you want. I’ve attempted to provide an objective list of features that you can evaluate.

I have a big soft spot for Ardour both because of its goals and its functionality.

I speak to multiple employees of Harrison in both a professional and friendly context with frequency.

I acquired my copies of Mixbus 5 and 6 without cost.

The Live article was an extension of thought of this original article. I originally wrote a “10 things about Mixbus” article in late December, but I decided to “wait until after NAMM”. This is in stark contrast to my previous article about Ableton Live. Last resort.buy an old MAC off Mixbus 6 arriving on the scene, I decided I wanted to highlight some features that Mixbus has that I wish every DAW had. An Intel i5 GIGABYTE Board w/ 16GB RAM, Lenovo AMD i7 (equivalent) w/solid state drive & 8GB RAM and lastly an old AMD (i5 equivalent) w/16GB RAM.Īll my windows versions are legit.all stable systems.

#Mixbus quantizing pro#

I have 3 different Win 10 Pro PC's running at the minute that I can try. I know in the past, all my issues were on shutting down Mixbus.my new interface will arrive tomorrow. I got a generic message from Mixbus stating that they have Mixbus on WIndows platforms running fine, it must be my equipment. My worst fear is that it is a Mixbus/Windows prob, not a FireWire/USB issue. Last kick at the can.I ordered a 4in/4out USB interface.

#Mixbus quantizing plus#

Plus the fact to get plugins working.had to use CARLA as there are not many Linux plugins that are simillar to the windows ones that I like. Only issue now is it has a few pops and clicks/studders now and again and it drives me bonkers! I have tried samnple rate settings, buffer settings, etc.best I could get was a studder on start up of track record/playback (when I hit the space bar for first time). I got it to a point where mixbus was running and all the outboard gear was configured.I got it working and was able to record from my firewire interface. I abandonded Windows.spent a week setting up and learning Linux.

#Mixbus quantizing Pc#

I GOT THE SAME ISSUE! I am starting to think it is something other than it not liking my FireWire set up, as this PC had a native FW connection on the motherboard.no wonky PCI card connection. This was a completely different PC with AMD (instead of Intel) processor. I knew as soon as it did that, the next time I reopen Mixbus, it will be corrupted and.it was. Went to shut down and on exit, it went to blue screen, then reboot. I tried a test with a mic and I thought everything was ok. I played around with it and loaded a few plugins, scanned for new ones etc. All looked good, it saw my FireWire Connection.I loaded Mixbus 6 32C. I basically built a new PC, reformatted HD and reloaded Win 10 Pro.

#Mixbus quantizing update#

So, I just wanted to post an update as this whole issue has become a nightmare. So I am no computer expert, but it sounds like it has an issue writing my preferences when it is closing.

I would assume the error would come back when mixbus tries to close on the next use though. But it worked for close to a year with Mixbus 5.so I still lean towards a PC HDD or BIOS issue.Īpparently this PFN_LIST_CORRUPT error can be bypassed by deleting my preferences folder in '(home folder)/AppData/Local/Mixbus'. I have read that the firewire card (PCI with 1394 legacy driver) can create problems.

#Mixbus quantizing upgrade#

If nothing else works, time to upgrade to a USB interface. My limiting factor is my firewire interface. And to top it all off, I remember a Win 10 update about a week before my issues started. More likely PC hardware as my interface has worked with Mixbus 5 and 6 (non 32C) with no prob. Mixbus support basically told me that they have windows machines running with no issues, so it is likely a hardware issue or an interface issue. I have an identical PC but with a stable OS. It has never worked 'flawlessly', random BSOD over the years. There is a good possibility there is a HDD issue. Thanks for the input, yes my next step is to abandon this PC all together.