Announcement

Collapse
No announcement yet.

Audio waveform height in timline and moving subclips to other folders.

Collapse
X
 
  • Time
  • Show
Clear All
new posts

  • Audio waveform height in timline and moving subclips to other folders.

    Hello folks,

    I made it through unscathed from our work trip to Dayton covering the 1st two rounds of March madness. I've got a couple questions that came out of that trip.

    1. How can I increase the size of the timeline's waveform display. We shoot audio on a normal, full level, but the waveform's are barely registering any changes.

    2. How can I move/manage groups of subclips. I was unable to move or transfer or copy subclips into desired folders. The source file would move, but the sublips would no show up - remaining in the original folder. (perhaps I'm using incorrect logic here)


    Please inform me, JEDIus Masters.

    Jade

  • #2
    1. You can increase the track height by right clicking on left track header, select Height, and choose 4 or 5. You can also switch the wave forms to Log in the User Settings

    2. Sub clips should drag between folders just like normal clips. How are you creating them? Can we see a screenshot of your Bin?
    1: Intel 13900K, Asus ROG Z790 Hero, G. Skill Trident Z5 6400 64G DDR5, Asus Tuff Gaming GeForce 4070Ti, WD SN850XNVMe 1T, 4T (2), Seagate IronWolf NAS 7200 14TB, Lian Li Galahad 360, Aja Kona 4, Super Flower Leadex Platinum 1600W

    2: 3970X Threadripper, Asus ROG Strix TR40 E Gaming, G. Skill Trident Z Neo 128G DDR4 3600, EVGA GeForce RTX 2080Ti, Samsung 970 EVO M.2 1T, Intel 660P M.2 2T (2), Seagate Ironwolf NAS 12T, Enermax TR4 360 AIO, Lian Li 011 DXL, AJA Kona 4, Asus ROG Thor 1200

    Comment


    • #3
      Originally posted by GrassValley_PS
      1. You can increase the track height by right clicking on left track header, select Height, and choose 4 or 5. You can also switch the wave forms to Log in the User Settings

      2. Sub clips should drag between folders just like normal clips. How are you creating them? Can we see a screenshot of your Bin?

      On the first point, I saw numerous Edius users over in Dayton. All of them had waveforms that took the entire height of the track, while not being larger than a 2 or 3 row size. I gave size 4 and 5 a try and the waveforms were still the same ratio.


      Here's a screenshot: Clip 'OSU Highlights' being the parent clip.




      I'm still experimenting with this one...

      Comment


      • #4
        Just changed tog 'log' view. I got better height, I'd like the same height scale in linear.

        Comment


        • #5
          In linear mode the waveform reflects how loud the sound is. If it is maximum volume it fills the display. Does it sound quiet?

          Have you tried adjusting the gain (right click on the clip, choose properties, go to the audio tab an look near the bottom)? This will make the clip louder and make the waveform bigger in linear mode. Add too much gain it is distorted.

          You can also normalize the clip (right click and choose normalize) and EDIUS will automatically work out the gain up to a certain level - although with the default of -20 I often find waveforms get smaller because my cameras actually record at a level higher than -20db.

          Log wave forms will always fill the display but don't reflect how loud a clip is. This is the default setting for EDIUS and probably how the other editors had it set.

          Personally I prefer linear. Neither way of displaying sound should affect how it sounds.
          EDIUS silver certified trainer.
          Main edit laptop: DVC Kaby Lake desktop processor laptop, 32GB RAM, 3.5Ghz i5 desktop processor, nVidia 1060, Windows 10.
          Desktop: 4Ghz 9900K processor, 32GB RAM, nVidia 1660TI GPU, Windows 10.
          Desktop: 2Ghz 12 core Xeon processor, 32GB RAM, nVidia 1060, BM Intensity Pro, Windows 10

          Comment


          • #6
            Thanks, David. I will give this a shot.

            Comment


            • #7
              Yes, of to Gain as David mentioned, and you will see the waveform grow larger. Depending on what you are doing, you can also use normalize to get larger waveforms.
              1: Intel 13900K, Asus ROG Z790 Hero, G. Skill Trident Z5 6400 64G DDR5, Asus Tuff Gaming GeForce 4070Ti, WD SN850XNVMe 1T, 4T (2), Seagate IronWolf NAS 7200 14TB, Lian Li Galahad 360, Aja Kona 4, Super Flower Leadex Platinum 1600W

              2: 3970X Threadripper, Asus ROG Strix TR40 E Gaming, G. Skill Trident Z Neo 128G DDR4 3600, EVGA GeForce RTX 2080Ti, Samsung 970 EVO M.2 1T, Intel 660P M.2 2T (2), Seagate Ironwolf NAS 12T, Enermax TR4 360 AIO, Lian Li 011 DXL, AJA Kona 4, Asus ROG Thor 1200

              Comment


              • #8
                Gain is not the same as audio waveform height scaling. One doesn't want to amplify the audio signal in the video, we just want to scale it so we can still see the detail when the audio is quiet.

                We need a zoom y axis amplitude control.

                Comment


                • #9
                  Originally posted by djspearritt
                  Gain is not the same as audio waveform height scaling. One doesn't want to amplify the audio signal in the video, we just want to scale it so we can still see the detail when the audio is quiet.

                  We need a zoom y axis amplitude control.
                  Yes thats true - since years!
                  But what should we do if we don't get it from the developers ??
                  We can use some workarounds - raising the gain is one of them; nothing else.
                  Sorry - kurt
                  HW: ASUS Z170-A; Proz: i7-6700K; RAM: 32 GB DDR4; GPU: RTX-3070, 8GB GDDR5; SSD: SAMSUNG-850-Pro, 500 GB
                  SW: WIN-10/64 PRO (22H2-19045-2364​​), Firefox u.a.
                  NLE: EDIUS-X(10.34.11471)-WG​​​; RESOLVE-18.6.00006 Studio
                  // Read > Test > Understand

                  Comment


                  • #10
                    Originally posted by kpot
                    But what should we do if we don't get it from the developers ??
                    Simple as that: don't buy their software/upgrades any more!
                    Intel Core i7-7820X ---- Noctua NH-D15S ---- MSI X299 GAMING M7 ACK ---- 64GB RAM 2666-15 Corsair Dominator Platinum ---- 500GB Samsung 960 EVO M.2 (system SSD) ---- 512GB Samsung 960 PRO M.2 (data SSD) ---- Aorus Nvidia GTX 1080 Ti ---- be quiet! SILENT BASE 600 Case ---- be quiet! Dark P. Pro P11 850W ---- Win10 Pro ---- Edius WG 8.53.2808

                    Comment


                    • #11
                      Originally posted by Captain
                      Simple as that: don't buy their software/upgrades any more!
                      Rooooooooooh.
                      Yvon durieux alias "Haddock" Belgium GMT + 2

                      Sorry for my poor english, I am french native speaking

                      Main System: Azus Z87 Pro, [email protected], 16gb ram, Nvidia GeForce GT 630, Windows 7 Pro 64, Samsung 840 pro, Edius 8.53.2808 WG and 9.54.6706 + NXexpress or HDspark, 2T separate video SSD.

                      Comment


                      • #12
                        Originally posted by djspearritt
                        Gain is not the same as audio waveform height scaling. One doesn't want to amplify the audio signal in the video, we just want to scale it so we can still see the detail when the audio is quiet.

                        We need a zoom y axis amplitude control.
                        Glad to read that I am not alone with this problem - but I never had it, before the NORMALIZE function was integrated. I use -18dB as a reference level which should be correct for digital, but then the audio - which was correctly recorded with my camera + external Sennheiser micro - is so small, I can hardly see - and hear - it.

                        At present I have to raise the gain by 10dB for every clip I put on the timeline - I don't think this is normal. I thought NORMALIZE was to adjust all audio clips, after the whole editing was made.

                        What do you suggest: Shall I set the reference level to 0dB or 8dB? This would probably solve it, but does not appear logical to me.

                        Comment

                        Working...
                        X
                        😀
                        🥰
                        🤢
                        😎
                        😡
                        👍
                        👎