|
|
Post by kcatthedog on Nov 18, 2021 7:56:45 GMT -6
I have a new to me 2020 m1 mini here going to one 34 inch monitor so far so good.
Is there anyway to use my 2012 i7 as a second monitor ?
Mini is big sur, mbp is Catalina.
Would sidecar do that, if so wirelessly or does it need to be hardwired ?
Thx!m
I thought sidecar was only for iPads.
|
|
|
|
Post by mrholmes on Nov 18, 2021 8:14:21 GMT -6
Yes, there are apps on the App store which can do this. Edit: Seems to be possible with a cable connection too.
(Google knows everything)
You may like a different - Idea:
But it's maybe an even better idea to use it as a server to run CPU intensive VSTis such as complex B3 Organ etc. Its donation ware.... audiogridder.com/ |
|
|
|
Post by Johnkenn on Nov 18, 2021 8:25:41 GMT -6
Yes, there are apps on the App store which can do this. Edit: Seems to be possible with a cable connection too. (Google knows everything)
You may like a different - Idea:
But it's maybe an even better idea to use it as a server to run CPU intensive VSTis such as complex B3 Organ etc. Its donation ware.... audiogridder.com/I think popmann has mentioned this? |
|
|
|
Post by kcatthedog on Nov 18, 2021 10:01:27 GMT -6
Thx, turns out even simpler, one main monitor off hdmi, run second on tb with tb to hdmi converter cable, which I have. So, rocking my new 34 inch curved as my main monitor (mixer in logic), second my older 27 inch , both hdmi, running the edit/region view in logic! Nice! ibb.co/ZTQP7V2 |
|
|
|
Post by popmann on Nov 18, 2021 10:47:15 GMT -6
Yes, there are apps on the App store which can do this. Edit: Seems to be possible with a cable connection too. (Google knows everything)
You may like a different - Idea:
But it's maybe an even better idea to use it as a server to run CPU intensive VSTis such as complex B3 Organ etc. Its donation ware.... audiogridder.com/I think popmann has mentioned this? Using a second computer to run VIs? Absolutely. Gold standard. Second audio interface. Connect via ideally analog (and one way MIDI) cabling. AudioGridder? Never used it. Heard about it...read up and something made me completely ignore it-haven't looked at recent developments. Don't remember what that was, but I find that idea of doubling (or 4x) the latency of your DAW and making the sample rate required to be synchronous with the project, so you don't have to have a second (small IO) interface...kinda...chincy and missing the benefits of having a second machine. Vienna Ensemble Pro is the go to for this and has been for years. ...but, if you run things MIDI all the way to mixdown--and fan out SD3 to it's 32ch output and put processing on those LIVE audio busses at mixdown...it will be a BIG shift in your workflow to use a second machine. You will see much more benefit for (what I feel like from reading is) your current workflow by limiting your "everyday" soundset to what you can fit on the internal Apple storage (and spending to make that big enough) and put the rest (older legacy instruments) and audio/project files on a Thunderbolt SSD. |
|
|
|
Post by kcatthedog on Nov 18, 2021 11:23:39 GMT -6
Thx, I was just trying to get 2 monitors working on my m1 mini.
Mission accomplished.
If I wanted to run say slate drums on the old mbp, but in logic sessions in the new mini mini, how would I do that ?
|
|
|
|
Post by mrholmes on Nov 18, 2021 11:31:46 GMT -6
Thx, I was just trying to get 2 monitors working on my m1 mini. Mission accomplished. If I wanted to run say slate drums on the old mbp, but in logic sessions in the new mini mini, how would I do that ?
Vienna Server or Audio Gridder. They also stream sound data, you also can run plug ins on the server machine. With Audio Gridder you also have the original plug in window in your M1 session, but the plug runs on your MBP. The setup is not too easy but once everything runs you will smile....
|
|
|
|
Post by Ward on Nov 20, 2021 9:08:12 GMT -6
Very interesting! Although not the intended beneficiary, I'm grateful for learning something new today!
Audio Griddler sounds like something I could use!
|
|
|
|
Post by OtisGreying on Nov 20, 2021 9:28:24 GMT -6
I think popmann has mentioned this? Using a second computer to run VIs? Absolutely. Gold standard. Second audio interface. Connect via ideally analog (and one way MIDI) cabling. AudioGridder? Never used it. Heard about it...read up and something made me completely ignore it-haven't looked at recent developments. Don't remember what that was, but I find that idea of doubling (or 4x) the latency of your DAW and making the sample rate required to be synchronous with the project, so you don't have to have a second (small IO) interface...kinda...chincy and missing the benefits of having a second machine. Vienna Ensemble Pro is the go to for this and has been for years. ...but, if you run things MIDI all the way to mixdown--and fan out SD3 to it's 32ch output and put processing on those LIVE audio busses at mixdown...it will be a BIG shift in your workflow to use a second machine. You will see much more benefit for (what I feel like from reading is) your current workflow by limiting your "everyday" soundset to what you can fit on the internal Apple storage (and spending to make that big enough) and put the rest (older legacy instruments) and audio/project files on a Thunderbolt SSD. popmann, so to run vienna the reccommended way is this done with a second interface for the second computer? I do have a smaller interface and I am really interested in incorporating my old computer into my set up specifically for extra VI use, but I've found I'd need to mess with the clocking of my main setup to get this done when I've researched. It sounds like Vienna ensemble pro solves for that? Are you running a vienna ensemble pro set up currently?
|
|
|
|
Post by gravesnumber9 on Nov 20, 2021 10:32:27 GMT -6
Maybe I'm just a bit slow this morning. This sounds really awesome and like something I could use. B3's (mainly, though also some others) crush my CPU and I'd love to process them on a second laptop which I don't really use for anything.
Is there an article or anything with a step-by-step, explain it to me like I'm a five year old set of instructions to do this? I can't even think of what I would search for on Google.
|
|
|
|
Post by popmann on Nov 20, 2021 11:20:45 GMT -6
VEP does all over ethernet. No secondary interface. Yes it “takes care” of whatever you think is a problem. There no digital connections. No need for “clocking” a second machine. One of the primary benefit is that the VI can run at its native rate without regard to the project sample rate.
If you ignore the ethernet apps that make it all synchronous and MORE latent than running it on the same machine (removing another advantage of the second machine)….its literally like using ANY external kidi device, which if youve never done it is lifht years more complex than a VI living inside your DAW. I forget how many people never did that for the 20 years that it was the ONLY choice.
I wouldn't run VEP or Audiogridder if they paid me. It removes nearly every reason I like using a second machine.
|
|
|
|
Post by gravesnumber9 on Nov 20, 2021 18:16:32 GMT -6
VEP does all over ethernet. No secondary interface. Yes it “takes care” of whatever you think is a problem. There no digital connections. No need for “clocking” a second machine. One of the primary benefit is that the VI can run at its native rate without regard to the project sample rate. If you ignore the ethernet apps that make it all synchronous and MORE latent than running it on the same machine (removing another advantage of the second machine)….its literally like using ANY external kidi device, which if youve never done it is lifht years more complex than a VI living inside your DAW. I forget how many people never did that for the 20 years that it was the ONLY choice. I wouldn't run VEP or Audiogridder if they paid me. It removes nearly every reason I like using a second machine. Reading the other thread it looks like you’re doing this and just printing audio, correct? |
|
|
|
Post by popmann on Nov 20, 2021 19:36:45 GMT -6
Always print audio with one or two machines.
But, if I need to record midi, that happens on the DAW box….until I get the strings or whatever wheee I want it—then I print that as audio.
|
|
|
|
Post by gravesnumber9 on Nov 20, 2021 20:55:53 GMT -6
Always print audio with one or two machines. But, if I need to record midi, that happens on the DAW box….until I get the strings or whatever wheee I want it—then I print that as audio. Interesting. I really love the committing aspect of that (and I do a ton of effects commitment on the way in) in terms of performance, but I really enjoy not having to think too much about instrument selection going in. Especially with piano. I just record with my default piano and then figure out later if a different instrument (say, a U1 or Steinway) would have been better. Likewise with my organ stuff I don't really fiddle too much with all of the stuff that my B3 instrument can do because I generally do that much later. I'm not sure why I got so hooked on that. I've recorded almost my entire career on real pianos until just a couple years ago and at least 50/50 on real organs. I never felt the need to change my piano sound or my organ settings. I think it's because I'm often serving as both engineer and performer maybe? Kind of nice to have at least one engineering task I can remove. |
|
