Reproducible by switching skins - I meant to mention this. Looks like the skin change isn't clearing up completely between the old skin and the new skin if the new skin doesn't redefine all the controls the old skin had. Or something. (LooxTeak -> LooxVoidex does it every time.)fycfung wrote:Also, sometimes when I am in the sequencer window, the middle panel on top (with the transport controls) somehow exposes a little rectangular chunk of some other panel that looks like it's underneath it, to the right of the BPM counter. I'm sorry I don't have a screenshot at the moment, and I am also not quite sure how to reproduce it, but it's shown up a couple of times.
LUNA PreRelease 1
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
-
- KVRAF
- Topic Starter
- 1645 posts since 24 May, 2002
Yes i also noticed it. It's a bug in the skin definition itself!
The TransportPanel.xml (Panels folder) of LooxVoidex should mention
<Width>360</Width> and not <Width>375</Width>
Thanks!
The TransportPanel.xml (Panels folder) of LooxVoidex should mention
<Width>360</Width> and not <Width>375</Width>
Thanks!
-
- KVRAF
- Topic Starter
- 1645 posts since 24 May, 2002
I noticed 1 synth that didn't make sound until it's editor was opened. I think it was Adventus.fycfung wrote:I'm having some problems with the sound not starting up right away when I boot up Luna. At least once, when I booted up into an exiting project, I could get nothing but silence, and then the synths were silent until I opened up the synth window and kind of "shocked" it back into action by twiddling with it a little, e.g., hitting one of the drums in the CM-505 window. I was using Wusikstation V1 and CM-505 at the time. I know this doesn't quite rise to the level of a reproducible bug report, sorry. Maybe someone else has experienced something similar.
Yes, it's not yet perfect there. Thanks for reporting!Third, if I move the end loop counter while a note is being played, the note tends to hang.
-
- KVRAF
- Topic Starter
- 1645 posts since 24 May, 2002
Strange, mda DX10 plays fine here... (Osx 10.3.2)
Anyone else having a prob with mda DX10 in LUNA OSX?
Anyone else having a prob with mda DX10 in LUNA OSX?
-
- KVRist
- 251 posts since 3 May, 2003
Yes, I noticed the same problem in Tiger (OSX 10.4.6, 2GHx PowerPC G5 iMac with 1Gb RAM). DX10 loads OK but there is no sound (works fine in other hosts in the same system). All my other plugins are working well in Luna.muzycian wrote:Strange, mda DX10 plays fine here... (Osx 10.3.2)
Anyone else having a prob with mda DX10 in LUNA OSX?
It's a while since I have posted (mainly because I have been spending much of my spare time skinning Luna). New skin(s) coming soon but I am waiting for the GUI changes in the next release of Luna before I submit anything.
A few points on the GUI and skinning Luna:
1. I noticed that in all the versions of Luna to date, the default Audio Mixing Desk height is too short in the OSX version and should be changed from 204 to 208 in Luna.txt
2. While it is great to have the ability to skin more of Luna, with the last release I'm not sure if all the changes to the GUI are an improvement. If possible it would be nice to have the options of a separate background graphic for the Audio Mixing Desk and an editable graphic for the 2 gray panels that originally sat at either side of the track header. I also preferred the parts being raised rather than sunken and would like the option to edit the look as well as the colour of the parts.
3. Other GUI related items on my wish list include the ability to resize the sliders and a more editable panning graphic but I'm sure these and other enhancements will come later.
I'm not in anyway trying to be negative here. Like others on this forum, I just want Luna to be the best and it is already shaping up rather well!
-
- KVRAF
- Topic Starter
- 1645 posts since 24 May, 2002
I'm installing 10.4 soon, will then check again.Calum wrote:Yes, I noticed the same problem in Tiger (OSX 10.4.6, 2GHx PowerPC G5 iMac with 1Gb RAM). DX10 loads OK but there is no sound (works fine in other hosts in the same system). All my other plugins are working well in Luna.muzycian wrote:Strange, mda DX10 plays fine here... (Osx 10.3.2)
Anyone else having a prob with mda DX10 in LUNA OSX?
FYI: Only 1 gui/skin change: the mixer strips can also be viewed as small mixer strips, cfrIt's a while since I have posted (mainly because I have been spending much of my spare time skinning Luna). New skin(s) coming soon but I am waiting for the GUI changes in the next release of Luna before I submit anything.
http://www.mutools.com/temp/luna-pr2.png
Thanks. Corrected the default settings.A few points on the GUI and skinning Luna:
1. I noticed that in all the versions of Luna to date, the default Audio Mixing Desk height is too short in the OSX version and should be changed from 204 to 208 in Luna.txt
The raised parts are parts using a sequence that is also used elsewhere.I also preferred the parts being raised rather than sunken and would like the option to edit the look as well as the colour of the parts.
The sunken parts are parts using a sequence that is only used in that part.
Thus just after doing a "Duplicate Sequence" a part will always be sunken!
Resize sliders -> in the mixer strip you mean?3. Other GUI related items on my wish list include the ability to resize the sliders and a more editable panning graphic but I'm sure these and other enhancements will come later.
Thanks!I'm not in anyway trying to be negative here. Like others on this forum, I just want Luna to be the best and it is already shaping up rather well!
-
- KVRist
- 251 posts since 3 May, 2003
Resize sliders -> in the mixer strip you mean?muzycian wrote:Calum wrote:muzycian wrote:Strange, mda DX10 plays fine here... (Osx 10.3.2)
3. Other GUI related items on my wish list include the ability to resize the sliders and a more editable panning graphic but I'm sure these and other enhancements will come later.

Finally figured out how to post an image (although I'm still struggling with the quotes!).
Yes, I would like to be able to change the physical size of both the horizontal and vertical slider handles (5) and be able to choose a more complex graphic for the panning control (6).
Did you have any thoughts on my request for additional background elements? For full flexibility it would be nice to have a separate graphic for (1), (2), (3) and (4) but for my purposes I would be happy if (2) could be added to the GUI as an option. i just don't think the GUI looks complete without something either side of the track header.
I now understand the purpose behind the raised and lowered bevels in the parts (7). Do you think it would be possible to make the bevels user (or at least skin designer) editable at some point in the future. The reason I am asking this is that I am considering making a MAC and PC version of each skin with lighting angles and contrast adjusted to match the appropriate interface. It would be nice to have the flexibility to alter (or remove) the bevel in the part graphic (7) to match any changes in llighting angle. And, yes I know this idea may be unworkable and completely OTT!!
-
- KVRist
- 49 posts since 25 Apr, 2006 from North Carolina, USA
This is a known bug with CM-505, acknowledged in a recent (past 3 or so) issue of CM. Glad they owned up to it, too - I was losing my effing mind trying to suss it on my end. In my experience, though, it's inconsistent; sometimes I have to hit a drum pad (on-screen), sometimes merely opening the edit window causes the sound to commence. Tres weird, seen from a programmer's view (it's what I do in the daytime, though not for audio).fycfung wrote:I'm having some problems with the sound not starting up right away when I boot up Luna. At least once, when I booted up into an exiting project, I could get nothing but silence, and then the synths were silent until I opened up the synth window and kind of "shocked" it back into action by twiddling with it a little, e.g., hitting one of the drums in the CM-505 window.
-
- KVRAF
- Topic Starter
- 1645 posts since 24 May, 2002
Yo Calum,
First of all: sorry for my late reply. But better later than never, they say
The Panning control is defined by the AudioMixerStrip (the surrounding of the pan control) and the StereoPanner Format (the inner content of the pan control).
(3) is defined by the TrackHeadersBackground format.
There indeed is no separate definition for (2), and so the window background will fill it up. It's a neat solution, imho. Drawing dummy rectangles there of whatever format will look daft, again imho.
What do other skin developers think about this?
But i'll keep my mind open for how to make the loox of the parts more skinnable.
Cheers,
Jo
First of all: sorry for my late reply. But better later than never, they say
You can change the height of the vertical slider handle and the width of the horizontal slider handle by simply adjusting the format picture of it, as the handle preserves the format picture's height/width respectively.Calum wrote: Yes, I would like to be able to change the physical size of both the horizontal and vertical slider handles (5) and be able to choose a more complex graphic
for the panning control (6).
The Panning control is defined by the AudioMixerStrip (the surrounding of the pan control) and the StereoPanner Format (the inner content of the pan control).
(1) and (4) are defined by the WindowBackground format. For now, only a single background format for all windows.Did you have any thoughts on my request for additional background elements? For full flexibility it would be nice to have a separate graphic for (1), (2),
(3) and (4) but for my purposes I would be happy if (2) could be added to the GUI as an option. i just don't think the GUI looks complete without something either side of the track header.
(3) is defined by the TrackHeadersBackground format.
There indeed is no separate definition for (2), and so the window background will fill it up. It's a neat solution, imho. Drawing dummy rectangles there of whatever format will look daft, again imho.
What do other skin developers think about this?
Because parts can be colored by the user, it's not (yet) workable to use a Format for it...I now understand the purpose behind the raised and lowered bevels in the parts (7). Do you think it would be possible to make the bevels user (or at least
skin designer) editable at some point in the future. The reason I am asking this is that I am considering making a MAC and PC version of each skin with lighting angles and contrast adjusted to match the appropriate interface. It would be nice to have the flexibility to alter (or remove) the bevel in the
part graphic (7) to match any changes in llighting angle. And, yes I know this idea may be unworkable and completely OTT!!
But i'll keep my mind open for how to make the loox of the parts more skinnable.
Cheers,
Jo
- KVRAF
- 7412 posts since 8 Feb, 2003 from London, UK
Could the Part be RGB-colourable but retain alpha-channel from the skin? (Is there much benefit to that..?)
-
- KVRist
- 251 posts since 3 May, 2003
Thanks Jo, I am happy to work with the GUI structure as it stands. When I send you my skin I will also send an image showing how it (and other skins) might benefit from the extra GUI elements (IMHO). It will be much easier to show you an example than to describe. Hopefully there will be scope for GUI adaptations in the future if you (and other skin developers) think it is worthwhile. I do realise it is not at the top of your list of priorities at the moment!muzycian wrote:Yo Calum,
First of all: sorry for my late reply. But better later than never, they say
There indeed is no separate definition for (2), and so the window background will fill it up. It's a neat solution, imho. Drawing dummy rectangles there of whatever format will look daft, again imho.
What do other skin developers think about this?
But i'll keep my mind open for how to make the loox of the parts more skinnable.
-
- KVRAF
- Topic Starter
- 1645 posts since 24 May, 2002
Received news from Linplug: the issue is on SaxLabs side, and they'll publish a fix.hvaring wrote:Any news on this?muzycian wrote:Indeed it crasheshvaring wrote:The Luna Free VST scanner chokes on Linplug's SaxLab. Maybe you can sort this out with Peter@Linplug?
Emailed Linplug about this; Waiting for the answer...
But they're working on other things as well and cannot release an update soon.
-
- KVRist
- 93 posts since 8 Dec, 2005
By the way, is it normal for Luna to take up 30-40% of my CPU on a 3.06Ghz Pentium 4 with 1G of RAM, WinXP SP2, not playing anything, just sitting in the background? That's what it's doing right now. Are the VSTi's that are sitting in the menu (but not set as player to any track) draining any CPU in the background somehow? (Doesn't seem likely...) Thanks!
