59 postsPage 2 of 3
1, 2, 3
Something not good in version land.
I watched Marcus's video on saving versions as opposed to having history "versions ". So I tried it on SONGAA and SONGBB not really those names but for clarity let's say they became SONGAA (version 1.1) and SONGBB (version 1.1). I thought this is good I like it.

Then I went into Project XYZ which had SONGAA and SONGBB in it. v4.4.1

If you've got this far what would you expect.
A) A crash?
B) Load SONGAA (version 1.1) and SONGBB (version 1.1)
C) Load SONGAA and SONGBB original version
D) A crash?

Personally I expected B

Digimax FS, 1818VSL
User avatar
by pawelhebda on Wed Jan 16, 2019 1:09 am
jazzundso wrote
pawelhebda wroteThis version prevent external scripts to be loaded!!! So no more great addons.

What do you mean?


Studio One X - scripts are not loaded in this version.

Also if any one was using SO4 in OSX 10.9.5 Maverick as I did (everything was working perfectly fine till now). In 4.1.2 program crashes on start :(
User avatar
by jpettit on Wed Jan 16, 2019 1:42 am
peterbirch wroteSomething not good in version land.
I watched Marcus's video on saving versions as opposed to having history "versions ". So I tried it on SONGAA and SONGBB not really those names but for clarity let's say they became SONGAA (version 1.1) and SONGBB (version 1.1). I thought this is good I like it.

Then I went into Project XYZ which had SONGAA and SONGBB in it. v4.4.1

If you've got this far what would you expect.
A) A crash?
B) Load SONGAA (version 1.1) and SONGBB (version 1.1)
C) Load SONGAA and SONGBB original version
D) A crash?

Personally I expected B

Did you do the versioning in the Song window?
If the Project was built on master from SONGAA and SONGBB original version then the project will still be there.

My Website, Free Studio One Advance Training
SPECS:Win 10 64-bit, 12 Core i7: 32Gb DDR4 ram, 40" 4K monitor, StudioLive 24, Quantum, Faderport16, Central Station Plus, Sceptre 6,Temblor T10, Eris 4.5, HP60, Studio One Pro 4.0, Reaper 5.9, Sonar Platinum
User avatar
by snb1 on Wed Jan 16, 2019 2:08 am
Not able to save Beat-Linear selection in my template. It'll save under the edit window but not on the song page.

Attachments
Screen Shot 2019-01-16 at 12.03.28 AM.png
Last edited by snb1 on Sat Jan 19, 2019 5:41 am, edited 1 time in total.

Studio One Pro 4.1.2 64 bit, Mac OS 10.12.6, Mac mini (Late 2012) 2.3GHz quad-core Intel Core i7 (Turbo Boost up to 3.3GHz) with 6MB L3 cache, Intel HD Graphics 4000, 16 GB ram, 240 GB OWC Extreme Pro 6G Solid State SATS Drive startup disk, 1 TB internal SATA Dive, (2x) 1 TB External Glyph Studio 7200RPM eSATA Drives, 500 GB External WD Drive

SkipNo Beet Productions
User avatar
by peterbirch on Wed Jan 16, 2019 3:14 am
[/quote]
Did you do the versioning in the Song window?
If the Project was built on master from SONGAA and SONGBB original version then the project will still be there.[/quote]
Who said the project was not there? Versioning was done by song, how else do you do it?
A, B, C or D? I noticed you didn't answer. Because you haven't tried it, I would go so far to say no-one has.

Digimax FS, 1818VSL
User avatar
by vanhaze on Wed Jan 16, 2019 3:50 am
pawelhebda wroteThis version prevent external scripts to be loaded!!! So no more great addons.


Indeed, Studio One X extensions are not loaded anymore in this S1 version and thus i can't use them anymore.
This is a real major bummer for me, i used them alot, it brought great extra functionality in S1,
especially in the MIDI area.

Why Presonus ?! :hunf:

Macbook Retina 2015 | OSX Mojave (latest version) | Studio One Pro 4 (latest version) | UAD Apollo Twin Thunderbolt
User avatar
by jazzundso on Wed Jan 16, 2019 4:20 am
vanhaze wrote
pawelhebda wroteThis version prevent external scripts to be loaded!!! So no more great addons.


Indeed, Studio One X extensions are not loaded anymore in this S1 version and thus i can't use them anymore.
This is a real major bummer for me, i used them alot, it brought great extra functionality in S1,
especially in the MIDI area.

Why Presonus ?! :hunf:

This can happen with every new update of Studio One. The Studio One X (3rd party) developer has to adjust his extension for the current Studio One version to make sure everything is still working. This has always been like that and won't change in the future since the Studio One X toolbar is not officially supported by Studio One / PreSonus at all.

This is a real major bummer for me, i used them alot, it brought great extra functionality in S1,
especially in the MIDI area.

Which of these functions in the MIDI area do you use most? (which are missing in Studio One itself..?)
Last edited by jazzundso on Wed Jan 16, 2019 5:39 am, edited 1 time in total.

Lukas Ruschitzka - composer, keyboardist, software developer from Mainz, Germany
http://www.lukas-ruschitzka.com || https://soundcloud.com/jazzundso || http://www.recording.de || http://www.youscreen.de

Core i7 3.24 GHz, Windows 7 (64 bit), 24 GB RAM, RME HDSP 9632, PreSonus FaderPort, PreSonus Monitorstation, PreSonus Eris 5

M-Audio Axiom Pro 61 - Clavia Nord Stage 2 - Moog Sub 37 - YAMAHA MoXF6 - Studio One 4 - Notion 6 - Sibelius 7.5 - EWQLSO Gold, EWQLS Choirs, VSL Special Edition, Spitfire Albion One, ProjectSAM Symphobia, Heavyocity Evolve, AEON, Damage, KOMPLETE 9 Ultimate
User avatar
by jonnylipsham on Wed Jan 16, 2019 5:29 am
vanhaze wroteIndeed, Studio One X extensions are not loaded anymore in this S1 version and thus i can't use them anymore.
This is a real major bummer for me, i used them alot, it brought great extra functionality in S1,
especially in the MIDI area.

Why Presonus ?! :hunf:


The developer of Studio One X is no longer developing it. A year or two back his entire system was hacked. He got scared off. Development on it was suspended permanently. PreSonus has never had anything to do with the "X" scripts. The developer is completely independent.

Please add your specs to your SIGNATURE.
Search the STUDIO ONE 4 ONLINE MANUAL. Access your MY.PRESONUS account.
OVERVIEW of how to get your issue fixed or the steps to create a SUPPORT TICKET.
Needs to include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce.



Gear:

Scan Computers UK 3XS Audio PC (Quad core i5 3.8GHz 8GB RAM) Windows 7 | Studio One 3 & 4 Professional | Notion 6 | Audiobox USB | Studio 1824c | SludioLive 16 Series III mixer | FaderPort (Classic) | Monitor Station v2 | Eris E5 monitors | HD7 & HD9 cans
User avatar
by jonnylipsham on Wed Jan 16, 2019 5:33 am
peterbirch wrote

"Did you do the versioning in the Song window?
If the Project was built on master from SONGAA and SONGBB original version then the project will still be there.[/quote]
Who said the project was not there? Versioning was done by song, how else do you do it?
A, B, C or D? I noticed you didn't answer. Because you haven't tried it, I would go so far to say no-one has.[/quote]"

Personally, I have versioning working fully as expected as demonstrated by Marcus in his video. So, I therefore suspect user error is at play there somewhere.

Please add your specs to your SIGNATURE.
Search the STUDIO ONE 4 ONLINE MANUAL. Access your MY.PRESONUS account.
OVERVIEW of how to get your issue fixed or the steps to create a SUPPORT TICKET.
Needs to include: 1) One Sentence Description 2) Expected Results 3) Actual Results 4) Steps to Reproduce.



Gear:

Scan Computers UK 3XS Audio PC (Quad core i5 3.8GHz 8GB RAM) Windows 7 | Studio One 3 & 4 Professional | Notion 6 | Audiobox USB | Studio 1824c | SludioLive 16 Series III mixer | FaderPort (Classic) | Monitor Station v2 | Eris E5 monitors | HD7 & HD9 cans
User avatar
by peterbirch on Wed Jan 16, 2019 6:43 am
Apparently no-one reads any more. Read my original post. This is NOT about versioning per se it is about projects.
Do this...
Go to project that you created before 4.1.2
Change the versions of these songs in the NEW versioning.lets say you wanted more tracks in your songs.
So you have the original songs and project from 4.1.1
Now your original songs are called Verison 1.1
Edited to make clearer..
Old project called FRED contains a song called JOE, FRED was created in 4.1.1
In 4.1.2 make a change to JOE and version it to JOE-V1
re-compile project FRED

Go into Project and it will say you've changed the songs in the project and redo them but with the ORIGINALS.
this wrong as you have moved on with ver1.1 as this is now saved as your working version.
Yes if you don't like it you can go back to the originals and redo but that is a different scenario.

Digimax FS, 1818VSL
User avatar
by roland1 on Wed Jan 16, 2019 7:21 am
I suspect some are treating the word "Project" as meaning song, not Project.

I use: Studio One Pro v4.1 & v3.56 on an i7 7700 win10 PC w16GB RAM and on a Mac Pro Tower (Sierra) w/RME & Focusrite interfaces.

When not loitering here, I can be found at: http://RolandK.ca

Remember, deception and commerce are old friends. Always ask questions; don't just nod and agree as expected.
[Unless it's on sale and there's a warning that says: "Hurry. Act now!"]
User avatar
by philangus on Wed Jan 16, 2019 1:43 pm
:thumbdown: :thumbdown: :thumbdown:

Well it's completely screwed some of my songs! :roll: Have any of you tried loading songs where audio bend had been used?

I have installed the latest version, 4.1.2 from the previous latest version 4.1.1 and it has completely corrupted some of the audio. As far as I have been able to work out, so far it seems to be audio tracks that were edited with audio bend. A lot of the tracks either have lots of sporadic digital distortion, or they have audio content missing! I desperately now need to back by version to the previous version and assess the damage. I just hope some of the historical auto-backups still work! I also noticed someone else has reported this issue in the question section.
User avatar
by roland1 on Wed Jan 16, 2019 9:19 pm
Thanks for the warning. I'm not going to install on my main computer. Don't need to find out after the fact (of losing files) that it's being looked into...

Philangus, you will now be asked for your system specs. There may also be a body cavity search. No one is above suspicion. :)

philangus wrote:thumbdown: :thumbdown: :thumbdown:

Well it's completely screwed some of my songs! :roll: Have any of you tried loading songs where audio bend had been used?

I use: Studio One Pro v4.1 & v3.56 on an i7 7700 win10 PC w16GB RAM and on a Mac Pro Tower (Sierra) w/RME & Focusrite interfaces.

When not loitering here, I can be found at: http://RolandK.ca

Remember, deception and commerce are old friends. Always ask questions; don't just nod and agree as expected.
[Unless it's on sale and there's a warning that says: "Hurry. Act now!"]
User avatar
by dmitrypetrenko on Wed Jan 16, 2019 11:47 pm
Hello! New features and bug fixes are accepted with delight. But, unfortunately, I and some other users found a nasty mistake after updating the DAW to the current version. When changing the tempo of the loop (both audio and MIDI) in previous versions of the program, the boundaries of the selected area always remained in their places - for example, 4 bars were allocated.
In the updated version, when the tempo changes, the selection boundaries are moved separately - these can be 7 and 3, depending on the decrease or increase of the tempo. Of course, it does not cost anything to do additional mouse movements and set boundaries manually, but there is an element of discomfort. I hope this problem will be fixed!
User avatar
by PreAl on Thu Jan 17, 2019 3:26 am
philangus wrote:thumbdown: :thumbdown: :thumbdown:

Well it's completely screwed some of my songs! :roll: Have any of you tried loading songs where audio bend had been used?


roland1 wroteThanks for the warning. I'm not going to install on my main computer. Don't need to find out after the fact (of losing files) that it's being looked into...

Philangus, you will now be asked for your system specs. There may also be a body cavity search. No one is above suspicion. :)



No he's not, he's got corrupted projects.

He needs to go to support and create a ticket, I suggest he sends his projects.. preferably simplified, before and afterwards.

Reading this thread has put me off updating sadly.

Studio One Pro 4, Faderport 1, Atom, Focusrite Saffire Pro 40, Maschine Studio, Octapad SPD-30, Roland A300, Windows 10 Pro 64 bit.
EVGA Geforce 1070 (Nvidia drivers). A bigly amount of other gear.
User avatar
by Lawrence on Thu Jan 17, 2019 8:19 am
vanhaze wroteIndeed, Studio One X extensions are not loaded anymore in this S1 version and thus i can't use them anymore.

Why Presonus ?! :hunf:


Must be a macOS thing as it still works here on Windows and the other part (the mp3 dll hack) never worked for macOS anyway.

That's one of the potential downsides of using or becoming dependent on free tools, that there is never any guarantee of ongoing support and/or updating from a developer. He or she may simply grow tired of developing or fixing it and since you never paid for it you can't really complain.

User avatar
by roland1 on Thu Jan 17, 2019 10:13 am
You got 3 likes from 3 moderators. God, I love politics. :D

It's true though about relying on free stuff from outside developers that could be ignored or abandoned.

That's why I prefer to rely on Presonus.

[I'll be performing my routine all this week at the luxurious Taj Mahal. Free water from Flint will be served.]

I use: Studio One Pro v4.1 & v3.56 on an i7 7700 win10 PC w16GB RAM and on a Mac Pro Tower (Sierra) w/RME & Focusrite interfaces.

When not loitering here, I can be found at: http://RolandK.ca

Remember, deception and commerce are old friends. Always ask questions; don't just nod and agree as expected.
[Unless it's on sale and there's a warning that says: "Hurry. Act now!"]
User avatar
by ganrob on Thu Jan 17, 2019 10:35 am
dmitrypetrenko wroteHello! New features and bug fixes are accepted with delight. But, unfortunately, I and some other users found a nasty mistake after updating the DAW to the current version. When changing the tempo of the loop (both audio and MIDI) in previous versions of the program, the boundaries of the selected area always remained in their places - for example, 4 bars were allocated.
In the updated version, when the tempo changes, the selection boundaries are moved separately - these can be 7 and 3, depending on the decrease or increase of the tempo. Of course, it does not cost anything to do additional mouse movements and set boundaries manually, but there is an element of discomfort. I hope this problem will be fixed!


I can confirm this behavior, and it is a bit of a pain for me as well.

Issue: When changing metronome tempo, left and right locators shift in the timeline
Steps to reproduce:

1. In a Song, set the Left and Right Locators in the Timeline Ruler at the beginning and end, respectively, of the area which you would like to loop.
2. In the transport, edit the metronome speed by either double clicking the current value and entering in the new value, or use the mouse scroll wheel while hovering over the current value

Result: Left and Right Locators have moved from the position in the beat.

Expected behavior: After tempo change, left and right indicators remain in the same beat positions.

Example: Set a loop from measure 3 to 6. Change the tempo. Loop has now shifted away from measure 3 to 6. Try not to curse.
User avatar
by gregghart on Thu Jan 17, 2019 11:11 am
I love your last step....try not to curse. Brilliant.

Win10x64 (Eng), Studio One 3.5 / 4.1, 32GB DDR4 RAM, Intel i7 5820, nVidia 960, Focusrite 18i8. Native Instruments Komplete Kontrol S88, Native Instruments Komplete Kontrol S61, Presonus FaderPort 8.

Please upvote this request for Pattern Editor: https://answers.presonus.com/28571/patt ... 571#q28571
User avatar
by PreAl on Thu Jan 17, 2019 12:31 pm
I appreciate there is a regular cycle of updates every 3 months or so, I do quite like this schedule it works well.

However I do hope Presonus can do some quick-ish regression fixes on what has been identified in this thread.

Obviously Studio One X is a "won't fix" however, it's not Presonus's problem.

Studio One Pro 4, Faderport 1, Atom, Focusrite Saffire Pro 40, Maschine Studio, Octapad SPD-30, Roland A300, Windows 10 Pro 64 bit.
EVGA Geforce 1070 (Nvidia drivers). A bigly amount of other gear.

59 postsPage 2 of 3
1, 2, 3

Who is online

Users browsing this forum: No registered users and 17 guests