Hi all, 1C11 is up at <http://www.doggiebox.com/distribution/Doggiebox-1C11.tbz>. Release notes: • In the drum kit editor, textual instrument details are now copied to the clipboard (suitable for pasting into a text editor or spreadsheet). • A warning is now displayed after exporting a MIDI file when there are one or more missing MIDI assignments in the drum kit. • Incoming MIDI messages are now handled by the top-most window only, instead of all open documents simultaneously. • Fixed a problem where the playback indicator would not appear if playback were initiated via MIDI. • Added "None" as an option when specifying MIDI input and output devices. • Removed the seldom-used push- and pull-tempo buttons in interests of simplifying the interface. • Tweaked slightly the appearance of the mono/stereo button. I would appreciate it if everyone would report any remaining MIDI-related or other important issues that are still present, because this cycle has been dragging on long enough and is starting to shape up well enough that I'd like to get 1.2 out the door soonish if possible. -ben -- Ben Kennedy, chief magician zygoat creative technical services 613-228-3392 | 1-866-466-4628 http://www.zygoat.ca
Have had it crash a few times editing a drum kit, but there was no crashlog written(?): *** malloc[2657]: Deallocation of a pointer not malloced: 0x6a0a000; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug Sep 2 13:25:42 PowerBook last message repeated 11 times Sep 2 13:25:51 PowerBook crashdump: Started writing crash report to: /Users/headcrash/Library/Logs/CrashReporter/Doggiebox.crash.log Sep 2 13:25:51 PowerBook /usr/libexec/crashreporterd: crashdump[2667] exited due to signal 5 Sep 2 13:26:12 PowerBook kernel: hotfiles_evict: err 1celocating file 2004-09-02 13:26:36.123 Doggiebox[2670] offset is too large, given sound length and buffer size Sep 2 13:26:42 PowerBook kernel: hotfiles_evict: err 1celocating file 2004-09-02 13:27:17.309 Doggiebox[2670] offset is too large, given sound length and buffer size 2004-09-02 13:27:26.190 Doggiebox[2670] offset is too large, given sound length and buffer size Sep 2 13:28:42 PowerBook last message repeated 4 times *** malloc[2670]: Deallocation of a pointer not malloced: 0xffffffff; This could be a double free(), or free() called with the middle of an allocated block; Try setting environment variable MallocHelp to see tools to help debug Sep 2 13:34:12 PowerBook last message repeated 11 times Sep 2 13:34:16 PowerBook crashdump: Started writing crash report to: /Users/headcrash/Library/Logs/CrashReporter/Doggiebox.crash.log Sep 2 13:34:16 PowerBook /usr/libexec/crashreporterd: crashdump[2683] exited due to signal 5 --- Possible to add drag and drop to drum kit building (from other kits, samples, etc.)? Is there a way to shorten a sequence?
On 02 9 2004 at 4:38 pm -0400, Glenn Sugden wrote:
Have had it crash a few times editing a drum kit, but there was no crashlog written(?):
Hey Glenn, Thanks for the console.log output, I will look into this. Do you remember what you were doing at the time? Is there a sequence of steps you can do to reliably reproduce this?
Possible to add drag and drop to drum kit building (from other kits, samples, etc.)?
You can copy and paste drums between kits (though you can't currently drag and drop). You can however drag and drop sound files onto existing drums.
Is there a way to shorten a sequence?
What do you mean? -ben -- Ben Kennedy, chief magician zygoat creative technical services 613-228-3392 | 1-866-466-4628 http://www.zygoat.ca
Ben Kennedy wrote:
I would appreciate it if everyone would report any remaining MIDI-related or other important issues that are still present, because this cycle has been dragging on long enough and is starting to shape up well enough that I'd like to get 1.2 out the door soonish if possible.
Cool. Any tweaks on the MMC side of MIDI that might have it doing its thing at last? I gotta give it a spin when I get home :) I gotta try the MIDI export properly, too .... Ah, yes, the push-pull tempo slider ... yeah, I never really got comfy with it. It was simpler just to enter known changes directly for tempo shifts. Cheers, Carl -- Carl Edlund Anderson http://www.carlaz.com/
On 03 9 2004 at 5:05 am -0400, Carl Edlund Anderson wrote:
Cool. Any tweaks on the MMC side of MIDI that might have it doing its thing at last? I gotta give it a spin when I get home :) I gotta try the MIDI export properly, too ....
No output-related MMC tweaks. I'm not sure what problem was presented in 1C10, but given the prior one worked for you, perhaps we can assume it was a fluke. :) If you still have issues now though, let me know.
Ah, yes, the push-pull tempo slider ... yeah, I never really got comfy with it. It was simpler just to enter known changes directly for tempo shifts.
Yeah. The slider is still there, it's just the little "arrow" buttons that were beneath it. Sterling convinced me that they are probably useless. The only reason they came to be in the first place was because I had recorded some solo guitar track like a year and a half ago, and wanted to playback a drum pattern alongside it which I had made up after the fact. Of course the guitar tempo drifted, so I hacked those in so that I could keep DB approximately in time while I auditioned my drum track. :) -ben -- Ben Kennedy, chief magician zygoat creative technical services 613-228-3392 | 1-866-466-4628 http://www.zygoat.ca
On 03 Sep 2004, at 22:30, Ben Kennedy wrote:
No output-related MMC tweaks. I'm not sure what problem was presented in 1C10, but given the prior one worked for you, perhaps we can assume it was a fluke. :) If you still have issues now though, let me know.
OK, I managed to run another test tonight. I hooked everything back up and pressed play. The deck started recording and DB started counting, but there was no sound. Then after 10 seconds or so, the sound suddenly cut in and everything carried on to the end of the dbsong, where DB obiediently stopped itself and the deck. OK, that was pretty good, though the lack of sound at the very beginning worried me. So I went back to the begining, primed to record, and hit play on DB again. This time DB started counting and the deck started playing, but no sound, at all, ever. Multiple attempts and no sound. Another couple of dbsongs and the same behavior. I unplugged the cable from iBook to deck, just in case some weird setting on the deck was killing the sound, but DB wasn't outputting any sound to the iBook's speakers either. I restarted DB, then restarted the iBook and then DB -- no luck in either case. In fact not until I disconnected MIDI and rebooted and fired up DB again did sound start coming out. It's almost as if DB decided to mute audio when MIDI was active, despite that pref being unchecked. Sometimes I would pick a short selection and hit play, and DB would correctly start the deck recording and then stop it when the selection stopped, despite the lack of audio (though DB didn't always stop correctly). Then if I primed the deck to record and hit play on DB, DB would sometimes correectly send the "back to start" command before it started the deck recording, though not always. So MIDI signals are definitely working at least some of the time (DB always seems to get the "start recording" bit right now), but once the audio was dead, it was dead! Odd :) But different from previous builds, whether or not anything is supposed to have changed! Cheers, Carl -- Carl Edlund Anderson http://www.carlaz.com/
On 09 9 2004 at 4:14 pm -0400, Carl Edlund Anderson wrote:
I restarted DB, then restarted the iBook and then DB -- no luck in either case. In fact not until I disconnected MIDI and rebooted and fired up DB again did sound start coming out.
This is very odd. Thanks for your continued testing, Carl. Can anybody else confirm or deny successful MIDI operation with actual outboard MIDI gear? Carl, if you change the MIDI source/target in the Prefs from your device to "None", does DB then start making noise again, or is it equally whacked in that case? -ben -- Ben Kennedy, chief magician zygoat creative technical services 613-228-3392 | 1-866-466-4628 http://www.zygoat.ca
Ben Kennedy wrote:
Carl, if you change the MIDI source/target in the Prefs from your device to "None", does DB then start making noise again, or is it equally whacked in that case?
Hmmm, interesting idea -- I'll give it a try tonight or on the weekend! I'll recheck all the MIDI settings on the deck, too. I have been wondering whether my deck is listening for the right kind of MIDI signal (does DB output MTC of 30 frames per second? that seems to be a kind of "default", but I'm not sure just what DB does. what device ID would be correct? again 17 seems a kind of default, but ...) or perhaps the iBook is outputting a shaky MIDI signal I need to set my Sync Error Level setting on the deck higher .... But none of those things should affect DB's capacity to simply output audio, and DB's ability to correctly send the "play/start recording" command via MMC is the thing it most consistently gets right (in all the builds I've tried with expect 1C10), so there can't be _too_ much wrong with DB's MIDI output .... Cheers, Carl -- Carl Edlund Anderson http://www.carlaz.com/
On 10 9 2004 at 5:17 am -0400, Carl Edlund Anderson wrote:
I have been wondering whether my deck is listening for the right kind of MIDI signal (does DB output MTC of 30 frames per second?
Yep, should be sending quarter-frames based on 30 fps.
what device ID would be correct? again 17 seems a kind of default, but ...)
For MTC, there is no device ID because it is is just a MIDI real-time event that is not channel-specific. For the MMC play/stop commands, it's sending on device id 0x7f ("all devices"). Where does 17 come from?
perhaps the iBook is outputting a shaky MIDI signal I need to set my Sync Error Level setting on the deck higher ....
This could be. It would be interesting to examine the actual MIDI output in relation to what is supposed to be sending; I wonder if some stuff is getting dropped. If I had a DIN cable here I could hook up my MOTU deck and plug the MIDI out to the MIDI in, and watch what happens...
But none of those things should affect DB's capacity to simply output audio...
True, and that's what's baffling me. I have one other small theory, w/rt which I have made a small change in the code which hopefully I will post later today. How fast is your iBook, perchance? -b -- Ben Kennedy, chief magician zygoat creative technical services 613-228-3392 | 1-866-466-4628 http://www.zygoat.ca
Carl et al., <http://www.doggiebox.com/distribution/Doggiebox-1C12.tbz> This contains a minor change which I am hoping MIGHT be related to the MIDI/non-audio issue. Also, it contains updated documentation for 1.2. Re the midi issue, one other thing that you might check is to ensure that in prefs, the input device is set to "none" (since presumably you are not using your deck to start doggiebox, or are you?) -ben -- Ben Kennedy, chief magician zygoat creative technical services 613-228-3392 | 1-866-466-4628 http://www.zygoat.ca
On 11 Sep 2004, at 00:26, Ben Kennedy wrote:
This contains a minor change which I am hoping MIGHT be related to the MIDI/non-audio issue.
Woah! I think you did it! This is way cool. I ran 3 (well, 3-and-a-half) tests, and all were very successful. I hooked it all up and pressed play on DB, and DB started the deck recording, with strong audio output from the get-go. Very strong! I had to dial back the output volume to avoid peaking on my deck :) So then I stopped it (I think I tried to stop it by stopping DB first, and I think I remember this didn't work, but this is not a big deal at present) and DB, and then just for the heck of it I pressed play on DB and it successfully zeroed the record track before restarting it (with audio all good). It did seem to stagger a bit when doing so, but basically worked. Still, I manually stopped the deck and DB again, manually zeroed the deck and (with levels OK now), pressed play for a proper "drum take". It ran fine all the way through and stopped neatly at the end. I ran the same test again twice more, noting the final stopping times, and got very close results. The VS-1680 (and probably other Roland devices) counts in an SMPTE kind of way, in hours, minutes, frames (1/30 sec), and sub-frames (1/100 frame). In my three tests, the particular dbsong was clocked in by the DB UI at 5.55 (with a little "ring" after the last "hit"). In the three tests, my deck stopped at: 5m56s27f31sf 5m56s29f10sf 5m56s28f81sf That suggests, perhaps, that the MIDI output from my iBook may be a little flaky (and hey, it's going through a USB<>MIDI adapter). Given that only lag at the beginning of the piece matters much, I'm not sure how noticeable it will be. But I look forward to finding out! IMO, this is pretty excellently cool. I plan to slap some guitar and bass on my new drum part and then go back to try swaping out the drum part using the MMC start feature and see how it sounds (though not tonight .... :)
Re the midi issue, one other thing that you might check is to ensure that in prefs, the input device is set to "none" (since presumably you are not using your deck to start doggiebox, or are you?)
No, but theoretically I could, if it were possible to set DB as the slave. I'm not sure whether or not there would be a good reason to do this. In any event, I admit I didn't check the input device setting this time; I just plugged it in to see if it worked, and basically it did. So: cool :) Cheers, Carl -- Carl Edlund Anderson http://www.carlaz.com/
i might be a small minority but i do use the tempo-slider regularly. doggiebox is a great tool for my drum practice, and it is very handy to be able to dial down the tempo for patterns where my body is not yet up to the task. i.e. i start slow and work up. in fact, if the lower limit could be dropped to 25% or lower i would be a very happy camper. On Sep 3, 2004, at 2:30 PM, Ben Kennedy wrote:
Ah, yes, the push-pull tempo slider ... yeah, I never really got comfy with it. It was simpler just to enter known changes directly for tempo shifts.
Yeah. The slider is still there, it's just the little "arrow" buttons that were beneath it. Sterling convinced me that they are probably useless. The only reason they came to be in the first place was because I had recorded some solo guitar track like a year and a half ago, and wanted to playback a drum pattern alongside it which I had made up after the fact. Of course the guitar tempo drifted, so I hacked those in so that I could keep DB approximately in time while I auditioned my drum track. :)
On 11 9 2004 at 10:03 pm -0400, David Holloway wrote:
i might be a small minority but i do use the tempo-slider regularly.
I never had any plans to axe the tempo slider entirely (I'm not sure how I gave that impression), so no worries. :)
doggiebox is a great tool for my drum practice, and it is very handy to be able to dial down the tempo for patterns where my body is not yet up to the task. i.e. i start slow and work up. in fact, if the lower limit could be dropped to 25% or lower i would be a very happy camper.
Cool, I'll try to accommodate this soon. With the current layout of controls, I did not want to just drop the lower limit, because it would mean jumps of more than one percentage point per screen pixel of the slider which might get confusing. On the other hand if you have the apple dev tools installed, you could fire up Interface Builder and tweak the lower bound on the slider control, in the mean time... :) -b -- Ben Kennedy, chief magician zygoat creative technical services 613-228-3392 | 1-866-466-4628 http://www.zygoat.ca
On Sep 13, 2004, at 3:36 PM, Ben Kennedy wrote:
On the other hand if you have the apple dev tools installed, you could fire up Interface Builder and tweak the lower bound on the slider control, in the mean time... :)
excellent! i do happen to have this this at my disposal... thanks for the tip. d.
participants (4)
-
Ben Kennedy -
Carl Edlund Anderson -
David Holloway -
Glenn Sugden