MuTools

Drenholm · Post by **Drenholm** » Fri Aug 04, 2006 7:16 pm

Upon attempting to open a session, having one already loaded, I often get the message "Couldn't load the current session" and have to start a new, blank session before I can load the session I wish to. (Luna Free)

muzycian · Post by **muzycian** » Mon Aug 07, 2006 2:01 pm

Drenholm, if the musession files are not too big, can you please zip and email the 2 musession files that give this problem.

Alternatively, contact me via my mutools email account, and we'll investigate this via logging.

Thanks,

Jo

muzycian · Post by **muzycian** » Mon Aug 07, 2006 2:54 pm

guitarfrodo wrote:Re: midi copy issue. Try to create a fresh copy of a part with alt and the arrow to pull a fresh copy to a new spot, suitable for having its own player.

Everything at this point is working fine.

Now, close Luna, reopen and you should be staring at the new part with now, no midi data. The best thing to do with that blank part is erase it quick because if you try to work with it, (I tried to rename it, before going to the editor to try adding data) it causes a lockup. Which in my case required a restart button escape and rendered the session file from that point further unusable.

Warning to all users: this is a severe issue!

Until the next version (PreRelease 4), don't use Alt+Drag to copy-duplicate a sequence.

Instead use control+drag = copy part using same sequence, then choose "Duplicate Sequence" from the new part's context menu.

Issue resolved in the next version! Then you can use the shortcut alt+drag

muzycian · Post by **muzycian** » Mon Aug 07, 2006 4:31 pm

pljones wrote:Minor UI bug. If I select a mixer strip in the player panel and hit edit, it gets its own window (which is great!). If I add and remove an effect to the strip, though, the width of the strip changes and it no longer fills its window.

Resolved in the next version

Also, I got a crash when dragging the volume slider on the same strip after closing it and opening it again.
DrWatson: http://www.drealm.info/luna/2006-08-04-drwtsn32.log
(LUNA didn't know it had crashed when I re-started.)

I just tried LooxBenu - really nice skin - but the separate mixer strip windows didn't get reskinned until closed and re-opened.

Related issues.

In the next version, it won't crash anymore!

(apology that i push the other issue a bit forward)

Unrelated UI request: I know I can right-click the timebar to turn looping on and off - but can we have a button back on the transport bar for this?

Yes, OK, will be back in PR4

Drenholm · Post by **Drenholm** » Mon Aug 07, 2006 10:12 pm

"Yes, OK, will be back in PR4"

Yess!!

The error seems to have gone away - don't you just hate that? - and it wasn't with two specific files anyway, just in general. Let's just say that I'm mad and your program is fine and be done with it.

jpumphandle · Post by **jpumphandle** » Tue Aug 08, 2006 7:49 am

1. When a midi file is imported into LUNA, the time signature defaults to 120 BPM regardless of the time signature in the midi file. Since only a single midi file can be imported, it would be nice to be able to use the time signature from the imported file.

2. The recording level is a guessing game when recording audio. It would be nice to have a level meter whenever the Audio record button is on. This would allow easy adjustment of recording levels instead of having to record short bits and then readjust the recording input source levels and then re-iterate.

Drenholm · Post by **Drenholm** » Tue Aug 08, 2006 9:35 am

On top of what he just said about recording, I'd like to request the ability to turn off the automatic normalisation of recorded audio.

Also, will we get to choose proejct and final mixdown sample rates and bit depths?

muzycian · Post by **muzycian** » Tue Aug 08, 2006 9:52 am

jpumphandle wrote:1. When a midi file is imported into LUNA, the time signature defaults to 120 BPM regardless of the time signature in the midi file. Since only a single midi file can be imported, it would be nice to be able to use the time signature from the imported file.

Fixed in PR4

2. The recording level is a guessing game when recording audio. It would be nice to have a level meter whenever the Audio record button is on. This would allow easy adjustment of recording levels instead of having to record short bits and then readjust the recording input source levels and then re-iterate.

In PR4, you will be able to monitor the audio input thru any one of the mixer strips!

So you will not only be able to see the level, but also to hear the audio input, eventually processed thru any of the plugins on that mixer strip.

Note that audio is *recorded* dry, i.e. before it's processed thru the mixer strip.

This new feature turns LUNA into a powerfull live audio effect

Drenholm · Post by **Drenholm** » Tue Aug 08, 2006 10:33 am

That'll be great. I think PR4 is going to kick ass. What about the things I mentioned? Thanks.

muzycian · Post by **muzycian** » Tue Aug 08, 2006 1:01 pm

Drenholm wrote:On top of what he just said about recording, I'd like to request the ability to turn off the automatic normalisation of recorded audio.

OK, will be added to the recording options panel.

Also, will we get to choose proejct and final mixdown sample rates and bit depths?

The samplerate is always the samplerate of the audio card.
Of course, you can apply high-quality resampling in an external wave editor.

Choice in bit-depth is planned for a future release.

Drenholm · Post by **Drenholm** » Tue Aug 08, 2006 8:10 pm

Thanks! You rock.

deleted · Post by **deleted** » Sun Aug 13, 2006 3:14 pm

DELETED

muzycian · Post by **muzycian** » Mon Aug 14, 2006 8:05 pm

michi_mak wrote:pr3 just works absolutely unstable - it crashes with every audio ( which it did not with pr1 and i didn't change my asio settings )

What do you exactly mean with "it crashes with every audio"?

Every audio file?
Every audio card?

Please try removing the AudioSetup.txt file from your Luna/Settings folder. Or try a fresh new install of LUNA PR3.

Does that makes a difference?

The ASIO Audio Setup has become more detailed in PR3, and maybe there is a conflict with an earlier installation?

i still can't bypass fx ( at least i couldn't find it )

True, it's not yet there.

Will push it in priority as it is indeed essential.

pljones · Post by **pljones** » Tue Aug 15, 2006 4:59 pm

muzycian wrote:Will push it in priority as it is indeed essential.

Can you squeeze it in next to the edit button on the mixer strip, as well as on the popup editor panel, please?

muzycian · Post by **muzycian** » Tue Aug 15, 2006 7:02 pm

pljones wrote:
muzycian wrote:Will push it in priority as it is indeed essential.
Can you squeeze it in next to the edit button on the mixer strip, as well as on the popup editor panel, please?

I try to keep the GUI as simple/uncluttered as possible.

A bypass-specific button near each plug slot sounds too heavy, imho.

I would rather put a bypass button in the plug editor panel, and maybe we can add a "Bypass ON/OFF" in the relevant context menu, as a shortcut.

Would do you think?

MuTools

KVR Audio

LUNA PreRelease 3