Please help! I can't get rg to use any softsynth- what am I not doing? (
hooked up fluidsynth, timidity, tried zyn- ...still nothing.... any ideas??
On Mon, Oct 24, 2011 at 2:12 AM, <
rosegarden-user-requ...@lists.sourceforge.net> wrote:
> Send Rosegarden-user mailing list submissions to
> rosegarden-user@lists.sourceforge.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/rosegarden-user
> or, via email, send a message with subject or body 'help' to
> rosegarden-user-requ...@lists.sourceforge.net
>
> You can reach the person managing the list at
> rosegarden-user-ow...@lists.sourceforge.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Rosegarden-user digest..."
>
>
> Today's Topics:
>
> 1. Re: Ramped tempo changes aren't ramped when exported as MIDI?
> (Thorben Dahl)
> 2. Re: Ramped tempo changes aren't ramped when exported as MIDI?
> (Abrolag)
> 3. MIDI file with broken BPM (Dan Muresan)
> 4. Re: MIDI file with broken BPM (Dan Muresan)
> 5. Re: Ramped tempo changes aren't ramped when exported as MIDI?
> (Lorenzo Sutton)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sat, 22 Oct 2011 21:50:54 +0200
> From: Thorben Dahl <thorbend...@gmail.com>
> Subject: Re: [Rosegarden-user] Ramped tempo changes aren't ramped when
> exported as MIDI?
> To: Chris Cannam <can...@all-day-breakfast.com>
> Cc: rosegarden-user@lists.sourceforge.net
> Message-ID: <4ea31e9e.4090...@gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 22 October 2011 20:09, Chris Cannam wrote:
> > This is not _hard_ as such, but it is fiddly, and it's worth noting
> > that the exported MIDI files would end up with multiple fixed tempi in
> > them if re-imported, rather than ramped tempi.
> Thank you for so quick replies! That goes for both of you :-D
>
> Personally, I wouldn't mind the ramp being "emulated" by multiple tempo
> changes, although I think it should be mentioned somewhere ;-)
>
> I really appreciate the work all of you put into Rosegarden, and I
> understand it if this little bug is too time-consuming or fiddly to fix.
> All in all, I like Rosegarden a lot!
>
> Thorben
>
>
>
> ------------------------------
>
> Message: 2
> Date: Sat, 22 Oct 2011 21:30:46 +0100
> From: Abrolag <abro...@users.sourceforge.net>
> Subject: Re: [Rosegarden-user] Ramped tempo changes aren't ramped when
> exported as MIDI?
> To: rosegarden-user@lists.sourceforge.net
> Message-ID: <20111022213046.02b46b25@debian>
> Content-Type: text/plain; charset=UTF-8
>
> On Sat, 22 Oct 2011 19:09:18 +0100
> Chris Cannam <can...@all-day-breakfast.com> wrote:
>
> > On 22 October 2011 18:51, D. Michael McIntyre
> > <michael.mcint...@rosegardenmusic.com> wrote:
> > > When I think about it, I'm surprised more people haven't run into
> this. ?Tempo
> > > ramps were never fully implemented from the beginning, years ago now,
> and
> > > nobody ever came back to finish the job. ?If my memory is correct, the
> MIDI
> > > export side of things is the one bit nobody ever finished.
> >
> > That's right -- I left that part undone when I added the ramped tempo
> > feature in 2006, and as far as I know nobody has looked at it since.
> >
> > MIDI doesn't have any way to represent a ramped tempo, so to implement
> > it would, I think, mean having to emit a tempo change at each event,
> > calculated so as to give the correct time gap to the next event. That
> > is, using e.g. Composition::getRealTimeDifference to convert the gap
> > to real time, and then picking the fixed tempo that would result in
> > the musical time gap being converted to the same real time.
> >
> > This is not _hard_ as such, but it is fiddly, and it's worth noting
> > that the exported MIDI files would end up with multiple fixed tempi in
> > them if re-imported, rather than ramped tempi.
> >
> >
> > Chris
> So this is not really a bug as such but a limitation in MIDI.
> However, pushing my luck a bit :)
> How about arranging it so that when importing such a file, if Rosegarden
> sees a
> lot of tempo changes less than, say, 100mS apart, it translates those as a
> ramp?
>
> --
> Will J Godfrey
> http://www.musically.me.uk
> Say you have a poem and I have a tune.
> Exchange them and we can both have a poem, a tune, and a song.
>
>
>
> ------------------------------
>
> Message: 3
> Date: Sun, 23 Oct 2011 22:56:59 +0300
> From: Dan Muresan <danm...@gmail.com>
> Subject: [Rosegarden-user] MIDI file with broken BPM
> To: Rosegarden-user <rosegarden-user@lists.sourceforge.net>
> Message-ID:
> <CAJ6Zc6O3190ysp-6Pxo87fwut=b9o_8bvzilzwwqu7kcrtg...@mail.gmail.com
> >
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hi,
>
> I have a MIDI file that I'm trying to use in RG, alongside other
> tracks (some audio, some RG MIDI). It turns out the MIDI file has a
> broken BPM setting (120 instead of 128). If I force the BPM in
> rosegarden to 128, the imported MIDI track won't match up with my
> other tracks (e.g. audio tracks). If I keep the BPM at 120, I won't be
> able to edit other MIDI tracks in RG (they won't match up with my
> audio tracks, again).
>
> To make matters worse, the Adjust -> Stretch dialog is completely
> non-intuitive and won't allow me (AFAICT) to stretch by a specified
> fraction, i.e. 128 / 120.
>
> Is there a way to change the BPM, but preserve the absolute durations
> in the imported MIDI track? Or to stretch by a specific fraction?
>
> Or, as a workaround, is there some other utility to edit a MIDI file
> and change the broken tempo (short of going into a hex editor)?
>
>
> Thanks,
> Dan
>
>
>
> ------------------------------
>
> Message: 4
> Date: Sun, 23 Oct 2011 23:08:13 +0300
> From: Dan Muresan <danm...@gmail.com>
> Subject: Re: [Rosegarden-user] MIDI file with broken BPM
> To: Rosegarden-user <rosegarden-user@lists.sourceforge.net>
> Message-ID:
> <caj6zc6pv-ogpeb0puppwpubekkwlqv88cyxeavvjvmpwsyp...@mail.gmail.com
> >
> Content-Type: text/plain; charset=ISO-8859-1
>
> > Or, as a workaround, is there some other utility to edit a MIDI file
> > and change the broken tempo (short of going into a hex editor)?
>
> Scratch that. The MIDI file has *correct absolute durations*, but a
> *broken BPM header*. So changing the BPM in a hex editor would be the
> same as changing the tempo in RG. I tried it with the obvious result.
>
> -- Dan
>
>
>
> ------------------------------
>
> Message: 5
> Date: Mon, 24 Oct 2011 10:15:14 +0200
> From: Lorenzo Sutton <lsut...@libero.it>
> Subject: Re: [Rosegarden-user] Ramped tempo changes aren't ramped when
> exported as MIDI?
> To: rosegarden-user@lists.sourceforge.net
> Message-ID: <4ea51e92.3040...@libero.it>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On 22/10/2011 19:51, D. Michael McIntyre wrote:
> > On Saturday, October 22, 2011, Thorben Dahl wrote:
> >
> >> Hello! I'm experiencing what I think is a bug, but what are your
> thoughts?
> >>
> >> When I export a MIDI file in Rosegarden, none of my ramped tempo changes
> >> act as ramped, instead acting as fixed tempo changes.
> >
> > It's a bug, and there is no way to work around it.
>
> Yes I remember this was discussed a while ago when someone asked about
> 'fermatas'
>
> A *very hackish* workaround if one really needed midi-file export could
> be to re-record the ramped midi 'live' at a fixed tempo thus
> 'hardcoding' the tempo changes to a new project and then exporting that
> to midi (see attached examples)
>
> Anyway it seems Rosegarden is not alone with ramp problems ;) have a look:
>
> http://www.cubase.net/phpbb2/viewtopic.php?p=761195&sid=82aa48082f7bce488a4358918839bd76
>
> Anyway I agree that as the ramps are linear the exported midi file
> (maybe have an option??) should hold the tempos that 're-create' the map,
> I guess the tricky part is to decide what "resolution" it should have.
>
> Lorenzo.
> >
> > When I think about it, I'm surprised more people haven't run into this.
> Tempo
> > ramps were never fully implemented from the beginning, years ago now, and
> > nobody ever came back to finish the job. If my memory is correct, the
> MIDI
> > export side of things is the one bit nobody ever finished.
> >
> > I'll try to take a look over the weekend and see if I think I have any
> hope of
> > getting that taken care of myself. If so, I'll give it a shot, and if
> not,
> > which is rather likely I'm afraid, it's just going to have to continue
> to be
> > broken until someone else fixes it.
>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: ramp.rg
> Type: application/octet-stream
> Size: 10457 bytes
> Desc: not available
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: ramp_workaround.rg
> Type: application/octet-stream
> Size: 10849 bytes
> Desc: not available
>
> ------------------------------
>
>
> ------------------------------------------------------------------------------
> The demand for IT networking professionals continues to grow, and the
> demand for specialized networking skills is growing even more rapidly.
> Take a complimentary Learning@Cisco Self-Assessment and learn
> about Cisco certifications, training, and career opportunities.
> http://p.sf.net/sfu/cisco-dev2dev
>
> ------------------------------
>
> _______________________________________________
> Rosegarden-user mailing list
> Rosegarden-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/rosegarden-user
>
>
> End of Rosegarden-user Digest, Vol 65, Issue 7
> **********************************************
>
------------------------------------------------------------------------------
RSA(R) Conference 2012
Save $700 by Nov 18
Register now
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user
