Licensing Question Linux and Windows

[cactus-head]

Hello,

If I have two computers one that has Linux installed and one that has Windows, can I install Mixcraft on each? I'm not talking about a dual boot on one machine, I'm talking about two separate installations. My goal is to migrate 100% to Linux, but there's a transitional period where there are dedicated programs on Windows (like Mixcraft and all the other audio processing stuff I use) that I can't give up. I need to make sure that they run smoothly on the linux machine independently while I'm attempting the transition.

[Acoustica Greg]

Hi,

Yes, you can install and register your copy of Mixcraft on two or three of your own personal computers.

Greg

[cactus-head]

Thanks

[jwmix]

My goal is to migrate 100% to Linux, but there's a transitional period
where there are dedicated programs on Windows (like Mixcraft and all the
other audio processing stuff I use) that I can't give up.

FYI

Like command line ways?
Well...

PowerShell
a Microsoft free scripting/automation product
created around 2002
became in 2016
a Microsoft open source
scripting/automation project
that runs on Windows, Linux and Mac OS

A lot of Windows products
(and third party products)
even have their own PowerShell cmdlets
(think commands)
and yes one can write
one's own cmdlets too
but most DAW users
will never need to
(but like Linux ways
it's available)

Windows PowerShell 5.1
is in one's Start button's menus
always start with the
regular PowerShell user verion
no need for the Admin version
(for now)

So maybe start learning
Windows PowerShell 5.1
and later let's us know
how Linux PowerShell 7.1 DAW actions
(in these other DAW/music worlds)
compares to Windows PowerShell 5.1 DAW actions
(Yes there is a Windows PowerShell 7.1 version too
but it's not as "Windows ways"
as Windows PowerShell 5.1
and is not sitting in one's computer
like Windows PowerShell 5.1 is)

Text based scripting like
Perl
Python
LUA
(and etc. ways)
can be rewitten
into PowerShell scripting/code
to take advantage of the
everything's an object in PowerShell
and these full objects
are passed via the pipeline too
(the more one uses PowerShell
the more one will understand
the full power of objects
compared to just text)

PowerShell can be ran
after the commandline prompt
just type in the PS actions
or via it's .ps1 scripting files
(the best and most powerful way)
or like how so many DAW users
now use scripting
via the CMD window's actions
(it's the same actions)
when one finds a PS action one needs
copy the PowerShell code
and paste it into Notepad
save with a meaningful name
then minutes/years later
copy from Notepad
and paste into a PowerShell window
(even better paste into the PowerShell ISE
and make one's own code changes)
after pasting into the PowerShell window
press the enter key

Need examples?

Windows PowerShell 5.1 cmdlet's
(think commands)
docs have
active user copy and paste examples
for learning PowerShell
and the PowerShell ISE
(the ISE is one of
PowerShell's text editors/runners
with many helpful
what can one use next
pop up windows)

PowerShell can be as simple
as one wants it to be
(like CMD dir actions
for most band members/studio workers)
or as powerful
as one needs it to be
(like a full Windows Form app's usage
where everything is done
via listboxes, textboxes or labels (and etc.)
using a talking computer
or images
or playing music
or whatever
for those certain
band members/studio workers/artists/clients/boss)

Whatever one's DAW data itch is
that needs to be scratched
PowerShell might do it

Notice the Windows PowerShell's docs examples
are business defined
just think/change this
into music data needs

If a program runs in Windows
like midicsv.exe and csvmidi.exe
(midi in text apps that produce output)
and whether the Windows app
produces output data
or not
PowerShell can run that app
and if the app produces output
then PS can use that app's output data
(to create different outputs too)

There are libraries
on the web like
NAudio, PeNet, DryWetMidi and etc.
(for whatever one's DAW or personal needs are)
plus every Windows library
(a lot sitting in one's computer)
that can be loaded into PowerShell
(like DAWs load VSTs)
and then PowerShell calls those library's actions

After learning
how the PowerShell doc examples work
one can then start working on
all the below DAW data issues/actions

Some studio workers
(concerning the below list of issues/actions)
might have the ole saying
I just run this app
and then see in it's output window
all the data I need
(that's okay)
but be aware
other studio workers
might have thousands of files/artists/clients
and need computer ways
not just the one person ways

With PowerShell
one can do the one person way
or the thousands of files way

Is an app/dll/whatever 32 or 64 bit?
Is it likely a VST?
Is it a midi file and what midi type?
Is there more than (number here) tracks in the midi file?

What are the midi file's midi event Tempo setting(s)?
What (in one's computer) DAW files have changed
or moved or been deleted (and at what time)?
What midi events happen at 1:23?
What words does one use most often in one's lyrics?
What does midi in text mean?

Where's one's project's file's midi/audio/text data?

A PowerShell randomly selected
Music Maker project file
was PowerShell searched
and it had over
200 possible c: finds
Around 70 turned out to be
just plain data bytes
but the rest where
full paths to some Guitar Pro files
full paths to some VST actions
full paths to some Mixcraft paths
and tons of Music Maker full paths
all in that one Music Maker project file

Which of one's DAW projects
contain the data
(here words or byte numbers)
within any of one's DAW's files?
(incuding one's DAW tracking files)

Can one merge audio/video files (wave/mp3/mp4/etc)?
Can one learn scales, chord note names, progressions (and etc.)?
Can one's computer create random guitar strums/music patterns/progressions?
Can one find an object's GUID info?
Can one create drum maps and put them into DAW use?
Can one find out what midi notes/events are played at (or near) 0:25?
Can one use .lnk files (it's data)?
Can one use mp3/audio/CD/etc. tags (it's data)?
Can one create/read/display CSV/logs/text/whatever files?

Can one test skin file color change actions
via only image changes
seeing the before and the after
skin color image changes
and then make the DAW use those changes?

The PowerShell actions
(are something like)
Search the skin file to get the SettingColorToChange
Show a full DAW image (or parts)
Then by using some Windows .NET Framework library calls
Pixel = GetPixel(AtThisLocation)
If(Pixel.Color match SettingColorToChange) {
SetPixel(ToNewColor)
} # End of If().
Show the new color changed image
Like the new color
Change the skin file's settings
Test the DAW
DAW break is over
Back to making music
That's one DAW itch scratched

Maybe a good place to
start with skin color changes
(for those skin file group of people)
using PowerShell
read all the skin files color data defines
get all the skin image pixel data colors
group the data
sort the data
(objects by color)
and then list them all

And hopefully finding out that the DAW
varys each object's color a little
70, 70, 70 for one object
and then other similar colored objects
set to 71, 69, 70
the next to 70, 69, 71
or something like that
then there's no need
to find where the pixel's location is
within the image (DAW)
just compare pixel colors

Maybe there's no such thing
as just a little itch afterall?
Good luck

All the above can be done via PowerShell
sometimes with loaded libraries
and sometimes without libraries
one file at a time
or by the thousands

Learn PowerShell ways
then Bing search for CSharp (C#) code
for what one wants to do
(say change image pixel's colors)
many Windows C# docs
have simple examples
(calling Windows libraries)
change the C# code into PowerShell code
(both are close to each other's ways)

But first learn PowerShell
how to read and write files
and then how to show an image
and so on
try walking
before one runs

Anyway PowerShell love's working with data
and after a while
one might too

Everyone's workflow is different
and no one's scripting code
will solve all of another's needs

But scripting let's one use
others shared scripting code
a piece here
a piece there
combined with one's own code
(the way all programmers work)
to solve one's own
scripting DAW data needs
(yep just like Linux ways)

But one must first
learn some PowerShell
in oder to put it all together
for one's own workflow
or DAW group projects
a drum map maker
a songwriting toolkit
skin files toolkit
midi controller actions
whatever's the itch
(that's what DAW breaks are for)

Start using PowerShell with one's
DAW data
the DAW data long before the DAW uses it
or the DAW data right before the DAW uses it
or the DAW data while the DAW is using it
or the DAW data long after the DAW is closed

PowerShell love's working with data
and producing more useful data

The single hardest part of PowerShell
is explaining how to
PowerShell "do it"
(saying use this cmdlet(s)
then having to explain the cmdlet(s)
and how to use the cmdlet(s)
over and over again)
so learn PowerShell ways
by using the doc's examples
(then I might have some DawPsDemo examples)

PowerShell scripting/coding
is not as difficult
as it might sound
(but it can be)
but if one did any
punch card stacks
peeks and pokes
basic
html
javascript
any programming
any scripting
midi controller actions
or even just simple CMD dir actions
one can start
learning and doing
active user copy and paste
PowerShell scripting/code
to solve one's own DAW data issues
start with the Windows PowerShell 5.1 doc examples
(one might even end up using .ps1 script running ways)

Maybe also take a look
at Microsoft's Pete Brown's
PowerShell usage of the Windows 10's
new system midi actions
all his PS midi note examples
and his PS midi controller examples
(written as .ps1 scripting files)
but can also be run via
active user copy and paste too
Downloaded his PS midi cmdlets
use the ISE (with pop up help)
and try his midi cmdlets
with one's input and output midi devices

One might also be interested
in Windows Terminal 1.7
command line ways
(maybe not so much
for most DAW users)

Just a FYI

Read PowerShell blogs, watch PowerShell ISE videos.

Adjust their PS business ways, to your PS music needs.

Have fun, find a PowerShell youngster (for help) and share!

[Mark Bliss]

Cut and paste is awesome! My favorite tool from the '90s!