Page 2 of 4
Re: Latest, Greatest Minitaur Editor - Get It Here
Posted: Thu Jul 05, 2012 9:39 pm
by Amos
muksys wrote:Amos,
There seams to be an issue with the Capture where it sometimes selects the Square Wave when in fact it is set to Saw, or it selects the Glide when it is in fact off. [...] I am running Minitaur FW 1.01 and WIN7 64bit.
you might want to try updating your Minitaur firmware. Here's the current production version:
http://seamslikereality.com/moog/Minita ... _7_MAC.zip (mac)
http://seamslikereality.com/moog/Minita ... _7_WIN.zip (windows)
Re: Latest, Greatest Minitaur Editor - Get It Here
Posted: Fri Jul 06, 2012 4:52 am
by tommy-
hey, great thing
very happy with it, but i have to ask (sorry), will there be a vst? i would definitly pay some euro to get it as vst into ableton that would be great.
edit:
Still got that one really annoying bug,
when i press "Under the Hood" sometimes the presets window opens and when that happened once i cant press anything in presets and cant go back to under the hood until i restart the programm. windows 7 64bit.
Re: Latest, Greatest Minitaur Editor - Get It Here
Posted: Fri Jul 06, 2012 5:32 am
by secmast
Amos wrote:secmast wrote:Got it crash (Mac version) when I want to save the preset impossible to save them.
Anyone else having this issue ?
I am testing Mac version on OSX 10.7.3 and I can save presets, no problem.
What OS version do you use?
Where on your computer (what folder/directory) did you install the editor?
I wonder if it's somehow possible that the app does not have permission to save to disk, in some configuration...
anyone else, can you report if saving presets is or is not working for you? Any other crash or problem reports?
Thanks!
10.7.4 and it is installed on the Application directory.
Sometimes I can use the preset sometimes just opening the preset windows it simply crash.
Here is the report:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000ff191919
VM Regions Near 0xff191919:
CG backing stores 00000000c83af000-00000000c8598000 [ 1956K] rw-/rw- SM=SHM
-->
Submap 00000000ffff0000-00000000ffff2000 r-x/r-x process-only submap
Re: Latest, Greatest Minitaur Editor - Get It Here
Posted: Fri Jul 06, 2012 10:27 am
by Amos
Thanks, guys! This is the kind of testing and feedback we need to be sure we deliver the best possible product.
I found a little work-around for the Windows bug, I think... it seems to work OK if you leave all the windows (under the hood, presets, front panel) open... problem happens when I x out of one of the windows and then try to re-open a different one. Once I had them all displayed at once, it seemed to work OK again. Obviously, we need to fix the source of the problem... but it's nice to work around it in the meanwhile...
Re: Latest, Greatest Minitaur Editor - Get It Here
Posted: Fri Jul 06, 2012 11:41 am
by muksys
Amos,
This seems to have fixed the issue. I verified the FW with the FW_Version_Cmd.sys file and it shows it's at 1.07 now. Thanks bunches! I'll let you know if it happens again.
Re: Latest, Greatest Minitaur Editor - Get It Here
Posted: Sat Jul 07, 2012 5:37 am
by DavyP
Had a bit of a play with this and seems to be pretty stable. No issues as yet on Mac OSX 10.7.3. Having fun now trying out and tweaking the various sounds. Id no idea the Minitaur was so versatile, Ive as usual barely scratched the surface of what it can do
Re: Latest, Greatest Minitaur Editor - Get It Here
Posted: Sat Jul 07, 2012 1:05 pm
by till
secmast wrote:10.7.4 and it is installed on the Application directory.
Sometimes I can use the preset sometimes just opening the preset windows it simply crash.
Here is the report:
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x00000000ff191919
VM Regions Near 0xff191919:
CG backing stores 00000000c83af000-00000000c8598000 [ 1956K] rw-/rw- SM=SHM
-->
Submap 00000000ffff0000-00000000ffff2000 r-x/r-x process-only submap
Some here, Amos!
I am using Mac OSX 10.7.4 on an iMac 2.66 GHz Intel Core 2 Duo, 4 GB RAM and I just got this when opening the preset window:
Code: Select all
Process: Minitaur Editor [5068]
Path: /Users/USER/Documents/*/Minitaur Editor.app/Contents/MacOS/Minitaur Editor
Identifier: com.moogmusic.Minitaur_Editor
Version: 1.0 (1.0)
Code Type: X86 (Native)
Parent Process: launchd [2057]
Date/Time: 2012-07-07 18:58:31.977 +0200
OS Version: Mac OS X 10.7.4 (11E53)
Report Version: 9
Sleep/Wake UUID: 5C0BD9A0-BAE2-4820-8230-0E772C7048D1
Interval Since Last Report: 657741 sec
Crashes Since Last Report: 1
Per-App Interval Since Last Report: 2311 sec
Per-App Crashes Since Last Report: 1
Anonymous UUID: 6CF59DC9-ECC2-4663-BA19-C84CC308524A
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 /Users/USER/Documents/*/Minitaur Editor.app/Contents/MacOS/Minitaur Editor
__TEXT 0000000000001000-00000000000e7000 [ 920K] r-x/rwx SM=COW /Users/USER/Documents/*/Minitaur Editor.app/Contents/MacOS/Minitaur Editor
Application Specific Information:
objc[5068]: garbage collection is OFF
Performing @selector(showPresetsAction:) from sender NSMenuItem 0x24ac50
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 com.moogmusic.Minitaur_Editor 0x00024969 Agg2D::attach(unsigned char*, unsigned int, unsigned int, int) + 21
1 com.moogmusic.Minitaur_Editor 0x0005c813 Surface::begin(bool) + 69
2 com.moogmusic.Minitaur_Editor 0x0006253d View::onLayoutChanged() + 29
3 com.moogmusic.Minitaur_Editor 0x00064622 View::draw(Rect) + 176
4 com.moogmusic.Minitaur_Editor 0x000647b8 View::draw(Rect) + 582
5 com.moogmusic.Minitaur_Editor 0x000649b9 Window::draw() + 145
6 com.moogmusic.Minitaur_Editor 0x00061cef Sugar::step() + 249
7 com.moogmusic.Minitaur_Editor 0x00078bb6 sugarStep(int) + 103
8 com.moogmusic.Minitaur_Editor 0x0007a022 -[OGLView drawRect:] + 143
9 com.apple.AppKit 0x91d668b5 -[NSView _drawRect:clip:] + 3717
10 com.apple.AppKit 0x91d95ce2 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 1958
11 com.apple.AppKit 0x91d96083 -[NSView _recursiveDisplayAllDirtyWithLockFocus:visRect:] + 2887
12 com.apple.AppKit 0x91d64212 -[NSView _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 708
13 com.apple.AppKit 0x91d63817 -[NSThemeFrame _recursiveDisplayRectIfNeededIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:topView:] + 259
14 com.apple.AppKit 0x91d5ee9e -[NSView _displayRectIgnoringOpacity:isVisibleRect:rectIsVisibleRectForView:] + 4817
15 com.apple.AppKit 0x91d57dc9 -[NSView displayIfNeeded] + 1365
16 com.apple.AppKit 0x91d54b8d -[NSWindow displayIfNeeded] + 316
17 com.apple.AppKit 0x91e16b7b -[NSWindow _reallyDoOrderWindow:relativeTo:findKey:forCounter:force:isModal:] + 1418
18 com.apple.AppKit 0x91e165ec -[NSWindow _doOrderWindowWithoutAnimation:relativeTo:findKey:forCounter:force:isModal:] + 79
19 com.apple.AppKit 0x91e164af -[NSWindow _doOrderWindow:relativeTo:findKey:forCounter:force:isModal:] + 997
20 com.apple.AppKit 0x91e16059 -[NSWindow orderWindow:relativeTo:] + 126
21 com.apple.AppKit 0x91e15821 -[NSWindow makeKeyAndOrderFront:] + 69
22 com.moogmusic.Minitaur_Editor 0x0007a3df -[OGLView showPresetsAction:] + 133
23 com.apple.CoreFoundation 0x90ed0d11 -[NSObject performSelector:withObject:] + 65
24 com.apple.AppKit 0x91e2086f -[NSApplication sendAction:to:from:] + 232
25 com.apple.AppKit 0x91f13e43 -[NSMenuItem _corePerformAction] + 536
26 com.apple.AppKit 0x91f13ac0 -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 171
27 com.apple.AppKit 0x91f13149 -[NSMenu _performActionWithHighlightingForItemAtIndex:sendAccessibilityNotification:] + 79
28 com.apple.AppKit 0x921eefcb -[NSMenu performActionForItemAtIndex:] + 65
29 com.apple.AppKit 0x921eeffe -[NSMenu _internalPerformActionForItemAtIndex:] + 45
30 com.apple.AppKit 0x921f322f -[NSMenuItem _internalPerformActionThroughMenuIfPossible] + 106
31 com.apple.AppKit 0x9205978c -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 172
32 com.apple.AppKit 0x91e89446 NSSLMMenuEventHandler + 452
33 com.apple.HIToolbox 0x92ca8dec _InvokeEventHandlerUPP(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*, long (*)(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*)) + 36
34 com.apple.HIToolbox 0x92b244f3 _ZL23DispatchEventToHandlersP14EventTargetRecP14OpaqueEventRefP14HandlerCallRec + 1602
35 com.apple.HIToolbox 0x92b23970 _ZL30SendEventToEventTargetInternalP14OpaqueEventRefP20OpaqueEventTargetRefP14HandlerCallRec + 482
36 com.apple.HIToolbox 0x92b38755 SendEventToEventTarget + 76
37 com.apple.HIToolbox 0x92ca92b0 _ZL18SendHICommandEventmPK9HICommandmmhPKvP20OpaqueEventTargetRefS5_PP14OpaqueEventRef + 482
38 com.apple.HIToolbox 0x92ca931a SendMenuCommandWithContextAndModifiers + 70
39 com.apple.HIToolbox 0x92d14b61 SendMenuItemSelectedEvent + 275
40 com.apple.HIToolbox 0x92b74f2d _ZL19FinishMenuSelectionP13SelectionDataP10MenuResultS2_ + 129
41 com.apple.HIToolbox 0x92d05a60 _ZL14MenuSelectCoreP8MenuData5PointdmPP13OpaqueMenuRefPt + 608
42 com.apple.HIToolbox 0x92b6cbde _HandleMenuSelection2 + 636
43 com.apple.HIToolbox 0x92b6c95d _HandleMenuSelection + 53
44 com.apple.AppKit 0x91d86dbc _NSHandleCarbonMenuEvent + 302
45 com.apple.AppKit 0x91d176c6 _DPSNextEvent + 2196
46 com.apple.AppKit 0x91d16942 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 113
47 com.apple.AppKit 0x91d12cb1 -[NSApplication run] + 911
48 com.apple.AppKit 0x91fa3bd9 NSApplicationMain + 1054
49 com.moogmusic.Minitaur_Editor 0x00002a15 start + 53
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x95c2790a kevent + 10
1 libdispatch.dylib 0x90472e10 _dispatch_mgr_invoke + 969
2 libdispatch.dylib 0x9047185f _dispatch_mgr_thread + 53
Thread 2:
0 libsystem_kernel.dylib 0x95c24c22 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x95c241f6 mach_msg + 70
2 com.apple.audio.midi.CoreMIDI 0x00183f67 XServerMachPort::ReceiveMessage(int&, void*, int&) + 101
3 com.apple.audio.midi.CoreMIDI 0x001a6f5b MIDIProcess::RunMIDIInThread() + 259
4 com.apple.audio.midi.CoreMIDI 0x001a78e2 MIDIProcess::MIDIInPortThread::Run() + 24
5 com.apple.audio.midi.CoreMIDI 0x0018553b XThread::RunHelper(void*) + 17
6 com.apple.audio.midi.CoreMIDI 0x00184f05 CAPThread::Entry(CAPThread*) + 123
7 libsystem_c.dylib 0x9525ded9 _pthread_start + 335
8 libsystem_c.dylib 0x952616de thread_start + 34
Thread 3:
0 libsystem_kernel.dylib 0x95c2683e __psynch_cvwait + 10
1 libsystem_c.dylib 0x95261e21 _pthread_cond_wait + 827
2 libsystem_c.dylib 0x9521242c pthread_cond_wait$UNIX2003 + 71
3 com.apple.audio.midi.CoreMIDI 0x001844ed CAGuard::Wait() + 67
4 com.apple.audio.midi.CoreMIDI 0x0018526d Task::Run() + 341
5 com.apple.audio.midi.CoreMIDI 0x0018553b XThread::RunHelper(void*) + 17
6 com.apple.audio.midi.CoreMIDI 0x00184f05 CAPThread::Entry(CAPThread*) + 123
7 libsystem_c.dylib 0x9525ded9 _pthread_start + 335
8 libsystem_c.dylib 0x952616de thread_start + 34
Thread 4:
0 libsystem_kernel.dylib 0x95c2702e __workq_kernreturn + 10
1 libsystem_c.dylib 0x9525fccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x952616fe start_wqthread + 30
Thread 5:
0 libsystem_kernel.dylib 0x95c2702e __workq_kernreturn + 10
1 libsystem_c.dylib 0x9525fccf _pthread_wqthread + 773
2 libsystem_c.dylib 0x952616fe start_wqthread + 30
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x41370000 ebx: 0x00064580 ecx: 0x41370000 edx: 0x00000000
edi: 0x00024962 esi: 0x00000000 ebp: 0xbfffdb28 esp: 0xbfffdae0
ss: 0x00000023 efl: 0x00010282 eip: 0x00024969 cs: 0x0000001b
ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f
cr2: 0x00000004
Logical CPU: 1
It does not happen every time. Got no pattern for this behavior yet.
Re: Latest, Greatest Minitaur Editor - Get It Here
Posted: Tue Jul 10, 2012 3:40 pm
by goldphinga
Please can I get a version that works on 10.5.8. I can't use the software at all as it stands..
Re: Latest, Greatest Minitaur Editor - Get It Here
Posted: Wed Jul 11, 2012 7:17 am
by secmast
Hi,
Any news with the problem on preset "load/save" causing a crash on 10.7.4 ?
Re: Latest, Greatest Minitaur Editor - Get It Here
Posted: Sat Jul 14, 2012 1:30 pm
by Genric DeFaulde
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
Re: Latest, Greatest Minitaur Editor - Get It Here
Posted: Sun Jul 15, 2012 8:02 pm
by Amos
Nothing yet, but this is a priority for the coming week, so we should see a new version soon. I'm not sure about 10.5.8 compatibility; I'll try to find out what the minimum system requirements are.
Till: On the PC version, a crash happens if you display the preset window, then X out of preset window, then display Under the Hood window. I think it also happens in the complimentary case, open Under the Hood window, close Under the Hood, then open Presets. Perhaps this sequence causes consistent error for you also?
Re: Latest, Greatest Minitaur Editor - Get It Here
Posted: Sun Jul 15, 2012 10:37 pm
by muksys
Amos,
Found an itty bitty bug.
If I have more than 1 window active (or all 3) then minimize one of them, the window(s) go blank until I maximize the first window that was minimized.
I am running WIndows 7, Editor 1.0, Minitaur 1.0.7.
Re: Latest, Greatest Minitaur Editor - Get It Here
Posted: Sun Jul 15, 2012 11:28 pm
by s0bie
I can't seem to get any correspondence between the editor and my minitaur. I'm running windows 7 and I am updated to the current firmware. My midi set up is with the minitaur as the in and out and I can't seem to get any midi in. I can't get any of the presets to work either. Anyone have any idea of what I could be doing wrong?
Re: Latest, Greatest Minitaur Editor - Get It Here
Posted: Mon Jul 16, 2012 4:41 pm
by till
s0bie wrote:I can't seem to get any correspondence between the editor and my minitaur. I'm running windows 7 and I am updated to the current firmware. My midi set up is with the minitaur as the in and out and I can't seem to get any midi in. I can't get any of the presets to work either. Anyone have any idea of what I could be doing wrong?
If you don't use a direct PC to Minitaur connection, try this first. Some USB hubs are evil for MIDI data.
Re: Latest, Greatest Minitaur Editor - Get It Here
Posted: Mon Jul 16, 2012 4:47 pm
by till
Amos wrote:... Till: On the PC version, a crash happens if you display the preset window, then X out of preset window, then display Under the Hood window. I think it also happens in the complimentary case, open Under the Hood window, close Under the Hood, then open Presets. Perhaps this sequence causes consistent error for you also?
I am unable to find a certain pattern to recreate the crash on demand. It just happens sometimes. But it never happens, when fiddling around with the editor without a connected Minitaur or any other USB except for the QWERTY keyboard. So I think it needs some Minitaur data to get the crash.