Am Mon, 09 Mar 2009 19:00:30 -0500 schrieb "Gabriel M. Beddingfield" <[email protected]>:
> [email protected] wrote: > > also more than 50% from fx_and sample_fun features don't work without that. > > maybe it's > > ok. and maybe nobody is interested to implement the really useful features > > from this > > branch. but if yes, we > > OK, I build the fx fun branch today. Nice stuff! I especially like the > sample > editor. my favourite is the note_key stuff to e.g. play samples like a melodic instrument. it's great for e.g nice experimental noises samples or melodic industrial sound samples.and since midi_out you also can use this samples as shapes for a connected midi out synth. you can tune every instrument with the instrument pitch and edit every note with a special key. also you can edit the relative midi note key to play e.g all the time a quart from every note. i love this :-)) and i spend the most develop on this note_key feature. it's the main feature from this branch. with a connected keyboard correct note length from every note in one pattern will recorded. of course only if ignore note_off is not activated. for a longer note_off over e.g. 2 pattern you can use the special note_off note. you also can play and record chords. but in moment only with a midi keyboard. blah blah :-) there are lot of nice and useful secrets into the branch. i planed a video tutorial for all features . but well.... the time to do this. also, the technical problem to do this. e.g. sync sound. > > Here's a rundown on how I think merging will go: > > 1. Most of the stuff in the GUI will require minor refactoring to get it > working. To get it working "right" will require only minor changes. When I > took nPosition out of Note... the DrumPatternEditor gave me the most > trouble... > but it was manageable. > > 2. #1 includes the sample editor. > > 3. I plan to have full support for MIDI In and Out on the transport_redesign > branch. I doubt much of the current code would be salvaged... but (if all > goes > the way I imagine it) it will not be difficult to replace, either. > > 4. Destructive recording will be the most interesting to merge. Right now, > all > of the realtime record code is in Hydrogen::addRealtimeNote()... which is > kind > of a hack to begin with. In the transport_redesign... it will look something > like this pseudo-code: > > class RealtimeRecording : public SeqClientInterface > { > public: > > int process(SeqScriptConstIterator& beg, > SeqScriptConstIterator& end, > const TransportPosition& pos, > uint32_t nframes) > { > SeqScriptConstIterator k; > Pattern* pat = Hydrogen::get_song()->get_pattern(pos); > > for( k = beg ; k != end ; ++k ) { > // Manipulate the pattern based on the SeqEvent's > // (*k) is H2Core::SeqEvent > // It's possible that some of the addRealtimeNote stuff > // could be modified to work here. > } > } > > }; // class RealtimeRecording > if you follow the forum thread you can see that this feature will created together with the forum member. the implementation use the mostly the Hydrogen::addRealtimeNote(). but the full destructive mode (default in destructive combo box) also act into inline int audioEngine_updateNoteQueue( unsigned nFrames ) . search for 'doErase' to find this. > Anyway... I would, of course, help with the merge. :-) :-)) thx. > > Peace, > Gabriel wolke ------------------------------------------------------------------------------ _______________________________________________ Hydrogen-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/hydrogen-devel
