LUNA Free Beta 6

[> DiGiT <]

to DIGIT: the win98se note was just a let you know message since the readme file says Luna should work with it. I've a family so therefore 4 machines. My music gets done on an offline machine amd2400 winxp 1.5gb. Daughter gets the laptop. Son the gamer the new fast machine 2gbram and that leaves his parents online with an old relic with a creative audigy platinum 1, there are no xp drivers for this but it works great. As such I try a lot of plugs and such on this first after downloading. Interestingly most run great. Luna nearly goes on win98se and the system requirements otherwise are low so thought it was worth the heads up. I could see a newbie the music software with such a set up picking up a copy of CM and giving the disc a spin, might as well work.

haha ok cool i see where youre commin from. good idea to test your plugins like that...

i thought you might have had a korg oasys or something that requires 98... have you heard of 98lite? im sure you have, its been out a while. it works nicely i must say.

[fycfung]

Okay, so I've managed to get some events edited in. I've even managed to get as far as the List Editor.

fycfung: double-click your part to open the sequence editor, then right-click the grid area. Under the Edit sub-menu, pick "Open List Editor". Then you can use the Insert button to insert a Program Change event.

However, once you've got the event there, it appears to be read-only. I don't see a way to change the values.

Being able to select multiple events (ranges or multiple separate) and then hit delete would be nice...

Thank you very much! I haven't had the chance to try it yet. So you're saying that the procedure to change the instrument of a part is to hack the event list by hand.

Is it too inflexible to, say, associate a MIDI instrument to each part too? (So we can set it once per part, and the channel involved will be switched to that instrument at the beginning of that part?) Just curious, maybe I'm not understanding the paradigm very well.

Thanks!

[pljones]

The channel number in MIDI is a way of letting a device on the MIDI bus identify messages that it should respond to. In a virtual-only studio, it only has meaning to multi-timbral VST instruments (and LUNA Free doesn't support them).

The MIDI Program Change event (plus Bank Control Change events) are what a MIDI device (or VSTi) uses to select a particular program (or patch).

The problem is -- when do you send the MIDI events? That has to be down to the arrangement, rather than to where they are being sent. The instrument could switch patches multiple times during a sequence, if so desired.

Of course, different Players can respond to program (and bank) events in different ways (not everything is a General MIDI sound module). (Muzys had something called X-Programs but I must admit to never having used them. They let you describe a particular module's mapping from Bank/Program numbers to names for subsequent use.)

[muzycian]

Following on from my B5 crash on close, I tried again with B6 and got the same result.

I loaded up sfz and Kj's master limiter, removed the unnecessary mixer strips and saved the session.
Link to session file.

I then exited Luna, saying "yes" to save. I got an application failure.
Link to DrWatson log. (clear your cache )

Files are now the B6 versions.

Did what you wrote, but can't repeat the crash

(also can't download the linked files, got "cannot find server" on that, tried several times)

[muzycian]

It doesn't remember the Player Panel player, either, which is really irritating. I want to be able to load up a session and start playing with the last selected player.

Will be improved soon!

[muzycian]

Argh! I was just about to try creating a MIDI sequence to try out editing bank (CC0/CC32) and program change messages to help fycfung and it crashed...

I had loaded up an existing Session containing sfz and Kjaerhus Classic Master Limiter, then drew in a new Part, eight bars long. I zoomed in (hmm, zooming was strange - it kept the right hand edge pinned rather than the last-touched-thing; horizontal autozoom didn't work, either) and scrolled until I had the part nicely in the window.

Then double-clicked and got a crash. DrWtsn32.log for this one.

(Yes, it's repeatable.)

The Dr Watson log file tells me that the crash has occured in Greem Machine!

Was that Green Machine also loaded? Can you retry this crash, but without Green Machine?

[muzycian]

Can someone else confirm my bug above?
*) Start Luna, start a new session.
*) Pencil in a new part, select Sequence, select "Create new MIDI player".
*) Double-click the part.
Every time I do this, I get a crash. (In fact, I've tried many ways to create and then edit a sequence part by double-clicking and they all crash. Right-click, Edit also crashes.)

Does not crash here...

[muzycian]

Can not save a project if I import a midi file in the project.

can some one confirm this

1.start a new session
2.import any midi file.
3 create midi instruments or vst synth. assign them to track
4.save session.
5.close LUNA.
6.reopen session. There is no data.

But session opens fine and data is there if is created as sequence part and drawn in piano roll.

I also tried to keep midi file in the same folder where session is, but i did not work.

It does work, but there indeed is a problem: the composition containing the imported midi file is not properly selected. You could right-click (osx: control-click) the composer, and choose "select next composition".

In the next version, the last used composition will be properly selected!

[muzycian]

wow, this sequencer is beyond light. It's the only one i can use with other apps open on my 1.25 ghz G4 mac I'm very impressed! It's also highly customizable as far as the GUI goes and I haven't seen any bugs at all. When will the full app be on sale?

Soon!

Want to make sure everything is ok!

[> DiGiT <]

jo could you possibly include a list of recent files at the bottom of the file menu for quick opening?

[muzycian]

I have a few more questions. Will luna have a drum piano roll similar to the one in cubase? i know it's not necessary but it makes drum programming very easy.

That might come in a next version.

I agree that a specialized drum editor is a very nice feature!

Will luna support trilogy vst some day?

Doesn't it now?

Is it possible to preorder Luna?

Well, the shop wil open one of these days.

You'll receive email then.

Cheers,

Jo

[muzycian]

fycfung: double-click your part to open the sequence editor, then right-click the grid area. Under the Edit sub-menu, pick "Open List Editor". Then you can use the Insert button to insert a Program Change event.

However, once you've got the event there, it appears to be read-only. I don't see a way to change the values.

Fixed in beta 7.

(as well as for aftertouch and pitchbend)

Being able to select multiple events (ranges or multiple separate) and then hit delete would be nice...

True. Will be added in beta 7.

[muzycian]

1) Yes to the licence
2) OK to the Beta message
3) Cancel to add VST plugins
4) Echo WDM Choose ASIO
5) MIDI Yoke 1 for the only MIDI In; MIDI Yoke 8 for the only MIDI Out; OK
6) Delete all the mixer strips
7) Delete the default part
Create a new MIDI Player called "Ch1" for channel 1 on MIDI Out (using the Player Panel)
9) Resize the arrange window down to three tracks high
The pointer now becomes a pencil within the arrange window without picking a tool
10) Draw in a four bar part and pick Sequence part (Ch1 is auto assigned)
11) Double-click the part with the pointer

Crash.

I think it's step 9 that's key...

Executed the above steps, no crash.

Can you sent me a Dr Watson dump or so of that crash, so i can have a more detailed view on where it crashes.

[muzycian]

I'm going offline now;

But i will spit all these issues out

Can't live with it

Hi Jo,
Take it easy. I think I speak for everyone when I say that you've got a lot of support here. You should be thrilled that there's so many people taking time and effort to help you nurture this project into something that we all will want to use and will enjoy using.

Absolutely!

I do appreciate all your support a lot!

Without you, i'm nothing!

Software MUST be intuitive. The days of "you've got to persevere with it and get to know its quirks" are long gone. If I can't figure it out within 5 minutes, I uninstall it. End of.

Software MUST be lightweight. A lot of people (well, me at least) don't upgrade their hardware every year - bloat must be avoided at all costs. Luna runs like greased lightning on my old hunk of junk.

I agree. That's indeed goal number 1!

So I found out that you were developing something new and jumped aboard at Muton Beta 2. I know you are an ace developer; that's clear from CMuzys and Myzys, so we know that with everybody's help and support this project may well turn out to be one of the slickest and easiest to use sequencer out there.

Again, thanks a lot for all your feedback!

I'll do my best to produce a fine, fun and productive musical tool!

[muzycian]

Bug Report:
1. open the "add new synth" tree, don't select anything, click on luna's close button. GUI stuck.

Fixed in beta 7.

2. Removed VST's appears even after rescan. When we moved VST plugs within the VST folder a rescan created duplicate entries.

Indeed, the function is called "Add VST Plugins".

If you're making such changes to your vst plugin setup, it's best to:

-> Quit Luna
-> Delete the VstPlugins.xml file in your Luna/Settings folder
-> Restart Luna, and do a fresh "Add VST Plugins"

3.In the save preset/bank dialog. clicking anywhere on the screen selects the highlighted option (einther "save bank" or "save preset"). In other words, once the save button is clicked, there is no way to dismiss the popup menu.

True. Fixed in beta 7.

4. When routing a sequence part into an effect by selecting it as a player, and deleting the effect via the "delete from session" option in the player panel, Luna crashes.

True.

Will be fixed in beta 7!

5.Play cursor can move out of the visable work area and there is no way to follow it.

You can press S to turn on/off auto-scrolling.

Auto-scrolling is automatically turned off whenever you scroll/zoom.