I've (finally!) found the time to start using DoggieBox, and I love it so far... However, I'll be posting a few (hopefully helpful!) suggestions as I dive into more and more of it: 1) Could you please save the "expanded/contracted state of the song window? 2) How about a warning/no-saving of empty MIDI export files? 3) Could you please add a "normalization" feature? Is that a really newbie-audio-person thing to ask? :-D Thanks again for a great proggie - which saved me a lot of time writing my own drum-box. ;-) --- I'm listening to "Headhunter V1.0" by Front 242 from Front by Front [Re-release] <http://www.gracenote.com/music/search.html? q=Front+242+Front+by+Front&f=artist&f=disc&x=0&y=0>
On 29 8 2004 at 3:23 pm -0400, Glenn Sugden wrote:
1) Could you please save the "expanded/contracted state of the song window?
Yes, I'll improve this eventually, thanks. Also, a future version will support discontiguous zooming of bars (i.e. you could have some zoomed while others were not). For those curious about how the latter will behave, feel free to try out <http://www.doggiebox.com/beta/Doggiebox-1D1.zip>. Warning: this build is OLDER than 1C10. Note also that the zoom state is not persistent across changes of selection in the playlist/section lists, but is intended to be.
2) How about a warning/no-saving of empty MIDI export files?
What do you mean?
3) Could you please add a "normalization" feature? Is that a really newbie-audio-person thing to ask? :-D
I agree this would be useful; the problem is how best to implement it. The peak in any song can change at any time due to simple adjustment of tempo or changing of drums, so to reliably calculate peak for export normalization would require a two-stage rendering on output.
Thanks again for a great proggie - which saved me a lot of time writing my own drum-box. ;-)
Glad you like it 8) Are you a developer? -ben -- Ben Kennedy, chief magician zygoat creative technical services 613-228-3392 | 1-866-466-4628 http://www.zygoat.ca
On Aug 30, 2004, at 2:08 PM, Ben Kennedy wrote:
2) How about a warning/no-saving of empty MIDI export files?
What do you mean?
I thought I had some MIDI data in a file, exported it to MIDI, and ended up with a 0 byte file... maybe a warning that can be disabled?
3) Could you please add a "normalization" feature? Is that a really newbie-audio-person thing to ask? :-D
I agree this would be useful; the problem is how best to implement it. The peak in any song can change at any time due to simple adjustment of tempo or changing of drums, so to reliably calculate peak for export normalization would require a two-stage rendering on output.
Understood. Please see the e-mail I just sent. :-)
Glad you like it 8) Are you a developer?
Yup. :-D http://www.aggroculture.com/resume/ (A bit out of date ;-) ::Glenn --- I'm listening to "Neologic Spasm" by Front Line Assembly from Hard Wired <http://www.gracenote.com/music/search.html? q=Front+Line+Assembly+Hard+Wired&f=artist&f=disc&x=0&y=0>
On 30 8 2004 at 6:07 pm -0400, Glenn Sugden wrote:
I thought I had some MIDI data in a file, exported it to MIDI, and ended up with a 0 byte file... maybe a warning that can be disabled?
Ah I see, in the case where there are no MIDI events assigned to the kit that you are exporting with... that could happen. Thanks, that is a good point. Actually, I will set it up to raise a warning whenever there is >= 1 missing assignment, since doing a MIDI file export in such a scenario is likely unintentional (i.e. you don't want missing drums). -b -- Ben Kennedy, chief magician zygoat creative technical services 613-228-3392 | 1-866-466-4628 http://www.zygoat.ca
participants (2)
-
Ben Kennedy -
Glenn Sugden