From: <b.o...@fr...> - 2006-06-16 19:10:22
|
Now lets have a look at Rosegarden. First of all: plugin all your equipment= and switch it on, PC's running 'cause you can read this, MIDI Out of your = Soundcard (there's an "OUT" on the plug) to MIDI IN of your Synth and MIDI = Out of Synth to MIDI IN of soundcard. Also try to get some speakers working= with your synth, hammer the keys and there ought to be some sound from the= speakers (not from breaking keys). Now start Rosegarden. All you'll see is an application with a menu (File, E= dit, Composition...) and a toolbar beneath it. There are funny colored symb= ols like a floppy disk, play-, stop, and record buttons and on the right si= de a "Q"-Symbol and next to it some keys (black/white) morping into a circu= it board. Press this button with your mouse's pointer (do not try to break = your screen or damage your TFT's surface). There'll be a funky new window with some text inside like =ABDevice=BB, =AB= Recording Device=BB and so on. There are some drop down lists, too, contain= ing your sound card (=ABM Audio Audiophile...=BB) and a line =ABgeneral mid= i device=BB, which is not a member of an army. This is a so called device m= apping. It says, that =ABGeneral Midi Device=BB will be mapped to =ABM Audi= o...=BB. If this is not contained in the dialog, mentioned before, get MIDI= working. Have a look at alsa.org and M-Audio-Section (ice1712 chipset). If dialog looks like this, =ABClose=BB it and return to the main window. No= w get the Pencil-Tool from the toolbar (looks like a pencil, righty right) = and move the mouse's cursor while you press the left mouse button over the = first track's area (on top there's a ruler, drag the segment from 1 to 4). = After doing so a green segment (green rectangle) is on your track. Right cl= ick it and choose =ABMatrix Editor=BB. You sill have the pencil tool select= ed, click on randomly chosen keys on the left side of the =ABMatrix Editor= =BB You ought to hear your Synth. If not, close this Matrix Editor, right c= lick the track's title on the left (says something like =ABunnamed=BB) and = choose =ABGeneral Midi Device=BB and your Synth's channel in the next menu.= This is called a =ABChannel Mapping=BB. You assigned a device and one of t= he device's channels to your track. Return to the Matrix Editor - now it wo= rks. If you never heard before phrases like =ABMidi Channel=BB, =ABMatrix Editor= =BB, =ABTracks=BB and =ABDevices=BB, you'd better read the Rosegarden Tutor= ial from begin to end very carefully. Recording's after that quite easy, so I won't explain it here. Basically yo= u'll have to determine the input device (if you had a closer look at the = =ABManage Midi Devices=BB-Dialog, you know where to look for) and set the c= hannel to record to (activate the the according recording switch left of th= e track's title and right of it's mute switch, bubble-like round thingy; ch= anging color when clicked) And to be honest, in your mail before you only mentioned, that you've answe= red to an already existing thread, not that you've found the tutorial. ----- original Nachricht -------- Betreff: Re: [Rosegarden-user] recording hardware synth sounds Gesendet: Fr 16 Jun 2006 17:32:47 CEST Von: "D. Michael 'Silvan' McIntyre"<ros...@gm...> > On Thursday 15 June 2006 6:32 pm, psykx.out wrote: > > Hello, I have read the rosegarden tutorial but i still can't work out > > how to get rosegarden to save or even store/understand hardware synth > > sounds. I have a roland xp-10 of which there is no bank for but I > > haven't really understood how to make a bank for it or even if it will > > solve my problems. >=20 > What are your problems? >=20 > Maybe try this alternate procedure: >=20 > http://rosegardenmusic.com/resources/documents/rgd-HOWTO.shtml >=20 > I think you can use that script on an .ins file from Cakewalk, so if you = can >=20 > find a Cakewalk .ins file describing the XP-10, maybe you have the work d= one >=20 > for you. >=20 > If all of that still doesn't get you there, I need to hand you to someone= =20 > else, because I've beaten this topic to death in the book, and if I still= =20 > haven't explained it to where you can understand it, then I *can't* expla= in >=20 > it to where you can understand it. Someone else might have better luck. >=20 > --=20 > D. Michael 'Silvan' McIntyre ---- Silvan > <dmm...@us...> > Linux fanatic, and certified Geek; registered Linux user #243621 >=20 > Author of Rosegarden Companion http://rosegarden.sourceforge.net/tutorial= / >=20 >=20 > _______________________________________________ > Rosegarden-user mailing list > Ros...@li... - use the link below to unsubscribe > https://lists.sourceforge.net/lists/listinfo/rosegarden-user >=20 --- original Nachricht Ende ---- =0A=0A=0A=0A=0A=0A=0A=0A |
From: <b.o...@fr...> - 2006-06-20 17:14:54
|
----- original Nachricht -------- Betreff: Re: [Rosegarden-user] recording hardware synth sounds Gesendet: Sa 17 Jun 2006 17:19:31 CEST Von: "D. Michael 'Silvan' McIntyre"<ros...@gm...> > On Friday 16 June 2006 8:41 pm, you wrote: >=20 > > I can play GM sounds from my keyboard with rosegarden but not any of my > > synth sounds or non GM sounds. I see know that I have to create a bank > > but I thought I would be able to (and would really like to) get > > rosegarden to simply record the midi data that comes in even if it > > doesn't understand it so it can replay it through the keyboard. e.g > > simply use rosegarden as a midi data storage device with the bonus of > > data editing and hydrogen support. > > > > Would i really have to make a new definition for each new sound? or can > > rosegarden understand the synth commands? >=20 > OK, so the problem is you're recording program changes Rosegarden doesn't > know=20 > anything about, and Rosegarden is just ignoring and dumping them. This= =20 > leaves you no real choice but to define programs for your gear, even thou= gh >=20 > you really have no particular need or desire to do that. It's extra work > for=20 > you to get to a place that any other MIDI sequencer would be out of the > box. >=20 > Is that about the size of it? >=20 I still don't get it, I use some Roland Equipment, too and for example my M= C 505 needed no additional information. I could insert PC- and CC-events to= cause program changes and I could hit record and got all the information c= aused by the MC 505, without any additional setup. After I while I found it boring to lookup all the programs in a chart and m= oved all the preset banks to a .rgd-file. All User Banks I just initialized= as 'user', was a bit of Copy & Paste for all banks but now it's quite neet= to just click =ABBank=BB, =ABProgram=BB and choose an entry. In addition to that Copy & Paste and Bank-editing I'd find it quite usefull= , if the dialogs wouldn' t reload that often after confirming the settings.= That causes a focus loss and I need to scroll a bit, if I manage a device = at the end of device list (for example). So after adding all the banks and = closing this dialog, the focus of the =ABManage Midi Devices=BB-dialog shou= ld stay on the edited device, not jump to the top and select the first entr= y. Maybe there could also be a nice init-Button, which inits a range of ban= ks with a given value. Makes it easier to setup dummy names for user banks,= while most synths have enough own memory (Saves time in comparison to writ= e SysEx-midi dumps to the cable).=0A=0A=0A=0A"Jetzt Handykosten senken mit = klarmobil - 14 Ct./Min.! Hier klicken"=0Ahttp://www.klarmobil.de/index.html= ?pid=3D73025=0A |
From: D. M. 'S. M. <ros...@gm...> - 2006-06-20 17:33:00
|
On Tuesday 20 June 2006 1:14 pm, b.o...@fr... wrote: > In addition to that Copy & Paste and Bank-editing I'd find it quite > usefull, if the dialogs wouldn' t reload that often after confirming the > settings. That causes a focus loss and I need to scroll a bit, if I manage > a device at the end of device list (for example). So after adding all the > banks and closing this dialog, the focus of the =ABManage Midi > Devices=BB-dialog should stay on the edited device, not jump to the top a= nd > select the first entry. Maybe there could also be a nice init-Button, whi= ch > inits a range of banks with a given value. Makes it easier to setup dummy > names for user banks, while most synths have enough own memory (Saves time > in comparison to write SysEx-midi dumps to the cable). The bank editor has all sorts of problems, and several very old outstanding= =20 bugs. That focus problem, the percussion checkbox not working properly, et= c. It's really a wretched thing to use, I think, but we don't get very many=20 complaints about it, and so it continues to occupy a very low place on our= =20 priority list. I figure most people opt for the alternative of using that= =20 script to turn a text file into an .rgd file, or they just have GM=20 instruments or something. If more people did anything with the bank editor= ,=20 we'd surely get a lot more complaints. =2D-=20 D. Michael 'Silvan' McIntyre ---- Silvan <dmm...@us...= t> Linux fanatic, and certified Geek; registered Linux user #243621 Author of Rosegarden Companion http://rosegarden.sourceforge.net/tutorial/ |
From: <b.o...@fr...> - 2006-06-21 15:24:32
|
> It's really a wretched thing to use, I think, but we don't get very many= =20 > complaints about it, and so it continues to occupy a very low place on ou= r=20 > priority list. I figure most people opt for the alternative of using tha= t=20 > script to turn a text file into an .rgd file, or they just have GM=20 > instruments or something. If more people did anything with the bank edit= or, >=20 > we'd surely get a lot more complaints. >=20 > --=20 > D. Michael 'Silvan' McIntyre ---- Silvan > <dmm...@us...> > Linux fanatic, and certified Geek; registered Linux user #243621 >=20 > Author of Rosegarden Companion http://rosegarden.sourceforge.net/tutorial= / >=20 >=20 I only wanted to point out, that there may be people, who do not use a piec= e of software as it was designed. That does not imply bad behaviour nor bad= software but shows, that there may be gap of interpreting objects of the r= eal world in a subjective context. Maybe that's why I don't understand the = problem behind =ABRecording Hardware Synths=BB and I seem to be a red liste= d species clicking all those funky knobs and see what will happen. (Maybe s= ome are bored after too much disappointment, don't want to register for a 1= 0th mailinglist or just died when pushing the wrong button [or got severly = injured]). I'd say it's nothing to complain about and I can live with that,= I don't create rgd-files that often. I like the GUI and I can handle some = =ABunexpected behaviour=BB, as well as I'm able to record hardware synths (= software synths too) just by following the steps from the manual - no magic= and no unnamed PC-whatevers (I remember that bank reset after recording wh= ich should be no problem to be solved by inserting a CC-event [CC32, bank n= umber] and a PC event [program number]) Maybe the synth's manual reveals ev= en more information 'bout SysEx and that sort of thing. I even managed to w= rite a small Qt-Application (PerlQt) to create specific SysEx-events to pre= set EFX, Reverb and so on (Roland MC 505 may not dump them seperatly). Basically I only wanted to keep the manual safe from harm...it's perfect (b= ut you'll have to spend some time reading and maybe that's why I won't get = sliced into pieces by pressing the wrong knob - manuals are my friend).=0A= =0A=0A=0A------------------------------------------------------=0Afreenet.d= e sucht den schlauesten Landkreis Deutschlands.=0AMitquizzen, fuer Ihren Kr= eis punkten und attraktive Preise gewinnen!=0Ahttp://www.herrderkreise.de= =0A |