Hey there,
I guess I never really checked the new stuff on my ozone copy I bought- not much time in my life- but tonight I checked it out, and wondered how we could use eq matching in a circumstance where we want to apply it to a different project each time???
More or less, I want to know how I can do this per project in tracktion. Say I make a really nice mix and want that applied to the rest of my EQ in the rest of the songs on separate projects...
ideas? do you have to make presets?
Thx
RONC
ozone eq matching??
-
- KVRAF
- 6490 posts since 14 Jun, 2004 from Rochester, NY
-
- KVRAF
- 7120 posts since 22 Jan, 2005 from Sweden
Basically what you do is make and save a profile of the project that you like that sounds really well.
Then you can recall that one and match that to your new projects.
It's really well described in the help system of Ozone.
Then you can recall that one and match that to your new projects.
It's really well described in the help system of Ozone.
-
- KVRAF
- 5268 posts since 16 May, 2002 from Brisbane , Australia
I think the description is quite strange.lfm wrote:It's really well described in the help system of Ozone.
Intel Core i7 8700K, 16gb, Windows 10 Pro, Focusrite Scarlet 6i6
-
- KVRian
- 1394 posts since 28 Mar, 2002 from Austria
Did you see the video-tutorial for matching eq on the iZotope page ?
http://www.izotope.com/products/audio/ozone/#
http://www.izotope.com/products/audio/ozone/#
-
- KVRAF
- 2049 posts since 18 Sep, 2003 from Seattle USA
I can't view the flash for some reason so I don't know if it's mentioned in the tutorial...
To use EQ matching in a project gets kind of tricky. To use EQ matching you need to take a snapshot of both the source and target. Snapshots can either be imported or exported into any of the 8-10 slots available (I forget how many are usable). The problem is that snapshots - either freshly captured or imported into Ozone3 - are global data and lives in a single 'shapshotstate' file. Ozone3 communicates only with this global snapshotstate file to save context to disk. This stuff is not saved in a preset. I've mentioned this to Ozoen3 development and they are considering various options that may be possible so that presets or something can be remembered so when you bring up an Ozone instance in any song the proper snapshots will be used. There's a lot of data in a snapshot though.
If you were to have a project with 11 songs, load an instance of Ozone3 into each song. Capture the source snapshot for the 1st song and match to the target snapshot that costs 2 slots. Move on to the 2nd song and capture the snapshot in third snapshot slot, match to the already present target. Now you've used 3 slots. After your 9th song you have run out of empty snapshot slots. If you reuse the 1st snapshot slot then it screws up the EQ match for the 1st song when you close the project session and reopen (maybe in the same session also I'm not sure). At any rate if you have a project with 9 songs and a target snapshot you're ok, I never replaced the 6db and pink slope so I had a max of 7 songs and a target snapshot.
Another thing to note is the great difference in sound when choosing an EQ FFT size of 1K, 4K, 16K.
It was all good fun for a while but in the end matching EQ (even when using the gentlest of smoothing - .96 or so) just never made sense to my ears. It sounded different and brighter and beefier but it just wasn't right (after all it is from 2 different songs - similiar as they may be!). It did help me decide to get my EQ chops in better order though!
To use EQ matching in a project gets kind of tricky. To use EQ matching you need to take a snapshot of both the source and target. Snapshots can either be imported or exported into any of the 8-10 slots available (I forget how many are usable). The problem is that snapshots - either freshly captured or imported into Ozone3 - are global data and lives in a single 'shapshotstate' file. Ozone3 communicates only with this global snapshotstate file to save context to disk. This stuff is not saved in a preset. I've mentioned this to Ozoen3 development and they are considering various options that may be possible so that presets or something can be remembered so when you bring up an Ozone instance in any song the proper snapshots will be used. There's a lot of data in a snapshot though.
If you were to have a project with 11 songs, load an instance of Ozone3 into each song. Capture the source snapshot for the 1st song and match to the target snapshot that costs 2 slots. Move on to the 2nd song and capture the snapshot in third snapshot slot, match to the already present target. Now you've used 3 slots. After your 9th song you have run out of empty snapshot slots. If you reuse the 1st snapshot slot then it screws up the EQ match for the 1st song when you close the project session and reopen (maybe in the same session also I'm not sure). At any rate if you have a project with 9 songs and a target snapshot you're ok, I never replaced the 6db and pink slope so I had a max of 7 songs and a target snapshot.
Another thing to note is the great difference in sound when choosing an EQ FFT size of 1K, 4K, 16K.
It was all good fun for a while but in the end matching EQ (even when using the gentlest of smoothing - .96 or so) just never made sense to my ears. It sounded different and brighter and beefier but it just wasn't right (after all it is from 2 different songs - similiar as they may be!). It did help me decide to get my EQ chops in better order though!
-
- KVRist
- 55 posts since 29 Aug, 2006
Iive seen the tutorial when I receive their newsletter, and it looks really cool 
Elemental audio Firium (I think it's now roger nichols) has the same function, but IMO it will never be a shortcut for mixing.
BTW I think (not sure..)you can make copy of EQ curve and store them on your hard drive with firium.
Marcus
Elemental audio Firium (I think it's now roger nichols) has the same function, but IMO it will never be a shortcut for mixing.
BTW I think (not sure..)you can make copy of EQ curve and store them on your hard drive with firium.
Marcus