Re: [Rosegarden-user] JACK MIDI... Why?

2020-03-23 Thread Sami Jumppanen
a2jmidid has been totally invisible for me. One checkbox in Studio Controls
(or a line in JACK settings). Need it between my old USB 8x8 MIDI Interface
and Reaper. If there are problems with a2jmidid, I'm sorry, I just haven't
seen it.

(People also say Linux Reaper is experimental and but after 280 hours with
no crash, runs fine on 2007 Core 2 Duo 2 GHz, 2 GB RAM, I have to say I
can't trust anyone).
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] Any way to continue a song with different studio?

2019-05-09 Thread Sami Jumppanen
>
>Actually, upon further thought, you can create a Device for each
> synth and assign multiple Devices to the same port.


Indeed, good points.

With daisy chaining there's always the need of setting the channels
correctly in each physical device - which I did, and now I really got a
hard one: should I expand the limited per synth settings (allow more
channels on each device)? Will it create problems in the future?

I have two multi-output devices. Yamaha TG33 (the one that doesn't listen
"All notes off", but luckily rg sends note offs at stop, hooray!)  has four
physical outputs. Yamaha V50 has two outputs assignable, and I've decided
to have MIDI channels 5 - 8 in use. Channel 5 is assigned on the "L"
output, others to the "R". That way, in my analog mixer, I can have dry and
wet sounds mixed form a single synth. If I add more channels for that
synth, I get a question how should I assing the L/R split? If I mix the
settings freely, I get away of remembering that in rg by naming the tracks
wisely (L/R appendix or dry/wet). But for other uses, it may not be that
handy.

If, OTOH, I keep the current 5 = "L" / 6,7,8 = "R" channel split, all my
old songs would work fine as they are, even if I have more channels
activated.

This is no way related to the rg problems I started to write about, but as
this is a user list, I thought why not to write :) For a short moment I
thought what if the device setup could incorporate division into physical
outputs per device... but more options tend to have negative effect on
usability.

Sami
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] Any way to continue a song with different studio?

2019-05-09 Thread Sami Jumppanen
Hi,
thank you for the thorough reply! Really appreciate it.

The first setback I encounter is that I have a studio set up, the default
studio project has tracks with all the device assignments done. When I try
opening older simpler song, I don't see the devices I had configured. With
all things considered, I will not get stuck with this, and I already tried
creating the missing devices. Just didn't bother to remake the banks, got
the right sounds playing anyway.

Connecting to the first device - good info! That seemed to work. The song
then ended up having the names of the devices like before (the old physical
devices), but first of them pointed to the first new MIDI port. Ok.

I'm sure I can take the time to try all the methods again with better
documentation.


to 9. toukok. 2019 klo 15.34 Ted Felix (t...@tedfelix.com) kirjoitti:

> On 4/26/19 7:57 AM, Sami Jumppanen wrote:
> > I'm having problems with my changed hardware synth studio (physical MIDI
> > ports) and continuing the old songs. I have found and tried different
> > ways to migrate songs to new studio, but none of them seem to work well
> > or at all.
>
>I would just create the studio from scratch and assign each track to
> the proper device/channel.  This might be a rather large undertaking,
> though.
>
> > 2. Open the old song and then import a new studio from a newer RG file.
>
>I tested this with a very simple (one Device) setup.  It worked fine
> for me.  RG assigns all Tracks to the first Device it finds.  This is
> probably the best guess it can come up with.  So, then it should be a
> matter of assigning the Tracks to the proper Devices/Channels.
>
>You mentioned that with one of these approaches (2 or 3), you ended
> up only with "one port of the new MIDI device".  That certainly sounds
> like a bug that would be easy to track down and fix.  Was that this
> case?  Can you provide more details so I can try to reproduce this and
> fix it?
>
> > 3. Import song to the default empty studio project.
>
>I'm not sure how you did this.  I tried doing this with File > Merge
>  > Merge File...  Is that what you tried?  For me, it did nothing.  I
> ended up getting an exception thrown and caught in
> RosegardenApplication.  (I'm running a debug build, so that might be why
> I didn't crash.  Still, it was a std::bad_alloc which is probably fatal
> at some later point.)
>
>Was this the case that crashed for you?  Crashes are certainly cause
> for concern, so I'll have a closer look.  If you can give me more
> details of the crash you encountered, I'd appreciate it.  Would like to
> get it fixed before the 19.06 release if I can.
>
> > Device configuration should be detached from sequencer work, it makes
> > very little sense anyway. Firstly mixing the terms device and port. One
> > MIDI port can feed many devices (synthesizers) by daisy chaining (or
> > other splitters/processors), so it's not rational to think about a MIDI
> > port as a "device".
>
>This is a good point.  RG restricts the user to one synth per MIDI
> port.  That's unrealistic.  The concept of a synth needs representation
> in the Studio.  I'll open a feature request.
>
> > If no
> > settings are found, so what? Just display patch numbers.
>
>See Feature Request #455:
>
> https://sourceforge.net/p/rosegarden/feature-requests/455/
>
> Ted.
>
>
> ___
> Rosegarden-user mailing list
> Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
> https://lists.sourceforge.net/lists/listinfo/rosegarden-user
>


-- 
Sami Jumppanen
http://netti.nic.fi/some-e
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


[Rosegarden-user] Any way to continue a song with different studio?

2019-04-26 Thread Sami Jumppanen
Hi,

I'm having problems with my changed hardware synth studio (physical MIDI
ports) and continuing the old songs. I have found and tried different ways
to migrate songs to new studio, but none of them seem to work well or at
all. I did not find anything specific from bug tracker with the word
"studio".

The status: I have defined a new studio and naturally saved the latest
correct setup as the default studio. Works fine when starting new songs. My
old studio had two MIDI ports (IN + OUT) and now I have the old two plus 8
new. The old ports are not connected, it is better to connect everything to
the new USB MIDI 8x8 interface for it's internal routing (playing something
without computer).

The problem is how to continue with old songs made for the two-port studio
setup? There are at least these possibilities:

1. Settings: always use default studio when opening songs.
2. Open the old song and then import a new studio from a newer RG file.
3. Import song to the default empty studio project.
4. Import MIDI file to the default empty studio project.
5. Open the new studio (template) AND the old song and copy segments from
the old song to the new? No, seems the segments cannot be copied between
songs.

I think I managed to use the option 1 yesterday, but then the studio only
included two devices: they were named like the old devices, but one of them
was connected to the the first port of my new MIDI interface. Only one port
was correct, and all the other ports were missing from the new studio.

Option 4 works (when I first open the old song "as is" with the old studio
and export it to MIDI file), but it naturally loses segments. As a bonus,
all the unused tracks are cleared, so I lose my studio template.

The other options either crash or leave me with one port of the new MIDI
device. Something like this.

Device configuration should be detached from sequencer work, it makes very
little sense anyway. Firstly mixing the terms device and port. One MIDI
port can feed many devices (synthesizers) by daisy chaining (or other
splitters/processors), so it's not rational to think about a MIDI port as a
"device".

Just to be able to send MIDI out, I need to define a device, but defining a
device requires defining patches as well. I know I could begin with GM set
and live with it or rename patches as I go along. And I eventually created
some banks, for my drum machine and two synths, but they are tied to MIDI
ports I no longer use. I have them in my new studio but the new studio
cannot be used for old songs.

If we could have the MIDI port (from a list of ports visible to ALSA)
selection in the track settings. Also, *if* the selected device matches a
predefined bank of patch names, those settings could be used. If no
settings are found, so what? Just display patch numbers. I understand that
the MIDI device world is not consistent with number of patches and all the
bank selections and whatnot. 128 programs is, however, a standard by the
MIDI program change.

What I like in Rosegarden is how the sequencer really works: it sends note
OFFs correctly when I stop it, and it even sends note ONs when I press
start in the middle of the notes. Not all DAWs do this. The lack of
features or problems just weigh quite much, and I hate I cannot do anything
really, no programming nor spend time for "trying things out", not in this
part of my life. I do want to create a more accurate step by step report on
the song / studio import problems if those are not widely known. I'm quite
as messed up with these issues as my post here is :D

Thanks.

-- 
Sami Jumppanen
http://netti.nic.fi/some-e
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] Crashes :(

2019-04-10 Thread Sami Jumppanen
For dying computer owners: before upgrading anything, use a known good PSU.
I just lost a week worth of late nights trying to set up a new computer. I
deducted that it was the PSU on the nearly functional computer that had
caused CPU failure, by having something else than DC voltage. On the
average the voltages were a bit low, but contained AC spiking.

That CPU didn't work with decent PSU (normal voltage levels) anymore, on
any board I tried - the other boards didn't even boot into BIOS. I had
three PSUs to test and always it was the old one that made the old board
work so well that I could install Ubuntu Studio and upgrade it even once,
but then I got jams and interrupted HDD writes.

I postponed indefinitely testing the other boards with another CPU because
I had an older computer that had no problems - and still runs fine.

PSUs are dangerous! :)


ke 10. huhtik. 2019 klo 9.33 david (gn...@hawaii.rr.com) kirjoitti:

> On 4/8/19 10:37 PM, D. Michael McIntyre wrote:
> > I haven't tested the timing thing either.  My computer keeps freezing.
> > When I reboot it, I'm stuck at 1024x768, and the only way I have managed
> > to make progress on that issue is to reinstall Kubuntu.  I've been
> > around that bush three times now, and I have grown tired of the
> > aggravation.  This machine is rather old, and I suspect the hardware is
> > just flaking out.
>
> My main desktop/server, also rather old, finally died. The onboard video
> went first. Then the machine just quit coming up at all.
>
> The backup desktop/server still works. It's "newer" than the dead main
> one, but has some peculiarities. For example, the BIOS doesn't recognize
> the presence of a keyboard unless it's plugged into the PS/2 port. Once
> Linux comes up, it works just fine with my USB keyboard, so it's not a
> problem with the keyboard.
>
> Hoping to replace the guts with a Ryzen 7 motherboard. Could use the
> speed for other things I do.
>
> > Either that, or Kubuntu 18.04 is less stable than its
> > many predecessors, which I find difficult to imagine.  Still, the
> > trouble started when I upgraded from 16.04, so that may be the culprit.
> > So many things have changed it's more trouble than it's worth to me to
> > try to keep track of any of it.
>
> Well, in my experience, upgrading from Ubuntu 16 to Kubuntu 18 was a big
> hairy problem. For instance, after upgrade and restart, no working
> network. I reinstalled fresh.
>
> > I had gotten in the habit of just buying a retail desktop PC off the
> > shelf, but you can't buy those anymore.  Getting Linux onto a retail
> > Windows PC is a huge pain in the ass anyway.
>
> In my experience, only if you want to keep Windows around.
>
> > I guess I have to go
> > figure out what components to buy and roll my own like it's 1995.  I am
> > not looking forward to this at all.
> Well, putting Linux on my wife's retail laptop PC that came with Windows
> on it worked just fine. Dell, Lenovo, HP apparently work. Only
> ointment-infestation I can imagine might be support for fancy new
> graphics cards?
>
> At the moment, I like Asus motherboards. My wife's laptop and the mobo
> in my backup desktop machine just work with Linux.
>
> Since my present laptop experiences a few issues (doesn't think it has a
> battery, takes 3-5 minutes before the built-in display shows the POST
> screen) due to having been dropped a few times, I'm thinking of jumping
> to a Dell 15"/4K HDR display and Intel processor.
>
> Looking for hardware that won't leave me crawling when I move to a
> 42mpixel camera and get to start making big panoramas.
>
> --
> David W. Jones
> gn...@hawaii.rr.com
> authenticity, honesty, community
> http://dancingtreefrog.com
>
>
> ___
> Rosegarden-user mailing list
> Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
> https://lists.sourceforge.net/lists/listinfo/rosegarden-user
>


-- 
Sami Jumppanen
http://netti.nic.fi/some-e
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] Crashes :(

2019-04-09 Thread Sami Jumppanen
Out of curiosity, what is the problem?


> >I had gotten in the habit of just buying a retail desktop PC off the
> >shelf, but you can't buy those anymore.  Getting Linux onto a retail
> >Windows PC is a huge pain in the ass anyway.  I guess I have to go
> >figure out what components to buy and roll my own like it's 1995.  I am
> >not looking forward to this at all.
>

- Buy a computer
- Put in another hard drive, I bought a cheap SSD
- (Unplug the supplied Windows drive if you're not going to use it for now)
- Install Linux

I did find the new Linux installer (with Ubuntu Studio) a bit strange. It
seemed all logical with empty HDD, but when having another HDD in the
computer with Ubuntu Studio, the installer says there were no other OS
found and logical volume management options and all the talk of deletion
look strange or scary :D

I am using now a 2006 era dual core and everything looks ok. Maybe the
newest computers bring new problems?

Sami
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] New Rosegarden Logo

2019-03-14 Thread Sami Jumppanen
Adding my observations from the world and logos: display DPI has gone up.
The old 3D controls (mainly speaking wrt Windows OS) have lost their edge.
UI and logo designs are reaching for clarity - like always, but the
competition and display technology are certainly some of the modern driving
factors. The old yellow rose is nearly blending on the light grey menu
background on my display. Admitting my displays are maybe a yard away (!)
from optimal and bit on the smaller side, but the mixing console takes its
toll :)  So I welcome darker colours with sharper edges. Not that I
couldn't find RG from the menu now.

And I will not go comparing the old vs. new. The old is truly beautiful, I
just don't feel it should be kept for historical reasons. Or, put it
another way: if the project lead wants to change it, I don't have anything
against it. I do value getting different opinions here though.

Sami
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] New Rosegarden Logo

2019-03-13 Thread Sami Jumppanen
Hi,

looks interesting. My first reaction was "India, elephant!". Then I see the
spike and all :)  Elephant is positive, friendly, good memory, strong.
India refers to deeper understanding and mental stability. But this is just
my first look and my own analysis. Need to give it more looks during a few
days to see more.


to 14. maalisk. 2019 klo 7.24 Ted Felix  kirjoitti:

>I've got a graphic designer working on a new logo for us.  Here's one
> of her ideas.  Let me know what you all think.
>
>https://www.rosegardenmusic.com/wiki/rosegarden_logo
>
> Ted.
>
>
> ___
> Rosegarden-user mailing list
> Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
> https://lists.sourceforge.net/lists/listinfo/rosegarden-user
>
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


Re: [Rosegarden-user] Introduction: 80's and 90's sound from hardware studio with Ubuntu Studio

2019-02-20 Thread Sami Jumppanen
>
>
> If you don't need/use those settings, they can be removed
> by editing the Controllers for the Device:
>

This sounds exactly what I need. Excellent!


>There are definitely bugs WRT rewinding CCs.  We just don't do that
> at all.  The only way to reliably get what was in the sequence is to
> start from time 0.  Bug #1560 covers this issue.  Not sure I'll ever
> have the necessary time to address this properly, but you might want to
> try back-leveling to 16.02 and see if you like that better.  It does
> make an attempt at sending the proper CCs at playback.  And with the
> Controller removed from the Device, you might see exactly what you want.
>

Okay. My problem with volume CC's is a bit strange, as I have not touched
track parameters, mixers or recorded any CC (ok, should still double-check
the events AND log the MIDI output).


>Let me know how it goes as this will be a second vote for me to at
> least putting in an option to provide 16.02's behavior in the current
> version.  That shouldn't be too hard to do.
>

I feel like the bad guy, but I just cannot afford (time wise) trying
different versions right now. I stay up late one night to get something
done, then I may not do anything the next night because of staying up too
late. So no vote for now.

A few words about previous talk: panic button. Should need no specific
reason to have that implemented, as it's standard feature of every
sequencer I've seen. It's not a nice thing to hit when doing live playing,
but surely in "just browsing" mode it will be ok. I did not try it for one
stuck note mainly because I don't believe in it. And that is not anybody's
fault here. I've been trying to use Ardour for MIDI work :D I had stuck
notes on STOP or just play! And the panic button did not help. Ardour stops
notes immediately on track mute for example, so somewhere the logic works.
Sometimes I did see note off being sent before note on, which obviously
caused stuck notes (if pressing stop amidst the note(s) playing), but let's
not get into Ardour, it's now being rewritten largely so maybe bug hunt is
waste of time over there. Surely we can learn from other software.

Stuck notes can be useful, yes :)

A thought: notes can also be cut by means of active sensing. That can be
done in the intended way (unplugging a cable or disconnecting software MIDI
flow for 300 ms). May not be ok for every situation, not all devices /
plugins may not support active sensing and I don't know if rg supports
active sensing, but that's one way. If there is active sensing from rg,
include a 300+ ms break when using the panic button.

Which notes should be playing at any given moment? I've thought about the
note bookkeeping and how it should be done: integer array(0..127) for each
channel of each MIDI port counting how many times a certain note on has
been sent. When need to stop MIDI notes (stop, track mute, change track
focus or other reason), send as many note offs as required to cancel the
note on  "on count" > 0. Synthesizers, at least the hardware ones I've
used, can play multiple notes for the same key. It does not always help
sending note off just once. These array values would be incremented and
decremented regardless of the "source" (external input or rg segment data),
so it should not be a burden. Admitting I have no idea how things are
implemented already.

(I really try to keep this short...)

-- 
Sami Jumppanen
http://netti.nic.fi/some-e
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user


[Rosegarden-user] Introduction: 80's and 90's sound from hardware studio with Ubuntu Studio

2019-02-18 Thread Sami Jumppanen
 has
happened on two different synths so far. The note velocities are recorded
correctly. The synth sound volumes do not indicate a change in the panel
(maybe there are separate "channel main volume" and CC volume). Switching
the performance program to something else and back resets the channel
volumes to default.

4. Boss Dr-550 does "M er" at times (MIDI error, received something bad),
and during that display it doesn't do anything. Have to press stop on the
unit to clear the error. A fix would be filtering out everything except
NOTE ON, as the unit doesn't listen to anything else (apart from MIDI
start/stop/continue/clock). -> an application running MIDI plugins,
connected after rg?

5. Yamaha V50 sometimes says "MIDI buffer full!", and I haven't seen a
logical reason for this. Surely there is MIDI data coming in, but where is
it from and what, that is unclear. Could be multi channel CC too quickly
and a too small MIDI buffer in the synth. I haven't seen that causing
problems with playing.

6. Matrix editor zooming from the bottom right corner using a regular
scroll wheel is sometimes cumbersome. H or V zoom levels are not reflected
to the combined zoom roller -> it has its own memory of zoom level. I'm not
sure if it's supposed to continue form where the H/V zoom was left or
always force 1:1, but it is a bit cumbersome.

7. Positive: comprehensive settings for MIDI sync! I can turn sending the
sync off. Say, I want to record some live audio, with sounds from Korg
Volca Bass. I can hit record and nothing unwanted happens, I just play the
keyboard and everything is fine. When I try the same in Qtractor, the Korg
starts playing its pattern, because a MIDI start and clock is sent. Didn't
find a way to turn it off in there.

8. Positive: rg is stable and runs well in my Core 2 Duo @ 2 GHz, 2 GB RAM.
I had a Quad core 6 GB RAM set up, but it started acting up before I got
anything to do, so this is a backup for now. I lost a week for the fresher
computer and trying to make it work. I had three motherboards and three
PSU's. Later on I deducted the problem is that the CPU has gone bad due to
the original failing PSU. Interestingly, it only runs on that failing PSU
(giving undervoltage by my measurements).

9. The scores, notation! Most likely I will need to print out notes to
someone later. Experimenting scores after I've done something worth of
"making notes of" :)


What I might want in rg:

* Per track / per channel MIDI OUT filter could be useful. In short: MIDI
out plugins.

* Settings to disable sending pan/cc. etc from the track parameters. I did
take a look at a few CC bugs and it really can get complicated. It is also
a question, if everything should be set correctly at the rg side, matching
to what was intended with the synthesizer settings. It may be a question of
getting used to certain workflow. Might be as simple as doing the settings
and saving a template (which I've done, but not to the degree of pan
controls, because my synths generally don't have pannable sounds, but here
we are...). Many different synths give many things to learn :)

Best regards and huge thanks!

-- 
Sami Jumppanen
http://netti.nic.fi/some-e
___
Rosegarden-user mailing list
Rosegarden-user@lists.sourceforge.net - use the link below to unsubscribe
https://lists.sourceforge.net/lists/listinfo/rosegarden-user