MuLab 10.0.85

[MuTools]

If you, or anyone else, can tell me the clipboard format they're using for such copy-paste i'll have a look at it.

[liquidsound]

Not easy!
It’s an unusual behavior by Reaper to be able to access the FL MIDI clipboard and, more intriguing, in Reaper the Edit>paste is dimmed, not selectable but Ctrl-V performs the paste of the MIDI item.

If I will find some info I will let you know.
Thanks for reply to my question

[pljones]

Hi Jo, I have a question:
In Reaper, when I use FL Studio-VST, FL Piano-roll has a command “Copy to MIDI clipboard”.

So I can copy the MIDI notes to that “clipboard” and then paste them in Reaper as a MIDI Item.

So far, I tried several DAWs and no one can do this but Reaper.

Is this something that could be implemented in MuLab in the future?

Can you do it from MuLab VST to Reaper now?

(I guess you're asking for from some other VST to MuLab app, though.)

[liquidsound]

Hi Jo, I have a question:
In Reaper, when I use FL Studio-VST, FL Piano-roll has a command “Copy to MIDI clipboard”.

So I can copy the MIDI notes to that “clipboard” and then paste them in Reaper as a MIDI Item.

So far, I tried several DAWs and no one can do this but Reaper.

Is this something that could be implemented in MuLab in the future?

Can you do it from MuLab VST to Reaper now?

(I guess you're asking for from some other VST to MuLab app, though.)

not working (as suspected).
“Copy to MIDI clipboard” is not well explained in the FL help:

“COPY TO MIDI CLIPBOARD… Copies the data to the MIDI clipboard. You can past data into any sequencer that supports MIDI clipboard format.”

Maybe “MIDI clipboard format” is part of the MIDI standards?
I have no clue.

[pljones]

Maybe “MIDI clipboard format” is part of the MIDI standards?

No, MIDI standards don't specify any clipboard. Clipboards are used for data exchange between computer applications. If and only if the DAW is granting the Plugin write access to the clipboard as a whole and the data written is tagged with a format specifier by the Plugin that the DAW understands would I expect the DAW to be able to paste the data in whatever manner it's used to pasting incoming clipboard MIDI data.

So the question is whether there's a standard for Clipboard MIDI data...

Yes, there is a standard for MIDI data on the clipboard, and it is the Standard MIDI File format. Applications that support MIDI copy-paste functionality place Standard MIDI File data on the public clipboard under a specific data type, allowing other compatible programs to retrieve and paste the data. While MusicXML is a more comprehensive format for exchanging music notation, MIDI copy-paste offers a quick way to transfer basic musical snippets between notation programs and Digital Audio Workstations (DAWs).

How it Works

Application Support:
When you copy MIDI in a program like Sibelius or Pro Tools, it places the Standard MIDI data on the public clipboard.

Data Type:
The clipboard stores this data under the data type public.midi-audio or a similar identifier.

Inter-Application Transfer:
Any other application that understands how to process MIDI data from the public clipboard (using the same data type) can then retrieve and paste that information

All the references Gemini quotes come from Avid / ProTools / Sibelius.

[liquidsound]

I saw the Sibelius reference during my search, but I could not find a technical data to post here to produce a solution for MuLab.
Maybe it is there but definitely none that I can understand...

Thans for digging into the subject

[xmstkvr]

Do you have any news on this odd issue about LX480 in M10 on your system?

I actually did. And here is what happens and why it works for you. And here is why final outcome is exactly as expected (they bounced the ball back to you).

When you install the LX480 VST2 version, it works in MuLab. But when you install the VST3 version, it doesn't work, and it crashes MuLAb completely.

Obviously, we tested more things, and here is the list of where LX480 v4 can load normally - VST2 or VST3, or just one or both

Cubase - VST2, VST3 ok
Reason - VST2, VST3 ok
Studio One - VST2, VST3 ok
FL Studio - VST2, VST3 ok
Ableton Live - VST2, VST3 ok
Reaper - VST2, VST3 ok
BitWig 5 (and 6 beta) - VST2, VST3 ok
MuLab 10 VST2 Ok, VST3 -=NOT OK=- crashing MuLab

It even loads fine in shells like VCV Rack and DDMF metaplugin. It only fails to load in VCV Rack. I really, honestly spent way too much time on this.


I lost many hours in troubleshooting this with other people, and in the end, I don't have the will to push this further. I initially provided all of these details, and you still pointed me in other directions, while the same product really works fine in all other DAWs on my own computer.

It was my logical conclusion that since the product works perfectly fine in other environments that you should at least look at yours. Now I dragged other people into this, and they had the same report.

That's fine, I can only accept that this will not get anywhere in the end, but at this point, I don't intend to push this further. I am giving up.

FYI I still intend to use MuLab because it's awesome software.

[MuTools]

I actually did. And here is what happens and why it works for you.

After reading your reply i still don't know why it worked well on my system but not on yours.

they bounced the ball back to you.

I did not receive an email from Relab.

When you install the LX480 VST2 version, it works in MuLab. But when you install the VST3 version, it doesn't work, and it crashes MuLAb completely.

On your system.
LX480 VST3 worked fine on my system.
Odd.
And frustrating for both of us.

I lost many hours in troubleshooting this with other people, and in the end, I don't have the will to push this further. I initially provided all of these details, and you still pointed me in other directions, while the same product really works fine in all other DAWs on my own computer.

Because i can't research something that is not happening here.

It was my logical conclusion that since the product works perfectly fine in other environments that you should at least look at yours.

I did!
But it worked fine here.
Can't retest it anymore as the demo license expired.
Then i tried to find a contact email/form on their site but couldn't find it.
(they say to click a button but there is no button; nor an email address)

FYI I still intend to use MuLab because it's awesome software.

Thanks.

[syntonica]

Hey Jo, I finally got around to purchasing Mulab 10 and the links are broken for Mac. In particular, the link for 10.0.46. Please help me!

[MuTools]

Thanks for upgrading.
Where do you see a link to M10.0.46 for Mac? That's an outdated version!
The latest official release version is M10.0.85, available here: https://www.mutools.com/mulab-app-downloads.html

[syntonica]

I'm sure I refreshed the page, but I managed to just change the URL from 46 to 85 and got it that way. Also, I sent you a Mac crash report from 10.1.latest. It's happened twice to me while closing out of the Plugin Manager. <glares at JUCE>

[carlosigls]

Is anyone having problems with PSP plugins? When I activate them, I only get sound on one channel. I have to deactivate them to get sound back on both channels.

[sl23]

Yeah, I had the same issue and stopped using them.

[tiger001]

stupid question but how do i stop the follow screen action ?

when i'm (extremely) zoomed in on a clip, when playing my screen always jumps back to the beginning of the clip, but i'd like to stay focused on the workarea
(can't find it in the MuLab Docs)


why not have the (composer) Loop length displayed in the main screen?
it would be nice if we could set the loop length to (e.g.) 8 bars, have it locked (to that length) and we could drag it around, and/or set the loop start to the loop end so to shift the loop right (or left) to have it adjacent to the 'previous' loop


every time i copy a clip further down the track (composer), my track gets record armed again (although i turn it off every time) - i know there's a preference somewhere but this behavior is kinda "rude", don't you think?

[sl23]

You have to turn off Auto Scroll.
Been a long time since I turned it off as I hated it, I'm also on my phone, but iirc, there is a setting to turn it off in the preferences. But also, the setting is saved in the project, never understood the point of having two settings!!

To turn it off in a project, right click in the composer area, not on a sequence, and you'll see the setting. Just unchecked it.

You may have to go over previous projects as I did in order for them to disable it globally. Pita! But when it's done, it's done. New projects will then not use auto scroll.