Forum Replies Created
-
Posts
-
Tested some sound and image stuff, ran out of time, so, wip (OS X). Input: esc,f,space. Image
This one is ani heavy.
[hint: Simon Arm?trong]
The problem with these jams is that once you feel serious about it, it’s often an exhausting experience. 48 hours in a month sounds more relaxed but it’s a different feeling. I prefer getting into the tunnel when i feel the need to and also have a little bit of time.
Secondly if you’re new to a tool, or want to introduce people to a new one, you want great docs/online resources next to you as otherwise you’ll spend most of your time trying to figure out how to do something instead of doing it.
Apart from such things it can be fun.
A few things from the last time i played around with m2 (OS X, 1.0.1/1.0.2[ogg]):
Btw. where do you post feature requests (thread, issue tracker)?
Requests:
a) Support for loading a folder structure directly, without the #Import, like in Max. Would be more flexible.b) DrawImage/Load would nice if you also could provide a parameter for atlas/animations/packed textures (like, width, height, [amount]) to access the sprites within the atlas. Currently you need to split all the data into several images in m2 (isn’t this relevant performance related?, didn’t have time to check out the source [yet]).
c) FLAC support.
Question:
a) How do you check the Mouse-Events/Buttons States in all different ways? I got it working one way (event with test on int) but not the others, only checked out the doc, not source/sdl).b) Does DrawImage support Clamp as a Warp Mode?
Quirks:
a) Wasn’t able to ‘just’ replay oggs with the proper sample rate (also in audiotest.monkey”.b) In some cases you needed to kill the task in order to exit a debug release.
c) Mostly m2 runs fine but in rare cases there can be a hickup and it stutters for a short moment.
d) Some fullscreen modes don’t work as expected (wrong mode, stretched only over a part of the screen).
e) PixMap operations are quite slow.
Something to relax (worked for me, V1.0.1, OS X, 1440×900). Input: esc,f,space. Image
It would be nice having support for fmod/wwise. Oggs can sound strange (frequency issues)?
[hint: Two letter acronym for monkey2.]
“If you wanted to be helpful”
Dude, i think it’s valuable giving honest feedback.
Both fmod (yep studio) as well as wwise offer indie, non/limited-commercial licences which probably suite a range of applications already. Check them out. The realtime mixing and mastering alone can make such a difference. Secondly it would be nice supporting a free (and limited) alternative too, just in case your sound design is basic or your budget is tight/# of assets are high.
Dunno about the current state of bass, i’ve only used it a couple of times with Max. Do bass and its extension work together well? From a quick observation, it looks less feature rich than fmod or wwise but like it also could offer some more than what we have right now.
Does libopenmpt work? I remember that some tracker libs allegedly supported a number of formats but once you threw various modules at them, they tended to crash or refuse to play. In the best case you have both replay and also pattern access (selection).
Part of the problem is that there is such a huge difference between a modern updated sound engine and the ability to replay samples with a few basic adjustments. For the later you at least want some accuracy, low latency, quality, reliability and read/write access to the data in order to feed it (gen/mic) or analyse the audio spectrum, best working in 2d and 3d mode. I would love to see attention to detail on sound (as well as other aspects m2 covers, it seems like such a huge amount of work for one person on all the platforms, therefore …).
The fun of m2 is the way you can directly code, its readability and that the source is available. Its downsides are that some aspects of it feel only wip or not up to date. Every section i’ve covered so far had their hick ups and lacked polishing. These days it’s early adopter but it shouldn’t stay like this in the future, otherwise the audience might stay small.
*updated*
OpenAL, Midi, … that’s not what you want when you’re into music and after more control and precision. I would love to see something different. OpenAL had quite some issues and i remember the official dev on it being discontinued.
[@What’s next: I still disagree with the many platforms approach. I prefer if there would be focus on ‘finishing’ desktop first. The more platforms there are, the larger the possibility is that m2 will share monkey’s fate: available for many platforms but not working convincingly on any of them.]
Oh no, not OpenAL (again).
Today you could use a bloom/glow shader (on the scene, maybe together with additional objects’ texture glow data [f.e. in the alpha channel]). In Max you could use an additively blend ‘glow’ texture on a quad strip (so, vertex and texcoord [uv] info), looking relatively nice but fillrate bound on old hardware.
feedback:
‘ audio (quirks & suggestions)
a) Sometimes the audio is rather unclean.
b) FLAC/mod/ogg support.
c) Convert audio formats.
d) Softsynth
e) fft analysis and some effects (like equalizer, distortion, high/low-pass, flanger, reverb).
And whilst i’m at it …‘ ted2
a) Retina support.
b) Nice font/settings, btw. scrolling down source the source cuts the text at the top.
c) Vertical text scrolling works with the trackpad (two finger swipe), horizontal scrolling doesn’t.
d) Find&Replace: You can only ‘return’ through the results until you click on the text; clicking on the find/replace box doesn’t reactivate it.
e) Adding OS X typical shortcuts (like, cmd+x/c/v/z/…, instead of ctrl+…). Weird when switching apps.
f) Double clicking on a text/command, marking the whole text/command.
g) F1+command under the text cursor firing up help with a search on the choosen command.
h) Highlighting all the signal commands and types and …
i) Keep the flat and easy look&feel, no shadows/icons/kirmskrams.
j) Trying to mark text on the right border (outside of the screen – scrolling) resets you to the left without marking anything.
:
‘ questionsa) Can you also load data without #Import (like in Max, a folder structure outside of the package)?
b) I very much like that Keyboard.KeyDown is an autofire etc. but isn’t it confusing that EventType.KeyDown differs?
c) How to add fragment shaders (post processing)?
d) How to swap between fullscreen and windowed into different resolutions?
e) Where is my (virtual) heart gone?
f) 3d 3d 3d …
‘ overalla) It’s easy and fun whipping up ideas (as long as you stay within boundaries).
b) I still miss zebra’s code indentation. For some reason i enjoy throwing #rems and #ends into the code (and afterwards deleting them again).
c) A guide on how to modify/add functions in the source, like sdl or ted2, could save people some time.
d) Some stuff could be implemented (more efficiently), sometimes there are many options how to use a method, sometimes you miss an option, a balancing act.
e) My issues were about memory access violations (typos [blame the keyboard/editor, not me], early double times import drama, [strings defs baby]), not putting canvas in front of certain commands (used to Max here) and how to define some properties correctly (every entry in the doc could use an example).
f) Hopefully more people will join m2. The more i use it (time *sigh*), the more i like it.Ahh, i ran out of time (wanted to do this and that) but anyway it was fun (OS X). Input: esc,f,space. Image
@Mark nice update!
[hint: 4,5,6,?]
I had some time to play with m2. One of the tests in its aliased bumpy glory (OS X). Input: esc,f,space,mouse. Image
I miss more sound options. Compile times are fast again, hurra! (What you really want, is realtime feedback). The docs are meh-> grep on source -> … Sometimes m2 feels great, sometimes cumbersome. The structure of Mojo is weird. I had a couple of freezes (slowed down input), canvas colors and pixmaps do strange things, couldn’t do stuff like Max(0.0,Sin(ang*d2r)), … still it was fun!
[hint: $ff-$59]
