Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Butler read ahead failure on dsream auditioner error
#1
Most of my errors are blue. But this one is RED! I have no idea what this means.
I'm on MB 32C V7.2.0 (I have more info if you need it) and most all that I use works ok.
But I have no idea what this error means. So I am reaching out to you folks to see what I need to FIX this.
---- ERROR = 2022-10-25T16:23:10 [ERROR]: Butler read ahead failure on dstream auditioner
NOTE: If you see the other noted attached errors and can help PLEASE assist!
Thanks ahead!
-- Rich


Attached Files Thumbnail(s)
   
Mini Mac i7, 3 GHz, 16GB RAM, OSX Monterey v12.6.5, 4 SSD drives, dual 27" displays. Mixbus 32C Latest, SSL 2+ interface, Mackie VLZ 1402 mixer and Mackie Mk3 8" monitors. Owner of LOGIC AUDIO PRODUCTIONS, Lake Havasu City, Arizona USA Cool
Reply
#2
AFAIK butler is a framework for data management and is a part of the I/O and handling of audio files and or MIDI data.
I have seen that error a few times when micro looping or triggering playback a sample or two into the region.
As far as I am aware it indicates a one off event and is not really an issue.
Macmini 8,1 | OS X 13.6.3 | 3 GHz i5 32G | Scarlett 18i20 | Mixbus 10 | PT_2024.3.1 .....  Macmini 9,1 | OS X 14.4.1 | M1 2020 | Mixbus 10 | Resolve 18.6.5
Reply
#3
(10-25-2022, 10:00 PM)Dingo Wrote: AFAIK butler is a framework for data management and is a part of the I/O and handling of audio files and or MIDI data.
I have seen that error a few times when micro looping or triggering playback a sample or two into the region.
As far as I am aware it indicates a one off event and is not really an issue.

Just an additional thought...
Could this be contributed or caused the the BLUE errors? (see attachment in OP)
Thanks again Chief! Big Grin
Mini Mac i7, 3 GHz, 16GB RAM, OSX Monterey v12.6.5, 4 SSD drives, dual 27" displays. Mixbus 32C Latest, SSL 2+ interface, Mackie VLZ 1402 mixer and Mackie Mk3 8" monitors. Owner of LOGIC AUDIO PRODUCTIONS, Lake Havasu City, Arizona USA Cool
Reply
#4
(10-26-2022, 02:38 PM)rdesanti Wrote:
(10-25-2022, 10:00 PM)Dingo Wrote: AFAIK butler is a framework for data management and is a part of the I/O and handling of audio files and or MIDI data.
I have seen that error a few times when micro looping or triggering playback a sample or two into the region.
As far as I am aware it indicates a one off event and is not really an issue.

Just an additional thought...
Could this be contributed or caused the the BLUE errors? (see attachment in OP)
Thanks again Chief! Big Grin

I am almost certain that this is a MIDI issue. I NEED help on how to hook up a MIDI controller keyboard to my SSL 2+ and the mixbus preferences. I think this will solve this issue.
BTW having a more powerful computer like an M1 with 8 or more CPU's and like 32GB of RAM would definitely resolve this issue. But I'm a retired guy in these days BARELY getting by on my fixed SS budget. Just my thoughts. Thanks ahead Chief, totally respect your help.


Attached Files Thumbnail(s)
   
Mini Mac i7, 3 GHz, 16GB RAM, OSX Monterey v12.6.5, 4 SSD drives, dual 27" displays. Mixbus 32C Latest, SSL 2+ interface, Mackie VLZ 1402 mixer and Mackie Mk3 8" monitors. Owner of LOGIC AUDIO PRODUCTIONS, Lake Havasu City, Arizona USA Cool
Reply
#5
Assuming you have a 5pin MIDI device (keyboard, pad etc) plugged into the back of your SSL2+ ... OR a USB MIDI device (keyboard, pad etc) plugged in to your Mac...
In Applications / Other / Audio MIDI setup you should be able to see your MIDI device.....
   
Then follow the steps outlined https://rsrc.harrisonconsoles.com/mixbus...rding-midi
Macmini 8,1 | OS X 13.6.3 | 3 GHz i5 32G | Scarlett 18i20 | Mixbus 10 | PT_2024.3.1 .....  Macmini 9,1 | OS X 14.4.1 | M1 2020 | Mixbus 10 | Resolve 18.6.5
Reply
#6
(11-06-2022, 06:10 PM)rdesanti Wrote:
(10-26-2022, 02:38 PM)rdesanti Wrote:
(10-25-2022, 10:00 PM)Dingo Wrote: AFAIK butler is a framework for data management and is a part of the I/O and handling of audio files and or MIDI data.
I have seen that error a few times when micro looping or triggering playback a sample or two into the region.
As far as I am aware it indicates a one off event and is not really an issue.

Just an additional thought...
Could this be contributed or caused the the BLUE errors? (see attachment in OP)
Thanks again Chief! Big Grin

I am almost certain that this is a MIDI issue. I NEED help on how to hook up a MIDI controller keyboard to my SSL 2+ and the mixbus preferences. I think this will solve this issue.
BTW having a more powerful computer like an M1 with 8 or more CPU's and like 32GB of RAM would definitely resolve this issue. But I'm a retired guy in these days BARELY getting by on my fixed SS budget. Just my thoughts. Thanks ahead Chief, totally respect your help.

OK the keyboard is connected by the MIDI in/out on the SSL, plus I also have it plugged in the USB. Is that ok? OR should I go with one or the other?
Thanks Dingo! Merry Chrismas and Happy New Year buddy! Big Grin Cool
Mini Mac i7, 3 GHz, 16GB RAM, OSX Monterey v12.6.5, 4 SSD drives, dual 27" displays. Mixbus 32C Latest, SSL 2+ interface, Mackie VLZ 1402 mixer and Mackie Mk3 8" monitors. Owner of LOGIC AUDIO PRODUCTIONS, Lake Havasu City, Arizona USA Cool
Reply
#7
(12-22-2022, 11:15 AM)rdesanti Wrote:
(11-06-2022, 06:10 PM)rdesanti Wrote:
(10-26-2022, 02:38 PM)rdesanti Wrote:
(10-25-2022, 10:00 PM)Dingo Wrote: AFAIK butler is a framework for data management and is a part of the I/O and handling of audio files and or MIDI data.
I have seen that error a few times when micro looping or triggering playback a sample or two into the region.
As far as I am aware it indicates a one off event and is not really an issue.

Just an additional thought...
Could this be contributed or caused the the BLUE errors? (see attachment in OP)
Thanks again Chief! Big Grin

I am almost certain that this is a MIDI issue. I NEED help on how to hook up a MIDI controller keyboard to my SSL 2+ and the mixbus preferences. I think this will solve this issue.
BTW having a more powerful computer like an M1 with 8 or more CPU's and like 32GB of RAM would definitely resolve this issue. But I'm a retired guy in these days BARELY getting by on my fixed SS budget. Just my thoughts. Thanks ahead Chief, totally respect your help.

OK the keyboard is connected by the MIDI in/out on the SSL, plus I also have it plugged in the USB. Is that ok? OR should I go with one or the other?
Thanks Dingo! Merry Chrismas and Happy New Year buddy! Big Grin Cool
Please look at this again. I know you are a busy guy! BTW V9 is AWESOME!
Mini Mac i7, 3 GHz, 16GB RAM, OSX Monterey v12.6.5, 4 SSD drives, dual 27" displays. Mixbus 32C Latest, SSL 2+ interface, Mackie VLZ 1402 mixer and Mackie Mk3 8" monitors. Owner of LOGIC AUDIO PRODUCTIONS, Lake Havasu City, Arizona USA Cool
Reply
#8
(10-26-2022, 02:38 PM)rdesanti Wrote: Just an additional thought...
Could this be contributed or caused the the BLUE errors? (see attachment in OP)

It's a total guess but maybe try increasing your audio buffer size temporarily and see if the errors go away.
Knowledge is knowing a tomato is a fruit...
Wisdom is knowing you don't put tomatoes in a fruit salad !!
Reply
#9
Heart 
Even in V9 I am getting these Butler read errors. However in V9 it's pointing to a reference track. Dingo say's it's not a big deal and I have all green on everything else. Going to speak to Harrison about this as I LOVE a GREEN error log! Thanks to all who helped! Big Grin
Mini Mac i7, 3 GHz, 16GB RAM, OSX Monterey v12.6.5, 4 SSD drives, dual 27" displays. Mixbus 32C Latest, SSL 2+ interface, Mackie VLZ 1402 mixer and Mackie Mk3 8" monitors. Owner of LOGIC AUDIO PRODUCTIONS, Lake Havasu City, Arizona USA Cool
Reply
#10
Confused   I Too encounter the error Butler read ahead. How do U get rid of it?   Also: What's with the input/output channel count configuration not supported   Confused

Log displays this info:

"2024-03-12T22:14:09 [INFO]: Output channel count configuration not supported
 2024-03-12T22:14:09 [INFO]: Input channel count configuration not supported
 2024-03-12T22:14:10 [INFO]: Scanning folders for bundled LV2s: C:\Program Files\Mixbus32C-9\lib\ardour9\LV2
 2024-03-12T22:14:22 [INFO]: xjadeo version: 0.8.13
 2024-03-12T22:14:23 [INFO]: harvid version: 901
 2024-03-12T22:14:24 [INFO]: Loading menus from C:\Program Files\Mixbus32C-9\share\ardour9\ardour.menus
 2024-03-12T22:14:29 [ERROR]: Butler read ahead failure on dstream auditioner
 2024-03-12T22:14:29 [ERROR]: Butler read ahead failure on dstream auditioner

 2024-03-12T22:14:32 [INFO]: Loading user ui scripts file C:\Users\WillF\AppData\Local\Mixbus9\ui_scripts
 2024-03-12T22:14:32 [ERROR]: Butler read ahead failure on dstream auditioner
 2024-03-12T22:14:33 [INFO]: Loading plugin order file C:\Users\WillF\AppData\Local\Mixbus9\plugin_metadata\plugin_order
 2024-03-12T22:14:35 [INFO]: Loading history from H:\My Works\Harrison Mixbus\Meet Harry Harrision\Meet Harry Harrision.history
 2024-03-12T22:14:35 [INFO]: Meet Harry Harrision: no history file "H:\My Works\Harrison Mixbus\Meet Harry Harrison\Meet Harry Harrision.history" for this session."


Sad How do I fix this the above RE - Butler read ahead failure on dstream auditioner & INFO: input/output channel count ? 

(Meet Harry Harrision - Name of project)

Regards
Will Fisher

Heart System- Win 10 x64-Pro, auto-update, i7core 6700K 4.0 chip, 64Gb RAM @2133, Focusrite Scarlett 18i20 Audio interface, Dual monitors 4Gb Video card,   
Software: Mixbus32C-V9, Waves Mercury, PA All in 2023, Nomad Factory Suite III, NI 14-Ultimate, Arturia Collection V9 + FX4 
MIDI Controllers - Keylab Essential 49-MK3, Oxygen 88, Maschine MK2 & Alesis Vortex Keytar
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)