Latest, Greatest Minitaur Editor - Get It Here

[fingersound]

Hello there,

there seems to bea serious problem with win xp with all the minitaur- editors. I tried all editors in this post and also the first"official" one and nothing worked (well,at least not with the 3 different win xp-machines I tried with...). The result was exactly as described by smut in his own posting. Dear amos please help the old fashioned xp-users!!!

[ashtarbrian]

Well I got an email yesterday or the day before announcing the new minitaur editor, which is 1.0 and appears to be the same as the one we have had for the last coupla weeks... (I am on OSX 10.6.8.), my real beef with the editor, is the way it saves patches, as it writes them apparently to the software itself, not to an external .xml file, or something that can be transported from system to system. Also, installing the new version LOSES all previous created patches. This is ridiculous and should be addressed. I had build a large number of patches, (not that it is that hard to program the minitaur, it's no Matrix12 or anything ), but there definitely should be a better preset save option.

My other complaint is that, as mentioned by other users above, the capture feature is sporadic at best. Which is actually worse then not having it at all. I save a patch, go to another, muck around a little, go back to the first, and around 50% of the time it is nothing near to what I had saved.... I honestly would rather not have it at all, and work that way, then something that works just when the starts are aligned properly...

It is also weird that the Editor has to be set up every time to route to the Minitaur in the USB setup, I know of no other device that has to be reset every time you instantiate it, perhaps having some user/application support/settings saved would appease this problem, as well as the user preset abomination. At the very least, in the install notes you could WARN people that they will lose everything they have done, and thus keep a backup of the older editors... (which has been my workaround, not very elegant for sure).

I mean not to criticize too much, as I love the minitaur, it works with pretty much everything i do on some level, and the editor is added value to a great device, so to harp on an ancillary add-on may come off a tad ingracious, but I think these things could be easily fixed, and a lot more of us would herald and champion the product to everyone.

Thanks!

[till]

You may open the application bundle with the right hand click on the program icon and find your patches saved inside the folder "Contents/Resources/data/presets".

The Pros for having the sound data inside the program file is, that you don't have to care where to save the file and from where to load then back again. Very iOS like approach.

The Cons is loosing files while swapping one version with another. And that most users won't be able to export their files for sharing with friends. Or importing patches from others.

[Moog Music]

Further updates and fixes for the Editor are definitely in the plans.

You definitely don't lose any presets; as Till has said, on the Mac you must control-click on the app icon and choose "Show Package Contents" to view the data/presets folder, where the presets are saved. You can copy from there, paste into the equivalent folder in the new version, email presets to friends, etc. Could this be made much friendlier and easier? Absolutely, and thanks for the suggestion.

[bozechicago]

I have downloaded both the current firmware and the editor from the email and have been experiencing a pretty significant and consistent crash.

1. Power up Minitaur
2. Launch Editor
3. Go to Under the Hood
4. Set input/output to Minitaur (connected straight to CPU or via hub, same issue).
5. Press Apple+1 for Presets
6......aaaand the app crashes.

this happens 19 times outta 20. Sometimes it makes it to the presets page.

If i open the presets page between steps 2&3, there is no crash until i try to change the file name.

Anyone else?

[bozechicago]

Hey, i think i found a pretty heavy bug with the editor....

Using the current firmware and the editor from the email...

1. Power on Minitaur
2. Open Under the Hood Window
3. Set Inputs and Outputs to Minitaur
4. Capture with Apple C
5. Open Presets Window
6. App crashes 19/20 times.

Can anyone else verify/replicate this bug?

[till]

Can anyone else verify/replicate this bug?

Some here, if I do it in exactly the same sequence with the editor open first.
But I can't recreate the other crash:

5. Press Apple+1 for Presets
6......aaaand the app crashes.

Using Mac OSX 10.8, straight USB connection, latest Minitaur Editor Version 1.0, Minitaur (firmware 1.07)

[timemaster]

Hey, i think i found a pretty heavy bug with the editor....

Using the current firmware and the editor from the email...

1. Power on Minitaur
2. Open Under the Hood Window
3. Set Inputs and Outputs to Minitaur
4. Capture with Apple C
5. Open Presets Window
6. App crashes 19/20 times.

Can anyone else verify/replicate this bug?

I get the exact same results every time. It will capture the setting, but trying to save it is useless

[anthroid]

i can replicate it every time.

Maybe the pointer passed to:

Code: Select all

Agg2D:attach(unsigned char*, unsigned int, unsigned int, int)

isn't getting allocated? Every crash I've had (which has been 20-30 times since I got the Minitaur yesterday) has happened during this call.

MacbookPro with Retina display (MacBookPro10,1)
Mac OS X 10.7.4
Minitaur Firmware version 1.0.7

Code: Select all

Process:         Minitaur Editor [8974]
Path:            /Applications/Minitaur Editor.app/Contents/MacOS/Minitaur Editor
Identifier:      com.moogmusic.Minitaur_Editor
Version:         1.0 (1.0)
Code Type:       X86 (Native)
Parent Process:  launchd [107]

Date/Time:       2012-09-01 12:56:05.242 -0500
OS Version:      Mac OS X 10.7.4 (11E2620)
Report Version:  9

Interval Since Last Report:          477566 sec
Crashes Since Last Report:           28
Per-App Interval Since Last Report:  12541 sec
Per-App Crashes Since Last Report:   7
Anonymous UUID:                      9A4B0250-0C2A-4DD8-93C0-BF163EAA1CD9

Crashed Thread:  0  Dispatch queue: com.apple.main-thread

Exception Type:  EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000004

VM Regions Near 0x4:
--> __PAGEZERO             0000000000000000-0000000000001000 [    4K] ---/--- SM=NUL  /Applications/Minitaur Editor.app/Contents/MacOS/Minitaur Editor
    __TEXT                 0000000000001000-00000000000e7000 [  920K] r-x/rwx SM=COW  /Applications/Minitaur Editor.app/Contents/MacOS/Minitaur Editor

Application Specific Information:
objc[8974]: garbage collection is OFF

Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   com.moogmusic.Minitaur_Editor 	0x00023fd9 Agg2D::attach(unsigned char*, unsigned int, unsigned int, int) + 21
1   com.moogmusic.Minitaur_Editor 	0x0005beb3 Surface::begin(bool) + 69
2   com.moogmusic.Minitaur_Editor 	0x00061be7 View::onLayoutChanged() + 29
3   com.moogmusic.Minitaur_Editor 	0x00063cd2 View::draw(Rect) + 176
4   com.moogmusic.Minitaur_Editor 	0x00063e68 View::draw(Rect) + 582
5   com.moogmusic.Minitaur_Editor 	0x00063e68 View::draw(Rect) + 582
6   com.moogmusic.Minitaur_Editor 	0x00064083 Window::draw() + 145
7   com.moogmusic.Minitaur_Editor 	0x0006138f Sugar::step() + 249
8   com.moogmusic.Minitaur_Editor 	0x0007829e sugarStep(int) + 118
9   com.moogmusic.Minitaur_Editor 	0x00079a94 -[OGLView drawRect:] + 125
10  com.apple.AppKit              	0x9a3ab8b5 -[NSView _drawRect:clip:] + 3717
11  com.apple.AppKit              	0x9a3dace2 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1958
12  com.apple.AppKit              	0x9a3a9212 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 708
13  com.apple.AppKit              	0x9a3aa37f -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 5169
14  com.apple.AppKit              	0x9a3a8817 -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 259
15  com.apple.AppKit              	0x9a3a3e9e -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 4817
16  com.apple.AppKit              	0x9a39cdc9 -[NSView displayIfNeeded] + 1365
17  com.apple.AppKit              	0x9a399b8d -[NSWindow displayIfNeeded] + 316
18  com.apple.AppKit              	0x9a39c698 _handleWindowNeedsDisplayOrLayoutOrUpdateConstraints + 804
19  com.apple.CoreFoundation      	0x9cf0bebd _runLoopObserverWithBlockContext + 29
20  com.apple.CoreFoundation      	0x9ced80ce __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 30
21  com.apple.CoreFoundation      	0x9ced800d __CFRunLoopDoObservers + 413
22  com.apple.CoreFoundation      	0x9ceaa984 __CFRunLoopRun + 1044
23  com.apple.CoreFoundation      	0x9ceaa1dc CFRunLoopRunSpecific + 332
24  com.apple.CoreFoundation      	0x9ceaa088 CFRunLoopRunInMode + 120
25  com.apple.HIToolbox           	0x9015e723 RunCurrentEventLoopInMode + 318
26  com.apple.HIToolbox           	0x901659b6 ReceiveNextEventCommon + 168
27  com.apple.HIToolbox           	0x901658fa BlockUntilNextEventMatchingListInMode + 88
28  com.apple.AppKit              	0x9a35c0d8 _DPSNextEvent + 678
29  com.apple.AppKit              	0x9a35b942 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 113
30  com.apple.AppKit              	0x9a357cb1 -[NSApplication run] + 911
31  com.apple.AppKit              	0x9a5e8bd9 NSApplicationMain + 1054
32  com.moogmusic.Minitaur_Editor 	0x00002075 start + 53

Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib        	0x9c99a90a kevent + 10
1   libdispatch.dylib             	0x9815de10 _dispatch_mgr_invoke + 969
2   libdispatch.dylib             	0x9815c85f _dispatch_mgr_thread + 53

Thread 2:
0   libsystem_kernel.dylib        	0x9c997c22 mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x9c9971f6 mach_msg + 70
2   com.apple.audio.midi.CoreMIDI 	0x00185fcb XServerMachPort::ReceiveMessage(int&, void*, int&) + 101
3   com.apple.audio.midi.CoreMIDI 	0x001a8f8b MIDIProcess::RunMIDIInThread() + 259
4   com.apple.audio.midi.CoreMIDI 	0x001a9912 MIDIProcess::MIDIInPortThread::Run() + 24
5   com.apple.audio.midi.CoreMIDI 	0x0018759f XThread::RunHelper(void*) + 17
6   com.apple.audio.midi.CoreMIDI 	0x00186f69 CAPThread::Entry(CAPThread*) + 123
7   libsystem_c.dylib             	0x92a1eed9 _pthread_start + 335
8   libsystem_c.dylib             	0x92a226de thread_start + 34

Thread 3:
0   libsystem_kernel.dylib        	0x9c99983e __psynch_cvwait + 10
1   libsystem_c.dylib             	0x92a22e21 _pthread_cond_wait + 827
2   libsystem_c.dylib             	0x929d342c pthread_cond_wait$UNIX2003 + 71
3   com.apple.audio.midi.CoreMIDI 	0x00186551 CAGuard::Wait() + 67
4   com.apple.audio.midi.CoreMIDI 	0x001872d1 Task::Run() + 341
5   com.apple.audio.midi.CoreMIDI 	0x0018759f XThread::RunHelper(void*) + 17
6   com.apple.audio.midi.CoreMIDI 	0x00186f69 CAPThread::Entry(CAPThread*) + 123
7   libsystem_c.dylib             	0x92a1eed9 _pthread_start + 335
8   libsystem_c.dylib             	0x92a226de thread_start + 34

Thread 0 crashed with X86 Thread State (32-bit):
  eax: 0x01000000  ebx: 0x00063c30  ecx: 0x01000000  edx: 0x00000000
  edi: 0x00023fd2  esi: 0x00000000  ebp: 0xbfffd5b8  esp: 0xbfffd570
   ss: 0x00000023  efl: 0x00010282  eip: 0x00023fd9   cs: 0x0000001b
   ds: 0x00000023   es: 0x00000023   fs: 0x00000000   gs: 0x0000000f
  cr2: 0x00000004
Logical CPU: 4

[Porksword909]

Cheers

Are there plans on making a plugin editor?
I'd be surprised if not, but Google told me nothing

[tagirov]

Is there a way to have some of the under the hood settings load on the minitaur as the default when it is not run via USB?

Hey Amos, does this revision of Minitaur Editor support 'Under the Hood' controls to remain with Minitaur away from a computer?

What you are asking for requires an update to the Minitaur internal firmware to support persistent preset memory. This is planned for the near future. So, not yet, but it's coming soon

Indeed, the ability to save user's own hardware defaults is very important feature request.
I use Minitaur for live and want to have my own default state of the synth.

Is there any progress on new firmware?

[hogo]

I guess there's not a lot of action here, but REV 2 of the minitaur software and firmware is quite awesome. Great job Amos and crew!

[bellay]

Hi

My System is Win7 x64
I am using the Minitaur Editor in conjunction with midiox/midiyoke, so I can use it whilst using the DAW at the same time.

I connected the Minitaur output with yoke1 which in turn is connected to the DAW and the editor as input. The DAW and the editor then use yoke2 as output, beeing connected to the input of the Minitaur. This worked great for some time. I was able to use the editor almost as well as if it was a plugin in my DAW. Loading and saving presets worked like a charm and I could easily change the 'under the hood' settings whilst playing and recording the Minitaur in my DAW. This worked well with all previous versions of the editor, but it changed with the new version (1_7_2012).

When I opened that editor the first time I was excited about the mass of new presets to get inspired by, so I tryed to load one of 'em up. That's when I had my first bluescreen. Beeing stubborn, I tried a few more times whith always the same result. I crashed the system three times - enough to corrupt system data, so I rebuild the filesystem and reinstalled all the VCredists, just to be sure.

Now I am not even able to use the editor on that computer. Everytime I start it, I get a short flash of the editor window followed by some message saying:
"
Microsoft Visual C++ Library

This application has requested the Runtime to terminate it in an unusual way.
Please contact the appliaction's support team for more information.
"

The editor is working great on another computer with also win x64. The new presets are pure win

I just reinstaled Windows 7, and now I'm getting the same error when I try to start the editor: "Microsoft Visual C++ Library

This application has requested the Runtime to terminate it in an unusual way.
Please contact the appliaction's support team for more information."

I tried to remove and reinstall all instances of Microsoft visual C, but nothing helps