User Details

Username: MartinH76
Website: None provided
Facebook: None provided
Twitter: None provided
Soundcloud: None provided
Account Status: enabled
Member since: Dec 20 2009
About MartinH76:
(report this profile)

Devices by MartinH76

No devices have been posted by this user.


Comments by MartinH76

Comments

But that makes no sense in the context of the device. You set the probability of an event happening relative to other events. These events happen at musical intervals. The point of this device is for a state machine to determine how likely one of those events happens compared to the other possible outcomes and the likelihood of each event happening is set by a percentage chance the user defines, e.g. there’s a 50% chance that event A happens on every beat, a 25% chance that event B happens on every beat, and a 25% chance event C happens every beat. That isn’t something that could be defined using musical intervals, because that doesn’t make logical sense. The events themselves _are_happening at defined musical intervals which are determined by the user.

I’m guessing you’ve not actually used the device, because it should be easy to see that what you’re saying doesn’t make sense in context of what it does?

This device _does_ use musical intervals to determine when events occur. The probability only helps determine how likely an event is to occur relative to other events. You've made a criticism which isn't valid at all.

Thanks Konstantin - it is a strange one. Could I ask a small favour? It might be something you've done with the device anyway, and I'm not going to pretend that I'm any kind of Max guru so I don't know if this will work, but could you refreeze the device and share it on your Gumroad page again? I had a similar issue with a M4L device several years ago and the problem was resolved when the developer froze the device again and re-shared it.

Unfortunately in order to use Miraweb to control the other device (Browser Mapper) with iOS, I don't think I've got any option other than using the standalone Max since Miraweb needs Max 8.2 to run, and the built-in version seems to be 8.1.11. I've spent a long time looking for a solution but I'm stumped. The most annoying thing is, if the actual Mira app displayed in portrait mode none of this would be a problem, but it only seems to open in landscape. Using Miraweb seems to be the only option to get it to run in portait.

Thanks for your time!
Martin

I love this device, it's awesome, but I have just discovered one small issue tonight. If I point Live's Preferences to the standalone Max app instead of the built-in Max for Live (which seems to be the only way I can get another device I use working properly), then the Dry/Wet knob stops appearing in Device Matrix when I select a device where it would usually appear. If I switch back to the built-in Max then the Dry/Wet knob appears again as expected.

The standalone Max is the latest release, 8.2.1.

It would be great if this could be fixed so I can use both devices together - as it stands I currently have to choose to lose some functionality in one device or the other.

Thanks in advance!

Thank you for the code - I've just downloaded this for free after watching the video. Looks like an interesting tool and exactly the kind of thing I like messing around with to generate new ideas! 🙂

Looks like that's fixed it! Thank you - I'll be testing it properly soon :-)

This doesn't work for me - the interface is missing a lot of elements compared to the picture here (mainly buttons and dials), and dropping a folder onto the device doesn't do anything. I'm running the latest version of Max and Ableton. Last time I noticed similar problems with a device it turned out the uploader hadn't frozen the device before uploading.

I'd love to try this device out, it sounds really useful! Could you maybe check the freezing thing and re-upload it please?

Looks like it's working now! I'll give it a try later tonight. Thank you :-)

Looks like it's working now! I'll give it a try later tonight. Thank you :-)

I think you may need to freeze this device and re-upload it - the device doesn't have any of the interface elements as seen on the Youtube demo video, except the Track/Spcm/Vel buttons on the right-hand side. Looks like it should be a very useful device though - thanks in advance!

Perfect! I should have tried that before posting, really. It behaves and looks exactly how I wanted when I switch back to Max 6.

I have no real reason to run Max 7, to be honest. Think I'll just stick with 6 for the foreseeable.

Cheers for the excellent device! :-)

I just discovered this yesterday and bought it immediately! It's potentially great, and something I've been after for a long time, but I've found one problem/bug with it, and one request:

The problem/bug is that there's no display visible unless I choose the "filled" version of the analyzer - I'd really prefer to use the lines, like in the screenshot you've used, but the display is completely blank if I try to use the unfilled version.

My request is just to make the display a bit more "solid", for want of a better word. The colours in the filled display option are so pale I can barely see them, whereas the lines in the screenshot above are nice and clear.

I'm on Live 9.2 and Max 7. Thanks!

I wish I could delete my last post - I might be wrong about this. I think I've got another M4L device hiding in my set somewhere which might be the culprit. I'll update this if I find out it's not this that's filling up my undo history after all.

I really like this device, but it fills up the undo history really badly even when it's sitting dormant. I've had a look at the patch but the only fix I know for this is to change live.objects to live.remote~s, and I can't see any live.objects in the patch, so I have no idea what I'm doing! :-)

It doesn't work, but it's kmtksk who needs to freeze the device then re-upload it, not us users who need to freeze it. I hope he does, because if it sounds as good as it looks this will be a pretty special device.

Oh, I will! Thanks for the great device. :-)

Yes, that's fixed it! Amazing work. This is going to come in REALLY handy for my upcoming live shows :-)

Do you mean the patch that you asked me to test doesn't work for you?

It might be worth freezing it and uploading it again... I'm not an expert by any means but I know freezing patches is often a simple cure for issues caused by missing externals from other user libraries. Maybe you have something that I'm missing on my system?

Yeah, that all seems to work fine. Plus it's really useful!

I'll check the ClyphX forums to see if I can find anything out. There aren't any non-standard externals in this patch I might need, are there? Did you freeze the device before uploading?

Oh right, I do have it set up like that. My plan didn't work anyway...

That video you've posted is making me want this to work even more now!

I know, but you can't add a remote input if there's no Input set up for ClyphX in the Control Surface section for it. ie. ClyphX doesn't even appear as an available MIDI port if Input is set to "none" in the top half of that pref pane.

Ah, that could be it - I don't get ClyphX as a MIDI port option because the manual says to leave the Input and Output section in the Control Surface section blank. I'll create a new IAC port and set it up like that - I'll let you know if it works!

Sorry about all the repeated posts - the webfilter at work seems to be doing something weird when I refresh the page.

I've done exactly as you've described but I can't get anything to happen. The rename function doesn't work, nor the Play and Stop functions.

This sounds incredibly useful, but I can't get it to do anything. I installed ClyphX and can successfully run [TEST] METRO like they suggest in the ClyphX User Manual to make sure it's running properly.

I've created a single 2 bar clip on a Drum Rack channel to test it, but pressing the buttons in the NoteScrambler doesn't do anything. Do I need to name the clip or give it an [ID], or something?

This sounds incredibly useful, but I can't get it to do anything. I installed ClyphX and can successfully run [TEST] METRO like they suggest in the ClyphX User Manual to make sure it's running properly.

I've created a single 2 bar clip on a Drum Rack channel to test it, but pressing the buttons in the NoteScrambler doesn't do anything. Do I need to name the clip or give it an [ID], or something?

This sounds incredibly useful, but I can't get it to do anything. I installed ClyphX and can successfully run [TEST] METRO like they suggest in the ClyphX User Manual to make sure it's running properly.

I've created a single 2 bar clip on a Drum Rack channel to test it, but pressing the buttons in the NoteScrambler doesn't do anything. Do I need to name the clip or give it an [ID], or something?

That's it! Fantastic - I hadn't even noticed the new X and Y boxes in the right-hand corner, and as you'd guessed, I was trying to map to the boxes next to the circle area. I feel like such a fool, lol. :-).

Thanks very much for the quick fix and for the awesome device. I think I'd better donate something now, since I'm going to be using this a LOT.

Oh no! Thanks for trying to fix it so quickly, but it's actually broken it a bit more! It still jumps between 0 and 1, but now the using the X and Y sliders doesn't move the point on the interface at all (you *can* move the point on the map by clicking and dragging it with the mouse & the X/Y sliders register the movement correctly, but if you try to use the sliders to move the point around the map, the point doesn't move at all).

Hope that makes sense! Sorry for causing you problems! :-)

This is a great device, but I'm having problems controlling the X and Y sliders with any MIDI CC controllers. They map fine, but the values of X and Y jump straight from 0.0 to 1.0 with nothing in between. Is there any easy way to get this to work?

Forgot to add - I'm running the 64 bit version of Live and M4L.

Not wokring here either - it doesn't make any sound at all. I had a quick look a the patch but can't spot anything obvious, but I'm not very experienced with Max.

MBP i7, running 10.8.3, Live 9.04, Max 6.1.0 (although I'm about to update to 6.1.2 right now - I didn't realise I hadn't!).