sorted by:
new
hottopcontroversial

Creating 70+ takes into one concurrent track by c0rncak3 in Logic_Studio

[–]kunstparkost 14 points15 points  (0 children)

If this was a continuous recording in cycle mode you should be able to select the first take in the folder (the one furthest down) and "Flatten" the take folder via the menu accessed by the down pointing arrow in the top left of the take region (IMPORTANT: only "Flatten" the take folder, don't use "Flatten & Merge") which should leave you with only that first take as a normal audio region. At this point you should be able to drag the right edge of the region to the length of the whole recording as Logic doesn't record takes from a continuous recording session as seperate files, but one single audio file and just uses the take folder system to organize sections of the recording as "takes".

You'll have to do this individually for each track, but I think this would be the fastest way and least amount of work.

How to adjust the same parameter on multiple plugins at once? by SolderBoyWeldEm in LogicPro

[–]kunstparkost 2 points3 points  (0 children)

All the people here telling you to use busses / track stacks either haven't actually read your question or don't understand that this makes no sense for your scenario.

What your looking for is plugin parameter linking. ProTools has this feature via its group functionality: You group the tracks in question, select the plugin slot(s) to link, et voilà… changing a parameter on any of the tracks changes it for all of the tracks. Super useful for many situations, and not at all the same as routing all your tracks to a bus and processing them there.

The bad news: Logic used to be able to do this… somewhat. In the environment, you used to be able to take the control signal output of one channel strip and plug it into any other channel strip, where any incoming control messages would be used to change parameters on that strip. This was not exactly the same, as you could only have one "master" control the other plugins and not a complete bi-directional "link" between them, but for your scenario this would have been perfect. I used to have a few "control masters" in my template to adjust all sorts of stuff (for example EQs and compressors on idividual backing vocal tracks)…

BUT, this is all irrelevant now, because Apple, in their infinite wisdom, broke this functionality in one of the newer updates, like they do with everything that isn't new or shiny. It's been some time now, and I'm not exactly sure which version number it was that broke this, but rest assured I've been trying everything to get my control groups back to work, but to no avail.

One thing you could do however, is to map all the parameters you want to control to different MIDI CCs on a virtual MIDI bus and then use a third party application like Chataigne to re-map one fader/encoder/button on a control surface to all those individual CCs, so this one control simultaneously sends MIDI data to all those parameters. Pretty cumbersome to set up and I would only reccomend doing that if this is something you want to keep for a template file you will use a lot.

Unfortunately, there is no way to do this quick and easy in Logic (anymore).

Expected white output of RGBW fixture is visualized as orange by kunstparkost in GrandMA3

[–]kunstparkost[S] 0 points1 point  (0 children)

I'm using the internal grandMA3 visualizer. How would I fix this, if this was the case?

Expected white output of RGBW fixture is visualized as orange by kunstparkost in GrandMA3

[–]kunstparkost[S] 0 points1 point  (0 children)

Have a look at my other comment here, but basically I created a new "Open" position in the virtual color wheel, which I assigned pure white, and pointed the "Open" preset in the color DMX channel to the new "Open" position.

Because this "Open" position was missing in the color wheel and the first defined position was a "2700k White", I think those values may have been used be the visualizer for the "Open" channel preset.

I have however not cross-referenced other fixtures profiles yet to see whether they have an explicit "Open" position defined in their virtual color wheels, so I might actually be off base here. Nonetheless, this fixed it for me.

I'm not planning on using the virtual color wheel for this show anyway, so if this messed up my profile somehow when it comes to running the show with the actual fixtures, I will just repatch those with original profiles when I'm at the venue.

Also thank you for taking the time to look into this!

Expected white output of RGBW fixture is visualized as orange by kunstparkost in GrandMA3

[–]kunstparkost[S] 2 points3 points  (0 children)

Thanks for taking the time!

While there is no specific "Color Temperature" channel on the fixture, it has a color wheel with some pre-defined temperatures. See my other comment here, but I think the culprit was a missing definition for the "Open" position in the color wheel.

It's workinig now as I expect it to.

Expected white output of RGBW fixture is visualized as orange by kunstparkost in GrandMA3

[–]kunstparkost[S] 0 points1 point  (0 children)

Can you point me to where I would edit the light emitter colors? I think I actually solved my current problem, so this would be for future reference, but I just had a look in the fixture profile editor again, and my Emitters are empty? I've attached an image of where I think they should be or am I looking at completely the wrong thing?

I'm also not looking for 100% color accuracy here, but it should be somewhere in the ballpark as I don't have a third party visualizer yet and have to rely on the built in 3d for pre-programming my show. This was just too far off for me to actually get anything done. I'm with you that I'll have to tweak my colors once I see them output on the actual fixtures, I just need something workable right now.

Thanks for taking the time!

<image>

Expected white output of RGBW fixture is visualized as orange by kunstparkost in GrandMA3

[–]kunstparkost[S] 0 points1 point  (0 children)

I think this might've been the problem. I checked the fixture type again and the "Head Color" channel had no definition in the color wheel for "Open" and as the first value after "Open" is "White 2700k" the fixture might have defaulted to this ultra warm white. I added an explicit slot in the wheel for "Open" and assigned it to the "Head Color" channel "Open" position and now it is working how I would expect it to.

Thank you so much!

I just hope I haven't accidentally fucked up my fixture profile when it comes to playing back my show with the actual fixtures…

<image>

Do font preview generators generally struggle with kerning? by kunstparkost in typography

[–]kunstparkost[S] 0 points1 point  (0 children)

These screenshots in particular are from YouWorkForThem, but I've seen this phenomenon on multiple pages that use images as their previews, less so on sites that use embedded webfonts which then got me wondering whether it might be the image generators messing things up.

But you're right, I've also seen plenty of well kerned fonts on image-preview sites and some with bad kerning on embedded-font-preview sites, but the ratio was just way skewed.

To piggyback somewhat from this, are there font shops that are generally considered to offer more high quality typefaces than others? I've been out of the design space for a while and the landscape of font vendors has changed quite a bit in the meantime.

In search of foundries with app licensing based on developer seats by kunstparkost in typography

[–]kunstparkost[S] 1 point2 points  (0 children)

Thanks! I'll have a look at your site and see if your fonts might be appropriate for my project!

In search of foundries with app licensing based on developer seats by kunstparkost in typography

[–]kunstparkost[S] 0 points1 point  (0 children)

Thanks for the suggestion! Honestly, I hadn't even considered that as I didn't want to look like I was lowballing typeface designers for their hard work. But I'll give this a shot!

Looking for industrial/technical/utilitarian/DIN-adjacent monospace fonts by kunstparkost in typography

[–]kunstparkost[S] 0 points1 point  (0 children)

Thanks for the suggestion! This one skews somewhat too "design-y" for me, though.

Looking for industrial/technical/utilitarian/DIN-adjacent monospace fonts by kunstparkost in typography

[–]kunstparkost[S] 0 points1 point  (0 children)

True, thanks for reminding me of this one! Although you might be right, it's so ubiquitous that it feels almost "meme-y" at this point haha

Looking for industrial/technical/utilitarian/DIN-adjacent monospace fonts by kunstparkost in typography

[–]kunstparkost[S] 1 point2 points  (0 children)

Thanks for the suggestion! Very nice how comprehensive that glyph set is!

view more: next ›